ATCB   

Explanation

The CICS application program issued two consecutive DFHTC writes or two consecutive DFHTC reads, but in either case did not issue an intervening wait.

System action

The transaction is abnormally terminated with a CICS transaction dump.

User response

Take corrective action within the program being executed.

This is almost certainly an application program error. Determine the flow of control through the application and determine why an intervening wait is not issued. The trace table may be useful to discover where the application is issuing the read and write requests. If necessary, start trace or auxiliary trace using the master terminal command and rerun the transaction to obtain a trace. The output of the auxiliary trace can be printed using the trace utility program, DFHTU710.

Problem determination

A transaction dump is provided with this abend. In the dump, register 12 addresses the current TCA, and register 10 and the field TCAFCAAA address the TCTTE associated with this task. In TCATPOS2, bit TCATPOWR (X'01') indicates that a write is requested by the DFHTC macro, and bit TCATPORR (X'10') indicates that a read is requested. In TCTTEOS, bit TCTTEOWR (X'01') indicates that a write is in progress, and bit TCTTEORR (X'10') indicates that a read is in progress.

Analysis:

Register    Label     Description

R10=@TCTTE  TCZARQ05  Bit TCATPOWR is on in byte
R12=@TCA    (TCZAQ1W) TCATPOS2, and bit TCTTEOWR
                      is on in byte TCTTEOS.

R10=@TCTTE  TCZARQ05  Bit TCATPOWR is on in byte
R12=@TCA    (TCZAQ2W) TCATPOS2, and bit TCTTEORR
                      is on in byte TCTTEOS.

R10=@TCTTE  TCZARQ12  Bit TCATPORR is on in byte
R12=@TCA              TCATPOS2, and bit TCTTEORR
                      is on in byte TCTTEOS.

Module

DFHZARQ


ATCB.html | Timestamp icon Last updated: Sunday, 4 June 2017