I assume you meant 01000B1 since 100B1 is not documented. The manual says wait state 0b1, reason 01 is data set not found. At the top it references the LOADxx member of parmlib, the IODF, or a device.
We are also using COD 1.9 (on a z10BC). We IPL from D48 (D9ESY1) and our load parm is 0D4621M. D46 is the catalog volume (D9ECAT) and that is where our SYS1.IODF01 is located. We put member LOAD21 in both SYS1.IPLPARM and SYS1.PARMLIB (both on D9ESY1, the SYSRES volume). Both copies are identical and say "IODF 01 SYS1". We don't have any IPL problems. Does your IODF match the active IOCDS? Is your IODF statement in the correct columns? Does it point to the correct IODF DSN? Is the HLQ correct? Has PARMLIB gone into extents? -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Larry Macioce Sent: Wednesday, September 29, 2010 7:24 AM To: IBM-MAIN@bama.ua.edu Subject: Help in troubleshooting CoD load I am trying to put up a CoD(z/OS1.9) as I am sitting on a 1.6 system. I used HCD to copy the current IODF to the sysres of the CoD. I have made the changes in the CoD installation guide. First time I ipled I rec'd a disabled wait 100B1...iodf problem..when I looked I had not put the correct parm in the load parm area of the ipl info on the console. Fixed that reipled and came up with an disabled wait 88 (ipliea50)loadxx and parmlib. Reread the guide it then says to move it(which it already was in sys1.iplparm) so I moved a copy into sys1.parmlib so it could be found. reipled and here i sit with a disable wait of 100b1 again...what am I missing?? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
