On Fri, Mar 10, 2017 at 2:16 PM, David Larry <[email protected]> wrote:
> Go easy on me I am new at this > > I have non SYS1 vsam datasets in my old master catalog > Upgrading to new os Z/OS 2.2 from 1.13 > From serverpack > > How do I recatalog these old datasets in the new MCAT > IMO, UNIX filesystem data sets (OMVS datasets) should NEVER be in the master catalog. What I'd do, and did myself in this case long ago, is to create a new user catalog to contain the OMVS filesystem data sets. On some Sunday, or another "maintenance only" day: (1) unmount all the OMVS data sets that you can; (2) do a REPRO MERGECAT LVL(omvshlq) to move the OMVS data sets into the user catalog; (3) connect the HLQ to the new catalog; (4) mount the OMVS data sets again (T OMVS=?? on the z/OS master catalog will do this). Another thing that I do is use a different HLQ for "site" OMVS files vs. IBM supplied, something like: ZFSPV.&SYSNAME..HOME.&SYSUID..ZFS, where &SYSNAME and &SYSUID are what you'd expect. I use UNIX automount to manage the creation and mounting of OMVS users' "home" directories. Everybody gets their own filesystem, rather than having everybody in the same filesystem. This stops one user from "using up" all the space for their files, leaving nothing for other users. Which then leads to "Mom! Billy won't share!" type arguments. > > if it helps these are ZFS & HFS files mounted OMVS > > David (with thanks to my friend Av who introduced me to IBM-MAIN) > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- "Irrigation of the land with seawater desalinated by fusion power is ancient. It's called 'rain'." -- Michael McClary, in alt.fusion Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
