Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Logical log input

This topic provides more information about logical log input considerations.

For more information, see  Log Master for DB2 documentation .

Logical log input considerations

The High-speed Apply Engine can read logical log input produced by either Log Master for DB2 or an application program that conforms to the published format.

Be aware of the following points regarding High-speed Apply Engine and logical log input:

  • High-speed Apply Engine reads logical log input only for apply requests for DB2 on mainframe targets.

  • Logical log input consists of the following files:

    • The logical log control file contains information about the format and content of the logical log.

    • The logical log data file contains actual change information (updates, deletes, inserts, or DDL objects) in logical log format.

    • (optional) The large volume VSAM files contain data from DB2 columns that hold large volumes of data (such as XML columns or LOB columns). The product or program that generates the logical log must generate these files to enable High-speed Apply Engine to apply data to large volume columns.

    • (optional) The logical log XMLSTRING control file contains the string IDs and string data that DB2 uses to encode the data in XML columns. High-speed Apply Engine needs this file when the logical log includes XML data and the DB2 subsystem of the target tables is different than the subsystem where the logical log was generated. The product or program that generates the logical log must obtain this information from the DB2 catalog table SYSIBM.SYSXMLSTRINGS. To apply the changes to a different target subsystem, High-speed Apply Engine uses the string IDs and data to serialize your XML data correctly.

  • The published format for logical log input does not define an order for the records in either the logical log control file or the logical log data file.

  • High-speed Apply Engine does not use all of the records in logical log input. It reads the following records in either the logical log control file or the logical log data file:

    • CLUS LOB/XML Cluster Data Set Record

    • DCCL Clustering Index Column Description Record

    • DCDX Clustering Index Description Record (deprecated)

    • DCL2 DB2 Column Description Record Part Two

    • DCLI DB2 Column Information Record

    • DCOL DB2 Column Description Record (deprecated)

    • DCXI Clustering Index Information Record

    • DDSM Data Sharing Member Record

    • DLCI Logical Log Column Information Record

    • DLCO Logical Log Column Description Record (deprecated)

    • DLDS Logical Log Data Set Record

    • DLGE Log Information End Record

    • DLGI Log Information Record

    • DLOB LOB Column Description Record

    • DSS1 SysStrings Base Record

    • DSS2 SysStrings TransTable Record

    • DTBC Table Record Count Record

    • DTBI Table Information Record

    • DTBL Table Description Record (deprecated)

    • DTBR Table RBA Record (deprecated)

    • DTS2 Table Space Description Record Part Two (deprecated)

    • DTSI Table Space Information Record

    • DTSP Table Space Description Record (deprecated)

    • DXML XML Column Description record

    • DXSF XMLSTRING Data Set Name Record

    • LLDF Data Change Record (in logical log data file)

    • XPTH Current Path Record

    • XTYP Type Record



Was this page helpful? Yes No Submitting... Thank you

Comments