EXEC parameters for EDGBKUP

Figure 1 shows the EXEC parameters for EDGBKUP.

Figure 1. EDGBKUP EXEC parameters


>>-+-RESTORE--------------+------------------------------------><
   |         .-NREORG-.   |   
   '-BACKUP(-+-COPY---+-)-'   
             +-DSS----+       
             '-REORG--'

RESTORE

Specify RESTORE to restore and forward recover the control data set from a backup copy. When you specify the BACKUP DD statement, DFSMSrmm restores the control data set. When you specify the JOURNAL DD or SMFIN DD statements, forward recovery is attempted. You can specify both the BACKUP DD statement and the JOURNAL or SMFIN DD statement in the same job step to restore and forward recover the control data set from journal backups and the journal data set or from SMF records.

RESTORE allows you to customize the DFSMSdss options that DFSMSrmm uses. See Customizing the DSSOPT DD statement for additional information.

Forward recovery using SMF records is only possible when you use the IBM SMF record type by means of parmlib option SMFAUD(YES). You cannot mix JOURNAL and SMFIN records for forward recovery in a single execution of EDGBKUP. Message EDG6138E is issued if you try this. When you have some journal records and some SMF records, run EDGBKUP multiple times with either SMFIN or JOURNAL specified in the correct sequence from the oldest records to the newest to the recovery target or latest time. If JOURNAL records are available for forward recovery, IBM recommends that you use journal records instead of SMF records.

When you forward recover from SMF records, it might not be possible to recover to an exact time that matches with the current DFSMSrmm JOURNAL. On restart of DFRMM, WTOR EDG2106D can be expected.

BACKUP(COPY | DSS | NREORG | REORG)

Specify BACKUP to control the way DFSMSrmm backs up, copies, and optionally reorganizes the DFSMSrmm control data set.

Restriction: You cannot RESTORE or REORG an active DFSMSrmm control data set. You must stop or quiesce DFSMSrmm or ensure that the control data set is not in use by DFSMSrmm.

COPY

Specify BACKUP(COPY) to use DFSMSdss to create a logical data set copy of the control data set and optionally, a backup of the journal. DFSMSrmm uses DFSMSdss to create the copy of the control data set and IDCAMS to back up the journal. To allow updates to the control data set during backup processing, set up the DFSMSdss concurrent copy environment, virtual concurrent copy environment, or a fast replication with virtual concurrent copy environment. You must have the hardware and software required to establish a concurrent copy session, a virtual concurrent copy session, or fast replication with concurrent copy or virtual concurrent copy.

Restriction: If you specify BACKUP(COPY) without establishing a non-intrusive copy environment, DFSMSrmm performs back up processing, but DFSMSrmm does not allow updates to the control data set until DFSMSdss notifies DFSMSrmm that the control data set copy or copy initialization completes. A non-intrusive copy environment is guaranteed by using the FR(PREFERRED) together with CONCURRENT(ANYREQUIRED) keywords. When you use FR(REQUIRED), there is no notification to DFSMSrmm until all DFSMSdss processing is completed. Although this might be a very short time, any CDS updates attempted during that period will be processed as if an intrusive backup is in progress. IBM recommends that you use FR(PREFERRED) with CONCURRENT.

DSSOPT is an optional DD statement that is for use with BACKUP(COPY). BACKUP allows you to customize the DFSMSdss COPY options that DFSMSrmm uses. See Customizing the DSSOPT DD statement for additional information.

The CDS copy that is created is ready for use with DFSMSrmm. No restore is required. However, you can optionally use the EDGBKUP utility with RESTORE and MASTER, and JOURNAL DD statements to perform forward recovery to your selected point in time.

DSS

Specify BACKUP(DSS) to use DFSMSdss to back up the control data set. DFSMSrmm uses DFSMSdss to back up the control data set and IDCAMS to back up the journal. To allow updates to the control data set during backup processing, set up the DFSMSdss concurrent copy environment or virtual concurrent copy environment. You must have the hardware and software required to establish a concurrent copy session or a virtual concurrent copy session.

Restriction: If you specify BACKUP(DSS) without establishing a concurrent copy session, DFSMSrmm performs back up processing but DFSMSrmm does not allow updates to the control data set until the control data set backup completes. If DFSMSrmm is active and you specify BACKUP(DSS), DFSMSrmm allows backup directly to tape when the journal is not full or locked.

DSSOPT is an optional DD statement that is for use with BACKUP(DSS). BACKUP allows you to customize the DFSMSdss options that DFSMSrmm uses. See Customizing the DSSOPT DD statement for additional information.

You can use the EDGBKUP utility or DFSMSdss to restore backups of the control data set that are created using DFSMSdss. If you use DFSMSdss to restore the backup, you must use the EDGBKUP utility to perform forward recovery to reset the control information in the restored control data set. DFSMSrmm issues message EDG0123D when you start DFSMSrmm and have not reset the control information in the control data set.

NREORG

Specify BACKUP(NREORG) to use IDCAMS to back up the control data set and to back up the journal data set.

NREORG is the default.

REORG

Specify BACKUP(REORG) to reorganize the control data set during backup processing. DFSMSrmm uses IDCAMS to back up the control data set, to optionally back up the journal, and to restore the control data set from the backup.