----- Original Message ---- From: Bill Neiman [EMAIL PROTECTED]
> Walter, > > When the documentation speaks about "automating" IXC102A, what it > really means is that the system will not issue IXC102A at all, with SFM > set up appropriately in a parallel sysplex. Barbara is correct - in a > parallel sysplex, SFM can isolate the outgoing system by fencing it from > the I/O subsystem, as long as there is a CF having connectivity to both > the outgoing system and some other system in the plex that can initiate > the isolation. You cannot achieve this function in a basic sysplex. Bill, I believe what you states, unfortunately I didn't understood that reading the book. Yes, Barbara is correct about isolating a system from the plex, but my point was another one. If you have a basic plex and you want to let SFM automate a system reset of a LPAR for a planning system shutdown, these stmts SYSTEM NAME(*) RESETTIME(20) in the SFM policy works fine. This is what I have experienced so far, and I would be grateful to you if you can confirm the following: 1. V XCF,my_lpar,OFF 2. R xx,SYSNAME=my_lpar ... system waits cleanup time (defined in COUPLExx), then goes in 0A2 ... ... system waits reset time (defined in SFM) then SFM resets the lpar .... 3. msg IXC102A pops up, having SFM reset the lpar I can safely reply R xx, DOWN (or automate the reply using my automation package) Sorry for being persistent on this, but I don't want to play with the fire, nor explaining rubbish to my operating staff. Best regards Walter Marguccio ---------------------------------------------------------------------- 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
