DSNL413I PROTOCOL ERROR DETECTED IN SYNCPOINT REQUEST/RESPONSE FROM PARTICIPANT location LUWID=luwid=token. INFORMATION RECORDED IN TRACE RECORD WITH IFCID=208 AND IFCID SEQUENCE NUMBER=seq-no

Explanation

Db2 is the coordinator of the logical unit of work identified by 'luwid=token'. A protocol error occurred during the SNA sync point exchange with the participant identified by 'location'. The protocol error fits into one of the following categories:
  • An unknown SNA PS header was received.
  • An SNA PS header was received in the wrong sequence.
  • An invalid LU6.2 verb sequence was used to deliver the SNA PS header.
  • A DEALLOCATE TYPE(ABEND_SVC) was received from the participant, indicating that the participant detected a protocol violation in the PS headers transmitted by Db2.
location
The relational database name (location-name) of the participant.
luwid=token
The global logical unit of work id and the local token that identify the thread.
seq-no
The IFCID sequence number associated with the trace record. The sequence number is printed in hexadecimal format. If the sequence number is zero, IFCID 208 was not active or it was active with a destination of the resident trace table only. IFCID 208 is a member of statistics class 4, which has a default destination of SMF.

If the protocol error is detected before the commit decision, the unit of work is backed out.

If the protocol error is detected after the commit decision, the outcome of the unit of work is unchanged. In this case, the remote participant might be indoubt. Db2 does not automatically resolve the indoubt thread with the partner 'location' after a protocol error is detected.

System action

Alert A005 is generated. A trace record whose IFCID=208 is written.

System programmer response

This is an APARable error, probably at the participant, but possibly at the Db2 coordinator. The Db2 documentation required is contained in the statistics class 4 trace record. Determine the destination of statistics class 4. Locate and print the trace record with SEQUENCE NUMBER='seq-no'.

Call the database administrator. The participant might need to manually resolve the indoubt thread.

Database Administrator Action: The Db2 coordinator does not know the status of the thread at the participant. The Db2 coordinator assumes that it is indoubt and maintains knowledge of the indoubt participant until it is purged with the RESET INDOUBT command. If the thread is indoubt at the participant, it must be resolved using manual (heuristic) means. The status of the thread at the local Db2 (the coordinator) can be determined with the DISPLAY THREAD command for type indoubt threads by including the LUWID('token') parameter in the command.

If the 'participant' location is also a Db2, the RECOVER INDOUBT command can be used at the participant to resolve the indoubt thread.