Need to cater for changing DLIBs when moving from small to larger volumes (catalog entry mismatch)

Thank you for the additional information. I read the support case, TS010244257, and now I think I understand the scenario. You have existing Dlibs cataloged in the existing driving system catalog with indirect volume references. For example the catalog entries contain volume symbols &DLIB1, &DLIB2, &DLIB3. In the deployment configuration you choose to catalog the target system data sets in the existing driving system catalog, assign the subject data sets to a single volume, indirectly catalog data sets on this volume, and assign that volume to symbol &DLIB. When you try to generate the deployment jobs, z/OSMF discovers a catalog entry collision and displays error message IZUD9704E (Generation of the deployment jobs failed. Indirect cataloging was requested for target data set data-set-name using symbol target-symbol, but a data set by that name is already indirectly cataloged using symbol current-symbol.).
https://www.ibm.com/docs/en/zos/2.5.0?topic=izud9900-izud9704e

The point of this message is z/OSMF does not support changing the volume symbol in a data set's catalog entry for an existing indirectly cataloged data set. So I think your request is for z/OSMF to provide an option to allow existing catalog entries to be updated with a new volume symbol instead of detecting an error and preventing the deployment jobs from being generated. Is my summary correct?

Hello,

Our response is in bold below :

What software are you deploying (z/OS?) z/OS v2.5

and how are you configuring the deployment operation? That is, on the Deployment Objectives page do you indicate Create a new software instance or Replace an existing software instance? Create a new software instance.

If creating a new software instance, are you creating a new global zone or connecting the target/dlib zones to an existing global zone? Creating a new global zone.

In the Deployment Configuration did you select an existing software instance to use as a model? No, its our first deployment with z/OSMF, so no model used.

In the Deployment Configuration do you modify the data set names from the Model data set names? Yes, some of the dataset names was modified

If you modify the data set names do you specify a unique name for the subject DLIB data sets? Yes

Do you indicate the subject DLIB data sets will be cataloged? Yes

Do you specify a target volume or storage class for the subject DLIB data sets? Yes, we specified target volumes

If you specify a volume, is this the MOD27 volume? Yes

Are there existing data sets with the same name in the driving system's catalog? There are existing datasets with the same names on 3x Mod-9 volumes of the previous version (z/OSv2.4)

On the volume? (FW4DL1, FW4DL2, FW4DL3) now intending to install on 1x Mod-27 volume FW5DLB

The issue we had was the datasets in the catalog on 3x MOD9 are mismatched with intended installation destination 1xMOD27. With Custompac Dialog method a Warning message was issued and but didn't prevent the installation from proceeding. Screenshots of messages can be found on the IBM case provided Case number TS010244257

If you require any additional information, please reach out.

Many thanks,

Vikesh

Hello, thank you for your request, however, can you please provide more information? In the scenario you describe, what software are you deploying (z/OS?) and how are you configuring the deployment operation? That is, on the Deployment Objectives page do you indicate Create a new software instance or Replace an existing software instance? If creating a new software instance, are you creating a new global zone or connecting the target/dlib zones to an existing global zone? In the Deployment Configuration did you select an existing software instance to use as a model? In the Deployment Configuration do you modify the data set names from the Model data set names? If you modify the data set names do you specify a unique name for the subject DLIB data sets? Do you indicate the subject DLIB data sets will be cataloged? Do you specify a target volume or storage class for the subject DLIB data sets? If you specify a volume, is this the MOD27 volume? Are there existing data sets with the same name in the driving system's catalog? On the volume?

Thank you for any clarity you can provide.