Re: REXX HI vs HE
On Tue, 16 Jun 2009 18:23:47 -0400, Tony Harminc tz...@attglobal.net wrote: ... HI and friends are conditions in the REXX interpreter, that are checked at each instruction (REXX clause, I assume that means). It's just a matter of turning the flag on using the IRXIC service, and the interpreter will notice it some time real soon. ... Thanks. Good information. My original question can be ignored. IBM finally reproduced the condition I ran into. There is definitely not any global condition influencing REXX behavior; it was a bug in the exec. (I do not understand IBM's initial difficulty reproducing the problem but I've decided not to inquire.) Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX HI vs HE
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'Keefepatrick.oke...@wamu.net 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX HI vs HE
On Tue, 16 Jun 2009 17:19:01 +1000, Wayne Bickerdike wayn...@gmail.com 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX HI vs HE
2009/6/16 Patrick O'Keefe patrick.oke...@wamu.net 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. HI and friends are conditions in the REXX interpreter, that are checked at each instruction (REXX clause, I assume that means). It's just a matter of turning the flag on using the IRXIC service, and the interpreter will notice it some time real soon. Unless, of course, there is a long-running single clause such as a call to some external environment. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
REXX HI vs HE
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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX HI vs HE
On Mon, 15 Jun 2009 12:37:23 -0500, Patrick O'Keefe patrick.oke...@wamu.net 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 should add that I understand that HI is supposed to raise the HALT condition where HE does not. My question is really if there is any installation-wide REXX option that would prevent HI from working ... but allows HE to work. ... Thanks. Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX HI vs HE
HI has always worked for me. Ken Klein Sr. Systems Programmer kenneth.kl...@kyfb.com 502-495-5000 x7011 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Patrick O'Keefe Sent: Monday, June 15, 2009 2:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: REXX HI vs HE On Mon, 15 Jun 2009 12:37:23 -0500, Patrick O'Keefe patrick.oke...@wamu.net 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 should add that I understand that HI is supposed to raise the HALT condition where HE does not. My question is really if there is any installation-wide REXX option that would prevent HI from working ... but allows HE to work. ... Thanks. Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX HI vs HE
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Patrick O'Keefe Sent: Monday, June 15, 2009 12:37 PM To: IBM-MAIN@bama.ua.edu Subject: REXX HI vs HE SNIPPAGE 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. SNIPPAGE I have the same problem, and I'm not using compiled REXX. However, we do have TRX installed. I have no idea if this is related to this particular problem, but I do know that when I am doing a lot of REXX and/or Panel work, I change my TSO logon to not use a proc that contains TRX (because it seems to cache the REXX and Panels that I'm changing). Regards, Steve Thompson -- Opinions expressed by this poster may not reflect those of poster's employer -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
