Thanks for the input. Actually now I was totally able to customize all my dataset names, which is really great. It is time consuming because I basically had to change everything.. My dlibs are on a dedicated volume and my RES datasets on another volume.
Then they changed all the ZFS dataset names, so they not end with ZFS now, so that required updates, because this then effects my BPXPRMxx member. I might change things to the new IBM names in 2.6, but small changes now. So my OMVS files are on a secondary RES, but cataloged as SYSAOP.ZA2511.xxxxxxxx datasets. SMPE, I use SMS, so I had to use a ton of filtering to place those. Lastly the CPAC datasets, are my SAVE-OFF's. I really never use them in production because I do system upgrades, but I do reference them for changes that I might have to propagate to my Parmlib/proclibs. This is why I use CPAC.ZOS25.xxxxxx and SMPE.MVS.ZOS25.xxxxxxxx this allows me to not have to deal with alias's. All my SYS1.xxxxx are SYS1SSA, which SMS has special rules for that allow me to direct to volumes of my doing. So far I like that part in z/OSMF. Now I hit a few things, because its always checking names in the background.. So when it says its going to build jobs, it lies, its actually verifying names first. So because I already installed z/OS 2.5 with a serverpac, I would like to bypass a few things and it will not let me. So back to adding a SSA for my duplicates to get thru the screens. I understand IBM is trying to make this idiot/Beginner proof, but I wish there was and advanced I know what I am doing option. Heck even with my serverpac this time, I modified every job, because it didn’t allow me to build what I wanted as a configuration. At least z/OSMF seems to allow name changes, but before it builds jobs it goes and validates all the names. I wish that was a batch job, but such as life.. So the saga continues.. Ms Terri E Shaffer Senior Systems Engineer, z/OS Support: ACIWorldwide – Telecommuter H(412-766-2697) C(412-519-2592) terri.shaf...@aciworldwide.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Keith Gooding Sent: Tuesday, October 26, 2021 3:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Serverpac installs January 2022 and beyond - Issues Updated External Email Hi Terri. I had a more positive experience with z/osmf installation of a z/os serverpac after some initial confusion. A long time ago I had created a ‘software instance’ from a pair of z/os 2.4 target/dlib zones. I used this as a model for my 2.5 installation and was very surprised when z/osmf proceeded to tailor the dataset names like the 2.4 instance - surprised because I expected that the model had to be an instance created by a z/osmf installation. I now see that it probably looks for matching DDDEFs and adjusts the new dataset names accordingly. I had to adjust the names for new datasets and operational datasets. Here I found that z/osmf appears to look for common HLQs in a dataset filter list and gives the opportunity to change that common HLQ to something else. I did this for instance for some CPAC datasets where we want the HLQ to be SYS1.CPAC instead of CPAC - I filtered on HLQs to get a list of all CPAC datasets and excluded the ones I did not want to change. If you do not have a model instance then of course to change all HLQs to SYS1 you would have to change each HLQ (CEe, ISF etc) separately. I still have some gripes but these occurred also with the old dialogue: - only single level aliases are supported. We want to use OMVS.ZOS250 as a 2 level alias pointing to a new catalog on sysres but this has to be done post-install. - SMPE.ZOS250.* non-VSAM datasets on the sysres are indirectly cataloged because indirect cataloging by the installation dialogue works at the volume level. - I always do what used to be called an ‘upgrade install’. With z/osmf I instead answered ‘no’ to ‘do you want to create operational datasets’. In both cases we still get some operational datasets such as CPAC.PARMLIB. Most of these are not required but to avoid clashing with existing datasets of the same name I rename them as SYS!.CPAC.* and indirectly catalog them on sysres. Keith GOODING > On 26 Oct 2021, at 18:05, Shaffer, Terri > <0000017d5f778222-dmarc-requ...@listserv.ua.edu> wrote: > > Okay I am going to retract the dataset names issue. Either my z/OSMF > decided to play nice now, or I did something wrong. > > I can modify all the names to my preferred names and HLQ.. > > So let me continue to see what happens.. It sure would have been nice to just > retrieve my CPAC.SAVE.CONFIG file. > > But okay.. > > Ms Terri E Shaffer > Senior Systems Engineer, > z/OS Support: > ACIWorldwide – Telecommuter > H(412-766-2697) C(412-519-2592) > terri.shaf...@aciworldwide.com > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ________________________________ [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] <http://www.aciworldwide.com> This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
