1) Does the ETXR exit routine share the Linkage Stack with the originating task?
Depends on your definition of the "originating" task. The ETXR runs under the control of an IRB on the attaching task when the attached task has ended. Typically all you would do in the ETXR is detach the ended task, but you might also have some application tidy-up to do. So from a strictly literal point of view, the linkage stack that the IRB sees is logically the same as the one that existed when the (now ended) task was attached. But... you really cannot (legally) know anything about that stack. You can use it to save/restore your own state, but that's all. If you try to extract anything from the stack entry that is "current" when your IRB gets control you will get a linkage stack exception because the system makes the stack entry look invalid to prevent ill-advised snooping. 2) Is the savearea pointed by R13 upon entry to the ETXR routine, 72 bytes long? (i.e. long enough to hold 16-32 bit GPRs but not long enough to also hold 16 ARs) You can't count on there even being a save area and since you're getting control in a freshly minted RB you don't need to save the "callers" state at all. When you're done, you DO need to return to the OS by issuing SVC 3, or branching to the address you got in R14 on entry to the IRB - which (surprise surprise surprise) points to an SVC 3 anyway. CC ---------------------------------------------------------------------- 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
