Thanks Allen I sent in a request for the software. I don't have the hardware, but I can install the software on an image and read the manuals.
In the "Getting Started with zSeries Fibre Channel Protocol" Redpaper, which was for z/800, z/900 processors, it answered my question. There are 240 subchannels defined on a FCP port. By giving one subchannel per Linux image, effectively limiting the number of Linux images that have access to FCP devices, all Linux images can have access to the devices on the FC SAN. I think 240 zLinux images will be sufficient, for now. I also see how they are mapped, from zLinux, to VM, to IOCP, to WWPN and so on, and how the FC SAN switch works (reminds me of an Escon Director). Tom Duerbusch THD Consulting (all you really ever needed was a 370 mode processor and bus and tag devices) >>> [EMAIL PROTECTED] 10/2/2006 6:09 PM >>> On Monday, 10/02/2006 at 04:41 EST, Tom Duerbusch <[EMAIL PROTECTED]> wrote: > Not on a z9....z/890... Industry-standard N_Port ID Virtualization (NPIV) on the z9 is needed if you want to apply zoning and LUN masking (FC access controls) to virtual machines and/or LPARs just as they are for discrete systems. With NPIV, each FCP subchannel, rather than chpid, is assigned a unique WWPN. Matching support in the local FC switch is required. On a z890 and z990 you can use the Linux-based FCP LUN Access Control utility to control guest/LPAR access to WWPNs and LUNs. Even though the other systems and switches see just one WWPN per FC chpid (and no special switch support is needed), the utility instructs the FCP adapter to act as a gatekeeper. Read more about it on ResourceLink at https://www-1.ibm.com/servers/resourcelink/hom03010.nsf/pages/fcpaccumain?opendocument. (You get to this by navigating first to Tools and then selecting "Configuration Utility for FCP LUN Access Control" in the first column.) Alan Altmark z/VM Development IBM Endicott
