> Does the PC routine (IEAARR) simply branch to the Target Routine (R15) > making it > an extension of the IEAARR PC Service Routine?
It's not necessarily "simply" and it depends on what you mean by "an extension of". But for the most part "yes". The IEAARR PC Service Routine runs in the caller's state and key (to the extent that an authorized user did what they're required to do). And yes, after doing whatever else it might feel necessary to do, it branches to the target routine. When the target routine returns to the system via the return address in reg 14, the system issues the PR to match the PC >Essentially, it works like a combo of BAKR and ESTAEX. I'd say it works like an ARR that you do not have to be authorized to define and use. ESTAEX is not used. That is why it is more efficient than issuing ESTAEX. It is not more efficient than an ARR if you happened to be in a position to use an ARR. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
