QUICKCOPY—Invoke CA Quick Copy

The QUICKCOPY keyword invokes pqc to create backup image copies. This keyword defines the copy type and specifies image copy parameters, such as the number of copies to be made, whether to update SYSIBM.SYSCOPY, the ddname or template for the allocation, the name of an exit module, and the type of copy. You can create up to eight backup copies at once and can specify whether the copy is for local or remote (recovery) sites and whether the copy is a primary or backup copy. Repeat the parameters for each copy. If you do not specify the parameters and ddname for the backup image copy in the syntax, the image copy is allocated dynamically using the settings in the PQC parmlib member.
cafrdb219
The QUICKCOPY keyword invokes
CA Quick Copy for DB2 for z/OS
to create backup image copies. This keyword defines the copy type and specifies image copy parameters, such as the number of copies to be made, whether to update SYSIBM.SYSCOPY, the ddname or template for the allocation, the name of an exit module, and the type of copy. You can create up to eight backup copies at once and can specify whether the copy is for local or remote (recovery) sites and whether the copy is a primary or backup copy. Repeat the parameters for each copy. If you do not specify the parameters and ddname for the backup image copy in the syntax, the image copy is allocated dynamically using the settings in the PQC parmlib member.
When you include QUICKCOPY in a job, the object whose name most recently precedes the QUICKCOPY option is copied. To recover and copy multiple objects in one step, include the QUICKCOPY statement after each object clause (TABLESPACE
tsname
or INDEXSPACE
isname
).
QUICKCOPY is
not
valid with the REBUILD control statement.
For more information about how to define copy types, see the
CA Quick Copy for DB2 for z/OS
documentation. For more information about backup copy types, see the
IBM
DB2 Administration Guide, Volume II.
Syntax
:
QUICKCOPY [COPY
nn
][([
Y
|N][,
ddname
|
templatename
][,
exitname
][,
icbackup
][,
devtype
])]
  • COPY
    nn
    Specifies the number of the copy.
    Limits:
    01 - 08
    Example:
    Specify COPY01 to make copy#1, specify COPY02 to make copy #2, and so on.
  • Y|N
    Specifies whether to register the copy in the SYSIBM.SYSCOPY. If you specify N, the copy is not registered.
    Default:
    Y
  • ddname
    |
    templatename
    Defines the ddname to use for the image copy data sets. If you are using TEMPLATE control statements, this parameter specifies the template name that contains the dynamic allocation parameters for the data sets.
    A ddname is required when more than one image copy data set are to be generated for the given object, or to identify the template to be used.
    If you do not specify the ddname in the syntax, the image copy is allocated dynamically using the settings in the PQC parmlib member.
    Default:
    SYSCP
    n
    01 (
    n
    identifies the copy number)
    Example:
    SYSCP101 is the DD name referenced by the first task for the first copy (COPY01).
  • exitname
    Defines the name of the user exit.
  • icbackup
    Specifies the type of copy. You can specify whether the copy is for local or remote (recovery) sites and if the copy is a primary or backup copy. The type of image copy is stored in the ICBACKUP column of SYSIBM.SYSCOPY.
    The following options are valid only for sites where the LOCALSITE option of DB2 is installed:
    • LP—Local primary (this is the default for COPY01)
    • LB—Local backup (this is the default for all copies except COPY01)
    The following options are valid only for sites where the RECOVERYSITE option of DB2 is installed:
    • RP—Recovery primary
    • RB—Recovery backup
  • devtype
    Defines the device type. This value updates the DEVTYPE column of the SYSIBM.SYSCOPY row for the image copy. If you do not define a device type, DEVTYPE is updated with the generic volume ID, such as 3420.
The default for QUICKCOPY is COPY01(Y,SYSCOPY) for a single copy and COPY01(Y,SYSCP101) for multiple copies.
Examples: QUICKCOPY
  • This example recovers two tablespaces and takes a backup image copy of each tablespace:
    //SYSIN    DD    * RECOVER TABLESPACE TDKATR.TSDEPT          QUICKCOPY COPY01(Y,SYSCP101,,LP)         TABLESPACE TDKATR.TSEMP93         QUICKCOPY COPY01(Y,EMPCP101,,LP)
  • This example recovers two tablespaces, but copies only tablespace TSEMP93:
    //SYSIN   DD    * RECOVER TABLESPACE TDKATR.TSDEPT          TABLESPACE TDKATR.TSEMP93         QUICKCOPY COPY01(Y,EMPCP101,,LP)
  • This example recovers a tablespace and an indexspace, and takes and dynamically allocates a backup image copy of each object using the PQC parmlib member settings:
    //SYSIN    DD    * RECOVER TABLESPACE TDKATR.TSDEPT         QUICKCOPY         INDEXSPACE TDKATR.XSDEPT93         QUICKCOPY
  • This example recovers a tablespace and takes a backup image copy using the dynamic allocation settings that are specified in the PQC parmlib member:
    //SYSIN   DD    * RECOVER TABLESPACE TDKATR.TSDEPT         QUICKCOPY COPY01(Y,,,LP)
Use of QUICKCOPY with Dynamically Allocated Data Sets
You can specify QUICKCOPY take an image copy while recovering multiple objects by using the following commands with dynamically allocated data sets:
  • RECOVER LIST
  • RECOVER OBJ-LIST
    RECOVER LIST and RECOVER OBJ-LIST is only valid with dynamic allocation.
  • RECOVER TABLESPACE
  • RECOVER INDEX
  • RECOVER INDEXSPACE
  • RECOVER DATABASE
You can use either of the following methods to dynamically allocate the image copy data sets:
  • TEMPLATE
    Defined in the SYSIN, or in a data set whose ddname is specified in the OPTIONS control statement.
    For more information about TEMPLATE and OPTIONS control statements, see the
    CA Quick Copy for DB2 for z/OS
    documentation and the IBM
    DB2 Reference Guide
    .
  • PQC Model
    Exists in the PQC parmlib member.
    For more information about using models for dynamic allocation of copy data sets, see the
    CA Quick Copy for DB2 for z/OS
    documentation.
CA Quick Copy for DB2 for z/OS
uses either all templates or all PQC models for dynamic allocation. You cannot use templates and PQC models together in the same job step.
CA Quick Copy for DB2 for z/OS
determines which method to use by checking whether a template has been defined for a job step. If any templates have been defined and are available to a job step,
CA Quick Copy for DB2 for z/OS
uses templates. In this case, a template must exist for each name that is referenced in the COPY
nn
parameter of the QUICKCOPY keyword. If a template does not exist, the recover terminates with an error message.
Examples: Use Templates to Dynamically Allocate Image Copy Data Sets
  • The following example uses a list to identify the objects to recover. Templates are used to dynamically allocate the image copy data sets. The templates are defined in the SYSIN and are available to QUICKCOPY:
    TEMPLATE TMPACT01  DSN  'PQC.RCVRL32.&DB..&TS..&LR.&PB.&PA..P&TIME.'      UNIT SYSDA                                                        TEMPLATE TMPACT02  DSN  'PQC.RCVRL32.&DB..&TS..&LR.&PB.&PA..B&TIME.'      UNIT SYSDA                                                        LISTDEF LIST32ALL   INCLUDE TABLESPACES DATABASE PQCDB32   RECOVER     LIST LIST32ALL                                  QUICKCOPY COPY01(Y,TMPACT01,,LP)                        COPY02(Y,TMPACT02,,LB)             INLINE-COPY YES             SORTLOG YES                  ALLMSGS
  • The following example uses templates to recover two tablespaces and make a backup image copy of each tablespace. Templates are used to dynamically allocate the image copy data sets:
    //SYSIN   DD    * TEMPLATE ICTEMPLT      DSN 'TSDUMP.&DB..&TS..&LR.&PB.&PA.(+1)'   RECOVER TABLESPACE TDKATR.TSDEPT         QUICKCOPY COPY01(Y,ICTEMPLT,,LP)         TABLESPACE TDKATR.TSEMP93         QUICKCOPY COPY01(Y,ICTEMPLT,,LP)