On 7/26/06, Jeff Gribbin, EDS <[EMAIL PROTECTED]> wrote:
Er ... meanwhile back at the original problem ... Folks, Ed is reporting that EVERY attempt to issue CP IPL command to ANY vdev is ALWAYS generating HCPCLS174E on a system that is otherwise running happily. Now, sorry and all that, but I just don't buy the idea that these symptoms match with a faulty paging pack - the symptoms are too consistent
You're right, we go distracted by interesting unrelated problems. A true paging error on 1st level would have caused other problems. So he is just getting the HCP174E because the IPL is not architected to have other ways to complain. As you suggest this happens in IPL and so that will be nothing traced by a virtual machine trace. There's a few different routes through HCPCLS that end in the 174E message. It would be nice to set up some TRSOURCE traps to see which HCPTRANS is involved and why. You'd need to look at a listing of HCPCLS at your level to find the right spots. PS This does look familiar. It crossed my mind that the virtual machine might simply be too small, but that does not seem possible. When you're very small there's the HCPVMI232E and beyond that CMS will detect it. Rob
