I have completed my zos 3.1 install including the rename job, we used a temporary HLQ with a new temporary catalog. After the rename job I am left with ZFS and CSI files that I cannot access from zos (I believe because of the PATH statement added) in the rename job. I cannot use IBM utility like IDCAMS or ADRDSSU to clone them to the correct names and correct catalog. These utilities fail with unable to locate dataset, I tried both names. The before the rename name and the name after the rename name. 

I can mount the zfs files and see the internal files. For the zfs files, the only way I thought of to get around this is to allocate new zfs with the correct names, mount the input zfs and mount the new output zfs and use the unix copy function to copy all the unix files over. Then I still have to deal with csi files somehow because they are the wrong name and catalog. Not sure what I do can do with the CSI's? Need help here also. 

I'm thinking I am not the only one who has this issue or I am doing something wrong, Can you please advise. Thanks appreciated Matt

Matthew, I'm a little confused by your scenario and why you cannot access the subject data sets.  Did you use the deployment option to create a new master catalog?  What do you mean by "a temporary HLQ and a new temporary catalog"?  Were the subject data sets cataloged in this "temporary" catalog, and does this catalog still exist?  As said, I'm confused by your scenario, and I fear this conversation may necessarily get quite involved.  You might be better off opening a support case to debug your situation.

Having said that, if and only if you used the deployment option to create a new master catalog, then after the Deployment is complete you can use the Delete Temporary Catalog Alias action on the target software instance.  z/OSMF will analyze all of the data sets, aliases, and catalogs, summarize its findings, and generate jobs you can use to remove the temp catalog aliases.  If you did not use the deployment option to create a new master catalog, then never mind.

I have completed my zos 3.1 install including the rename job, we used a temporary HLQ with a new temporary catalog. After the rename job I am left with ZFS and CSI files that I cannot access from zos (I believe because of the PATH statement added) in the rename job. I cannot use IBM utility like IDCAMS or ADRDSSU to clone them to the correct names and correct catalog. These utilities fail with unable to locate dataset, I tried both names. The before the rename name and the name after the rename name. 

I can mount the zfs files and see the internal files. For the zfs files, the only way I thought of to get around this is to allocate new zfs with the correct names, mount the input zfs and mount the new output zfs and use the unix copy function to copy all the unix files over. Then I still have to deal with csi files somehow because they are the wrong name and catalog. Not sure what I do can do with the CSI's? Need help here also. 

I'm thinking I am not the only one who has this issue or I am doing something wrong, Can you please advise. Thanks appreciated Matt

Matthew, I'm a little confused by your scenario and why you cannot access the subject data sets.  Did you use the deployment option to create a new master catalog?  What do you mean by "a temporary HLQ and a new temporary catalog"?  Were the subject data sets cataloged in this "temporary" catalog, and does this catalog still exist?  As said, I'm confused by your scenario, and I fear this conversation may necessarily get quite involved.  You might be better off opening a support case to debug your situation.

Having said that, if and only if you used the deployment option to create a new master catalog, then after the Deployment is complete you can use the Delete Temporary Catalog Alias action on the target software instance.  z/OSMF will analyze all of the data sets, aliases, and catalogs, summarize its findings, and generate jobs you can use to remove the temp catalog aliases.  If you did not use the deployment option to create a new master catalog, then never mind.

I have completed my zos 3.1 install including the rename job, we used a temporary HLQ with a new temporary catalog. After the rename job I am left with ZFS and CSI files that I cannot access from zos (I believe because of the PATH statement added) in the rename job. I cannot use IBM utility like IDCAMS or ADRDSSU to clone them to the correct names and correct catalog. These utilities fail with unable to locate dataset, I tried both names. The before the rename name and the name after the rename name. 

I can mount the zfs files and see the internal files. For the zfs files, the only way I thought of to get around this is to allocate new zfs with the correct names, mount the input zfs and mount the new output zfs and use the unix copy function to copy all the unix files over. Then I still have to deal with csi files somehow because they are the wrong name and catalog. Not sure what I do can do with the CSI's? Need help here also. 

I'm thinking I am not the only one who has this issue or I am doing something wrong, Can you please advise. Thanks appreciated Matt

Matthew, the additional information helps.  In particular you state:

This may be the underlying issue, as I think you misunderstand the option to create a new master catalog.  The new master catalog you create during the deployment is intended to be the master catalog used when you IPL the new target system.  That is why the Rename job renames the data sets so the desired true data set name is cataloged in the new master, and a data set alias (or PATH for VSAM data sets) is created in the driving system's catalog.  The new master catalog is not meant to be a temporary catalog.   If you want to use the existing driving system's catalog in the end, then in the future don't choose the option to create a new master catalog.  This page may help explain the options:
https://www.ibm.com/docs/en/zos/3.1.0?topic=page-catalogs

Matthew, I'm a little confused by your scenario and why you cannot access the subject data sets.  Did you use the deployment option to create a new master catalog?  What do you mean by "a temporary HLQ and a new temporary catalog"?  Were the subject data sets cataloged in this "temporary" catalog, and does this catalog still exist?  As said, I'm confused by your scenario, and I fear this conversation may necessarily get quite involved.  You might be better off opening a support case to debug your situation.

Having said that, if and only if you used the deployment option to create a new master catalog, then after the Deployment is complete you can use the Delete Temporary Catalog Alias action on the target software instance.  z/OSMF will analyze all of the data sets, aliases, and catalogs, summarize its findings, and generate jobs you can use to remove the temp catalog aliases.  If you did not use the deployment option to create a new master catalog, then never mind.

I have completed my zos 3.1 install including the rename job, we used a temporary HLQ with a new temporary catalog. After the rename job I am left with ZFS and CSI files that I cannot access from zos (I believe because of the PATH statement added) in the rename job. I cannot use IBM utility like IDCAMS or ADRDSSU to clone them to the correct names and correct catalog. These utilities fail with unable to locate dataset, I tried both names. The before the rename name and the name after the rename name. 

I can mount the zfs files and see the internal files. For the zfs files, the only way I thought of to get around this is to allocate new zfs with the correct names, mount the input zfs and mount the new output zfs and use the unix copy function to copy all the unix files over. Then I still have to deal with csi files somehow because they are the wrong name and catalog. Not sure what I do can do with the CSI's? Need help here also. 

I'm thinking I am not the only one who has this issue or I am doing something wrong, Can you please advise. Thanks appreciated Matt

Matthew, the additional information helps.  In particular you state:

This may be the underlying issue, as I think you misunderstand the option to create a new master catalog.  The new master catalog you create during the deployment is intended to be the master catalog used when you IPL the new target system.  That is why the Rename job renames the data sets so the desired true data set name is cataloged in the new master, and a data set alias (or PATH for VSAM data sets) is created in the driving system's catalog.  The new master catalog is not meant to be a temporary catalog.   If you want to use the existing driving system's catalog in the end, then in the future don't choose the option to create a new master catalog.  This page may help explain the options:
https://www.ibm.com/docs/en/zos/3.1.0?topic=page-catalogs

Matthew, I'm a little confused by your scenario and why you cannot access the subject data sets.  Did you use the deployment option to create a new master catalog?  What do you mean by "a temporary HLQ and a new temporary catalog"?  Were the subject data sets cataloged in this "temporary" catalog, and does this catalog still exist?  As said, I'm confused by your scenario, and I fear this conversation may necessarily get quite involved.  You might be better off opening a support case to debug your situation.

Having said that, if and only if you used the deployment option to create a new master catalog, then after the Deployment is complete you can use the Delete Temporary Catalog Alias action on the target software instance.  z/OSMF will analyze all of the data sets, aliases, and catalogs, summarize its findings, and generate jobs you can use to remove the temp catalog aliases.  If you did not use the deployment option to create a new master catalog, then never mind.

I have completed my zos 3.1 install including the rename job, we used a temporary HLQ with a new temporary catalog. After the rename job I am left with ZFS and CSI files that I cannot access from zos (I believe because of the PATH statement added) in the rename job. I cannot use IBM utility like IDCAMS or ADRDSSU to clone them to the correct names and correct catalog. These utilities fail with unable to locate dataset, I tried both names. The before the rename name and the name after the rename name. 

I can mount the zfs files and see the internal files. For the zfs files, the only way I thought of to get around this is to allocate new zfs with the correct names, mount the input zfs and mount the new output zfs and use the unix copy function to copy all the unix files over. Then I still have to deal with csi files somehow because they are the wrong name and catalog. Not sure what I do can do with the CSI's? Need help here also. 

I'm thinking I am not the only one who has this issue or I am doing something wrong, Can you please advise. Thanks appreciated Matt