z/OS does indeed behave this way. Every volume is initialized with the non-sysres wait state code. This is how IBM can document the consequence of IPLing from a non-sysres volume. The wait state code gets overwritten by properly formed IPL text.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Eells Sent: Friday, November 13, 2015 4:00 AM To: [email protected] Subject: (External):Re: IPL wait state Actually, there is, as long as the volume has been initialized. (Thanks to JM for helping track this down.) From the ICKDSF book, under INIT: "If you do not specify IPLDD, ICKDSF writes special bootstrap records that cause the processing unit to be placed in a WAIT state if the volume or minidisk is specified during an attempt to load the system. Bit 12 of the wait state PSW is set on." I have not verified that this loads a WAIT00F, however. I suppose one could argue that this is a special case of IPL text (and I'd be forced to agree) but when we use that term we usually mean the one we write to IPL an operating system. So it seems we might have a volume that was not INITted or that has incorrect IPL text written to it. In any event, the best next action is unchanged: Write the IPL text and try the IPL again. Gerhard Adam wrote: > You can't get a wait state code because there is nothing there to load it. > All zeros is what you would expect if the "bootstrap" records never got > loaded. > > Sent from my iPhone > >> On Nov 12, 2015, at 6:58 AM, John Eells <[email protected]> wrote: >> >> Nathan Astle wrote: >>> Hello, >>> >>> I did applied some maintenance to my sandbox system. When i loaded >>> with the LPAR with the new address. >>> >>> i got the below message in the HMC, >>> >>> Central processor (CP) 0 is looping due to switching between program >>> status words (PSWs) that are not valid. The program status word >>> (PSW) is 0000000000000000. >>> >>> The IPLTEXT was not written to the newly cloned RES Volume. Could >>> that be a reason ? >>> >>> >>> I am not getting a correct explanation about x'000' on my search >>> about the above PSW in MVS manual codes. >>> >>> Any suggestions ? >>> >>> z/OS 1.11 >> <snip> >> >> I think (but have not tested that) you should get a 00F wait if you try to >> IPL from a volume with no IPL text. However, the IPL text--at the level >> matching the system you are trying to IPL--is required to IPL. If you never >> wrote it to the IPL volume the IPL will fail. <snip> -- John Eells IBM Poughkeepsie [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
