z/OS DFSMSdss Storage Administration
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


IMPORT

z/OS DFSMSdss Storage Administration
SC23-6868-01

Read syntax diagramSkip visual syntax diagram
>>-+--------+--------------------------------------------------><
   '-IMPORT-'   

IMPORT specifies that the data sets that are being restored were dumped from a different system and they should be considered new data sets.

Because the restored data sets are new to the system, DFSMSdss modifies certain source data set processing. The following examples apply:
  • DFSMSdss bypasses checking to see if you are authorized to read a data set with the same name as the one that was dumped.

    If you are authorized to read the input dump data set that contains the data sets that are being restored, DFSMSdss considers that you have the authority to read any data set that is being restored. DFSMSdss continues to check to see that you are authorized to create a new target data set or replace an existing target data set.

    If you are restoring the data set without renaming it, the restore might be unsuccessful. There are several common reasons for such a failure:
    • You do not have sufficient authority to create a target data set with the same name as the source data set. You must obtain the required access authority to do so before you can restore the data set.
    • A data set already exists with the same name as the source data set and you did not specify the REPLACE or REPLACEUNCONDITIONAL keyword. You must also specify the REPLACE or REPLACEUNCONDITIONAL keyword if you want the restore to replace an existing data set.
    • A data set with the same name as the source data set is already cataloged, but is not available to the restoring system. You must make the volumes that contain the data set, and, as applicable, its VVDS, available to the restoring system before you can restore the data set.
    • A catalog contains a phantom entry for a data set with the same name as the source data set. In this case, the data set does not exist on any volume. You can perform a separate DELETE NOSCRATCH operation for that data set name. Or you can specify the DELETECATALOGENTRY parameter to request that DFSMSdss perform a DELETE NOSCRATCH operation for you.
      Attention: Do not use the DELETECATALOGENTRY keyword if the restoring system is sharing catalogs, but not the data set volumes, with another system.
  • DFSMSdss can try to access a VVDS for a source data set in order to obtain information such as the resource owner. If you specify IMPORT, DFSMSdss suppresses a VVDS not available error.
To specify IMPORT, you must have the proper RACF® facility class authorization.
Note:
  1. IMPORT should be RACF-protected.
  2. IMPORT is only supported for logical data set restore.
  3. DELETECATALOGENTRY might have to be specified to successfully restore a data set with the old data set name.
  4. When IMPORT is specified, DFSMSdss does not create a discrete data set profile unless the source data set is RACF-protected when it is dumped and you specify the MENTITY keyword.

For more information about RACF authorization, see Protecting DFSMSdss functions.

For more information about using the IMPORT keyword, see Protecting the usage of DFSMSdss.

For more information about using the DELETECATALOGENTRY keyword to successfully restore a data set with the old data set name, see Managing availability with DFSMSdss.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014