Re: Getting ABEND reason code from attached subtask

2019-08-06 Thread Peter Relson
Has all IBM code that issues an ABEND documented to give a reason code been updated to use the REASON keyword rather than just loading R15 before the ABEND? I'd assume "no" (the "subtle difference" is not one that causes enough grief to warrant the cost). A different approach to that question

Re: Getting ABEND reason code from attached subtask

2019-08-05 Thread Seymour J Metz
behalf of Peter Relson Sent: Sunday, August 4, 2019 7:54 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Getting ABEND reason code from attached subtask what about the normal completion reason code (R0)? "Normal completion reason code" is not a concept supported by z/OS. Of course there

Re: Getting ABEND reason code from attached subtask

2019-08-05 Thread Kirk Wolf
Thanks everyone! On Sun, Aug 4, 2019 at 6:55 AM Peter Relson wrote: > > what about the normal completion reason code (R0)? > > "Normal completion reason code" is not a concept supported by z/OS. Of > course there is "value in R0 upon normal completion" but that is not > surfaced. > > The TCB/

Re: Getting ABEND reason code from attached subtask

2019-08-04 Thread Peter Relson
what about the normal completion reason code (R0)? "Normal completion reason code" is not a concept supported by z/OS. Of course there is "value in R0 upon normal completion" but that is not surfaced. The TCB/STCB has the information that is available. Since you attached with ECB the TCB/STC

Re: Getting ABEND reason code from attached subtask

2019-08-03 Thread Greg Price
On 2019-08-04 4:06 AM, Kirk Wolf wrote: I'm curious. Say that I have something like: ATTACH EP=MYPROG,ECB=MYECB LTR R15,R15 BZ ATTERR ST R1,MYTCB WAIT 1,ECB=MYECB DETACH MYTCB I know that I can get either the subtask return code or ABEND completion code(s) from the ECB. But in the case of an A

Re: Getting ABEND reason code from attached subtask

2019-08-03 Thread Steve Smith
At ABEND, R15 contains the REASON. For a normal return, R15 contains the return code, and R0 often contains a reason, but that is a weaker convention. On a normal return, registers come back however the called program sets them. However, a subtask returns to the system. Maybe you could find the

Re: Getting ABEND reason code from attached subtask

2019-08-03 Thread Seymour J Metz
: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Getting ABEND reason code from attached subtask @Kirk, is the ABEND reason code somewhere in the TCB? I would do the search but you can do it as well as I. Is R0 = normal completion reason code "architected"? I don't recall that it is. It is something of a

Re: Getting ABEND reason code from attached subtask

2019-08-03 Thread Charles Mills
* the contents of R0 have vanished. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Kirk Wolf Sent: Saturday, August 3, 2019 2:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Getting ABEND reason code from attached subtask I&#

Re: Getting ABEND reason code from attached subtask

2019-08-03 Thread Seymour J Metz
Subject: Getting ABEND reason code from attached subtask I'm curious. Say that I have something like: ATTACH EP=MYPROG,ECB=MYECB LTR R15,R15 BZ ATTERR ST R1,MYTCB WAIT 1,ECB=MYECB DETACH MYTCB I know that I can get either the subtask return code or ABEND completion code(s) from the ECB. B

Getting ABEND reason code from attached subtask

2019-08-03 Thread Kirk Wolf
I'm curious. Say that I have something like: ATTACH EP=MYPROG,ECB=MYECB LTR R15,R15 BZ ATTERR ST R1,MYTCB WAIT 1,ECB=MYECB DETACH MYTCB I know that I can get either the subtask return code or ABEND completion code(s) from the ECB. But in the case of an ABEND, is there an easy way to get the reas