Generating Load Files

can read the changes recorded in the DB2 logs and can use them to generate a load file. The load file contains one or more records for each transaction that occurred for a specified table during a specified log range. These transactions consist of INSERTs, UPDATEs, DELETEs, and MASS DELETEs. Load files can be used to update tables in the same DB2 subsystem or in other subsystems.
caladb2
CA Log Analyzer™ for DB2 for z/OS
can read the changes recorded in the DB2 logs and can use them to generate a load file. The load file contains one or more records for each transaction that occurred for a specified table during a specified log range. These transactions consist of INSERTs, UPDATEs, DELETEs, and MASS DELETEs. Load files can be used to update tables in the same DB2 subsystem or in other subsystems.
For example, you can use a load file to load table transactions into a set of audit tables (also referred to as a data warehouse). Maintaining a data warehouse can help you monitor table activity by enabling you to query the audit tables directly using SQL. These direct queries can be more efficient than generating DML detail reports against the original tables and searching through them. Typically, when populating an audit table or data warehouse, you also include URID information for each record. This information can include the plan name and authorization ID of the process that performed the transaction, the time that the transaction occurred, and so on.
You can also use a load file to replicate changes from one table to another. This function is useful in a testing environment, in which you test your data in a test table before replicating the data to your production environment. Typically, when replicating table changes in this manner, the production table is identical to the test table.
You can also use a load file to propagate table changes to an external database. This function is useful when different groups in the same company use different database systems.
When you create a load file, you can specify the utility that you will use to update the target table.
CA Log Analyzer™ for DB2 for z/OS
then generates the appropriate control statements for that utility.
CA Log Analyzer™ for DB2 for z/OS
can generate load control statements for the following utilities:
  • CA Fast Load for DB2 for z/OS
  • IBM LOAD
  • Log Apply (a component of
    CA Log Analyzer™ for DB2 for z/OS
    )
The utility that you select depends on the task you are performing.
CA Fast Load for DB2 for z/OS
and IBM LOAD are intended for use when you are updating a data warehouse for historical reporting purposes. Log Apply is intended for use when you are replicating changes to an identical table.