RESTORE/RECOVER › General Information › Restore Considerations for GDG Data Sets › NEWNAME:

NEWNAME:

When this parameter is specified, RESTORE treats the target DSNAME as a new data set creation. The target data set will always be cataloged and placed in the sphere, whether the sphere is full or not.

For non-SMS Data Sets without NEWNAME:

• If a catalog entry exists, the entry is left intact.
• If no catalog entry exists, the data set will be cataloged unless doing so would force another entry out of the catalog (that is, the sphere is full).

For SMS Data Sets without NEWNAME:

• If a catalog entry exists and it has a valid status, the status will be left intact.
• If a catalog entry exists but a valid status cannot be detected, or if a catalog entry does not currently exist, the status of the entry will be set to a status as close as possible to what it was at the time of the backup, unless doing so would force another entry out of the catalog. Therefore, the following will apply:
  • Data sets with a status of ACTIVE when backed up will be placed back in ACTIVE status, unless doing so would force another entry out of the catalog.
  • Data sets with a status of DEFERRED or ROLLED-OFF when backed up, but no longer have a valid status or catalog entry when the restore is initiated, will be placed in DEFERRED status whether or not the sphere is full.
  • If the original catalog status cannot be determined it will be placed in ACTIVE status.
  • If the sphere is full (that is, the GDG's limit has been reached), the entry will be placed in DEFERRED status, regardless of what its status was at the time of the backup.

If CA Disk cannot set a data set's catalog entry to the status CA Disk feels is correct, message 3729 will be issued to indicate the status the data set was left in, and the reason for placing the data set in that status.

For more information, see User Exit GDGCATEX —GDG Data set Catalog Action in the Systems Guide.