>:>a) The Extended Addressability Guide says that each workunit (TCB or SRB) >:>has its own stack. From that I it appears that the IRB is sharing the stack >:>with the orginating task. So, I won't be using the stack to save the state in >:>the exit. Hence the second question on the size of the save area provided by >:>the system for the exit. > >Why can't you use the stack? The IRB blocks the RBs older than it.
I guess you have a point. I was concerned with the ETXR abending and the messing up the stack for the originating task. I tested this and my ESTAI gets control, recovers and retries with the stack will reset to what it was upon entry to the originating task (I do not adjust SDWALSLV before retrying). I'll stay with using the linkage stack then - thanks! >:>As Binyamin noted, the system requires the ETXR to restore the regs. Since >:>the doc is not specific, I'll have to save and restore both GPRs and ARs - just >:>to be on the safe side. > >On the other hand, it may be doc that was true at MVS 3.8 and is no longer >required. Very true but all I have is the doc to go by. This is a moot point now, since I'm staying with using the stack. Cheers, Vic ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
