On Wed, 15 Jan 2014 04:18:42 -0600, Donald Likens <[email protected]>
wrote:
>Note: The zFS would have been created with a different master catalog. I was
>assuming that SYS1 statement in the entry in the manual meant that it was
>cataloged in the master catalog. Has anyone put the OMVS root ion the SYSRES?
>IF so, how did you do it?
>
Since I create a sysres (set) shared between several sysplexes and monoplex
LPARs for one company I support, I've been using DEFINE RECATALOG
in each sysplex (other than the one that I clone from) to accomplish
this even since we moved from HFS to zFS for "sysres" file systems
(back at z/OS 2.6). It accomplishes the same thing as
indirect catalogging for me, so I haven't changed anything since
moving to z/OS 1.13 (skipped 1.12).
So I run a IDCAMS command similar to this for each sysres (set) file system
in each sysplex / monoplex:
DEFINE CLUSTER -
(NAME(SYS1.OMVS.resvol.ROOT.ZFS ) -
VOLUMES(resvol) -
RECATALOG -
LINEAR)
The only "negative" (if you can call it that, I don't consider it so) is a
warning
if you run a diagnose about the mismatch. Actually, as I think about this
when writing, this warning may not show up anymore with the indirect
cataloging support for zFS.
BTW, my IODF data sets that we rotate between are handled the same way but
it spans several more companies and sysplexes than the sysres zFS configuration
I referred to above. I don't have to play with exporting / importing IODFs
anywhere in the complex (z/OS 2.1 has some nice enhancements for complex
wide activate now too - can't wait to get there).
Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
