On 7/25/06, Jeff Gribbin, EDS <[EMAIL PROTECTED]> wrote:
If you set traces before issuing the IPL command you will, "see" the IPL Command Simulator running in guest storage and will (hopefully) gain some insight as to exactly what's happening at the moment that the error occur
But this was on a native IPL, not with a virtual machine from what I read. The cases where I got a paging I/O error was when the paging space had not been properly formatted. Either not formatted (because someone thought it was enuf to just do cyl 0) or after some playing with define mdisk in a way that the CC in the key did not match the real cylinder number. And I know that CP pages out some stuff very early in the startup. My approach would be to format the page space on that pack (but not after displaying the key fields in that range of cylinders to convince myself that I was right). Either by IPLing some rescue system if you have that, or by the Stand-alone ICKDSF (which also lives on your PARM disk I think). Rob
