Hi Rob, Q SET shows Machine ESA, and I changed the storage to 256M after the first install attempt because the ramdisk system spits out a message saying it really needs that much in order to install without problems. I'm not too sure what you mean about the contents of /boot changing after zipl and pointing the wrong way. That's possible I suppose, but I'm not sure how it might have happened. The only thing I've done since the install & failed ipl was to link the minidisk to another Linux guest so I could re-run zipl. I linked the mdisk with a CP link command, then dynamically allocated it to Linux using "echo 'add range.....' >> /proc/dasd/devices" command, mounted it to /mnt, chroot /mnt, cd /boot, and ran zipl. Did I miss anything or mess up somewhere? I haven't had a chance to start the ramdisk system again to run zipl that way, but I'll do that next.
The Trace I displayed: Ready; T=0.02/0.03 22:40:44 trace i HCPTRI1027I An active trace set has turned RUN off. -> 00F22548 BZ 4780C0E0 -> 00F22558 CC 0 CP IPL 151 CLEAR Tracing active at IPL -> 00002008 ???? 0000 *** 00002008 PROG 0001 -> 00000000 OPERATION CP Someone else suggested that I issue a trace prog run and then ipl. That displayed: trace prog run HCPTRI1027I An active trace set has turned RUN off. Ready; T=0.01/0.01 22:54:22 cp ipl 151 clear Tracing active at IPL -> 00002008 ???? 0000 *** 00002008 PROG 0001 -> 00000000 OPERATION HCPGIR453W CP entered; program interrupt loop *** 00000000 PROG 0006 -> 00000000 SPECIFICATION CP I'm new to VM and none of this means anything to me, but all the zeros have me worried. I would expect instructions or numbers or almost anything else if I were doing this in MVS; zeros are just about the last thing I'd want to see. Sue Rob van der Heij wrote: > On Wed, 2004-02-04 at 08:08, Sue Sivets wrote: > > I just finished installing Suse Linux on a VM mini disk (previous installs were > > in standalone lpars). When I tried to ipl the system for the first time I > > received the following message: > > HCPGIR453W CP entered; program interrupt loop > > Since I wasn't at all sure the ipl text really was written, I linked the new mini > > disk to another linux guest and re-ran zipl. The system still doesn't ipl. > > Has anyone run into something like this before? Does anyone have any ideas about > > what I can or should do next? > > Could it be that the userid is in XC mode (Q SET) now, or maybe short of > storage? If zipl did not write the IPL records you'd get different ones. > One option could be that the contents of /boot changed after zipl and it > now points the wrong way. You could make sure and start from the ramdisk > system again, load the dasd driver and re-run zipl. > If nothing else you could run TRACE I during IPL and see where it gets. > > Rob -- Suzanne Sivets Systems Programmer Innovation Data Processing 973-890-7300 Fax 973-890-7147 [EMAIL PROTECTED]
