Right. That's a semantic misnomer from my part. I said that because that's where the LPAR is told what load device to run from is. The thing is that the ramdisk image worked and accessed the devices properly. Should I manually run a silo command with the T2 option specified? I am unsure if YaST did that all properly.
Thanks for the info on the subchannel status. That give me someplace to start. Jim: The device status is Channel End + Device End, which is normal. The subchannel status is Incorrect Length, which may indicate that you have something wrong with your image on disk. The associated channel program should start at absolute location 8. See "Initial Program Loading" in the Principles of Operation for details. You aren't booting "from" the SE, by the way. You're booting via the SE from DASD. The SE is just the messenger. Romney On Mon, 11 Mar 2002 10:05:22 -0600 James Melin said: >Has anyone seen this message on the SE console when attempting to ipl a >freshly installed Linux? > >The load control unit or device is busy. Device status is 0C and >subchannel status is 40. > >This is in a G5 with Ficon to a ficon director and from there into an IBM >'shark' dasd box. > >I'm having trouble finding the device status codes and subchannel status >codes as they might pertain to an initial load from the service element.
