COPYDDN

The ddnames correspond to the data sets that receive either an image copy or DSN1COPY-type copy of the table space or partitions that you are loading.

If you specify ddname2 for this option, you must either allocate this data set in your JCL or dynamic allocation must be active for both the primary and backup copy data sets. If you specify ddname2 and dynamic allocation is active for only the primary copy data set, LOADPLUS terminates because it expects a second copy data set.

If you are registering the copies, ddname1 will be the Db2 local primary and ddname2 will be the local backup. For information about using these data sets in LOADPLUS, see Copy-data-sets-in-LOADPLUS.

If you use this option to override the default name in the installation options module, you must also change the name in your JCL.

When LOADPLUS invokes DSNUTILB (and you specify COPY YES), LOADPLUS passes this option to the IBM Db2 LOAD utility for processing.

Restriction

This option does not apply to LOB or XML copy data sets.

Partition-level copies

If you are making partition-level copies, specify only the ddname prefix (no nn) in this option. If you are dynamically allocating copy data sets (and you specify COPYLVL PART), LOADPLUS appends the partition number to the ddname prefix. Specify a prefix that results in eight characters or less after LOADPLUS appends the highest partition number. For more information, see Specifying ddname prefixes.

If you are not dynamically allocating copy data sets, the ddname that you specify in the JCL must have the partition number nn appended to this prefix. The length of nn can be from one through seven characters, depending on the length of the prefix. The length of the ddname with the prefix must be eight characters or less. For example, if you are loading partition 15, you could specify ddname1 as BCOPY, and specify BCOPY015 in your JCL.

If you are loading a partition-by-growth table space, ensure that the ddname prefix that you specify allows for the number of partitions specified for MAXPARTITIONS in your table space definition.

Dynamic allocation

If dynamic allocation is active and you specify more than one ddname prefix for dynamic allocation, the prefix for each ddname must be different enough for LOADPLUS to differentiate one prefix from another. To be different enough, if these prefixes are different only because one prefix has additional trailing bytes, then these trailing bytes must contain at least one nonnumeric byte. For example, the first set of prefixes that follow is different enough, but the second set is not:

• Acceptable set:

• Unacceptable set:

Specifying the default

You can specify the default for the COPYDDN command option in your installation options module by using the COPYDDN installation option. LOADPLUS was shipped with a default value of (BMCCPY,BMCCPZ) for this option. The command option overrides the default that is in the installation options module.