IFCID 0191 trace record common diagnostic procedures
The diagnosis of a DRDA exception condition that is identified by DDIS begins with one or more IFCID 0191 trace records and the Db2 reason code that is recorded within the QW0191RS field of the QW0191HD section.
For each reason code, a diagnostic procedure exists which documents the specific nature of the IFCID 0191 records.
How to interpret IFCID 0192 records
The correct format for DDM data streams is described in DDM under the term "DSS". Essentially, DDM data streams consist of one or more DSSs, each of which contains a DDM level 6a header. Flags in the DDM level 6a header tell the receiver (Db2) about the relationship between the current DSS and other DSSs in the data stream.
The DCRM component of Db2 is responsible for validating the content of DDM level 6a data streams, as described by the DDM term DSS. DDM defines several syntax error and protocol error conditions, which are produced when invalid DDM data streams are detected. These errors are produced for one of the following reasons:
- A DDM level 6a header contains an invalid flag setting or data value.
- The flag settings or data values in a DDM level 6a header are not consistent with the flag settings or data values in the previous DDM level 6a header.
In order to describe these errors, the DCRM component records trace data for two events:
- A DDM data stream is detected which contains a syntax error. When an error of this type is encountered, a DDM SYNTAXRM message is sent to describe the error. Within the SYNTAXRM message, the DDM SYNERRCD (syntax error code) and the DDM SVRCOD (severity code) describe the cause and severity of the error. For these errors, the reader should refer to the DDM SYNERRCD documentation, to determine the nature of the error.
- A DDM data stream is detected which contains a protocol error. When an error of this type is encountered, a DDM PRCCNVRM message is sent to describe the error. Within the PRCCNVRM message, the DDM PRCCNVCD (conversational protocol error code) and the DDM SVRCOD (severity code) describe the cause and severity of the error. For these errors, the reader should refer to the DDM PRCCNVCD documentation to determine the nature of the error.
In either case, DCRM records the following information in the trace record:
- The nature of the error (protocol or syntax)
- The DDM severity code (SVRCOD)
- The DDM error code (PRCCNVCD for protocol errors, SYNERRCD for syntax errors)
- The offset of the current DDM level 6a header in the data stream. This offset is measured from the start of the first DDM level 6a header in the data stream.
- The current DDM level 6a header, as defined in the DDM DSS term. This header might or might not be the cause of the error, since many of the errors indicate an inconsistent condition between the current DDM level 6a header and the previous DDM level 6a header. Thus, it is possible that the error was caused by the previous DDM level 6a header.
- The first 250 bytes of data in the data stream that follows the current level 6a header
- The offset of the previous DDM level 6a header, if the error was detected in a header other than the first. This offset is measured from the start of the first DDM level 6a header in the data stream.
- The previous DDM level 6a header, as defined in the DDM DSS term.
How to interpret IFCID 0193 records
These records document the inconsistency between the SQLCODE returned by the AS for a commit or rollback command, and the disposition of the Unit of Work reported by the AS. For example, if a commit command was sent, and an ENDUOWRM reply message was received with UOWDSP = '01'X (commit disposition), and the SQLCODE in the SQLCA was -204, then the IFCID record would contain the values -204,'C','C'. The complete data stream for the reply, including the SQLCARD and the ENDUOWRM, is in the IFCID 0191 record, which is always written when an IFCID 0193 record is written.