Keith E. Moe wrote:
First, since the SRB is a unit of work that is independent of any existing dispatchable unit in the Master, any normal error that occurs within it has no impact on any other work in the address space. If it abends, it doesn't take a TCB with it. (The SRB must still use appropriate recovery, though.)
One of the very nice aspects of SRB design is that, from a recovery point of view, SRBs can function as a logical extension of the scheduler's TCB or other so-called "related" task. Specifically, when PTCBADDR= is specified on IEAMSCHD, the system percolates errors back to the related TCB -- usually the one from which IEAMSCHD was issued. (You see this as SPRC records in the system trace.) If an SRB without an FRR routine abends, a LOGREC software error record is cut and the related TCB is abended. If that TCB has an ESTAE routine, it gets control.
An SRB will want to establish its own FRR for recovery if it allocates resources that must be cleaned up if it abends, if time-of-failure SDUMP is desired for problem diagnosis, if it wants to inhibit LOGREC software error recording, etc. Otherwise, any errors can be dealt with by the related TCB's ESTAE routine ... or not.
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
