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
