It is 0. I know this because I do a compare for anything other
than zero going to S0C3 ( EX 0,*).
Regards,
Steve Thompson
On 10/03/2016 03:11 AM, Rupert Reynolds wrote:
To get things clear, what's the RC from ATTACHX?
Rupert
On 1 Oct 2016 00:05, "Steve Thompson" <[email protected]> wrote:
I'm doing some work and needed to do an ATTACHX with an ECB.
So for test purposes I'm attaching IDCAMS. It runs and gives CC=0.
Ok, in the main task, I've done the ATTACHX with the ECB and then went and
did a few instructions and then did a WAIT for the ECB.
CPU trace shows I don't get dispatch again until the POST is effected for
the ECB.
I've looked at the ECB and my understanding of the doc for ATTACHX is that
it gets posted with the CC from the sub task, or ABEND if it is that the
program ABENDed.
My ECB has, what appears to be, an RB address.
Now I did have it giving me back the zero (hey, ATTACH IEFBR14, it works).
But now with IDCAMS or an internal program (written to give S0C3 to test
what happens), I'm getting other than what is documented.
I've taken various dumps, I've been tracing using SVC 50 (originally
documented as NOP now reserved, but it still works as NOP).
I tried capturing the contents of the ECB before issuing the DETACH in the
case it gets changed by the effect of the DETACH, but it is the same before
and after.
I'm just baffled.
Anyone know of a working example I could take a look at?
Regards,
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
