> Thanks Skip. We do have AUTOIPL coded but the SAMDP parameter is > NONE. I'll set this up and test it (if I can think of a way to > generate a wait state) duled automatic reIPL on z10 >
V XCF,sysname,OFF,DUMP,REIPL will generate a wait state while will drive AutoIPL processing. > I'm supposing that you have AUTOIPL coded in DIAGxx. AUTOIPL causes > automatic IPL in a situation that would otherwise leave you in a > wait state. We actually had this problem repeatedly early in R13 > because the system would run totally out of real storage, a problem > that was eventually fixed by APAR. The main point is that DIAGxx > should also include the SADMP parameter as shown below. It requires > that you configure standalone dump to work without manual > intervention, a good idea in any case. You should get an SAD for > most any wait state code other that V XCF,OFF. > > AUTOIPL SADMP(hhhh,SMSYSC) MVS(LAST) Unfortunately, the architected interface to the machine (LPAR) which z/OS AutoIPL uses to IPL standalone dump or re-IPL z/OS does not provide a way for z/OS to supply a wait state code. So there can be no logging of the wait state to the HMC. The only way to determine the wait state code is a standalone dump. When AutoIPL re-IPLs z/OS directly without a standalone dump, there is no way to determine what the wait state code was. Whenever a requirement come in to z/OS about this lack of logging, I respond that this is a requirement for the machine (LPAR), not z/OS. When/if LPAR chooses to enhance the interface to allow z/OS to provide a wait state code, z/OS will be happy to make use of it. 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
