On thinking about this some more, I'm not sure I can do this. My OMVS HLQ is in the NOT-shared Master catalogs for each LPAR. I know I can have SYS1 and PAGE successfully defined in multiple catalogs. But, not anything else. The catalog/VVDS relationship will be broke in the other Lpars.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Gibney, David Allen,Jr > Sent: Thursday, January 14, 2016 11:56 AM > To: [email protected] > Subject: Re: z/OS 2.1 and FONTS; Moving from z/OS 1.13 > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]] > > On Behalf Of Elardus Engelbrecht > > Sent: Wednesday, January 13, 2016 9:40 PM > > To: [email protected] > > Subject: Re: z/OS 2.1 and FONTS; Moving from z/OS 1.13 > > > > Gibney, David Allen,Jr wrote: > > > > > I have a small shop, 4 monoplex LPARs, no GRS. Very careful > > > sharing of a > > limited set of disks including the system resident (IPL) volume, a > > Mod-27. Up until now, I have made separate (R/O) copies of the ROOT > > and other system > > ZFS/HFS(s) for each LPARs. > > > This new Unix filesystem with FONTS is not small and I am > > > wondering if it > > is safe to have only one (R/O) copy of it (probably on the IPL > > volume), shared by two or more LPARs? > > > > That's possible (sharing of IPL volser) as long all those LPARS are on > > the same z/OS level. > > I have been sharing the traditional RESVOL since at least z/OS 1.7 > > > > > > My SMP/E points to an entirely separate target Mod 27 and set of > > > OMVS > > files. These are cloned after maintenance to alternating IPL and > > maintenance level OMVS files. > > > > What is your catalog setup? Do you have separate master catalogs and > > their own set of user catalogs? Or are you sharing your catalogs? > > > > Mostly LPAR specific catalog systems. My two sandboxes share several > USERCATS. > OMVS HLQ is in the unshared Master(s) Which could complicate things :) > > > > I believe it is safe to share a Read Only OMVS dataset, unless you > > have something to prevent sharing of such OMVS datasets, for example > > having a folder which is written to. > > I am figuring on mounting them R/O. > > > > > Of course, moving from z/OS v1.13 to 2.1 requires two different IPL > > volsers during rolling upgrades. > > All independent monoplexes, but yes new IPL volumes for the new 2.1 system. > No real co-existence, just need to insure viable fallback. Never been able to > justify the CPU resources for even basic Sysplex. And never really had the > need. We have multiple Lpars to isolate production from development from > sandbox work. > > Part of my concern is that I only have 16 M27 defined. (user to make do with > 12 M9 before our last DASD upgrade). I'm running short until I complete the > migrations > > > > > Groete / Greetings > > Elardus Engelbrecht > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
