> It looks like most of the datasets the system is complaining about are > in their own user catalogs. I should be able to connect the user > catalog to the master catalog on the zOS 1.13 side and be ok. > > Tho there is one that is cataloged in the z2.1's master catalog. I may > have to just ignore the error message for that. I think that solves > that problem.
I know I am a bit late on this, but do you really want to *share* the OMVS environment in an ADCD sysplex of two differing z/OS levels? Not sharing OMVS would take care of all error messages, and you already have the infrastructure duplicated for each release. Of course, if you plan to later migrate the 1.13 system in that plex to a 2.1 system using the same sysres's, forget I said anything. Having recently renamed a system that is using the ADCD sysplex setup (making it shared HFS/zFS depite being a monoplex), we discovered the hard way how asinine the delivered symbolic links are, pointing back and forth in several symbolic substitutions. OMVS did come up (and TCPIP came up!), but since /tmp was not mounted correctly due to the &SYSNAME having gotten changed, we could not even set new paths in OMVS, because that requires tmp to be available. I would not be surprised if you run into problems like this down the road with your semi-shared setup. Admittedly, yours seems like a later version of my 1.13 ADCD version (in mine the root was still an HFS, which we were very grateful for, because we could just catalog it on another system and then set the links). Essentially, we ended up replacing the symbolic links in the root with hardcoded links and all was well again. Of course, this effectively stopped "OMVS sharing". But now I have an idea how to remove 'sysplex sharing' of OMVS in my monoplex and remove the BPX CDSs, since they are not needed. That will also take care of all the complaining OMVS health checks that still don't take into account that ieasysxx says PLEXCFG=MONOPLEX, so nobody ever will automove anything away from my monoplex. (After 2 years, I am now almost where I want my system to be!) Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
