> (BTW, why should PR/SM care what OS is to be run in the LPAR?) So it can know which one the IFLs can be given to? It was probably not using IFLs either since it was defined as MVS. I've been told also that you get a little penguin picture there somewhere too. Course I haven't actually seen it since no one lets me near an HMC.
Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, January 14, 2008 2:41 PM To: [email protected] Subject: Re: [LINUX-390] IODF-HCD Defining FCP on a z9 for z/Linux >>> On Mon, Jan 14, 2008 at 5:11 PM, in message <[EMAIL PROTECTED]>, Alan Altmark <[EMAIL PROTECTED]> wrote: -snip- >> Define "attached" in this context. > > "Configured" is the term of art. As long as the chpids, CUs, and > devices are configured to the VM LPAR (via IOCDS, HCD, or dynamic > DEFINE), then CP > (EDEVICE) and Linux (ATTACH or DEDICATE) can talk to the FCP adapters. This was the problem the OP was having. Since the LPAR was defined as being an "MVS LPAR" (BTW, why should PR/SM care what OS is to be run in the LPAR?), HCD would not allow him to configure the FCP I/O devices onto the LPAR. He had to either create a new LPAR definition, saying it was a "VM LPAR" or delete and redefine the existing one. > The above is necessary, but typically not sufficient. Additional > configuration of your SAN fabric is usually required to give Linux > and/or CP access to the target WWPNs & LUNs. Sure, but you have to get past the first hurdle before you can even try to deal with these items. Mark Post ---------------------------------------------------------------------- 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
