Kurt, Our Shop standard dictates that a new master catalog is created with every z/OS upgrade. An additional standard clones new master catalogs from the new z/OS master catalog so that every lpar has its own new master catalog as the implementation rolls across the board. So, yes, I really want to create that new master catalog. What I want, in this case, doesn't matter.
I used IEFBR14 to create the names that the configuration was expecting and still no joy. I am assuming z/OSMF's instance was aware that the source datasets were ZFS files and expected the targets to be the same. Is this assumption correct? If so, I'll try to get the SMS sheriff to modify the ACS routines this one time to allow for their creation as ZOS25.OMVS.*. That should enable the workflow instance creation to proceed, right? Bob -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Kurt J. Quackenbush Sent: Wednesday, May 4, 2022 10:07 AM To: [email protected] Subject: Re: z/OSMF Portable Software Instance - Deployment Question Bob, are you sure you really want to create a new master catalog? Or, do you really want to use your existing master catalog and existing user catalogs, or perhaps create some new user catalogs connected to your existing master catalog? The point is, if you use your existing master catalog then you don't need to provide, and z/OSMF won't create and use, temporary catalog aliases. Sadly, as you are observing, you modified the data set names in the generated jobs so the actual data sets now don't match the configuration expected by z/OSMF. Hence the errors creating the workflow instances. Other than rename the data sets as expected by z/OSMF there is no way to fix this error. If you really want to proceed on your current path, then you need to rename or recreate the data sets as z/OSMF expects. Perhaps you can update your ACS routines, or define a STORCLAS, to create zFS data sets that have an HLQ other than OMVS. If you can't do either, then I suggest you consider changing your configuration to use your existing master catalog so you can use your existing OMVS HLQ. I suspect this is what you really wanted to do anyway. Kurt Quackenbush IBM | z/OS SMP/E and z/OSMF Software Management | [email protected] Chuck Norris never uses CHECK when he applies PTFs. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Richards, Robert B. (CTR) Sent: Tuesday, May 3, 2022 11:30 AM To: [email protected] Subject: [EXTERNAL] z/OSMF Portable Software Instance - Deployment Question I have a z/OSMF Software Management question that I hope someone on IBM-Main can provide me with the answer. I was on the Configure CATALOGs page of a z/OS 2.5 deployment and successfully provided the Temporary Catalog Alias entries for three HLQs. The issue was the fourth HLQ - OMVS. Everything I tried failed. The alias of OMVS is already defined in our driving system's Master Catalog and RELATEd to a shared user catalog. Because our ACS routines only allow a HLQ of OMVS to allocate to the "HFS/ZFS" pool, I knew any other HLQ would not work. For the record, all OMVS.* data sets that I was trying to allocate would be unique in our driving system's master catalog. I was unable to get off of this webpage without specifying a Temporary Catalog Alias for it, so I specified one and moved on to let the six jobs be generated. Subsequently, I edited the job that creates and populates the OMVS datasets to REMOVE that Temporary Catalog Alias wherever it was referenced and submitted the job to a successful conclusion. Next, I moved onto "Perform Workflows" and was instantly stopped with 21 errors looking for the OMVS datasets containing the Temporary Catalog Alias.OMVS.* I do not know how to get out if this situation and there does not appear to be anyway to bypass/rectify it. All three workflows produce the same set of errors. Any advice is greatly appreciated. Bob ---------------------------------------------------------------------- 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
