> My reading of the commands manual leads me to believe > that syncsvcd only stops the current UOW, a TCB in another AS in > this case? All the other stuff running in the Primary AS and comming > from other Secondary ASs will still run? Or have I got that wrong? > > I'm going to try maxing out the size of my trace tables but I still > won't trap the events if all the other work keeps running before the > data is captured.
SLIP A=SYNCSVCD to stop the unit of work under which the PER event occurred, when conditions at the time of the PER event allow the work unit to be stopped. SDUMP subsequently sets all of the TCBs (below the dump TCB) in an address space to be nondispatchable while the dump TCB it capturing that address space. The STATUS STOP for those TCBs is done asynchronously by an SRB scheduled to the address space. SRB dispatching in the address space is not affected. So if you have changed your program to take work which used to run under a TCB and instead run it under an enclave SRB so that you can run it on a zIIP, you may experience some reduction in serviceability because this work will no longer be automatically stopped by SDUMP while SDUMP is capturing the address space. That is just one of the negative consequences of converting TCB work to be SRB work. You can get some information about when the SDUMP events occurred by doing VERBX IEAVTSFS against the dump of interest. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
