If you only have about 20 minutes of batteries left, do as orderly a shutdown as possible. (Even our heavily loaded production system doesn't take 20 minutes to come down.)
As pointed out before, get the major players down (IMS, DB2, CICS) - those that have business critical transactions that may take a long time to recover. The 'rest' (meaning MVS components) are pretty robust. >From experience on education systems I'd say the $PJES2 isn't even >necessary. I would not subscribe to that. $PJES2 should always be done. If JES2 comes down is another matter. >I've always seen JES2 stopping after the V XCF OFF before the final 0A2 >arrived. True. When JES2 does not come down after $PJES2 doing the V xcf,off is my cure-all (since I can never remember the commands that would tell me which UNIX process is still up). That's why I drum it into operator's heads to use the v xcf command even on monoplexes. >This makes me belive JES2 is one of the (few?) products that listens for >the forthcoming offline that XCF communicates and then terminates in a >clean quick manner. Actually, *every* xcf group member gets the notification that a system is about to leave, listening to or not. It's just that not every member of an xcf group terminates itself on the system being removed (if it'S still up). But the cleanup interval (until the wait state is loaded) is there exactly for cleanup purposes. Best regards, Barbara -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner ---------------------------------------------------------------------- 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
