Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Kurt, thank you so much for your assistance. I would not have gotten through this without your help. 

This was my first time through zosmf install and what I did not like (unless I missed it) was being able to assign certain datasets to not use the temporary HLQ so they would be allocated with their own unique names in the correct existing catalog. Specifically, the vsam CSI's and the ZFS files. The naming standards at this place for zfs files are SYS1.ZOS.* so I believe all SYS1 were assigned to the temporary mcat and I could not change that. If I remember correctly?   

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Matt, glad I could help.  Connecting existing user catalogs to a new master catalog, and therefore allowing use of existing HLQs for those existing user catalogs, is not currently supported, so you didn't miss it.  Your example naming standard for zfs files of SYS1.ZOS.* looks like a multi-level catalog alias, which is in addition to connecting existing user catalogs, but also not currently supported.  Your best option for now may be to let z/OSMF catalog those data sets in the new master catalog, and then after the configuration steps in the workflows are complete and you've removed the temporary catalog aliases, then manually rename and recatalog those data sets into your desired user catalogs.

We do understand the requirements, and both of those are in our backlog.

Kurt, thank you so much for your assistance. I would not have gotten through this without your help. 

This was my first time through zosmf install and what I did not like (unless I missed it) was being able to assign certain datasets to not use the temporary HLQ so they would be allocated with their own unique names in the correct existing catalog. Specifically, the vsam CSI's and the ZFS files. The naming standards at this place for zfs files are SYS1.ZOS.* so I believe all SYS1 were assigned to the temporary mcat and I could not change that. If I remember correctly?   

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Hi Kurt,

I'm installing ZOS 3.1 FROM ZOMSF and I have done all step until generating JCL to deploy.

I have found 7 generated JOB. 

I have choosed REFZ31 as SSA.

The problem is that the last 2 jobs which are IZUD06RN and IZUD07UC, try to alter the datasets and rename them without REFZ31.

But, I want to maintain datasets with HLQ REFZ31 as they are SMP/E datasets and maintain the master catalog created during the deploy as a user catalog for all REFZ31 datasets.

When I need to deploy ZOS31 on an LPAR I copy all dataset to new volumes with ADRDSSU + Rename (Remove REFZ31) and I create a new master catalogue.

Could you help me to deal with that issue.

Best regards,

Matt, glad I could help.  Connecting existing user catalogs to a new master catalog, and therefore allowing use of existing HLQs for those existing user catalogs, is not currently supported, so you didn't miss it.  Your example naming standard for zfs files of SYS1.ZOS.* looks like a multi-level catalog alias, which is in addition to connecting existing user catalogs, but also not currently supported.  Your best option for now may be to let z/OSMF catalog those data sets in the new master catalog, and then after the configuration steps in the workflows are complete and you've removed the temporary catalog aliases, then manually rename and recatalog those data sets into your desired user catalogs.

We do understand the requirements, and both of those are in our backlog.

Kurt, thank you so much for your assistance. I would not have gotten through this without your help. 

This was my first time through zosmf install and what I did not like (unless I missed it) was being able to assign certain datasets to not use the temporary HLQ so they would be allocated with their own unique names in the correct existing catalog. Specifically, the vsam CSI's and the ZFS files. The naming standards at this place for zfs files are SYS1.ZOS.* so I believe all SYS1 were assigned to the temporary mcat and I could not change that. If I remember correctly?   

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Abdennacer, when you choose the option to create a new master catalog, as you observe z/OSMF unconditionally renames the data sets to their true and desired names and removes the temporary catalog alias (SSA) prefix.  z/OSMF does create data set aliases (and PATHs for VSAM data sets) with the temporary catalog alias prefix for some of the data sets, but all are renamed to their true names as defined in the deployment configuration.

If you want all data sets to keep your chosen data set name prefix, please consider choosing the option to use the driving system's catalogs instead of creating a new master catalog.  In this case in the configuration you can define all data sets to contain your prefix, REFZ31, and z/OSMF will not rename them.  You can also tell z/OSMF to create a new user catalog for all of the data sets with the REFZ31 prefix if you like.  Later during your custom deploy/clone process you can remove the prefix and create your new master catalog.

If you want to try this option, go back to the Objectives step in the Deployment checklist, and change your catalog selection to "Existing master catalog".  Then update the configuration to add your prefix to all data set names, and regenerate the JCL.

Let me know if you have further questions or troubles.

Hi Kurt,

I'm installing ZOS 3.1 FROM ZOMSF and I have done all step until generating JCL to deploy.

I have found 7 generated JOB. 

I have choosed REFZ31 as SSA.

The problem is that the last 2 jobs which are IZUD06RN and IZUD07UC, try to alter the datasets and rename them without REFZ31.

But, I want to maintain datasets with HLQ REFZ31 as they are SMP/E datasets and maintain the master catalog created during the deploy as a user catalog for all REFZ31 datasets.

When I need to deploy ZOS31 on an LPAR I copy all dataset to new volumes with ADRDSSU + Rename (Remove REFZ31) and I create a new master catalogue.

Could you help me to deal with that issue.

Best regards,

Matt, glad I could help.  Connecting existing user catalogs to a new master catalog, and therefore allowing use of existing HLQs for those existing user catalogs, is not currently supported, so you didn't miss it.  Your example naming standard for zfs files of SYS1.ZOS.* looks like a multi-level catalog alias, which is in addition to connecting existing user catalogs, but also not currently supported.  Your best option for now may be to let z/OSMF catalog those data sets in the new master catalog, and then after the configuration steps in the workflows are complete and you've removed the temporary catalog aliases, then manually rename and recatalog those data sets into your desired user catalogs.

We do understand the requirements, and both of those are in our backlog.

Kurt, thank you so much for your assistance. I would not have gotten through this without your help. 

This was my first time through zosmf install and what I did not like (unless I missed it) was being able to assign certain datasets to not use the temporary HLQ so they would be allocated with their own unique names in the correct existing catalog. Specifically, the vsam CSI's and the ZFS files. The naming standards at this place for zfs files are SYS1.ZOS.* so I believe all SYS1 were assigned to the temporary mcat and I could not change that. If I remember correctly?   

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Hi Kurt,

If I choose to use the master catalog of my driving system, can I create a user catalog and alias REFZ31 on my driving system? In order to catalog all REFZ31 on the user catalog instead of driving master catalog, and then I can connect the user catalog to the master catalog of my future zos31 SYST LPAR (which maintain SMPE).

Regards,

Abdennacer, when you choose the option to create a new master catalog, as you observe z/OSMF unconditionally renames the data sets to their true and desired names and removes the temporary catalog alias (SSA) prefix.  z/OSMF does create data set aliases (and PATHs for VSAM data sets) with the temporary catalog alias prefix for some of the data sets, but all are renamed to their true names as defined in the deployment configuration.

If you want all data sets to keep your chosen data set name prefix, please consider choosing the option to use the driving system's catalogs instead of creating a new master catalog.  In this case in the configuration you can define all data sets to contain your prefix, REFZ31, and z/OSMF will not rename them.  You can also tell z/OSMF to create a new user catalog for all of the data sets with the REFZ31 prefix if you like.  Later during your custom deploy/clone process you can remove the prefix and create your new master catalog.

If you want to try this option, go back to the Objectives step in the Deployment checklist, and change your catalog selection to "Existing master catalog".  Then update the configuration to add your prefix to all data set names, and regenerate the JCL.

Let me know if you have further questions or troubles.

Hi Kurt,

I'm installing ZOS 3.1 FROM ZOMSF and I have done all step until generating JCL to deploy.

I have found 7 generated JOB. 

I have choosed REFZ31 as SSA.

The problem is that the last 2 jobs which are IZUD06RN and IZUD07UC, try to alter the datasets and rename them without REFZ31.

But, I want to maintain datasets with HLQ REFZ31 as they are SMP/E datasets and maintain the master catalog created during the deploy as a user catalog for all REFZ31 datasets.

When I need to deploy ZOS31 on an LPAR I copy all dataset to new volumes with ADRDSSU + Rename (Remove REFZ31) and I create a new master catalogue.

Could you help me to deal with that issue.

Best regards,

Matt, glad I could help.  Connecting existing user catalogs to a new master catalog, and therefore allowing use of existing HLQs for those existing user catalogs, is not currently supported, so you didn't miss it.  Your example naming standard for zfs files of SYS1.ZOS.* looks like a multi-level catalog alias, which is in addition to connecting existing user catalogs, but also not currently supported.  Your best option for now may be to let z/OSMF catalog those data sets in the new master catalog, and then after the configuration steps in the workflows are complete and you've removed the temporary catalog aliases, then manually rename and recatalog those data sets into your desired user catalogs.

We do understand the requirements, and both of those are in our backlog.

Kurt, thank you so much for your assistance. I would not have gotten through this without your help. 

This was my first time through zosmf install and what I did not like (unless I missed it) was being able to assign certain datasets to not use the temporary HLQ so they would be allocated with their own unique names in the correct existing catalog. Specifically, the vsam CSI's and the ZFS files. The naming standards at this place for zfs files are SYS1.ZOS.* so I believe all SYS1 were assigned to the temporary mcat and I could not change that. If I remember correctly?   

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt

Yes, absolutely, you can create a new user catalog with an alias of REFZ31 on your driving system, and then catalog all target data sets in that user catalog.

As I mentioned previously, on the Objectives step of the deployment checklist, choose the Existing Catalogs option.  On the Data Sets step of the configuration wizard, name all your data sets with the REFZ31 prefix.  Then on the Catalogs step of the Configuration wizard, select the REFZ31 prefix, click Actions -> Select Catalog.  On the Select Catalog page, click Actions -> New Catalog to define your new user catalog.

Hi Kurt,

If I choose to use the master catalog of my driving system, can I create a user catalog and alias REFZ31 on my driving system? In order to catalog all REFZ31 on the user catalog instead of driving master catalog, and then I can connect the user catalog to the master catalog of my future zos31 SYST LPAR (which maintain SMPE).

Regards,

Abdennacer, when you choose the option to create a new master catalog, as you observe z/OSMF unconditionally renames the data sets to their true and desired names and removes the temporary catalog alias (SSA) prefix.  z/OSMF does create data set aliases (and PATHs for VSAM data sets) with the temporary catalog alias prefix for some of the data sets, but all are renamed to their true names as defined in the deployment configuration.

If you want all data sets to keep your chosen data set name prefix, please consider choosing the option to use the driving system's catalogs instead of creating a new master catalog.  In this case in the configuration you can define all data sets to contain your prefix, REFZ31, and z/OSMF will not rename them.  You can also tell z/OSMF to create a new user catalog for all of the data sets with the REFZ31 prefix if you like.  Later during your custom deploy/clone process you can remove the prefix and create your new master catalog.

If you want to try this option, go back to the Objectives step in the Deployment checklist, and change your catalog selection to "Existing master catalog".  Then update the configuration to add your prefix to all data set names, and regenerate the JCL.

Let me know if you have further questions or troubles.

Hi Kurt,

I'm installing ZOS 3.1 FROM ZOMSF and I have done all step until generating JCL to deploy.

I have found 7 generated JOB. 

I have choosed REFZ31 as SSA.

The problem is that the last 2 jobs which are IZUD06RN and IZUD07UC, try to alter the datasets and rename them without REFZ31.

But, I want to maintain datasets with HLQ REFZ31 as they are SMP/E datasets and maintain the master catalog created during the deploy as a user catalog for all REFZ31 datasets.

When I need to deploy ZOS31 on an LPAR I copy all dataset to new volumes with ADRDSSU + Rename (Remove REFZ31) and I create a new master catalogue.

Could you help me to deal with that issue.

Best regards,

Matt, glad I could help.  Connecting existing user catalogs to a new master catalog, and therefore allowing use of existing HLQs for those existing user catalogs, is not currently supported, so you didn't miss it.  Your example naming standard for zfs files of SYS1.ZOS.* looks like a multi-level catalog alias, which is in addition to connecting existing user catalogs, but also not currently supported.  Your best option for now may be to let z/OSMF catalog those data sets in the new master catalog, and then after the configuration steps in the workflows are complete and you've removed the temporary catalog aliases, then manually rename and recatalog those data sets into your desired user catalogs.

We do understand the requirements, and both of those are in our backlog.

Kurt, thank you so much for your assistance. I would not have gotten through this without your help. 

This was my first time through zosmf install and what I did not like (unless I missed it) was being able to assign certain datasets to not use the temporary HLQ so they would be allocated with their own unique names in the correct existing catalog. Specifically, the vsam CSI's and the ZFS files. The naming standards at this place for zfs files are SYS1.ZOS.* so I believe all SYS1 were assigned to the temporary mcat and I could not change that. If I remember correctly?   

Matt, after you've completed the Deployment Checklist (finished the last step in the checklist), a new software instance object is created in the z/OSMF db corresponding with the software you just installed.  From the Software Management main page, go to the list of Software Instances and find this new software instance object.  Select it, click Actions, Delete Temporary Catalog Aliases.

Kurt, back to my question pertaining to the path statements and your response 'Delete Temporary Catalog Alias '. I think I missed this somewhere in the workflow, where would this be found? I am to the point where I'd like to remove the path so I can either copy or rename the zfs files to my desired name. I tried to copy them using utility ADRDSSU using the temp HLQ name Z31MCAT.SYS1.ZOS31.OMVS.ETC. I got the error unable to locate file, I'd like to copy and/or rename all my zfs files so they are in my system master catalog where they belong. Dropping the Z31MCAT HLQ and just be SYS1. 

Listcat display if it helps. 

PATH ---------- Z31MCAT.SYS1.ZOS31.OMVS.ETC                  
     IN-CAT --- CATALOG.Z31MCAT                              
     HISTORY                                                 
       DATASET-OWNER-----(NULL)     CREATION--------2024.206                                                   
     RELEASE----------------2     EXPIRATION------0000.000
   PROTECTION-PSWD-----(NULL)     RACF----------------(NO)
   ASSOCIATIONS                                           
     CLUSTER--SYS1.ZOS31.OMVS.ETC                         
     DATA-----SYS1.ZOS31.OMVS.ETC.DATA                    
   ATTRIBUTES                                             
     UPDATE   

Thanks Matt

Matt, please DO NOT REMOVE the data set aliases and PATHs manually... instead tell z/OSMF to do it, later.

The PATH entry (for VSAM data sets) and data set alias (for non-VSAM) allow programs access to the data sets via the driving system's catalog.  That is, when z/OSMF, SMP/E, or other programs are running on the driving system they can find the data set if referenced by the PATH or alias name, Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT for example.  Whereas the true data set name, like SYS1.ZOS31.OMVS.JAVAROOT, will only be found by programs later when running on your target system using the new target system master catalog. 

After running the generated deployment jobs, the next step in the Deployment checklist is to perform the supplied workflows which help you setup and configure the installed software.  The workflow step actions run from the driving system, so they need to access the data sets through the driving system catalog.  In fact, during this time z/OSMF will EXPECT to find the data sets using these PATH and alias names, so please do NOT manually remove them.

Later, after you're done with the setup and configuration, after the Deployment is complete, then you can remove the PATHs and data set aliases by using the Delete Temporary Catalog Alias action against the target software instance.  Not only will this action generate the JCL necessary to remove the PATHs and aliases, but it will disconnect the new target system master catalog from the driving system's catalog, and update the data set names referenced by z/OSMF for this software instance.

Kurt, thanks for confirming. I guess I'll have to go the SSA route as I did with Custompac. 

Another question if I could, concerning the vsam files and job IZUD06RN, after the vsam file is renamed, there is a define for a path entry. I have not used these in the past

and I'm not sure what they are used for? can these be removed? 

Would removing them require downstream jobs to abend or would the downstream jobs need to be modified?

Thank you, appreciated Matt

IF LASTCC = 0 THEN -                          
  DEFINE PATH( -                              
    NAME(Z31MCAT.SYS1.ZOS31.OMVS.JAVAROOT) -  
    PATHENTRY(SYS1.ZOS31.OMVS.JAVAROOT)) -    
    CATALOG(CATALOG.Z31MCAT)                  

Matt, sadly in z/OSMF Software Management you cannot define two different symbols to represent a single volume.

At the moment I can think of only two possible workarounds, neither of which is ideal:

1. Update your existing catalog entries to use one single symbol for the SYSRES.
2. On the Catalogs page of the Configuration wizard tell z/OSMF the data sets that use the &RES2 symbol will be uncataloged.   Whether this is even possible however depends on if those data sets may be uncataloged and all have an HLQ that is unique from other data sets.

Is there a way to define 2 symbolics in the 'Volumes and Storage Classes' for the new sysres volume? It appears that in the existing master catalog some indirect cataloged datasets sets are cataloged with 

&RES2 and some are cataloged with '******' . In the 'Volumes and Storage Classes' panel I select the new RES volume, select modify to define indirect catalog method and enter both symbols, but the field only lets you enter 1 symbolic? Is there some kind of work around for this? 

Thanks Matt