DFS2146 INVALID DATA BLOCK RECEIVED LINK xx.

Explanation

A data block was received on link xx that, when checked, was found to contain invalid or lost data, or the conversational routines detected an error while attempting to process a conversational type message.

System action

The data block is rejected. If the data block was a resync, restart, or shutdown message, the link has stopped. If the data block was a user or system message, the message was discarded (dequeued) on the sending IMS. Also, the associated sending MSNAME path was stopped on the sending IMS and message DFS2140 with a 2146 reason code was issued on the sending IMS. Both sides write type 6701 ID = MSSx (x = 1, 2, or 3) log records.

Operator response

(master terminal): Display the logical link in the partner system (/DIS MSNAME) to see if the link was stopped. If the partner was not stopped, the error was recovered. If it was stopped, restart the link (/START MSNAME).

System programmer response

Print the type 6701 log records and analyze the error.

Problem determination

Contact the system programmer if the error persists.

The following CLBTEMP fields will be set in the LLB block in the 6701 MSS1 record:
  • CLBTEMP1 = Pseudo abend code if this is a conversational error. CLBTEMP4 is CONM or CON2 for conversational type errors.
  • CLBTEMP2 = Return code if applicable
  • CLBTEMP3 = Message key = x'00000862' = decimal 2146
  • CLBTEMP4 = Module ID. i.e. C'CONM' = DFSCONM0, C'CON2' = DFSCON20, C'CMSV' = DFSCMSV0, or C'CMSZ' = DFSCMSZ0.
  • If applicable, R5 or R14 BALR offset into the module that detected the error