Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

It appears that the contents of the workflows (three in this instance)  are also written as PDS members to the zOS dataset SYS1.CPAC.WORKFLOW in XML format. Is there any way to extract this info in readable form even in a limited capacity ? 

Martin

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

Extract the workflow information into human consumable form directly from the definition file?  No.  After you create the workflow instance in the Workflows task, then you can Print it, but not before.

It appears that the contents of the workflows (three in this instance)  are also written as PDS members to the zOS dataset SYS1.CPAC.WORKFLOW in XML format. Is there any way to extract this info in readable form even in a limited capacity ? 

Martin

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

Extract the workflow information into human consumable form directly from the definition file?  No.  After you create the workflow instance in the Workflows task, then you can Print it, but not before.

It appears that the contents of the workflows (three in this instance)  are also written as PDS members to the zOS dataset SYS1.CPAC.WORKFLOW in XML format. Is there any way to extract this info in readable form even in a limited capacity ? 

Martin

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

One more question - is it possible to reopen a deployment that's been marked 'complete' ?  Even if I select  to 'modify' such a deployment, most of the checklist items are marked 'complete' and are no longer 'selectable' 

Thanks,

Martin

Extract the workflow information into human consumable form directly from the definition file?  No.  After you create the workflow instance in the Workflows task, then you can Print it, but not before.

It appears that the contents of the workflows (three in this instance)  are also written as PDS members to the zOS dataset SYS1.CPAC.WORKFLOW in XML format. Is there any way to extract this info in readable form even in a limited capacity ? 

Martin

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.

No, you cannot modify a Deployment that has the state "Completed".  Why do you want to "reopen" the Deployment?  What are you trying to do?  Are your data set rename questions pertaining to a Deployment that is already complete?  I'm confused then about your original ask and what you want to do.

You can View the Deployment instead of Modify and that lets you see the configuration and generated JCL.  If you want to see the workflows, go to the Software Instance that was created by the deployment and select action Perform Workflows.  This will open the list of workflow instances created during the Deployment.

One more question - is it possible to reopen a deployment that's been marked 'complete' ?  Even if I select  to 'modify' such a deployment, most of the checklist items are marked 'complete' and are no longer 'selectable' 

Thanks,

Martin

Extract the workflow information into human consumable form directly from the definition file?  No.  After you create the workflow instance in the Workflows task, then you can Print it, but not before.

It appears that the contents of the workflows (three in this instance)  are also written as PDS members to the zOS dataset SYS1.CPAC.WORKFLOW in XML format. Is there any way to extract this info in readable form even in a limited capacity ? 

Martin

Thanks Kurt - presumably the rename must include ALL of the new V3.1 datasets, not just the SMP/E CSI that the initial error is being issued against ? 

Regards,

Martin

Martin, I am sorry to say there is no way to get around this problem.  You must rename the data sets back to the names that are known to z/OSMF.  After you have performed the workflows and completed the Deployment operation, then you can rename data sets.  However, if you created a new master catalog during the deployment and want to remove the temporary catalog alias prefix, please use the Delete Temporary Catalog Alias action in Software Management instead of manually renaming data sets.  This action will update z/OSMF's known data set names as well as rename the data sets.

Hi There

We are currently installing zOS V3.1 via zOSMF Software Management and are now in the midst of customising and renaming the final configuration.  I wanted to revisit the installation workflows and received the error:

GIM70533E CSI data set ZOSR31.SPYSCP.ZOS.V3R1.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed.

This is because at this stage we have renamed our CSI to it's final system name by removing the HLQ ZOSR31.   Is there a way to get around this by tweaking zOSMF somehow internally to allow the workflow contents to be viewed ? I really don't want to have to start renaming datasets back with prefix ZOSR31 if I can help it.

Thanks

Martin

Unfortunately the website will not allow me to upload screen shots.