FDRAPPL DUMP Statement

DUMP statement

The DUMP TYPE=APPL statement invokes Application Backup. Only one DUMP statement is allowed per execution of ABR.

SIM statement

If SIM is specified, FDRAPPL performs the Application Backup in simulation mode. The TAPE1 DD statement must specify DD DUMMY, and no Application Control File is created or written. FDRAPPL produces a report in PRINT VTOC format showing the data sets that would be backed up. The main purpose of simulation is to check that the right data sets are being selected.

DUMP statement syntax

DUMP statement rarely used operands

There are some additional operands that can be specified on a DUMP TYPE=APPL statement, but they are rarely used with FDRAPPL. Their definitions can be found in Archive-DUMP-and-SCRATCH-Statements. They are:

For DUMP TYPE=APPL, MAXBTRKS= defaults to 65536, which disables the feature.

DUMP statement operands

Controls whether the ENQ on QNAME=FDRABR, RNAME=ABRvvvvvv is issued to serialize the operation on a given volume so that no more than one ABR operation of any type will process a given volume at a time.

Normal FDRAPPL DUMP processing does not make changes to the volume, so ABRENQ=NO is the default to allow multiple application backups to run on the same volume at the same time. Also, using USERINDEX=YES (the recommendation) causes each Application Backup job to create files with unique names provided that the Application Backups with the same USERINDEX do not run concurrently. Also, ARCB1DSN/ARCB2DSN should be specified to make sure that the backups of the Application Control File have unique names, if there is a chance that Application Backups using the same Application Control File might run at the same time.

However, if the backup files created by Application Backup are being cataloged, and an Application Backup job is processing an input volume at the same time as another Application Backup job or Archive job, and either the USERINDEX=YES option is NOT used, or Application Backups with the same USERINDEX run concurrently, then the two jobs could create duplicate names for the Application Backup files. If duplicate names are created, then only the first occurrence will be cataloged; cataloging of later occurrences will fail. The consequence may be that the restore will not find the backup file (in the case of a backup file that extends to more than 5 tape volumes), or that tapes under catalog control may expire prematurely.

Do not issue the ENQ to serialize the operation.

Issue the ENQ to serialize the operation. When running multiple concurrent APPL backup jobs against the same volume with ABRENQ=YES, also code TIME=1440 for the jobstep to avoid S522 abends.

Default: NO.

FDRAPPL backs up the Application Control File used to record the backups for this Application Backup as the last file on the backup tapes. If the ARCB1DSN= and/or ARCB2DSN= operands are specified, those data set names are used for the tape file name of this backup (on TAPE1 and TAPE11 respectively). If those operands are omitted, then the backup file name is formed by taking the name of the Application Control File itself and changing the index level of ARCHIVE to ARCBKUP (for TAPE1) and ARCBKU2 (for TAPE11).

FDRAPPL does not backup the Application Control File. ARCBACKUP=NO should be specified only when you are using other means to backup and recover the Application Control Files, or when the Application Backup is to be used only for on site recovery and never at a disaster site.

Default: DSF.

Specifies the data set name to be used for the backup of the Application Control File as the last file on the Application Backup tapes. This backup is done automatically unless ARCBACKUP=NO is specified. ARCB1DSN= specifies the tape file name to be used on TAPE1, and ARCB2DSN= on TAPE11. These names may be any valid z/OS data set name, including a GDG relative generation, for example, ARCB1DSN=PAYROLL.APPL.BACKUP(+1)

These data sets are always cataloged internally by FDRAPPL.

Specifies how FDRAPPL handles cataloging of the tape files that it creates.

All the files are cataloged.

No files are cataloged, except for any backup file that exceeds five tape volumes and the backup of the Application Control File (see ARCBACKUP=).

Files are cataloged by the rules used for normal Archive Backups (it catalogs the backup file anytime the volume list changes from the previous file created, which includes the first file created, any file that requires a new output tape, and the first file after a file that requires a new output tape).

Default: NO, except that ARCCAT=ALL is forced if the backup is on DASD or on cloud storage, or EXPDT=99000 (catalog control to some tape management systems) is specified on the TAPEx DD Statement or TAPExx DD Statement.

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.

The backup file for both copies (TAPEx and TAPExx) is to be 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 the HLQ of FDR. If the specified or defaulted container name does not exist, it is created automatically, provided that the FDRTCTSR started task is running (Installation-Checklist). 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.APPLICATION

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).

This operand does not affect the COMPRESS= operand nor the ENCRYPT option (FDRCRYPT-Backup-Encryption); in those operands, COPY1 always refers to the copy created on TAPEx and COPY2 to TAPExx.

DSNENQ=

Specifies whether a SYSDSN enqueue should be issued for each selected data set on a volume during the backup of the volume. See Data Set Enqueue Option in FDRAPPL-Processing-Options-and-Requirements for more details. The options for DSNENQ= are:

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

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.

Default: NONE.

DSNENQ= should not be specified if you have multiple TAPEx DD statements, to DUMP multiple DASD volumes concurrently, and multi-volume data sets may be involved.

If the DSNENQ= operand is used to request data set enqueues, an enqueue failure (in-use data set) will not be considered an error (see Step Termination in FDRAPPL-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.

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.

NO

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.

Invokes special processing when Hierarchical File System (HFS) and zSeries File System (zFS) 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 data set is not backed up. See Hierarchical File System (HFS) and zSeries File System (zFS) in FDR-Processing-by-Type-of-Data-Set  for details and security requirements.

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, you should unmount the file system before the backup to be sure of getting a usable backup.

nnnnn

Enables FDRAPPL to accept additional SELECT and EXCLUDE statements during this execution. You can specify values up to 65535, but values over 100 increase the region required by FDRAPPL. If SELECT CATDSN= is used, an internal SELECT is generated for each data set/volume combination selected from the catalog, so MAXCARDS= may need to be specified if a large number of data sets are selected.

Default: 100 statements.

nnnnn

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

If COPY1=COPY2 is specified, MAXFILE= cannot exceed 255.

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

nnnn

Specifies the number of days (1 to 9999) that COPY1 (TAPEx) backups are kept. FDRAPPL calculates an expiration date from this value.

If RETPD2= is omitted, this same expiration applies to all COPY2 backups created in the same step.

See Backup Retention and Tape Management in Introduction-to-FDRAPPL for a discussion of backup retention.

Default: 365 days, unless overridden by RETPD= or EXPDT= on individual TAPE DD statements.

nnnn

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

If RETPD2= is omitted and RETPD= is specified, the same expiration applies to all COPY2 backups created in the same step.

See Backup Retention and Tape Management in Introduction-to-FDRAPPL for a discussion of backup retention.

Default: 365 days, unless overridden by RETPD= or EXPDT= on individual TAPE DD statements.

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

Up to 1 cylinder of DASD data is read at a time.

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

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

The 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.

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

FDRAPPL records the same backup date and time (in the Application Control File) for every data set backed up in this FDRAPPL step. If you are using a permanent ACF for the application and backups are run more than once per day, this makes it easier to select a particular instance of the backups.

Default: The backup time recorded is the time that the backup started from the volume on which the data set resided. If multiple volumes are processed in the step, the backup time is different for each of them.

If FDRAPPL 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).

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 will sort 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 is xxx0 are processed first, then xxx1, and so on.

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

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.