CICS ABEND CODES

AACA

Explanation: An invalid error code has been passed to the DFHTFP or DFHACP programs.

System Action: CICS terminates the task abnormally with a dump.

User Response: Notify the system programmer.

Module: DFHTFP,DFHACP

AALM

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the log manager (LM) 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.

Module: DFHAMLM

AALN

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the TD manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMTD

AALO

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the CICS/DB2 table manager DFHD2TM. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMD2

AALP

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Program Manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMPG

AALQ

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Business Application Manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMBA

AALR

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Temporary Storage Manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMBA

AALS

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Global Enqueue Manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMBA

AALT

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Internet Inter-Orb Protocol Manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMOP

AALU

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Sockets Domain Manager. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMSO

AALV

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the Enterprise Java Domain. The domain that detected the original error provides a trace entry 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: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMEJ

AAL1

Explanation: DFHALP was processing a request that deadlocked. The most likely reason for the abend is that an ALLOCATE QUEUE request has been suspended because there are no contention-winning links available. AAL1 is issued for non time-out related deadlocks, for instance the task may have been cancelled. AAL8 is issued for stall purges and deadlock time-outs.

System Action: CICS terminates the task abnormally. A dump is taken.

User Response: Ensure that there are enough contention-winning sessions available to satisfy the ALLOCATE QUEUE request.

If you are running with modegroups, ensure that there are contention-winning sessions available to satisfy the ALLOCATE request in that modegroup.

Module: DFHALP

AAL2

Explanation: Either an incorrect response (other than PURGED) was returned from the suspend of the allocated task, or an incorrect response was

returned from the resume.

System Action: The transaction is abnormally terminated with a dump.

User Response: Check the return code from the resume or the suspend to determine the cause of the error.

Module: DFHALP

AAL3

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 the reason why the task was purged. It was purged either by the master terminal operator or as a result of a deadlock timeout.

Module: DFHALP

AAL4

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.

Module: DFHALP

AAL6

Explanation: An error (INVALID, DISASTER or EXCEPTION response) has occurred on a call to SIGNOFF_TERMINAL_USER by DFHALP during sign-off for a surrogate terminal session running CRTE. 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.

Module: DFHALP

AAL7

Explanation: An error (INVALID, DISASTER or EXCEPTION response) has occurred on a call to schedule a remote terminal delete by DFHALP during sign-off for a surrogate terminal session running CRTE. 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.

Module: DFHALP

AAL8

Explanation: DFHALP was processing a request that deadlocked. The most likely reason for the abend is that an ALLOCATE QUEUE request has been suspended because there are no contention-winning links available. AAL1 is issued for non time-out related deadlocks. AAL8 is issued for stall purges and deadlock time-outs.

System Action: CICS terminates the task abnormally. A transaction or system dump is not taken unless the transaction dump table has been modified for AAL8.

User Response: Ensure that there are enough contention-winning sessions available to satisfy the ALLOCATE QUEUE request. If you are running with modegroups, ensure that there are contention-winning sessions available to satisfy the ALLOCATE request in that modegroup.

It might be necessary to increase the deadlock timeout (DTIMEOUT) value for the transaction to prevent this abend from recurring.

If you require a transaction or system dump for this abend then add AAL8 to the transaction dump table.

Module: DFHALP

AAMA

Explanation: There is an internal logic error in DFHAMP.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMC

Explanation: The task was purged before a GETMAIN request to the storage manager domain was able to complete successfully.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Module: DFHAMP

AAMD

Explanation: An unexpected return code has been received from DFHDMP. This is due to an internal 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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMF

Explanation: An unexpected return code has been received following a call to the kernel (KE) domain. This might be due to an internal logic error.

System Action: CICS terminates the task abnormally with a dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMH

Explanation: An unexpected return code has been received following a call to DFHFCMT. This might be due to an internal logic error.

System Action: CICS terminates the task abnormally with a dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMI

Explanation: An unexpected return code has been received following a call to DFHFCRL. This might be due to an internal logic error.

System Action: CICS terminates the task abnormally with a dump. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMJ

Explanation: While installing a file, using RDO, a call was made to DFHFCFS to enable the file. An irrecoverable error was returned from DFHFCFS.

System Action: The task is abnormally terminated with a CICS transaction dump.

At the time the error is detected, CICS writes a message to the console, records an exception trace entry and takes a system dump.

User Response: Inform the system programmer. Examine the trace and the dump to identify the point of error.

Module: DFHAMP

AAMK

Explanation: While installing a file, using RDO, a call was made to DFHFCDN. An irrecoverable error was returned from DFHFCDN.

System Action: The task is abnormally terminated with a CICS transaction dump. At the time the error is detected, CICS writes a message to the console,

records an exception trace entry, and takes a system dump.

User Response: Inform the system programmer, Examine the trace and dump to identify the point of error.

Module: DFHAMP

AAMN

Explanation: There has been an unexpected return code from a call to DFHPRPT. This might be due to an internal 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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMO

Explanation: An invalid return code was returned from DFHTOR, the CICS terminal object resolution program.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMP

Explanation: An unexpected return code has been received from DFHPUP. This might be due to an internal 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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMQ

Explanation: An attempt has been made to install a partner using RDO. However, the partner resource manager (PRM) is unavailable having failed to

initialize during CICS initialization.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: If you need to use the PRM, correct the problem which prevented the PRM from initializing, and restart CICS.

Module: DFHAMP

AAMS

Explanation: There has been an unexpected return code following a GETMAIN request to the storage manager. This is due to an internal 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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMT

Explanation: There is an internal logic error in DFHAMP due to an unexpected return code from DFHTMP.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAMZ

Explanation: An unexpected return code has been received from DFHZCP. This is due to an internal 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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHAMP

AAM1

Explanation: DFHXMCL has returned an unexpected response during the install of a transaction class. This can be caused by the task being purged during the install.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

If an error has occurred, at the time the error is detected, CICS issues a DFHXMnnnn console message, records an exception trace entry and takes a system dump.

User Response: Determine why the task has failed. If there is a system dump, use it together with the trace entry and the console message to resolve the problem. If there is no system dump, the task has been purged either by the master terminal operator or as a result of deadlock timeout.

Module: DFHAMP

AAM2

Explanation: DFHXMXD has returned an unexpected response during the install of a transaction definition. This can be caused by the task being purged during the install.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

If an error has occurred, at the time the error is detected, CICS issues a DFHXMnnnn console message, records an exception trace entry and takes a system dump.

Module: DFHAMP

AAOA

Explanation: An application has issued a CPI verb which CICS does not support. The entry point referenced in the application program was resolved in the link edit stub, but the function requested could not be resolved when control passed to CICS.

There are two possible reasons for this: You have linkedited your application program with a CPI stub which supports more function than this release of CICS. The linkedit stub has been corrupted.

System Action: The transaction is abnormally terminated with a CICS transaction dump. An exception trace entry is also written.

User Response: At the time of the error, general register 0 points to an 8-byte character string which should match the name of the issued CPI call. Use the trace or the dump to verify that this character string is the name of a CPI function which is supported.

If the character string is not an intelligible character string, the stub has probably been corrupted.

Module: DFHCPI

AAOB

Explanation: An application has issued a CPI verb which specifies more than eight parameters.

System Action: The transaction is abnormally terminated with a CICS transaction dump and an exception trace entry is also written.

User Response: Change your application program so that the correct number of parameters is specified on the CPI call.

Module: DFHCPI

AAOC

Explanation: CPI Communications is invoked with an invalid number of parameters for call

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: The exception trace point produced with this abend contains the incorrectly issued CPI Communications verb name. Use this to determine where the application program was in error and amend it accordingly.

The SAA CPI Communications Reference manual, SC26-4399, provides a detailed description of all the CPI Communications verbs and how they should be called.

Module: DFHCPARH

AAOD

Explanation: The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain 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 the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Module: DFHCPCBI

AAOE

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Module: DFHCPCBA

AAOF

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the reason the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Module: DFHCPCBS

AAOG

Explanation: During the processing of CMACCP (accept conversation), CPI Communications detected that the application was attached with an

unsupported sync level.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: This condition is caused by a back-end CPI Communications transaction being attached with a sync level that is not CM_NONE (0) or CM_CONFIRM (1).

Change the front-end transaction, (that is, the initiator of the conversation in the other system) so that it defines the sync level correctly.

Module: DFHCPCBA

AAOH

Explanation: Journaling of data sent on a CPI communications mapped conversation has failed. This condition is caused by a nonzero response from the CICS log manager.

Problem Determination: Register 12 addresses the current TCA and field TCAJCAAD and register 4 address the JCA. The log manager request is

contained in JCATR2 and the response code is in JCAJCRC.

Possible request codes are:

X'8001' - WRITE

X'8003' - PUT

Possible response codes are:

X'01' - IDERROR - Journal identification error

X'02' - INVREQ - Invalid request

X'03' - STATERR - Status error

X'05' - NOTOPEN - Journal not open

X'06' - LERROR - Journal record length error

X'07' - IOERROR - I/O error.

The address of the TIOA is contained in register 8 and its data length is in TIOATDL.

Analysis:

R4=@JCA TCZARQPJ JCAJCRC is nonzero.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Use the dump to ascertain why the journal or log record could not be written correctly. If a journal record length error is indicated, TIOATDL

may have been corrupted.

Module: DFHCPCOJ

AAOI

Explanation: The journaling of data received on a CPI Communications mapped conversation has failed.

Problem Determination: Register 12 addresses the current TCA and field TCAJCAAD and register 4 address the JCA. The CICS log manager request is

contained in JCATR2 and the response code is in JCAJCRC.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: This condition is caused by an invalid response from the log manager. Use the dump to ascertain why the journal or log record could not be

written correctly. If a journal record length error is indicated, TIOATDL may have been corrupted.

Modules: DFHCPCRI, DFHCPCRW

AAOJ

Explanation: CPI Communications has detected an unexpected response from one of its internal routines.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events prior to this error. For example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

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

Module: DFHCPIC

AAOK

Explanation: CPI Communications has detected an unexpected call to one of its internal routines.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace also provides details of the error itself.

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

Module: DFHCPIC

AAOL

Explanation: CPI Communications has made an invalid call to DFHLUC.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCLR

AAOM

Explanation: The CPI Communications and the DFHZUSR state machines are out of synchronization.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Modules: DFHCPCLR, DFHCPSRH

AAON

Explanation: CPI Communications has detected an unexpected response from DFHLUC.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Modules: DFHCPCLR, DFHCPCLC

AAOO

Explanation: CPI Communications has been invoked 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: A level 2 trace for 'CP' of the transaction shows the course of events before this error occurred (such as the modules called and their parameters) plus details of the error itself.

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

Module: DFHCPARH

AAOP

Explanation: The CPI Communications state machine has been requested to perform a state transition request that is considered to be an 'impossible'

situation. (The SAA CPI Communications Reference manual, (SC26-4399) documents all these situations.)

There are two possible causes of this error:

The CPC (conversation control block) has been overwritten in such a way that the conversation state has been altered, or

There is an error in the CPI Communications state machine.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: A level 2 trace for 'CP' of the transaction shows the course of events prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

The transaction dump shows the CPC. You may need further assistance from IBM to fully resolve this problem. You need further assistance from IBM to

resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCFS

AAOQ

Explanation: The return code generated by CPI Communications does not have an entry in the state table against the current CPI Communications verb.

This error is detected by the CPI Communications state machine.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCFS

AAOR

Explanation: CPI Communications has detected an invalid value in the CPC (conversation control block).

There are 2 possible causes of this error:

The CPC (conversation control block) has been overwritten, or

There is an error in CPI Communications which causes it to reject valid values.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: A level 2 trace for 'CP' of the transaction shows the course of events prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

Module: DFHCPIC

AAOS

Explanation: CPI Communications has detected that the conversation state is RESET for a situation where this should not occur. That is, the conversation

control block (CPC) is about to be deleted.

There are two possible causes of this error:

The CPC has been overwritten, or There is an error in CPI communications.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: A level 2 trace for 'CP' of the transaction shows the course of events prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself. You may need further assistance from IBM to fully resolve this problem. You need further

assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPIC

AAOT

Explanation: While chaining through the CPCs (conversation control blocks) for a given conversation, CPI Communications detected that the chain was broken.

There are two possible causes of this error.

1. The CPC chain has been overwritten, or

2. There is an error in the CPI Communications chaining mechanism.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Determine which of the above caused the error.

You may need further assistance from IBM to fully resolve this problem. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCBI

AAOU

Explanation: CPI Communications has detected an error in the TP_name or partner_LU_name while processing an initialize conversation request. The TP_name or partner_LU_name is obtained by lookup of the sym_dest_name in the partner resource table (PRT).

There are two possible causes of this error.

1. The entry in the PRT contains invalid data, or

2. There is an error in the mechanism that returns the data from the PRT and interprets it.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: A level 2 trace for 'CP' of the transaction shows the course of events prior to this error, for example, the modules called and their

parameters. The level 2 trace also provides details of the error itself.

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

Module: DFHCPCBI

AAOV

Explanation: CPI Communications has detected that its internal state table is corrupted.

This error is detected by the CPI Communications state machine.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: This is a CICS internal logic error.

A level 2 trace for 'CP' of the transaction shows the course of events prior to this error, for example, the modules called and their parameters. The level 2 trace

also provides details of the error itself.

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

Module: DFHCPCFS

AAOW

Explanation: CPI Communications has detected an internal logic error in DFHCPCLC.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCLC

AAOX

Explanation: CPI Communications has detected a bad syncpoint return code which has been set on a synclevel 0 or 1 conversation. The bad return code is only expected on a synclevel 2 conversation.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPIC

AAOY

Explanation: CPI Communications detected an invalid LL field in the GDS records from which it was receiving on a mapped conversation.

Although it is possible that the remote system is sending invalid records, it is more likely to be an error in the receive logic because DFHZARRC (a lower level receive module) also checks the LLs before passing them to CPI Communications.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Use CICS traces and, possibly a VTAM trace, to determine the data that was sent between both systems.

A level 2 CICS trace for 'CP' of the transaction documents the course of events prior to this error (such as the modules called and their parameters). The level 2 trace also provides details of the error itself.

Module: DFHCPCRB

AAOZ

Explanation: CPI Communications has detected an invalid ID field in the GDS records it was receiving on a mapped conversation. The exception trace point that accompanies this abend gives the ID field in data 3. The valid IDs are '12FF'X for application data and '12F1'X for null data.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Use CICS traces and, possibly, a VTAM trace to determine the data that was sent between both systems.

Module: DFHCPCRB

AAO2

Explanation: CPI Communications has detected an unexpected response from DFHLUC.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCBA

AAO3

Explanation: The CPI interface detected that a call was made to a CPI Communications function without CPI Communications being initialized. This implies that CPI Communications initialization failed while CICS was initializing.

System Action: The transaction is abnormally terminated with a CICS transaction dump. An exception trace entry is also written when this event occurs.

User Response: Check the console listing to determine the reason why CPI Communications failed to initialize during CICS initialization. Correct the

problem and restart CICS.

If the console listing indicates that CPI Communications initialized successfully, you need further assistance to resolve the problem. Collect the console

listing, the traces and the transaction dump. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPI

AAO4

Explanation: DFHZARL, or a module called by DFHZARL, has detected a logic error. This error is almost certainly caused by the module receiving invalid

data or indicators from VTAM.

System Action: Before returning to the CPI Communications layer, DFHZARL calls DFHZNAC to clean up the session and put out messages on the CSNE

log. CPI Communications abnormally terminates the transaction with a CICS transaction dump, and produces an exception trace entry.

User Response: Check the CSNE log to determine the type of error. You may need further assistance from IBM to fully resolve this problem. You need

further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCPCLR

AAO5

Explanation: The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain 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 the reason why the task was purged. It was purged either by the master terminal operator or as a result of deadlock timeout.

Modules: DFHCPCBA, DFHCPCBI, DFHCPCBS

AAO7

Explanation: The CPI Communications syncpoint request handler has been passed an invalid DFHLUC parameter list. This is a CICS internal logic error.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: A level 2 trace for 'CP' of the transaction shows the course of events before this error occurred (such as the modules called and their

parameters) plus details of the error itself. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination

Guide for guidance on how to proceed.

Module: DFHCPSRH

AAO8

Explanation: The CPI Communications syncpoint request handler has been passed an invalid conversation control block (CPC). This is a CICS internal

logic error.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: A level 2 trace for 'CP' of the transaction shows the course of events before this error occurred (such as the modules called and their

parameters) plus details of the error itself. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination

Guide for guidance on how to proceed.

Module: DFHCPSRH

AAO9

Explanation: A task has been 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.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate why the task was purged.

If the task was purged by the master terminal operator, 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, the number of tasks in the system should be reduced to avoid

short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Module: DFHCPCLR

ABAC

Explanation: An activity issued EXEC CICS RETURN (without the ENDACTIVITY option) but no events were processed during the activation. The activity

was executed with a RUN command.

System Action: The task is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this abend.

User Response: Investigate why the activity did not process any events.

Module(s): DFHBASP

ABAD

Explanation: An activity issued EXEC CICS RETURN ENDACTIVITY while there were activity completion events pending. The activity was executed with a

RUN command.

System Action: The task is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command cannot handle this abend.

User Response: Investigate why the activity had pending activity completion events.

Module(s): DFHBASP

ABAE

Explanation: An activity issued EXEC CICS RETURN (without the ENDACTIVITY option) but no events were processed during the activation. The activity

was executed with a LINK command.

System Action: The task which issued the LINK is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command

cannot handle this abend.

User Response: Investigate why the activity did not process any events.

Module(s): DFHEIBAM

ABAF

Explanation: An activity issued EXEC CICS RETURN ENDACTIVITY while there were activity completion events pending. The activity was executed with a

LINK command.

System Action: The task which issued the LINK is abnormally terminated with a CICS transaction dump. The EXEC CICS HANDLE ABEND command

cannot handle this abend.

User Response: Investigate why the activity had pending activity completion events.

Module(s): DFHEIBAM

ABLA

Explanation: The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The domain 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 by the master terminal operator or as a result of deadlock timeout.

If the task was purged by the master terminal operator, 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, the number of tasks in the system should be reduced to avoid

short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR

ABLB

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 in the dump

table).

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Please see the related message produced by the domain that originally detected the error.

Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR

ABMA

Explanation: The user has supplied a terminal I/O area (TIOA) with an invalid data length that was either equal to zero or greater than the storage

accounting length minus 12.

Alternatively, the length field of a header or trailer area provided by the application program is invalid (that is, not positive).

Problem Determination: The output services work area (OSPWA) is in user storage and will be printed in a transaction dump. It is addressed by register 2

at the time of the abend. Relevant fields are:

OSPTR7

OSPHDRA

OSPTRLA

TIOATDL

TIOASAL

Analysis:

R4=@TIOA PBCKTDL TIOATDL is zero or greater

than TIOASAL-12.

R2=@OSPWA PBD20080 R0 (= first halfword of

R0=length trailer) is zero.

of trailer R8=OSPTRLA.

R8=@trailer OSPTR7 has X'20' bit set.

R2=@OSPWA PBDTXHDR R0 (= first halfword of

R8=@header header) is zero.

R0=length R8=OSPHDRA.

of header. OSPTR7 has X'40' bit set.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Correct the program that supplied the erroneous data length.

Check the TIOA. If either of the conditions described is present, check the application program. For programs using command-level interface, the TIOA is

obtained by CICS using the length of the data item passed in the FROM option on an EXEC CICS SEND MAP or EXEC CICS SEND TEXT command, or in

the TRAILER or HEADER option on an EXEC CICS SEND TEXT or an EXEC CICS SEND PAGE command. Check the data item for zero length.

Header and trailer records have a special format described in the CICS Application Programming Reference. An ABMA abend occurs if the first halfword (the

length) is not positive. Check the remainder of the header/trailer record for validity when the length is checked.

Modules: DFHPBP, DFHMCP

ABMB

Explanation: The user has specified a cursor position in the BMS output request. It is larger than the current screen size for the 3270 for which output is

being built.

Problem Determination: If the abend occurs in DFHPBP:

At the time of the abend, register 2 points to the OSPWA and register 1 to the TTP. Relevant fields are:

OSPTR3 has X'10' bit set to indicate a user-specified cursor position

OSPCP contains a halfword cursor position specified by user

TTPSCSZ contains the halfword value of the screen size to compare against.

If the abend occurs in DFHMCP or DFHMCX:

OSPCP contains a halfword cursor position specified by user

OSPTR3 has X'10' bit set to indicate a user-specified cursor position

OSPSCSZ contains the halfword value of the screen size to compare against.

Analysis:

In DFHPBP:

R2=@OSPWA PBDBADC OSPTR3 X'10' bit set

indicates the user-

R1=@TTP specified cursor

position.

TTPSCSZ halfword screen

size.

OSPCP halfword cursor

position.

In DFHKCP or DFHMCX:

R6=@OSPWA MCENEAU2 OSPTR3 X'10' bit set

indicates the user-

specified cursor

position.

OSPSCSZ halfword screen

size.

OSPCP halfword cursor

position.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Correct the program that specified the incorrect cursor location.

Use trace to identify the statement issuing the request. Check that the cursor position is being correctly set. The program may have been designed to run in

alternate screen size mode but is being run in default screen size mode, or it may have been designed to run on a 3270 model different from the one in use. If

the program is routing a message, the route list should be checked. If the program is to run with various 3270 models, the cursor position should be within

the size of the smallest screen.

Modules: DFHPBP, DFHMCP (for minimum-function BMS), DFHMCX

ABMC

Explanation: The CMSG transaction is attempting to send a message to a greater number of terminals than is possible. There is no fixed maximum

because the value depends on the other operands specified on the routing command.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Redefine the route list.

Module: DFHMCP

ABMD

Explanation: DFHTPR or DFHTPP has issued a DFHDI TYPE=SEND and has received a return code other than "FUNCERR-REQUEST FOR CHANGE

DIRECTION SIGNALED" or "NORESP"

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Inform your system programmer.

Modules: DFHTPP, DFHTPR

ABME

Explanation: DFHTPR or DFHTPP has detected an invalid datastream or DFHWBBMS detected invalid forms data while processing a basic mapping

support (BMS) request.

System Action: The transaction is abnormally terminated with a CICS transaction dump. If the ABEND was issued from DFHTPR or DFHTPP then register

7 indicates the location at which the ABEND was detected.

User Response: If DFHTPR or DFHTPP issued the ABEND then examine the transaction dump for bad data in the TIOA. If the origin of the bad data is an

application program, correct the program. If DFHWBBMS issued the ABEND then check the validity of the incoming forms data in the CICS trace.

Modules: DFHTPP, DFHTPR, DFHWBBMS

ABMF

Explanation: The value specified for the length option of the basic mapping support (BMS) send map is greater than the length of the 'from' area.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Redefine the value for the length option.

Module: DFHPBP

ABMG

Explanation: The user has requested a basic mapping support (BMS) service that was not specified at system generation, or at initialization.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Correlate services requested against options specified in the system generation of BMS.

Follow this procedure:

1. Scan the trace table for the transaction ID that issued the abend. If this is CSPQ (page cleanup), module DFHTPQ abnormally terminated because a

message purge delay of zero has been specified and CSPQ has been entered via a terminal. The message purge delay is specified in the PRGDLAY of

the DFHSIT macro, and its value can be found in SITPRGD.

2. Scan the trace table for the last BMS request (code 'FA'). Use the option bytes at the start of the failing module to see if the requested functions have

been generated. For example, paging may have been requested, but standard or minimum BMS was specified in the SIT.

3. If the BMS request is compatible with the BMS options in the CICS system generation, some incompatible suffixing amongst BMS modules must have

occurred. This can happen if the DFHSIT macro specified individual suffixes for the BMS modules.

The following modules differ between standard and full-function BMS:

DFHMCP

DFHRLR

DFHPBP

DFHTPP

Modules: DFHMCP, DFHTPQ

ABMI

Explanation: The map specified for a BMS input mapping request was not an input map.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Either define another input map or redefine the existing map.

Modules: DFHMCP, DFHMCX, DFHMCY

ABML

Explanation: The terminal control locate routine received invalid data from DFHRLR and returns with an error return code. DFHRLR is attempting to scan the

TCT for a BMS ROUTE request with LIST=ALL or operator class or operator ID specified in the route list. The terminal control table may have been corrupted.

Problem Determination: Register 11 points to the current TCTTE in the search.

The TCT prefix (DFHTCTFX) can be located from CSATCTBA.

The first terminal entry (TCTTE) in the TCT is addressed by TCTVTEBA.

TCTTETEL is the halfword offset from current TCTTE to the next.

Analysis: The current TCTTE address is either not on a full-word boundary or is not within the limits of the TCT, or the address of the next TCTTE, obtained

by adding TCTTETEL to the current address, is invalid. This check is made by locate code (DFHZLOC) in DFHZCX.

R11=@TCTTE RLRLOCN Issue DFHTC CTYPE=LOCATE

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

The terminal control table has probably been corrupted during execution. Attempt to scan through the TCT in a dump. (Because the system dump uses the

same technique for printing all TCTTEs, the system dump fails at the same point.)

Determine which entry is incorrect. It may be that the TCTTE has been overwritten by user data that is recognizable in the dump.

Check the application program for references to the TCTTE pointer. Check for user data that may be addressed from the same pointer.

In an assembler program, there may be multiple equates for the TCTTE base register.

It may be that the TCT is being overwritten by some earlier transaction. If this is so, it is probably one associated with the terminal whose TCTTE is

overwritten.

Modules: DFHRLR for full-function BMS

ABMM

Explanation: An invalid map was specified.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Use the supplied dump to diagnose the problem. Register 6 contains the address of the BMS instruction being executed when the error

was recognized.

Module: DFHPBP

ABMO

Explanation: The map specified for a BMS output mapping request was not an output map.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Either define another output map or redefine the existing map.

Modules: DFHMCP, DFHMCX, DFHMCY

ABMQ

Explanation: The query transaction (CQRY) has been initiated and either the task is not terminal-oriented, or the associated terminal is not defined to CICS

as a 3270 or SCSPRINT device. This abend will occur if CQRY is entered at a console, even when the console is a 3270 device, since the console has the

appearance to CICS of a keyboard/printer device. The CQRY transaction does not have an operator interface, and under normal conditions there is no need

for an operator to invoke CQRY or for a user transaction to START the CQRY transaction. CQRY is run automatically by CICS when a 3270 or SCSPRINT

device connects. In the transaction dump, register 8 contains the address of the TCTTE for the associated terminal. If register 8 contains zero, this indicates

that the task is not terminal-oriented.

System Action: The task is abnormally terminated with a CICS dump.

User Response: Ensure that the terminal associated with CQRY is of the 3270 or SCSPRINT family of devices.

Module: DFHQRY

ABMR

Explanation: The Page Retrieval transaction (CSPG) has been initiated but the task is not terminal-oriented.

System Action: The task is abnormally terminated with a CICS dump.

User Response: Ensure that a terminal is associated with the CSPG transaction.

Module: DFHTPR

ABMU

Explanation: The application program supplied an address that is not within region boundaries. The low-order 3 bytes of general register 1 in the transaction

dump contain the erroneous address. The high-order byte of register 1 indicates the address type as follows:

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Correct the application program that is supplying the erroneous address.

Modules: DFHMCP, DFHEMS

ABMV

Explanation: DFHRLR has detected an invalid route list entry.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check that the route list is correctly built with reserved field in the entry containing blank and a stopper of halfword X'FFFF' to terminate the

list.

Module: DFHRLR

ABMX

Explanation: A text string passed to BMS contained a set attribute order that was invalid for one of the following reasons:

1. The set attribute sequence was less than three characters.

2. The attribute type was invalid.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Correct the application program.

Module: DFHPBP

ABMY

Explanation: BMS is building a TTP (Terminal Type Parameter) control block but the pagesize selected for a terminal by BMS is zero because either the

default or alternate screensize has been defined as zero.

In the transaction dump, significant general purpose register contents are as follows:

1. Register 6 points to the BMS extension of the TCTTE

2. Register 10 points to the TTP (Terminal Type Parameter) control block

3. Register 11 points to the TCTTE

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check the TERMINAL and TERMTYPE definitions which determined the attributes of the offending TCTTE.

Module: DFHRLR

ABMZ

Explanation: The address of the terminal I/O area (TIOA) in TCTTEDA was found to be zero.

When using BMS fast path as a result of an EXEC CICS RECEIVE MAP, DFHEMS always initializes TCTTEDA with the address of the TIOA. If TCTTEDA is

subsequently found to be zero by DFHMCX, an overwrite must have occurred.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Investigate why TCTTEDA is zero.

Scan the trace table for the last BMS request (code FA) for the failing task and try to determine which user programs have been given control since that BMS

request.

Modules: DFHMCP, DFHMCX, DFHMCY

ABM0

Explanation: The map specified for a basic mapping support (BMS) request could not be located.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check if the map has been defined. If it has, check that it has been specified correctly.

Modules: DFHMCP, DFHMCX, DFHMCY

ABM1

Explanation: A basic mapping support (BMS) service is requested by a task associated with a terminal that is not supported by BMS. The request is not a

routing request.

Problem Determination: At the time of the abend, register 11 addresses the TCTTE, and TCTTETEA and register 6 address the TCTTE extension,

TCTETTE.

Relevant fields are:

TCTTEDDS the device dependent suffix.

TCTTEMSS the map set suffix.

Analysis: DFHRLR tests the device dependent suffix and the map set suffix in the TCTTE extension. If both of these are zero, the terminal is not supported

by BMS and DFHRLR abends the task with the abend code ABM1.

R4= RLRSFXCK TCTEDDS=X'00' and

TCTEMSS=X'00'.

@TCTTETE The device dependent suffix

and the map set suffix have

loaded into the lower two

bytes of register 3 by the

subroutine RLRSUFXS.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Do not use terminals not supported by BMS for applications using BMS services.

Check the terminal type and model number. Confirm that it is a terminal that is not supported by BMS. A list of terminals supported by BMS is given in the

CICS Application Programming Guide. Check that the TCT macro for the terminal accurately describes the physical terminal.

Module: DFHRLR

ABM2

Explanation: No user data was supplied for this BMS request. That is, the address of a user data area was not found in either TCTTEDA or TCAMSIOA.

When a BMS macro level output request is issued, the user must have placed the address of the data to be passed to BMS in TCTTEDA or TCAMSIOA

before issuing the macro. The choice is made on the following criteria:

If the data is to be passed in a TIOA by a terminal-oriented task, the address of this TIOA may be placed either at TCTTEDA, or in TCAMSIOA together

with the setting of binary zeros into TCTTEDA.

If the data is being passed by a terminal-oriented task but not in a TIOA, the address of the TIOA-like area of this data must be placed in TCAMSIOA and

binary zeros set into TCTTEDA.

If the data is being passed by a non-terminal-oriented task, the address of the TIOA-like area of this data must be placed in TCAMSIOA. TCTTEDA

cannot be referenced, because there is no TCTTE associated with this task.

If a task attempts to pass addresses from both TCTTEDA and TCAMSIOA, the address in TCTTEDA is the one selected.

Problem Determination: The output services work area (OSPWA) is addressed by register 9. The TCTTE is addressed by register 11. The TCA is

addressed by register 12.

The relevant fields are:

Field Description

OSPIND01 OSPWA indicator byte 1

OSPIOA Alternate I/O area address

OSPSIOA Address of address of data (TCTTEDA/TCAMSIOA)

OSPTIOA Address of user data found by BMS

OSPTR1-8 BMS request data saved from the TCA

TCTTEDA Terminal data area address

TCAFCI Facility control indicator

TCAMSIOA Alternate I/O area address

Analysis: The ABM2 abend is invoked at one point in DFHMCP, at label MCPABEND. There are five regions in DFHMCP in which the user's data is sought:

Labels

TYPE=MAP MCPMAP

TYPE=PAGEBLD,DATA=YES/ONLY MCPPGBLD

MCPGTIOA

TYPE=TEXTBLD,DATA=YES/ONLY MCPPGBLD

MCPGTIOA

Mapping but not PAGEBLD,DATA=YES/ONLY MCPMAPNG

No (mapping,PAGEBLD,TEXTBLD,PAGEOUT) MCPDFALT

"Mapping" refers to BMS requests that specify maps, that is OSPTR3 bits 5 or 6 or 7 or OSPTR4 bit 3 set on.

Each of these functional regions does a BAL to subroutine MCPFTIOA to search for a user data area. If a valid area (abend ABMU if not) is found, its address

is put into OSPTIOA and the address of the data address (of TCAMSIOA or TCTTEDA) is set into OSPSIOA. If a data area is not found, OSPTIOA is cleared

and OSPSIOA is now loaded with the address of OSPTIOA as a null data area.

On the BAL return, OSPTIOA is tested for a nonzero value. If it is zero, a branch to MCPABEND is taken.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: The programmer must place the address of the data into TCTTEDA or TCAMSIOA, whichever is appropriate.

Firstly, check that the user has loaded TCTTEDA or TCAMSIOA with the address of the user data, by checking the application listing and the contents of

TCTTEDA and/or TCAMSIOA.

Next, check that the BMS request has been correctly decoded by CICS by referring to the OSPWA request bytes (OSPTR1-8) or decoding the last BMS

entry in the trace table. See OSPIND01 to check correct decoding of PAGEBLD or TEXTBLD, and TCAFCI bit 7 to identify whether the task is

terminal-oriented or not.

At the abend point, register 1 contains the user data address last loaded, and register 4 the address of OSPTIOA as an address of null data.

If a CICS error is suspected, concentrate initially on subroutine MCPFTIOA, because this is a simple piece of code that shows the data-fetch logic. ABM2

condition is trapped early in the CICS decoding of the DFHBMS request and involves module DFHMCP only.

Case/Register Label Description

R9=@OSPWA MCPMAP OSPTR4 has OSPTRM

(X'04') bit set for

TYPE=MAP.

R9=@OSPWA MCPPGBLD OSPTR5 has OSPTRB

(X'80') bit set and

BMS sets bit

OSPLMPB (X'08') in

OSPIND01 for

TYPE=PAGEBLD.

OSPTR4 has X'40',

X'80', or X'C0' set

for DATA=NO, ONLY,

or YES respectively,

so should be X'80'

or X'C0'.

R9=@OSPWA MCPTXBLD OSPTR7 has OSPTRX

(X'80') bit set and

BMS sets bit

OSPLMTB (X'04') in

OSPIND01 for

TYPE=PAGEBLD.

OSPTR4 has X'40',

X'80', or X'C0' set

for DATA=NO, ONLY,

or YES respectively,

so should be X'80'

or X'C0'.

R9=@OSPWA MCPMAPNG OSPTR3 has OSPTSN

(X'01'), OSPTSA

(X'02'), or OSPTMN

(X'04') bits set, or

OSPTR4 has OSPTMA

(X'10') bit set for

mapping.

OSPTR4 has X'04' or

X'80' or X'C0' set for

DATA=NO, ONLY, or YES

respectively, so should

be X'80' or X'C0'.

All R12=@TCA MCPFTIOA TCAFCI has

TCAFCTRM (X'01') bit

set if the task is

terminal-oriented.

All R11=@TCTTE MCPFTIOA TCTTEDA could point

to a use TIOA but does

not, thus causing the

abend.

All R12=@TCA MCPFTIOA TCAMSIOA could point

to a user data area

(TIOA or otherwise),

but does thus causing

the abend.

All R9=@OSPWA MCPNTOTM OSPTIOA contains the

address of the user

area found, so is

zero.

OSPSIOA points

to OSPIOA (which is

copied from TCAMSIOA)

as being the second-dry

data area sought by

BMS for data .

OSPIA (TCAMSIOA) was

also zero so causing

the abend.

Module: DFHMCP

ABM3

Explanation: A BMS input or output request has been issued from a task that is not terminal-oriented.

System Action: The task is abnormally terminated with a CICS dump.

User Response: The task issuing a BMS input or output request must be attached to a terminal.

Module: DFHMCP

ABM4

Explanation: An invalid request response has been received to a temporary storage PUT or PUTQ request issued by BMS. The data passed to the

temporary storage program has an invalid length.

Problem Determination: Abend in DFHMCP (see Analysis)

The OSPWA (output services work area) is in user storage and is printed in a transaction dump. It is addressed by register 9 at the time of the abend.

Relevant fields are:

OSPTITLE

OSPTTCNT

OSPPLTI

OSPTOTPG

The message control record (MCR) is an area of user storage obtained by BMS. It is addressed by register 8 at the time of the abend. The first 8 bytes

contain storage accounting information. MCRLLBB contains the length of the MCR (halfword) abend in DFHTPP.

The page buffer is addressed by register 7 at the time of the abend. It contains storage accounting fields in the first 8 bytes and a halfword length at offset 8

(TSIOAVRL).

In both cases, the temporary storage use map (DFHTSMAP) is addressed from CSATSATA. TSMAPCOM contains the number of available bytes in a control

interval on the temporary storage data set.

Analysis: If the temporary storage request preceding the abend is a DFHTS PUT, the abend occurred in DFHMCP. If the temporary storage request

preceding the abend is a DFHTS PUTQ, the abend occurred in DFHTPP. If the abend occurred in DFHMCP, DFHMCP is attempting to put the message

control record to temporary storage. Check the length of the MCR (MCRLLBB). It may be negative.

The length of the MCR is calculated by code following label MCPNODDS and is:

28 + 21 * OSPTTCNT + (length of title record)

+ (space for page/LDC table,

if needed)

The address of the title record is at OSPTITLE and the length is contained in the first halfword. Space for the page/LDC table is required if OSPPLT1 is

nonzero, which should occur only for messages routed to LDC devices (3600, 3650, 3767, 3770, 3790). The number of entries is in OSPTOTPG. 2 bytes are

required per entry.

If the abend occurred in DFHTPP, BMS is attempting to add a page to the temporary storage queue, and the page buffer will not fit in the control interval.

TSIOAVRL contains the length of the page buffer.

For messages directed to 3270 devices, the page buffer consists of a 3270 data stream with a 4-byte page control area following it (a 3270 data stream may

be larger than the number of characters available on the screen, particularly if extended 3270 attributes are used). For messages directed to other devices,

the page buffer consists of a message formatted with NL characters, a 4-byte page control area following it. The length in TSIOAVRL should be less than the

length in the preceding storage accounting area, otherwise an error has occurred in constructing the page, possibly in prior BMS requests.

In either of the above cases, if the length of the area being output appears valid, it is necessary to increase the control interval size for the temporary storage

data set.

DFHMCP

R8=@MCR MCPMCRTS The MCR is too long or

has invalid length (�4).

DFHTPP

R7=@pgbuf TPNOPGL The page buffer is

or too large.

TPNODDS

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Determine from the trace table whether the abend occurred in DFHMCP or DFHTPP.

Check the length of the appropriate area.

If the MCR length is invalid, possible reasons are:

more than 64 characters.

there are a large number of terminals in the TCT.

Modules: DFHMCP, DFHTPP

ABM5

Explanation: A DFHTS TYPE=PURGE request has been issued with an invalid REQID. This incorrect request was issued by basic mapping support (BMS).

DFHTPR cannot find the terminal identifier for the current terminal in the terminal list in the message control record (MCR).

Problem Determination: The TS identifier is built in TCATSDI before the TS purge is issued, although this has probably been overwritten before the dump is

taken. The trace table entry for the DFHTS TYPE=PURGE contains the TS identifier in the last 8 bytes.

The OSPWA is addressed by register 9.

OPSTSID temporary storage identifier (8 bytes).

The terminal list starts at MCRIDLST and the terminal identifier is at the start of the terminal entry. Each terminal entry is X'15' bytes long.

Analysis: DFHMCP uses the temporary storage identifier in OSPTSID.

Cannot find the terminal identifier for this terminal in the terminal list in the MCR.

R9=@(OSPWA) MCPCKPGS Code builds the temporary

storage code in TCATSDI

and issues DFHTS

TYPE=PURGE macro,

specifying IDERROR exit

of MCPTSIDE, where the

abend is raised.

R8=@(MCR) TPRCKID Code scans terminal list

for a terminal entry that

has the id of the current

terminal, and if it

cannot be found, links to

TPRSNH to raise the abend.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check the trace table and find the preceding PUT/PUTQ TS requests. Check whether the identifier for the PUT/PUTQ is the same as that

for the PURGE. If it is not, find out how they differ. Check to see if the OSPWA has been corrupted.

This error is very unlikely, as the label indicates (TPRSNH - "Should Not Happen"). DFHTPS has scanned the MCR to identify the terminals to which this

message is directed, and has created an AID to initiate CSPG (DFHTPR) at each of them. However, when DFHTPR retrieves the MCR, it cannot find the

current terminal identifier in the list of terminals. Presumably the MCR has been corrupted between creation of the AID and dispatching of CSPG at the

terminal. Check back through the trace table to find the instance of DFHTPS that built the AID for this terminal (transaction CSPS); it will have issued a TC

LOCATE request to verify that the terminal identifier is valid, and this identifier can be seen in the trace entry.

Modules: DFHMCP, DFHTPR

ABM6

Explanation: Transaction CSPS, scheduled internally by BMS, has not been installed.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Install the transaction CSPS (Group DFHBMS).

Module: DFHMCP

ABM7

Explanation: The trailer specified to be used while building pages of text data is longer than the page.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Correct the application program that issues the request with too long a trailer.

Module: DFHPBP

ABM8

Explanation: A BMS text request specified a value for the JUSTIFY option which is zero or too large for the page being built.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Correct the application program that specified too large or zero value for the JUSTIFY option.

Module: DFHPBP

ABM9

Explanation: The text data overflow routines have been reentered while text overflow was in process. This condition occurs when the line requirements for

the text header and/or trailer exceed the line capacity of the page for which data is being formatted.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Reduce the number of lines required for the header and/or trailer or increase the page size of the terminal.

Module: DFHPBP

ABNA

Explanation: No route list was supplied with a route request 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHTPS

ABNB

Explanation: Either the principal facility of the task is not a TCTTE of the correct type, or the task has no principal facility.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Ensure that DFHTPS has not been specified as the initial program of a transaction other than CSPS. Check that the operator did not enter

CSPS from the terminal.

Module: DFHTPS

ABNC

Explanation: An attempt to access a temporary storage queue failed.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Ensure that temporary storage is correctly generated.

Module: DFHTPS

ABNE

Explanation: An error response was received from an invocation of a BMS TYPE=ROUTE or TYPE=STORE request.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check that BMS was correctly generated.

Module: DFHTPS

ABNF

Explanation: The transaction was not in send mode when it sent data to 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHTPS

ABNG

Explanation: An attach request was received from the remote system without any data indicating the reason for the request.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHTPS

ABNH

Explanation: An attempt to ship data to the remote 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHTPS

ABNI

Explanation: CICS could not find a profile for an LU6.2 transaction routing request.

System Action: CICS terminates the task abnormally.

User Response: Either you have specified an incorrect name in the PROFILE parameter of an EXEC CICS ALLOCATE command, or you have not installed

the profile. Correct the error before resubmitting the transaction.

Module: DFHTPS

ABNJ

Explanation: The task was 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 the reason why the task was purged. It was purged either by the master terminal operator or as a result of a deadlock timeout.

Module: DFHTPS

ABNK

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.

Module: DFHTPS

ABRC

Explanation: The bridge exit is not defined and could not be autoinstalled.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Either define the program using RDO or change the program autoinstall exit to allow it to be autoinstalled.

Modules: DFHBRMS, DFHBRTC

ABRD

Explanation: The bridge exit is disabled.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Identify why the bridge exit is disabled. Enable the bridge exit and retry the action.

Modules: DFHBRMS, DFHBRTC

ABRE

Explanation: The bridge exit could not be loaded.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Investigate why it cannot be loaded. It may not have been defined in the DFHRPL library.

Modules: DFHBRMS, DFHBRTC

ABRF

Explanation: The bridge exit is defined as remote.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Define the bridge exit as a local program.

Modules: DFHBRMS, DFHBRTC

ABRG

Explanation: An invalid bridge facility token was specified

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: This error was probably caused by the incorrect data being sent to the bridge exit from the client application.

Check the data set by tracing the data sent from the client application.

Ensure that the bridge facility token in the data transmitted by the application is correct.

Module: DFHBRXM

ABRH

Explanation: The bridge facility token specified is not known to CICS.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: The most likely error is that the client application specified too small a keep time for the bridge facility. Before the client reused the bridge

facility token, CICS had already discarded it. Check the bridge facility keep time in the outbound messages. CICS will use the keep time value specified in

the last message used by a transaction. Alternatively use the trace or CEDX to look at the keep time in the BRXA passed back on the terminate call to the

bridge exit.

Another possible error is that the client application passed a request to a CICS system other than that on which the original request was sent. Bridge

facilities are only valid on a single CICS system.

Module: DFHBRXM

ABRI

Explanation: There are no free bridge facility tokens available. This is probably due to excessive keep time values being specified on the bridge exit

termination call.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Review the keep time values used by the client applications. If some client applications are returning excessive values, modify the bridge

exit to specify a limit to the values.

Module: DFHBRXM

ABRJ

Explanation: An invalid FACILITYLIKE value was specified.

The FACILITYLIKE value can be specified on the bridge exit initialization call. If the default value (blanks) is returned, the value in the user transaction profile

definition is used. If no FACILITYLIKE value is specified in the profile definition, a value of CBRF is used.

The name must be that of an installed VTAM 3270 terminal.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Define the terminal specified by FACILITYLIKE, change the value on the profile definition, change the value supplied by the client

application, or install a terminal definition for CBRF

Module: DFHBRXM

ABRK

Explanation: The USERID check failed following the call to the bridge exit.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction will not be started.

User Response: Enter the correct password. If the password is correct or was not supplied, review the RACF definitions.

Module: DFHBRXM

ABRN

Explanation: The bridge exit returned a value in BRXA_RESP that is not valid for the command for which it was invoked.

System Action: The transaction is backed out.

User Response: Change the bridge exit to only return valid response settings.

Modules: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC

ABRQ

Explanation: The bridge exit issued an abend.

System Action: The transaction is backed out.

User Response: Identify why the bridge exit abended.

Modules: DFHBRMS, DFHBRTC

ABRR

Explanation: The user transaction's profile could not be found.

System Action: The task is abnormally terminated with a CICS transaction dump. The user transaction is not started.

User Response: Check that the profile name in the user transaction definition is correct, and that this profile has been defined.

Module: DFHBRXM

ABRY

Explanation: CICS returned an unexpected error running the bridge exit. This is a CICS internal 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Modules: DFHBRMS, DFHBRTC

ABRZ

Explanation: The bridge exit returned invalid data in the BRXA.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: If a user supplied bridge exit was used, review the format of the data returned by the exit.

If a CICS supplied exit was used, this is a CICS error. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem

Determination Guide for guidance on how to proceed.

Modules: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHXMBR

ABR3

Explanation: An unsupported BMS request was received by the bridge exit.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: The bridge only supports minimum function BMS and SEND TEXT. This transaction cannot be used in a bridge environment.

Module: DFHEMS

ABR4

Explanation: The link DFHL3270 command did not specify a commarea.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: The link DFHL3270 command must specify a commarea to contain the BRIH and any message vectors.

Module: DFHBRMR

ABR5

Explanation: The commarea specified in the link DFHL3270 command is shorter than the BRIH.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: The link DFHL3270 command must specify a commarea to contain the BRIH and any message vectors.

Module: DFHBRMR

ABR6

Explanation: The commarea specified in the link DFHL3270 command does not contain a valid BRIH.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: The link DFHL3270 command must specify a commarea which must contain a valid BRIH.

Module: DFHBRMR

ABSA

Explanation: A message passed to DFHBSMSG is too long. This is a CICS internal error.

System Action: CICS terminates the task abnormally with a dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHTBS

ABXA

Explanation: A next BRMQ vector in the input message passed to the formatter is the wrong type of a RECEIVE vector. RECEIVE and RECEIVE MAP

have separate vectors.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: This may just indicate that the transaction has gone down an error path which should result in a transaction backout. If not, the input

message should have a BRMQ vector for this command. Change the client application, recompile and retry.

Module: DFH0CBRF

ABXB

Explanation: The BRIH requested that outbound BMS vector must include the ADS descriptor. The map did not contain an ADS descriptor. This means

that the mapset was not assembled with CICS TS 1.2 or later.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Either reassemble the mapset using the current level of BMS macros, or set BRIH-ADSDESCRIPTOR to BRIHADSD-NO (the default value

is BRIHADSD-YES). Note that BRIHADSD-YES is required when codepage conversion of the Link3270 message is required (e.g. using ECI). If you need to

reassemble the mapset and don't have the mapset source, the utility DFHBMSUP can be used to recreate it.

Module: DFHBRMF

ABXC

Explanation: An error occurred when a SYNCPOINT request was issued by the bridge exit.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check for other CICS messages and exception trace entries to investigate the cause of the SYNCPOINT error.

Module: DFH0CBRE

ABXD

Explanation: An error occurred when a SYNCPOINT ROLLBACK request was issued by the bridge exit.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check for other CICS messages and exception trace entries to investigate the cause of the SYNCPOINT ROLLBACK error.

Module: DFH0CBRE

ABXE

Explanation: The bridge exit was expecting data to be passed on the BRDATA parameter of the START command. No data was found.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Correct the transaction which issued the START. Recompile, reload and retry.

Module: DFH0CBAE,DFH0CBRE

ABXF

Explanation: An error was detected by the bridge exit when it tried to input the next message.

System Action: An exception trace is made of any error information. The task is abnormally terminated with a CICS transaction dump.

User Response: Check for other CICS messages and exception trace entries to investigate the cause of the input error.

Module: DFH0CBAE,DFH0CBRE,DFH0CBAI

ABXG

Explanation: An error was detected by the bridge exit when it tried to output the next message.

System Action: An exception trace is made of any error information. The task is abnormally terminated with a CICS transaction dump.

User Response: Check for other CICS messages and exception trace entries to investigate the cause of the output error.

Module: DFH0CBAE,DFH0CBRE

ABXH

Explanation: The user transaction issued a request which requires more data (such as a RECEIVE request). No data was available in the message, and

mqcih-conversationaltask was set to mqcct-no which specifies that the transaction is non conversational.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: This may be correct behaviour as defined by the client application. If it is not, the client application should either supply additional data, or

be redesigned to allow the transaction to be conversational.

Module: DFH0CBRF

ABXI

Explanation: A message received by the bridge exit, exceeded the maximum message size.

System Action: An exception trace is made of the first 4K of data in error. The task is abnormally terminated with a CICS transaction dump.

User Response: Check that the client application is passing the correct data. If it is, it will be necessary to change the size of the buffer. This is in field

block-length in the sample exit. Recompile and reload the exit and retry.

Module: DFH0CBAE,DFH0CBRE

ABXJ

Explanation: The bridge exit detected an error in the MQCIH header passed by the client application.

System Action: An exception trace is written containing the MQCIH header. The task is abnormally terminated with a CICS transaction dump.

User Response: The client application has either not set the MQCIH header, or is using a version of the header which is incompatible with the bridge exit.

Correct the client application. Recompile, reload and retry.

Module: DFH0CBAE,DFH0CBRE

ABXK

Explanation: The bridge exit detected an error in the data passed on the BRDATA parameter of the START command.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

User Response: Correct the transaction which issued the START. Recompile, reload and retry.

Module: DFH0CBAE,DFH0CBRE

ABXM

Explanation: The bridge exit or formatter was called with a function or command which it doesn't support. This either indicates a storage overwrite, or that

the bridge exit is not designed for this command.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

User Response: Check the BRXA data in the trace to see if there has been a storage overwrite, or whether the exit supports this command.

Module: DFH0CBAE,DFH0CBRE,DFH0CBRF

ABXN

Explanation: The formatter detected that the input message was truncated.

System Action: An exception trace is made of the first 4K of the message. The task is abnormally terminated with a CICS transaction dump.

User Response: Check that the transport mechanism allows for messages of this length. If this is correct, it indicates that the client application is issuing

an incorrect message. Trace the outbound message on the client application. Recompile, reload and retry.

Module: DFH0CBRF

ABXO

Explanation: The formatter detected an error in a BRMQ vector passed by the client application.

System Action: The field MQCIH-ERROROFFSET is set to indicate the position of the error in the message An exception trace is made of the MQCIH and

BRMQ vector. The task is abnormally terminated with a CICS transaction dump.

User Response: Correct the client application. Recompile, reload and retry.

Module: DFH0CBRF

ABXP

Explanation: The formatter detected an error in a BRMQ vector header passed by the client application.

System Action: The field MQCIH-ERROROFFSET is set to indicate the position of the error in the message An exception trace is made of the MQCIH and

BRMQ vector. The task is abnormally terminated with a CICS transaction dump.

User Response: Correct the client application. Recompile, reload and retry.

Module: DFH0CBRF

ABXQ

Explanation: The formatter could not find an ADSD vector as part of the BRMQ-RM vector when MQCIH-ADSDESCRIPTOR specified

MQCADSD-MSGFORMAT.

System Action: An exception trace is made of the request. The task is abnormally terminated with a CICS transaction dump.

User Response: Correct the client application. Recompile, reload and retry.

Module: DFH0CBRF

ABXS

Explanation: An error was detected by the bridge exit when it tried to open the queue for the input or output message.

System Action: An exception trace is made of any error information. The task is abnormally terminated with a CICS transaction dump.

User Response: Check for other CICS messages and exception trace entries to investigate the cause of the open error.

Module: DFH0CBRE

ABXU

Explanation: The conversion between client code page and server code page is not supported by CICS/390; for example conversion has been requested

between Japanese code page 932 and Latin-1 code page 500.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure that the Client codepage, both default and overrides are in the same group as the Server codepage. for example client code page

852 from Latin-2 group, is only supported to server code page 870.

Module: DFHBRMF

ABXV

Explanation: The client code page which has been requested by the client is not one which CICS can support.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure that the Client codepage is valid.

Module: DFHBRMF

ABX1

Explanation: The bridge exit or formatter was called with an invalid BRXA-HEADER. This indicates a storage overwrite.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

As CICS also does a check of the BRXA on return from the call to the exit, there will probably be a subsequent ABRZ abend.

User Response: Investigate the cause of the storage error, and retry.

Module: DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX2

Explanation: The bridge exit or formatter was called with an invalid BRXA-TRANSACTION-AREA. This indicates a storage overwrite.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

As CICS also does a check of the BRXA on return from the call to the exit, there will probably be a subsequent ABRZ abend.

User Response: Investigate the cause of the storage error, and retry.

Module: DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX3

Explanation: The bridge exit or formatter was called with an invalid BRXA-COMMAND-AREA. This indicates a storage overwrite.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

As CICS also does a check of the BRXA on return from the call to the exit, there will probably be a subsequent ABRZ abend.

User Response: Investigate the cause of the storage error, and retry.

Module: DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX5

Explanation: The bridge exit or formatter was called without a user-area. This probably indicates an error in the bridge exit.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the cause of the storage error, and retry.

Module: DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX6

Explanation: The bridge exit or formatter was called with an invalid user-area. This indicates a storage overwrite or an error in the bridge exit.

System Action: An exception trace is made of the data in error. The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the cause of the storage error, and retry.

Module: DFH0CBAE,DFH0CBRE,DFH0CBRF

ABX7

Explanation: A TC command passed to the formatter, exceeded the maximum message size.

System Action: An exception trace is made of the first 4K of data in error. The task is abnormally terminated with a CICS transaction dump.

User Response: Check that the user transaction is passing the correct data. If it is, it will be necessary to change the size of the buffer. This is in field

block-length in the sample exit. Recompile and reload the exit and retry.

Module: DFH0CBRF

ABX8

Explanation: A next BMS BRMQ vector in the input message passed to the formatter does not contain the mapset requested to answer a RECEIVE MAP

request.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: This may just indicate that the transaction has gone down an error path which should result in a transaction backout. If not, the input

message should have a BRMQ vector for this mapset. Change the client application, recompile and retry.

Module: DFH0CBRF

ABX9

Explanation: A next BMS BRMQ vector in the input message passed to the formatter does not contain the mapname requested to answer a RECEIVE

MAP request.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: This may just indicate that the transaction has gone down an error path which should result in a transaction backout. If not, the input

message should have a BRMQ vector for this mapname. Change the client application, recompile and retry.

Module: DFH0CBRF

ACAA

Explanation: This explanation applies to the two transaction abend codes, ACAA and ACAD. CICS cannot find a match for a function code in the language

definition table because the parameterized resource definition contains an unrecognized resource type code. The abend code issued depends on the

DFHCAP operation that was invoked before the error occurred:

Abend DFHCAP operation

ACAA ANALYZE

ACAD DEFAULTS

The cause of the abend is either:

The language definition table, DFHEITCU, in the library is invalid for the release of CICS you are running, or

A CICS logic error has occurred.

System Action:

In a CICS environment, the CEDA transaction is abnormally terminated with a CICS transaction dump.

In a batch environment, processing is abnormally terminated with an operating system dump.

User Response: Ensure that the DFHEITCU module is in the library and is valid for this release of CICS.

If a valid version of DFHEITCU is already in the library, a CICS logic error has occurred. You need further assistance from IBM to resolve this problem. See

Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCAP

ACAD

Explanation: See ACAA.

Module: DFHCAP

ACAI

Explanation: An internal error has occurred when module DFHCAP was invoked. There was an invalid function code for a domain call to DFHCAP.

System Action:

In a CICS environment, the CEDA transaction is abnormally terminated with a CICS transaction dump.

In a batch environment, processing is abnormally terminated with an operating system dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCAP

ACAJ

Explanation: An internal error has occurred when module DFHCAP was invoked while processing an EXEC CICS CREATE command. The preallocated

dynamic storage area was too small.

System Action: The transaction executing the EXEC CICS CREATE command is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCAP

ACAM

Explanation: An internal error has occurred when module DFHECBAM was invoked while processing a CBAM transaction.

System Action: CBAM is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHECBAM

ACCA

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCB

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCC

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCD

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCE

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCF

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCG

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCH

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCI

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCJ

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCK

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCL

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCM

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCN

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCO

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCP

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCQ

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCR

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCS

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCT

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCU

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCV

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCW

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCx

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCY

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACCZ

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC1

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC2

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC3

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC4

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC5

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC6

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC7

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC8

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACC9

Explanation: Abend codes with 'ACC' as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the

C/370 User's Guide.

ACFA

Explanation: During the loading of a Coupling Facility Data Table by the CFCL transaction, an abend was detected or a domain call returned a response

(such as DISASTER) after which normal processing could not continue.

System Action: A message is issued (one of DFHFC7100, DFHFC7101, DFHFC7103 or DFHFC7104). Loading of the data table is terminated and CFCL

abends.

User Response: If this abend is produced as a result of an abend during loading, message DFHFC7103 is issued. If it is a result of a domain call failure,

depending on which domain the failure was returned by, one of the messages DFHFC7100, DFHFC7101 or DFHFC7104 is issued. Refer to the description of

the message for further information and guidance.

Module: DFHFCDL

ACFB

Explanation: A transaction has issued a request to a coupling facility data table for which it holds an active lock, but after the lock was acquired, the

coupling facility data table server for the pool in which this coupling facility data table resides failed and was restarted. This request is of a type which cannot

continue against a new instance of the server, because it is reliant on the lock which was acquired before the server failed.

System Action: The requesting transaction abends with a transaction dump.

CICS continues normally.

User Response: Retry the failed transaction.

Module: DFHEIFC

ACFC

Explanation: A transaction has issued a request to a coupling facility data table which was last accessed using a previous instance of the coupling facility

data table server (that is, the server for the pool in which this coupling facility data table resides has failed and been restarted one or more times since the

last access). We therefore need to reopen the access between this CICS file and the coupling facility data table, but the attempt to reopen access has failed.

System Action: The requesting transaction abends with a transaction dump.

CICS continues normally.

User Response: Retry the failed transaction. If the error continues to occur, issue an explicit close request for the file, followed by an explicit open request.

Module: DFHEIFC

ACFD

Explanation: During the loading of a Coupling Facility Data Table by the CFCL transaction, a call to the CICS Transaction Manager has returned a response

(such as DISASTER) after which normal processing could not continue.

System Action: Message DFHFC7121 is issued. Loading of the data table is terminated and CFCL abends.

User Response: Refer to the description of the message for further information and guidance.

Module: DFHFCDL

ACFE

Explanation: An attempt was made to attach a transaction specifying DFHFCDL as the program to be given control, but the transaction was not internally

attached by CICS.

DFHFCDL is for use by CICS system transaction CFCL. This loads a Coupling Facility Data Table.

System Action: The transaction is abnormally terminated. CICS processing continues.

User Response: Establish why an attempt was made to attach CFCL illegally, or why a transaction definition specified DFHFCDL as the program to be

given control.

Module: DFHFCDL

ACHA

Explanation: The remote server transaction, CEHS, is not at a compatible level to operate with the CICS/CMS system. This usually indicates that the

service levels of CICS/CMS and the remote server are different.

Problem Determination: To diagnose a problem with the remote server, it is generally helpful to obtain a trace of the remote server's activity up to the point

of failure.

A remote server trace is obtained by invoking the remote server with the TRACE option, (type CEHS TRACE). The remote server operates as normal but

causes entries to be written to a trace log in temporary storage. Note that main storage, not auxiliary, is used for this queue hence large amounts of memory

can be used up if this trace is left on for long.

The trace is found in a queue whose name is 'CEHSxxxx', where 'xxxx' is the four-character terminal identifier. The queue can be browsed in text form or in

hexadecimal form using CEBR. To find the terminal identifier, invoke CEBR on the terminal that has run CEHS, without giving a queue name. The queue

name will default to 'CEBRxxxx', where 'xxxx' is the terminal identifier.

Note: CEBR requires the queue name to be in UPPER CASE.

For a description of the remote server and its trace entries and abend codes, see the CICS/VS Remote Server Diagnosis Manual (LC33-0438).

System Action: CICS terminates the remote server transaction abnormally with a dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCHS

ACHB

Explanation: The remote server has received a data frame from CICS/CMS that is out of sequence. A frame may have been lost in transmission.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHC

Explanation: The remote server did not receive the expected acknowledgement type data frame from CICS/CMS.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHD

Explanation: The remote server did not receive the expected response type data frame from CICS/CMS.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHE

Explanation: The remote server received an unexpected data frame from CICS/CMS. This indicates a logic error in the remote server.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHF

Explanation: The remote server attempted to send one of a series of data frames to CICS/CMS when, at this time, only a single frame is allowed. This

indicates a logic error in the remote server.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHG

Explanation: The remote server attempted to send data to CICS/CMS. However, it was not set to the correct mode to do so. This indicates a logic error in

the remote server.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHH

Explanation: A TIOA has not been created from the data received by the remote server from CICS/CMS.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHI

Explanation: The remote server has received an unexpected return code from the Transformer 2 program.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: For further information, see the 'Problem Determination' section for abend code ACHA.

Module: DFHCHS

ACHJ

Explanation: An error has occurred processing a request from CICS/CMS which had the 'No-Reply' option. The remote server cannot, therefore, return the

error condition to CICS/CMS.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the remote server and diagnose the problem by executing the same command from CECI under CICS/CMS without the

NOCHECK option. For further information, see the 'Problem Determination' section for abend code ACHA.

Module: DFHCHS

ACHK

Explanation: The transformer program has requested neither EIP nor DLI to execute the request received from CICS/CMS. This indicates a logic error

because the request has to be destined for either EIP or DLI.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: For further information, see the 'Problem Determination' section for abend code ACHA.

Module: DFHCHS

ACHL

Explanation: CICS/CMS has supplied a buffer to the remote server which is not large enough to hold the reply that the remote server has to return.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHM

Explanation: The remote server has tried to receive a response from CICS/CMS which failed repeatedly until the retry limit was exceeded.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHN

Explanation: The remote server has tried to receive a request from CICS/CMS which failed repeatedly until the retry limit was exceeded.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHO

Explanation: The remote server has tried to receive a reply from CICS/CMS which failed repeatedly until the retry limit was exceeded.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further

information, see the 'Problem Determination' section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. You need further assistance from IBM to resolve this problem. See Part 4

of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCHS

ACHP

Explanation: CICS/CMS has made a request to the remote server for which the reply would need more than the maximum storage allowed (32660 bytes).

This indicates that a logic error has occurred.

System Action: CICS terminates the remote server abnormally with a dump.

User Response: For further information, see the 'Problem Determination' section for abend code ACHA.

Module: DFHCHS

ACHR

Explanation: The CICS/CMS remote server transaction (CEHS) has been initiated and either the task is not terminal-oriented, or the associated terminal is

a console.

System Action: CICS abnormally terminates the remote server with a dump.

User Response: Ensure the transaction is initiated with an associated terminal and that the terminal is not defined as a console. For further information, see

the 'Problem Determination' section for abend code ACHA.

Module: DFHCHS

ACHS

Explanation: The CICS/OS2 remote server transaction (CEHP) has been initiated and either the task is not terminal-oriented, or the associated terminal is

a console.

System Action: CICS abnormally terminates the remote server with a dump.

User Response: Ensure the transaction is initiated with an associated terminal and that the terminal is not defined as a console. For further information, see

the 'Problem Determination' section for abend code ACHA.

Module: DFHCHS

ACL0

Explanation: The new operator failed to allocate storage whilst creating an object. This problem will occur if there is insufficient storage available to the

CICS region to satisfy the request.

System Action: CICS abnormally terminates the transaction.

User Response: This abend may occur if you are in a loop creating objects and not deleting them. Alternatively CICS might be short on storage and you

should try resubmitting the transaction.

Module: ICCGLBIC

ACL1

Explanation: The CICS Foundation Classes have thrown an exception which the application programmer failed to catch.

System Action: CICS abnormally terminates the transaction.

User Response: Check that you have coded your application to catch exceptions. Interrogate the message object contained within the exception object to

establish the cause of the exception being thrown.

Another possible cause of this abend is that you are running a Foundation Classes program on a machine that does not have the C++ runtime installed.

Check that your machine has the C++ runtime installed.

Module: ICCGLBIC

ACL2

Explanation: The CICS Foundation Classes invoked the default handleEvent method (defined in class IccResource) in order to handle a CICS condition

because the application programmer did not implement his own handleEvent method.

System Action: CICS abnormally terminates the transaction.

User Response: Implement your own handleEvent method or customize your resource objects so they do not call the handleEvent method for any of the

possible CICS conditions.

Module: ICCRESEC

ACL3

Explanation: The CICS Foundation Classes responded to an application programmer's request to abend a CICS task.

System Action: CICS abnormally terminates the transaction.

User Response: The application programmer requested that the CICS Foundation Classes abend the transaction using the appropriate return enumeration

from the handleEvent method (see IccResource class).

Module: ICCRESIC

ACL4

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACL5

Explanation: The CICS Foundation Classes received an error from a CICS storage request (GETMAIN). In response to a new operator request the CICS

Foundation Classes issued a CICS GETMAIN request to allocate storage which CICS was unable to satisfy.

System Action: CICS abnormally terminates the transaction.

User Response: This abend may occur if you are in a loop creating objects and not deleting them. Alternatively CICS might be short on storage and you

should try resubmitting the transaction.

Module: ICCBASEC

ACL6

Explanation: The CICS Foundation Classes detected an error while processing a storage release request.

System Action: CICS abnormally terminates the transaction.

User Response: This abend can occur if you try to delete an object that does not exist (that is, it has already been deleted). It may also indicate a CICS

memory management problem, or a storage corruption problem. If the error persists, please contact your support organization.

Module: ICCBASEC

ACL7

Explanation: The CICS Foundation Classes have thrown an exception which the application programmer failed to catch.

System Action: CICS abnormally terminates the transaction.

User Response: Check that you have coded your application to catch exceptions. Interrogate the message object contained within the exception object to

establish the cause of the exception being thrown.

Another possible cause of this abend is that you are running a Foundation Classes program on a machine that does not have the C++ runtime installed.

Check that your machine has the C++ runtime installed.

Module: ICCGLBIC

ACL8

Explanation: The CICS Foundation Classes have thrown an exception which the application programmer failed to catch.

System Action: CICS abnormally terminates the transaction.

User Response: Check that you have coded your application to catch exceptions. Interrogate the message object contained within the exception object to

establish the cause of the exception being thrown.

Another possible cause of this abend is that you are running a Foundation Classes program on a machine that does not have the C++ runtime installed.

Check that your machine has the C++ runtime installed.

Module: ICCGLBIC

ACL9

Explanation: The CICS Foundation Classes responded to an application programmer's request to abend a CICS task.

System Action: CICS abnormally terminates the transaction.

User Response: A resource object was customized to cause a transaction abend if a particular CICS condition was raised, and this condition was

subsequently raised by CICS.

Module: ICCRESIC

ACLA

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLB

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLC

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLD

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLE

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLF

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLG

Explanation: The CICS Foundation Classes detected an internal error.

System Action: CICS abnormally terminates the transaction.

User Response: This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Module: ICCGLIBC

ACLH

Explanation: The CICS Foundation Classes detected an error while processing a storage release request.

System Action: CICS abnormally terminates the transaction.

User Response: This abend can occur if you try to delete an object that does not exist (that is, it has already been deleted). It may also indicate a CICS

memory management problem, or a storage corruption problem. If the error persists, please contact your support organization.

Module: ICCBASEC

ACNA

Explanation: The table DFHCNV cannot be loaded. This is a general purpose abend code indicating that the LOAD request for the conversion table,

DFHCNV, has failed.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Examine the transaction dump to determine the exact condition returned from LOAD request.

Module: DFHCCNV

ACNB

Explanation: The program DFHUCNV cannot be linked This is a general purpose abend code indicating that the LINK request for the conversion program

DFHUCNV, has failed.

System Action: The transaction is abnormally terminated with a transaction dump.

Module: DFHCCNV

ACN1

Explanation: The table DFHCNV cannot be loaded. This is probably because a table has not been pregenerated. It could also occur if the table DFHCNV

has been linked above 16MB but DFHCCNV has been linked below 16MB.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Check that the DFHCNV module is in the library and is valid for this release of CICS. Check the linkage of DFHCNV and relink it with the

correct AMODE if necessary.

Module: DFHCCNV

ACN2

Explanation: The table DFHCNV has been loaded but the first record is in the wrong format. This is probably due to an error during assembly or linkedit,

but could also be the result of a storage overwrite.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: The table should be reassembled and linked. Check the assemble and linkedit output. Check for any messages issued from CICS

indicating that storage overwrites have occurred.

Module: DFHCCNV

ACN3

Explanation: The program DFHUCNV cannot be linked. A user conversion program must be available (even if it only returns).

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Check that the DFHUCNV module is in the library and is valid for this release of CICS. Check the linkage of DFHUCNV and relink it with

the correct AMODE if necessary.

Module: DFHCCNV

ACN4

Explanation: An unrecognized format of a DFHCNV table has been encountered.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Re-assemble and re-link edit the DFHCNV macro.

Module: DFHCCNV

ACN5

Explanation: An override for the default client code page has been received; however the value is not recognized.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Check that the client system is using one of the client code pages supported by CICS/390.

Module: DFHCCNV

ACN6

Explanation: The client sent data in unicode but the client and server code pages are not the same. Unicode data is only tolerated provided that conversion

is not required.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure that the Client codepage and the Server codepage are the same.

Module: DFHCCNV

ACNC

Explanation: The client code page which has been requested by the client is not one which CICS can support.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure that the Client codepage is valid.

Module: DFHCCNV

ACND

Explanation: The conversion between client code page and server code page is not supported by CICS/390; for example conversion has been requested

between Japanese code page 932 and Latin-1 code page 500.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure that the Client codepage, both default and overrides are in the same group as the Server codepage. for example client code page

852 from Latin-2 group, is only supported to server code page 870.

Module: DFHCCNV

ACNE

Explanation: The conversion between client code page and server code page is not supported by CICS/390. Although the code pages are in the same

group, CICS does not have a conversion table to match the requested server code page for the client code page specified.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure that the Client codepage and the server codepage are correct. If they are as intended, then CICS can not support the requested

conversion.

Module: DFHCCNV

ACN7

Explanation: An override for the default binary format has been received; however the value is not recognized.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Data formats should be either S/370 or INTEL, anything else is unsupported by CICS/390.

Module: DFHCCNV

ACN8

Explanation: CICS data conversion is processing a FIELD defined as containing GRAPHIC characters (which are only DBCS): that is DFHCNV

TYPE=FIELD,DATATYP=GRAPHIC,... However the client code page (defined in the CLINTCP operand), and the server code page (defined in the SRVERCP

operand) imply that the FIELD contains only SBCS characters, for example DFHCNV TYPE=ENTRY,CLINTCP=437,SRVERCP=037

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Correct the FIELD definition.

Module: DFHCCNV

ACN9

Explanation: The table DFHCNV cannot be loaded. This abend code is issued following a NOTAUTH condition being raised during loading of the DFHCNV

table.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Ensure the resource security definitions are correct.

Module: DFHCCNV

ACP1

Explanation: DFHIC TYPE=GET response code is other than the normal response during print key processing.

System Action: The transaction is abnormally terminated with a CICS transaction dump. The keyboard of the terminal on which the print key was depressed

remains locked to indicate the failure of the operation.

User Response: Analyze the dump. The response code is in the low order byte of register 0.

Module: DFHCPY

ACP2

Explanation: DFHIC TYPE=INITIATE response code is other than the normal response during print key processing.

System Action: The transaction is abnormally terminated with a CICS transaction dump. The keyboard of the terminal on which the print key was depressed

remains locked to indicate the failure of the operation.

User Response: Analyze the dump. The response code is in low-order byte of register 0.

Module: DFHCPY

ACQA

Explanation: The Connection Quiesce Protocol transaction has been initiated by user action, such as a START command or by typing the transaction

identifier at a terminal. The transaction is not intended to be initiated in this way.

System Action:

1. If the transaction was not initiated by terminal input, message DFHZC4951 is written to destination CSNE.

2. An exception trace record is written to all active trace destinations.

3. The transaction is abnormally terminated with a CICS transaction dump.

User Response: Determine what caused the transaction to be initiated. The exception trace record contains information which will help you.

Module: DFHCLS5

ACQB

Explanation: The Connection Quiesce Protocol transaction has encountered an error when communicating with another system on an APPC session.

System Action:

1. Message DFHZC4951 is written to destination CSNE.

2. An exception trace record is written to all active trace destinations.

3. The transaction is abnormally terminated with a CICS transaction dump.

User Response: Determine what caused the failure. A likely cause is a failure of the session with the partner system.

Module: DFHCLS5

ACQC

Explanation: The Connection Quiesce Protocol transaction has encountered an unexpected error.

System Action:

1. Message DFHZC4951 is written to destination CSNE.

2. An exception trace record is written to all active trace destinations.

3. The transaction is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCLS5

ACRA

Explanation: The relay program has been invoked without a terminal as its principal facility.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Ensure that DFHAPRT has not been specified as the initial program of a task that is not terminal-related.

Module: DFHAPRT

ACRB

Explanation: The relay program has been invoked by a transaction that is not defined as remote.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check that the relay program is defined correctly. Determine why DFHAPRT was invoked if the transaction is not a remote transaction.

Module: DFHAPRT

ACRC

Explanation: The relay program received an invalid response from DFHZCX.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHAPRT

ACRD

Explanation: The system entry for the system to which routing is to be performed could not be found.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check the installed transaction definition to confirm that the system was correctly specified. Check that the system entry is defined in the

TCT.

Module: DFHAPRT

ACRE

Explanation: A transaction invoked from an APPC terminal and specified in the installed transaction definition as remote has abnormally terminated

because the link is out of service.

System Action: The task is abnormally terminated.

User Response: Wait until the link is available. The CICS supplied transaction CEMT INQUIRE CONNECTION can be used to check the states of the links.

Module: DFHAPRT

ACRF

Explanation: The relay program received a nonzero return code from the dynamic router following its first invocation.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the dump to determine why the dynamic routing program has failed by checking the contents of the passed COMMAREA DFHDYE for

correctness. The COMMAREA address can be found from field TCACOMM in the system TCA for the task. The COMMAREA fields are mapped via the

DFHDYPDS DSECT.

Module: DFHAPRT

ACRG

Explanation: An ATI initiated remote transaction defined with DYNAMIC(YES) has failed because there is no matching entry in the AID chain.

Each AID in the chain has been checked and none has been found where

The AID terminal ID matches that of the TCTTE

The installed transaction definition and the AID transaction IDs match

The AID is for a remote transaction

The AID has not been canceled.

System Action: The task is abnormally terminated with a CICS system dump.

User Response: The dump can be used to help ascertain the mismatch. Check the transactions listed in the TCTTE and PCT fields of the system dump

against the AID chain.

Module: DFHAPRT

ACRH

Explanation: The profile for the session that will carry intersystem flows during transaction routing could not be found.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check the installed transaction definition to confirm that TRPROF is correctly specified.

Module: DFHAPRT

ACRI

Explanation: An error occurred when attempting to link to the dynamic routing program.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

A message in the range DFHRT4417 to DFHRT4420 is written to the CSMT log.

User Response: Refer to the message sent to the CSMT log. It identifies the cause of the link failure and provides further user guidance.

Modules: DFHAPRT, DFHEPC

ACRJ

Explanation: An abend has occurred in the dynamic routing program after a link has been executed from DFHAPRT or DFHEPC.

System Action: The transaction is abnormally terminated with a CICS transaction dump. Message DFHRT4416 is written to the CSMT log.

User Response: Refer to message DFHRT4416. It identifies the abend in the dynamic routing program and provides further user guidance.

Modules: DFHAPRT, DFHEPC

ACRK

Explanation: The relay program has been invoked with no address for the 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHAPRT

ACRL

Explanation: The task does not own the 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHAPRT

ACRM

Explanation: In response to a request from the dynamic routing program, DFHAPRT has attempted an INITIAL_LINK to a program that is not the initial

program of the transaction for which the dynamic router has been invoked. The attempt has failed.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Examine the following possibilities:

The autoinstall user-replaceable module (URM) was called but is unable to do the autoinstall.

The autoinstall URM was called but data supplied by the autoinstall URM is invalid.

The autoinstall URM was called, but there is no processing program table (PPT) entry for the autoinstall model.

There is a problem with the autoinstall URM.

There is no PPT entry for the program, and either autoinstall is not active or the autoinstall URM indicated that the program should not be autoinstalled.

The program is disabled.

The program cannot be loaded.

The program is defined as remote.

Module: DFHAPRT

ACRN

Explanation: The dynamic routing program has indicated that the transaction should not be routed, but execute in the local system. Prior to invoking the

application program, a security check is performed. This check has failed.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Ensure that the transaction security definition is correct.

Module: DFHAPRT

ACRO

Explanation: An attempt has been made to invoke the CRSQ transaction from a terminal. CRSQ is an internal CICS transaction and cannot be invoked in

this way.

System Action: The task is abnormally terminated.

User Response: None. You can use CEMT and EXEC CICS commands to cancel AIDs.

Module: DFHCRQ

ACRP

Explanation: The dynamic router has supplied a sysid whose supported functions are unknown. This may be due to either a backlevel release, or APPC is

used for communication and no work has flowed across this connection.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Give an alternative sysid, or revert to the old style START, or flow some routed work across the connection.

Module: DFHAPRT

ACSA

Explanation: The remote scheduler task (CRSR) does not own an intersystem link TCTTE as its principal facility.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Ensure that DFHCRS is not specified as the initial program of a task other than CRSR. Check that the terminal operator did not enter

CRSR.

Module: DFHCRS

ACSB

Explanation: An unexpected reply was received from a remote system in response to a request to schedule a task on that 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRS

ACSC

Explanation: An unexpected request was received from a remote system when expecting a request to schedule a task.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRS

ACSD

Explanation: An internal logic error has been detected.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRS

ACSE

Explanation: Module DFHCRS has been attached in an unsupported manner.

System Action: CICS abnormally terminates the transaction with a transaction dump.

User Response: Module DFHCRS should be executed only by transaction CRSR, which executes with an MRO session, an LU6.1 session or an LU type

6.2 conversation as its principal facility. Ensure that the transaction is being attached by a CRSR transaction in the connected system, and not by a user

transaction.

If the transaction is being attached by a CRSR transaction, you will need assistance from IBM to resolve the problem. You need further assistance from IBM

to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCRS

ACSF

Explanation: The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first

detects the purged condition provides an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the reason why the task was purged. It was purged either by the master terminal operator or as a result of a deadlock timeout.

Module: DFHCRS

ACSG

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 will have provided 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: Please see the related error message produced by the domain that detected the original error.

Module: DFHCRS

ACSH

Explanation: The processing of APPC mapped data requires the generation of an LU6.2 attach 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:

The entry in the TCT for the remote system has been defined with parallel sessions

The remote system can support a sync level of 2

The correct sync level has been requested.

Module: DFHCRS

ACSI

Explanation: An APPC conversation failure occurred when an attach between CICS systems was issued.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Check the connection to the remote CICS system and try to reestablish it.

Module: DFHCRS

ACSJ

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain. The

domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table). This failure is

either the result of a task purge, or a CICS logic error.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the related diagnostic material produced by the recovery manager domain and determine the reason for the failure.

In the case of a CICS logic error, you need further assistance from IBM. You need further assistance from IBM to resolve this problem. See Part 4 of the

CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHCRS

ACSL

Explanation: CICS has been unable to attach a transaction to perform a mass flag (CFTS) or mass remote delete (CDTS) request.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRS

ACSM

Explanation: Transaction CFTS has abended. The mass flagging of terminals for deletion has 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRS

ACSN

Explanation: Transaction CFTS has stalled. The mass flagging of terminals for deletion has exceeded the expected time and is therefore assumed to have

failed.

System Action: The task is abnormally terminated with a CICS transaction dump. A flag is set in the remote work element (RWE) to indicate that the

mainline transaction has assumed that CFTS has failed.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRS

ACTA

Explanation: The relay program running in the terminal-owning region has received an unexpected request from the application owning region. The request

received is in violation of CICS transaction routing protocols.

The request will be in the DFHLUCDS DSECT in DFHZTSP's LIFO - field LUCOPN0

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZTSP

ACTB

Explanation: The relay program running in the terminal-owning region issued a terminal control WRITE,LAST request to the application-owning system, and

received a nonzero return code from terminal control.

This is the usual return code from terminal control in TCATPAPR.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why terminal control was unable to process the request.

Module: DFHZTSP

ACTC

Explanation: The relay program running in the terminal-owning region issued a terminal control request to free its session to the application-owning system,

and received a nonzero return code from terminal control.

This is the usual return code from terminal control in TCATPAPR.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why terminal control was unable to process the request.

Module: DFHZTSP

ACTD

Explanation: The relay program running in the terminal-owning region issued a terminal control WRITE,WAIT,READ request to the application-owning

system, and received a nonzero return code from terminal control.

This is the usual return code from terminal control in TCATPAPR.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why terminal control was unable to process the request.

Module: DFHZTSP

ACTE

Explanation: The relay program running in the terminal-owning region attempted to free its session with the APPC terminal, and received a nonzero return

code from terminal control.

The return code will be in the DFHLUCDS DSECT in DFHZTSP's LIFO field, LUCRCODE.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed.

Module: DFHZTSP

ACTF

Explanation: The relay program running in the terminal-owning region issued a terminal control request to free its session to the application-owning system,

and received a nonzero return code from terminal control.

This return code can be found in the TCA field, TCATPAPR.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. The transaction on the application-owning

region may have abnormally terminated or the session may have failed.

Module: DFHZTSP

ACTG

Explanation: The relay program running in the terminal-owning region issued a request to attach a transaction in the application-owning region, but the

response received from that region was invalid.

The return code in the TCA (field TCATPAPR) will be nonzero, and either there will be no TIOA (field TCTTEDA in the TCTTE is zero) or there will be no FMH7

at the start of the TIOA.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. The transaction on the application-owning

region may have abnormally terminated or the session may have failed.

Module: DFHZTSP

ACTH

Explanation: A privileged allocate was issued against a remote LU 6.2 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZISP

ACTI

Explanation: The relay transaction has an ISC or MRO session as its principal facility. However the TCTTE for that session is not owned by the task.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRT

ACTJ

Explanation: The principal facility of the relay transaction is not a TCTTE.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Task CXRT should only be started in a terminal-owning region by an ALLOCATE request issued in an application-owning region against a

remote APPC device. The principal facility of the task should be an ISC or MRO link. Check that your CICS system is defined in such a way that this will

always be the case. Also ensure that program DFHCRT is started only by task CXRT.

Module: DFHCRT

ACTK

Explanation: The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first

detected the purged condition will have provided an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate the reason why the task was purged. It was either purged by the master terminal operator or as a result of a deadlock timeout.

Module: DFHZISP

ACTL

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 will have provided 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.

Module: DFHZISP

ACUA

Explanation: DFHZXRL was called with a request which is not supported for transaction routing.

The request is located in the DFHLUC parameter list which is printed in the exception trace. DFHZXRL is called from DFHZARL, which will put details of the

request in its trace entry.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUB

Explanation: The parameter list passed to DFHZXRL for an ALLOCATE request does not contain the TCTSE address of a remote APPC terminal.

The TCTSE address is located in the DFHLUC parameter list which is printed in the exception trace. DFHZXRL is called from DFHZARL, which will put details

of the request in its trace entry.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUC

Explanation: The TCTSE address passed to DFHZXRL is not that of a remote LU 6.2 terminal.

The TCTSE address is located in the DFHLUC parameter list which is printed in the exception trace. DFHZXRL is called from DFHZARL, which will put details

of the request in its trace entry.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUD

Explanation: The profile DFHCICSR could not be located as an installed profile definition.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Check that the IBM-supplied profile DFHCICSR is correctly defined and installed to CICS.

Module: DFHZXRL

ACUE

Explanation: A request to DFHZTSP to build a surrogate TCTTE was not satisfied.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUF

Explanation: A session between the application-owning region and the terminal-owning region was not allocated because the request was incorrectly

specified.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUG

Explanation: A request to allocate a session between the application-owning region and the terminal-owning region failed. The return code from the

ALLOCATE request indicated that the profile could not be located as an installed transaction definition, although an earlier attempt to locate it was

successful.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUH

Explanation: A request to allocate a session between the application-owning region and the terminal-owning region failed. The return code from the

ALLOCATE request indicated that the requested session is already owned by the TCA.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUI

Explanation: An ISC session between the application-owning region and the terminal-owning region was not allocated because the MODENAME named in

the profile could not be found. The profile DFHCICSR as supplied by IBM does not specify a MODENAME. Therefore, this error will occur when a

MODENAME has been added to the IBM-supplied profile, but that MODENAME is not defined in the SESSIONS definition for the terminal-owning region.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Ensure that the MODENAME specified in profile DFHCICSR was also specified when defining the SESSIONS to the terminal-owning region.

Module: DFHZXRL

ACUJ

Explanation: A session between the application-owning region and the terminal-owning region was not allocated because the maximum session count for

the mode group specified in profile DFHCICSR is zero.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the CEMT transaction to set sessions in the required mode group available for use.

Module: DFHZXRL

ACUK

Explanation: No TCT entry was found for the terminal-owning region specified in the TCTSE for the remote terminal.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Ensure that the terminal-owning region defined in the remote system entry is also defined with a system entry in the TCT.

Module: DFHZXRL

ACUL

Note: The description of this abend also applies to ACUX and ACUZ.

Explanation: The transaction routing program in the application-owning region issued a terminal control WRITE,WAIT,READ request to the terminal-owning

region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The relay program in the terminal-owning region terminates abnormally. In this case, determine the reason why the relay program has abnormally

terminated.

The session has failed.

Module: DFHZXRL

ACUM

Explanation: A request to DFHZTSP to free a surrogate TCTTE was not satisfied.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUO

Note: The description of this abend also applies to ACUQ, ACUS and ACU1.

Explanation: A terminal control READ request has failed. The transaction routing program in the application-owning region attempted to receive data from

the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The relay program in the terminal-owning region terminates abnormally. In this case, determine the reason why the relay program has abnormally

terminated.

The session has failed.

Module: DFHZXRL

ACUP

Note: The description of this abend also applies to ACUR.

Explanation: The transaction routing program in the application-owning region did not receive a rollback from the terminal-owning region. This violates CICS

transaction routing protocols.

The trace from the terminal-owning region will show its response to the application-owning region.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUQ

Explanation: Refer to the description of abend ACUO.

Module: DFHZXRL

ACUR

Explanation: Refer to the description of abend ACUP.

Module: DFHZXRL

ACUS

Explanation: Refer to the description of abend ACUO.

Module: DFHZXRL

ACUT

Explanation: The transaction routing program in the application-owning region did not receive either a syncpoint or a rollback from the terminal-owning

region. This violates CICS transaction routing protocols.

The trace from the terminal-owning region will show its response to the application-owning region.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACUV

Explanation: The transaction routing program in the application-owning region issued a terminal control ISSUE ABEND request on an MRO link to the

terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The relay program in the terminal-owning region terminates abnormally. In this case, determine the reason why the relay program has abnormally

terminated.

The session has failed.

Module: DFHZXRL

ACUW

Explanation: The transaction routing program in the application-owning region issued a terminal control ISSUE ERROR request on an MRO link to the

terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The relay program in the terminal-owning region terminates abnormally. In this case, determine the reason why the relay program has abnormally

terminated.

The session has failed.

Module: DFHZXRL

ACUX

Explanation: Refer to the description of abend ACUL.

Module: DFHZXRL

ACUY

Explanation: The transaction routing program in the application-owning region issued a terminal control WRITE,WAIT request to the terminal-owning region,

and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The relay program in the terminal-owning region terminates abnormally. In this case, determine the reason why the relay program has abnormally

terminated.

The session has failed.

Module: DFHZXRL

ACUZ

Explanation: Refer to the description of abend ACUL.

Module: DFHZXRL

ACU0

Explanation: The transaction routing program in the application-owning region issued a terminal control WRITE,LAST,WAIT request to the terminal-owning

region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The relay program in the terminal-owning region terminates abnormally. In this case, determine the reason why the relay program has abnormally

terminated.

The session has failed.

Module: DFHZXRL

ACU1

Explanation: Refer to the description of abend ACUO.

Module: DFHZXRL

ACU2

Explanation: The transaction routing program in the application-owning region received a response from the terminal-owning region which violates CICS

transaction routing protocols.

The trace from the terminal-owning region will show its response to the application-owning region.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACU3

Explanation: The transaction routing program in the application-owning region attempted to set the conversation state machine to a state which violates

CICS transaction routing protocols.

The register containing the state can be determined from the assembler listing.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACU4

Explanation: The transaction routing program in the application-owning region issued a SET request to the conversation state machine and received a

nonzero return code. This violates CICS transaction routing protocols.

The trace entry on return from DFHZUSR will show the request type and current state.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACU5

Explanation: An program running in an application-owning region has issued an ALLOCATE against an APPC device attached to a terminal owning region,

but the connection between the two systems is not installed.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Install the connection between the two regions.

Module: DFHZXRL

ACU6

Explanation: A request to DFHRTSU to prepare the surrogate TCTTE for syncpoint gave an unexpected response and reason code. The response and

reason code are included in DFHRTSU's parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACU7

Explanation: A request to allocate a session between the application-owning region and the terminal-owning region was issued, 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.

Module: DFHZXRL

ACU8

Explanation: A request to DFHRTSU to get the recovery status of a surrogate TCTTE gave an unexpected response and reason code. The response and

reason code are included in DFHRTSU's parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACU9

Explanation: A request to recovery manager to set the recovery status of a link gave an unexpected response and reason code. The response and reason

code are included in DFHRMLN's parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRL

ACVA

Explanation: The transaction routing program in the terminal-owning region issued a terminal control WRITE,WAIT,READ request to the application-owning

region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVB

Explanation: The transaction routing program in the terminal-owning region attempted to issue an ISSUE SIGNAL request on an MRO link to the

application-owning region. This violates CICS transaction routing protocols.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRT

ACVC

Explanation: The transaction routing program in the terminal-owning region issued an ISSUE SIGNAL request on an LU 6.2 link to the application-owning

region, and received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVD

Explanation: The transaction routing program in the terminal-owning region issued a READ,WAIT request to the application-owning region, and received a

nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVE

Explanation: The transaction routing program in the terminal-owning region issued a WRITE request to the application-owning region, and received a

nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

the program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

the session has failed.

Module: DFHZXRT

ACVF

Explanation: The transaction routing program in the terminal-owning region issued a WRITE,LAST,WAIT request to the application-owning region, and

received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVG

Explanation: The transaction routing program in the terminal-owning region issued a FREE request to free the session with the LU 6.2 terminal, and

received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed.

Module: DFHZXRT

ACVH

Explanation: The transaction routing program in the terminal-owning region issued a FREE request to free the session with the application-owning region,

and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVK

Explanation: The transaction routing program in the terminal-owning region issued an ISSUE ABEND request on an LU 6.2 link, and received a nonzero

return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the connected region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVL

Explanation: The transaction routing program in the terminal-owning region issued an ISSUE ABEND request on an MRO link to the application-owning

region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVM

Explanation: The transaction routing program in the terminal-owning region issued an ISSUE ERROR request on an LU 6.2 link, and received a nonzero

return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the connected region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVN

Explanation: The transaction routing program in the terminal-owning region issued an ISSUE ERROR request on an MRO link to the application-owning

region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

The program in the application-owning region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Module: DFHZXRT

ACVO

Explanation: The transaction routing program in the terminal-owning region issued an ISSUE PREPARE request and received either a nonzero return code

or a response which violates CICS transaction routing protocols.

The return code is located in TCASPRC and the response is located in TCASPSN1.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine whether the problem is caused by the return code or the response. If terminal control was unable to

process the request, the abend may occur when:

The program in the connected region terminates abnormally. In this case, determine the reason why the program has abnormally terminated.

The session has failed.

Otherwise the distributed application programs may have violated APPC conversation protocols.

Module: DFHZXRT

ACVP

Explanation: The transaction routing program in the terminal-owning region did not receive an FMH43 from the application-owning region. This violates CICS

transaction routing protocols.

The trace from the application-owning region will show its response to the terminal-owning region.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHZXRT

ACVQ

Explanation: The transaction routing program in the terminal-owning region issued a request to the APPC terminal, and received a nonzero return code from

terminal control.

Both the request and the return code are located in the DFHLUC parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed or be

in the wrong state, for example, as the result of both the terminal and application issuing SYNCPOINT ROLLBACK at the same time.

Module: DFHZXRT

ACVR

Explanation: The transaction routing program in the terminal-owning region issued a SEND,LAST,WAIT request to the LU 6.2 terminal, and received a

nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System Action: The task is abnormally terminated with a transaction dump and an exception trace entry.

User Response: Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed.

Module: DFHZXRT

ACWA

Explanation: CICS CWTO transaction has failed because the task does not own a terminal (TCTTE) as its principal facility. This has probably happened

because CWTO has been started as an EXEC CICS START transid without a terminal ID.

System Action: The transaction is abnormally terminated without a transaction dump.

User Response: Retry with a terminal ID value or enter CWTO from a terminal.

Module: DFHCWTO

ACXA

Explanation: The catch-up transaction, CXCU, has failed. CXCU runs either in response to a transaction request from an end-user, or is run automatically

by an active CICS system in response to the appearance of an alternative CICS system. Its purpose is to inform the alternate system of the active system's

state regarding terminals and DBCTL connection.

System Action: The catch-up transaction, CXCU, is abnormally terminated with a CICS transaction dump. Both active and alternate CICS systems

continue, but the alternate CICS system is less effective in the event of a takeover. For example, terminal back-up sessions may not be established. This

abend is accompanied by DFHDX8313.

User Response: Retry by entering 'CXCU' from a terminal. If the error persists, diagnose the problem from the dump.

Module: DFHCXCU

ADCA

Explanation: This abend is issued if DBCTL returns a non-zero response code when a DL/I request has been issued from an application program.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Look up accompanying message DFHDB8109 that appears on the CDBC transient data destination.

Module: DFHDLIDP

ADCB

Explanation: This abend occurs when DBCTL has notified CICS that a task has issued a DL/I request, but it did not have a PSB scheduled. If your

application does have a PSB scheduled then a possible cause for this abend is that the DBCTL STOP THREAD command may have been used to terminate

the DBCTL thread that corresponds to this task.

System Action: CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: Check if the DBCTL operator has issued a STOP THREAD command for the task that has abnormally terminated. Look up DBCTL

response code 28 in the DBCTL return code section of the IMS Messages and Codes manual.

Module: DFHDLIDP

ADCC

Explanation: This abend occurs when DBCTL has notified CICS that a task has issued program specification block (PSB) request, but it has a PSB

already scheduled. CICS prevents a task from issuing a PSB schedule request to DBCTL when it has already issued a PSB schedule request by returning a

PSBSCH response in UIBDLTR. However, in this case it is DBCTL that has rejected the subsequent PSB schedule request. A possible cause for this abend

is a storage over-write.

System Action: CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: Check for any messages issued from your CICS system indicating that storage over-writes have taken place. Look up DBCTL response

code 32 in the DBCTL return code section of the IMS Messages and Codes manual.

Module: DFHDLIDP

ADCD

Explanation: This abend is issued when a deadlock has been detected by IMS and this transaction has been selected for abnormal termination.

This abend can occur when a transaction is accessing IMS resources via DBCTL or via a remote DLI request to a remote CICS region. The remote CICS

region can be accessing IMS via DBCTL, or if it is a CICS 4.1 region or earlier, accessing IMS via local DLI.

System Action: Access to IMS resources via DBCTL is withdrawn for this transaction. Further attempts to access IMS will result in an AEY9 abend.

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: If ADCD abends occur infrequently in your system, no action is required although you may like to consider setting your system up in such

a way that, after an ADCD abend is issued, the transaction is automatically restarted. See the CICS Recovery and Restart Guide for further information.

If ADCD abends are occurring frequently in your system, you may need to review the design of your applications. Some general techniques for deadlock

avoidance are described in the CICS Recovery and Restart Guide.

Module: DFHDLIDP

ADCE

Explanation: This abend is issued when the module DFHDBAT returns a nonzero return code in reply to a DL/I request issued from an application program

to DBCTL. DFHDBAT is a task related user exit and forms part of the CICS-DBCTL interface. This abend is accompanied by message DFHDB8110.

System Action: CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: Look up the accompanying message DFHDB8110 that appears on the CDBC transient data destination.

Module: DFHDLIDP

ADCI

Explanation: This abend is issued when IMS returns a user abend 3303 response for a DL/I request issued from an application program.

System Action: Access to IMS resources via DBCTL is withdrawn for this transaction. Further attempts to access IMS will result in an AEY9 abend.

CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: Check the description in the IMS Messages and Codes manual for the meaning of IMS user abend 3303.

Module: DFHDLIDP

ADCJ

Explanation: This abend is issued when an application has been using DBCTL, and while the application was still scheduled to DBCTL, the CICS-DBCTL

interface was terminated.

System Action: CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: Check the CDBC transient data destination for messages indicating the reason for termination of the CICS-DBCTL interface. If you do not

know where the CDBC transient is, then please check with your system programmer. Check for messages issued from the DBCTL system.

Module: DFHDLIDP

ADCP

Explanation: When checking the DBCTL program specification block (PSB), the external security manager checked the usage of the PSB, and found that:

The user was unauthorized to access the PSB, or

The PSB was unknown to the external security manager, or

The user was set to the capability of the default user.

The meaning of the term "user" in the above context depends on the way the transaction was invoked.

If the transaction is being run from a local terminal, or has been routed from a remote terminal, the user is the terminal user. (For a routed transaction, if

PSBCHK=NO is specified in the SIT, or RESSEC=NO is specified in the transaction definition (CEDA DEFINE TRANSACTION command), the security

manager does not check the terminal user.)

If the transaction is being run as a result of a request from another CICS MRO region, the user is the owner of the other CICS system (as defined to the

external security manager in the JOB statement of the initializing JCL).

If the transaction is being run as a result of a request from a connected ISC system, the user is defined in the SECURITYNAME operand of the installed

CONNECTION definition that defines the link between the remote system and the local system. Ensure that the name in the SECURITYNAME operand is

the same as that supplied by the connected CICS system. This will depend upon the type of CONNECTION between the two systems. For further

information about this, refer to the CICS Intercommunication Guide.

Notes.

By the above definitions, a PSB used by a routed transaction has two users, the terminal user and the communicating region. Therefore, for routed

transactions, the external security manager makes two checks, on the terminal user (as qualified in 1 above), and on the communicating region (2 or 3

above).

System Action: CICS abnormally terminates the task attempting to schedule the PSB. CICS processing continues.

User Response: Ensure that the PSB is defined to the external security manager, and that all users have the correct level of authorization. If the system

setup is correct, note the security violation.

Module: DFHDLIDP

ADCQ

Explanation: This abend occurs when an application has issued an EXEC DLI SCHD request for a PSB that contains no DBPCBs, and the SYSSERVE

keyword was not specified. This abend also occurs when an application has issued a PCB request for a PSB that contains no DBPCBs, and the IOPCB

option was not specified.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check that the application program has scheduled the appropriate PSB.

Module: DFHDLIDP

ADCR

Explanation: This abend occurs when an application has issued a DL/I request other than a schedule request, and the DBCTL DRA return code of 40

indicates that there was no active communication with DBCTL.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check the CDBC transient data destination for messages indicating the reason for termination of the CICS-DBCTL interface. If you do not

know where the CDBC transient data destination is, check with your system programmer. Check for messages issued from the DBCTL system.

Module: DFHDLIDP

ADCS

Explanation: CICS issued a single-phase commit request to DBCTL and an unexpected response was returned from DBCTL.

System Action: CICS issues message DFHDB8119 to transient data queue CDBC, then terminates the task abnormally with a CICS transaction dump.

User Response: Message DFHDB8119 shows the unexpected response from DBCTL, along with the recovery token of the LUW involved. The explanation of

message DFHDB8119 indicates how the outcome of the LUW can be determined.

Module: DFHDBAT

ADCT

Explanation: A user has attempted to invoke the CICS-DBCTL control transaction from a terminal.

System Action: CICS rejects the request.

User Response: Do not try to invoke CICS internal transactions directly.

Module: DFHDBCT

ADCV

Explanation: The connection to DBCTL was terminated and then re-established. The failing task had issued a schedule request against an earlier run of

DBCTL and is therefore no longer scheduled.

System Action: CICS abnormally terminates the transaction with a transaction dump. CICS processing continues.

User Response: No action is required, although you may like to consider setting your system up in such a way that, after an abend ADCV is issued, the

transaction is automatically restarted.

Module: DFHDLIDP

ADDA

Explanation: An error (INVALID or DISASTER response) has occurred on a call to the storage manager domain. The domain that detected the original error

provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System Action: The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User Response: See related message from the domain that detected the original error.

Modules: DFHDBME, DFHDLI, DFHDLIDP

ADDB

Explanation: An error (INVALID or DISASTER response) has occurred on a call to the catalog (CC) domain. The domain that detected the original error

provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System Action: The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User Response: See related message from the domain that detected the original error.

Modules: DFHDBCON, DFHDBDSC

ADDC

Explanation: An error (INVALID or DISASTER response) has occurred on a call to the loader (LD) domain. The domain that detected the original error will

have provided an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System Action: The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User Response: See related message from the domain that detected the original error.

Modules: DFHDBCON, DFHDBDI

ADDI

Explanation: CICS has been notified of a DBCTL failure. However, it has been unable to complete the search for a DBCTL alternate. This is possibly due to

an unexpected return code from an IEFSSREQ request.

System Action: A CICS transaction dump is produced. CICS continues as if no XRF DBCTL alternate has been found. This abend is accompanied by

message DFHDX8323.

User Response: Refer to message DFHDX8323 for further information. It may be necessary to restart DBCTL manually.

Module: DFHDBCT

ADDJ

Explanation: CICS has failed to connect to DBCTL because program DFHDBAT could not be ENABLED.

System Action: A CICS transaction dump is produced. The state of the CICS/DBCTL interface remains not connected.

User Response: Refer to the transaction dump to determine why the ENABLE failed.

Module: DFHDBCON

ADEF

Explanation: A severe error has been encountered when executing transaction CLS3.

System Action: CLS3 is abnormally terminated with a transaction dump. CICS issues message DFHZC4948.

User Response: See message DFHZC4948 for further guidance.

Module: DFHCLS3

ADIR

Explanation: The abend code is issued for either of the following reasons:

A DFHDI or DFHBMS request was issued when the DFHDIP program was generated as a dummy.

A DFHDI TYPE=RECEIVE or TYPE=NOTE was attempted but the transaction identification did not specify either INBFMH=DIP or INBFMH=ALL.

System Action: A CICS transaction dump is provided to assist in problem determination.

User Response: Either generate a DFHDIP program into the system or specify INBFMH correctly on the profile definition.

Module: DFHDIP

ADLE

Explanation: A DL/I request was made for a remote database, but the system named in the remote PDIR entry was unknown to CICS, that is, not specified

in a DFHTCT TYPE=SYSTEM macro or CEDA DEFINE CONNECTION command.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Either correct the SYSIDNT parameter in the relevant DFHDLPSB entry, or define the remote system to CICS with a DFHTCT

TYPE=SYSTEM macro or a CEDA DEFINE CONNECTION command.

Module: DFHDLIRP

ADLF

Explanation: A DL/I request was made for a remote database, but the link to the system on which the database resides was down.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Notify the system programmer. Once the link to the remote system has been reestablished, resubmit the transaction.

Module: DFHDLIRP

ADLG

Explanation: A DL/I request was made for a remote database, but there were errors in the DL/I argument list that was provided by the user.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Ensure that any errors in the DL/I argument are corrected.

Module: DFHDLIRP

ADLP

Explanation: When checking the DLI program specification block (PSB), the external security manager checked the usage of the PSB, and found that:

The user was unauthorized to access the PSB, or

The PSB was unknown to the external security manager, or

The user was set to the capability of the default user.

The meaning of the term "user" in the above context depends on the way the transaction was invoked.

If the transaction is being run from a local terminal, or has been routed from a remote terminal, the user is the terminal user. (For a routed transaction, if

PSBCHK=NO is specified in the SIT, or RESSEC=NO is specified in the transaction definition (CEDA DEFINE TRANSACTION command), the security

manager does not check the terminal user.)

If the transaction is being run as a result of a request from another CICS MRO region, the user is the owner of the other CICS system (as defined to the

external security manager in the JOB statement of the initializing JCL).

If the transaction is being run as a result of a request from a connected ISC system, the user is defined in the SECURITYNAME operand of the installed

CONNECTION definition that defines the link between the remote system and the local system. Ensure that the name in the SECURITYNAME operand is

the same as that supplied by the connected CICS system. This will depend upon the type of CONNECTION between the two systems. For further

information about this, refer to the CICS Intercommunication Guide.

Note: By the above definitions, a PSB used by a routed transaction has two users, the terminal user and the communicating region. Therefore, for routed

transactions, the external security manager makes two checks, on the terminal user (as qualified in 1 above), and on the communicating region (2 or 3

above).

System Action: The task attempting to schedule the PSB abnormally terminates.

User Response: Ensure that the PSB is defined to the external security manager, and that all users have the correct level of authorization. If the system

setup is correct, note the security violation.

Module: DFHDLIRP

ADMA

Explanation: The alternate CICS task responsible for tracking the DBCTL connection status of the active CICS has received an error from the CICS

Availability Manager (CAVM) message input service.

System Action: The tracking transaction terminates with a CICS transaction dump. No further action is taken in response to DBCTL status changes. The

global exits, XXDFB and XXDTO, are never invoked and no attempt at a DBCTL restart is made in the event of a takeover. This abend is accompanied by

DFHDX8331.

User Response: Check for any other messages relating the CAVM dataset problems. In the event of a takeover, it may be necessary to restart DBCTL

manually.

Module: DFHDBCR

ADMB

Explanation: The CICS/XRF DBCTL tracking task has received an unrecognizable message from the CICS/XRF message manager. This abend is preceded

by message DFHDX8333.

System Action: The CICS/XRF DBCTL tracking task abends.

User Response: Refer to the instructions for message DFHDX8333.

Module: DFHDBCR.

ADMD

Explanation: The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has been unable to complete its

search for a DBCTL alternate, possibly due to an unexpected return code from an IEFSSREQ request.

System Action: A CICS transaction dump is produced. The tracking transaction continues as if no DBCTL alternate had been found. This abend is

accompanied by message DFHDX8335.

User Response: Refer to message DFHDX8335 for further information. It may be necessary to restart DBCTL manually.

Module: DFHDBCR.

ADPL

Explanation: A server program has issued a command which is restricted in the distributed program link (DPL) environment. Certain API and CPI-RR

requests, and the DL/I terminate request are not allowed in the DPL environment. See the CICS Application Programming Guide for a list of these restricted

commands.

A server program is a program which has been remotely linked, or a program defined to run with the DPL subset.

System Action: CICS abends the transaction with a transaction dump.

User Response: Remove the restricted commands from the server program, or run the server program locally.

Module: DFHEIP, DFHCPIR, DFHDLI

ADXA

Explanation: The XRF DBCTL state catch-up transaction, DXCU, has failed.

System Action: DXCU is abnormally terminated with a CICS transaction dump. This abend is accompanied by DFHDX8319.

User Response: Diagnose the error from the CICS transaction dump. Refer to DFHDX8319 for further information.

Module: DFHDXCU

ADXB

Explanation: The XRF DBCTL state catch-up transaction, DXCU, has failed.

System Action: DXCU is abnormally terminated with a CICS transaction dump. This abend is accompanied by DFHDX8318.

User Response: Use the dump to help diagnose the problem. Refer to DFHDX8318 for further information. Check for any other messages relating to CICS

availability manager (CAVM) data set problems.

Module: DFHDXCU

AD2A

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain. A

console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2B

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain. A

console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2C

Explanation: An unexpected EXCEPTION response has occurred on a locate call to directory manager (DD) domain to locate a DB2TRAN control block. A

console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2D

Explanation: An error (INVALID or DISASTER response ) has occurred on a locate call to directory manager (DD) domain to locate a DB2TRAN control

block. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2E

Explanation: An unexpected EXCEPTION response has occurred on a locate call to directory manager (DD) domain to locate a DB2ENTRY control block.

A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2F

Explanation: An error (INVALID or DISASTER response ) has occurred on a locate call to directory manager (DD) domain to locate a DB2ENTRY control

block A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2G

Explanation: A transaction attempted to use a DB2ENTRY that is DISABLED or is DISABLING. The DISABLEDACT attribute of the DB2ENTRY specified

ABEND meaning that new transactions that attempt to use the DB2ENTRY should be abended.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use CEMT INQ DB2TRAN TRANSID(tttt) where tttt is the transid, to determine the name of the DB2ENTRY involved. Re-enable the

DB2ENTRY or discard the DB2ENTRY so that the transid will use a pool thread.

Module: DFHD2EX1

AD2H

Explanation: The CICS-DB2 attachment facility detected that a dynamic plan exit program abended.

System Action: CICS trapped the abend from the dynamic plan exit, issued message DFHDB2050, and then abnormally terminated the task with a CICS

transaction dump.

User Response: See the associated DFHDB2050 transient data message to determine the abend code with which the dynamic plan exit program abended.

Determine why the exit program abended.

Module: DFHD2EX1

AD2I

Explanation: The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because it was not link edited AMODE 31.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the associated DFHDB2051 transient data message to determine the name of the dynamic plan exit program involved. Re-linkedit the

dynamic plan exit program AMODE 31.

Module: DFHD2EX1

AD2J

Explanation: The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because it is disabled.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the associated DFHDB2053 transient data message to determine the name of the dynamic plan exit program involved. Enable the

dynamic plan exit program.

Module: DFHD2EX1

AD2K

Explanation: The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because no program definition was found.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the associated DFHDB2057 transient data message to determine the name of the dynamic plan exit program involved. Ensure that the

dynamic plan exit program has been correctly defined to CICS.

Module: DFHD2EX1

AD2L

Explanation: The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because the program could not be loaded.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the associated DFHDB2058 transient data message to determine the name of the dynamic plan exit program involved. Ensure that the

dynamic plan exit program has been correctly defined and is in a load library accessible to CICS.

Module: DFHD2EX1

AD2M

Explanation: The CICS-DB2 attachment facility failed to link to a dynamic plan exit program because the program is defined as remote.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the associated DFHDB2066 transient data message to determine the name of the dynamic plan exit program involved. Correct the

program definition for the dynamic plan exit program so that it is defined as local.

Module: DFHD2EX1

AD2N

Explanation: The CICS-DB2 attachment facility failed to link to a dynamic plan exit program.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: See the associated DFHDB2054 transient data message to determine the name of the dynamic plan exit program involved. Examine the

transaction dump to determine why the link failed.

Module: DFHD2EX1

AD2O

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an WAIT_MVS call to the dispatcher (DS) domain. A

console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2P

Explanation: The transaction was unable to obtain a DB2 thread from a DB2ENTRY or the pool. See the associated transient data message DFHDB2011

to determine which DB2ENTRY was involved or whether it was the pool. The transaction was abended because the DB2ENTRY or the pool specified

threadwait(no) meaning do not wait for a thread if all threads are currently in use. Note if message DFHDB2011 indicates that the pool was being used, it

means the transaction was using the pool directly rather than overflowing to the pool. (An abend AD3T is produced when a transaction overflows to the pool

and no pool threads are available.)

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Determine whether more threads should be allocated to the DB2ENTRY or the pool, or whether the number of instances of this transaction

should be limited using TRANCLASS.

Module: DFHD2EX1

AD2Q

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an getmain call to the storage manager (SM) domain.

A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2R

Explanation: The CICS-DB2 thread TCB processing the DB2 request for this transaction has abended. An exception trace (AP 319D) is written containing

the MVS abend code and reason code as well as the relevant CICS-DB2 control blocks used by the CICS task and the CICS-DB2 thread TCB. In particular

the CSUB control block contains data from the MVS SDWA at the time of the abend, for example fields CSB_SDWA_REGS (regs 0 -15) and

CSB_SDWA_PSW.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Examine the trace in the CICS transaction dump to determine why the CICS-DB2 thread TCB abended.

Module: DFHD2EX1

AD2S

Explanation: The thread TCB servicing the DB2 request for the transaction issued a sign-on request to DB2 which failed. The installed DB2CONN specifies

THREADERROR(N906D) or THREADERROR(ABEND).

System Action:

If THREADERROR(N906D) is specified in the DB2CONN, processing continues. A -906 sqlcode is returned to the application, and a transaction dump is

taken with abend code AD2S.

If THREADERROR(ABEND) is specified in the DB2CONN, the task is abnormally terminated with a CICS transaction dump.

User Response: Examine the AUTHID or AUTHTYPE parameter of the DB2ENTRY or pool used for the transaction. Ensure the id is authorised to access

the plan in DB2.

Module: DFHD2EX1

AD2T

Explanation: An attempt to create a DB2 thread by the TCB servicing the DB2 request for the transaction failed with DB2 reason code 00F30040. The

installed DB2CONN specifies THREADERROR(N906D) or THREADERROR(ABEND).

System Action:

If THREADERROR(N906D) is specified in the DB2CONN, processing continues. A -906 sqlcode is returned to the application and a transaction dump is

taken with abend code AD2T.

If THREADERROR(ABEND) is specified in the DB2CONN, the task is abnormally terminated with a CICS transaction dump.

User Response: Either the plan is unavailable or is not known to DB2.

Module: DFHD2EX1

AD2U

Explanation: An attempt to create a DB2 thread by the TCB servicing the DB2 request failed. The installed DB2CONN specifies THREADERROR(N906D)

or THREADERROR(ABEND).

System Action:

If THREADERROR(N906D) is specified in the DB2CONN, processing continues. A -906 sqlcode is returned to the application and a transaction dump is

taken with abend code AD2U.

If THREADERROR(ABEND) is specified in the DB2CONN, the task is abnormally terminated with a CICS transaction dump.

User Response: Examine the dump to determine why the create thread failed.

Module: DFHD2EX1

AD2V

Explanation: The CICS-DB2 attachment facility issued a commit or abort request to DB2 but received a reason code 00F30805 indicating that connection

to DB2 has been lost. This is due to DB2 terminating abnormally or being in the process of terminating abnormally. If the commit or abort request was

preceded by a prepare request, DB2 may well still be indoubt. In this case, the CICS-DB2 attachment facility instructs CICS to remember the outcome of the

UOW pending resynchronisation, which will happen when CICS and DB2 are reconnected. For an abort request not preceded by a prepare, i.e. a transaction

abend or syncpoint rollback, DB2 will not be indoubt as the UOW was still inflight. DB2 will backout updates made by the UOW when restarted so there is no

need for CICS to remember the outcome of the UOW.

System Action: The transaction completes normally but a transaction dump is taken with abend code AD2V. If DB2 is indoubt about the outcome of the

UOW it will be resolved when CICS and DB2 are reconnected.

User Response: Contact your system programmer to restart the DB2 subsystem.

Module: DFHD2EX1

AD2W

Explanation: The CICS-DB2 attachment facility issued a single-phase commit call to DB2 but received an unexpected response. Transient data message

DFHDB2055 details the DB2 reason code received. The commit request may have been processed or it may have been ended. There is no resynchronisation

needed, as no CICS recoverable resources were updated.

System Action: The CICS-DB2 attachment facility abnormally terminates the transaction with abend code AD2W. The CICS recovery manager will

supersede the AD2W abend code with abend code ASPR. A transaction dump is taken.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2X

Explanation: The CICS-DB2 attachment facility detected that the CICS task and the thread TCB were in an invalid state. A console message is output, an

exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The task is abnormally terminated with a transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD2Y

Explanation: The transaction was unable to obtain a DB2 thread from a DB2ENTRY or the pool because there were no TCBs available on which to create

the thread. The number of thread TCBs currently running is at the TCBLIMIT defined in the DB2CONN. Message DFHDB2010 is output to transient data. The

transaction was abended because either:

The DB2ENTRY specifies threadwait(no), meaning do not wait for a thread, including having to wait to create a thread because a TCB is not available -

that is, do not wait for a TCB either.

The DB2ENTRY specified threadwait(pool), but the pool definition within the DB2CONN specifies threadwait(no), and again there were no TCBs available.

The transaction was using the pool directly, the pool specifies threadwait(no) and no TCB was available.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Determine whether TCBLIMIT should be increased or whether the number of transactions using DB2 at any one instance should be limited

using transaction classes.

Module: DFHD2EX1

AD2Z

Explanation: DB2 detected a deadlock and the CICS-DB2 attachment facility attempted a syncpoint rollback command for the transaction as

DROLLBACK(YES) was specified for the DB2ENTRY or POOL. The syncpoint rollback command failed. Message DFHDB2070 is output to transient data

detailing the transid involved and the EIBRESP2 from the failed syncpoint rollback command.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Examine the eibresp2 value to determine why the syncpoint rollback request failed. One possible reason could be that the transaction

running is a DPL server transaction which was DPLed to by a client transaction without specifying the SYNCONRETURN parameter. In this case syncpoints,

or syncpoint rollbacks, cannot be taken by the server transaction, so DROLLBACK(YES) is invalid in this case.

Module: DFHD2EX1

AD21

Explanation: The CICS-DB2 attachment facility received a request for a resource manager with the incorrect name. Message DFHDB2045 is output to

transient data detailing the invalid name.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD22

Explanation: The CICS-DB2 attachment facility EDF processor was unable to interpret the SQL request.

System Action: The command is not interpreted by EDF. A CICS transaction dump is taken with abend code AD22.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EDF

AD23

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain made by

the CICS-DB2 attachment facility service transaction CEX2. A console message is output, an exception trace written and, possibly, a system dump taken

(depending on the options specified in the dump table).

System Action: The CICS-DB2 service task initiates a force shutdown of the CICS-DB2 interface.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX2

AD24

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain

made by the CICS-DB2 attachment facility service transaction CEX2. A console message is output, an exception trace written and, possibly, a system dump

taken (depending on the options specified in the dump table).

System Action: The CICS-DB2 Service task initiates a force shutdown of the CICS-DB2 interface.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX2

AD25

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain made by

the CICS-DB2 attachment facility while processing a DSNC command. A console message is output, an exception trace written and, possibly, a system

dump taken (depending on the options specified in the dump table).

System Action: The DSNC command fails and the transaction is abnormally terminated with a transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CC

AD26

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain

made by the CICS-DB2 attachment facility while processing a DSNC command. A console message is output, an exception trace written and, possibly, a

system dump taken (depending on the options specified in the dump table).

System Action: The DSNC command fails and the transaction is abnormally terminated with a transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CC

AD27

Explanation: The CICS-DB2 attachment facility attempted to attach a TCB on which a DB2 thread was to be created to service the SQL request from the

application. The attach of the TCB failed due to lack of storage.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Increase the size of the CICS region or lower the TCBLIMIT value specified in the DB2CONN.

Module: DFHD2EX1

AD28

Explanation: The CICS-DB2 attachment facility attempted to attach a TCB on which a DB2 thread was to be created to service the SQL request from the

application. The attach of the TCB failed.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD29

Explanation: The CICS-DB2 attachment facility was unable to link to its EDF processor DFHD2EDF.

System Action: The command is not interpreted by EDF. Message DFHDB2048 is output to transient data and a transaction dump is taken with abend

code AD29.

User Response: Examine the trace in the CICS transaction dump to determine why the link to module DFHD2EDF failed.

Module: DFHD2EDF

AD3A

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a LOCK call to the lock manager (LM) domain made by

the CICS-DB2 attachment facility startup program. A console message is output, an exception trace written and, possibly, a system dump taken (depending

on the options specified in the dump table).

System Action: Startup of the CICS-DB2 interface is terminated, and the interface is closed. The task is abnormally terminated with a CICS transaction

dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2STR

AD3B

Explanation: An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on an UNLOCK call to the lock manager (LM) domain

made by the CICS-DB2 Attachment facility startup program. A console message is output, an exception trace written and, possibly, a system dump taken

(depending on the options specified in the dump table).

System Action: Startup of the CICS-DB2 interface is terminated, and the interface is closed. The task is abnormally terminated with a CICS transaction

dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2STR

AD3C

Explanation: An error (INVALID, DISASTER response) has occurred on a CONNECT_TO_DB2 function call to the CICS-DB2 Coordinator program

DFHD2CO made by the CICS-DB2 Attachment facility startup program. A console message is output, an exception trace written and, possibly, a system

dump taken (depending on the options specified in the dump table).

System Action: Startup of the CICS-DB2 interface is terminated, and the interface is closed. The task is abnormally terminated with a CICS transaction

dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2STR

AD3D

Explanation: An unexpected response was received while attempting to delete a record from a temporary storage queue during processing of a DSNC

STRT command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the

dump table).

System Action: The DSNC STRT command fails. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3E

Explanation: During processing of a DB2 request for the transaction, an identify request was made to identify the calling TCB to DB2. The identify request

failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The DB2 request fails. The task is abnormally terminated with a CICS transaction dump.

User Response: Examine the exception trace in the dump to determine why the identify request failed. The CSUB control block is output as part of the

exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The identify request contains eyecatcher

"IDEN" and is followed by the DB2 FRB response and reason codes.

Module: DFHD2D2

AD3F

Explanation: During processing of a DB2 request for the transaction, a terminate thread request was made to DB2 which failed. A console message is

output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The DB2 request fails. The task is abnormally terminated with a CICS transaction dump.

User Response: Examine the exception trace in the dump to determine why the terminate thread request failed. The CSUB control block is output as part of

the exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The terminate thread request contains

eyecatcher "TERM" and is followed by the DB2 FRB response and reason codes.

Module: DFHD2D2

AD3G

Explanation: An unexpected response was received from an EXEC CICS GETMAIN issued during processing of a CICS-DB2 DSNC command. A console

message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The DSNC command fails. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3I

Explanation: An unexpected response was received from an EXEC CICS INQUIRE DB2CONN command issued during startup of the CICS-DB2 interface. A

console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: Startup of the CICS-DB2 interface is terminated, and the interface is closed. The task is abnormally terminated with a CICS transaction

dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3J

Explanation: A commit request to DB2, issued during the second phase of syncpoint, failed. A console message is output, an exception trace written and,

possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The task is abnormally terminated with a CICS transaction dump. CICS maintains a record that the UOW committed pending a future

resynchronization request with DB2.

User Response: Examine the exception trace in the dump to determine why the commit request failed. The CSUB control block is output as part of the

exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The commit request contains eyecatcher

"COMM" and is followed by the DB2 FRB response and reason codes.

Module: DFHD2D2

AD3K

Explanation: An abort request to DB2, issued during the second phase of syncpoint, failed. A console message is output, an exception trace written and,

possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The task is abnormally terminated with a CICS transaction dump. CICS maintains a record that the UOW backed out pending a future

resynchronization request with DB2.

User Response: Examine the exception trace in the dump to determine why the abort request failed. The CSUB control block is output as part of the

exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The abort request contains eyecatcher

"ABRT" and is followed by the DB2 FRB response and reason codes.

Module: DFHD2D2

AD3L

Explanation: During processing of a DB2 request for the transaction, an associate request was made to associate the DB2 connection with the calling

TCB. The associate request failed. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options

specified in the dump table).

System Action: The DB2 request fails. The task is abnormally terminated with a CICS transaction dump.

User Response: Examine the exception trace in the dump to determine why the associate request failed. The CSUB control block is output as part of the

exception trace entry, and it contains a record of all calls to DB2 starting at field CSB_TRACE_ENTRIES_START. The associate request contains

eyecatcher "ASSO" and is followed by the DB2 FRB response and reason codes.

Module: DFHD2D2

AD3M

Explanation: An unexpected error occurred during processing of a DSNC MODIFY command. A console message is output, an exception trace written

and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The DSNC MODIFY command fails. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3P

Explanation: An unexpected error occurred during processing of a DSNC STOP command. A console message is output, an exception trace written and,

possibly, a system dump taken (depending on the options specified in the dump table).

System Action: The DSNC STOP command fails. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3Q

Explanation: An unexpected response was received while attempting to read a record from a temporary storage queue during processing of a DSNC STRT

command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump

table).

System Action: The DSNC STRT command fails. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3R

Explanation: An unexpected response was received while attempting to read a record from a temporary storage queue during startup of the CICS-DB2

interface. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump

table).

System Action: Startup of the CICS-DB2 interface is terminated, the interface is closed. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2STR

AD3S

Explanation: An unexpected response was received from an EXEC CICS SET DB2CONN command issued during startup of the CICS-DB2 interface. A

console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump table).

System Action: Startup of the CICS-DB2 interface is terminated, and the interface is closed. The task is abnormally terminated with a CICS transaction

dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3T

Explanation: The transaction was unable to obtain a DB2 thread from the pool. Message DFHDB2011 is output to transient data. The transaction was

abended because the transaction tried using a DB2ENTRY but all threads were in use on the DB2ENTRY, and despite threadwait(pool) being specified, all

threads in the pool were also in use. The pool definition within the DB2CONN specifies threadwait(no).

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Determine whether more threads should be allocated to the DB2ENTRY or the pool, or whether the number of instances of this transaction

should be limited using TRANCLASS.

Module: DFHD2EX1

AD3U

Explanation: An error (INVALID or DISASTER response ) has occurred on a locate call to transaction manager (XM) domain to locate a transaction

definition. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2EX1

AD3W

Explanation: An unexpected response was received while attempting to write a record to a temporary storage queue during startup of the CICS-DB2

interface. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump

table).

System Action: Startup of the CICS-DB2 interface is terminated, and the interface is closed. The task is abnormally terminated with a CICS transaction

dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2STR

AD3X

Explanation: An unexpected response was received while attempting to write a record to a temporary storage queue during processing of a DSNC STRT

command. A console message is output, an exception trace written and, possibly, a system dump taken (depending on the options specified in the dump

table).

System Action: The DSNC STRT command fails. The task is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHD2CM1

AD3Z

Explanation: The CICS-DB2 thread TCB processing the DB2 request for this transaction has abended because the DB2 adapter is being shutdown.

System Action: The task is abnormally terminated.

User Response: If this abend should occur at CICS or DB2 shutdown then it can be ignored, because the DB2 adapter is abending the task as part of

shutdown processing, otherwise you will need assistance from IBM.

Module: DFHD2EX1

AEC1

Explanation: An attempt has been made to use the Command Level Interpreter (CECI) or the Enhanced Master Terminal (CEMT) or an RDO (CEDA,

CEDB, CEDC) transaction on a terminal that is not supported.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use a terminal that is supported by the Command Level Interpreter, Enhanced Master Terminal, or RDO transaction.

Modules: DFHECIP, DFHECSP, DFHEMTP, DFHESTP, DFHEOTP, DFHEDAP

AEC2

Explanation: An attempt has been made to use the Command Level Interpreter (CECI) or the Enhanced Master Terminal (CEMT) or an RDO (CEDA,

CEDB, CEDC) transaction on a display terminal of size less than 24 X 80.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use a display terminal that is supported by the Command Level Interpreter or Enhanced Master Terminal or RDO transaction.

Modules: DFHECIP, DFHECSP, DFHEMTP, DFHESTP, DFHEOTP, DFHEDAP

AEC3

Explanation: An unsuccessful attempt has been made to call VS COBOL II to initialize a thread (for the first VS COBOL II program in a CICS transaction).

System Action: The transaction is abnormally terminated. The program is disabled.

User Response: Check your library setup to ensure that all of the VS COBOL II interface modules are present.

Module: DFHAPLI

AEC4

Explanation: An unsuccessful attempt has been made to call VS COBOL II to initialize a run-unit (for any VS COBOL II program in a CICS transaction).

System Action: The transaction is abnormally terminated. The program is disabled.

User Response: Check your library setup to ensure that all of the VS COBOL II interface modules are present.

Module: DFHAPLI

AEC5

Explanation: An unexpected error has been encountered by C/370 during the THREAD INITIALIZATION phase while attempting to execute a C language

program.

System Action: The return code received from C/370 is placed into the field EIBRESP2; then the transaction is abnormally terminated. The program is

disabled.

User Response: Refer to the error message(s) provided by C/370 to determine the cause of the problem.

Module: DFHAPLI

AEC6

Explanation: An unexpected error has been encountered by C/370 during the RUNUNIT INITIALIZATION phase while attempting to execute a C language

program.

System Action: The return code received from C/370 is placed into the field EIBRESP2; then the transaction is abnormally terminated. The program is

disabled.

User Response: Refer to the error message(s) provided by C/370 to determine the cause of the problem.

Module: DFHAPLI

AEC7

Explanation: Language Environment has encountered an unexpected error during the THREAD INITIALIZATION phase while attempting to execute a

Language Environment enabled program. The return code received from Language Environment is placed into the field EIBRESP2.

System Action: Message DFHAP1200 is issued and the transaction is abnormally terminated. The program is disabled.

User Response: Refer to the error message or messages issued by Language Environment to determine the cause of the problem.

Module: DFHAPLI

AEC8

Explanation: Language Environment has encountered an unexpected error during the RUNUNIT INITIALIZATION phase while attempting to execute a

Language Environment enabled program.

System Action: The return code received from Language Environment is placed into the field EIBRESP2. Message DFHAP1200 is issued and the

transaction is abnormally terminated. The program is disabled.

User Response: Refer to the error message or messages issued by Language Environment to determine the cause of the problem.

Module: DFHAPLI

AEC9

Explanation: Language Environment has encountered an unexpected error during the RUNUNIT BEGIN INVOCATION phase while attempting to execute a

Language Environment enabled program.

System Action: The return code received from Language Environment is placed into the field EIBRESP2. Message DFHAP1200 is issued and the

transaction is abnormally terminated. The program is disabled.

User Response: Refer to the error message or messages issued by Language Environment to determine the cause of the problem.

Module: DFHAPLI

AEDA

Explanation: The CEDF transaction has been started with an invalid start code. This could be the result of attempting to start the execution diagnostic

facility (EDF) with EXEC CICS START(CEDF).

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why the start has failed.

Module: DFHEDFX

AEDB

Explanation: DFHEDFP has been passed an invalid EDFXA. This is an internal CICS 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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHEDFX

AEDC

Explanation: The program EDF has terminated because a GETMAIN request to the storage manager failed.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why the request has failed.

Module: DFHEDFX

AEDD

Explanation: CICS has attempted to attach the EDF task to display the user request but the attach has failed.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why the attach has failed.

Module: DFHEDFX

AEDE

Explanation: CICS has suspended the user task to allow the EDF task to complete but an error has occurred while performing the suspend.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why the suspend has failed.

Module: DFHEDFX

AEDF

Explanation: CICS has suspended the user task to allow the EDF task to complete. The user task has been purged while suspended, before control was

returned from EDF.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: The task was probably purged by the master terminal operator.

Investigate the reason why the task was purged. This may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

Module: DFHEDFX

AEDG

Explanation: CICS has suspended the user task to allow the EDF task to complete. The user task has gone away while suspended, before control was

returned from EDF.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine the reason why the task finished before being resumed.

Module: DFHEDFX

AEDH

Explanation: An error occurred when CICS called the Program Manager in order to discover details of the user program that has invoked EDF.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use the transaction dump to determine why the call has failed.

Module: DFHEDFX

AED1

Explanation: This abend is produced as a result of either:

An attempt to use the execution diagnostic facility (EDF) on an unsupported terminal,

Using the temporary storage browse transaction (CEBR) on an unsupported device, or

An attempt to initiate the temporary storage browse transaction (CEBR) with a non-terminal principal facility.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use a terminal or device that is properly supported.

Modules: DFHEDFP, DFHEDFBR

AED2

Explanation: The program EDF has terminated a task and placed this abend code in the terminated task's TCA. This occurs because execution of EDF is

about to be abnormally terminated. A probable reason for EDF being terminated is that a line, control unit, or a terminal has been put out of service.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Use a terminal that is supported as a display terminal by EDF. A CICS transaction dump of the task terminated with this abend code is

available for review.

Module: DFHEDFX

AED3

Explanation: The program EDF has terminated a task and placed this abend code in the terminated task's TCA. The termination occurs because execution

of EDF is about to be abnormally terminated.

One possible cause of an abend in EDF is incorrect data being sent to the terminal by the user task.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: A CICS transaction dump of the terminated task and also a similar dump for EDF, when its termination was abnormally terminated, are

available for review.

Module: DFHEDFX

AED4

Explanation: An internal logic error has been detected in EDF module DFHEDFP.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: This indicates a CICS logic error. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem

Determination Guide for guidance on how to proceed.

Module: DFHEDFP

AED5

Explanation: An internal logic error was been detected in EDF. Insufficient dynamic storage was pre-allocated.

System Action: EDF is terminated abnormally with dumps having dump codes CXSP, RMIN, PAGE, LDIN. The user task continues.

User Response: The problem may be avoided by less complex user interactions with EDF. If the problem persists, you may need further assistance. You

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

Module: DFHEDFD

AED6

Explanation: An internal logic error was detected in EDF.

System Action: EDF is terminated abnormally with dumps having dump codes CXSP, RMIN, PAGE, LDIN. The user task continues.

User Response: The problem may be avoided by less complex user interactions with EDF. If the problem persists, you may need further assistance. You

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

Module: DFHEDFU

AED7

Explanation: The installed definition of the transaction CEDF has a TWA size which is too small.

System Action: CICS abnormally terminates the transaction with a CICS transaction dump.

User Response: If you have an updated copy of the CEDF transaction installed, ensure that you have a TWA size at least as big as the one defined by the

IBM supplied definition. If you do not have an updated CEDF you may need further assistance to resolve this problem. You need further assistance from IBM

to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHEDFP

AED8

Explanation: A terminal control error has occurred in DFHEDFX.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHEDFX

AED9

Explanation: A temporary storage error has occurred in EDF. This could be caused by an input/output error on temporary storage or because temporary

storage data is full.

System Action: EDF is abnormally terminated with a CICS transaction dump.

User Response: Investigate the reason for the temporary storage request failure. Ensure that the definition of the temporary storage data set is correct.

See the CICS Problem Determination Guide for further guidance in dealing with temporary storage problems.

Module: DFHEDFD

AEIA

Note: The description of this abend also applies to AEID to AEI9, AEXC, AEXF, AEXG, AEXI to AEXL, AEXV to AEXX, AEX0 to AEX9, AEYA to AEYC,

AEYE to AEY3, AEY7, and AEZE to AEZQ.

Explanation: The EXEC interface program issues an abend when an exceptional condition has occurred but the command does not have the RESP option

(or NOHANDLE option), or the application program has not executed an EXEC CICS HANDLE CONDITION command for that condition. This will cause

DFHEIP to take the system action for the condition in question. In most cases, the system action will be to abend the transaction.

Problem Determination: The function code of the command that produced the exceptional response and the response code can be found in the EXEC

interface block (EIB). The EIB is part of a larger control block, used by DFHEIP, known as the EXEC interface storage block (EIS). The EIS is addressed by

the TCAEISA, which is the system part of the TCA + X'90' The EIB is pointed to from the EIS + X'8'.

The function code may be located at offset X'1B' in the EIB while the response codes may be one of the following at the given offsets:

EIBRCODE X'1D'

EIBRESP X'4C'

EIBRESP2 X'50'

The CICS Application Programming Reference gives translations of the encoded functions and their responses.

Analysis: Because these abend codes are directly related to exceptional conditions that can be specified in HANDLE CONDITION commands, the

application programmer should decide whether the condition is one that should be handled by the application (for example ENDFILE), or one that requires

modifications to the application or CICS tables.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Change the application program either to prevent the condition recurring, to check it by using the RESP option, or to handle the condition

when it does occur (by using the EXEC CICS HANDLE CONDITION command). If necessary, use the contents of the EIBRESP2 field or the EIBRCODE in

the EIB to assist in determining the cause of the exceptional condition.

Module: DFHEIP

AEID

Explanation: EOF condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIE

Explanation: EODS condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIG

Explanation: INBFMH condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIH

Explanation: ENDINPT condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEII

Explanation: NONVAL condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIJ

Explanation: NOSTART condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIK

Explanation: TERMIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIL

Explanation: FILENOTFOUND condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIM

Explanation: NOTFND condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIN

Explanation: DUPREC condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIO

Explanation: DUPKEY condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIP

Explanation: INVREQ condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIQ

Explanation: IOERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIR

Explanation: NOSPACE condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIS

Explanation: NOTOPEN condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIT

Explanation: ENDFILE condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIU

Explanation: ILLOGIC condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIV

Explanation: LENGERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIW

Explanation: QZERO condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEIZ

Explanation: ITEMERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI0

Explanation: PGMIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI1

Explanation: TRANSIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI2

Explanation: ENDDATA condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI3

Explanation: INVTSREQ condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI4

Explanation: EXPIRED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI8

Explanation: TSIOERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEI9

Explanation: MAPFAIL condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AELA

Explanation: The executing function has been purged before control could be returned.

System Action: The transaction is marked to be abnormally terminated with abend code AELA.

User Response: Investigate the reason the task was purged. It was purged either by the master terminal operator, or as a result of a deadlock timeout.

If the task was purged by the master terminal operator, 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 then the number of tasks in the system should be reduced to avoid

short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Module: DFHETL

AELB

Explanation: The executing function has been purged before control could be returned.

System Action: The transaction is marked to be abnormally terminated with abend code AELB.

User Response: Investigate the reason the task was purged. It was purged either by the master terminal operator, or as a result of a deadlock timeout.

If the task was purged by the master terminal operator, 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 then the number of tasks in the system should be reduced to avoid

short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Module: DFHEGL

AEMA

Explanation: An error (INVALID or DISASTER response) has occurred on a call to the application (AP) domain when a request for set user exit active could

not be serviced.

System Action: The task is abnormally terminated. The domain that detected the original error issues a console message and might provide an exception

trace, and depending on the options specified in the dump table, a system dump.

User Response: See the associated console message for further guidance.

Module: DFHUEM

AEMB

Explanation: An error (INVALID or DISASTER response) has occurred on a call to the loader (LD) domain. The domain that detected the original error will

have provided an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

System Action: The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User Response: See the related message from the domain that detected the original error.

Module: DFHUEM

AEMP

Explanation: The task was purged before a set active request to the application (AP) domain was able to complete successfully. The domain that first

detected the purged condition may provide an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate why the task was purged. This is 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.

Module: DFHUEM

AEMQ

Explanation: The task was purged before an IDENTIFY_PROGRAM request to the loader (LD) domain was able to complete successfully. The domain that

first detected the purged condition provides an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump (depending on the options in the dump table).

User Response: Investigate why the task was purged. This is 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

Module: DFHUEM

AETA

Explanation: A CICS transaction has issued a non-CICS command via an application "stub" (an expansion of a DFHRMCAL macro). Program DFHERM has

determined that the exit has been disabled since the previous DFHRMCAL request was issued from the transaction.

System Action: The task is abnormally terminated with a transaction dump

User Response: Notify your system programmer.

Module: DFHERM

AETC

Explanation: A CICS transaction has issued a non-CICS command via an application "stub" (an expansion of a DFHRMCAL macro). However, the

task-related user exit (TRUE) is not known to program manager.

System Action: The task is abnormally terminated with a transaction dump

User Response: Ensure that the TRUE as identified to the DFHRMCAL macro has been correctly defined to CICS.

Module: DFHERM

AETF

Explanation: The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected

the purged condition will have provided an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate why the task was purged. This is 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.

Module: DFHERM

AETG

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 will have provided 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.

Module: DFHERM

AETH

Explanation: The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected

the purged condition will have provided an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate why the task was purged. This is 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.

Module: DFHERM

AETI

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 will have provided 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.

Module: DFHERM

AETJ

Explanation: An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an ADD_LINK call to the recovery manager (RM)

domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the

options in the dump table).

For all errors, DFHERM provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHERM

AETK

Explanation: An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an SET_LINK call to the recovery manager (RM)

domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the

options in the dump table).

For all errors, DFHERM provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHERM

AETL

Explanation: An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an SET_UOW call to the recovery manager (RM)

domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the

options in the dump table).

For all errors, DFHERM provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHERM

AETM

Explanation: An error (EXCEPTION, DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INQUIRE_TRANSACTION call to the

transaction manager (XM) domain. For errors other than EXCEPTION, the XM domain provides an exception trace, a console message, and possibly a

system dump (depending on the options in the dump table).

For all errors, DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AETN

Explanation: An EXCEPTION response with an unexpected reason occurred on an INITITIATE_RECOVERY call to recovery manager (RM) domain.

DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AETO

Explanation: An error (DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INITIATE_RECOVERY call to the recovery manager (RM)

domain. The RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

DFHRMSY also provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AETP

Explanation: An error (EXCEPTION, DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an TERMINATE_RECOVERY call to recovery

manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump

(depending on the options in the dump table).

For all errors, DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AETQ

Explanation: An EXCEPTION response with an unexpected reason occurred on an INQUIRE_UOW call to the recovery manager (RM) domain. DFHRMSY

provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AETR

Explanation: An error (DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INQUIRE_UOW call to the recovery manager (RM) domain.

The RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

DFHRMSY also provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AETS

Explanation: An error (EXCEPTION, DISASTER, INVALID, KERNERROR, or PURGED) has occurred on an INQUIRE_STARTUP call to recovery manager

(RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending

on the options in the dump table).

For all errors, DFHRMSY provides an exception trace, console message DFHAP0002, and possibly a system dump (depending on the options in the dump

table).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHRMSY

AEXC

Explanation: RESIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXF

Explanation: ESCERROR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXG

Explanation: UOWLNOTFOUND condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXI

Explanation: TERMERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXJ

Explanation: ROLLEDBACK condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXK

Explanation: END condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXL

Explanation: DISABLED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXU

Explanation: During execution of an EXEC CICS command, a NOTPOSS condition has been raised on encountering an invalid parameter. This is probably

caused by a previous storage overlay.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Refer to abend AEIA for an explanation of how to determine the function code of the CICS command that caused the abend.

It is not possible to set an EXEC CICS HANDLE CONDITION for NOTPOSS.

The system programmer should investigate the cause of the storage overlay.

Modules: DFHEIDTI, DFHEIQDS, DFHEIQSA, DFHEIQSC, DFHEIQSM, DFHEIQSP DFHEIQST, DFHEIQSX

AEXV

Explanation: VOLIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXW

Explanation: SUPPRESSED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXX

Explanation: TASKIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEXY

Explanation: The executing transaction has been purged before control could be returned.

This can arise when the transaction is purged while

A CICS command was being processed

The transaction was waiting to be dispatched

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Contact your system programmer to determine why the transaction has been purged.

Modules: DFHACP, DFHBEP, DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHBSTS, DFHBSTZO, DFHD2CC, DFHD2EX1, DFHD2EX2,

DFHD2STR, DFHEDCP, DFHEDFP, DFHEDI, DFHEEI, DFHEGL, DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHEIIC, DFHEIP, DFHEIPA,

DFHEIPRT, DFHEIPSE, DFHEIPSH, DFHEIQDE, DFHEIQDN, DFHEIQDS, DFHEIQDU, DFHEIQD2, DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQPF,

DFHEIQPN, DFHEIQRQ, DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL, DFHEIQSM, DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX,

DFHEIQTM, DFHEIQTR, DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIUOW, DFHEKC, DFHEMS, DFHEOP, DFHEPC, DFHERM, DFHESC, DFHESE,

DFHESN, DFHETC, DFHETL, DFHETRX, DFHPCPC2, DFHTACP, DFHTFP, DFHTIEM, DFHUEM, DFHWBTC, DFHXMBR, DFHXTP, DFHZATS, DFHZNCA,

DFHZNCE, DFHZTSP, DFHZXQO, DFHZXST

AEXZ

Explanation: A command has failed due to a serious failure in a CICS component (resource manager).

System Action: The transaction is abnormally terminated with abend code AEXZ. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User Response: Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no

transaction dump is available, contact your system programmer.

Modules: DFHACP, DFHBEP, DFHBREX, DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, DFHBSTS, DFHBSTZO, DFHCDKRN, DFHEDCP, DFHEDFP,

DFHEDI, DFHEEI, DFHEGL, DFHEIACQ, DFHEICRE, DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS, DFHEIIC, DFHEIP, DFHEIPA, DFHEIPRT,

DFHEIPSE, DFHEIPSH, DFHEIQDE, DFHEIQDN, DFHEIQDS, DFHEIQDU, DFHEIQD2, DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQPF, DFHEIQPN,

DFHEIQRQ, DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSL, DFHEIQSM, DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX, DFHEIQSY,

DFHEIQTM, DFHEIQTR, DFHEIQTS, DFHEIQUE, DFHEIQVT, DFHEIUOW, DFHEKC, DFHEMS, DFHEOP, DFHEPC, DFHESC, DFHESE, DFHESN,

DFHETC, DFHETL, DFHETRX, DFHFCFL, DFHPCPC2, DFHSJIN, DFHTACP, DFHTFP, DFHTIEM, DFHUEH, DFHUEM, DFHWBTC, DFHXMBR, DFHXTP,

DFHZATS, DFHZNCA, DFHZNCE, DFHZTSP, DFHZXQO, DFHZXST

AEX0

Explanation: TCIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX1

Explanation: DSNNOTFOUND condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX2

Explanation: LOADING condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX3

Explanation: MODELIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX4

Explanation: UOWNOTFOUND condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX5

Explanation: PARTNERIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX6

Explanation: PROFILEIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX7

Explanation: NETNAMEIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX8

Explanation: LOCKED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEX9

Explanation: RECORDBUSY condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYA

Explanation: INVERRTERM condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYB

Explanation: INVMPSZ condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYC

Explanation: IGREQID condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYD

Explanation: A transaction has requested that CICS access a storage area that the transaction itself could not access. This occurred when an invalid

storage area was passed to CICS as an output parameter on an EXEC CICS command.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Examine the trace to find the exception trace entry created by DFHEISR and then identify the parameter in error. If the abend is handled,

EXEC CICS ASSIGN ASRASTG, ASRAKEY, ASRASPC, and ASRAREGS give additional information about the abend. At the time of the abend, register 2

points to the storage area at fault.

Change one or more of the following:

Correct the code in error in the transaction issuing the EXEC CICS command in order to supply a valid storage area.

If storage protection is active, change the EXECKEY on the CEDA definition for the program that issued the EXEC CICS command from USER to CICS.

If storage protection is active, change the TASKDATAKEY attributes on the transaction definition from CICS to USER.

If transaction isolation is active, change the ISOLATE attribute on the transaction definition from YES to NO.

Module: DFHSRP

AEYE

Explanation: INVLDC condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYG

Explanation: JIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYH

Explanation: QIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYJ

Explanation: DSSTAT condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYK

Explanation: SELNERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYL

Explanation: FUNCERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYM

Explanation: UNEXPIN condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYN

Explanation: NOPASSBKRD condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYO

Explanation: NOPASSBKWR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYP

Explanation: SEGIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYQ

Explanation: SYSIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYR

Explanation: ISCINVREQ condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYT

Explanation: ENVDEFERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYU

Explanation: IGREQCD condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYV

Explanation: SESSIONERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYX

Explanation: USERIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYY

Explanation: NOTALLOC condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEYZ

Explanation: CBIDERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEY0

Explanation: INVEXITREQ condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEY1

Explanation: INVPARTNSET condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEY2

Explanation: INVPARTN condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEY3

Explanation: PARTNFAIL condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEY6

Explanation: Internal logic error in DFHUEM. This arises when using EXITALL to DISABLE an exit program from all exit points for which it has been

enabled. The entire user exit table has been scanned and all associations of the program have been found. But the activation count for the program in its exit

program block indicates there should be more associations (for example, the activation count has not been reduced to zero). The user exit table and

associated control blocks (EPBs and EPLs) are out of step and have probably been corrupted.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHUEM

AEY7

Explanation: NOTAUTH condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEY8

Explanation: No DSA was found on the chain while trying to free dynamic storage for an assembler language program using an EXEC CICS command.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Ensure that the DFHEIENT, DFHEISTG, and DFHEIEND macro invocations are correctly positioned and retry. If the error persists, you will

need further assistance. You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on

how to proceed.

Module: DFHEIP

AEY9

Explanation: One of the following:

An EXEC CICS command has been issued that is not supported by the EXEC interface program DFHEIP.

A transaction has issued an EXEC CICS command which is supported in principle by the EXEC interface program DFHEIP, but for which the prerequisite

function has not been included in the current CICS start-up.

A non-CICS command has been issued via an application "stub" (expansion of a DFHRMCAL macro), and the program DFHERM has detected that the

necessary non-CICS support is not available.

An attempt has been made to use remote resources, but the local SYSID has been specified in an EXEC CICS command, or vice versa.

An attempt has been made to use remote resources, but ISC is not supported.

An EXEC CICS command contains an invalid AID or CONDITION identifier. This indicates that the EXEC CICS command has become corrupted.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check that the sysid specified and the resource names were correct. If not, notify the system programmer. Either the command (or an

application stub) has become corrupted, or the unavailable function needs to be generated (CICS command), ENABLEd (non-CICS command), or

exceptionally the non-CICS support has suffered damage and is attempting to withdraw itself from the CICS system.

Modules: DFHEIP, DFHEEI

AEZA

Explanation: A transaction has been defined with a TASKDATALOC(ANY), but the programs within the transaction are running amode 24. The exec

interface program is therefore is unable to access the TCA for the application. Furthermore, any reference to the EIB would cause the transaction to fail with

an OC4 protection exception.

System Action: The transaction is abnormally terminated.

Module: DFHEIP

AEZB

Explanation: A transaction has been defined with a TASKDATALOC(ANY), and the application is attempting to call a task related user exit. However the

task related user exit has been linkedited AMODE 24 and enabled with the LINKEDITMODE option, thereby directing CICS to invoke it in AMODE 24. An

AMODE 24 task related user exit cannot run when the calling application is running with TASKDATALOC(ANY), as this would cause a protection exception,

or a storage overwrite.

System Action: The transaction is abnormally terminated.

User Response: Either redefine and install a new definition for the transaction with TASKDATALOC(BELOW), or modify the task related user exit so that it

is invoked in AMODE 31.

Module: DFHERM

AEZC

Explanation: A transaction has been defined with a TASKDATALOC(ANY), but a program within the transaction is defined to run AMODE 24. CICS cannot

invoke the AMODE 24 program when the transaction is running with TASKDATALOC(ANY), as this would cause a protection exception, or a storage

overwrite.

System Action: The transaction is abnormally terminated.

User Response: Either redefine and install a new definition for the transaction with TASKDATALOC(BELOW), or relink the program as AMODE 31.

Module: DFHAPLI

AEZD

Explanation: An attempt has been made to run a program defined as EXECKEY(USER) as part of a transaction defined as TASKDATAKEY(CICS). These

attributes are incompatible and the transaction is abended. This incompatibility could occur as a result of the program definition being autoinstalled. See the

CICS Customization Guide and the CICS Resource Definition Guide for more information about program autoinstall.

System Action: The transaction is abnormally terminated.

User Response: Redefine and install a new definition either for the transaction with TASKDATAKEY(USER), or for the program with EXECKEY(CICS).

If this abend occurs when running a CICS transaction, a possible cause is that you are not using the CICS-supplied definition for the program. If you are using

your own copies of CICS-supplied program definitions, they must be defined as EXECKEY(CICS).

Module: DFHAPLI

AEZE

Explanation: CHANGED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZF

Explanation: PROCESSBUSY condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZG

Explanation: ACTIVITYBUSY condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZH

Explanation: PROCESSERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZI

Explanation: ACTIVITYERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZJ

Explanation: CONTAINERERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZK

Explanation: EVENTERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZL

Explanation: TOKENERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZM

Explanation: NOTFINISHED condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZN

Explanation: POOLERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZO

Explanation: TIMERERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZP

Explanation: SYMBOLERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AEZQ

Explanation: TEMPLATERR condition not handled.

This is one of a number of abends issued by the EXEC interface program. Because of their similar characteristics these abends are described as a group.

See the description of abend AEIA for further details.

Module: DFHEIP

AFCB

Explanation: Module DFHEIFC issued a resource level security check (RSLC) request to module DFHXSRC and received a response other than OK or

EXCEPTION.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Examine the trace to find the exception trace entry created by DFHXSRC at the time of the error. Use this trace entry to determine the

cause of the return code from DFHXSRC.

Module(s): DFHEIFC

AFCC

Explanation: An internal logic error was detected when calling the file control request processing module DFHFCFR. Either DFHFCFR returned an INVALID

response to its caller indicating an error in the caller's parameter list, or DFHFCFR passed back a return code that was not recognized by its caller.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Modules: DFHEIFC, DFHDMPCA

AFCE

Explanation: A GETMAIN for FFLE storage has failed.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Retry the failed transaction.

Module: DFHEIFC

AFCF

Explanation: A deadlock has been detected between two or more tasks issuing file control requests.

System Action: The task that would have entered deadlock is abended with a CICS transaction dump.

User Response: Examine this transaction and other transactions in the system that update the same files to find the cause of the deadlock, then correct

the error.

When transactions update several files within the same unit of work, all transactions should update these files in the same order. A transaction that abends

AFCF may be retried by specifying RESTART(YES) in the transaction definition and by coding a suitable DFHREST program.

Modules: DFHEIFC, DFHDMPCA

AFCG

Explanation: A transaction has issued a sequence of file control requests that would cause the file to deadlock itself. This response arises for different

reasons depending upon the file type.

If the file is being accessed in non-RLS mode, the response is caused by the transaction making conflicting requests against the same CI. For example, if

the file is being accessed using LSR, a self deadlock will arise when an attempt is made to read a record that is in the same CI as a record that is the

subject of a READ UPDATE or WRITE MASSINSERT request issued by the same transaction.

If the file is accessed in RLS mode there is no CI locking, but self deadlock responses can still arise. They are caused by sequences of requests that are

either logically meaningless or which cannot be performed by VSAM RLS.

With VSAM RLS the most likely causes of this abend are as follows:

Two successive READ UPDATE requests against the same record by the same transaction without an intervening REWRITE, DELETE or UNLOCK

command.

This is an incorrect use of file control requests.

A transaction has created a record by WRITE MASSINSERT and then, without terminating the WRITE MASSINSERT sequence by issuing an UNLOCK

request, the same transaction has attempted to modify the same record by issuing a READ UPDATE or DELETE request.

This sequence of requests fails if VSAM has not written the record out to disk. The only way to guarantee that the record has been written to disk is to

issue the UNLOCK request.

A transaction has updated or deleted a record using a browse for update sequence and then, without terminating the browse for update sequence by

issuing an ENDBR request, the same transaction has attempted to modify the same record by issuing a separate READ UPDATE or DELETE or WRITE

request.

This sequence of requests fails if VSAM has not written the record out to disk. The only way to guarantee that the record has been written to disk is to

issue the ENDBR request.

If the file is used to access a coupling facility data table, then self deadlock responses are caused by sequences of requests that are either logically

meaningless or which cannot be performed by coupling facility data tables support.

For coupling facility data tables, the most likely cause of this abend is as follows:

Two successive READ UPDATE requests have been issued against the same record by the same transaction without an intervening REWRITE, DELETE

or UNLOCK command.

This is an incorrect use of file control requests.

System Action: The task that would have entered deadlock is abended with a CICS transaction dump.

User Response: Examine the previous requests made by this transaction against this file to identify the cause of the deadlock, then correct the error. In

some cases (particularly when the file is being accessed in RLS mode or is using a coupling facility data table) this abend may indicate a programming error

in the program that issued the file control requests.

Modules: DFHEIFC, DFHDMPCA

AFCH

Explanation: The transaction has issued a request for a remote shared data table for which it has an active browse, but in the meantime the table has been

disabled or closed by the owning CICS system, or the owning CICS system has failed.

System Action: The requesting transaction abends with a transaction dump.

CICS continues normally.

User Response: In the application owning region, take whatever action normally follows the issue of a FORCE request in, or the failure of, the file owning

CICS system.

See the CICS Shared Data Tables Guide for further guidance. guidance.

Module: DFHEIFC

AFCJ

Explanation: DFHFCU issued a call to DFHFCFS to open a file. A purged error was returned from DFHFCFS because the task has been waiting for a

resource longer than the DTIMEOUT interval specified for the CSFU transaction.

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

User Response: Examine the dump to determine the cause of the error. A system dump can be produced by adding the appropriate dump table entry using

the CEMT SET TRDUMPCODE command.

Module: DFHFCU

AFCK

Explanation: The transaction issued a file update request (READ UPDATE, WRITE or DELETE) against an RLS mode data set for which a DFSMSdss

non-BWO backup was in progress.

System Action: The transaction is abnormally terminated with a CICS transaction dump. CICS processing continues.

User Response: All new file update requests are prohibited when a non-BWO backup is in progress for an RLS mode data set. This restriction is

automatically lifted when the backup completes. (A non-BWO backup is any type of backup operation other than a Backup While Open backup.) When the

backup has completed, retry the transaction.

Modules: DFHDMPCA, DFHEIFC

AFCL

Explanation: During the loading of a Shared Data Table by the CFTL transaction, a call to the CICS Transaction Manager has returned a response (such as

DISASTER) after which normal processing could not continue.

System Action: Message DFHFC0949 is issued. Loading of the data table is terminated and CFTL abends.

User Response: Refer to the description of the message for further information and guidance.

Module: DFHDTLX

AFCM

Explanation: During the loading of a data table by the CFTL transaction, an abend was detected, or a domain call returned a response (such as

DISASTER) after which normal processing could not continue.

System Action: A message is issued (one of DFHFC0945, DFHFC0946, or DFHFC0947). Loading of the data table is terminated and CFTL abends.

User Response: If this abend is produced as a result of an abend during loading, message DFHFC0945 is issued. If it is a result of a domain call failure,

depending on which domain the failure was returned by, one of the messages DFHFC0946 or DFHFC0947 is issued. Refer to the description of the message

for further information and guidance.

Module: DFHDTLX

AFCN

Explanation: The transaction issued a file request that caused file control to attempt to create a journal record but the record was too large for the journal

buffer to accommodate. This indicates that a journal referenced in the file definition is using an MVS logstream, which in turn, is using a coupling facility

structure which has been defined with a MAXBUFSIZE parameter less than the recommended 64000.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Redefine the coupling facility structure that the logstream is using with a MAXBUFSIZE parameter of 64000. The journal in error can be the

forward recovery log or the journal used for auto-archiving. If the module that detected the error is DFHDMPCA, the error is associated with a journal

referenced in the definition of the CSD (DFHCSD).

Modules: DFHDMPCA, DFHEIFC

AFCO

Explanation: An attempt was made to attach a transaction specifying DFHDTLX as the program to be given control, but the transaction was not internally

attached by CICS.

DFHDTLX is for use by CICS system transaction CFTL. This loads a Shared Data Table.

System Action: The transaction is abnormally terminated. CICS processing continues.

User Response: Establish why an attempt was made to attach CFTL illegally, or why a transaction definition specified DFHDTLX as the program to be given

control.

Module: DFHDTLX

AFCR

Explanation: The program issued a file control request against a file opened in RLS mode. While executing this request, CICS detected that the

SMSVSAM server address space had failed.

System Action: The task is abnormally terminated with a CICS transaction dump.

CICS disables all further RLS accesses and initiates error recovery.

User Response: Retry the transaction when the server is available again

If the SMSVSAM server fails, it should normally automatically restart itself as quickly as possible. If this does not happen, consult the VSAM documentation

which provides further guidance on debugging problems in the SMSVSAM server.

Modules: DFHEIFC, DFHDMPCA

AFCS

Explanation: The program issued a file control request against a file opened in RLS mode. VSAM was unable to perform this request because the

SMSVSAM server address space was inactive.

However, if an offsite restart is being performed (that is, OFFSITE=YES was specified as a system initialization override), this transaction abend is also

issued even if the SMSVSAM server address space is active. This is because RLS access is not allowed during an offsite restart for any RLS file control

requests other than those issued by transactions which have been attached by CICS to perform RLS recovery work.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Retry the transaction when the server is available again.

If the SMSVSAM server fails, it should normally automatically restart itself as quickly as possible. If this does not happen, consult the VSAM documentation

which provides further guidance on debugging problems in the SMSVSAM server.

If an offsite restart is being performed, retry the transaction after RLS recovery has been completed when RLS access by user transactions is allowed again.

Modules: DFHEIFC, DFHDMPCA

AFCT

Explanation: The program has made a file control request against a file opened in RLS mode. The SMSVSAM server has been recycled since an earlier

RLS request from the same unit of work. The same unit of work cannot issue requests against two different instances of the SMSVSAM server. Note that this

abend will occur even if the earlier request was not successful.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Resubmit the transaction.

Modules: DFHEIFC, DFHDMPCA

AFCU

Explanation: A program made a file control request against a file that is being accessed in VSAM RLS mode. The underlying data set is in lost locks state.

File control requests are not allowed against a data set that is in lost locks state.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Recovery from lost locks is normally automatic. See the CICS Recovery and Restart Guide for a full explanation of lost locks recovery. You

will not be able to issue any file control requests against this data set until all systems that owned locks at the time of the lock structure failure have

completed their lost locks recovery.

See the CICS Recovery and Restart Guide for guidance on how to determine which CICS systems still have lost locks recovery pending, for information on

commands that allow you to find the work that these systems have outstanding, and on commands that allow you to force a system to immediately complete

lost locks recovery. The commands that force immediate completion of lost locks recovery should only be used as a last resort as they may cause loss of

data integrity. It is better to allow the automatic recovery procedures to complete normally.

Modules: DFHEIFC, DFHDMPCA

AFCV

Explanation: A request made against a file opened in RLS mode was unable to acquire a record lock. It waited for the lock, but the wait time exceeded the

maximum wait time applicable to that request.

System Action: The task is abnormally terminated with a CICS transaction dump.

CICS prints message DFHFC0164 and message DFHFC0165 which identify the transaction or transactions that were immediately in front of this transaction

in the queue for the lock. Normally this transaction or these transactions are the owners of the lock, although this is not the case if a chain of requests for the

record has built up.

User Response: Retry the transaction.

If the problem recurs, see messages DFHFC0164 and DFHFC0165 to determine the transaction that is holding the lock. In most cases the problem lies with

the lock owner rather than the transaction that has failed.

Examples of causes of timeouts are as follows:

The transaction that holds the lock has a design error. For example:

- A conversational transaction updates a recoverable record and then issues a terminal control read. It does not issue syncpoint (and therefore does not

release the lock) until the end user has responded to the terminal control read. It may therefore hold the lock for a considerable period.

- A transaction updates very many records in recoverable files before issuing syncpoint. You are recommended to keep the number of updates made

within a unit of work small and to issue frequent syncpoints to ensure that locks are released regularly.

The system in which the lock holder is running is experiencing severe performance degradation. Investigate the reason for the performance degradation.

There is a deadlock between RLS and another resource manager. For example one transaction may be holding an RLS lock and waiting for a lock on a

transient data queue. The transaction that times out may hold the lock on the transient data queue and be waiting for the RLS lock. RLS can detect

deadlocks only when all the locks involved in the deadlock are RLS locks. A deadlock such as this can appear to RLS to be a long wait for a lock and is

reported as a time out. Examine the design of the transactions to determine whether resource manager deadlocks can occur.

It may be possible for RLS deadlocks to be reported as RLS timeouts if VSAM does not perform deadlock detection until after the time out value for the

request occurred. For example, assume that DEADLOCK_TIMEOUT in specified as (15,4) in SYS1.PARMLIB. This means that VSAM does not attempt

to detect cross-MVS deadlocks until 4 periods of 15 (that is, 60) seconds have elapsed. If DTIMOUT was not active for the transaction and the SIT

specified FTIMEOUT=30, the RLS request times out after 30 seconds, before VSAM has attempted to detect cross-MVS deadlocks. Adjust FTIMEOUT,

DTIMOUT, and DEADLOCK_DETECTION to avoid such effects.

Modules: DFHEIFC, DFHDMPCA

AFCW

Explanation: The program issued a file control request against a file opened in RLS mode. VSAM RLS detected that this request would cause a deadlock.

This transaction is abended in order to break the deadlock chain.

System Action: The task is abnormally terminated with a CICS transaction dump.

CICS prints message DFHFC0166 and message DFHFC0167 which identify the other transactions in the deadlock chain.

User Response: Retry the transaction.

Examine the logic of all the programs involved in the deadlock chain to determine whether they could be improved to avoid possible sources of deadlock. See

the CICS Application Programming Guide for guidance on how to write programs that avoid deadlocks.

Modules: DFHEIFC, DFHDMPCA

AFCY

Explanation: The transaction issued a file request resulting in a call to the main file control program (DFHFCFR). During the processing of the request the

transaction was purged (that is, was the subject of an explicit PURGE or FORCEPURGE request, was timed out, or was selected by CICS for termination in

an attempt to alleviate an SOS condition). A "purged" response was returned from DFHFCFR to its caller.

System Action: The task is abnormally terminated with a CICS transaction dump.

Exception trace entries are made between the point at which the purge is detected and the issuing of the abend.

User Response: In some instances, for example if the transaction was explicitly purged, no further action is necessary.

Otherwise examine the exception trace and the transaction dump to identify the point at which the purge occurred.

Modules: DFHDMPCA, DFHEIFC

AFCZ

Explanation: The transaction issued a file request resulting in a call to the main file control program (DFHFCFR). A "disastrous error" response was

returned from DFHFCFR to its caller.

System Action: At the time the error is detected, CICS writes a message to the console, records an exception trace entry, and takes a system dump. The

trace and dump identify the point of error.

Subsequently, the task is abnormally terminated with a CICS transaction dump.

User Response: The system programmer should use the trace and dumps to determine what the error is, and why it has occurred.

Modules: DFHDMPCA, DFHEIFC

AFC0

Explanation: An attempt has been made to update a file after file control restart failed.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Determine the cause of the failure in file control restart. Restart CICS.

Modules: DFHEIFC, DFHDMPCA

AFC2

Explanation: DFHFCU issued a call to DFHFCFS to open a file. A disastrous error was returned from DFHFCFS.

System Action: The task is abnormally terminated with a CICS transaction dump.

At the time the disastrous error is detected, CICS writes a message to the console, records an exception trace entry and takes a system dump.

CICS processing continues.

User Response: The system programmer should examine the trace, the system dump and any related CICS messages to identify the cause of the error.

Module: DFHFCU

AFC7

Explanation: The CICS definition file (CSD) manager (DFHDMPCA) issued a request to DFHFCFS to enable, open or close the DFHCSD file. A "disastrous

error" response was returned from DFHFCFS to DFHDMPCA.

System Action: The task is abnormally terminated with a CICS transaction dump.

At the time the disastrous error is detected, CICS writes a message to the console, records an exception trace entry and takes a system dump.

CICS processing continues.

User Response: The system programmer should examine the trace, the system dump and any related CICS messages to identify the cause of the error.

Module: DFHDMPCA

AFDA

Explanation: An attempt was made to attach a transaction specifying DFHFCQT as the program to be given control, but the transaction was not internally

attached by CICS.

DFHFCQT is for use by CICS system transactions CFQS and CFQR. These provide support for VSAM RLS data set quiesce and unquiesce operations,

DFSMSdss BWO and non-BWO backups, and certain other data set related operations.

System Action: The transaction is abnormally terminated. CICS processing continues.

User Response: Establish why an attempt was made to illegally attach CFQS or CFQR, or why a transaction definition specified DFHFCQT as the program

to be given control.

Module: DFHFCQT

AFDB

Explanation: An attempt was made by CICS to internally attach a transaction specifying DFHFCQT as the program to be given control, and the transaction

id was other than CFQS or CFQR.

DFHFCQT is for use by CICS system transactions CFQS and CFQR. These provide support for VSAM RLS data set quiesce and unquiesce operations,

DFSMSdss BWO and non-BWO backups, and certain other data set related operations.

System Action: The transaction is abnormally terminated with a CICS transaction dump. CICS processing continues but it is probable that VSAM RLS data

set quiesce support has been lost.

User Response: Restart CICS. If the problem reoccurs, a more severe error is indicated. In this case, you will need assistance from IBM. You need further

assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHFCQT

AFDC

Explanation: CICS system transaction CFQS has failed due to a serious error. An attempt will be made to reattach the transaction. CICS messages should

indicate the cause of the error.

CFQS provides support for the initiation of VSAM RLS data set quiesce and unquiesce operations.

System Action: CFQS is abnormally terminated with a CICS transaction dump. CFQS is reattached and CICS processing continues.

User Response: Check Transient Data Queue CSFL for message DFHFC6028, indicating that the reattach of CFQS was successful. If the reattach fails,

VSAM RLS data set quiesce initiation support is lost. If this support is required, CICS must be restarted.

If it is not possible to restore VSAM RLS quiesce initiation support, a more severe error is indicated. In this case, you will need assistance from IBM. You

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

Module: DFHFCQT

AFDD

Explanation: CICS system transaction CFQR has failed due to a serious error. An attempt will be made to reattach the transaction. CICS messages should

indicate the cause of the error.

CFQR provides support for VSAM RLS data set quiesce and unquiesce operations, DFSMSdss BWO and non-BWO backups, and certain other data set

related operations.

System Action: CFQR is abnormally terminated with a CICS transaction dump. CFQR is reattached and CICS processing continues.

User Response: Check Transient Data Queue CSFL for message DFHFC6028, indicating that the reattach of CFQR was successful. If the reattach fails,

VSAM RLS data set quiesce support is lost. If this happens, CICS must be restarted.

If it is not possible to restore VSAM RLS quiesce support, a more severe error is indicated. In this case, you will need assistance from IBM. You need further

assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHFCQT

AFDE

Explanation: An attempt was made to attach a transaction specifying DFHFCRD as the program to be given control, but the transaction was not internally

attached by CICS.

DFHFCRD is for use by CICS system transaction CSFR. This provides support for error recovery after a failure of the SMSVSAM server.

System Action: The transaction is abnormally terminated. CICS processing continues.

User Response: Establish why an attempt was made to illegally attach CSFR, or why a transaction definition specified DFHFCRD as the program to be

given control.

Module: DFHFCRD

AFDF

Explanation: An attempt was made to attach a transaction specifying DFHFCOR as the program to be given control, but the transaction was not internally

attached by CICS.

DFHFCOR is for use by CICS system transaction CFOR. This provides part of the RLS offsite recovery support.

System Action: The transaction is abnormally terminated. CICS processing continues.

User Response: Establish why an attempt was made to illegally attach CFOR, or why a transaction definition specified DFHFCOR as the program to be

given control.

Module: DFHFCOR

AFDG

Explanation: CICS system transaction CFOR has failed due to a serious error. CICS messages should indicate the cause of the error.

DFHFCOR provides part of the RLS offsite recovery support.

This abend indicates that this CICS system has completed its RLS offsite recovery, but an error occurred either in attempting to issue message

DFHFC0575D which reports this fact, or in attempting to process the reply to message DFHFC0575D.

System Action: CFOR is abnormally terminated with a CICS transaction dump. CICS processing continues.

User Response: If you are using an automated procedure to check for and reply to message DFHFC0575D, then you should shut this CICS down and

restart it specifying OFFSITE=YES again. If you are using manual procedures to check for completion of all RLS offsite recovery and to reply to message

DFHFC0575D then you can "tick" this CICS off the list of systems which have completed their recovery, but you must ensure that it is not restarted with

OFFSITE=NO until all other CICS systems have completed their RLS offsite recovery. Also note that until the system is restarted, RLS access will not be

allowed by this system.

Module: DFHFCOR

AFDH

Explanation: VSAM has returned a response indicating that the RLS lock structure in the coupling facility is full. VSAM RLS is unable to create any new

locks.

This abend code is usually issued from various CICS systems residing within the same sysplex.

System Action: The transaction which issued the VSAM RLS request is abnormally terminated with a CICS transaction dump. CICS processing continues.

User Response: Allocate a larger VSAM RLS lock structure and rebuild the RLS structure into the new larger structure. See OS/390 MVS Setting up a

Sysplex, (GC28-1779) and DFSMS/MVS DFSMSdfp Storage Administration Reference, (SC26-4920) for further details on creating RLS lock structures and

rebuilding lock structures.

Modules: DFHEIFC, DFHDMPCA

AGMA

Explanation: An attempt to initiate the good morning message transaction was made without specifying a termid for it to be displayed.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Use the dump to determine how the attempt to start the transaction was made. Ensure that no EXEC CICS STARTs are made for the

good morning message transaction where no termid is specified.

Module: DFHGMM

AICA

Explanation: A task has been executing for longer than the runaway time interval (defined by the ICVR operand on the system initialization table macro,

DFHSIT) without giving up control. The runaway task condition indicates a possible loop in the application.

System Action: The task is terminated with an AICA transaction dump.

User Response: See the CICS Problem Determination Guide for guidance on dealing with loops.

Module: DFHSRP

AICB

Explanation: A RETRIEVE WAIT request has been reissued in system shutdown.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: None

Module: DFHICP

AICC

Explanation: An incorrect response was returned from a timer (TI) domain request.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Modules: DFHTAJP, DFHICP

AICD

Explanation: A incorrect response was returned from a kernel (KE) domain request.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHICP

AICE

Explanation: An incorrect response was returned from a dispatcher (DS) domain request (other than AICG).

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHICP

AICF

Explanation: An incorrect response was returned from a transaction manager (TM) domain request.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHICP

AICG

Explanation: A PURGED response was returned from a dispatcher domain (DS) request, with a reason code of TASK_CANCEL. TASK_CANCEL was

returned as the transaction had been explicitly cancelled.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Notify your system programmer to determine why the task has been purged.

Module: DFHICP

AICH

Explanation: The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected

the purged condition will have provided an exception trace.

System Action: The task is abnormally terminated with a CICS transaction dump.

User Response: Investigate why the task was purged. This is 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: DFHICP, DFHEIIC

AICJ

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 will have provided 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.

Module: DFHICP

AICK

Explanation: Module DFHEIIC has issued a resource level security check (RSLC) request to module DFHXSRC and received a response other than OK or

EXCEPTION.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Examine the trace to find the exception trace entry created by DFHXSRC at the time of the error. Use this trace entry to determine the

cause of the return code from DFHXSRC.

Module: DFHEIIC

AICL

Explanation: DFHEIIC detected an invalid function code in the command level parameter list. This is caused either by 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 trace of the IC and EI components would aid problem determination. Look in the program storage

section of the transaction dump and compare argument 0, the exec interface descriptor (EID), for the command being processed with the argument 0

produced by the translator for the same command. Any differences mean that an overwrite of the application program may have occurred. You need further

assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

Module: DFHEIIC

AICN

Explanation: An incorrect response has been returned from a user domain (US) request.

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 Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHICP

AICO

Explanation: An unexpected EXCEPTION response was received from a call to the user (US) domain.

The call was issued during initialization of a transaction that was started without a terminal. The call was made as part of processing to associate the

transaction with its intended user. The attempt to associate the intended user with the transaction has failed.

The userid for the intended user of the transaction may not be correctly defined.

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Determine why the intended user of the transaction is not correctly defined.

Examine messages produced for the CICS job by the external security manager (ESM). This may require the assistance of a security administrator.

It may be necessary to examine the transaction dump to determine why the external security manager has informed CICS that the user is not correctly

defined.

When the user has been correctly defined, consider rerunning the transaction.

Module: DFHICXM

AICQ

Explanation: Module DFHDFST is executing at a terminal which is not permitted.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Determine why this transaction is executing at a terminal.

Module: DFHDFST

AICR

Explanation: A DFHTC write request has failed for IRC. The return codes within TCATPAPR and TCTEIRET should be examined to determine the cause of

failure.

System Action: The CSNC transaction is abnormally terminated with a CICS transaction dump.

User Response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to

proceed.

Module: DFHCRR

AICS

Explanation: Module DFHDFST has encountered an error during Retrieve processing.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Use level 1 trace entries to determine the cause of the failure.

Module: DFHDFST

AICT

Explanation: Module DFHDFST has encountered an error during START processing.

System Action: The transaction is abnormally terminated with a transaction dump.

User Response: Use level 1 trace entries to determine the cause of the error.

Module: DFHDFST

AIEA