Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see UNLOAD PLUS for DB2 13.1.

UNLOAD PLUS input copy data set

UNLOAD PLUS requires this data set if you specify the INFILE option to unload from one of the following types of copy data set instead of a DB2 table space:

  • A full or incremental image copy
  • A DSN1COPY sequential data set
  • An inline copy

Related topics

UNLOAD-PLUS-data-sets

UNLOAD-PLUS-DD-statements


Warning

Unpredictable results can occur if the data sets do not match the options that you specify in the INFILE command option.

For information about the data set needed when you use the INFILE option to unload from a VSAM linear data set, see VSAMDD-data-sets.


Unloading from a single data setIf you specify the INFILE option and you are unloading from a single data set that contains an entire table space or one partition of a partitioned table space, you must have one DD statement that uses the ddname that you specified in the INFILE option.


Unloading an entire partitioned table spaceIf you are unloading an entire partitioned table space from multiple image copy data sets (one image copy data set for each partition of the table space), you must have one DD statement for each partition. Each DD statement must use the ddname that you specified in the INFILE option as a prefix and the partition number of the copy as a suffix, even if multiple image copy data sets are stacked as multiple files on a tape.

Note

Concatenating multiple image copy data sets, particularly when mixing copy data sets from tape with copy data sets from DASD, produces unpredictable results.


Unloading only selected partitionsIf you are unloading only selected partitions, you must have one DD statement for each selected partition. Use the ddname that you specified in the INFILE option as a prefix and the partition number of the copy as a suffix.


Unloading from multiple table spacesIf you are unloading from multiple table spaces, you must have one DD statement for each selected table space. Use the ddname that you specified in the INFILE option as a prefix and the sequence in which the table space is referenced using the SELECT statements as a suffix.

For example, if the first SELECT statement specifies INFILE COPY, a DD statement with a ddname of COPY1 must represent the table space. If the second statement references a table in a different table space, you must have a DD statement with COPY2 for the ddname. If the second SELECT statement references a table in the same table space as the first, you do not need an additional DD statement for the copy.

Note

Concatenating multiple image copy data sets, particularly when mixing copy data sets from tape with copy data sets from DASD, produces unpredictable results.

Unloading from stacked tape data sets

To avoid issues while mounting a stacked data set or to prevent conflicts with stacked copies created with parallel processes (parallel processing can complicate stacking):

  • Ensure local and primary copies are not mixed and files of the same type are stacked on the same tapes only.
  • Ensure multiple partition copies from the same file are stacked by partition number in ascending order, the stacked data sets on tape volumes need to be placed in FSN (file sequence number) in ascending order.

 

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