>And as far as I know, an SRB does not get automatically suspended >just because the PER hardware detects a hit. Definitely true. PER is no more than a program check. After processing the PER interrupt control continues at the PER address (unless you've directed SLIP to do something different, such as ACTION=RECOVERY). There is no status saving of the unit of work, it never takes a trip to the dispatcher.
>By the time slip got around to scheduling the actual dump request, >that SRB had already run to completion The idea's right, but one minor detail: SLIP will have "issued" SDUMP. SDUMP will have done SUMLST processing, and SDUMP will have "scheduled" the rest of the dump. All that will happen before the interrupted work unit continues. It's the "scheduled rest of the dump" that might not have begun before the SRB completed. Various other factors come into play related to system and address-space non-dispatchability and the "quiesce" option of the dump as to whether the SRB might or might not run to completion Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
