Re: IODF-HCD Defining FCP on a z9 for z/Linux
On Monday, 01/14/2008 at 05:43 EST, Mark Post <[EMAIL PROTECTED]> wrote: > 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. PR/SM doesn't care. IOCP doesn't care. HCD cares, wanting to ensure that you create a valid IODF for z/OS. Alan Altmark z/VM Development IBM Endicott -- 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
> (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: LINUX-390@VM.MARIST.EDU 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
Re: 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
HI guys, I figured it out. There are two sections in the IODF, an LPARNAME and a CONFIG-ID For sanity I had the LPARNAMES and the CONFIG-ID the same. The CONFIG-ID is for z/OS and I think VM. It has no meaning in Linux. The CONFIG-ID is defined in option 1. In OPTION 5 you can associate Devices to a CONFIG-ID so you can select which Devices go to what z/OS (via the IPLPARM(LOAD**) All you need for Linux in the IODF is options 3,4,5 and no need to connect the devices to a CONFIG-ID. Sam Bass 254-771-7212 Sr z/OS Systems Specialist -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, January 14, 2008 3:38 PM To: LINUX-390@VM.MARIST.EDU Subject:Re: IODF-HCD Defining FCP on a z9 for z/Linux >>> On Mon, Jan 14, 2008 at 4:11 PM, in message <[EMAIL PROTECTED]>, Robert J Brenneman <[EMAIL PROTECTED]> wrote: > Both Linux and VM can talk directly to the channels so you don't have to > define anything for Linux or VM in HCD OS config. As long as the channels, > CU & devices are attached to the lpar Linux & VM can use them. Define "attached" in this context. 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
On Monday, 01/14/2008 at 04:46 EST, Mark Post <[EMAIL PROTECTED]> wrote: > >>> On Mon, Jan 14, 2008 at 4:11 PM, in message > <[EMAIL PROTECTED]>, Robert J > Brenneman <[EMAIL PROTECTED]> wrote: > > Both Linux and VM can talk directly to the channels so you don't have to > > define anything for Linux or VM in HCD OS config. As long as the channels, > > CU & devices are attached to the lpar Linux & VM can use them. > > 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. 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. Alan Altmark z/VM Development IBM Endicott -- 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
>>> On Mon, Jan 14, 2008 at 4:11 PM, in message <[EMAIL PROTECTED]>, Robert J Brenneman <[EMAIL PROTECTED]> wrote: > Both Linux and VM can talk directly to the channels so you don't have to > define anything for Linux or VM in HCD OS config. As long as the channels, > CU & devices are attached to the lpar Linux & VM can use them. Define "attached" in this context. 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
Both Linux and VM can talk directly to the channels so you don't have to define anything for Linux or VM in HCD OS config. As long as the channels, CU & devices are attached to the lpar Linux & VM can use them. -- Jay Brenneman -- 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
IODF-HCD Defining FCP on a z9 for z/Linux
I am trying to define FCP Channel, Controller and Unit so z/Linux native can use it. The LPAR that we are using for z/Linux is defined as MVS. HCD does not allow me to attach FCP units to an MVS LPAR. If I define a new LPAR as VM and it allows me to attach it. In order for z/Linux native to use FCP does the LPAR OS TYPE have to be defined as VM so I can attach the FCP Units to it or does z/Linux talk directly to the FCP channels? Sam Bass 254-771-7212 Sr z/OS Systems Specialist -- 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
