Abend codes AZxx

AZAB
Explanation:

DFHZARM has a SEND DATA request with a data length greater than 65 528 bytes which is the maximum that it can process.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

This is a CICS internal logic error. You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Module(s):

DFHZARM

AZAD
Explanation:

DFHZCN1 has been started from an unexpected system. The CCIN transaction can only be issued by a client.

System action:

The transaction is abnormally terminated. Exception trace point AP3008 is written. Data1 holds the XMIQ start type.

User response:

Issue the CCIN transaction only from a client.

Module(s):

DFHZCN1

AZAE
Explanation:

DFHZCN1 was started from a terminal facility, but not an LU6.2 session. The CCIN transaction may only be issued by a client.

System action:

The transaction is abnormally terminated.

User response:

Issue the CCIN transaction only from a client.

Module(s):

DFHZCN1

AZAF
Explanation:

DFHZCN1 was started for transaction CCIN. However either the environment is wrong or the client architecture has been violated. This abend is always issued in conjunction with a DFHZC32nn message which explains the problem in more detail.

System action:

Exception trace point AP30xx is written. The transaction is abnormally terminated.

User response:

Look for a DFHZC32nn message on the console or CSNE and look for exception trace points AP30xx. Use these to diagnose the problem.

Module(s):

DFHZCN1

AZAG
Explanation:

DFHZCT1 has been started from an unexpected system. The CTIN transaction can only be issued by a client.

System action:

The transaction is abnormally terminated with a CICS transaction dump. Exception trace point AP302A is written. Data1 holds the XMIQ start type.

User response:

Issue the CTIN transaction only from a client.

Module(s):

DFHZCT1

AZAH
Explanation:

DFHZCT1 was started from a terminal facility, but not an LU62 session. The CTIN transaction can only be issued by a client.

System action:

The transaction is abnormally terminated with a CICS transaction dump. Exception trace point AP3032 is written. Data1 holds the principal facility address.

User response:

Issue the CTIN transaction only from a client.

Module(s):

DFHZCT1

AZAI
Explanation:

DFHZCT1 was started for transaction CTIN. However either the environment is wrong or the client architecture has been violated. This abend is always issued in conjunction with a DFHZC32nn message which explains the problem in more detail.

System action:

Exception trace point AP30xx is written. The transaction is abnormally terminated.

User response:

Look for a DFHZC32nn message on the console or CSNE and look for exception trace points AP30xx. Use these to diagnose the problem.

Module(s):

DFHZCT1

AZAJ
Explanation:

DFHZCN1 was started for transaction CCIN. However, the CCIN transaction is being started on a surrogate, which means that it has been defined as a remote transaction. CCIN must be a local transaction and be run on a CICS region which is directly connected to a client.

System action:

Exception trace point AP3041 is written. The transaction is abnormally terminated.

User response:

Either use the default definitions for CCIN or ensure that it is defined as a local transaction.

Module(s):

DFHZCN1

AZAK
Explanation:

DFHZCT1 was started for transaction CTIN. However, the CTIN transaction is being started on a surrogate, which means that it has been defined as a remote transaction. CTIN must be a local transaction and be run on a CICS region which is directly connected to a client.

System action:

Exception trace point AP3039 is written. The transaction is abnormally terminated.

User response:

Either use the default definitions for CTIN or ensure that it is defined as a local transaction.

Module(s):

DFHZCT1

AZCA
Explanation:

An internal logic error has been detected during APPC mapped processing. The conversation state maintained by DFHZARL does not match that maintained jointly by DFHETL and DFHZARM.

The problem may also arise when CICS is assembling application data and receives end of chain before receiving all of the data that is expected.

System action:

The task is abnormally terminated with a CICS transaction dump. CICS processing continues.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Module(s):

DFHZARM

AZCB
Explanation:

CICS has received sense code X'088901xx' during APPC mapped processing. This should be followed by an error data GDS (generalized data stream) variable.

CICS has attempted to receive the error data. However this attempt has failed because no data has been received or because the data received is not for an CICS ISSUE ERROR of the correct length.

CICS expects the error data to indicate that the other system does not recognize GDS ID X'12F2' (function management data).

System action:

The task is abnormally terminated with a CICS transaction dump.

The erroneous GDS ID is returned to the remote system for further analysis there.

User response:

Check for session failure and for abend by the transaction in the other system.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Module(s):

DFHZARM

AZCC
Explanation:

The failing transaction has sent function management data to a transaction running in a system that does not provide support for application function management data.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that the remote system can support application function management data.

Module(s):

DFHZARM

AZCD
Explanation:

A possible intersystem logic error has been detected during APPC mapped processing. The length of application data that is to be received (as determined from the LL fields and concatenation flags) does not match the length actually received. CICS determines the length of application data that is to be received from the LL fields and concatenation flags. However, CICS has not received all of the data that is expected.

This abend can be caused by a loss of data following the failure of a persistent sessions restart in a partner system. In this case, no logic error has occurred because any updates are backed out.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

If this abend is not caused by the failure of a persistent sessions restart in a partner system, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Module(s):

DFHETL, DFHZARM

AZCE
Explanation:

An intersystem error has been detected during APPC mapped processing. The length of application data that is to be received (as determined from the LL fields and concatenation flags) exceeds the CICS implementation limit of 32 767, for receive and converse commands, or 65 000 for CICS transaction routing or function shipping requests.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Reduce the amount of data that the transaction in the remote system is transmitting to CICS.

Modules:

DFHETL, DFHZARM

AZCF
Explanation:

An internal logic error has been detected during APPC mapped processing. An invalid request has been passed to DFHZARL.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARM

AZCG
Explanation:

An internal logic error has been detected during APPC mapped processing. DFHZARM expects the TCTTE passed to have been defined as APPC, TCTEILUC (TCTELUC) set on, and TCTECVT set to TCTEMAPD (to indicate a mapped conversation).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARM

AZCH
Explanation:

Sense code X'0889xxxx' has been received unexpectedly during the processing of APPC mapped data.

This represents a violation of the APPC architecture by the remote system.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHETL, DFHZARM

AZCI
Explanation:

The processing of APPC mapped data requires generation of an APPC attach function management header (FMH) with default values. In particular, the sync level requested is defaulted to 2. However, the session that is to be used has been bound with a sync level of 1.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that:

Modules:

DFHETL, DFHZARM, DFHZARQ

AZCJ
Explanation:

An APPC structured field with GDS ID X'12F1' (null data) has been sent to a remote system that does not support the receipt of these fields. The remote system has responded negatively and has terminated the conversation.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

The problem is in the remote system. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARM

AZCK
Explanation:

An internal logic error has been detected during error recovery for APPC mapped processing. The conversation was being switched to RECEIVE state by an internal CICS SEND INVITE, but the conversation had already been FREEd by the partner.

System action:

The task is abnormally terminated with a CICS transaction dump. CICS processing continues.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARM

AZCL
Explanation:

CICS has received sense code X'088901xx' during APPC mapped processing. The generalized data stream (GDS) should contain a valid GDS identity in the error data but CICS does not recognize the value. The values recognized by CICS are:

X'12F1'null data
X'12F2'function management data
X'12FF'application data.
System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check for session failure and for an abend by the transaction in the other system.

Modules:

DFHZARM

AZCM
Explanation:

An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message produced by the domain that detected the original error.

Modules:

DFHZARM

AZCN
Explanation:

The task has been purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHZARM

Start of change
AZCO
Explanation:

The VTAM persistent sessions initialization transaction CGRP has been started directly from a terminal. This is not permitted. This transaction can only be started internally by CICS.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

None.

Modules:

DFHZCGRP

End of change
AZCP
Explanation:

A logic error has been detected in ZCP. An allocation request for a starting task cannot be satisfied.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSUP DFH62XM

AZCQ
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain to change the recovery status of an intercommunication session. The domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

This failure is either the result of a task purge, or it represents a CICS logic error and you will need assistance from IBM.

See the related diagnostic material produced by the recovery manager domain.

Modules:

DFHZSUP DFHMRXM DFH62XM

AZCR
Explanation:

A logic or protocol error has been detected during processing of an APPC SYNCPOINT ROLLBACK request. An attempt has been made to restore the conversation state to what it was after completion of the last successful unit of work. This saved state does not match flows received from the partner.

The problem arises during rollback in one of the following situations:

System action:

The task is abnormally terminated with a CICS transaction dump. Other processing continues.

User response:

The problem can arise because of a failure in CICS, or a failure in the partner. To determine which is failing, analyze the flows at the last successful syncpoint. Try to determine the states the two LUs were in at this point. Look at the last syncpoint flow into CICS from the partner, before the abend. From this flow, calculate whether the change-direction indicator on the SPCMOD modifier byte is on. ( See the SNA Formats manual for further information on the SPCMOD modifier byte.) The indicator must only be set when the saved CICS conversation state is send. If the last CICS state was send, and the indicator is on, CICS is at fault. Similarly, if the last CICS state was receive, and the indicator is off, CICS is at fault.

If the last CICS state was send and the indicator is off, or the last CICS state was receive, and the indicator is on, CICS has received a change-direction indicator when it was not expecting one. In this case, examine the partner for a logic error.

Modules:

DFHZARL

AZCT
Explanation:

A terminal read-time-out condition has been detected. The transaction has been waiting for a terminal input message for an interval longer than specified in the RTIMOUT value for that transaction.

Coding RTIMOUT in the PROFILE entry causes the task to be abnormally terminated if the terminal does not send input within the specified time.

System action:

The transaction is abnormally terminated. A dump is not provided unless the dump table entry for transaction dump code AZCT indicates that one should be taken.

User response:

If a HANDLE ABEND command has been issued for this task, the read that was timed-out is still outstanding. In order to cancel this read, issue an ABEND command at the end of the user exit routine so that CICS can clean up the terminal’s TCTTE. No further terminal control commands should be issued.

Modules:

DFHZARQ

AZCU
Explanation:

The COVR transaction has been started directly from a terminal, or by a START command. This is not permitted. This transaction can only be started internally by CICS.

System action:

The transaction is abnormally terminated. No transaction dump is taken.

User response:

None.

Modules:

DFHZCOVR

AZCV
Explanation:

A logic error has been detected in the COVR transaction while trying to connect to VTAM.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZCOVR

AZCW
Explanation:

An attempt has been made to run the CICS internal task CSTP as a user transaction.

System action:

CICS terminates the task with a transaction dump.

User response:

Investigate why the attempt was made to run CSTP as a user transaction.

Modules:

DFHZCSTP

AZIA
Explanation:

The transaction attempted to acquire or free storage during MRO processing. The response from the CICS storage manager (SM) domain indicated that the request was invalid.

System action:

The task is abnormally terminated with a dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZIS2

AZIB
Explanation:

The transaction was purged whilst waiting for storage to receive MRO data from a connected subsystem. The purge may have been the result of operator action, such as CEMT SET TASK PURGE, or as the result of the waiting time exceeding the DTIMOUT value for the transaction.

System action:

The task is abnormally terminated with a dump.

User response:

If the condition is caused by time-out, examine the DTIMOUT value for the failing transaction and increase it if it is too low.

Modules:

DFHZIS2

AZIC
Explanation:

An INVALID, DISASTER, or EXCEPTION condition has occurred on a call to the storage manager domain (DFHSMGFM) to FREEMAIN a CRB control block.

The domain that detected the original error provides an exception trace, a console message, and possibly a system dump.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Please see the related message from the domain that detected the original error.

Modules:

DFHZIS2

AZID
Explanation:

A PURGED condition has occurred on a call to the storage manager domain (DFHSMGFM) to FREEMAIN a CRB control block.

The domain that detected the original error provides an exception trace.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHZIS2

AZIE
Explanation:

An interregion communication (IRC) ISSUE-ERROR or ISSUE-ABEND flow has been received in violation of IRC protocols. This can be caused by:

System action:

The task is abnormally terminated with a transaction dump.

User response:

Check whether a mixture of mapped and unmapped conversations are being used as this can cause this abend. Check for any other reasons for transactions to be abending on the attached system.

If a CICS logic error is involved, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARQ

AZIF
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain to change the recovery status of an intercommunication session. The domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table).

Start of changeThis is either the result of a task purge, a CICS logic error, or of the inappropriate use of the indoubt test transaction, CIND. CIND should be activated only on the CICS system where the syncpoint processing was initiated. In particular, CIND should not be used on any of the CICS mirror transactions.End of change

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Start of changeDetermine whether CIND has been activated for a transaction that did not initiate the syncpoint processing. If CIND is not being used see the related diagnostic material produced by the recovery manager domain and determine the reason for the failure.End of change

In the case of a CICS logic error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARQ

Start of change
AZIG
Explanation:

An MRO session read-time-out condition has been detected. The transaction has been waiting for an MRO session for an interval longer than specified in the RTIMOUT value for that transaction.

Coding RTIMOUT in the PROFILE entry causes the task to be abnormally terminated if the session does not respond within the specified time.

System action:

The transaction is abnormally terminated. A dump is not provided unless the dump table entry for transaction dump code AZIG indicates that one should be taken.

User response:

If a HANDLE ABEND command has been issued for this task, the read that was timed-out is still outstanding. In order to cancel this read, issue an ABEND command at the end of the user exit routine so that CICS can clean up the terminal’s TCTTE. No further terminal control commands should be issued.

Modules:

DFHZIS2

End of change
AZI1
Explanation:

An IRC data transmission request has been issued, but cannot be completed because the transmission protocol has been violated.

If the session is not used for distributed transaction processing, that is if it is used for function shipping or transaction routing, then the problem is caused by a CICS logic error.

If the session is used for distributed transaction processing, then the following are possible causes of the abend:

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Determine the cause of the abend and if appropriate, correct the application. For further guidance, refer to the section on the EXEC Interface block (EIB) in the CICS Intercommunication Guide. The EIB describes the state of the session after a request has been issued.

Modules:

DFHZARQ

AZI2
Explanation:

An IRC data transmission request has been issued but cannot be completed. Possible causes of the problem include:

If the abend was caused by DFHIRP rejecting the transmission request, the dump will contain DFHIRP’s return code in the field TCTEIRET for the TCTTE representing the failed IRC session. The address of this TCTTE is in field B of the trace entry representing the DFHTC data transmission request.

The meanings of the DFHIRP return codes are given in the copybook, DFHIRSDS.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

If the cause of the error was a purge or a time-out, no further action is required.

If the error was caused by a condition such as an attempted SEND while in RECEIVE state or vice versa, analyze the dump and correct the protocol violation.

Modules:

DFHZARQ

AZI3
Explanation:

A terminal control request issued by an application to a remotely-owned terminal failed because the conversation with the other system failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARQ

AZI4
Explanation:

An IRC data transmission request has been issued, but cannot be completed because the other system has become unavailable for interregion communication.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Rerun the transaction when IRC is available.

Modules:

DFHZARQ

AZI5
Explanation:

An IRC data transmission request has been issued, but the data sent by the connected system in response to the request violated IRC protocols.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARQ

AZI6
Explanation:

The transaction was connected to another transaction in another CICS system via an IRC link. This other transaction has abnormally terminated.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Correct the cause of the abend in the connected transaction.

Modules:

DFHZARQ

AZI7
Explanation:

The transaction was processing an MRO request which involved waiting for a response from a connected subsystem. The ‘wait’ request was rejected by the CICS dispatcher.

System action:

The transaction is abnormally terminated with a dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZIS2

AZI8
Explanation:

The error log data received with an ISSUE-ABEND flow on an IRC connection was not in the correct format.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZIS1

AZI9
Explanation:

The transaction was processing an MRO request which involved waiting for a response from a connected subsystem. During the wait, the failing transaction was purged. The purge can only have been the result of operator action, such as a CEMT SET TASK PURGE.

System action:

The task is abnormally terminated with a dump.

User response:

Investigate the reason the transaction was purged.

Modules:

DFHZIS2

AZRA
Explanation:

DFHZARRC detected that the address of an FMH in the APPC was not in the receive buffer. The cause could either be a storage overwrite or a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. Check the TCTTE in the transaction dump for printable characters or other signs of a storage violation error.

Modules:

DFHZARRC

AZRB
Explanation:

Module DFHZARR0 was called with an invalid first parameter. The first parameter should be the code of the function to be performed. This is a CICS logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR0

AZRD
Explanation:

The logical and physical APPC receive buffers have become out of step. This problem is caused either by a storage overwrite or by a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. Check the TCTTE in the transaction dump for printable characters or other signs of a storage violation error.

Modules:

DFHZARR0

AZRE
Explanation:

The logical APPC receive buffer (addressed by TCTERBLA) starts before or after the physical receive buffer (addressed by TCTERBLA). This is not valid as the logical receive buffer is the part of the physical receive buffer that is yet to be processed. This problem could be caused either by a storage overwrite or by a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible then a level 1 and 2 trace of the TC component would aid problem determination. Check the TCTTE in the transaction dump for printable characters or other signs of a storage violation error.

Modules:

DFHZARR0

AZRF
Explanation:

The DFHZUSR state machine has returned an invalid state error at a point where it should not be possible. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRF

AZRG
Explanation:

The DFHZUSR state machine has returned an invalid state error at a point where it should not be possible. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR

AZRH
Explanation:

The DFHZARR state variable RECEIVE_TYPE, used to control receive processing, has been set to an invalid value. The only other module that has access to this variable is DFHZARRF. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR

AZRI
Explanation:

One of the parameters passed to DFHZARR1. was invalid. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR1

AZRJ
Explanation:

The length of a record that DFHZARR0 has been requested to remove from the APPC receive buffer, is longer than the buffer itself. This problem could be caused either by a storage overwrite or by a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. Check the TCTTE in the transaction dump for printable characters or other signs of a storage violation error.

Modules:

DFHZARR0

AZRK
Explanation:

The DFHLUC parameter list passed back from DFHZERH to DFHZARRF contained an invalid combination of LUCCIERR, LUCCIFRE, and LUCCIRBK fields. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRF

AZRL
Explanation:

Module DFHZARRF was called with an invalid first parameter. The first parameter should be the code of the function to be performed. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRF

AZRM
Explanation:

Module DFHZARR called one of its own internal routines at the wrong time. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR

AZRN
Explanation:

The DFHLUC parameter list passed back from DFHZERH to DFHZARRF did not have LUCCIERR set on. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRF

AZRO
Explanation:

Module DFHZARER was called with an invalid first parameter. The first parameter should be the code of the function to be performed. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARER

AZRP
Explanation:

Module DFHZARER detected an invalid response from DFHZNAC. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARER

AZRQ
Explanation:

Module DFHZARRA was called with an invalid parameter. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRA

AZRR
Explanation:

Module DFHZARRA detected that the application buffer chained off of a TCTTE at offset TCTERCSA had a corrupted header. This is caused either by a CICS logic error or by a storage overwrite. The exception trace point that accompanies this abend code gives the TCTTE address.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. Check the TCTTE in the transaction dump for printable characters or other signs of a storage violation error.

Modules:

DFHZARRA

AZRS
Explanation:

Module DFHZARRA is unable to acquire main memory for a new application buffer into which it is supposed to copy some data. This is because the DFHLUC receive request is SUBTYPE=LLID, SET=YES and DFHZARRA does not know the length to acquire on the GETMAIN. DFHZARRA requires the length of the record currently being received, but it has been set to 0 in error. This is a CICS logic error. The exception trace point that accompanies this abend code gives the TCTTE address.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRA

AZRT
Explanation:

Module DFHZARRA has detected that the application buffer, into which it is supposed to copy some data, is invalid. This is either because the address of the buffer is zero or because its length is less than that of the data to be copied into it. This is a CICS logic error. The exception trace point that accompanies this abend code gives the buffer address and length plus the data address and length.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRA

AZRU
Explanation:

Module DFHZARRF detected an unexpected response from DFHZARR0. This is a CICS logic error. The exception trace point that accompanies this abend code gives the invalid response code.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, then a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARRF

AZRV
Explanation:

Module DFHZARR1 detected an unexpected response from DFHZARR0. This is a CICS logic error. The exception trace point that accompanies this abend code gives the invalid response code.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

One of the parameters passed to DFHZARR1

AZRW
Explanation:

Module DFHZARRA detected a negative record length in the TCTTE (field TCTELLC). This is caused either by a CICS logic error or by a storage overwrite. The exception trace point that accompanies this abend code gives the TCTTE address and the value of TCTELLC.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. Check the TCTTE in the transaction dump for printable characters or other signs of a storage violation error.

Modules:

DFHZARRA

AZRY
Explanation:

Module DFHZARR detected an unexpected response from DFHZARRC. This is a CICS logic error. The exception trace point that accompanies this abend code gives the invalid response code.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR

AZRZ
Explanation:

Module DFHZARR detected an unexpected response from an internal subroutine. This is a CICS logic error. The exception trace point that accompanies this abend code gives the invalid response code.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem determination. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR

AZR2
Explanation:

Module DFHZARRA is unable to acquire main memory for a new application buffer because the storage manager GETMAIN failed.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Use the trace to identify the failing return from the storage manager and analyze the reason for failure.

Modules:

DFHZARRA

AZR3
Explanation:

During a GETMAIN request, the storage domain detected that the task has been purged.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Use the trace to investigate why the task was purged. Check if the master terminal operator was responsible.

Modules:

DFHZARRA

AZR4
Explanation:

An unexpected response has been received from a dispatcher domain call.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARER

AZR5
Explanation:

An unexpected response has been received from a dispatcher domain call.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARR1

AZR6
Explanation:

An exception condition was raised as the result of a request from the APPC communications routine DFHZARL to the CICS recovery manager domain. This is either caused by a CICS logic error or by the inappropriate use of the indoubt test transaction, CIND. CIND should be activated only on the CICS system where the syncpoint processing was initiated. In particular, CIND should not be used on any of the CICS mirror transactions.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Determine whether CIND has been activated for a transaction that did not initiate the syncpoint processing. If CIND is not being used, you will need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZARER

AZS0
Explanation:

An invalid request was passed via the DFHZSTAM macro to the processing DFHZSTAP program. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZS1
Explanation:

No TCTTE pointer was passed via the DFHZSTAM macro to the processing DFHZ program. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZS2
Explanation:

The TCTTE passed via the DFHZSTAM macro to the processing DFHZSTAP program does not relate to an MRO or an APPC Conversation. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZS3
Explanation:

The TCTTE passed via the DFHZSTAM macro to the processing DFHZSTAP program for an APPC Conversation, but the LUC Extension Control Block was not located. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZS4
Explanation:

While processing a DFHZSTAM request in DFHZSTAP, the DFHZUSRM LUC State Machine was found to have an invalid setting. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZS5
Explanation:

Whilst processing a DFHZSTAM request in DFHZSTAP, the Internal State number was found to have an invalid setting. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZS6
Explanation:

Whilst processing a DFHZSTAM request in DFHZSTAP, the Internal State number was found to have an invalid setting. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZSTAP

AZTA
Explanation:

The task does not own a terminal as its principal facility.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTB
Explanation:

An attempt to install or delete a remote terminal in this CICS system has failed. This may be because CATA was trying to install a local terminal at the same time as CITS was installing a remote terminal with the same termid. In this situation CICS gives priority to the locally installed terminal (CATA). This abend can also occur if the CITS/CDTS/CMTS/CFTS transactions are not available (that is , if the transactions have not been installed).

System action:

DFHZTSP is abnormally terminated with a CICS transaction dump.

User response:

If there was an abend AZI6/AZTS abend in the TOR then retry the request after the locally installed terminal with the same TERMID has logged off. Otherwise, verify that the listed transactions exist and have been installed. If the failure persists then you need further assistance to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTC
Explanation:

An attempt to install or delete a remote terminal in this system has failed. This is because a short-on-storage (SOS) condition has caused the failure of a GETMAIN for the attach of CITS, CDTS, or CFTS.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason for the SOS condition. See the CICS Problem Determination Guide for guidance on dealing with the SOS condition.

Retry the transaction later.

Modules:

DFHZTSP

AZTF
Explanation:

DFHZTSP tried to GETMAIN or FREEMAIN a TCTTE whose length (TCTTETEL) is longer than the largest TCTTE SUBPOOL and is therefore invalid. This implies a storage violation or a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to identify the TCTTE in error. First, check whether this is a storage overwrite. If so, check in your statistics to see if you are getting a number of storage violations caused by the same transaction. If this is the case, then a user-supplied application is probably causing the problem.

If it is not a storage violation problem, or if there is a random storage violation, there might be an error in CICS. In this case, you need further assistance to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTG
Explanation:

An attempt has been made to attach a task on a remotely-owned terminal without an intersystem TCTTE as its principal facility.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTH
Explanation:

An error response was received from the remote terminal control macro.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

Start of change
AZTI
Explanation:

An attempt has been made to attach a task on a remotely-owned terminal, but the terminal is not defined in this system as a remotely-owned terminal.

This may occur after an AZVK abend when CICS attempts to delete the surrogate TCTTE, but there is still a transaction running against it.

Alternatively, another task holds a lock on this terminal.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the terminal control table definitions in the systems involved. If the definitions are correct, check that no other tasks have locks held on the terminal (CECI, for example).

Check to see if an AZVK abend occurred earlier for this terminal and determine if the link session timing out was the original cause. All should be well once the long running transaction finishes.

Modules:

DFHZTSP

End of change
AZTL
Explanation:

An attempt has been made to attach a task to a remotely-owned terminal that cannot be used to run this transaction.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Inform the system programmer. Check the terminal control table definitions in the systems involved.

Modules:

DFHZTSP

AZTM
Explanation:

The data received from the remote system does not contain an FMH (function management header).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTN
Explanation:

Conversation with a remote system has been unexpectedly terminated.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTO
Explanation:

The TCTTE ownership chain is in error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTP
Explanation:

A BMS TYPE=STORE request issued on behalf of a remote transaction failed.

System action:

The task abnormally terminates with a CICS transaction dump.

User response:

Inform the system programmer. Check that the required BMS support has been generated.

Modules:

DFHZTSP

AZTQ
Explanation:

Invalid BMS data received from remote system.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTR
Explanation:

A BMS TYPE=PAGEOUT request issued on behalf of a remote system failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that the required BMS support has been generated.

Modules:

DFHZTSP

Start of change
AZTS
Explanation:

An attempt to send data to a remote system failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the conversations with the remote system failed. The transaction on the remote system has probably been abnormally terminated or the session has failed.

If message 'DFHZC4930 Session unbound following read timeout.' occurred just before the AZTS then the AZTS is caused by a timeout occurring on an APPC session when CICS attempted to converse with the remote system.

Modules:

DFHZTSP

End of change
AZTT
Explanation:

An attempt was made to attach a task on a remote system, but the connection with the remote system is not an APPC or MRO connection.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Redefine the connection as APPC or MRO, or avoid using transaction routing on this connection.

Modules:

DFHZTSP

AZTU
Explanation:

The task does not own the link TCTTE after a sync point has been taken.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZTV
Explanation:

An invalid function management header (FMH) has been received from the remote system.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

Start of change
AZTW
Explanation:

An attempt was made to attach a task on a remotely-owned terminal that was already running a task.

This may be caused by a read time out occurring in the terminal owning region for the link session being used by this transaction. The read timeout is specified in profile DFHCICSS. Although the session has timed out the transaction may still be running and the surrogate TCTTE is unable to accept any more transactions until the first one has finished.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the terminal control table definitions in the systems involved.

Check to see if a read timeout abend occurred on the TOR for the same terminal to determine if this is the cause. Wait until the transaction terminates before retrying any further transactions on this terminal.

Modules:

DFHZTSP

End of change
AZTY
Explanation:

A session TCT entry for a remotely owned APPC terminal or connection could not be created because to do so would exceed the maximum number of APPC sessions permitted.

Start of changeThe maximum number of sessions depends on whether the PTF shipped for APAR PQ27823 is installed. The basic limit is 46656 and the names are in the range -AAA to -999. The APAR doubles this limit to 93312 giving an additional range of AAA- to 999-.End of change

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Inform the system programmer. Either wait for the system to become less busy, or delete some APPC sessions.

Start of changeThe system programmer should consider increasing the number of CICS TORs.End of change

Modules:

DFHZTSP

AZTZ
Explanation:

The CICS relay program DFHCRT has been attached in an unsupported manner.

System action:

CICS abnormally terminates the transaction with a transaction dump.

User response:

The relay transaction executes with an MRO session or an LU type 6.2 conversation as its principal facility. Ensure that the transaction is being attached by APPC terminal sharing logic and not directly by a user transaction.

If the transaction is being attached by APPC terminal sharing logic, you need further assistance to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZT1
Explanation:

The task has been attached improperly in the application-owning region when transaction routing.

System action:

CICS abnormally terminates the transaction with a transaction dump.

User response:

The conversation with the routing system should be an MRO session or an LU type 6.2 conversation. Ensure that the transaction is being attached by the CICS relay program in the connected system and not by a user program.

If the transaction is being attached by the CICS relay program in the connected system, you need further assistance to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZT3
Explanation:

The task is being routed back to the region from where it came.

System action:

CICS abnormally terminates the transaction with a transaction dump.

User response:

Correct the transaction definition.

Modules:

DFHZTSP

AZT6
Explanation:

The task in the application-owning region has received a ROLLBACK request from the terminal-owning region, but the conversation is continuing. The terminal-owning region has violated the transaction routing protocol.

System action:

CICS abnormally terminates the transaction with a transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZT7
Explanation:

A session terminal control table (TCT) entry for a remotely owned APPC terminal or connection could not be added to the TCT.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZT8
Explanation:

A session terminal control table (TCT) entry for a remotely owned APPC terminal or connection could not be deleted from the TCT.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZTSP

AZT9
Explanation:

A session terminal control table (TCT) entry for a remotely owned APPC terminal or connection could not be deleted from the TCT because it is locked by another task.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

The other task may be transitory in nature, and if so, another attempt will succeed.

Modules:

DFHZTSP

AZVA
Explanation:

DFHZTSP has timed out waiting for service transaction CITS to complete during the creation of a remote terminal while attaching a task in the application-owning region.

The probable cause of this is that the application-owning region is very busy, so the CITS transaction has been waiting to be dispatched for longer than the timeout value allowed by DFHZTSP. Lack of storage on the target system is one possible reason why CITS has not been dispatched, or has been dispatched but has not completed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Retry the transaction when the system becomes less busy. For more information on improving transaction throughput on the target system, see the CICS Performance Guide.

Modules:

DFHZATS

AZVB
Explanation:

DFHZCQ has failed to create the remote terminal definition. A previous message or messages should indicate the reason for the failure.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the previous message or messages for further guidance.

Modules:

DFHZATS

AZVC
Explanation:

An unexpected error has occurred in DFHZATS. This is probably caused by DFHZATS being unable to address the CSA, EIB or the TCA. It can also occur if DFHZATS is called with an EXEC CICS START command for transactions CITS, CFTS, CMTS or CDTS. These are internal CICS transactions and should not be called in this way.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZVD
Explanation:

An unexpected error has occurred in the install procedure of DFHZATS.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

This is a CICS logic error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZVE
Explanation:

DFHZATS is trying to install a remote terminal with the same terminal id as an existing TCT entry.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Change the terminal names to ensure that a duplicate does not occur in the same system.

Modules:

DFHZATS

AZVF
Explanation:

One of the remote install or delete transactions of DFHZATS (CITS, CFTS, CMTS or CDTS) has been started directly from a terminal. This is not permitted. These transactions can only be started internally by CICS.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

None.

Modules:

DFHZATS

AZVG
Explanation:

An error has occurred in the remote delete routines.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZVH
Explanation:

An error has occurred in the remote delete routine during the mass deletion of remote terminals.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZVI
Explanation:

An error has occurred in the remote delete routine while an attempt was being made to delete a single remote terminal.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the CADL transient data queue for any associated messages indicating the reason for the error. If you cannot resolve the problem, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZVJ
Explanation:

An error has occurred during the mass deletion of remote terminals. This is caused by a CICS logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

Start of change
AZVK
Explanation:

An unexpected return code has been received from the remote delete routine during the deletion of a single remote terminal.

This may occur after an AZTW abend when CICS attempts to delete the surrogate TCTTE, but there is still a transaction running against it. It may also occur without an AZTW if the link session timed out leaving the transaction in the AOR still running but followed by a logoff from the terminal which initiated the long running transaction.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Look for an accompanying DFHZC6911 message indicating the reason for the delete failure, and take appropriate action.

Check to see if the link session for this terminal timed out and whether the terminal then issued another transaction or logged off. All should be well once the long running transaction finishes.

Modules:

DFHZATS

End of change
AZVL
Explanation:

An error has occurred during the mass flagging of remote terminals for deletion.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZVM
Explanation:

An error has occurred in DFHZATMF. This is probably caused by DFHZATMF being unable to address the CSA, EIB, or the TCA.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATMF

AZVN
Explanation:

The remote delete flag transaction of DFHZATMF (CRMF) has been started directly from a terminal. This is not permitted. This transaction can only be started internally by CICS.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

None.

Modules:

DFHZATMF

AZVO
Explanation:

The remote delete transaction of DFHZATMD (CRMD) has been started directly from a terminal. This is not permitted. This transaction can only be started internally by CICS.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

None.

Modules:

DFHZATMD

AZVP
Explanation:

An error has occurred in DFHZATMD. This is probably caused by DFHZATMD being unable to address the CSA, EIB, or the TCA.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATMD

AZVQ
Explanation:

A request to install a shipped terminal definition has been rejected by the autoinstall user program.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Retry the transaction when the system is less busy.

Modules:

DFHZATS

AZVR
Explanation:

An attempt to install a shipped terminal definition has failed because the autoinstall user program has issued an unexpected return code.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the autoinstall user program to determine why this return code was issued.

Modules:

DFHZATS

AZVS
Explanation:

An attempt to install a shipped terminal definition has failed because an error has occurred in the autoinstall user program.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the autoinstall user program to determine the reason for the failure.

Modules:

DFHZATS

AZVU
Explanation:

DFHZATS was attempting to autoinstall a shipped terminal, a virtual terminal or a shipped connection and the autoinstall URM was called. However the autoinstall failed for one of the following reasons:

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZATS

AZXA
Explanation:

An unexpected error, with reason code 5, has been detected in the catchup program, DFHZXCU. See the description of message DFHXG6492 for further details.

System action:

Console message DFHXG6492 is issued, and CICS continues after abending the transaction.

User response:

Refer to message DFHXG6492.

Modules:

DFHZXCU

AZXB
Explanation:

An unexpected error, with reason code 4, has been detected in the catchup program, DFHZXCU. See the description of message DFHXG6492 for further details.

System action:

Console message DFHXG6492 is issued, and CICS continues after abending the transaction.

User response:

Refer to message DFHXG6492.

Modules:

DFHZXCU

[[ Contents Previous Page | Next Page Index ]]