FDR COPY Statement

COPY statement syntax

COPY


,CONFMESS=NO|YES


,CPYVOLID=NO|YES


,DATA=ALL|USED


,DSNENQ=HAVE|NONE|TEST|USE



,ENQ=OFF|ON|RESERVE


,HFS=QUIESCE


,MAXERR=20|nnnn


,PROT=NONE


,SMSPROT=ALL|NONE


,VOLRESET=NO|YES

COPY statement

The COPY statement requests a full-volume DASD-to-DASD copy. It is required if a copy is to be performed and must be the first and only statement input. Each DASD volume specified by a DISKx DD statement is copied to the DASD volume specified by the matching TAPEx DD statement; TAPEx must point to the same type of DASD (for example, 3390) as DISKx. If a TAPExx DD statement is also specified, FDR also creates a backup of DISKx.

A COPY is essentially a DUMP and a RESTORE in separate subtasks under FDR, so almost all options documented for DUMP and RESTORE in the preceding sections apply. The backup data created by the DUMP subtask is passed directly to the RESTORE subtask. No backup data set is created unless you provide a TAPExx DD statement to create a backup as well as doing the copy.

Important

A SYSPRINx DD statement is required matching DISKx/TAPEx pair. This print data set records the messages from the dump of the DISKx volume. The SYSPRINT data set records the messages from the restore to the TAPEx volume.

An FDR COPY operation can copy from a DASD volume to a larger capacity volume of the same DASD type (for example, 3390-3 to 3390-9). If you want to copy from a larger DASD (such as 3390-9) to a smaller device (3390-3) it is usually more convenient to use COMPAKTOR (COMPAKTOR-CPK-DASD-Volume-Reorganization) or FDRCOPY (FDRCOPY-Copy-or-Move-Data-Sets). However, if you prefer to use COPY TYPE=FDR and no data sets are allocated on tracks beyond the end of the smaller DASD, you can do so by specifying PROT=NONE.

Warning

It is best that the target volume be placed offline to all systems other than the system where the copy is to be run. If you do not, the other systems may access the original VTOC of the restored volume and access or delete the wrong data.

COPY statement operands

TYPE=FDR

Indicates that the entire volume is to be copied. It is required.

CONFMESS=

NO

Begin the copy immediately.

YES

The operator must reply to a console WTOR for message FDRW01 before the copy begins.

Default: CONFMESS=YES.

CPYVOLID=

NO

The volume serial of the output DASD is retained.

YES

Volume serial of the output DASD is replaced with the volume serial of the input DASD. The output volume is placed offline at the end of the copy.

See VOLRESET= for details on its interaction with CPYVOLID=.

Default: CPYVOLID=NO, unless the volume being copied was SMS-managed, when CPYVOLID=YES is forced.

DATA=

ALL

All allocated tracks of all data sets are copied.

USED

Only the used portion of Physical Sequential (PS) and PO (partitioned, PDS) data sets are copied. On almost all volumes, this makes the copy run faster.

Default: DATA=ALL.

DSNENQ=

Specifies whether a SYSDSN enqueue should be issued for each of the data sets on an input volume during the copy of the volume. 

The options for DSNENQ= are:

HAVE

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

NONE

No data set enqueue is issued.

TEST

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

USE

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

Default: DSNENQ=NONE

Tip

Use DSNENQ=USE if you want to prevent other tasks from using the data sets until the copy is complete.

EMSG=

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

OK

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

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

ENQ=

Specifies whether a SYSVTOC enqueue or RESERVE should be issued on the VTOC of each input and output DASD volume during the copy. 

OFF

The VTOC is not enqueued or reserved during the copy.

ON

An enqueue, but not a reserve, is issued on both the input and output volumes during the copy. This enqueue may be effective only on the system where the backup is executing; other systems may still be able to update the VTOC.

RESERVE

An enqueue and a hardware reserve is issued on both the input and output volumes during the copy. On the system where FDR is executing, an enqueue for (SYSVTOC,volser) is done, but other systems are unable to read or write any data on the volume.

Default: No enqueue or reserve on the input volume, and a reserve on the output volume.

HFS=

QUIESCE

Invokes special processing when Hierarchical File System (HFS) data sets are copied. HFS=QUIESCE implies DSNENQ=USE so it 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. 

Important

HFS=QUIESCE implies DSNENQ=USE (see DSNENQ=) for all data sets being copied, not just HFS data sets.

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

MAXERR=

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 (i.e. TAPExx is used), where MAXERR=1 is forced.

PROT=

NONE

FDR can only copy to volumes of the same type as the dumped DASD and normally requires that the output DASD have the same or larger capacity (number of cylinders) as the input DASD, for example, 3390-3 to 3390-3 or 3390-9. PROT=NONE allows FDR to copy to a smaller DASD of the same type, for example, 3390-9 to 3390-3. Do not specify PROT=NONE unless you need this function since it also suppresses other validity checks.

Warning

Since FDR always places data tracks in their original locations, copy to a smaller DASD fails if the larger DASD had data sets allocated beyond the bounds of the smaller DASD. Use COMPAKTOR to convert such DASD volumes.

Default: All validity checks are done.

SMSPROT=

ALL

Enforces several rules when SMS-managed volumes are involved: SMS-managed volumes can only be copied to SMS-managed volumes, and non-SMS volumes only to non-SMS volumes. CPYVOLID=YES is forced when an SMS-managed volume is copied.

NONE

Allows the copy of SMS-managed volumes to non-SMS volumes, and vice versa. Also allows the copy of SMS-managed volumes to new volume serial numbers if CPYVOLID=NO is specified.

Warning

SMSPROT=NONE should be used with caution. If used, it may be necessary to restart SMS or vary the volume offline and back online before the new volume location is recognized. See System-Managed-Storage-SMS for more details on restoring and moving SMS-managed volumes.

Default: SMSPROT=ALL

VOLRESET=

YES

If CPYVOLID=NO is specified or defaulted, and the volume serial of the output DASD is different from that of the original DASD on the backup, the volume serials that are part of the data set names of the VTOC Index (SYS1.VTOCIX.volser), the VVDS (SYS1.VVDS.Vvolser) and the ABR Model DSCB (usually FDRABR.Vvolser) are checked to see if they match the input volume serial. If so, they are renamed to match the volume serial number of the output DASD. Also, the DSCB field DS1DSSN (data set serial number, usually the volume serial number of the first or only volume of the data set) for every data set on the volume is changed to the new volume serial number if the existing value matched the original volume serial number.

Regardless of the value of CPYVOLID=, the ABR Model DSCB on the copied volume (if it exists) sets the cycle number to 63 to force the next ABR backup to be a full-volume backup and increment the generation number.

NO

Do not do any of the processing listed above for VOLRESET=YES. All data sets are copied with the names they have on the backup and the ABR Model DSCB is restored unmodified.

Default: VOLRESET=NO

Important

  • wIf you intend to copy the backup to a new permanent volume serial, use CPYVOLID=NO with VOLRESET=YES. Note that data sets on the volume are not recataloged to the new volume serial, but you can catalog them using the IDCAMS “DEFINE” command (note that VSAM must be recataloged with DEFINE CLUSTER RECATALOG and SMS-managed, non-VSAM data sets must be recataloged using DEFINE NONVSAM RECATALOG); see the IBM IDCAMS manual for syntax details.
  • wIf you intend to restore the backup to a temporary volume serial but later relabel it back to the original volume serial (from the backup), use CPYVOLID=NO with VOLRESET=NO.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*