Batch Copy Facility

The Batch Copy facility lets you copy data between any two DB2 tables in batch mode and automates how the data is copied.
carcudb2
The Batch Copy facility lets you copy data between any two DB2 tables in batch mode and automates how the data is copied.
For example, when using Batch Copy, the statements to unload the data from the source table to the target table are generated, the load utility is executed, and the target table can be created automatically. The control statements for the copy are stored in a user-specified batch data set. Once this batch data set is closed and unallocated, it can be submitted to the CA Batch Processor for execution.
Use of the Batch Copy facility provides the following benefits:
  • Familiarity -- Because the Batch Copy facility is an extension of RC/Copy, users that are familiar with RC/Copy will be able to quickly use the Batch Copy facility.
  • Increased Resources -- If data needs to be copied between enormously large tables, resources can be consumed at an exhaustive rate during peak hours. With the Batch Copy facility, you can write the statements needed to copy the data to a batch data set. This data set can be submitted during off-peak hours to increase resource availability.
  • Row Limitations -- You can specify an exact number or rows to be copied, which is useful when only a few rows are needed from a large table.
  • Multiple Subsystem Support -- Table selection is expanded because you can copy data from multiple DB2 subsystem IDs (SSID) within a location. Previously, tables could only be copied within the same DB2 subsystem ID (SSID).
  • Automatic Utility Execution -- You can select which utilities should automatically be executed after the data has been copied. For example, the PDASTATS option of CA Database Analyzer or RUNSTATS can be executed to reflect the new data statistics.
  • Data Conversions -- Support is provided for a wider variety of data type conversions than online copy.
  • Row Order -- ORDER BY criteria specified if EQF is supported. Data sorted in the target tables clustering order could eliminate the need for a reorg.