Perform these steps to move your control data set and journal to a different device by using the EDGHSKP utility with the PARM='BACKUP' parameter.

1. Allocate a new control data set and journal. Refer to Step 12: Creating the DFSMSrmm control data set for information on allocating the control data set. Now is a good time to consider whether you should allocate the control data set as an extended format (EF) data set and to optionally set the extended addressability (EA) attribute so that the control data set can grow beyond 4GB in size.
2. Back up the control data set and the journal.
   Example: With DFSMSrmm active, run EDGHSKP,PARM='BACKUP' ' to back up the control data set and the journal and to clear the current journal.

    // EXEC PGM=EDGHSKP,PARM='BACKUP'
    //MESSAGE  DD DISP=SHR,DSN=messages
    //SYSPRINT DD SYSOUT=*
    //BACKUP   DD DISP=(,CATLG),DSN=cds backup(+1),UNIT=SYSALLDA,
    //         RECFM=VB,LRECL=9216,BLKSIZE=0
    //JRNLBKUP DD DISP=(,CATLG),DSN= journal backup(+1),UNIT=SYSALLDA,
    //         RECFM=VB,LRECL=9248,BLKSIZE=0,BUFNO=30

   This clears the current journal data set. Some records might be written to the journal if any updates are made to the control data set before the DFSMSrmm procedure is stopped. This is not a problem because the restore operation will use them in forward recovery.

3. Stop or quiesce the DFSMSrmm procedure to prevent any further updates to the control data set during recovery.
4. Restore the backup of the control data set to the new control data set allocated in step 1 .
   Example: This JCL example puts the latest DFSMSrmm information into the new control data set and uses the old journal to forward recover the control data set backup to the point where the you stopped the DFSMSrmm procedure.

   // EXEC PGM=EDGBKUP,PARM='RESTORE'
   //SYSPRINT DD SYSOUT=*
   //BACKUP DD DISP=SHR,DSN=cds backup(0)
   //MASTER DD DISP=SHR,DSN=new control data set
   //JOURNAL DD DISP=SHR,DSN=old journal

   Note: Steps 2, 3, and 4 can be optimized to minimize DFSMSrmm downtime and to reorganize the control data set in less time. To optimize the DFSMSrmm downtime, use these steps:

   1. Back up the control data set and the journal. For example, with DFSMSrmm active, run EDGHSKP,PARM=’BACKUP’ to back up the control data set and the journal and to clear the current journal.

      // EXEC PGM=EDGHSKP,PARM=’BACKUP’
      //MESSAGE DD DISP=SHR,DSN=messages
      //SYSPRINT DD SYSOUT=*
      //BACKUP DD DISP=SHR,DSN=new control data set
      //JRNLBKUP DD DISP=(,CATLG),DSN= journal backup(+1),UNIT=SYSALLDA
      // RECFM=VB,LRECL=9248,BLKSIZE=0,BUFNO=30

      This copies the control data set to the new control data set and reorganizes the records and clears the current journal data set. Once the backup is completed, the new control data set is almost ready for use by DFSMSrmm. Some records might be written to the journal if any updates are made to the control data set before the DFSMSrmm procedure is stopped. This is not a problem because the forward recovery operation will use them.
   2. Stop or quiesce the DFSMSrmm procedure to prevent any further updates to the control data set during recovery.
   3. Forward recover the new control data set from step b. For example, this JCL example uses the old journal to forward recover the new control data set to the point where you stopped the DFSMSrmm procedure.

      // EXEC PGM=EDGBKUP,PARM=’RESTORE’
      //SYSPRINT DD SYSOUT=*
      //MASTER DD DISP=SHR,DSN=new control data set
      //JOURNAL DD DISP=SHR,DSN=old journal

5. Implement the new data sets by using one of these techniques:
   • Use IDCAMS ALTER command to rename the new control data set and new journal, after renaming the old data sets, or
   • Create a new EDGRMMxx parmlib member with the new names, or
   • Update the current parmlib member to include the names of the new control data set and journal.
6. 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.

   If you are keeping multiple control data set and journal backups for error recovery situations, perform step 2 again to backup the control data set and journal.

   Recommendation: Back up the new data sets now to avoid keeping the old journal for recovery. As your backup copies are created in the future, your requirement for the old journal will be eliminated.

You are done when you have successfully moved the control data set and journal.