Doesn’t the existence of the IEE025I message indicate that z/OS was trying to vary them online at IPL but failed?
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jerry Whitteridge Sent: Friday, December 6, 2024 11:53 AM To: [email protected] Subject: Re: EXTERNAL Email: Re: z/OS Devices under z/VM If you can easily vary them online to z/OS without doing anything in z/VM check your IODF for the Online at IPL setting for the device Jerry Whitteridge Sr Manager Managed Services [email protected] 480 578 7889 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Matt Hogstrom Sent: Friday, December 6, 2024 9:50 AM To: [email protected] Subject: EXTERNAL Email: Re: z/OS Devices under z/VM They are defined in z/OS but show offline. I can attach them and everything works fine. I’ll do some experimentation today to narrow it down. Thanks Peter. -- Matt Hogstrom “To achieve great things two things are needed: a plan, and not quite enough time.” - Leonard Bernstein > On Dec 6, 2024, at 11:31, Farley, Peter > <[email protected]> wrote: > > That IEE025I error message sure sounds like the z/OS instances do not have > devices 9005 to 900F defined in their IODF’s or maybe have no CHPID’s for > that range, or perhaps some newer-than-my-experience virtual hardware > definition(s) in the VM directory. > > The manual description for solving the IEE025I message includes in the > description the statement “there are no paths of the indicated type, logical > or physical, available for this device or console, or the device is not in a > ready state.”. The advice “Check all logical paths to the device” also > appears on that page. > > Peter > > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > Matt Hogstrom > Sent: Friday, December 6, 2024 11:11 AM > To: [email protected] > Subject: Re: z/OS Devices under z/VM > > I have a dummy entry in the directory to define the MDISKS > > Here is a snippet > > USER MVSDUMMY NOLOG 512M 512M G > MDISK 9000 3390 0000 END UV9000 MWV ALL ALL ALL > MDISK 9001 3390 0000 END UV9001 MWV ALL ALL ALL > MDISK 9002 3390 0000 END UV9002 MWV ALL ALL ALL > MDISK 9003 3390 0000 END UV9003 MWV ALL ALL ALL > MDISK 9004 3390 0000 END UV9004 MWV ALL ALL ALL > MDISK 9005 3390 0000 END UV9005 MWV ALL ALL ALL > MDISK 9006 3390 0000 END UV9006 MWV ALL ALL ALL > MDISK 9007 3390 0000 END UV9007 MWV ALL ALL ALL > > . . . > > The UV9000 - UV9004 were predefined and accessible across all the guests and > work fine. > > I added UV9005-UV900F (only 5-7 are shown for brevity) > > The guests look like this > > USER R100 R100 8000M 12000M (there are three guests) > > LINK MVSDUMMY 9000 9000 MW > LINK MVSDUMMY 9001 9001 MW > LINK MVSDUMMY 9002 9002 MW > LINK MVSDUMMY 9003 9003 MW > LINK MVSDUMMY 9004 9004 MW > LINK MVSDUMMY 9005 9005 MW > LINK MVSDUMMY 9006 9006 MW > LINK MVSDUMMY 9007 9007 MW > > I attached the new devices to the first guest, ran DSF to init the volumes > and brought them online which was all good. > > When the system was re-ipl’d the new devices didn’t con online and give the > following message: > > RESPONSE=R12F IEE025I UNIT 9005 HAS NO LOGICAL PATHS > > When “ATTached” they are accessible. > > The 9000 - 9004 come online with no intervention. > > I’ll keep digging but this is where I’m at. > > All systems have write access to the volumes. > > -- > > Matt Hogstrom > > “To achieve great things two things are needed: a plan, and not quite enough > time.” > > - Leonard Bernstein > >> On Dec 6, 2024, at 10:52, Farley, Peter >> <[email protected]<mailto:[email protected]>> >> wrote: >> >> Look at the current directory entries for any one of the VM’s and see how >> the z/OS disks are defined, then replicate that format for each of the >> “shared” disks in all of the VM directories but with RR as the read/write >> attribute for each shared disk. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
