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 runnin g happily. Now, sorry and all that, but I just don't buy the idea that thes e symptoms match with a faulty paging pack - the symptoms are too consisten t and there are no other symptoms - remember that this system is UP AND RUNNING, with LOTS of active users - unless Ed's current system pagerate is really and truly zero, for this to be the one-and-only symptom of a faulty page volume would be downright bizarre. Now, IIRC, the way that CP, "loads" the IPL simulator is by first paging out a guest page (page 1?) and then messing with the guest's page tables to point the guest page at the IPL simulator which sits inside the CP nucleus (it's been several years - can anybody help out here?) and then dispatching the guest, which triggers a pagein. This, "feels" like the only paging operation that's going to be common the ALL IPL VDEV commands . Comment? Personally, for starters, I'd be using TRACE ALL (probably NOT to the console, but to the virtual printer) just to get a feel for how long it goes before it crashes - and then, "fine down" the trace based on that experience. If Ed gets HCPCLS174E before any instructions are executed then we'll have a, "smoking gun" pointing straight at the process that saves the guest page and then loads the IPL Simulator - if not then at least one real possibility will have been eliminated. (A thought - the guest page is probably not saved with IPL CLEAR - Ed, can you confirm tha t IPL vdev CLEAR fails as well as IPL vdev NOCLEAR?) I have a second Euro that I'll stake against a nickel that says that this is NOT a problem with Ed's paging packs - any takers for THIS one? Regards, Jeff (Eliminate the impossible) Gribbin
