> When you IPL a new operating system via autoipl (does that work?), > is there any gotcha other than to remember to always CLPA?
When SADMP starts an IPL of MVS, it is essentially the same as if you did a Load Clear from the HMC. We don't know or care whether it is a new or old operating system. > If a system is in a tight loop (like memterm in master), will the > sadump option on the vary command issued on *another* system, not > the looping one (and assuming that an sadump policy is established) > work? Or will it just get stuck behind whatever other messages XCF > couldn't get at because it couldn't get the processor? AutoIPL processing is driven by the wait state code/reason code that ends up occurring, so the question is, what would that be in the situation you are describing? If the system is alive enough that XCF's status update task can get dispatched and read from the couple data set, then I would guess that you could end up with the desired 0A2 wait state with the reason code for the DUMP/REIPL options of VARY XCF,OFF. If it is not alive enough to do that, and you have SFM set up to do fencing, then the system should eventually get fenced because it is not updating its status, and it should be able to respond to being fenced by loading the 0A2-104 wait state. (It only needs to be alive enough to process a machine check and dispatch an SRB in *Master* for that to happen). 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: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
