Volume DUMP (w/FDRINSTANT Variations) Statement

DUMP statement syntax

Only one DUMP, SIM, SNAP, CONSNAP, PSPLIT, CONPSPLIT, FCOPY, or CONFCOPY statement is permitted in each execution of FDRABR.

DUMP statement

The DUMP statement initiates a Volume Backup of DASD volumes or data sets. If TYPE=FDR is specified, a full-volume backup is taken of each selected DASD volume. If TYPE=ABR, AUTO, or DSF is specified, an incremental backup is taken of each selected DASD volume. In some circumstances, a full-volume backup may be taken in place of the incremental.

SIM statement

If SIM is specified instead of DUMP, ABR performs the DUMP function in a simulation mode. The TAPEx DD Statement must specify DD DUMMY. ABR does not perform the actual DUMP operation, but it prints the data set names selected by this operation using the PRINT VTOC format.

SNAP and CONSNAP statement

The SNAP and CONSNAP statements are used with FDRINSTANT when the DASD subsystem is an EMC Symmetrix with the optional TimeFinder/Clone or TimeFinder/Snap features. CONSNAP is used only with EMC. FDRINSTANT-for-EMC-TimeFinder describes Snap for TimeFinder. However, the volume backup consists of two steps, a SNAP step (that creates the backup), and a DUMP step (that transfers this backup to long term storage). Specify all of the same operands on the SNAP and DUMP statements, except for the SNAP= operand that is added to the DUMP step to invoke FDRINSTANT.

PSPLIT and CONPSPLIT statement

The PSPLIT and CONPSPLIT statements are used with FDRINSTANT when the DASD subsystem is an Hitachi Vantara system with the optional ShadowImage feature. FDRINSTANT-for-Hitachi-ShadowImage contains details of its use. However, the volume backup consists of two steps, a PSPLIT step (that creates the backup), and a DUMP step (that transfers this backup to long term storage). Specify all of the same operands on the PSPLIT and DUMP statements, except for the PPRC= operand that is added to the DUMP step to invoke FDRINSTANT.

FCOPY and CONFCOPY STATEMENT

The FCOPY and CONFCOPY statements are used with FDRINSTANT when the DASD is an IBM or other vendor subsystem with the optional FlashCopy feature. FDRINSTANT-for-FlashCopy contains details of its use. However, the volume backup consists of two steps, a FCOPY step (that creates the backup), and a DUMP step (that transfers this backup to long term storage). Specify all of the same operands on the FCOPY and DUMP statements, except for the FCOPY= operand that is added to the DUMP step to invoke FDRINSTANT.

DUMP statement operands

Specifies the type of dump to be performed. It is required.

An incremental backup of all the volumes selected. ABR examines the update flag set by the operating system. Any data set that has been updated or created since the last Volume Backup is dumped, as well as any data set for which backup has been requested through the backup remote queue or by a SELECT statement. This function creates a new cycle within the current generation. For more information, see Generations and Cycles in Overview-of-FDRABR-Volume-Backups.

ABR automatically determines whether a full volume or incremental backup. ABR compares the number of incremental backups taken with AUTOUPD=YES (“auto cycles”) in effect with the maximum number of cycles specified in the ABR Model DSCB on the volume. When the number of auto cycles exceeds the cycle limit, a TYPE=FDR full volume dump is taken. The default maximum cycles before a full volume backup is forced is 10, but can be changed by program FDRABRM or the ABR ISPF Dialogs.

DSF

A manual backup of only the data sets specified by SELECT statements or the DD=ALL option.

A full volume backup of all the volumes selected. This begins a new generation of backups for those DASD volumes.

Specifies that ABR does not increment the auto cycle count for this execution. This is useful if this is a special run or a run outside of auto control. May be specified with TYPE=ABR, DSF, or AUTO.

Specifies that this incremental backup counts for TYPE=AUTO operations.

Default: YES.

Specifies how many buffers are used for dumping each DASD volume. Each buffer holds one DASD volume track. The buffers acquired are divided into two sets in order to overlap input and output I/O operations; each DASD I/O reads DASD volume tracks into one-half of the buffers.

Buffers sufficient to read one cylinder of the input DASD are acquired (usually 16).

nn

The number of buffers specified are acquired.

Default: MAX, unless RTC=YES is specified on the DUMP statement or as a global option.

cloudname

The name of the cloud where the backup is directed.

Default: The backup is created on tape or disk, as indicated by the TAPEx DD statement.

Controls the use of FDR software compression. Values for COMPRESS= are:

The backup file for both copies (TAPEx and TAPExx) is compressed.

Only the backup on TAPEx DD statements are compressed.

Only the backup on TAPExx DD statements are compressed.

See Memory Requirements in Processing-Options-and-Requirements for the additional storage required by COMPRESS=.

Default: Backups are not compressed.

cloudcontainer

The name of the container in the cloud where the backup is stored. The name must start with FDR.. If the specified or defaulted container name does not exist, it is created automatically, provided that the FDRTCTSR started task is running (See Installation in FDRTCT-Transparent-Cloud-Tiering. The name may be up to 128 characters long. If the name does not fit on one line, then break it any point and code CONTAINER= on subsequent lines with the next part of the name. Example:

Default: FDR.ABR.BACKUP.

Swaps the copy numbers in the ABR backup data set names created on the TAPEx and TAPExx DD statements; TAPEx is created with a copy number of “2”; if TAPExx is also present, it is created with a copy number of “1” (see Tape Format and Naming Conventions in Introduction-to-FDRABR-Archiving-and-Superscratch for the backup data set naming conventions including the copy number). If only TAPEx is present, only COPY2 is created. If you send COPY2 off site, this can be useful when you wish to create only an off site backup (no COPY1 for on site recovery).

DATA=

All allocated tracks of all selected data sets are backed up. You may need to specify DATA=ALL if the data sets to be backed up include JES2 spool/CHKPT data sets or CICS sequential journal data sets.

Only the used portion of Physical Sequential (PS) and PO (partitioned, PDS) data sets are backed up. On most volumes, this makes the dump run faster.

Default: ALL for full-volume backups. USED for incremental (data set) backups.

Specifies that ABR does not check the expiration date of the most recent full-volume dump.

Default: ABR forces a full volume backup if the most recent full volume backup of the DASD being processed has reached its expiration date, as recorded in the ABR Model DSCB on the volume.

DSNENQ=

Specifies whether a SYSDSN enqueue is issued for each selected data set on a volume during the backup of the volume. See Data Set Enqueue Option in Processing-Options-and-Requirements for more details.

The options for DSNENQ= are:

Enqueue the data sets. If an enqueue fails, ask the operator what to do.

No data set enqueue is issued.

Do not enqueue the data sets, but test to see if they are enqueued to another task.

Enqueue the data sets. This is the most frequently used option.

Default: NONE. DSNENQ=NONE is forced in a DUMP step using FDRINSTANT, since it is dumping copies of the original data sets.

Used when the FDR e-mail notification facility has been invoked by including an FDREMAIL DD statement in the FDR execution JCL.

E-mail notifications are sent from successful FDR operations as well as failures.

Default: E-mail notifications are sent only for FDR failures.

Specifies whether a SYSVTOC enqueue is issued on the VTOC of each DASD volume while data sets from it are being backed up. See VTOC Enqueue Option in Processing-Options-and-Requirements for more details.

The VTOC is not enqueued or reserved during the backup.

The VTOC of each DASD volume is enqueued during its backup. This enqueue may be effective only on the system where the backup is executing; other systems may still be able to update the VTOC.

In addition to the enqueue, a hardware reserve is issued on each DASD volume during its backup.

Default: ON, except that it is reserve for a SNAP, CONSNAP, PSPLIT, CONPSPLIT, FCOPY, or CONFCOPY statement (an FDRINSTANT point-in-time backup).

If the DSNENQ= operand is used to request data set enqueues, an enqueue failure (in-use data set) is not considered an error (see Step Termination in Processing-Options-and-Requirements). Use ENQERR=NO if you want messages about active data sets but want the step to terminate normally.

Default: A DSNENQ failure is considered an error and causes a condition code or abend at step termination. This is to call attention to the error.

Specifies processing if the DSNENQ= option finds that a data set is in use (enqueued):

Do not backup an active data set. This is ignored for a full-volume backup.

Backup a data set even if it is active (a warning message is still produced).

Default: PROCESS.

If RTC=YES is in effect, then page-fix the disk and tape I/O buffers in real storage for the duration of the DUMP operation, and pass real channel programs to the system instead of virtual channel programs. This saves considerable CPU time that the system would otherwise consume for fixing and unfixing pages at the beginning and end of each I/O operation, and for translating the channel programs from virtual to real. EXCPVR=YES may reduce elapsed time by 5 to 20 percent and may reduce CPU time and CPU service units by 40 to 60 percent.

If RTC=YES is in effect, then pass virtual channel programs to the system, and allow the system to fix and unfix the pages of the I/O buffers at the beginning and end of each I/O operation.

If RTC=YES is not in effect, then EXCPVR= is ignored.

Default: YES.

This operand is used only if you are licensed for FDRINSTANT and only if the DASD being backed up is in a DASD subsystem with the FlashCopy feature. Possible values are:

This operand is specified on an ABR FCOPY or CONFCOPY statement to copy an online volume to an offline target volume, creating a persistent point-in-time Incremental FlashCopy volume image. The use of FCOPY=INCR produces a persistent relationship, which is retained after ABR moves the FlashCopy image to tape by coding FCOPY=(USE) on the DUMP to tape step.

This operand is specified on a DUMP statement following a step that executed an ABR FCOPY or CONFCOPY statement to copy an online volume to an offline target volume creating a frozen point-in-time volume image to move the point-in-time backup from the FlashCopy image to tape.

Same as FCOPY=USE but at the end of moving each FlashCopy image to tape, ABR re-releases the FlashCopy session so that it is no longer maintaining the point-in-time image.

Please read FDRINSTANT-for-FlashCopy for complete documentation on FDRINSTANT and FlashCopy.

Specifies the format of the sequential backup file.

The backup is created using a maximum block size of 56K. A block contains the image of one or more tracks from the input DASD.

The backup is created using a maximum block size of 32K. For blocks that would be more than 32K, they are written as two blocks of 32K or less. However, FORMAT=SPLIT causes use of a DASD I/O technique that is less efficient than that used by FORMAT=NEW, which impacts backup performance.

Default: FORMAT=NEW if all (TAPE1/TAPE11) backups to tape; FORMAT=SPLIT if any (TAPE1/TAPE11) backups to DASD.

Invokes special processing when Hierarchical File System (HFS) data sets are backed up. HFS=QUIESCE and ZFS=QUIESCE imply DSNENQ=USE so it first attempts to get a SYSDSN enqueue on the file. If the enqueue fails, it probably means that the file system is mounted to UNIX System Services (USS), so a “quiesce” call is issued to prevent updates to the data set during the backup. If the quiesce fails and ENQERR=BYPASS was specified, the HFS or zFS data set is not backed up by an incremental backup. See Hierarchical File System (HFS) and zSeries File System (zFS) in FDR-Processing-by-Type-of-Data-Set for details and security requirements.

When used with FDRINSTANT, the HFS=QUIESCE and ZFS=QUIESCE operands appear on the SNAP, CONSNAP, PSPLIT, CONPSPLIT, FCOPY, or CONFCOPY statement, not on the DUMP statement, since the data set only needs to be quiesced while the point-in-time image is being created.

Default: HFS and zFS data sets are not quiesced unless HFSQUIESCE is set to “YES” in the FDR Global Options (see General-Options). If you use the default, unmount the file system before the backup to be sure of getting a usable backup.

nnnnnnn

Specifies the size, in bytes, of the table used to the store the VSAM cluster and component names while matching them with VTOC DSCBs. Specifying ICFCORE= increases the backup region requirement by the value specified. The default is large enough for most volumes.

Used with DUMP TYPE=AUTO only. Specifies the maximum number volumes for which full volume dumps can be forced by TYPE=AUTO within this execution. Incremental backups continue to be taken for any additional volumes, even if they have exceeded their auto cycle limit, unless full-volumes are forced by the last full-volume expiration date or maximum cycle number (63).

Default: A full-volume backup is forced for all volumes exceeding the auto cycle limit.

nnnnn

Enables ABR to accept additional SELECT, EXCLUDE, and MOUNT statements during this execution. You can specify values up to 65535, but values over 100 increase the region required by ABR.

Default: Default is 100 SELECT, EXCLUDE, and MOUNT statements.

nnnn

Specifies the maximum number of DASD volume serials that ABR can process in this execution. ABR builds its volume list from DISKxxxx DD statements and/or online volumes if ONLINE, ONLVOL, or MOUNT is coded. Once this limit is reached, additional volumes are ignored.

Default: 256 volumes, unless overridden by the MAXONLINE option in the FDR Global Options.

nnnn

Specifies the number of tape or DASD errors (1 to 9999) that, if reached, cause the operation to abend. Each error is indicated by a message and possible mini-dump.

Default: 20, except when the output is a tape where MAXERR=1 is forced.

nnnnn

Specifies the maximum file number ABR creates on tape (1 to 65534). When the maximum file number is exceeded, ABR starts a new tape using file sequence number 1. A MAXFILE= over 255 may be appropriate when you are outputting to high-capacity tapes.

Default: 255, unless overridden in the FDR Global Options (see MAXFILES).

nn

Specifies that ABR is to dump an offline target image of the volume created by FDRINSTANT taken “nn” backups ago. “1” specifies the backup taken prior to the current backup for this volume, “2” the next oldest, and so on. If not specified (or 0) the most current backup is dumped.

If these operands are omitted, ABR only processes volumes specified by DISKxxxx DD statements or ABR MOUNT statements.

Specifies that ABR is to process every volume that is online to the system; if there are more than 255 online volumes, you need to specify MAXDD= to increase that limit (See MAXDD= in Full-Volume-RESTORE-Statement).

Specifies that ABR is to scan all SELECT statements for the operands VOL=, VOLG=, or CATDSN= (for volume selected from the catalog). These volumes, if online, are appended to the ABR volume list.

If ABR finds that the user specified EXCLUDE statements with ALLDSN and VOL= or VOLG=, these volumes are not included in the online list unless a DISKxxxx DD statement is present for this volume. This is a way of excluding certain volumes, for example, EXCLUDE ALLDSN,VOLG=WORK.

This operand is used only if you are licensed for FDRINSTANT and only if the DASD being backed up is in an Hitachi Vantara DASD subsystem with the ShadowImage option. It is specified on a DUMP statement following a step that executed an ABR PSPLIT or CONPSPLIT statement to split a ShadowImage copy from its online volume, creating a frozen point-in-time volume image. Possible values are:

Move the point-in-time backup from the ShadowImage copy to tape.

Same as PPRC=USE but at the end of moving each ShadowImage copy to tape, ABR re-establishes the ShadowImage copy so that it is again mirroring the online volume.

Please read FDRINSTANT-for-Hitachi-ShadowImage for complete documentation on FDRINSTANT and ShadowImage.

PRINT=

Requests that ABR print the names of all data sets selected for backup.

Specifies that ABR is to use the PRINT VTOC format of program FDRABRP (see FDRABRP-VTOC-Report) for each data set that was dumped.

Specifies that ABR is to simply print the data set names.

Specifies that ABR is to invoke FDREPORT to process the list of data sets backed up from each DASD volume. FDREPORT writes a data file, in FDREPORT compressed data format, to the $RPTSUT2 DD statement specified in the ABR JCL. This data file contains basic description information about the data sets plus the backup information necessary to restore the data sets. This data file can be used as input to FDREPORT to generate reports on the data sets, to query on data set backups, and to generate ABR SELECT statements for input to an ABR restore. An example can be found in Build the Database and Restoring Data Sets in Disaster-Recovery; details can be found in the FDREPORT HELP.

Default: DSN, except for full-volume backups where data set names are not printed by default. PRINT=ABR is the default for a SIM statement (simulation).

REMOTEINSTANT=

Remote FlashCopy is invoked to establish a FlashCopy relationship between the Remote Metro Mirror/PPRC secondary unit and a remote tertiary device. The Remote Tertiary device is specified by using the FLASHUNIT= parameter on the MOUNT statement.

vMetro Mirror / PPRC secondary units must be in duplex status and tertiary remote units must be in simplex state.

vIf the source volume is not the primary volume in a duplexed Metro Mirror relationship, the REMOTEINSTANT= operand is ignored.

vREMOTEINSTANT=INBAND is supported in FlashCopy / Metro Mirror environments only.

An attempt is made to use Preserve Mirror FlashCopy. If the attempt is not successful, the operation continues and REMOTEINSTANT= is ignored. FlashCopy is used and the metro mirror relationship may enter a “pending” state.

An attempt is made to use Preserve Mirror FlashCopy. If the attempt is not successful, the operation is terminated.

RETPD=nnnn

Specifies the number of days (1 to 9999) that COPY1 (TAPEx) backups are kept. ABR calculates an expiration date from this value. If RETPD2= is omitted, this same expiration applies to all COPY2 backups created in the same step.

RETPD2=nnnn

Specifies the number of days (1 to 9999) that COPY2 (TAPExx) backups are kept. ABR calculates an expiration date from this value.

See Backup Retention and Tape Management in Overview-of-FDRABR-Volume-Backups for a discussion of tape retention.

Default: For a full-volume backup (TYPE=FDR) is the default stored in the ABR Model DSCB on this volume, set by the ABR utility FDRABRM or the FDR Volume Initialization panel (A.I.8); separate defaults for RETPD= and RETPD2= are stored in the model. For incremental backups, the default is the expiration date of the most recent COPY1 or COPY2 full-volume backup as recorded in the ABR Model DSCB. These defaults can be overridden by RETPD= or EXPDT= on individual TAPE DD statements.

Use READ TRACK CCWs to read DASD data tracks. RTC=YES also causes:

vUp to one cylinder of DASD data is read at a time.

vFDR buffers are moved above the 16MB line (about 2MB per concurrent backup), allowing more concurrent backups to be run in one step.

vThe elapsed time of FDR backups when the backup data set is itself on DASD is significantly improved.

vThe elapsed time of FDR backups on fast tapes and DASD, especially on FICON channels, may be improved.

Use other techniques to read DASD data tracks.

It can also be specified as READTRACKCCW=.

Default: NO, unless RTC=YES is specified as a global option.

If ABR finds that a SELECT or EXCLUDE statement was never referenced (no data set on any input DASD was selected by the statement):

A condition code or abend is not to be issued at step termination. You might use SELTERR=NO when you expect some unmatched SELECT and EXCLUDE statements, perhaps because some data sets may not exist.

A condition code or abend is issued at step termination to call attention to a possible control statement error.

Default: YES, unless overridden in the FDR Global Options (see SELTERR in General-Options).

ABR bypasses selected volumes based only on the presence or absence of the ABR Model DSCB, ignoring the SMS storage group attribute.

ABR does not process SMS-managed volumes unless their associated storage group has the attribute AUTO-DUMP=YES and AUTO-BACKUP=YES. (Volumes with AUTO-DUMP=YES but AUTO-BACKUP=NO are selected for TYPE=FDR runs only, and bypassed on all incremental backups). The SMS-managed volumes must still have a proper ABR Model DSCB.

Default: YES.

ABR does not exclude data sets from SMS-managed volumes based on the attributes of their SMS management class.

Data sets on SMS-managed volumes are excluded from data set backups if their associated SMS management class has the attribute “ADMIN OR USER COMMAND BACKUP=NONE” (for all data set backups) or “AUTO-BACKUP=NO” (for TYPE=ABR/AUTO). If not excluded by the above, data sets are selected by normal ABR rules (see “Data Set Selection Rules” in Section 52.2) or by SELECT statements. See System-Managed-Storage-SMS for more details on SMS processing.

Default: NO.

(For SNAP, CONSNAP, PSPLIT, CONPSPLIT, FCOPY, and CONFCOPY statements only) on an SMS-managed volume, if ABR discovers certain errors in a VVDS (such as message FDR152 REASON=F for a VVR or NVR that is missing from the VVDS), it issues message FDR152 and fails the operation. If you want the operation to complete despite the error, specify the SMSPROT=NONE operand; the message is still issued but the operation completes. The description of message FDR152 shows which reason codes are covered.

This operand is used only if you are licensed for FDRINSTANT and only if the DASD volume being backed up is a DASD subsystem with the SnapShot option or in an EMC Symmetrix subsystem with the TimeFinder/Clone or TimeFinder/Snap options. It is specified on a DUMP statement following a step that executed an ABR SNAP or CONSNAP statement to snap an online volume to an offline target volume, creating a frozen point-in-time volume image. Possible values are:

Move the point-in-time backup from the SnapShot target volume to tape.

Same as SNAP=USE, but at the end of backing up each snapped volume, ABR issues a request to delete all the storage assigned to the snapped copy. For EMC Symmetrix, the request terminates the Snap session.

Same as SNAP=USE, but at the end of moving each snapped volume to tape, ABR re-establishes the snapped unit so that it is again mirroring the online volume. This is mainly used for EMC Symmetrix volumes.

Please read FDRINSTANT-for-EMC-TimeFinder for FDRINSTANT and Symmetrix TimeFinder.

ABR does not reset the update/change flag in the Format 1 DSCBs of data sets it backs up in this execution. Since the update flag remains set, the data sets are included in the next backup job even if they are not updated again.

UPDATEFLAG=NOCHANGE is useful when you are testing the operation of ABR compared to another DASD management product, such as IBM's DFSMShsm. If you execute ABR Volume Backups first, followed by DFSMShsm backups, ABR backs up all updated data sets and leave the update flag on. Then DFSMShsm backs up the same data sets and turn the update flag off. This allows each ABR and DFSMShsm backup to select the same data sets and do equivalent work so that you can compare elapsed time and resources used by both.

Supported only on SNAP, CONSNAP, PSPLIT, CONPSPLIT, FCOPY, and CONFCOPY statements for FDRINSTANT.

ABR does not verify the volume serial number of the FDRINSTANT offline target DASD. Any DASD volume of the proper type and size can be used as the target.

ABR verifies that the FDRINSTANT offline target DASD has the same volume serial as the online source DASD volume. This is true if the last use of the target was for an FDRINSTANT backup of this source volume, or if you have used ICKDSF to initialize the target volume. You may need to omit VERIFYVOLSER=YES on the first FDRINSTANT use of the target DASD volume since the volume serial number may not match. VERIFYVOLSER=YES is used to verify that you are not accidentally overlaying a target volume used with another source volume.

Default: Default is NO.

VOLSORT=

Volumes are processed in the order that they are found during a scan of the system UCBs, which is usually (but not always) in z/OS device address order.

If you have more than one TAPEx DD statement in this ABR step, ABR sorts the volumes to be backed up by the last digit of their z/OS device address, to attempt to balance channel and control unit utilization during concurrent backups. In other words, all volumes whose z/OS address are xxx0 are processed first, then xxx1, and so on.

Default: YES, except that NO is forced if you have only one TAPEx DD statement.

VOLSORT= only applies to volumes selected by the ONLINE or ONLVOL operands or MOUNT statements. It does not apply to volumes selected by DISKxxxx DD statements that are always processed first, in the order the DD statements appear in the JCL.

Invoke zEDC (zEnterprise Data Compression) for both compression and decompression if the CPU and the operating system support it.

Use the zEDC hardware compression/decompression feature:

Do not use the zEDC hardware compression/decompression feature.

Default: NO.