Hello Kurt,
thanks for your quick reply!
I found a workaround for that case, the z/OMSF-Deployment is a bit different to the old Custompac-Dialog, it gives us less customizing options before unpacking the archieves. But we are looking forward to some enhancements in future, to make it a litte more customizable :).
Thanks!
------------------------------
Ramon Esteves Salgueiro
------------------------------
Original Message:
Sent: Tue September 03, 2024 09:57 AM
From: Kurt Quackenbush
Subject: Deployment of z/OS 3.1 creating new MCat
Ramon, enhancing z/OSMF to connect existing user catalogs to a new master catalog is in our backlog. There is no great solution currently, sorry. My advise is NOT to modify the generated deployment and workflow jobs. Instead, catalog the data sets in the new master catalog. Then, after the supplied Workflows have been performed and the Deployment is complete, manually rename and re-catalog the subject data sets into your desired user catalogs. It is important to wait until the Deployment is complete before renaming/re-cataloging.
------------------------------
Kurt Quackenbush
IBM, z/OS SMP/E and z/OSMF Software Management
kurtq@us.ibm.com
Original Message:
Sent: Mon September 02, 2024 04:03 AM
From: Ramon Esteves Salgueiro
Subject: Deployment of z/OS 3.1 creating new MCat
Hello Guys,
z/OSMF gives us two options to deploy z/OS 3.1, creating a new MCat or using an existing one. We want to create a new MCat, so i choose option 1, in our installation we have some "specials" like SMP-Datasets are SMS-managed and we do not copy all of them to the system volumes, the same we have for OMVS-Datasets. The problem we have is, that z/OSMF doesnt allow any exisiting catalogs in Option 1, furthermore the SMP- and OMVS-HLQ are required to be cataloged, so i cannot use "do not catalog" to catalog them afterwards, as a possible workaround. In fact right now i dont see a possibility to refelect our enviroments specifications to the deployment workflow.
I assume we could solve that by manually editing the created workflow-jobs and submitting them outside z/OSMF, that is not really a good option so i am searching for a workaround that allows us to handle our specific situation inside z/OSMF.
It could be great if someone of the experts maybe have a suggestions how we could solve that inside of z/OSMF :)
Many Thanks!
------------------------------
Ramon Esteves Salgueiro
------------------------------