Re: Is TCBECB supposed to be zero at end of task?

-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Peter Relson Sent: Saturday, September 08, 2007 8:01 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Is TCBECB supposed to be zero at end of task? I don't feel a whole lot of need to answer thi

Re: Is TCBECB supposed to be zero at end of task?

Thank you all for your replies. Peter thanks for confirming my original TCBECB question. I decided to solve the problem by creating an ETXR "stub" routine that is less than 128 bytes long. The stub is copied to the end of each subtask's context area. Each instance of a subtask get passed this c

Re: Is TCBECB supposed to be zero at end of task?

I don't feel a whole lot of need to answer this, as TCBECB is not a programming interface so you should not be relying on the contents of that field or current system behavior in regard to that field. But, for what it's worth, it is definitely the case that the normal system processing of "detach"

Re: Is TCBECB supposed to be zero at end of task?

On Fri, 7 Sep 2007 10:40:18 -0500 Vic Petrone <[EMAIL PROTECTED]> wrote: :>I have a main program that attaches a subtask. The main program specifies :>both ECB= and EXTR= on the ATTACHX macro. The ECB pointed by ECB=, :>resides ***within*** a subtask context area allocated by the main program.

Is TCBECB supposed to be zero at end of task?

I have a main program that attaches a subtask. The main program specifies both ECB= and EXTR= on the ATTACHX macro. The ECB pointed by ECB=, resides ***within*** a subtask context area allocated by the main program. When the subtask terminates, the ETXR routine receives control with the addres