I’m in a bit of new territory in terms os working with the root file system for 
USS.

I have a small sysplex for development and recently I was looking to install 
some additional software that I’d like to place under a mount point off `/`.  I 
could find something existing but it is more intuitive to add a new mount point 
in root and mount a ZFS over it.  

The systems are in a SYSPLEX but all USS filesystems are independent so there 
is no sharing across the systems at this point.  

The plex is able to IPL one of three versions of z/OS (2.3, 2.4 or 2.5) at a 
time.

Each version has its own root FS.  My diabolical plan was to run 2.5 and then 
mount the 2.3 and 2.4 file systems using RDWR mode, add the entry, unmount, do 
the next one and then re-ipl. on 2.4 install the new software anchored off the 
new mount point.

When trying to mount one of the older ROOT FS using this MOUNT command

MOUNT FILESYSTEM('OMVS.ROOT.MT24R1') -
      MOUNTPOINT('/var/omvsroot') -   
      TYPE(ZFS) -                     
      MODE(RDWR)                      

I am getting these messages when attempting to mount as RDWR … READ mounts fine.

IOS000I 0AA4,EF,WRI,E7,0200,,56E80000,MT24R1,CATALOG ,  
80020000A4000C0000000000000000A0A1A2A3A400030000000000E20000000C    
IOS000I 0AA4,EF,WRI,E7,0200,,56E80000,MT24R1,CATALOG ,  
80020000A4FFFF0000000000000000A0A1A2A3A400030000000000E20056E800    

IEC331I 050-018(00201110,MT24R1),MVSZFS,MVSZFS,VMMC,IGG0CLE2         

IEF196I IEC331I 050-018(00201110,MT24R1),MVSZFS,MVSZFS,VMMC,IGG0CLE2 
IEF196I IEC161I 037(050,018,IGG0CLE2)-005,MVSZFS,MVSZFS,SYS00019,,,  
IEF196I IEC161I OMVS.ROOT.MT24R1,OMVS.ROOT.MT24R1.DATA,              
IEF196I IEC161I ICF.MIST.USER.CATALOG                                

IEC161I 037(050,018,IGG0CLE2)-005,MVSZFS,MVSZFS,SYS00019,,, 117      
IEC161I OMVS.ROOT.MT24R1,OMVS.ROOT.MT24R1.DATA,                      
IEC161I ICF.MIST.USER.CATALOG                                        

IOEZ00964E DFSMS CATALOG returned error code 50 reason code 12 while trying to 
open aggregate OMVS.ROOT.MT24R1.                           

As with many things VSAM there is a lot of data and so little information.  

DIAGNOSE on the VVDS runs clean and indicates no errors.

I’m continuing to diagnose the issue but I presume this should be fairly 
straight forward so any guidance is welcome.

Matt Hogstrom

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to