I don't know if compiled REXX works differently from interpretive. There is a possibility that you are executing an ISPF service or something that isn't interruptible.
I know that I might have to hit ATTN a few times and enter the HI command to break a looping or long running REXX. Can you execute with TRACE? Is there a call to a REXX external routine that you can substitute your own code and use it to stop your REXX? HTH On Tue, Jun 16, 2009 at 3:37 AM, Patrick O'Keefe<[email protected]> wrote: > What is the supposed difference between HI and HE to REXX? > I have never been able to terminate an errant exec under TSO > with an HI (even though the response to ATTN tells me I can). > Is there anything that would make HI work in some installations > but not others? > > I specifically said "in some installations" rather than "for some > exes" because I've got a problem with an IBM-supplied NetView > exec that is misbehaving in our shop. An internally issued HI is not > stopping execution of the exec for me but, of course, works fine > for IBM. (It's compiled REXX so I can't see what is going on.) > > This is a hare-brained idea, but I wonder if there could be something > in my shop (my last 2 shops) that would prevent HI from working. > > BTW, I tried searching the archives, but a search for REXX plus HI or > HE finds a few too many irrelevant hits. :-) > > Thanks. > Pat O'Keefe > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
