On Tue, 16 Jun 2009 17:19:01 +1000, Wayne Bickerdike <[email protected]> wrote:
>I don't know if compiled REXX works differently from interpretive. I don't think the behavior is any different. I just mentioned that to indicate that I couldn't see what the exec was doing and that my diagnostic options were limited. > >There is a possibility that you are executing an ISPF service or >something that isn't interruptible. That could be the case in the past when I ran into this under TSO, but the most recent case is an exec running in NetView - no ISPF. > >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. I'm not sure how the equivalent process works in NetView. EXECs run as interruptable long running commands in sort of a pseudo- subtask. NetView has a read up while the exec is running and (I guess) issues an HI if the user enters a CANCEL or RESET. But I don't know what causes the REXX interpreter to give up control so that the CANCEL can be read and the HI presented. I don't know if I mentioned it but the CANCEL works fine for NetView lvl 2 but fails for me. > >Can you execute with TRACE? ... Nope. > ... Is there a call to a REXX external routine that you can >substitute your own code and use it to stop your REXX? > Not that I know of. 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
