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]> 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
