On 30 September 2016 at 19: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 > 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. Did you zero the ECB before you did the ATTACHX? If the POST bit (X'40') is already on when you WAIT... > CPU trace shows I don't get dispatch again until the POST is effected for the > ECB. OK. What does the POST trace entry look like? R0 contains the value to go in the ECB. > I've looked at the ECB After you regain control after the POST, I assume... > 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. OK > My ECB has, what appears to be, an RB address. Is the POST bit (X'40') on? The WAIT bit (X'80')? Perhaps tell us the exact content of the ECB. > 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'm not sure what this means. When you ATTACH IEFBR14, your ECB looks good when your main wakes up? But when you ATTACH IDCAMS or other programs, it has an RB address? Or something else? Are you quite sure the ECB you WAITed on is one and the same as the ECB you gave to ATTACHX? Particularly if neither is initialized, or is in use for some other purpose, there's room for lots of trouble. > I've taken various dumps, I've been tracing using SVC 50 (originally > documented as NOP now reserved, but it still works as NOP). How does SVC 50 play into this? As a trace table entry marker? > 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. DETACH shouldn't affect this ECB. > I'm just baffled. So far, so am I. But I'll bet there's a simple problem here that you're not seeing. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
