How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

First I would like to thank you for your patience and tolerance of me. This is my last question. Can we have to use our z/os 3.1 upgrade PSI as a model on a z/os 3.1 driving system for a z/os 3.2 upgrade on a new target system. We don't upgrade each system it stays at the level we have it until it is no longer needed, all the way back to z/os 1.13. Thanks again 

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

I'm not sure if I understand your question, but are you asking "Can I use my z/OS 3.1 driving system as a model when I eventually install z/OS 3.2?"  Yes.  When you installed z/OS 3.1 you created a software instance object that represents that installed software.  You can use this software instance as your model when you install z/OS 3.2.  If that is not the question you are trying to ask, please rephrase.

First I would like to thank you for your patience and tolerance of me. This is my last question. Can we have to use our z/os 3.1 upgrade PSI as a model on a z/os 3.1 driving system for a z/os 3.2 upgrade on a new target system. We don't upgrade each system it stays at the level we have it until it is no longer needed, all the way back to z/os 1.13. Thanks again 

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

How do I import or get the 3.1 PSI (it is currently on a 2.4 system zosmf we used as the driver system) to the current target system zosmf ? I hope that makes sense. 

I'm not sure if I understand your question, but are you asking "Can I use my z/OS 3.1 driving system as a model when I eventually install z/OS 3.2?"  Yes.  When you installed z/OS 3.1 you created a software instance object that represents that installed software.  You can use this software instance as your model when you install z/OS 3.2.  If that is not the question you are trying to ask, please rephrase.

First I would like to thank you for your patience and tolerance of me. This is my last question. Can we have to use our z/os 3.1 upgrade PSI as a model on a z/os 3.1 driving system for a z/os 3.2 upgrade on a new target system. We don't upgrade each system it stays at the level we have it until it is no longer needed, all the way back to z/os 1.13. Thanks again 

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

Ah, OK.  You need to carry over your z/OSMF data directory, /global/zosmf/data (or /var/zosmf/data), to your 3.1 system and use that for the z/OSMF server running on z/OS 3.1.  Then you'll have all the data available on that new server, including the definitions for your software instances.

How do I import or get the 3.1 PSI (it is currently on a 2.4 system zosmf we used as the driver system) to the current target system zosmf ? I hope that makes sense. 

I'm not sure if I understand your question, but are you asking "Can I use my z/OS 3.1 driving system as a model when I eventually install z/OS 3.2?"  Yes.  When you installed z/OS 3.1 you created a software instance object that represents that installed software.  You can use this software instance as your model when you install z/OS 3.2.  If that is not the question you are trying to ask, please rephrase.

First I would like to thank you for your patience and tolerance of me. This is my last question. Can we have to use our z/os 3.1 upgrade PSI as a model on a z/os 3.1 driving system for a z/os 3.2 upgrade on a new target system. We don't upgrade each system it stays at the level we have it until it is no longer needed, all the way back to z/os 1.13. Thanks again 

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

Ah, OK.  You need to carry over your z/OSMF data directory, /global/zosmf/data (or /var/zosmf/data), to your 3.1 system and use that for the z/OSMF server running on z/OS 3.1.  Then you'll have all the data available on that new server, including the definitions for your software instances.

How do I import or get the 3.1 PSI (it is currently on a 2.4 system zosmf we used as the driver system) to the current target system zosmf ? I hope that makes sense. 

I'm not sure if I understand your question, but are you asking "Can I use my z/OS 3.1 driving system as a model when I eventually install z/OS 3.2?"  Yes.  When you installed z/OS 3.1 you created a software instance object that represents that installed software.  You can use this software instance as your model when you install z/OS 3.2.  If that is not the question you are trying to ask, please rephrase.

First I would like to thank you for your patience and tolerance of me. This is my last question. Can we have to use our z/os 3.1 upgrade PSI as a model on a z/os 3.1 driving system for a z/os 3.2 upgrade on a new target system. We don't upgrade each system it stays at the level we have it until it is no longer needed, all the way back to z/os 1.13. Thanks again 

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------

Good Morning Kurt

I copied the /global/zosmf/data over from our driver system (2.4) to our target system (3.1). They share RACF DB but I received the following RACF error message. Is there something else I need to do.  

ICH408I USER(IZUSVR  ) GROUP(IZUADMIN) NAME(Z/OSMF STC USERID   )
  /global/zosmf/data/logs/zosmfServer/workarea/org.eclipse.osgi  
  /151                                                           
  CL(DIRACC  ) FID(D9E2F3F3F1C13FB7000000000DC38552)             
  INSUFFICIENT AUTHORITY TO OPENDIR                              
  ACCESS INTENT(R--)  ACCESS ALLOWED(GROUP      ---)             
  EFFECTIVE UID(0000004134)  EFFECTIVE GID(0000001385)           

ICH408I USER(IZUSVR  ) GROUP(IZUADMIN) NAME(Z/OSMF STC USERID   )
  /global/zosmf/data/datastore/DeploymentManager/seg0/c1110.dat  
  CL(FSOBJ   ) FID(D9E2F3F3F1C13FB7000000000CC48552)             
  INSUFFICIENT AUTHORITY TO OPEN                                 
  ACCESS INTENT(R--)  ACCESS ALLOWED(GROUP      ---)             
  EFFECTIVE UID(0000004134)  EFFECTIVE GID(0000001385)           

ICH408I USER(IZUSVR  ) GROUP(IZUADMIN) NAME(Z/OSMF STC USERID   )
  /global/zosmf/data/logs/zosmfServer/kc/runtime/diskcache/SSB2  
  H8_2.4.0                                                       
  CL(DIRACC  ) FID(D9E2F3F3F1C13FB7000000000EB18552)             
  INSUFFICIENT AUTHORITY TO OPENDIR                              
  ACCESS INTENT(R--)  ACCESS ALLOWED(GROUP      ---)             
  EFFECTIVE UID(0000004134)  EFFECTIVE GID(0000001385)           

Ah, OK.  You need to carry over your z/OSMF data directory, /global/zosmf/data (or /var/zosmf/data), to your 3.1 system and use that for the z/OSMF server running on z/OS 3.1.  Then you'll have all the data available on that new server, including the definitions for your software instances.

How do I import or get the 3.1 PSI (it is currently on a 2.4 system zosmf we used as the driver system) to the current target system zosmf ? I hope that makes sense. 

I'm not sure if I understand your question, but are you asking "Can I use my z/OS 3.1 driving system as a model when I eventually install z/OS 3.2?"  Yes.  When you installed z/OS 3.1 you created a software instance object that represents that installed software.  You can use this software instance as your model when you install z/OS 3.2.  If that is not the question you are trying to ask, please rephrase.

First I would like to thank you for your patience and tolerance of me. This is my last question. Can we have to use our z/os 3.1 upgrade PSI as a model on a z/os 3.1 driving system for a z/os 3.2 upgrade on a new target system. We don't upgrade each system it stays at the level we have it until it is no longer needed, all the way back to z/os 1.13. Thanks again 

You also need to update the Workflow data set name.  On the Modify page, click the Workflows tab, select each workflow definition file, click Actions -> Modify to change the data set name.

The "not so straight forward" steps have to do with updating the provider defined data set properties.  You can see these properties if you View the software instance and click on the "Provider Defined Properties" tab.  Unfortunately you can't update the data set names in these properties in the UI.  The only way to update them is using the Modify REST API.  Sigh.  However, if your intention is only to use the subject software instance as a model for a future deployment, and if you never to create any workflow instances for the subject software instance, then you don't need to update the provider defined data set properties.

To update the data set names for the Non-SMP/E Managed data sets, in the Modify action, on that tab in your screen capture, select one data set and click Actions -> Modify to change the name of one data set.

But honestly, there's more to update which will not be so straight forward, so I really recommend you try to use the Delete Temporary Catalog Alias action.

Edward, what action are you using when you receive that message?

I assume MC31A is the temporary catalog alias created during the install of z/OS 3.1.  z/OSMF has a "Delete Temporary Catalog Alias" action that will analyze your catalogs abd generate the jobs necessary to update the SMP/E DDDEF entries, delete the data set aliases with the MC31A prefix, delete (EXPORT DISCONNECT) the new target system master catalog from the driving system's master catalog, and finally update the data set names in the software instance object referenced by z/OSMF.  Select the software instance created during the install of z/OS 3.1 and select this action.

If you have already manually deleted the new target system master catalog from the driving system's master catalog, did you also delete the data set aliases, and update the DDDEF entries as necessary?  Start by using the Modify action on the z/OS 3.1 software instance and changing the data set name for the global zone CSI.

How to delete temporary Alias from zOSMF after it has been deleted on driver system.

Receive message

Processing failed on system "MVS2" . Error: "IZUD9730E: The request cannot be completed because an error occurred reading global zone "MC31A.SMP31A.GLOBAL.CSI" on system "MVS2" . Error: "GIM70533E: CSI data set MC31A.SMP31A.GLOBAL.CSI for the GLOBAL zone does not exist in the catalog or the catalog can not be accessed." "

------------------------------
Edward Lewis
------------------------------