Type record (XTYP)
Each logical log contains one instance of the Type Record. This record is present in a logical log created from any source. The record describes the originating Db2 subsystem, the version of the logical log format, and information about the default character sets and encoding schemes used in the originating database environment.
Record status: Platform independent
Field name | Offset | Definition | Description | |
|---|---|---|---|---|
Dec | Hex | |||
CNTLRECORDTYPE | 00 | 00 | CHAR(4) | Control record type: XTYP - Type Record |
CNTLFILETYPE | 04 | 04 | CHAR(4) | Type (format) of control file - 'DB2' represents Db2 |
CNTLFILETYPEVERSION | 08 | 08 | CHAR(6) | |
CNTLFILESYSID | 14 | 0E | CHAR(4) | Originating Db2 subsystem ID |
SQLDELIMITER | 18 | 12 | CHAR(1) | SQL delimiter is defined by the DSNZPARM on the system where the logical log was created |
MIXED | 19 | 13 | CHAR(1) | Y - mixed DBCS/SBCS allowed N - mixed DBCS/SBCS not allowed |
DECIMALPOINT | 20 | 14 | CHAR(1) | Decimal point character, either a comma or a period |
EBCDICSINGLECCSID | 21 | 15 | CHAR(5) | Default Coded Character Set ID (CCSID) used for single-byte EBCDIC on originating Db2 subsystem |
EBCDICDOUBLECCSID | 26 | 1A | CHAR(5) | Default CCSID used for double-byte EBCDIC on originating Db2 subsystem |
EBCDICMIXEDCCSID | 31 | 1F | CHAR(5) | Default CCSID used for mixed EBCDIC on originating Db2 subsystem |
ASCIISINGLECCSID | 36 | 24 | CHAR(5) | Default CCSID used for single-byte ASCII on originating Db2 subsystem |
ASCIIDOUBLECCSID | 41 | 29 | CHAR(5) | Default CCSID used for double-byte ASCII on originating Db2 subsystem |
ASCIIMIXEDCCSID | 46 | 2E | CHAR(5) | Default CCSID used for mixed ASCII on originating Db2 subsystem |
UNICODESINGLECCSID | 51 | 33 | CHAR(5) | Default CCSID used for single-byte Unicode on originating Db2 subsystem (if Db2 subsystem does not support Unicode, field contains blanks) |
UNICODEDOUBLECCSID | 56 | 38 | CHAR(5) | Default CCSID used for double-byte Unicode on originating Db2 subsystem (if Db2 subsystem does not support Unicode, field contains blanks) |
UNICODEMIXEDECCSID | 61 | 3D | CHAR(5) | Default CCSID used for mixed Unicode on originating Db2 subsystem (if Db2 subsystem does not support Unicode, field contains blanks) |
ENCODINGSCHEME | 66 | 42 | CHAR(1) | A - ASCII E - EBCDIC U - Unicode |
APPENCODINGSCHEME | 67 | 43 | CHAR(1) | A - ASCII E - EBCDIC U - Unicode |
DB2VERSION 1 | 68 | 44 | CHAR(3) | Version of Db2 that the product was running against when the logical log was created. For example: 910 - version 9.1.nn A10 - version 10.1.nn For IBM Db2 Version 12 or later, DB2VERSION contains a constant Z99. |
DB2CATALOGMODE 1 | 71 | 47 | CHAR(1) | Migration mode of the Db2 catalog when the logical log was created: ' ' - migration mode not set (default value) C - conversion mode E - enabling-new-function mode N - new-function mode |
UNTRANOBJNAMEINSCAN | 72 | 48 | CHAR(1) | Y - untranslatable characters encountered in table or column names during log scan N - no untranslatable characters encountered |
UNTRANOBJNAMEINSQL | 73 | 49 | CHAR(1) | Y - untranslatable characters present in Db2 object names within generated SQL N - no untranslatable characters present |
UNTRANOBJNAMEINDDL | 74 | 4A | CHAR(1) | Y - untranslatable characters present in generated DDL objects N - no untranslatable characters present U - unknown (for example, when the product generates only logical log output and the INCLUDEDDL value is Yes) |
FUNCTIONLEVEL 1 | 75 | 4B | For IBM Db2 Version 11 or earlier: CHAR(3) | Function level of the Db2 catalog when the logical log was created. BMC AMI Log Master for Db2 uses this field to identify Db2 version-specific functionality when you are skipping a version migration (for example, migrating from Db2 Version 8 to Version 10). For Db2 Version 12 or later, FUNCTIONLEVEL specifies the function level of the subsystem or data sharing group on which the LOGSCAN statement ran when the logical log was created. The format is vvrmmm. For example: Before new function activation (BNFA) - 121100 After new function activation (ANFA) - 121500 |
For IBM Db2 Version 12 or later: CHAR(6) | ||||
CODELEVEL 1 | 81 | 51 | CHAR(6) | For Db2 Version 12 or later, the code level of the subsystem or data sharing member on which the LOGSCAN statement ran when the logical log was created. The format is vvrmmm. |
CATALOGLEVEL 1 | 87 | 57 | CHAR(6) | For Db2 Version 12 or later, the catalog level (highest level of CATMAINT) of the subsystem or data sharing group on which the LOGSCAN statement ran when the logical log was created. The format is vvrmmm. |
(Total Length) | 93 | 5D | Not applicable | Not applicable |
1 IBM Db2 Version 12 and later support a continuous delivery model with levels in vvrmmm format that are incompatible with the previous FUNCTIONLEVEL, DB2VERSION, and DB2CATALOGMODE fields. If DB2VERSION is a constant Z99, you should use the FUNCTIONLEVEL, CODELEVEL, and CATALOGLEVEL fields in vvrmmm format.
Related topic