Every SVC Dump, more or less, stops the tasks of the address space being dumped (sets them non-dispatchable) until the data for that address space is captured. But stopping does require "time" and other tasks continue running until the "stop" takes effect. And SRBs are not stopped. (The "global capture" phase of the dump sets the whole system non-dispatchable except possibly for non-quiesceable SRBs, but once that phase is done, it is only the tasks of the individual address spaces that are non-dispatchable
SYNCSVCD is basically the same as a single address-space SVC-entry SVC Dump -- the caller does not get control back until the dump data has been captured. If there are other tasks involved in the address space, their behavior is identical between SYNCSVCD and SVCD. When SLIP takes an SVC Dump, it is branch-entry. A normal branch-entry SVC Dump returns to the caller after capturing the summary dump part of the dump (prior to capturing the private storage for the dump). SYNCSVCD changes this behavior, in the hope of getting a dump that better reflects the state of that task. Capturing summary dump data is often the key to a "good" dump. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
