On Wed, 26 Mar 2008 19:48:32 -0400, Bob Rutledge <[EMAIL PROTECTED]> wrote:
>... >> Under SLIP ACTION=SYNCSVCD, it says: >> >> "SLIP will stop the unit of work before starting the dump ... > >I should have added that, since SYNCSVCD is used (only) with >PER traps, ... Aha! That explains why I can't find anything comparable to ACTION other than on SLIP. > ...it can be more than "good for diagnosis". You really >want the work that altered that storage or fetched that unexpected >instruction to sit still while it's having its picture taken. >... Well, I guess it depends on what "unit of work" means. If it means the TCB or RB, I agree. If it means the whole address space, then I'm not so sure. But I suspect it *does* mean the TCB or RB. I had not been thinking of it like that. Today I saw an SVCDUMP that had "SYNC DUMP" in its title and wondered what that implied. It was taken during an ECSA shortage event where many address spaces locked up. I was afraid the dumps were adding to the problem. (Maybe they were. Are all SVCDUMPS synchronous?) It's probably more likely we still have QUIESCE=YES somewhere. BTW, I *DID* need remedial manual reading. I didn't know that one BookManager found a reference in a section you then have to switch to a browser FIND function to find additional references in that section. You don't (or at least *I* don't) get multiple BookManager search results for multiple hits in the same section. :-( Pat O'Keefe ---------------------------------------------------------------------- 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
