Robert, Is there any chance that the DASD device is *reserved* to another system? Personally, I'd make sure that it was OFFLINE to all other systems (z/OS, z/VM, ...).
The reason that I say this is that we had something similar (too long ago to be sure) happen when one system was backing up the IPL volume for another system. The IPL failed because the backup on the other system had a DASD reserve on the pack. -- John McKown Senior Systems Programmer UICI Insurance Center Applications & Solutions Team This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Robert Kippers > Sent: Friday, May 28, 2004 8:31 AM > To: [EMAIL PROTECTED] > Subject: Linux install > > > I'm in the begining stages of loading Linux a separate lpar. I have > IPL'd off the the tape and went through the process to ipl off dasd. > When I IPL of dasd I receive the following error message: > "The Load control unit or device is busy" . > Yes, dasd address is defined as being shareable to other lpars. Is the > reason why I am receiving the error message? > > tks > > - Rob > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390