ATNI   

Explanation

There are two forms of this abend:

VTAM form

The node error program (NEP) or NACP decides the task should be abnormally terminated. DFHZNAC informs the request module to abend the transaction after the TC unit has completed.

Non-VTAM form

The terminal error program (TEP) or terminal abnormal condition program (TACP) decides the task should be abnormally terminated. DFHTACP informs DFHZARQ to abend the transaction after the TC unit has completed.

System action

The task is abnormally terminated with a CICS transaction dump.

User response

This usually occurs when, due to a hardware failure, a network device rejects the data stream sent to it. The device itself may indicate an error code that will give a specific reason for the rejection. Check the CSMT log for further information.

This abend can also result from an error in a connected system such as a mirror transaction abend.

Abend ATNI can occur if a user application does not correctly handle an error return code from an external resource manager, such as DB2.

For the NEP (VTAM) form, run a VTAM trace type=BUF for the logical unit and repeat the error.

For the TEP (non-VTAM) form, run a link trace for the line or local channel address for the device.

Examine the data stream and error response to determine the cause of the error.

This type of error occurs if the definitions in the TCT do not match the attributes of the actual device.

Module

DFHZARL, DFHZARM, DFHZARQ, DFHZRAQ, DFHZSUP


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