On Thu, 2 Jul 2020 18:32:42 -0400 Mark Post <[email protected]> wrote: > On 7/2/20 5:32 PM, Martha McConaghy wrote: > -snip- > > I don't know what to do with this situation, though, to get full > > use of the 2nd fabric. First there is the IPL issue...how can I > > have an alternate IPL address if 2000 doesn't work? Then, there is > > the issue of Linux once it boots...not sure how to get multipath > > drivers introduced after the boot process is already done. The LUN > > contains the operating system as well as data. > > The IPL issue is the bigger problem. Since IPL is a CP command, if it > fails, you're back in CP mode. So, no scripting of multiple attempts. > You'll need to issue a different LOADDEV command to specify the other > WWID and LUN to try the second path. Perhaps even IPL from the other > FCP adapter. I don't believe that can be automated without having > something like a SECUSER watching and trying different things if it > fails.
I don't know the details that you want to accomplish. However, it would also be possible to setup an EDEV with "set edev" in which case z/VM would do the FCP multipathing for you. You would be able to just do an IPL like with normal DASD. I personally would add this to the autolog virtual machine with some script instead of SYSTEM CONFIG, but that is up to your choice. As an alternative, if you really have to boot from some FCP adapter directly, you might want to have a look at the SCSIDISC utility. I think I remember that they implemented a method to talk directly to the SCSI bus with REXX there... Berthold ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
