Image copy options

This topic describes the options that enable image copies during a load job.

    COPY

    The COPY option tells BMC AMI Load  whether to produce a copy of the table space or selected partitions during the load.

    Operands

    NO

    (Default) Tells BMC AMI Load not to make a copy of the table space

    Important

    BMC AMI Load ignores the COPYPEND option.

    If you specify COPY NO, you can specify COPYPEND. For more information, see COPYPEND .

    YES

    BMC AMI Load creates a copy of the table space or partitions, depending on the type of object that you are loading and the value of your other options. BMC AMI Load creates a standard Db2 image copy.

    The unit name and options for the copy destinations are defined by the one of the following methods. The value of the +OVERRIDEOUTPUT parameter determines the method that BMC AMI Load  uses.

    The following considerations apply to the COPY option:

    • You cannot specify COPY if you specify RESUME YES SHRLEVEL CHANGE.
    • You must specify the OUTPUT command, or the XCPYDYNM automation control point must be available to provide the image copy data set name for each image copy.
    • BMC AMI Load  registers all copies with Db2 in the SYSIBM.SYSCOPY table. 
    • BMC AMI Load  ignores any INLINE specification.

    COPYPEND 

    This option is available only if you specify COPY NO.

    The COPYPEND option specifies whether BMC AMI Load  should set the table space to COPY pending status if a copy was not made as part of the load job.

    When COPYPEND is not specified, the +COPYPENDING parameter setting takes effect. For more information, see +COPYPENDING .

    Operands

    YES(Default) Sets COPY pending status
    NODoes not set COPY pending status

    COPYDDN(lp,lb)

    COPYDDN(lp,lb) tells BMC AMI Load  to produce a primary and, optionally, a backup copy to the indicated local copy destinations.

    The first value specifies a local primary (lp) copy; the second value specifies a local backup (lb) copy. If you specify COPYDDN, you must specify at least a local primary copy.

    These values do not specify a DD name; they signify the intention to produce a copy to this destination. The actual unit name and options for the copy destinations are defined by the one of the following methods. The value of the +OVERRIDEOUTPUT parameter determines the method that BMC AMI Load  uses.

    The following considerations apply to COPYDDN:

    • You cannot specify COPYDDN if you specify RESUME YES SHRLEVEL CHANGE.
    • (BMC.DB2.SPE2207) Open link If copy datasets are not defined in the JCL, you must specify the OUTPUT command (for BMC AMI Load), or the XCPYDYNM (dynamic image copy data set allocation) automation control point must be available to provide the image copy data set name for each image copy.
    • (BMC.DB2.SPE2207) Open link BMC AMI Load  supports COPY datasets defined in the JCL when loading a single partition or a non-partitioned table space. 
    • The parentheses are optional if you specify only one destination name (for example, COPYDDN LP1); the parentheses are required if you specify two DD names.
    • COPYDDN specified before the INTO TABLE can have two positional parameters, for example COPYDDN (A,B). COPYDDN coded after the INTO TABLE can have only one positional parameter, for example COPYDDN(A).
    • The following table shows the partitions that BMC AMI Load  copies:

      Command

      Partition copied

      LOAD DATA INDDN SYSREC REPLACE COPYDDN(A) INTO TABLE A.B

      Whole table

      LOAD DATA INDDN SYSREC RESUME YES COPYDDN(A) INTO TABLE A.B

      Only the partitions that are loaded

      LOAD DATA INDDN SYSREC RESUME YES INTO TABLE A.B PART X REPLACE COPYDDN(A)

      Only the partitions that are loaded

      LOAD DATA INDDN SYSREC RESUME YES COPYDDN(A) INTO TABLE A.B PART X REPLACE

      Only the partitions that are loaded

      LOAD DATA INDDN SYSREC INTO TABLE A.B PART X REPLACE COPYDDN(A)

      Only partition X

    RECOVERYDDN(rp,rb)

    RECOVERYDDN(rp,rb) tells BMC AMI Load  to produce a primary and, optionally, a backup copy to the indicated remote copy destinations.

    The first value specifies a remote primary (rp) copy; the second value specifies a remote backup (rb) copy.

    These values do not specify a DD name; they signify the intention to produce a copy to this destination. The actual unit name and options for the copy destinations are defined by one of the following methods. The value of the +OVERRIDEOUTPUT parameter determines the method that BMC AMI Load  uses.

    The following requirements and considerations apply to the RECOVERYDDN option:

    • You cannot specify RECOVERYDDN if you specify RESUME YES SHRLEVEL CHANGE.
    • (BMC.DB2.SPE2207) Open link If copy datasets are not defined in the JCL, you must specify the OUTPUT command (for BMC AMI Load), or the  XCPYDYNM (dynamic image copy data set allocation) automation control point must be available to provide the image copy data set name for each image copy.
    • (BMC.DB2.SPE2207) Open link BMC AMI Load  supports COPY datasets defined in the JCL when loading a single partition or a non-partitioned table space. 
    • The parentheses are optional if you specify only one destination name. The parentheses are required if you specify two DD names.
    Was this page helpful? Yes No Submitting... Thank you

    Comments