Scheduling an SRB into the Master sure seem to be a touchy subject, I have two observations/comments.
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.) If the SRB schedules an IRB, the IRB abending can take an unsuspecting TCB down. Of course, the SRB could overlay storage in the Master and cause a systems crash, but anything running in Key 0, Supervisor State in ANY address space can cause enough damage to bring the system down. Running in the Master probably increases this by only a very small percent. Second, the blame really goes back to IBM's design of CADS. By their very nature, any CADS should have been made persistent and NOT tied to the life of the creating address space, i.e., it should have been maintained just like CSA/SQA and not automatically freed when the "owner" terminated. So the only place to create a CADS that must never go away is the Master. Keith E. Moe Laid Back Software, Inc. http://www.laidbacksoftware.com (408) 749-0655 Creator of the TSO Environment and Administration Manager Product. (I also do MAINVIEW support for BMC Software, Inc.) ---------------------------------------------------------------------- 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
