My understanding is that this issue goes away (or is mitigated) with z/OS
V1.12. Indirect cataloging is available for VSAM in 1.12 but not before.
Our process is to have the zFS on a separate volume and use the &SYSR1 to
handle the various datasets at IPL.
For example.
SYS1.OMVS.ROOT.Z19RS1 is a dataset
SYS1.OMVS.ROOT.Z19RS2 is a another one.
Our sysres is Z19RS1
In our BPXPARMs we have coded:
ROOT FILESYSTEM('SYS1.OMVS.ROOT.&SYSR1')
TYPE(HFS) /* Filesystem type */
MODE(RDWR) /* Mounted for read ONLY */
/* */
So AT IPL Time, it resolves to the correct ROOT dataset.
HTH
Lizette
>
>Our upcoming migration from HFS to zFS for the root file systems is causing a
>new problem for us.
>
>
>
>The previous maintenance method was to keep the HFS root file system on
>the sysres with all other non-VSAM SMPE-target files. All datasets were
>implicitly cataloged at IPL time. By replacing the SYSRES volume a total
>replacement or back-off of maintenance was just an IPL away. We currently
>are running from a single mod 27 sysres. The rest of the HFS/ZFS file systems
>will be mounted from other non-SMPE impacted volumes.
>
>
>
>The zFS file systems on the other hand is subject to the special volume
>ownership and naming requirements of VSAM. We can no-longer use a simple
>full volume copies to transfer the test SYSRES to production. Further it looks
>like a second dump will need to be done of the test zFS root files and then a
>restore with the RENAMEU option run made under the production master
>catalog. We may even have to put the zFS files on separate sysres volumes
>which are "owned" by the production system catalog structure.
>
>
>
>Does this make sense or what are some other ideas to maintain the new zFS
>root files?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
