z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Steps for moving the control data set using non-dfsmsrmm utilities

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

Perform these steps to move your control data set to a different device by using non-DFSMSrmm utilities such as AMS REPRO and EXPORT/IMPORT, or DFSMSdss ADRDSSU.

  1. Allocate a new control data set only if you are planning to use AMS REPRO.
  2. Stop or quiesce the DFSMSrmm procedure to prevent any further updates to the control data set during recovery.
  3. Copy the old control data set to the new control data set by using one of these utilities:
    • AMS REPRO.
    • AMS EXPORT followed by IMPORT.
    • DFSMSdss ADRDSSU utility.
      Here is an example of copying the old control data set to the new control data set by using the DFSMSdss ADRDSSU utility.
      //COPYCDS  EXEC PGM=ADRDSSU,REGION=8M
      //SYSPRINT DD SYSOUT=*
      //SYSIN    DD *
              COPY -
              LOGINDYNAM (SHRPK3) -
              DS(INC(RMM.CDS)) -
              OUTDYNAM(SHRPK2) -
              SPHERE -
              RENAMEU(*.CDS,*.NEWCDS)
  4. Implement the data sets by using one of these techniques:
    • Use IDCAMS ALTER command to rename the new control data set, having first renamed the old data set, or
    • Create a new EDGRMMxx parmlib member, or
    • Update the current parmlib member to include the name of the new control data set.
  5. If you stopped DFSMSrmm, start the DFSMSrmm procedure, using the updated parmlib member or the new parmlib member. If you quiesced DFSMSrmm, use the MODIFY command to specify the parmlib member suffix to be used. This will use the moved control data set and the unmoved journal.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014