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
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).
User Response: Inform the system programmer.
Examine the trace and the dump to identify the point
of error.
Module: DFHAMTD
AALO
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).
of error.
Module: DFHAMD2
AALP
call to the Program Manager. The domain that detected
the original error provides a trace entry and possibly a
the dump table).
of error.
Module: DFHAMPG
AALQ
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).
of error.
Module: DFHAMBA
AALR
call to the Temporary Storage Manager. The domain
that detected the original error provides a trace entry
of error.
Module: DFHAMBA
AALS
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
of error.
Module: DFHAMBA
AALT
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
of error.
Module: DFHAMOP
AALU
call to the Sockets Domain Manager. The domain that
of error.
Module: DFHAMSO
AALV
call to the Enterprise Java Domain. The domain that
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.
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
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
Module: DFHALP
AAL6
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
the dump table).
Module: DFHALP
AAL7
schedule a remote terminal delete by DFHALP during
the dump table).
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.
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.
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.
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.
Module: DFHAMP
AAMF
received following a call to the kernel (KE) domain.
This might be due to an internal logic error.
with a dump.
Module: DFHAMP
AAMH
received following a call to DFHFCMT. This might be
due to an internal logic error.
with a dump.
Module: DFHAMP
AAMI
received following a call to DFHFCRL. This might be
due to an internal logic error.
with a dump. You need further assistance from IBM to
resolve this problem. See Part 4 of the CICS Problem
User Response:
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.
At the time the error is detected, CICS writes a
message to the console, records an exception trace entry
and takes a system dump.
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.
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.
Module: DFHAMP
AAMO
Explanation: An invalid return code was returned
from DFHTOR, the CICS terminal object resolution
program.
Module: DFHAMP
AAMP
received from DFHPUP. This might be due to an
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.
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.
Module: DFHAMP
AAMT
Explanation: There is an internal logic error in
DFHAMP due to an unexpected return code from
DFHTMP.
Module: DFHAMP
AAMZ
received from DFHZCP. This is due to an internal logic
error.
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.
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.
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
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:
v You have linkedited your application program with a
CPI stub which supports more function than this
release of CICS.
v The linkedit stub has been corrupted.
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.
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
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
request to the storage manager (SM) domain was able
to complete successfully. The domain that first detected
the purged condition provides an exception trace.
Module: DFHCPCBI
AAOE
Module: DFHCPCBA
AAOF
Module: DFHCPCBS
AAOG
Explanation: During the processing of CMACCP
(accept conversation), CPI Communications detected
that the application was attached with an unsupported
sync level.
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:
Register Label Description
R4=@JCA TCZARQPJ JCAJCRC is nonzero.
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.
address the JCA. The CICS log manager request is
contained in JCATR2 and the response code is in
JCAJCRC.
X�8001� WRITE
X�8003� PUT
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.
Analysis:
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.
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
unexpected call to one of its internal routines.
course of events prior to this error, for example, the
Module: DFHCPIC
AAOL
Explanation: CPI Communications has made an
invalid call to DFHLUC.

Module: DFHCPCLR
AAOM
Explanation: The CPI Communications and the
DFHZUSR state machines are out of synchronization.
Modules: DFHCPCLR, DFHCPSRH
AAON
unexpected response from DFHLUC.
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.
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.
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:
v The CPC (conversation control block) has been
overwritten in such a way that the conversation state
has been altered, or
v There is an error in the CPI Communications state
machine.
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
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.
Module: DFHCPCFS
AAOR
invalid value in the CPC (conversation control block).
There are 2 possible causes of this error:
v The CPC (conversation control block) has been
overwritten, or
There is an error in CPI Communications which
causes it to reject valid values.
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:
v The CPC has been overwritten, or
v There is an error in CPI communications.
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.
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
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.
the error itself.
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.
Module: DFHCPCFS
AAOW
internal logic error in DFHCPCLC.
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.
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.
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.
proceed.
Module: DFHCPCRB
AAOZ
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.
User Response: Use CICS traces and, possibly, a
VTAM trace to determine the data that was sent
between both systems.
proceed.
Module: DFHCPCRB
AAO2
unexpected response from DFHLUC.
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.
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.
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
on how to proceed.
Module: DFHCPCLR
AAO5
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.
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
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.
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
Abend codes ABxx
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.
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
ENDACTIVITY while there were activity completion
events pending. The activity was executed with a RUN
command.
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
(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
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
handle this abend.
User Response: Investigate why the activity had
pending activity completion events.
Module(s): DFHEIBAM
ABLA
It was purged either by the master terminal operator or
as a result of deadlock timeout.
storage cannot be increased, the number of tasks in the
system should be reduced to avoid short-on-storage
Modules: DFHMCP, DFHMCPE, DFHM32, DFHPBP,
DFHRLR
ABLB
Explanation: An error (INVALID, DISASTER, or
trace, a console message and, possibly, a system dump
(depending on the options in the dump table).
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:
v OSPTR7
Chapter 3. Transaction abend codes 1143
v OSPHDRA
v OSPTRLA
Register 4 or OSPTIOA points to the TIOA. In the
TIOA, the following fields are relevant:
v TIOATDL
v 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.
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:
v OSPTR3 has X�10� bit set to indicate a user-specified
cursor position
v OSPCP contains a halfword cursor position specified
by user
v TTPSCSZ contains the halfword value of the screen
size to compare against.
If the abend occurs in DFHMCP or DFHMCX:
v Register 6 points to the OSPWA (in LIFO storage)
v OSPCP contains a halfword cursor position specified
by user
v OSPTR3 has X�10� bit set to indicate a user-specified
cursor position
v 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 userspecified
cursor
position.
OSPSCSZ halfword screen
size.
OSPCP halfword cursor
position.
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.
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�
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.
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.
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.
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.
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
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.
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.
User Response: Either define another output map or
redefine the existing map.
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.
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.
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:
X'01' Title address (TCAMSTA)
X'02' Alternate I/O area address (TCAMSIOA)
X'03' Map address (TCABMSMA)
X'04' Header address (TCAMSHDR)
X'05' Route list address (TCAMSRLA)
X'06' Trailer address (TCAMSTRL)
X'07' Map set address (TCAMSMSA)
X'08' TIOA address (TCTTEDA)
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.
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.
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
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.
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.
ABM0
Explanation: The map specified for a basic mapping
support (BMS) request could not be located.
User Response: Check if the map has been defined. If
it has, check that it has been specified correctly.
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.
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.
Module: DFHMCP
ABM3
Explanation: A BMS input or output request has been
issued from a task that is not terminal-oriented.
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.
Back to top
View user's profile Send private message
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
Greate Post!! Salute Author
1 salutes
PostPosted: Mon Oct 18, 2010 12:04 am Post subject: CICS ABEND CODES Reply
with quote
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).
Register 8 points to the MCR.
Register 5 points to the current entry.
Register 0 points to the end of table.
Register 9 points to the TCTTE.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Module: DFHTPS
ABNG
Explanation: An attach request was received from the
remote system without any data indicating the reason
for the request.
Module: DFHTPS
ABNH
Explanation: An attempt to ship data to the remote
system failed.
Module: DFHTPS
ABNI
Explanation: CICS could not find a profile for an
LU6.2 transaction routing request.
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
to complete successfully. The task that first detected the
purged condition provides an exception trace.
Module: DFHTPS
ABNK
Module: DFHTPS
ABRC
Explanation: The bridge exit is not defined and could
not be autoinstalled.
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.
User Response: Identify why the bridge exit is
disabled. Enable the bridge exit and retry the action.
ABRE
Explanation: The bridge exit could not be loaded.
User Response: Investigate why it cannot be loaded. It
may not have been defined in the DFHRPL library.
ABRF
Explanation: The bridge exit is defined as remote.
User Response: Define the bridge exit as a local
program.
ABRG
Explanation: An invalid bridge facility token was
specified
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.
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.
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.
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.
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.
ABRR
Explanation: The user transaction�s profile could not
be found.
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.
ABRZ
Explanation: The bridge exit returned invalid data in
the BRXA.
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.
Modules: DFHBRIC, DFHBRMS, DFHBRSP,
DFHBRTC, DFHXMBR
ABR3
Explanation: An unsupported BMS request was
received by the bridge exit.
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.
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.
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.
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.
with a dump.

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.
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.
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.
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.
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.
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
input error.
Module: DFH0CBAE,DFH0CBRE,DFH0CBAI
ABXG
when it tried to output the next message.
output error.
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.
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
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.
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
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.
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.
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.
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.
4K of the message. The task is abnormally terminated
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.
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.
Module: DFH0CBRF
ABXS
when it tried to open the queue for the input or output
message.
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.
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.
User Response: Ensure that the Client codepage is
valid.
Module: DFHBRMF
ABX1
with an invalid BRXA-HEADER. This indicates a
storage overwrite.
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.
ABX2
with an invalid BRXA-TRANSACTION-AREA. This
indicates a storage overwrite.
transaction dump.
ABRZ abend.
error, and retry.
ABX3
with an invalid BRXA-COMMAND-AREA. This
indicates a storage overwrite.
transaction dump.
ABRZ abend.
error, and retry.
ABX5
without a user-area. This probably indicates an error in
the bridge exit.
transaction dump.
error, and retry.
ABX6
with an invalid user-area. This indicates a storage
overwrite or an error in the bridge exit.
transaction dump.
error, and retry.
ABX7
Explanation: A TC command passed to the formatter,
exceeded the maximum message size.
4K of data in error. The task is abnormally terminated
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.
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.
message should have a BRMQ vector for this
mapname. Change the client application, recompile and
retry.
Module: DFH0CBRF
Abend codes ACxx
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:
v The language definition table, DFHEITCU, in the
library is invalid for the release of CICS you are
running, or
v A CICS logic error has occurred.
System Action:
v In a CICS environment, the CEDA transaction is
abnormally terminated with a CICS transaction
dump.
v 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
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:

dump.
Module: DFHCAP
ACAJ
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
Module: DFHCAP
ACAM
module DFHECBAM was invoked while processing a
CBAM transaction.
System Action: CBAM is abnormally terminated with
a CICS transaction dump.
Module: DFHECBAM
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.
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.
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
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.
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.
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.
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.
ACHA.
to proceed.
Module: DFHCHS
ACHD
Explanation: The remote server did not receive the
expected response type data frame from CICS/CMS.
ACHA.

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.
ACHA.
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.
ACHA.
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.
ACHA.
to proceed.
Module: DFHCHS
ACHH
Explanation: A TIOA has not been created from the
data received by the remote server from CICS/CMS.
ACHA.
to proceed.
Module: DFHCHS
ACHI
Explanation: The remote server has received an
unexpected return code from the Transformer 2
program.
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.
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.
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.
ACHA.
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.
ACHA.
to proceed.
Module: DFHCHS
ACHN
request from CICS/CMS which failed repeatedly until
the retry limit was exceeded.
ACHA.
to proceed.
Module: DFHCHS
ACHO
reply from CICS/CMS which failed repeatedly until the
retry limit was exceeded.
ACHA.
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.
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
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.
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
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.
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.
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.
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.
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.
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.
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
an error while processing a storage release request.
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
failed to catch.
transaction.
Module: ICCGLBIC
ACL8
failed to catch.
transaction.
Module: ICCGLBIC
ACL9
Explanation: The CICS Foundation Classes responded
to an application programmer�s request to abend a
CICS task.
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
an internal error.
transaction.
Module: ICCGLIBC
ACLB
an internal error.
transaction.
Module: ICCGLIBC
ACLC
an internal error.
transaction.
Module: ICCGLIBC
ACLD
an internal error.
transaction.
Module: ICCGLIBC
ACLE
an internal error.
transaction.
Module: ICCGLIBC
ACLF
an internal error.
transaction.
Module: ICCGLIBC
ACLG
an internal error.
transaction.
Module: ICCGLIBC
ACLH
an error while processing a storage release request.
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.
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.
determine the exact condition returned from LINK
request.
Module: DFHCCNV
ACN1
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.
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.
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).
User Response: Check that the DFHUCNV module is
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.
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.
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.
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.
User Response: Ensure that the Client codepage is
valid.
Module: DFHCCNV
ACND
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.
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
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.
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.
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
User Response: Correct the FIELD definition.
Module: DFHCCNV
ACN9
This abend code is issued following a NOTAUTH
condition being raised during loading of the DFHCNV
table.
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.
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.
operation.
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
transaction has encountered an error when
communicating with another system on an APPC
session.
System Action:
1. Message DFHZC4951 is written to destination
CSNE.
trace destinations.
User Response: Determine what caused the failure. A
likely cause is a failure of the session with the partner
system.
Module: DFHCLS5
ACQC
transaction has encountered an unexpected error.
System Action:
1. Message DFHZC4951 is written to destination
CSNE.
trace destinations.
Module: DFHCLS5
ACRA
Explanation: The relay program has been invoked
without a terminal as its principal facility.
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.
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.
Module: DFHAPRT
ACRD
Explanation: The system entry for the system to
which routing is to be performed could not be found.
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.
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
v The AID terminal ID matches that of the TCTTE
v The installed transaction definition and the AID
transaction IDs match
v The AID is for a remote transaction
v The AID has not been canceled.
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.
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.
A message in the range DF
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
PostPosted: Mon Oct 18, 2010 12:08 am Post subject: CICS abend codes Reply
with quote
ACRI
Explanation: An error occurred when attempting to
link to the dynamic routing program.
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.
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.
Module: DFHAPRT
ACRL
Explanation: The task does not own the facility.
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.
User Response: Examine the following possibilities:
v The autoinstall user-replaceable module (URM) was
called but is unable to do the autoinstall.
v The autoinstall URM was called but data supplied by
the autoinstall URM is invalid.
v The autoinstall URM was called, but there is no
processing program table (PPT) entry for the
autoinstall model.
v There is a problem with the autoinstall URM.
v 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.
v The program is disabled.
v The program cannot be loaded.
v 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.
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.
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.
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.
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.
Module: DFHCRS
ACSC
Explanation: An unexpected request was received
from a remote system when expecting a request to
schedule a task.
Module: DFHCRS
ACSD
Explanation: An internal logic error has been detected.
Module: DFHCRS
ACSE
Explanation: Module DFHCRS has been attached in
an unsupported manner.
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
proceed.
Module: DFHCRS
ACSF
to complete successfully. The task that first detects the
purged condition provides an exception trace.
Module: DFHCRS
ACSG
that detected the original error will have provided an
the dump table).
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.
User Response: Check that:
v The entry in the TCT for the remote system has been
defined with parallel sessions
v The remote system can support a sync level of 2
v The correct sync level has been requested.
Module: DFHCRS
ACSI
Explanation: An APPC conversation failure occurred
when an attach between CICS systems was issued.
User Response: Check the connection to the remote
CICS system and try to reestablish it.
Module: DFHCRS
ACSJ
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.
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
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.
Module: DFHCRS
ACSM
Explanation: Transaction CFTS has abended. The mass
flagging of terminals for deletion has failed.
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.
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.
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
Module: DFHZTSP
ACTB
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.
User Response: Use the transaction dump to
determine why terminal control was unable to process
the request.
Module: DFHZTSP
ACTC
request to free its session to the application-owning
system, and received a nonzero return code from
terminal control.
TCATPAPR.
the request.
Module: DFHZTSP
ACTD
WRITE,WAIT,READ request to the application-owning
terminal control.
TCATPAPR.
the request.
Module: DFHZTSP
ACTE
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.
the request. The terminal session may have failed.
Module: DFHZTSP
ACTF
request to free its session to the application-owning
terminal control.
This return code can be found in the TCA field,
TCATPAPR.
the request. The transaction on the application-owning
region may have abnormally terminated or the session
may have failed.
Module: DFHZTSP
ACTG
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.
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.
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.
Module: DFHCRT
ACTJ
Explanation: The principal facility of the relay
transaction is not a TCTTE.
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
purged condition will have provided an exception
trace.
was purged. It was either purged by the master
Module: DFHZISP
ACTL
the dump table).
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.
with a transaction dump and an exception trace entry.
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.
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.
Module: DFHZXRL
ACUD
Explanation: The profile DFHCICSR could not be
located as an installed profile definition.
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.
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.
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.
Module: DFHZXRL
ACUH
region failed. The return code from the ALLOCATE
request indicated that the requested session is already
owned by the TCA.
Module: DFHZXRL
ACUI
Explanation: An ISC session between the
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.
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
region was not allocated because the maximum session
count for the mode group specified in profile
DFHCICSR is zero.
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.
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 request. This abend code may result when:
v The relay program in the terminal-owning region
terminates abnormally. In this case, determine the
reason why the relay program has abnormally
terminated.
v The session has failed.
Module: DFHZXRL
ACUM
Explanation: A request to DFHZTSP to free a
surrogate TCTTE was not satisfied.
Module: DFHZXRL
ACUO
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.
terminated.
Module: DFHZXRL
ACUP
ACUR.
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.
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
Module: DFHZXRL
ACUT
application-owning region did not receive either a
syncpoint or a rollback from the terminal-owning
region. This violates CICS transaction routing protocols.
Module: DFHZXRL
ACUV
ISSUE ABEND request on an MRO link to the
terminal-owning region, and received a nonzero return
the trace entry on return from DFHZIS1.
terminated.
Module: DFHZXRL
ACUW
ISSUE ERROR request on an MRO link to the
terminal-owning region, and received a nonzero return
terminated.
Module: DFHZXRL
ACUX
Explanation: Refer to the description of abend ACUL.
Module: DFHZXRL
ACUY
WRITE,WAIT request to the terminal-owning region,
and received a nonzero return code from terminal
control.
terminated.
Module: DFHZXRL
ACUZ
Explanation: Refer to the description of abend ACUL.
Module: DFHZXRL
ACU0
WRITE,LAST,WAIT request to the terminal-owning
terminal control.
terminated.
Module: DFHZXRL
ACU1
Module: DFHZXRL
ACU2
application-owning region received a response from the
terminal-owning region which violates CICS transaction
routing protocols.
Module: DFHZXRL
ACU3
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.
Module: DFHZXRL
ACU4
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.
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.
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.
Module: DFHZXRL
ACU7
region was issued, but the connection with the remote
system is not an APPC or MRO connection.
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.
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.
Module: DFHZXRL
ACVA
WRITE,WAIT,READ request to the application-owning
terminal control.
v The program in the application-owning region
reason why the program has abnormally terminated.
Module: DFHZXRT
ACVB
terminal-owning region attempted to issue an ISSUE
SIGNAL request on an MRO link to the
application-owning region. This violates CICS
Module: DFHZXRT
ACVC
terminal-owning region issued an ISSUE SIGNAL
request on an LU 6.2 link to the application-owning
terminal control.
The return code is located in the DFHLUC parameter
Module: DFHZXRT
ACVD
terminal-owning region issued a READ,WAIT request
to the application-owning region, and received a
Module: DFHZXRT
ACVE
terminal-owning region issued a WRITE request to the
application-owning region, and received a nonzero
return code from terminal control.
v the program in the application-owning region
v the session has failed.
Module: DFHZXRT
ACVF
terminal-owning region issued a WRITE,LAST,WAIT
request to the application-owning region, and received
a nonzero return code from terminal control.
Module: DFHZXRT
ACVG
terminal-owning region issued a FREE request to free
the session with the LU 6.2 terminal, and received a
Module: DFHZXRT
ACVH
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.
Module: DFHZXRT
ACVK
terminal-owning region issued an ISSUE ABEND
request on an LU 6.2 link, and received a nonzero
v The program in the connected region terminates
abnormally. In this case, determine the reason why
the program has abnormally terminated.
Module: DFHZXRT
ACVL
terminal-owning region issued an ISSUE ABEND
request on an MRO link to the application-owning
terminal control.
Module: DFHZXRT
ACVM
terminal-owning region issued an ISSUE ERROR
request on an LU 6.2 link, and received a nonzero
Module: DFHZXRT
ACVN
terminal-owning region issued an ISSUE ERROR
request on an MRO link to the application-owning
terminal control.
Module: DFHZXRT
ACVO
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.
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:
Otherwise the distributed application programs may
have violated APPC conversation protocols.
Module: DFHZXRT
ACVP
terminal-owning region did not receive an FMH43 from
the application-owning region. This violates CICS
The trace from the application-owning region will show
its response to the terminal-owning region.
Module: DFHZXRT
ACVQ
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.
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
terminal-owning region issued a SEND,LAST,WAIT
request to the LU 6.2 terminal, and received a nonzero
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.
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
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.
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.
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.
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.
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.
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:
v The user was unauthorized to access the PSB, or
v The PSB was unknown to the external security
manager, or
v 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.
v 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.)
v 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).
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.
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.
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.
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).
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
response) has occurred on a call to the catalog (CC)
the dump table).
Modules: DFHDBCON, DFHDBDSC
ADDC
response) has occurred on a call to the loader (LD)
will have provided an exception trace, a console
message, and possibly a system dump (depending on
the options in the dump table).
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.
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:
v A DFHDI or DFHBMS request was issued when the
DFHDIP program was generated as a dummy.
v 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.
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
database, but the link to the system on which the
database resides was down.
User Response: Notify the system programmer. Once
the link to the remote system has been reestablished,
resubmit the transaction.
Module: DFHDLIRP
ADLG
database, but there were errors in the DL/I argument
list that was provided by the user.
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:
v The user was unauthorized to access the PSB, or
v The PSB was unknown to the external security
manager, or
v 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.
v 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.)
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).
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.
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
E
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
PostPosted: Mon Oct 18, 2010 12:10 am Post subject: CICS abend codes Reply
with quote
AD2A
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
Module: DFHD2EX1
AD2B
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
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
Module: DFHD2EX1
AD2D
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).
Module: DFHD2EX1
AD2E
has occurred on a locate call to directory manager (DD)
domain to locate a DB2ENTRY control block. A console
Module: DFHD2EX1
AD2F
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
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.
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.
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
to link to a dynamic plan exit program because it is
disabled.
dynamic plan exit program involved. Enable the
dynamic plan exit program.
Module: DFHD2EX1
AD2K
to link to a dynamic plan exit program because no
program definition was found.
dynamic plan exit program involved. Ensure that the
dynamic plan exit program has been correctly defined
to CICS.
Module: DFHD2EX1
AD2L
to link to a dynamic plan exit program because the
program could not be loaded.
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
to link to a dynamic plan exit program because the
program is defined as remote.
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
to link to a dynamic plan exit program.
dynamic plan exit program involved. Examine the
transaction dump to determine why the link failed.
Module: DFHD2EX1
AD2O
WAIT_MVS call to the dispatcher (DS) domain. A
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.)
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
getmain call to the storage manager (SM) domain. A
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.
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
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:
returned to the application and a transaction dump is
taken with abend code AD2T.
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:
returned to the application and a transaction dump is
taken with abend code AD2U.
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.
Module: DFHD2EX1
AD2X
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).
Module: DFHD2EX1
AD2Y
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:
v 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.
v The DB2ENTRY specified threadwait(pool), but the
pool definition within the DB2CONN specifies
threadwait(no), and again there were no TCBs
available.
v The transaction was using the pool directly, the pool
specifies threadwait(no) and no TCB was available.
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.
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
received a request for a resource manager with the
incorrect name. Message DFHDB2045 is output to
transient data detailing the invalid name.
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.
Module: DFHD2EDF
AD23
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
System Action: The CICS-DB2 service task initiates a
force shutdown of the CICS-DB2 interface.
Module: DFHD2EX2
AD24
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
System Action: The CICS-DB2 Service task initiates a
force shutdown of the CICS-DB2 interface.
Module: DFHD2EX2
AD25
the CICS-DB2 attachment facility while processing a
DSNC command. A console message is output, an
table).
System Action: The DSNC command fails and the
transaction is abnormally terminated with a transaction
dump.
Module: DFHD2CC
AD26
by the CICS-DB2 attachment facility while processing a
DSNC command. A console message is output, an
table).
System Action: The DSNC command fails and the
transaction is abnormally terminated with a transaction
dump.
Module: DFHD2CC
AD27
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.
User Response: Increase the size of the CICS region or
lower the TCBLIMIT value specified in the DB2CONN.
Module: DFHD2EX1
AD28
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.
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
the CICS-DB2 attachment facility startup program. A
System Action: Startup of the CICS-DB2 interface is
terminated, and the interface is closed. The task is
Module: DFHD2STR
AD3B
by the CICS-DB2 Attachment facility startup program.
A console message is output, an exception trace written
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
table).
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
System Action: The DSNC STRT command fails. The
task is abnormally terminated with a CICS transaction
dump.
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
System Action: The DB2 request fails. The task is
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
the transaction, a terminate thread request was made to
DB2 which failed. A console message is output, an
table).
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
from an EXEC CICS GETMAIN issued during
processing of a CICS-DB2 DSNC command. A console
System Action: The DSNC command fails. The task is
Module: DFHD2CM1
AD3I
from an EXEC CICS INQUIRE DB2CONN command
issued during startup of the CICS-DB2 interface. A
Module: DFHD2CM1
AD3J
Explanation: A commit request to DB2, issued during
the second phase of syncpoint, failed. A console
with a CICS transaction dump. CICS maintains a record
that the UOW committed pending a future
resynchronization request with DB2.
dump to determine why the commit request failed. The
commit request contains eyecatcher ?COMM? and is
Module: DFHD2D2
AD3K
Explanation: An abort request to DB2, issued during
the second phase of syncpoint, failed. A console
with a CICS transaction dump. CICS maintains a record
that the UOW backed out pending a future
resynchronization request with DB2.
dump to determine why the abort request failed. The
abort request contains eyecatcher ?ABRT? and is
Module: DFHD2D2
AD3L
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).
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
System Action: The DSNC MODIFY command fails.
The task is abnormally terminated with a CICS
transaction dump.
Module: DFHD2CM1
AD3P
Explanation: An unexpected error occurred during
processing of a DSNC STOP command. A console
System Action: The DSNC STOP command fails. The
dump.
Module: DFHD2CM1
AD3Q
while attempting to read a record from a temporary
dump.
Module: DFHD2CM1
AD3R
while attempting to read a record from a temporary
storage queue during startup of the CICS-DB2 interface.
terminated, the interface is closed. The task is
Module: DFHD2STR
AD3S
from an EXEC CICS SET DB2CONN command issued
during startup of the CICS-DB2 interface. A console
Module: DFHD2CM1
AD3T
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).
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
response ) has occurred on a locate call to transaction
manager (XM) domain to locate a transaction
definition. A console message is output, an exception
Module: DFHD2EX1
AD3W
while attempting to write a record to a temporary
storage queue during startup of the CICS-DB2 interface.
Module: DFHD2STR
AD3X
while attempting to write a record to a temporary
dump.
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.
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
Abend codes AExx
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.
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
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.
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).
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).
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
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
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
an unexpected error during the RUNUNIT
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.
Module: DFHAPLI
AEC9
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.
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).
determine why the start has failed.
Module: DFHEDFX
AEDB
Explanation: DFHEDFP has been passed an invalid
EDFXA. This is an internal CICS error.
Module: DFHEDFX
AEDC
Explanation: The program EDF has terminated
because a GETMAIN request to the storage manager
failed.
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.
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.
determine why the suspend has failed.
Module: DFHEDFX
AEDF
allow the EDF task to complete. The user task has been
purged while suspended, before control was returned
from EDF.
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
allow the EDF task to complete. The user task has gone
away while suspended, before control was returned
from EDF.
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.
determine why the call has failed.
Module: DFHEDFX
AED1
Explanation: This abend is produced as a result of
either:
v An attempt to use the execution diagnostic facility
(EDF) on an unsupported terminal,
v Using the temporary storage browse transaction
(CEBR) on an unsupported device, or
v An attempt to initiate the temporary storage browse
transaction (CEBR) with a non-terminal principal
facility.
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.
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 terminate
One possible cause of an abend in EDF is incorrect data
being sent to the terminal by the user task.
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.
User Response: This indicates a CICS logic error. You
need further assistance from IBM to resolve this
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
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
Module: DFHEDFU
AED7
Explanation: The installed definition of the transaction
CEDF has a TWA size which is too small.
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
Module: DFHEDFP
AED8
Explanation: A terminal control error has occurred in
DFHEDFX.
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
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
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.
Because of their similar characteristics, the
above-named abend codes for the EXEC interface
program are described as a group. The codes and their
corresponding exceptional conditions are as follows:
Code Condition
AEIA ERROR
AEID EOF
AEIE EODS
AEIG INBFMH
AEIH ENDINPT
AEII NONVAL
AEIJ NOSTART
AEIK TERMIDERR
AEIL FILENOTFOUND
AEIM NOTFND
AEIN DUPREC
AEIO DUPKEY
AEIP INVREQ
AEIQ IOERR
AEIR NOSPACE
AEIS NOTOPEN
AEIT ENDFILE
AEIU ILLOGIC
AEIV LENGERR
AEIW QZERO
AEIZ ITEMERR
AEI0 PGMIDERR
AEI1 TRANSIDERR
AEI2 ENDDATA
AEI3 INVTSREQ
AEI4 EXPIRED
AEI8 TSIOERR
AEI9 MAPFAIL
AEXC RESIDERR
AEXF ESCERROR
AEXG UOWLNOTFOUND
AEXI TERMERR
AEXJ ROLLEDBACK
AEXK END
AEXL DISABLED
AEXV VOLIDERR
AEXW SUPPRESSED
AEXX TASKIDERR
AEX0 TCIDERR
AEX1 DSNNOTFOUND
AEX2 LOADING
AEX3 MODELIDERR
AEX4 UOWNOTFOUND
AEX5 PARTNERIDERR
AEX6 PROFILEIDERR
AEX7 NETNAMEIDERR
AEX8 LOCKED
AEX9 RECORDBUSY
Code Condition
AEYA INVERRTERM
AEYB INVMPSZ
AEYC IGREQID
AEYE INVLDC
AEYG JIDERR
AEYH QIDERR
AEYJ DSSTAT
AEYK SELNERR
AEYL FUNCERR
AEYM UNEXPIN
AEYN NOPASSBKRD
AEYO NOPASSBKWR
AEYP SEGIDERR
AEYQ SYSIDERR
AEYR ISCINVREQ
AEYT ENVDEFERR
AEYU IGREQCD
AEYV SESSIONERR
AEYX USERIDERR
AEYY NOTALLOC
AEYZ CBIDERR
AEY0 INVEXITREQ
AEY1 INVPARTNSET
AEY2 INVPARTN
AEY3 PARTNFAIL
AEY7 NOTAUTH
AEZE CHANGED
AEZF PROCESSBUSY
AEZG ACTIVITYBUSY
AEZH PROCESSERR
AEZI ACTIVITYERR
AEZJ CONTAINERERR
AEZK EVENTERR
AEZL TOKENERR
AEZM NOTFINISHED
AEZN POOLERR
AEZO TIMERERR
AEZP SYMBOLERR
AEZQ TEMPLATERR
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.
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
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.
operator, or as a result of a deadlock timeout.
storage cannot be increased then the number of tasks in
the system should be reduced to avoid short-on-storage
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.
operator, or as a result of a deadlock timeout.
Module: DFHEGL
AEMA
response) has occurred on a call to the application (AP)
domain when a request for set user exit active could
not be serviced.
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
response) has occurred on a call to the loader (LD)
will have provided an exception trace, a console
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.
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
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.
transaction.
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.
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.
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.
transaction.
Module: DFHERM
AETG
the dump tablE
Module: DFHERM
AETH
transaction.
Module: DFHERM
AETI
the dump table).
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,
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).
Module: DFHERM
AETK
an SET_LINK call to the recovery manager (RM)
in the dump table).
Module: DFHERM
AETL
an SET_UOW call to the recovery manager (RM)
in the dump table).
Module: DFHERM
AETM
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
For all errors, DFHRMSY provides an exception trace,
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,
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
DFHRMSY also provides an exception trace, console
message DFHAP0002, and possibly a system dump
Module: DFHRMSY
AETP
an TERMINATE_RECOVERY call to recovery manager
(RM) domain. For errors other than EXCEPTION, the
RM domain provides an exception trace, a console
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
AETP
an TERMINATE_RECOVERY call to recovery manager
(RM) domain. For errors other than EXCEPTION, the
RM domain provides an exception trace, a console
Module: DFHRMSY
AETQ
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).
Module: DFHRMSY
AETR
INQUIRE_UOW call to the recovery manager (RM)
domain. The RM domain provides an exception trace, a
console message, and possibly a system dump
DFHRMSY also provides an exception trace, console
Module: DFHRMSY
AETS
an INQUIRE_STARTUP call to recovery manager (RM)
in the dump table).
Module: DFHRMSY
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.
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
AEXY
Explanation: The executing transaction has been
purged before control could be returned.
This can arise when the transaction is purged while
v A CICS command was being processed
v The transaction was waiting to be dispatched
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).
terminated with abend code AEXZ. CICS takes a
transaction dump, unless module DFHDUIO is not
loaded.
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
Module:
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.
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:
v Correct the code in error in the transaction issuing
the EXEC CICS command in order to supply a valid
storage area.
v 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.
v If storage protection is active, change the
TASKDATAKEY attributes on the transaction
definition from CICS to USER.
v If transaction isolation is active, change the ISOLATE
attribute on the transaction definition from YES to
NO.
Module: DFHSRP
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.
Module: DFHUEM
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.
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
to proceed.
Module: DFHEIP
AEY9
Explanation: One of the following:
v An EXEC CICS command has been issued that is not
supported by the EXEC interface program DFHEIP.
v 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.
v 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.
v An attempt has been made to use remote resources,
but the local SYSID has been specified in an EXEC
CICS command, or vice versa.
v An attempt has been made to use remote resources,
but ISC is not supported.
v An EXEC CICS command contains an invalid AID or
CONDITION identifier. This indicates that the EXEC
CICS command has become corrupted.
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.
terminated.
User Response: Either redefine and install a new
definition for the transaction with
TASKDATALOC(BELOW), or relink the programs as
amode 31.
Module: DFHEIP
AEZB
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.
terminated.
TASKDATALOC(BELOW), or modify the task related
user exit so that it is invoked in AMODE 31.
Module: DFHERM
AEZC
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.
terminated.
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.
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.
Module: DFHEIP
AEZG
Explanation: ACTIVITYBUSY condition not handled.
Module: DFHEIP
AEZH
Explanation: PROCESSERR condition not handled.
Module: DFHEIP
AEZI
Explanation: ACTIVITYERR condition not handled.
Module: DFHEIP
AEZJ
Explanation: CONTAINERERR condition not handled.
Module: DFHEIP
AEZK
Explanation: EVENTERR condition not handled.
Module: DFHEIP
AEZL
Explanation: TOKENERR condition not handled.
Module: DFHEIP
AEZM
Explanation: NOTFINISHED condition not handled.
Module: DFHEIP
AEZN
Explanation: POOLERR condition not handled.
Module: DFHEIP
AEZO
Explanation: TIMERERR condition not handled.
Module: DFHEIP
AEZP
Explanation: SYMBOLERR condition not handled.
Module: DFHEIP
AEZQ
Explanation: TEMPLATERR condition not handled.
Module: DFHEIP
Abend codes AFxx
AFCB
Explanation: Module DFHEIFC issued a resource level
security check (RSLC) request to module DFHXSRC
and received a response other than OK or EXCEPTION.
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.
Modules: DFHEIFC, DFHDMPCA
AFCE
Explanation: A GETMAIN for FFLE storage has failed.
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.
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:
v 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.
v 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.
v 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:
v 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.
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.
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.
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.
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.
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.
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).
AFCO
transaction specifying DFHDTLX as the program to be
attached by CICS.
DFHDTLX is for use by CICS system transaction CFTL.
This loads a Shared Data Table.
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.
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.
AFCS
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.
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.
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.
User Response: Resubmit the transaction.
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.
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.
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.
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:
v 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.
v The system in which the lock holder is running is
experiencing severe performance degradation.
Investigate the reason for the performance
degradation.
v 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.
v 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.
AFCW
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.
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.
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.
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.
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
User Response: The system programmer should use
the trace and dumps to determine what the error is,
and why it has occurred.
AFC0
Explanation: An attempt has been made to update a
file after file control restart failed.
User Response: Determine the cause of the failure in
file control restart. Restart CICS.
AFC2
Explanation: DFHFCU issued a call to DFHFCFS to
open a file. A disastrous error was returned from
DFHFCFS.
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.
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.
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
transaction specifying DFHFCQT as the program to be
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.
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.
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
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
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
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
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
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
on how to proceed.
Module: DFHFCQT
AFDE
transaction specifying DFHFCRD as the program to be
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.
to illegally attach CSFR, or why a transaction definition
specified DFHFCRD as the program to be given
control.
Module: DFHFCRD
AFDF
transaction specifying DFHFCOR as the program to be
attached by CICS.
DFHFCOR is for use by CICS system transaction
CFOR. This provides part of the RLS offsite recovery
support.
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
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.
AGMA
Explanation: An attempt to initiate the good morning
message transaction was made without specifying a
termid for it to be displayed.
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
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
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.
User Response: None
Module: DFHICP
AICC
Explanation: An incorrect response was returned from
a timer (TI) domain request.
Modules: DFHTAJP, DFHICP
AICD
Explanation: A incorrect response was returned from
a kernel (KE) domain request.
Module: DFHICP
AICE
a dispatcher (DS) domain request (other than AICG).
Module: DFHICP
AICF
a transaction manager (TM) domain request.
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.
User Response: Notify your system programmer to
determine why the task has been purged.
Module: DFHICP
AICH
transaction.
Modules: DFHICP, DFHEIIC
AICJ
the dump table).
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.
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.
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
Module: DFHEIIC
AICN
Explanation: An incorrect response has been returned
from a user domain (US) request.
Module: DFHICP
AICO
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.
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.
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
Module: DFHCRR
AICS
Explanation: Module DFHDFST has encountered an
error during Retrieve processing.
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.
User Response: Use level 1 trace entries to determine
Module: DFHDFST
AIEA
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.
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: DFHIEXM
AIEB
Explanation: The transaction id (CIEP) of the ECI for
TCP/IP listener task has been initiated invalidly,
probably by entering the id at a terminal. This
transaction must only be initiated by CICS internal
processes.
terminated.
User Response: Do not initiate CIEP directly.
Module: DFHIEP
AIIA
Explanation: An error occurred in the IIOP Request
Processor which prevented it from sending a reply to
the Request Receiver.
terminated.
User Response: The Request Processor will have
issued an exception trace and a message.
Examine this information to determine why the
Request Processor failed.
Module: com.ibm.cics.iiop.RequestProcessor
AIIT
Explanation: The IIOP Request Processor timed out
waiting for a request from a Request Receiver. It
received a timed out notification from the RZ domain
in response to a listen on the RequestStream of which it
is the target.
Reasons for this problem include:-
v the RTIMOUT value for this RequestProcessor
transaction is too low.
v the client program has failed to send a further
method request when one is expected by a
transactional object.
v a CICS failure or logic error may have occurred.
User Response: See any related diagnostic material
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
Module: com.ibm.cics.iiop.RequestProcessor
AII1
Explanation: An IIOP Request Receiver transaction
(default CIRR) was started invalidly. This transaction
can only be initiated internally by CICS.
terminated.
User Response: Do not issue this transaction.
Module: DFHIIRRS
AII2
Explanation: The IIOP Request Receiver program
DFHIIRR returned an exception which may have been
caused by data received from the client.
terminated.
User Response: DFHIIRR will have issued an
exception trace point and a message and attempted to
send a messageError or systemException to the client.
Examine this information to determine why the request
receiver rejected the request.
Module: DFHIIRRS
AII3
Explanation: An IIOP Request Receiver task has been
purged.
terminated.
User Response: None.
Module: DFHIIRRS
AII4
Explanation: The IIOP Request Receiver program
DFHIIRR has returned a disaster response due to a call
to another CICS program failing.
terminated.
User Response: DFHIIRR, or the program it called,
will have issued an exception trace point and a
message.
Examine this information to determine why the request
receiver failed.
Module: DFHIIRRS
AII5
Explanation: The IIOP Request Receiver stub program
was invoked from the sockets domain. However the
TCPIPSERVICE defined in RDO did not specify a
PROTOCOL of IIOP.
terminated.
User Response: Change the TCPIPSERVICE definition
to specify PROTOCOL(IIOP).
Module: DFHIIRRS
AINA
Explanation: An application program has issued an
EXEC CICS LINK command to the indoubt testing tool
program DFHINDT but has failed to pass a commarea
containing the request to be executed. Valid requests
are: ON, OFF, RESYNC COMMIT or RESYNC
BACKOUT.
User Response: Correct the application program so
that it passes a commarea to DFHINDT containing a
valid request for DFHINDT.
Module: DFHINDT
AINB
Explanation: An application program has issued an
EXEC CICS LINK command to the indoubt testing tool
program DFHINDT passing a commarea that did not
contain a valid request to be executed, Valid requests
are: ON, OFF, RESYNC COMMIT or RESYNC
BACKOUT
that it passes a commarea to DFHINDT containing a
valid request for DFHINDT.
Module: DFHINDT
AINC
Explanation: The indoubt testing tool issued a EXEC
CICS INQUIRE EXITPROGRAM command to inquire
on the status of the indoubt testing tool task related
user exit program DFHINTRU, and the command
failed with a NOTAUTH response.
User Response: The indoubt testing tool can be run
under transaction CIND , under a user transaction
where the program EXEC CICS LINKs to DFHINDT. or
under a transaction where the program EXEC CICS
LINKs to DFHINDAP. If command security checking is
active for the transaction (CMDSEC=YES), check that
the user has read access to resource EXITPROGRAM. If
resource security checking is active for the transaction
(RESSEC=YES), check that the user has read access to
resource DFHINTRU.
Modules: DFHINDT, DFHINDAP
AIND
Explanation: The indoubt testing tool issued a EXEC
CICS INQUIRE EXITPROGRAM command to inquire
on the status of the indoubt testing tool task related
user exit program DFHINTRU, and the command
failed with an unexpected response.
Modules: DFHINDT, DFHINDAP
AINE
an START_LINK_BROWSE command issued by the
indoubt tool to recovery manager (RM) domain. For
errors other than EXCEPTION, the RM domain
the dump table).
For all errors, DFHINDT provides an exception trace,
Module: DFHINDT
AINF
unexpected reason occurred on an GET_NEXT_LINK
call issued by the indoubt testing tool to recovery
manager (RM) domain. DFHINDT provides an
exception trace, console message DFHAP0002, and
the dump table).
Module: DFHINDT
AING
GET_NEXT_LINK call issued by the indoubt testing
tool to recovery manager (RM) domain. The RM
in the dump table).
DFHINDT also provides an exception trace, console
Module: DFHINDT
AINH
an END_LINK_BROWSE command issued by the
indoubt tool to recovery manager (RM) domain. For
the dump table).
Module: DFHINDT
AINI
an INQUIRE_UOW command issued by the indoubt
testing tool to recovery manager (RM) domain. For
the dump table).
Module: DFHINDT
AINJ
unexpected reason occurred on an
INITIATE_RECOVERY call issued by the indoubt
testing tool to recovery manager (RM) domain.
DFHINDT provides an exception trace, console
Module: DFHINDT
AINK
INITIATE_RECOVERY call issued by the indoubt
testing tool to recovery manager (RM) domain. The RM
in the dump table).
DFHINDT also provides an exception trace, console
Module: DFHINDT
AINL
an SET_RECOVERY_STATUS command issued by the
indoubt testing tool to recovery manager (RM) domain.
For errors other than EXCEPTION, the RM domain
the dump table).
Module: DFHINDT
AINM
an TERMINATE_RECOVERY command issued by the
indoubt testing tool to recovery manager (RM) domain.
For errors other than EXCEPTION, the RM domain
the dump table).
Module: DFHINDT
AINN
an ADD_LINK command issued by the indoubt testing
tool 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, DFHINTRU provides an exception trace,
Module: DFHINTRU
AINO
Explanation: The indoubt testing tool task related user
exit DFHINTRU issued an EXEC CICS INQUIRE
TRANSACTION command to inquire whether the
current transaction was in the indoubt transaction class
DFHTCIND. The command failed with a NOTAUTH
response.
User Response: When the indoubt testing tool is
active, the task related user exit DFHINTRU is invoked
whenever a CICS transaction is started. For all
transactions for which command security checking is
active, ensure that the user has read access to resource
TRANSACTION. If started transaction resource security
checking is specified, for all transactions for which
resource security checking is active, ensure that the
user has read access to the transaction name in the
specified RACF resource class.
For more information on command security and
resource security see the CICS RACF Security Guide.
Module: DFHINTRU
AINP
exit DFHINTRU issued an EXEC CICS INQUIRE
TRANSACTION command to inquire whether the
current transaction was in the indoubt transaction class
DFHTCIND. The command failed with an unexpected
response.
Module: DFHINTRU
AINQ
exit DFHINTRU issued an EXEC CICS INQUIRE TASK
command to inquire on the current task to obtain the
unit of work ID to include in message DFHIN1009. The
command failed with a TASKIDERR response.
Module: DFHINTRU
AINR
command failed with a NOTAUTH response.
User Response: When the indoubt testing tool is
active, the task related user exit DFHINTRU is invoked
whenever a CICS transaction is started. For all
transactions for which command security checking is
active (CMDSEC=YES), ensure that the user has read
access to resource TASK.
Module: DFHINTRU
AINS
command failed with an unexpected response.
Module: DFHINTRU
AISA
Explanation: The mirror transaction (CSMI) has been
attached from some facility other than a terminal. This
is not permitted.
User Response: Using the dump, check the field
TCAFCAAA to identify the invalid attach.
Module: DFHMIRS
AISB
Explanation: The mirror transaction (CSMI) has
detected errors in the data passed to it from the
attaching transaction.
User Response: The invalid input will be visible in
the transaction dump. This error is likely to be caused
by some mismatch between the two systems. A typical
example might be a DL/I request received on a system
generated without DL/I.
Module: DFHMIRS
AISC
Explanation: The mirror transaction (CSMI) has not
received a TIOA from the terminal.
User Response: Use the trace in the dump and the
dumped TCTTE to analyze the problem further.
Module: DFHMIRS
AISD
Explanation: The mirror program executed the request
and received a nonzero return code as a result. The
data flow control state of the intersystem link being
used was such that this information could not be
returned normally.
System Action: The mirror task is abnormally
User Response: The transaction dump provided will
provide information required to analyze the source of
the nonzero return code at its point of origin.
Module: DFHMIRS
AISF
Explanation: The CICS mirror program DFHMIRS has
been attached in an unsupported manner. The principal
facility for the mirror transaction is defined as APPC,
however the conversation is unmapped.
User Response: There is a problem with the system
that caused the mirror transaction to be attached. You
Module: DFHMIRS
AISG
Explanation: The mirror program executed the request
and produced the reply. This would not be sent
because the data flow control state of the intersystem
link was such that this could not be done.
System Action: The task (CSMI) is abnormally
User Response: Use the transaction dump provided to
analyze the problem.
Module: DFHMIRS
AISH
Explanation: The new connection task, CSNC, has
been invoked in an incorrect manner (for example,
from a terminal or via an EXEC CICS START request).
Module: DFHCRNP
AISI
Explanation: A function shipping request was passed
by DFHEIP to DFHISP. This was found to be invalid by
the transformer, DFHXFP.
System Action: The transaction issuing the function
shipping request is abnormally terminated with a CICS
transaction dump.
User Response: The transaction dump will provide
information to further analyze the problem.
Module: DFHISP
AISJ
Explanation: The IRC control task CSNC has abended
because the attempt to LINK to DFHCRR failed.
System Action: CSNC is abnormally terminated with
a system dump. All tasks using MRO links to other
systems are abnormally terminated. All tasks in other
CICS regions (including shared database batch regions)
that are currently communicating with this system are
also abnormally terminated.
User Response: Ensure that program DFHCRR is
available.
Module: DFHCRNP
AISK
Explanation: The user transaction has been
abnormally terminated during the execution of a
function shipping request on an APPC session. This has
happened because the mirror transaction on the remote
system has abnormally terminated, and caused a
request for syncpoint rollback to be sent across the
session. CICS abends the user transaction in these
circumstances so that function shipping remains
transparent to the transaction.
User Response: Check the log on the mirror system to
determine the reason for the original abend of the
mirror task.
Module: DFHISP
AISL
Explanation: The LU services manager transaction has
been started directly from a user terminal. This is not
permitted.
User Response: None. The LU services manager
transaction must be started internally by CICS.
Modules: DFHLUP, DFHCLS3, DFHCLS4, DFHZLS1
AISN
Explanation: Task CSNC attempted to acquire a
SUSPEND TOKEN to enable it to suspend itself until
further work arrives. The attempt failed.
a dump. The IRC facility is disabled.
Module: DFHCRNP
AISO
Explanation: Task CSNC attempted to suspend itself,
awaiting further work. The attempt failed.
a dump. The IRC facility is disabled.
Module: DFHCRNP
AISP
Explanation: A mirror transaction (transaction
identifiers CSHR, CSM1, CSM2, CSM3, CSM5, or CSMI)
has been invoked with an invalid principal facility. The
mirror transaction executes with an MRO session, an
LU6.1 session or an APPC session as its principal
facility.
User Response: Do not attempt to invoke the mirror
transaction by entering the transaction identifier at a
terminal.
Module: DFHMIRS
AISQ
Explanation: An EXEC CICS command has been
issued against a CPI Communications session. A CPI
Communications session is one that has a
CPI-Communications Control Block (CPC) associated
with it.
User Response: Do not mix EXEC commands with
CPI Communications calls on the same end of a
conversation.
Module: DFHMIRS
AISR
Explanation: The CICS Inter-Region Session Recovery
Program (DFHCRR) has been invoked in an incorrect
manner, for example, from a terminal.
System Action: The program DFHCRR is abnormally
Module: DFHCRR
AISS
Explanation: A security violation has occurred while
CICS was attempting to start a conversation with a
remote APPC system. The security access level of the
requestor was insufficient to access the transaction on
the connected APPC system. Depending on the nature
of the request and the way security has been set up, the
requestor with an insufficient access level can be the
local CICS system, the requesting transaction, or the
terminal user.
Note: DTP programs do not abend with code AISS
after a security failure in the remote region.
User Response: First, verify that the access was
correctly denied. Then, if required, change the access
level.
Module: DFHZARM
AIST
returned after a DFHTC TYPE=LOCATE command.
systems are abnormally terminated. All tasks in other
CICS regions (including shared database batch regions)
that are currently communicating with this system are
also abended.
User Response: The trace in the system dump should
be used to analyze the problem further.
Module: DFHCRNP
AISU
Explanation: An INVALID, DISASTER, or
EXCEPTION condition has occurred on a call to the
storage manager domain (SM) to FREEMAIN a FCENT
control block.
system dump.
Module: DFHMIRS
AISV
Explanation: A PURGED condition has occurred on a
call to the storage manager domain (SM) to FREEMAIN
a FCENT control block.
system dump.
transaction.
Module: DFHMIRS
AISW
storage manager domain (SM) to GETMAIN or
FREEMAIN a CRB control block.
system dump.
Module: DFHCRSP
AISX
call to the storage manager domain (SM) to GETMAIN
or FREEMAIN a CRB control block.
system dump.
It was purged either as a result of a purge from the
master terminal operator via the CEMT transaction, or
by the task being timed out after waiting for longer
than the DTIMOUT (deadlock timeout) value specified
for the transaction.
Module: DFHCRSP
AISY
Explanation: The LU services manager transaction has
been started, but invalid parameters have been
detected.
User Response: See message DFHZC4921 for further
guidance.
Module: DFHLUP
AISZ
Explanation: DFHMXP has received an unexpected
reply when committing START PROTECT NOCHECK
requests sent on a LUTYPE6.2 synclevel 1 conversation.
User Response: Determine what happened to
transaction CVMI in the partner system. If the START
PROTECT NOCHECK requests had been committed,
no further action is necessary. If they had not been
committed, user-defined action is required to recover
from the error.
Module: DFHMXP
AIS1
returned after a DFHMROQM FUNC=ENQ command
was issued.
This command was issued when enqueueing work for
the IRC control task (CSNC) during IRC initialization.
System Action: If IRC is being initialized during CICS
initialization (as a result of IRCSTRT being specified in
the DFHSIT or override parameters), then CICS is
abnormally terminated.
If IRC is being initialized during the execution of a
CEMT SET IRC OPEN command, then the CEMT
transaction is abnormally terminated.
Module: DFHCRSP
AIS2
returned after a DFHMROQM FUNC=WAIT_Q
command was issued.
This command was issued when waiting for more IRC
work to process.
systems are abnormally terminated.
All tasks in other CICS regions (including shared
database batch regions) that are currently
communicating with this system are also abended.
Module: DFHCRNP
AIS3
Explanation: An attempt to issue a STCK (Store
Clock) instruction failed.
a system dump.
All tasks using MRO links to other systems are
abnormally terminated.
User Response: Repair or enable the system clock.
Module: DFHCRNP
AIS4
returned after a DFHMROQM FUNC=ENQUEUE
command. This command was issued when enqueueing
work to the IRC �delayed work� queue.
Module: DFHCRNP
AIS5
returned after a DFHMROQM FUNC=ENQUEUE
command was issued.
This command was issued when enqueueing work to
the IRC �immediate work� queue.
Module: DFHCRNP
AIS6
Explanation: An INVALID, DISASTER or
storage manager domain (SM) to GETMAIN or
FREEMAIN a file control read set buffer.
system dump.
Module: DFHMIRS
AIS7
call to the storage manager domain (SM) to FREEMAIN
a file control read set buffer.
system dump.
terminal operator , or as a result of a deadlock timeout.
Module: DFHMIRS
AIS8
in module DFHMIRS.
Module: DFHMIRS
AIS9
Explanation: The mirror program has detected that a
DPL server program has returned in an invalid state
following the completion of the LINK command. The
server program or a program it linked to has initiated a
synclevel 2 conversation with another program which
in turn has issued a syncpoint. The server program has
not responded to the syncpoint request which is still
outstanding when control returns to the mirror
program.
The mirror program only issues this abend code if the
LINK request did not specify SYNCONRETURN.
User Response: Correct the design of the DTP
application or applications initiated by the server
program. If the SYNCONRETURN option is not
specified on the LINK request, only the client program
should initiate the syncpoint. If it is necessary to issue
syncpoint requests from the DTP applications, consider
using the SYNCONRETURN option on the LINK
request. See the CICS Intercommunication Guide for
further details of the LINK command and its options.
Module: DFHMIRS
AITA
call to the recovery manager (RM) domain to initialize
the recovery status of an IRC session. The domain
This failure is either the result of a task purge, or a
CICS logic error,
System Action: The CSNC task is abnormally
determine the reason for the failure. In the case of a
CICS logic error, you need further assistance from IBM.
Module: DFHCRNP
AITB
CICS logic error,
Module: DFHISP
AITC
CICS logic error,
Module: DFHMIRS
AITD
Explanation: The mirror program has received an
unexpected response from the RX domain.
There are several reasons why this error may occur:
v A request received from an EXCI client is
inconsistent with an earlier request in the same Unit
of Work
v CICS has received an unexpected response from the
Recoverable Resource Management Services
component of MVS.
v There has been an internal error in the RX domain.
User Response: Use the exception trace provided by
the RX domain to determine the reason for the failure.
If the error is caused by an inconsistent request from an
EXCI client, there may be an error in the client
program.
In the other cases, you might need further assistance
from IBM. You need further assistance from IBM to
Module: DFHMIRS
AITE
Explanation: A transaction has executed a
transactional EXCI request from a batch region, and has
been waiting for one of the following events for longer
than the interval specified in the RTIMOUT value for
the transaction.
v A further transactional EXCI request from the batch
region
v A syncpoint initiated by Resource Recovery
Management Services (RRMS).
User Response: Determine why the expected event
has not occurred:
If a further transactional EXCI request is expected
v The batch program may be suspended
If a syncpoint is expected
v The batch program may be suspended before
reaching syncpoint
v RRMS may have started syncpoint processing but is
waiting for another Resource Manager to respond to
the syncpoint request.
Module: DFHMIRS
AITF
transactional EXCI request from a batch region, and has
been purged while waiting for one of the following
events:
region
User Response: Determine why the expected event
has not occurred:
If a further transactional EXCI request is expected
v The batch program may be suspended
If a syncpoint is expected
v The batch program may be suspended before
reaching syncpoint
v RRMS may have started syncpoint processing but is
waiting for another Resource Manager to respond to
the syncpoint request.
Module: DFHMIRS
AITG
transactional EXCI request from a batch region, and
both of the following events has occurred:
region
Normally, only one event should occur, and not both.
User Response: Determine why both events have
occurred. This situation may arise when an EXCI client
times out on a DPL request that CICS is not ready to
receive and then proceeds to take a syncpoint. If this is
not the case, you may need assistance from IBM. You
Module: DFHMIRS
AITH
Explanation: A mirror transaction processing an ECI
request from a TCP/IP connected client has failed
while trying to receive data from, or send data to, a
client. This could be a read time out, or a more serious
error in the flows that prevented CICS from correctly
processing the data.
User Response: If the error was a time out, determine
why the client has not continued with the extended
ECI conversation. Other errors will have associated IE
domain messages to aid in problem determination.
Module: DFHMIRS
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
AJAA
Explanation: The CREA/CREC transaction could not
allocate the shared memory it required. The transaction
will free all allocated memory and issue this abend.
System Action: The transaction is terminated.
User Response: Examine the trace to determine why
the GETMAIN failed. If the CICS region was short on
storage then take the necessary steps to correct this. If
your region was not short on storage you may need
help from IBM to resolve this problem. You need
Module: DFHADDRM
AJAB
Explanation: The CREA/CREC transaction could not
free the shared memory it allocated.
the FREEMAIN failed. You may need help from IBM to
proceed.
Module: DFHADDRM
AJAC
Explanation: The CREA/CREC transaction browses
the installed REQUESTMODELs. An attempt to start or
continue the browse of the REQUESTMODELs failed
with an unexpected return code.
the INQUIRE REQUESTMODEL call failed. You may
need help from IBM to resolve this problem. You need
Module: DFHADDRM
AJAD
Explanation: The CREA/CREC transaction received
an unexpected return code from an EXEC CICS call
and could not continue.
Module: DFHADDRM
AJAE
Explanation: The CREA/CREC transaction used the
EXEC CICS SEND MAP call to display a BMS map.
This call returned an expected return code.
the SEND MAP call. You may need help from IBM to

proceed. failed.
Module: DFHADDRM
AJAF
Explanation: The CREA/CREC transaction used the
EXEC CICS RECEIVE MAP call to receive data from a
BMS map. This call returned an expected return code.
the RECEIVE MAP call failed. You may need help from
IBM to resolve this problem. You need further
on how to proceed.
Module: DFHADDRM
AJAG
Explanation: The CREA/CREC transaction must be
invoked using the transaction ID of �CREA� or �CREC�.
You are not able to use another transaction ID to
invoke DFHADDRM (the program invoked for the
CREA/CREC transaction).
User Response: Use CREA or CREC to invoke the
CREA/CREC transaction.
Module: DFHADDRM
AJA0
Explanation: The native method
SetAbendForCondition has been passed an invalid Resp
value by the Wrapper class.
Module: DFJCICS
AJCD
Module: DFHJCP
AJCE
Module: DFHJCP
AJCS
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
Module: DFHJCP
AJCT
Module: DFHJCP
AJCU
Explanation: A purge response has been received from
either the log manager or or the recovery manager. The
domain that detected the original purge condition
provides an exception trace.
Module: DFHJCP
AJH0
Explanation: Hotpooling initialization failed before
CEEPIPI could be called. Either the address of CEEPIPI
was found to be zero in CSZCEEPI, or initialization of
the services module DFHAPPIS failed.
with a CICS transaction dump. Hotpooling cannot be
used.
User Response: Message DFHAP1224 may be issued
to say that CEEPIPI could not be found. Check that the
DFHRPL concatenation contains the Language
Environment SCEERUN dataset, check that CEEPIPI is
a member thereof, and is executable. If DFHAPPIS
failed, CICS trace entries are written to diagnose the
failure it found. DFHAP0002 may also have been
issued.
Modules: DFHAPLH (DFHAPLH1)
AJH1
Explanation: The call to CEEPIPI to initialize the PIPI
environment failed.
used.
User Response: The PIPI return and reason codes are
captured in a CICS trace entry, and are explained in the
Language Environment Programmers Guide (SC28-1939).
AJH2 * Abend code AJH2 modified by MPU MEKF

userid(HPVG)
Explanation: CICS was unable to load HPJDLL, which
is needed to run Java Program Objects.
used.
User Response: Messages DFHAP1219 and
DFHAP1220 accompany this abend. Check the action
for those messages. Check that the DFHRPL
concatenation contains a dataset with the Visual Age
for Java Enterprise Toolkit runtime code, that there is a
member HPJDLL, and that it is executable. Check that
there is an RDO program definition for HPJDLL, or
that Program Autoinstall is active.
Modules: DFHAPLH (DFHAPH8)
AJH3
Explanation: CICS could not find in HPJDLL the
exported functions needed to run Java Program
Objects.
used.
for those messages. Check that the level of HPJDLL in
the Visual Age for Java Enterprise Toolkit runtime is
sufficient to support Hotpooling.
AJH4
Explanation: CICS called HPJDLL to initialize the Java
environment but HPJDLL returned a null environment
handle.
used.
AJH5
Explanation: CICS called HPJDLL to obtain a handle
to the Java Program Object services, but HPJDLL
returned a null handle.
used.
AJH8
Explanation: CICS called HPJDLL to load the
application�s Java Program Object and obtain the main
class name, but HPJDLL returned a null main class
name.
for those messages. HPJDLL normally throws a Java
Exception, which is diagnosed with a message and Java
Stack Trace on the CESE destination.
Check that the application program is a Java Program
Object. Only Java Program Objects can be invoked
directly under Hotpooling.
Check that the Java Program Object was made with a
level of the Visual Age for Java Enterprise Toolkit
ByteCode Binder which supports Hotpooling.
The program cannot be used in Hotpooling, but might
be usable with NotHotpool. Use CEMT or CEDA to
turn Hotpooling off and try the application again.
AJH9
Explanation: CICS called HPJDLL to run the main
class of the application�s Java Program Object. On
return to CICS, a Java Exception remained unhandled.
User Response: Message DFHAP1223 accompanies
this abend and gives the main class name. HPJDLL
describes the exception with a message and Java Stack
Trace on the CESE destination. The application must be
changed, either to avoid throwing the exception, or to
catch it and handle it before returning.
AJHA
Explanation: The CEEPIPI call DFHAPH8 to initialize
the Java environment failed.
AJHB
Explanation: The CEEPIPI call DFHAPH8 to load the
application�s Java Program Object failed.
AJHC
Explanation: The CEEPIPI call DFHAPH8 to run the
main class of the application�s Java Program Object
failed.
AJHD
Explanation: CICS found that the transaction had
been purged during a request to a CICS service.
User Response: Check that the task was cancelled by
the CICS operator.
Modules: DFHAPLH (DFHAPPIS)
AJHE
Explanation: After executing a program, storage or
transient data request, CICS failed to restablish the task
on its application TCB. The TCB was not used for
anything else during the request, and should have been
available.
Modules: DFHAPLH (DFHAPPIS)
AJHF
Explanation: The call to CEEPIPI to terminate the PIPI
environment failed.
AJMB
Explanation: The CICS-JVM interface has rejected an
attempt to invoke a Java program to run under control
of a JVM because a previous JVM for the same CICS
task terminated abnormally. The CICS-JVM interface is
unable to create a JVM to run the Java program.
This error occurs when the previous JVM was
terminated because of a Java program invoking the
Java system.exit method and because errors occurred
during the subsequent JVM termination. A system.exit
invocation causes a forced termination of the JVM and
the LE/370 runtime environment.
User Response: Examine why the previous JVM
termination failed. Wherever possible avoid the use of
system.exit to return from Java programs.
Module: DFHAPLJ
AJ01
Explanation: The main method of the Java
environment setup class, Wrapper, has been invoked
without an an argument. Wrapper main expects the
class name of the user�s main to be passed as the first
argument.
The callUserClass method of Wrapper detects this, sets
return code INVALID_ARGUMENTS and invokes
native method SetAbend to abend the task.
Module: DFJCICS
AJ02
Explanation: A CICS AbendError has been caught by
the Java environment setup class, Wrapper.
return code ABEND_RECEIVED and invokes native
method SetAbend to abend the task.
User Response: See related messages to determine the
reason for the original abend.
Module: DFJCICS
AJ03
Explanation: A CicsConditionException has been
caught by the Java environment setup class, Wrapper.
return code CONDITION_RECEIVED and invokes
native method SetAbendForCondition to abend the
task. The appropriate default abend code for the
condition should be issued but, if for some reason this
is not possible, an AJ03 abend may be issued.
reason for the original CicsConditionException.
Module: DFJCICS
AJ04
Explanation: An unexpected error has been caught by
the Java environment setup class, Wrapper, attempting
to invoke the user class.
return code UNEXPECTED_EXCEPTION and invokes
native method SetAbend to abend the task.
Module: DFJCICS
AJ05
Explanation: An unhandled exception has been caught
by the Java environment setup class, Wrapper, as an
InvocationTargetException from the user class.
return code INVOCATION_TARGET_EXCEPTION and
invokes native method setAbend to abend the task.

reason for the original Exception.
Module: DFJCICS
AJ07
Explanation: The Java environment setup class,
Wrapper, has been unable to invoke the user�s main
method. The class whose name was passed as an input
parameter to its CallUserClass method was not found.
User Response: If your Java program has been bound
using ET/390, check that the -main option correctly
specifies, or defaults to, the name of the class
containing your main method.
Module: DFJCICS
AJ09
Wrapper, has been unable to invoke the user�s main
method. A public static method, taking either a
CommAreaHolder or a String array as input, was not
found in the class whose name was passed as an input
parameter to the CallUserClass method of Wrapper.
User Response: Check that you have provided a main
method, with an appropriate method signature, in the
specified class. If your Java program has been bound
using ET/390, check that the -main option correctly
specifies, or defaults to, the name of the class
containing your main method.
Module: DFJCICS
AJ10
Wrapper, has detected that the user�s class has used
JDBC or SQLJ. It however has been unable to load the
DB2 JDBC classes necessary to call back the JDBC/SQL
driver for cleanup processing following completion of
the user class.
Module: DFJCICS
AJ11
JDBC or SQLJ. It however has been unable to find the
DB2 JDBC static method to call back the JDBC/SQL
the user class.
Module: DFJCICS
AJ12
JDBC or SQLJ. It however has been unable to invoke
the DB2 JDBC static method to call back the JDBC/SQL
the user class.
Module: DFJCICS
AJ99
Wrapper, has detected an AbendException and issued
setAbend. The abend code extracted from the
AbendException is too long.
System Action: Task abnormal termination continues
with the abend code set to AJ99
User Response: Correct the abend code String used to
create the AbendException.
Module: DFJCICS
Abend codes AKxx
AKCB
Explanation: The CICS transaction manager restart
task could not complete because a necessary step failed.
The task has done some essential recovery operations
and abnormally terminated itself with code AKCB.
System Action: CICS writes a transaction dump for
the transaction manager restart task.
CICS sends three messages to the console, one to
identify the error detected by the transaction manager
restart task, one to say that the task has failed, and one
that gives you the option of cancelling CICS or letting
it continue. Depending on the nature of the original
error, you may see messages from some other system
component (for example, an access method).
User Response: Use the messages and dumps to find
out the cause of the failure.
Module: DFHKCRP
AKCC
Explanation: The CICS transaction manager has
abended the transaction because the purge threshold of
its TRANCLASS has been reached. This is specified by
the PURGETHRESH parameter on CEDA DEFINE
TRANCLASS. See the CICS Resource Definition Guide
manual for more details of this parameter.
System Action: The transaction is abended and
messages DFHAC2004 and DFHAC2236 are issued. The
transaction dump is suppressed for this abend code.
User Response: Resubmit the transaction. The cause
of the abend may be a temporary stress condition in
the system.
If the problem persists, determine why the
TRANCLASS purge threshold has been reached. Ensure
that PURGETHRESH has been specified correctly. Also,
ensure that the MAXACTIVE value of the TRANCLASS
has not been set too low. Transactions attached after the
MAXACTIVE limit has been reached are immediately
queued subject to the PURGETHRESH limit.
If PURGETHRESH and MAXACTIVE are set correctly,
look for a more general problem which has caused a
decrease in the capacity of the system to execute
transactions in the TRANCLASS. The decrease might,
for example, be caused by a connected CICS region
which processes requests for transactions in the
TRANCLASS, if this connected region has slowed
down.
Examine all resources (files, links, storage, and so on)
used by the transactions in the TRANCLASS which is
reaching the purge threshold and determine why the
capacity of the system is reduced.
Modules: DFHXMAT, DFHXMCL
AKCE
Explanation: While CICS transaction manager was
recording changes to a transaction or profile definition,
a write to the system log failed.
System Action: CICS terminates the transaction with a
transaction dump.
User Response: Use the dumps to find out why the
write to the log failed.
Module: DFHKCQ
AKCF
Explanation: While CICS transaction manager was
recording changes to a profile definition, a write to the
catalog failed.
transaction dump.
User Response: Use the dumps to find out why the
write to the catalog failed.
Module: DFHKCQ
AKCR
Explanation: Transaction manager has received an
invalid request code. The last AP F000 trace entry
before the program control program (PCP) ABEND
TRACE entry (TRACE ID �F2�, request code X�6000�)
will contain the invalid transaction manager request
code in the fifth byte of the first section of the trace.
User Response: Determine the cause of the invalid
request code and correct the problem.
Module: DFHXCP
AKCS
Explanation: A deadlock timeout condition has been
detected. This condition may occur within a transaction
that specifies DTIMOUT to be nonzero on its installed
transaction definition. Deadlock timeout occurs when a
transaction has been waiting or has been suspended for
longer than the time specified in DTIMOUT.
The abend may be driven by a variety of internal CICS
events, for example:
v A short on storage condition
v A temporary storage shortage
v ENQUEUE
v An ALLOCATE request
v A RETRIEVE WAIT request.
The abend can also occur if CICS stops running for a
time, for example while an sdump is taken. This is
because deadlock timeout is based on total elapsed

time, and not just the time CICS is executing.
Analysis: The transaction receiving the AKCS abend
must have been suspended or must be waiting for a
reason such as a short on storage, enqueued on a lock,
a short on temporary storage, a suspend after
RETRIEVE WAIT, a suspend after ALLOCATE, or an
implicit ALLOCATE within function shipping or
terminal sharing support. If none of these apply, the
trace might reveal some event that has caused CICS to
stop running for a time.
terminated. A dump is not provided (even if a dump
table entry has been set up) unless install/delete
processing causes this abend, in which case a
transaction dump is taken.
User Response: The transaction should be reexecuted,
and the situation causing the SUSPEND to occur may
clear itself.
The AKCS abend is to be expected occasionally, unless
DTIMOUT is set to zero. No special action is necessary.
Module: DFHXCP
AKCT
Explanation: A terminal read-time-out condition has
been detected. The transaction has been waiting for a
terminal input message for an interval longer than
specified in the RTIMOUT value for that transaction.
If an EXEC CICS HANDLE ABEND has been issued for
this task, the read that was timed-out is still
outstanding. To cancel this read you should issue an
EXEC CICS ABEND at the end of the user exit routine
so that CICS can clean up the terminal�s TCTTE.
terminated. A transaction dump is not provided.
User Response: This abend is a normal one. Coding
RTIMOUT in the PROFILE entry asks for the task to be
abnormally terminated if the terminal does not send
input within the specified time.
Module: DFHXCP
AKCV
Explanation: A bad return code was passed as a result
of the resume of a task suspended by ICP.
System Action: The transaction is terminated with a
dump.
User Response: Check the response from the resume
in the trace to determine the cause of the error.
Module: DFHALP
AKC0
Explanation: An attempt has been made to run the
CICS internal task CSSY as a user transaction.
System Action: CICS terminates the task with a
transaction dump.
User Response: Investigate why the attempt was
made to run CSSY as a user transaction.
Module: DFHAPATT
AKC1
Explanation: A DFHKC WAIT request was issued
when the ECB was already marked as waiting.
System Action: There is a probable user error. The
transaction is abnormally terminated.
User Response: Correct the program that issued the
request.
Module: DFHXCP
AKC2
Explanation: A bad response has been received from a
dispatcher (DS) domain call.
terminated with a transaction dump and a trace entry.
User Response: Examine the trace entry for further
information.
Module: DFHXCP
AKC3
Explanation: The task has been purged, probably due
to operator action such as a CEMT TASK PURGE
command. The task might also have been purged as a
result of CICS issuing a purge request.
determine why the task was purged. In particular, if
the purge was operator initiated, the dump should be
useful in determining why this task needed to be
explicitly purged.
Modules: DFHXCP, DFHXMAT, DFHXMCL,
DFHXMIQ, DFHXMTA
AKC6
Explanation: DFHKC RESUME should always be
preceded by DFHKC SUSPEND. If this protocol is
violated then the transaction is abnormally terminated
with abend code AKC6.
System Action: Transaction is abnormally terminated
with abend code AKC6.
User Response: Examine the trace entry for further
information.
Module: DFHXCP
AKC8
Explanation: A bad response has been received from a
call to the kernel (KE) domain during the processing of
a task purge request.
System Action: The transaction is abended with a
transaction dump.
User Response: Examine the dump and any exception
trace entries for further information.
Module: DFHXCP
AKC9
Explanation: An incorrect response has been received
from a call to the enqueue (NQ) domain during the
processing of a DFHKC TYPE=ENQ or a DFHKC
TYPE=DEQ request.
User Response: Examine the dump and any exception
trace entries for further information. Since the DFHKC
service is only used for internal enqueues, this abend
indicates an error in CICS. You need further assistance
to proceed.
Module: DFHXCP
AKEA
Explanation: A program check has been detected by
the kernel (KE) domain.
System Action: If an application is in control, the
ASRA abend is presented to the application. Otherwise,

the functional recovery routine of the CICS module in
control at the time is given control. This recovery
routine produces suitable diagnostics and may
terminate CICS.
User Response: Look at the kernel domain section of
the system dump to determine where the program
check has occurred.
Module: DFHKESTX
AKEB
Explanation: An operating system abend has been
detected by the kernel (KE) domain.
ASRB abend is presented to the application. Otherwise,

terminate CICS.
User Response: Check the console for any MVS
messages that may have caused this abend.
Look at the kernel domain section of the system dump
to determine where the abend has occurred.
Module: DFHKESTX
AKEC
Explanation: The kernel (KE) domain has detected
runaway.
AICA abend is presented to the application. Otherwise,

terminate CICS.
the system dump to determine where the runaway has
occurred.
Modules: DFHKESTX, DFHKERRU
AKED
Explanation: The kernel (KE) domain has been
requested to initiate abend processing as a result of a
deferred abend request.
System Action: Abend processing starts for the task
that is subject to the deferred abend request.
User Response: The task is not abended with AKED
but by an abend code specified by the requestor of the
deferred abend. See the description of this abend for
further guidance.
Module: DFHKEEDA
AKEF
Explanation: The kernel (KE) domain has detected an
error while processing a domain call. The error may
have been caused by a domain gate that was not yet
active during initialization
transaction terminates with a system dump. Otherwise,
terminate CICS.
User Response: See any related messages from the
kernel domain.
Look at the kernel domain section of the system dump
to determine where the error has occurred. Check that
a call has not been made to a domain gate that has not
yet been made active. Check that the caller has NOT
specified KERNERROR(YES).
Module: DFHKERKE
AKEG
Explanation: The kernel (KE) domain issued an SM
GETMAIN for kernel stack storage, but the GETMAIN
request failed.
transaction terminates with a system dump. Otherwise,
terminate CICS.
the system dump to determine why sufficient storage
was not available.
If the short-on-storage condition persists, consider
increasing the size limit of the CICS DSA. You can vary
the DSA dynamically using the DSALIM parameter on
the CEMT master terminal command.
Module: DFHKESGM
AKEH
Explanation: The transaction was purged while
running outside the control of CICS.
System Action: CICS terminates the transaction
abnormally.
The EXEC CICS HANDLE ABEND command can not
handle this abend.
User Response: Investigate the reason the transaction
was purged.
Module: DFHKESTX
AKEI
Explanation: The kernel (KE) domain has detected
runaway while the transaction is running outside the
control of CICS.
AICA abend is presented to the application. Otherwise,

the functional recovery routine of the CICS module
which was last in control at the time of runaway
detection is given control. This recovery routine
produces suitable diagnostics and may terminate CICS.
The EXEC CICS HANDLE ABEND command can not
handle this abend.
User Response: See the CICS Problem Determination
Guide for guidance on dealing with loops.
Module: DFHKESTX
AKEZ
Explanation: A user attach has failed because there are
insufficient kernel tasks available. This indicates an
System Action: Message DFHKE0001 is issued and a
system dump is taken. The attach of the user
transaction fails.
Module: DFHKETA
AKSE
Explanation: A user has generated an addition to the
keyword table, but code has not been added to process
this keyword.
terminated and a dump is taken.
User Response: Add code to process the keyword.
Module: DFH99KC
Abend codes ALxx
ALGA
Explanation: An error has occurred obtaining a lock
within the log manager domain.
System Action: The recovery routine of the module in
control is invoked which issues message DFHLG0002
with a system dump. DFHLG0002 reports the module
in control at the time of the error.
User Response: See the description of message
DFHLG0002 for further guidance.
Modules: DFHLGGL, DFHLGJN, DFHLGLD,
DFHLGST
ALGB
Explanation: An error has occurred releasing a lock
within the log manager domain.
DFHLGST
ALGC
Explanation: A disaster response has been detected
when processing the building block code used by the
log manager.
DFHLGST
ALGD
Explanation: A disaster response has been detected
when processing the building block storage interface
code used by the log manager.
Modules: DFHLGCM, DFHLGGL, DFHLGJN,
DFHLGLD, DFHLGST
ALGE
Explanation: An unexpected error has occurred while
the log manager was attempting to find a journal
model definition.
Module: DFHLGJN
ALGF
Explanation: An unexpected error occurred when the
log manager was attempting an enqueue or dequeue
operation.
Modules: DFHLGGL, DFHLGJN, DFHLGST
ALGG
Explanation: Transaction CSQC has been issued from
a terminal. This is not permitted. The transaction can
only be started internally by CICS.
terminated.
User Response: Do not try to invoke CSQC from a
terminal.
Module: DFHLGQC
ALIA
Explanation: CICS has issued a GETMAIN request
during the initialization phase for an OS/VS COBOL
application program in order to get run time storage
for the task global table and working storage areas.
However insufficient storage was available to satisfy
the request.
System Action: CICS abnormally terminates the task.
Storage Manager domain where the original error was

detected.
Module: DFHAPLI
ALIB
during the initialization phase for a C/370 application
program in order to obtain run time execution storage.
the request.
detected.
Module: DFHAPLI
ALIC
during the initialization phase for an LE/370
application program in order to obtain run time
execution storage above the 31-bit line. However
insufficient storage was available to satisfy the request.
detected.
Module: DFHAPLI
ALID
application program in order to obtain run time
execution storage below the 31-bit line. However
detected.
Module: DFHAPLI
ALIE
during the initialization phase for a C/370 application
program in order to obtain thread storage. However
detected.
Module: DFHAPLI
ALIF
application program in order to obtain thread storage.
the request.
detected.
Module: DFHAPLI
ALIG
Explanation: CICS has been unable to determine the
language of the user application program about to be
executed. Either the program was compiled against an
old level of compiler that is no longer supported by
CICS, or the language of the program is not supported
by CICS.
and disables the program. CICS processing continues.
User Response: Ensure that the program to be run is
written in one of the languages and compiled against a
level of compiler supported by CICS. See the CICS
Application Programming Guide for details of the
languages and compilers currently supported.
Module: DFHAPLI
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
AMI1
Explanation: When the mirror task is resumed, a bad
response other than a time out or a cancellation was
given by the dispatcher.
System Action: The mirror transaction is abnormally
User Response: Use the dump and the trace to
determine the cause of the error.
Module: DFHMIRS
AMNA
Explanation: An exception response has been received
from the monitoring (MN) domain while processing a
user event monitoring point (EMP) request. The
exception response is produced when the 4-byte
DATA1 field in the user parameter contains an invalid
address.
determine why the DATA1 value passed to the
monitoring (MN) domain was invalid.
Module: DFHCMP
AMNB
Explanation: An exception response has been received
from the monitoring (MN) domain whilst processing a
user event monitoring point (EMP) request. The
exception response is produced when the 4-byte
DATA2 field in the user parameter contains invalid
data.
determine why the DATA2 value passed to the
monitoring (MN) domain was invalid.
Module: DFHCMP
AMNZ
Explanation: An unexpected error response has been
received from the monitoring (MN) domain while
processing a user event monitoring point (EMP)
request.
User Response: This indicates a possible error in CICS
code. An earlier CICS message is issued from the
monitoring domain. Follow the user response for that
message.
Module: DFHCMP
AMSA
Explanation: An input data stream received from a
3270 begins with a set buffer address (SBA) order but is
not followed by two 1-byte address fields. This is
probably due to a hardware error.
User Response: It may be possible to bypass the
problem by entering two spaces before the data to be
entered.
If the problem persists, you need further assistance.
Module: DFHMSP
AMSB
in module DFHMSP.
User Response: Retry the CMSG transaction,
specifying operands in a different order. If this fails,
keep the dump and contact your IBM Support Center.
Module: DFHMSP
AMSC
trace.
transaction.
Module: DFHMSP
AMSD
User Response: See the related error message

produced by the domain that detected the original
error.
Module: DFHMSP
Abend codes ANxx
ANQA
within the enqueue domain.
control is invoked which issues message DFHNQ0002
with a system dump. DFHNQ0002 reports the module
DFHNQ0002 for further guidance.
Modules: DFHNQED, DFHNQIB, DFHNQNQ,
DFHNQST
ANQB
within the enqueue domain.
control is invoked. This routine issues message
DFHNQ0002 with a system dump. DFHNQ0002 reports
the module in control at the time of the error.
Modules: DFHNQED, DFHNQIB, DFHNQNQ,
DFHNQST
ANQC
Explanation: An error has occurred obtaining a
sysplex enqueue. The limit for the number of
concurrent sysplex resource ENQ requests has been
reached.
System Action: Module DFHNQED issues message
DFHNQ0103 and the task issuing the EXEC ENQ
request is abended.
Module: DFHNQED
ANQD
Explanation: An error has occurred obtaining a
sysplex enqueue. An unexpected environmental error
has been detected.
System Action: Module DFHNQED issues message
request is abended.
Module: DFHNQED
ANQE
Explanation: An EXEC ENQ has been issued on a
resource for which the enqmodel is either disabled or
in the waiting state.
System Action: Module DFHNQRN issues message
request is abended.
Module: DFHNQRN
ANSA An error has occurred obtaining the

numberspace lock within the AP domain.
control is invoked which issues message DFHAP0002
with a system dump. DFHAP0002 reports the module
DFHAP0002 for further guidance.
Module: DFHBRNS
ANSB
within the AP domain.
control is invoked which issues message DFHAP0002
with a system dump. DFHAP0002 reports the module
DFHAP0002 for further guidance.
Module: DFHBRNS
Abend codes AOxx
AOTA
Explanation: The OT domain resynchronization
transaction CJTR has been started in an incorrect
manner (for example, from a user terminal, or by a
start request). This is not permitted.
User Response: None. The OT domain
resynchronization transaction must be started internally
by CICS.
Module: DFHOTR
AOTB
Explanation: An unexpected error was encountered by
the OT domain resynchronization transaction CJTR.
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
Module: DFHOTR
Abend codes APxx
APCF
Explanation: A CICS task has invoked a program
which was defined as PL/I, but the program was not
compiled with a supported PL/I compiler.
System Action: CICS terminates the task, and disables
the program.
User Response: Check that the program is PL/I. If the
program is PL/I, recompile it with the PL/I optimizing
compiler; you may need to change the source program.
If the program is not PL/I, redefine it correctly.
Module: DFHAPLI
APCG
Explanation: The transaction was purged either by
master terminal actions or due to deadlock timeout
actions as part of a request to the loader for a usable
program copy. Deadlock timeout could be caused by a
program whose size exceeds the available space in the
DSAs or EDSAs.
transaction dump.
User Response: Use the dump to investigate why the
transaction was purged. This may be due to waiting for
loader resources or for program storage. Check the
program size. It may be necessary to increase the
overall size limits of the DSAs or EDSAs.
Modules: DFHACP, DFHCRNP, DFHCRSP,
DFHDBCT, DFHDBDSC, DFHEDFP, DFHEIP,
DFHEICRE, DFHEIDEF, DFHEIDEL, DFHEIINS,
DFHEIPSH, DFHEIQIR, DFHEIQSJ, DFHFCRP,
DFHFEP, DFHICP, DFHKCQ, DFHMCP, DFHMCPE,
DFHMCY, DFHMSP, DFHPCPG, DFHPHP, DFHPSIP,
DFHPUP, DFHRDCAL, DFHRTC, DFHSII1, DFHSIJ1,
DFHSPP, DFHSTP, DFHTACP, DFHTBSGB, DFHTCRP,
DFHTDX, DFHTFP, DFHTSPA, DFHTSRP, DFHUSBP,
DFHXRCP, DFHXRE, DFHXRSP, DFHZATA,
DFHZATD, DFHZCPLN, DFHZGAI, DFHZQ00,
DFHZNCA, DFHZOPA, DFHZXCU
APCH
Explanation: A request for a VS COBOL II program
could not be executed because a problem has occurred
during system initialization for VS COBOL II. This is
probably due to the absence of VS COBOL II or
Language Environment support.
terminated and the program is disabled.
User Response: Redefine the program or ensure that
the correct Language Environment or VS COBOL II
support is present.
Module: DFHAPLI
APCI
Explanation: A request for a PL/I program could not
be executed because execution of PL/I programs has
been disabled.
User Response: Ensure that the PL/I libraries are
included in DFHRPL.
Module: DFHAPLI
APCJ
Explanation: A request for a C program could not be
executed either because C/370 was unable to recognize
the program as having been compiled under the C/370
Compiler, or because the program was not link-edited
with the attribute AMODE(31).

User Response: Ensure that the program is correctly
defined to CICS; or, if necessary, recompile the program
using the current level of the C/370 Compiler.
Module: DFHAPLI
APCK
Explanation: A request for a C program could not be
honored; execution of C programs has been disabled
either because CICS was unable to load the required
C/370 support module EDCCICS, or because C/370
initialization failed. This abend may be accompanied by
message DFHFC0410.
System Action: The transaction is terminated
abnormally and the program is disabled.
User Response: Refer to the explanation for message
DFHFC0410 and, in particular, check that C/370 has
been installed correctly.
Module: DFHAPLI
APCL
Explanation: An attempt to run the program failed
because Language Environment was unable to
determine its language.
User Response: Ensure that the program is correctly
defined to CICS.
Module: DFHAPLI
APCN
Explanation: An attempt to release an internal CICS
program, a mapset, or a partitionset because the
program, mapset or partitionset has not been loaded or
has already been deleted. This is probably an internal
CICS error.
terminated with a CICS transaction dump. The name of
the program for which the RELEASE was attempted
can be found in the abend dump at TCAPCPI.
User Response: This is either an internal CICS error
or is due to the overwriting of CICS internal control
blocks. You need further assistance from IBM to resolve
this problem. See Part 4 of the CICS Problem
Modules: DFHAMPEN, DFHFEP, DFHMCP,
DFHMCPE, DFHMCY, DFHPHP, DFHTBSSP,
DFHZCPLN
APCO
Explanation: A GETMAIN of storage for LEVEL 2
trace failed during transaction initialization.
Module: DFHAPXM
APCS
because CICS was unable to make a successful
connection with Language Environment to determine
the run-time characteristics of the program. This abend
is accompanied by message DFHAP1200 which gives
the reason code set by Language Environment
indicating the nature of the error.
User Response: Refer to the Language Environment
Debugging Guide and Runtime Messages manual for the
meaning of the reason code, and take whatever action
is necessary to correct the error.
Module: DFHAPLI
APCT
Explanation: One of the following has occurred:
1. The program name in the EXEC CICS HANDLE
ABEND program is not usable at the time an abend

occurs because:
v The program is not on the relocatable program
library (RPL).
2. An attempt to load a mapset or partitionset failed
because although the program is defined to CICS
v It is not available on the RPL, or
v It is disabled, or
v It cannot be autoinstalled.
3. An attempt to link to, load, or release an internal
CICS program failed because:
v The program is not on the RPL.
Problem Determination: The trace preceding the
abend indicates the program, mapset, or partitionset
that could not be loaded, linked to, or released. The
name is also in TCAPCEPI.
System Action: The transaction requiring the program
is abnormally terminated with a CICS transaction
dump.
User Response: In cases 1 and 2, define the program,
mapset partitionset to CICS using CEDA and ensure it
is enabled.
In case 3, the definition of a CICS-provided module is
incorrect. Check for associated messages issued during
CICS start up.
Modules: DFHACP, DFHAMPEN, DFHCRSP,
DFHEDFP, DFHEIP, DFHEICRE, DFHEIDEF,
DFHEIDEL, DFHEIINS, DFHEIPSH, DFHEIQSJ,
DFHFEP, DFHICP, DFHMCP, DFHMCPE, DFHMCY,
DFHMELDE, DFHPCPG, DFHPHP, DFHPUP,
DFHRDCAL, DFHSII1, DFHTBSGB, DFHTFP,
DFHTSRP, DFHZCPLN, DFHZQ00, DFHZXCU
APCW
Explanation: The program language is defined as
COBOL but the level of the compiler under which it
was originally compiled cannot be determined. Most
probably, the program was compiled under an OS/VS
COBOL II compiler but the required level of support
for that compiler is not present in the system.
User Response: Check that OS/VS, COBOL II or
Language Environment support is present in the
system and that the required interface modules
(IGZECIC or CEECCICS) have been correctly loaded
during system startup.
Module: DFHAPLI
APCY
Explanation: In an MVS/ESA environment, a CICS
macro request has been issued from a PL/I or COBOL
application. Alternatively, it is possible that the
application program has been link edited without the
EXEC interface module (for example, DFHECI or
DFHELII) which is used by the CICS high-level
language programming interface. See the CICS System
Definition Guide for details of what has to be done to
include this module.
User Response: Remove the macro request from the
application program.
Module: DFHAPLI
APCZ
Explanation: An attempt has been made to run either
an �old-style� application program (that is, a program
with a pre-release 1.6 or a DFHE program stub) or an
OS/VS COBOL program, either having been link-edited
with the RENT or REFR attributes. These types of
programs are not reentrant and therefore cannot be
loaded into read-only storage.
terminated.
User Response: Relink the program without the RENT
and REFR attributes.
Module: DFHAPLI
APC0
Explanation: A serious error occurred in a call to the
program manager domain when trying to link a system
program.
transaction dump.
User Response: Use the dump to investigate why the
error occurred. Look at the trace records prior to the
error for abnormal conditions in processing the PGLK
domain call. This may be due to a problem with
directory manager, loader, or storage manager. Check
the program size. It may be necessary to increase the
overall size limits of the DSAs or EDSAs.
Modules: DFHEICRE, DFHEIDEF, DFHEIDEL,
DFHEIINS, DFHPCP, DFHMCY
APC1
Explanation: A request for a TGT exceeding 64KB has
been detected.
transaction and disables the installed program
definition.
User Response: Change the application program to
reduce the working storage requirement. Perform
CEMT NEWCOPY and ENABLE for the program when
it has been corrected.
Module: DFHAPLI
APC2
Explanation: An illegal branch has been attempted by
a Language Environment user program following an
abend condition with an active handle label abend.
Usually an Out-Of-Block GOTO will have resulted,
implying that the program tried to branch to, for
example, an inactive block.
User Response: Use the dump and trace to determine
the cause of the error and amend the GOTO in error.
Module: DFHAPLI
APC3
because the program appeared to be defined to CICS as
Language Environment but no Language Environment
support was present in the system and no other
language environment was able to run the program.
User Response: Redefine the program to CICS in a
language other than Language Environment.
Module: DFHAPLI
APC4
Explanation: A call to the loader domain to define
program ILBOCOM failed.
terminated.
User Response: Check that the library containing the
OS/VS COBOL runtime library modules is named in
the DFHRPL DD concatenation.
Module: DFHPCPC2
APC5
Explanation: A call to the loader domain to load
program ILBOCOM failed.
terminated.
User Response: Check that the library containing the
OS/VS COBOL runtime library modules is included in
the DFHRPL concatenation. If it is, obtain and check a
trace of the failure. If no reasonable explanation is
found (such as lack of storage), you will need further
proceed.
Module: DFHPCPC2
APC6
Explanation: An internal error has occurred.
terminated.
User Response: See the associated X�F230� Exception
trace entry for further diagnostic information. For an
ACQUIRE error ensure the associated module is in a

library in the CICS DFHRPL concatenation. For an
IDENTIFY error make sure that the associated module
has not been MVS LOADed for example by the
inadvertent link-editing of a VS COBOL II program
with a COBOL subprogram.
Module: DFHPCPC2
APC7
Explanation: An MVS IDENTIFY call has given a non
zero return code. The IDENTIFY call was being used to
make the entry point ILBOCOM0 known to MVS.
terminated.
Module: DFHPCPC2
APC8
Explanation: An MVS LOAD of ILBOCOM0 has given
a non zero return code.
terminated.
User Response: Ensure the library containing the
OS/VS COBOL runtime modules is available to
STEPLIB.
Module: DFHPCPC2
APC9
Explanation: An MVS LOAD of ILBOCOM has given
a non zero return code.
terminated.
User Response: Ensure the library containing the
OS/VS COBOL runtime modules is available to
STEPLIB.
Module: DFHPCPC2
APLx
Explanation: Abend codes with �PL� as the middle two
characters are issued by PL/I, and are described in
further detail in the OS PL/I Optimizing Compiler:
Programmer�s Guide.
APP1
Explanation: The DFHIC TYPE=GET response code
was not a normal response.
is in the low-order byte of register 0.
Module: DFHP3270
APP2
Explanation: The length of data that has been passed
to DFHP3270 via temporary storage is less than or
equal to 5.
Problem Determination: Register 6 points to the data
retrieved from temporary storage via a DFHIC
TYPE=GET macro invocation. The layout of this data is:
v Terminal data area length (2 bytes)
v Write control indicator (1 byte)
v Write control or carriage control character (1 byte)
v Data (variable length)
Analysis: DFHP3270 has been called to handle a print
request from a 3270 Information Display System
terminal. It obtains from temporary storage the data to
be printed, via a DFHIC TYPE=GET invocation. It
ensures that some data to be printed is present. The
area returned from temporary storage contains the data
to be printed preceded by 4 bytes as described above.
DFHP3270 has found that, because the length of data
passed to it is less than or equal to 5, there is no data
to be printed.
User Response: Check the user DFHTEP. If it is not at
fault, submit an APAR.
If this abend has occurred, the data that DFHP3270
obtained from temporary storage was probably put
there with an incorrect length. The user may have
requested indirectly that this data be placed in
temporary storage either by an application request for
printing (for example ISSUE PRINT) or by pressing the
Print Request key. However, CICS should control the
data length for this request. Under normal
circumstances, the only way the user could have
requested directly that data is to be placed in
temporary storage is in the user�s TEP. The user should
check any invocations of DFHIC TYPE=PUT in
handling print requests, particularly when dealing with
the �printer unavailable or busy� condition, and ensure
that the length field is set correctly.
Module: DFHP3270
APP3
Explanation: An attempt to request data has been sent
to a nonprinter or unsupported device type by either:
v A terminal operator entering CSPP as a transaction
code, or
v A transaction issuing a DFHTEP request.
terminated. A CICS transaction dump is not provided.
User Response:
1. Ensure that the terminal operator ceases to use
CSPP as a transaction code, or
2. Correct the user DFHTEP program.
Module: DFHP3270
APR1
Explanation: An abnormal DFHIC TYPE=PUT
response code was received during print key
processing.
operation.
is in low-order byte of register 0.
Module: DFHPRK
APSJ
Explanation: The abending transaction invoked the
system spooler initialization program (DFHPSIP)
illegally, that is from a program other than the CICS
module, DFHSIJ1.
abnormally. The EXEC CICS HANDLE ABEND
command can not handle this abend.
User Response: Remove any calls or links to DFHPSIP
from your application programs. If you can find no
invocation of DFHPSIP in your application, you need
further assistance to resolve this problem. You need
Module: DFHPSIP
APST
Explanation: A task issued a SPOOL command
without the mandatory NOHANDLE operand.
with a dump.
User Response: Correct the syntax of the command,
specifying NOHANDLE.
Module: DFHEPS
APSU
Explanation: The CICS SVC passed an invalid JES
interface return code to the CICS system spooler (an
MVS subtask).
User Response: This is an internal error � check any
JES failures that occurred at the same time.

Module: DFHPSPST
APSV
Explanation: A storage area for VSAM macro return
codes contained an invalid value.
with a dump.
User Response: Check the syntax and input data of
the spool commands issued by the failing transaction.
Check any JES failures that occurred at the same time.
Module: DFHPSPST
APSW
Explanation: An abend occurred within a CICS system
spooler subtask.
with a dump.
User Response: This is an internal CICS error. You
Module: DFHPSPST
APSX
Explanation: A CICS storage area used for notification
of invalid parameters contained an invalid value.
with a dump.
Module: DFHPSPST
APSY
Explanation: A CICS storage area for MVS macro
return codes contained an invalid value.
with a dump.
Module: DFHPSPST
APSZ
Explanation: A CICS area, used to store a JES interface
return code, contained an invalid value.
with a dump.
This is an internal CICS error. You need further
on how to proceed.
Module: DFHPSPST
APTI
the purged condition will have provided an exception
trace.
Module: DFHPSPST
APTJ
the dump table).
Module: DFHPSPST
APUA
Explanation: An internal error was detected when
module DFHPUP was invoked. The GETSTG parameter
is missing on a call to DFHPUP (PUPF).
System Action:
dump.
Module: DFHPUP
APUB
module DFHPUP was invoked. The GETSTG parameter
is missing on a call to DFHPUP (PUPU).
System Action:
dump.
Module: DFHPUP
APUC
module DFHPUP was invoked. An invalid function
code was supplied for a domain call to DFHPUP.
System Action:
dump.
Module: DFHPUP
APUD
Explanation: The RDO language definition table
(DFHEITSP) could not be located in the library.
System Action:
dump.
User Response: Ensure that module DFHEITSP is in
the library and is valid for this release of CICS.
Module: DFHPUP
APUE
Explanation: The RDO language definition table
(DFHEITSP) could not be loaded because of a lack of
available storage.
System Action: Processing is abnormally terminated
with an operating system dump.
User Response: Allocate more storage and resubmit
the offline COPY or APPEND command(s) that failed.
Modules: DFHPUP (Batch environment)
APUF
Explanation: Either the RDO language definition table
is invalid or it is missing from the library.
System Action:
dump.
User Response: Ensure that module DFHEITSP is in
the library and is valid for this release of CICS.
Module: DFHPUP
APUG
Explanation: An internal error was detected in
module DFHPUP. Storage could not be obtained for the
CSD record buffer.
System Action:
dump.
Module: DFHPUP
APUH
module DFHPUP. Storage could not be obtained for the
argument list.
System Action:
dump.
Module: DFHPUP
APUI
module DFHPUP. Storage cannot be freed for the
argument list.
System Action:
dump.
Module: DFHPUP
APUJ
module DFHPUP. Storage cannot be freed for the CSD
record buffer.
System Action:
dump.
Module: DFHPUP
APUK
Explanation:
v In a CICS environment, storage could not be
acquired for a buffer to contain logged RDO
commands in the CEDA transaction.
v In a batch environment, storage could not be
acquired for a buffer to contain back-translated
resource definitions from the CSD.
System Action:
dump.
Module: DFHPUP
APUL
Explanation:
APUM, APUN and APUO.

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 DFHPUP
operation that was invoked before the error occurred:
Abend DFHPUP operation
APUL FLATTEN
APUM TRANCASE
APUN COMPARE
APUO BACKTRANS
The cause of the abend is either:
1. A language definition table (DFHEITSP or
DFHEITCU) in the library is invalid for the CICS
release you are running, or
2. A CICS logic error has occurred.
System Action:
dump.
User Response: Your response depends on which of
the two possible reasons apply:
1. Ensure that the DFHEITSP and DFHEITCU
modules in the library are valid for this release of
CICS.
2. 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: DFHPUP
APUM
Explanation: Refer to the description of abend APUL.
Module: DFHPUP
APUN
Module: DFHPUP
APUO
Module: DFHPUP
APUP
Explanation: An internal error occurred in DFHPUP
processing of the language definition table for RDO.
There was a stack error building a keyword list for the
syntax tree.
System Action:
dump.
Module: DFHPUP
APUQ
processing of the language definition table for RDO.
Too many keywords found in syntax expansion.
System Action:
dump.
Module: DFHPUP
APUR
processing of an argument list or a CSD record buffer.
The data type for a keyword field conflicts with the
data type specified in the language definition table.
System Action:
dump.
User Response: Ensure that the module DFHEITSP is
Module: DFHPUP
APUS
processing of a CSD record buffer. The integer data
length for a keyword field is invalid.
System Action:
dump.
Module: DFHPUP
APUT
processing of an argument list or a CSD record buffer.
The keyword existence bit number, which is the KEP(1)
value in language definition table DFHEITSP, is not
valid.
System Action:
dump.
Module: DFHPUP
.*---------------------------------------------------------------
APUZ
Explanation: CICS has found an unrecognized
resource type code in a CSD record. The unrecognized
code does not match any of the function codes in the
language definition table. This abend can occur for one
of the following reasons:
1. You are using a CICS release that does not support
a type of definition that was created on the CSD file
by a later CICS release.
2. The language definition table (DFHEITSP or
DFHEITCU) is invalid for this CICS release.
3. The CSD manager (DFHDMP) has passed an

invalid CSD record buffer to DFHPUP. This is a
CICS internal logic error.
System Action:
dump
User Response: Determine which of the possible
reasons caused the error. If you can eliminate reasons 1
and 2, you can assume that reason 3 applies.
Take action corresponding to the reason you have
established as follows:
1. Avoid operations on groups containing
definition-types that are unsupported by the CICS
release you are running.
2. Ensure that the library contains versions of
DFHEITSP and DFHEITCU that are valid for the
CICS release you are running.
3. 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: DFHPUP
APXA
Explanation: The user transaction�s profile could not
be found.
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: DFHAPXM
Abend codes ARxx
ARCB
Explanation: CICS has attempted to enable a
task-related user exit, or a global user exit during
initialization, but failed because the exit program could
not be found.
On all types of start, CICS attempts to enable DFHEDP,
the EXEC DLI task-related user exit. On an emergency
restart, CICS enables transaction backout exit programs
as specified by the first two TBEXITS system
initialization parameters.
On all types of start, CICS attempts to enable file
control backout programs as specified by the third,
fourth, fifth and sixth TBEXITS system initialization
parameters.
System Action: CICS issues a message to the console
indicating which exit program is involved. CICS
initialization then terminates abnormally with a system
dump.
User Response: If the associated message indicates
that program DFHEDP could not be found, check that
IBM-supplied group DFHEDP is included in the group
list used at CICS cold or initial start time.
For transaction backout exit programs, including the
file control backout programs, ensure the program has
been defined and is in a library available to CICS.
If necessary, use the dump to find out why the exit
program could not be enabled.
Module: DFHRCEX
ARHA
Explanation: The SAA resource recovery interface 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.
Module: DFHCPIR
ARHB
been invoked with an invalid number of parameters for
the call.
System Action: the transaction is abnormally
User Response: The exception trace point produced
with this abend contains the SAA resource recovery
verb name that was issued incorrectly. Use this to
determine where the application program was in error
and amend application program accordingly. The SAA
Resource Recovery Reference Manual, SC31-6821, provides
a detailed description of the SAA resource recovery
verbs and how they should be called.
Module: DFHCPIR
ARHC
detected an unexpected return code from the syncpoint
program. This is a CICS internal logic error.
Module: DFHCPIR
ARM0
transaction specifying DFHRMXN3 as the program to
be given control, but the transaction was not internally
attached by CICS.
DFHRMXN3 is for use by CICS system transaction
CSKP. This provides support for activity keypoints,
to attach CSKP incorrectly, or why a transaction
definition specified DFHRMXN3 as the program to be
given control.
Module: DFHRMXN3
ARPA
Explanation: An unexpected response from DFHSUSN
has occurred when trying to sign off a user of the
CRTE transaction in the target system when processing
a CANCEL request.
This abend can be caused by incorrect use of the VTAM
VARY INACT command. Otherwise it indicates that
there may be an error in CICS.
System Action: The CSSF transaction (CRTE cancel
processor transaction) is terminated with an ARPA
abend.
User Response: Ensure that the VTAM VARY inact
command is used correctly. If this is not the cause of
the abend, you need further assistance from IBM to
correct this problem. You need further assistance from
proceed.
Module: DFHRTC
ARPF
Explanation: The alias could not be initialized.
System Action: One of the following messages is
issued: DFHRP0103, DFHRP0104, DFHRP0106,
DFHRP0108, DFHRP0109.
User Response: See the user response for the message.
Module: DFHRPAS
ARPG
Explanation: The alias was not able to link to the
CICS program or the Encode function of the converter
one of the following reasons:
v The userid supplied for the alias was not valid.
v The CICS program is not defined as a resource to the
external security manager.
v The CICS program name is not valid.
v The CICS program was on a different system from
CICS ONC RPC, and the specified system name was
not valid.
v The converter program name was not valid.
v The converter program is defined as remote.
v The alias is not authorized to use the converter
DFHRP0139, DFHRP0141, DFHRP0156, DFHRP0157,
DFHRP0159.
Module: DFHRPAS
ARPH
Explanation: The alias detected a global work area
error.
System Action: The following message is issued:
DFHRP0118.
Module: DFHRPAS
ARPI
Explanation: The alias detected a logic error.
DFHRP0170.
Module: DFHRPAS
ARPJ
Explanation: The alias ends for one of the following
reasons:
v An unexpected response was received from CICS
during transaction initialization.
v The external security manager is no longer available.
v The remote CICS region in which the CICS program
was running abended.
v The CICS program, which was running in a remote
CICS region, abended.
v The reply could not be sent to the client.
DFHRP0150, DFHRP0165, DFHRP0166, DFHRP0167.
Module: DFHRPAS
ARPK
Explanation: The alias detected a CICS logic error.
DFHRP0160.
Module: DFHRPAS
ARPL
Explanation: The alias detected an authorization error.
DFHRP0134.
Module: DFHRPAS
ARPM
Explanation: The alias detected an error in user code.
DFHRP0169.
Module: DFHRPAS
ARPN
Explanation: The alias detected an error while trying
to switch TCBs.
DFHRP0151.
Module: DFHRPAS
ARPO
Explanation: The alias program detected an abend.
issued: DFHRP0181, DFHRP0182, DFHRP0183.
Module: DFHRPAS
ARPU
Explanation: The connection manager could not access
the CICS ONC RPC data set, and received an error
response when it tried to send message DFHRP1512.
System Action: None.
to resolve this problem. See the CICS External Interfaces
Guide and Part 4 of the CICS Problem Determination
Module: DFHRPC01
ARPV
Explanation: The connection manager received an
unexpected response from CICS following an EXEC
CICS command.
issued: DFHRP1540, DFHRP1651, DFHRP1954.
Module: DFHRPC0E
ARPW
Explanation: The connection manager received an
unexpected response from CICS following an EXEC
CICS command.
DFHRP1969.
Module: DFHRPC0E
ARPX
Explanation: The connection manager was started
against an invalid terminal.
DFHRP1522.
Module: DFHRPC01
ARPZ
Explanation: The connection manager has insufficient
authority.
DFHRP1902.
Module: DFHRPC0B
ARP2
Explanation: The server controller detected an internal
error during CICS ONC RPC enable processing.
DFHRP0529, DFHRP0590, DFHRP0591.
Module: DFHRPMS
ARP4
Explanation: The server controller has performed an
exception disable because of an internal error.
DFHRP0726, DFHRP0728, DFHRP0730, DFHRP0741.
Module: DFHRPMS
ARP5
Explanation: An invalid attempt was made to start the
server controller.
DFHRP0640.
Module: DFHRPMS
ARP9
Explanation: There was not enough storage for the
connection manager.
System Action: None.
Module: DFHRPC01
ARTA
Explanation: The task does not own a terminal as its
principal facility.
User Response: Ensure that DFHRTE has not been
specified as the program for a task other than CRTE.
Ensure that CRTE has not been initiated by means
other than terminal input.
Module: DFHRTE
ARTB
Explanation: There is no input TIOA or the data
length is zero.
User Response: Ensure that DFHRTE has not been
specified as the program for a task other than CRTE.
Ensure that CRTE has not been initiated by means
other than terminal input.
Module: DFHRTE
ARTC
Explanation: The link to the required system is not
usable for an unknown reason.
Module: DFHRTE
ARTD
Explanation: An internal logic error has been detected.
Module: DFHRTE
ARTE
Explanation: An error was encountered when
attempting to read from or write to temporary storage.
User Response: Determine the cause of the temporary
storage problem and correct it.
Module: DFHRTE
ARTF
routing transaction (CRTE) from a terminal that has a
permanent transaction code set.
Module: DFHRTE
ARTG
Explanation: CICS could not find the profile specified
for a transaction being routed.
with a dump.
User Response: Check your transaction and profile
definitions.
Module: DFHRTE
ARTH
schedule a remote terminal delete by DFHRTE during
the dump table).
with a dump.
Module: DFHRTE
ARUA
Explanation: An exception condition was returned on
the ADD_LINK during the BIND phase of ATTACH for
the transaction invoked by the RUN command.
System Action: CICS terminates the invoked
transaction abnormally with a dump. The RUN
SYNCHRONOUS command that was issued by the
application returns with an error response of INVREQ
(RESP2 2Cool.
User Response: More details can be found in the
trace.
Module: DFHXMRU
ARUB
Explanation: A RUN SYNCHRONOUS command
caused an attempt to attach a transaction defined as
remote. Only transactions defined as local may be run
synchronously.
application returns with an error response of
ACTIVITYERR or PROCESSERR (RESP2 27).

trace.
Module: DFHXMXM
ARUC
Explanation: A RUN SYNCHRONOUS command
caused an attempt to attach a transaction with an
invalid USERID.
application returns with a resp2 value of 27.
trace.
Module: DFHXMRU
ARXA
Explanation: A transactional EXCI request has been
received from a batch region. CICS has encountered an
error when attempting to express interest in an RRMS
Unit of Recovery.
DFHRXUW provides an exception trace, console
message DFHRX0002, and possibly a system dump
User Response: Resource Recovery Services (RRS)
may have been shut down after the request was
received by CICS. If this is the case, retry the EXCI
request once RRS has been restarted.
If this is not the case, use the exception trace provided
by the RX domain to determine the reason for the
failure. You might need further assistance from IBM in
this situation. You need further assistance from IBM to
Module: DFHRXUW
ARXB
an ADD_LINK call to the recovery manager (RM)
in the dump table).
For all errors, DFHRXUW provides an exception trace,
console message DFHRX0002, and possibly a system
Module: DFHRXUW
ARXC
Explanation: A transactional EXCI request has been
received from a batch region when either:
v CICS did not register as a resource manager with
Recoverable Resource Management Services (RRMS)
because system initialization parameter RRMS=NO
was specified.
v the RX domain did not succesfully complete its
initialization.
User Response: If CICS was started with system
initialization parameter RRMS=NO, restart CICS
specifying RRMS=YES (or route transactional EXCI
requests to another CICS system).
Otherwise, investigate why the RX domain did not
initialize succesfully. A failure during initialization of
the domain is accompanied by a console message and a
system dump. You need further assistance from IBM to
Module: DFHRXUW
ARZE
terminated with abend code ARZE. CICS takes a
loaded.
programmer.
Modules: DFHRZLN, DFHRZRM, DFHRZSO,
DFHRZSO1, DFHRZTA, DFHRZXM
ARZF
terminated with abend code ARZF. CICS takes a
loaded.
programmer.
ARZI
terminated with abend code ARZI. CICS takes a
loaded.
programmer.
ARZJ
terminated with abend code ARZJ. CICS takes a
loaded.
programmer.
ARZ2
Explanation: An attempt to service a GIOP request
failed during task attach due to required resources
being unobtainable, or missing information from
request data.
System Action: The request fails and the task is
abnormally terminated with abend code ARZ2. CICS
takes a transaction dump, unless module DFHDUIO is
not loaded.
programmer.
Module: DFHRZXM
ARZ3
request data.
not loaded.
programmer.
Modules: DFHRZIX, DFHRZTCX
ARZ4
request data.
not loaded.
programmer.
Modules: DFHRZRM, DFHRZSO1
Abend codes ASxx
ASCA
Explanation: A DFHSC TYPE=GETMAIN request has
resulted in a call to the storage manager (SM) domain
which has returned an INVALID or DISASTER
response.
User Response: There has been an earlier failure
which led to the response from the storage manager
domain. Investigate the earlier failure (which is
accompanied by a console message and a system
dump).
Module: DFHSMSCP
ASCB
Explanation: A DFHSC TYPE=FREEMAIN request has
resulted in a call to the storage manager (SM) domain
which has returned an INVALID or DISASTER
response.
which led to the response from the storage manager
domain. Investigate the earlier failure (which is
accompanied by a console message and a system
dump).
Module: DFHSMSCP
ASCP
Explanation: A task which has issued an
unconditional DFHSC TYPE=GETMAIN request has
been purged while waiting for sufficient contiguous
main storage to become free.
This will either have been 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
If the task was purged by the master terminal operator
then this may have been in an attempt to clear the
system which appeared to be deadlocked for some
reason.
the DTIMOUT value being exceeded then this may be
due to insufficient main storage being available for the
Module: DFHSMSCP
ASCR
Explanation: A DFHSC macro request has been issued
with an invalid request type.
Detection of the invalid request by DFHSMSCP causes
a console message and a system dump to be produced.
User Response: Use the associated console message
and system dump to investigate the problem.
Module: DFHSMSCP
ASDA
Explanation: The default shutdown transaction
(CESD) has been started directly from a terminal. This
is not permitted. This transaction can only be started
internally by CICS.
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
ASFA
Explanation: An internal logic error occurred in
DFHSFP because of an unexpected response from
EXEC CICS. This abend code is usually accompanied
by message DFHCE3598 which contains the associated
return codes.
Module: DFHSFP
ASFB
Explanation: An attempt was made to execute the
CICS signoff program without an associated terminal.
dump. This abend code is usually accompanied by
message DFHCE3598.
User Response: Only use the signoff program when
there is a related terminal.
Module: DFHSFP
ASFC
Explanation: An attempt was made to execute the
CICS signoff program against an APPC session.
message DFHCE3598.
User Response: Only use the signoff program when
Module: DFHSFP
ASHA
terminated with abend code ASHA. CICS takes a
loaded.
programmer.
Module: DFHSHDM
ASHB
terminated with abend code ASHB. CICS takes a
loaded.
programmer.
Module: DFHSHDM
ASHR
terminated with abend code ASHR. CICS takes a
loaded.
programmer.
Module: DFHSHRSP
ASHU
Explanation: In the process of transferring the request
from one region to another an abend occurred due to a
routing failure. The Request cannot be routed to a
suitable region. The request is unserviceable.
terminated with abend code ASHU. CICS takes a
loaded.
User Response: Check the links between regions are
available. Check the Distributed Routing Program name
is correct and the program is usable. 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.
Module: DFHSHRSP
ASH2
Explanation: An attempt to service a Scheduler
Services request failed due to required resources being
unobtainable. This may result in a request being
unserviceable or an Activity being marked abended
depending on the nature of the failure.
terminated with abend code ASH2. CICS takes a
loaded.
User Response: Check that any required links
between regions are available. Check the Distributed
Routing Program name is correct and the program is
usable. 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.
Module: DFHSHXM
ASH3
Explanation: A transaction bound to a Scheduler
Services request has backed out. No other abend code
has been set. The SH abend request uses this abend
code by default.
System Action: The transaction continues backing out.
A subsequent task will process the SH abend request.
Module: DFHSHRM
ASH4
Explanation: A Scheduler Services request attempted
to attach a transaction that is currently disabled.
terminated with abend code ASH4. CICS takes a
loaded.
User Response: Check the status of the transaction.
For further assistance, or if module DFHDUIO is not
loaded and no transaction dump is available, contact
your system programmer.
Module: DFHSHXM
ASIA
Explanation: An error has occurred on a call to the
storage manager (SM) domain. The domain that
detected the original error will have provided an
the dump table).
with a CICS transaction dump. CICS then terminates
abnormally.
Module: DFHSII1
ASIB
CICS internal task CPLT as a user transaction.
transaction dump.
made to run CPLT as a user transaction.
Module: DFHSIPLT
ASJD
Explanation: An attempt to load a DLL by SJ Domain
has failed.
transaction dump.
User Response: See message DFHSJ0503 to determine
the DLL name and the reason why the load failed.
Module: DFHSJCS
ASJE
Explanation: An attempt to locate the Wrapper class
has failed.
transaction dump.
User Response: Verify the location and attributes of
the CICS Wrapper class. See message DFHSJ0501 for
further information.
Module: DFHSJCS
ASJF
Explanation: An attempt to change the HFS working
directory has failed.
transaction dump.
User Response: See message DFHSJ0502 to determine
the directory name and the reason why the attempt
failed.
Module: DFHSJCS
ASJG
Explanation: An attempt by SJ domain to fetch the
user-replaceable module DFHJVMAT has failed.
transaction dump.
User Response: Verify that module DFHJVMAT is
contained in a dataset referenced by ddname
SDFHAUTH and that it is executable.
Module: DFHSJIN
ASJ1
Explanation: CICS attempted to initialize the Java
environment for a task by issuing a JNI_CreateJavaVM
call to the Java Native Interface. The call was not
successful.
System Action: Exception trace SJ 050C is created. The
dump.
User Response: Examine the HFS files used for stdout
and stderr (as named by the environment variables
STDOUT and STDERR, whose default names are
dfhjvmout and dfhjvmerr) for error messages output by
the JVM. Also examine destination CEEMSG for error
messages output by Language Environment and the
Java Native Interface (JNI). The trace table from the
transaction dump contains the exception trace
mentioned above.
Module: DFHSJCS
ASJ3
Explanation: The CICS JVM interface invoked the
JVM to find the main method of the CICS Wrapper
class used to set up the operating environment before
executing the user Java class. The JVM failed to find
the main method of the CICS Wrapper class.
System Action: DFHSJCS provides an exception trace,
console message DFHSJ0002, and possibly a system
transaction dump.
Java Native Interface (JNI).
Module: DFHSJCS
ASJ4
Explanation: The SJ domain failed to build the
argument list required to invoke the CICS Wrapper
class used to set up the operating environment before
executing the user Java class. This is possibly due to
lack of free storage.
System Action: DFHSJCS provides an exception trace,
console message DFHSJ0002, and possibly a system
transaction dump.
Module: DFHSJCS
ASJ5
Explanation: The CICS JVM interface invoked the
CICS Wrapper class used to set up the operating
environment before executing the user Java class. The
Wrapper returned an exception.
Module: DFHSJCS
ASJ6
Explanation: The SJ domain issued a call to the kernel
to ensure that CICS�s ESTAE is the current ESTAE. This
is required before calling CICS services from a native C
environment which is running with LE�s ESTAE in
effect. The call failed.
User Response: Examine the CICS Kernel or MVS
messages and diagnostics that should be present as a
result of the failure.
Module: DFHSJCS
ASNA
Explanation: An internal logic error occurred in
DFHSNP because of an unexpected response from
EXEC CICS.
message DFHCE3548.
Module: DFHSNP
ASNB
Explanation: An attempt was made execute the CICS
sign on program without an associated terminal. This
abend code is usually accompanied by message
DFHCE3548.
dump.
User Response: Only use the sign on program when
Module: DFHSNP
ASNC
Explanation: The signon program attempted to send a
request to the user but failed to do so.
message DFHCE3548.
Module: DFHSNP
ASND
Explanation: A request from DFHSNTU to ENQ on
the address of the SNEX has failed during signoff
terminal user.
System Action: A transaction dump is taken and the
task which issued the signoff is abended.
Module: DFHSNTU
ASOA
Explanation: The TCP/IP listener task CSOL has been
incorrectly started from a terminal. It can only be
enabled by the Sockets Domain at CICS system
initialization or by using CEMT SET TCPIP OPEN or
the equivalent SPI function.
Module: DFHSOL
ASOB
Explanation: The TCP/IP listener task CSOL has
encountered a locking error while attempting to issue a
lock.
User Response: The exception trace prior to this
abend gives more information as to why this abend
was issued.
Module: DFHSOL
ASOC
encountered an unlocking error while attempting to
issue an unlock.
User Response: The exception trace prior to this
abend gives more information as to why this abend
was issued.
Module: DFHSOL
ASOL
abended.
User Response: Investigate why the transaction was
abended. The exception trace prior to this abend gives
more information as to why this abend was issued.
Module: DFHSOL
ASPA
recovery manager (RM) domain was able to complete
condition provides an exception trace.
with a CICS transaction dump. If processing is at a
point where data integrity might not be maintained,
CICS is abnormally terminated.
transaction.
If CICS is abnormally terminated, it should be
emergency restarted to ensure that data integrity is
maintained.
Module: DFHAPAC
ASPB
the dump table).
with a CICS transaction dump. If processing is at a
point where data integrity might not be maintained,
CICS is abnormally terminated.
domain that detected the original error. If CICS was
abnormally terminated, it should be emergency
restarted to ensure that data integrity is maintained.
Module: DFHAPAC
ASPC
Explanation: An error (INVALID or DISASTER) has
occurred on a call to the bridge syncpoint routine
(DFHBRSP). The domain that detected the original
error will have provided an exception trace, and,
possibly, a system dump (depending on the options
Module: DFHSPP
ASPD
Explanation: The transaction requested syncpoint via
EXEC CICS SYNCPOINT, or rollback via EXEC CICS
SYNCPOINT ROLLBACK, but this is not allowed in a
transaction that is associated with an OTS transaction.
abnormally. EXEC CICS HANDLE ABEND command
cannot handle this abend.
User Response: The error indicates an invalid attempt
to syncpoint the transaction.
If DB2 is being accessed in the transaction, check that
the DB2ENTRY or DB2CONN pool definition used by
the transaction does not specify DROLLBACK(YES).
Module: DFHEISP
ASPF
Explanation: CICS issued an internal syncpoint
request resulting in a syncpoint with an intersystem
session which has returned ROLLEDBACK to recovery
manager (RM) domain. As a result, the transaction is
abnormally terminated because the unit of work which
was being syncpointed has been backed out.
This could result from shutting down IRC or from the
failure of a connected CICS region.
terminated. Recoverable resources updated by the unit
of work are backed out and locks released. The EXEC
CICS HANDLE ABEND command cannot handle this
abend.
Message DFHAC2215 is sent to the terminal end user if
possible, and message DFHAC2245 is sent to transient
data destination CSMT.
User Response: Determine why the remote
intersystem session returned a ROLLEDBACK response
to the syncpoint request. Once this has been corrected
retry the transaction.
To avoid ASPF abends in future, ensure that no
in-flight units of work exist before shutting down IRC.
Module: DFHAPAC
ASPI
Explanation: During CICS synchronization level 1
(synclevel 1) commit, an unexpected FMH or no data
has been received from the partner system. Local
resources and synclevel 2 partners have been
committed, but synclevel 1 function-shipped resource
updates may have been backed out.
System Action: The transaction does not abend. CICS
synclevel 1 commit processing continues, with the aim
of committing as many synclevel 1 resources as
possible.
determine why the FMH was invalid or missing, It is
likely that the error is in the remote system.
See the CICS Family: Communicating from CICS on
System/390 for more information about syncpointing.
Module: DFHCR2U
ASPJ
Explanation: During CICS synchronization level 1
(synclevel 1) commit, unexpected syncpoint message
data has been received from the partner system. Local
resources and synclevel 2 partners have been
committed, but synclevel 1 function-shipped resource
updates may have been backed out.
System Action: The transaction does not abend. CICS
synclevel 1 commit processing continues, with the aim
of committing as many synclevel 1 resources as
possible.
determine why the message data was invalid. It is
likely that the error is in the remote system.
See the CICS Family: Communicating from CICS on
System/390 for more information about syncpointing.
Module: DFHCR2U
ASPN
Explanation: A transaction has issued an EXEC CICS
RETURN in backout required program state. The
backout required program state is set when an
application receives or issues an abend, or receives a
backout request on a protected conversation.
abend.
User Response: To avoid the transaction abend, the
application should code an EXEC CICS SYNCPOINT
command before the EXEC CICS RETURN. A syncpoint
issued in �backout required� program state results in a
backout being performed, and the ROLLEDBACK
condition returned on the EXEC CICS SYNCPOINT
command. If this condition is then handled, a
subsequent EXEC CICS RETURN will complete
successfully. For LU61 conversations the application
should issue an EXEC CICS FREE followed by an
EXEC CICS SYNCPOINT ROLLBACK, in order to
avoid a subsequent ASP8 abend.
Module: DFHAPAC
ASPO
Explanation: An intersystem session failed while a
syncpoint was being taken. The intersystem session that
failed was the link to the coordinator system. The
failure occurred during the indoubt period of syncpoint
processing. As a result this CICS system is in doubt as
to the outcome of the unit of work for the transaction.
The unit of work is not shunted to await the return of
the coordinator system, but is instead unilaterally
committed. The unit of work is not shunted for one of
the following reasons:
v The transaction definition specifies WAIT(NO).
v The unit of work includes an MRO session to a
back-level CICS system which does not support the
WAIT(YES) option, and the role of the session in the
unit of work is such that it cannot await the return of
the coordinator system.
v The unit of work includes an LU6.1 session, and the
role of the session in the unit of work is such that it
cannot await the return of the coordinator system.
v The unit of work involves a task related user exit
which is not enabled with the INDOUBTWAIT
option.
v The unit of work has updated a recoverable transient
data destination, which is defined with WAIT(NO).
v The unit of work involves the installation of CICS
resource definitions from the CSD (CICS system
definition) file.
The unit of work is committed, rather than backed out,
because the transaction definition specifies
ACTION(COMMIT).
The fact that the unit of work is committed is
remembered by the recovery manager (RM) domain
until the unit of work is resynchronized with the
coordinator system. At this time, according to whether
the coordinator system committed or backed out, the
recovery manager domain issues resynchronization
messages reporting whether or not the resolution of the
unit of work in the subordinate system was consistent
with the coordinator system.
of work are committed and locks released. The EXEC
abend.
User Response: Any updates performed by the unit of
work are committed. There is a danger that recoverable
resources will be inconsistent with the coordinator
system if the coordinator system has backed out. If the
reason for the failure is the first of those listed above
and if you wish CICS to ensure that data integrity is
maintained, change the indoubt transaction definition
to specify WAIT(YES) so that CICS automatically
handles indoubt failures and resynchronizes the unit of
work when the link to the coordinator system is
reestablished.
Module: DFHAPAC
ASPP
Explanation: An intersystem session failed while a
syncpoint was being taken. The intersystem session that
failed was the link to the coordinator system, and the
failure occurred during the critical indoubt period of
syncpoint processing. As a result this CICS system is in
doubt as to the outcome of the unit of work for the
transaction.
The unit of work is not shunted to await the return of
the coordinator system. Instead it is unilaterally backed
out. The unit of work is not shunted for one of the
following reasons:
v The transaction definition specifies WAIT(NO).
v The unit of work includes an MRO session to a
back-level CICS system which does not support the
WAIT(YES) option, and the role of the session in the
unit of work is such that it cannot await the return of
the coordinator system.
v The unit of work includes an LU6.1 session, and the
role of the session in the unit of work is such that it
cannot await the return of the coordinator system.
v The unit of work involves a task related user exit
which is not enabled with the INDOUBTWAIT
option.
v The unit of work has updated a recoverable transient
data destination, which is defined with WAIT(NO).
v The unit of work involves the installation of CICS
resource definitions from the CSD (CICS system
definition) file.
The unit of work is backed out, rather than committed,
because the transaction definition specifies
ACTION(BACKOUT).
The fact that the unit of work is backed out is
remembered by recovery manager (RM) domain until
the unit of work is resynchronized with the coordinator
system. At this time, according to whether the
coordinator system backed out or committed, the
recovery manager domain issues resynchronization
messages reporting whether or not the resolution of the
unit of work in the subordinate system was consistent
with the coordinator system.
abend.
User Response: Any updates performed by the unit of
work are backed out. There is a danger that recoverable
resources will be inconsistent with the coordinator
system if the coordinator system has committed. If the
reason for the failure is the first of those listed above
and if you wish CICS to ensure that data integrity is
maintained, change the indoubt transaction definition
to specify WAIT(YES) so that CICS automatically
handles indoubt failures and resynchronizes the unit of
work when the link to the coordinator system is
reestablished.
Module: DFHAPAC
ASPQ
Explanation: During phase 2 of the two phase
syncpoint protocol an error occurred while
communicating with a remote system. The error
occurred after the recoverable resources were
committed or backed out, so data integrity is not in
danger.
of work will have backed out or committed depending
on the decision taken by the recovery manager (RM)
domain, which was not influenced by this later
problem. The EXEC CICS HANDLE ABEND command
User Response: Refer to earlier messages issued by
the communication or remote resource management
components of CICS to determine the cause of the
intersystem communication problem.
Module: DFHAPAC
ASPR
Explanation: Intersystem communication failed while
a syncpoint was being taken. Communication with the
coordinator system has been interrupted, and the

doubt as to the outcome of the unit of work for the
transaction.
However, this CICS system has not updated any
recoverable resources in the unit of work and hence
does not require the unit of work to be shunted to
await resynchronization of its resources later. The
coordinator system commits or backs out its resources.
No resources on this system need to be kept in step.
This error can occur with external resource managers
connected to CICS via the resource manager interface
(RMI) as well as CICS systems connected via LU 6.2,
and MRO. If an external resource manager such as DB2
is the only recoverable resource updated in the
transaction, the recovery manager (RM) domain can
optimize the syncpoint protocol. In this instance, the
external resource manager becomes the syncpoint
coordinator. If the link to the external resource manager
is lost during this time, CICS will be indoubt as to
whether the external resource manager updates were
committed or backed out.
terminated. There are no recoverable resources affected
in this CICS system. The EXEC CICS HANDLE ABEND
command cannot handle this abend.
User Response: Refer to messages on the remote
system to determine if the remote resources were
backed out or committed.
Module: DFHAPAC
ASP1
Explanation: Intersystem communication failed while
a syncpoint was being taken. Communication with the
coordinator system has been interrupted, and the
doubt about the outcome of the unit of work for the
transaction.
Alternatively, a transaction may have timed out while
waiting for Recoverable Resource Management Services
(RRMS) to provide the outcome of the unit of work, or
RRMS may have failed during the critical indoubt
period.
The transaction definition specifies WAIT(YES) as an
indoubt attribute. Therefore the unit of work is not
completed but is shunted and allowed to wait for
resynchronization with the coordinator system. If the
WAITTIME attribute is specified on the transaction
definition, the unit of work waits for the specified time.
If after that time the coordinator system has not
resynchronized, a unilateral decision is made about the
unit of work as specified by the ACTION keyword on
the transaction definition. A WAITTIME of zero, the
default, means an indefinite wait. The unit of work can
also be forced to take a unilateral decision by means of
a CEMT SET UOW command.
terminated. The EXEC CICS HANDLE ABEND
The associated unit of work is shunted awaiting the
return of the coordinator system. Recoverable resources
updated by the unit of work remain locked. The locks
are released when the unit of work is backed out or
committed at resynchronization time, or when a
unilateral decision is made by this system.
User Response: None. Any updates performed by the
unit of work are resolved automatically when
resynchronization with the coordinator system takes
place.
Alternatively, the user can force resolution of the
updates independently of the coordinator system by
making a CEMT request to commit or back out the unit
of work.
Module: DFHAPAC o*---------- ABCODE ASP2
ALTERED BY APAR PQ47569 ----------------
ASP2
Explanation: A syncpoint has been attempted when
an intersystem conversation is in a state in which the
EXEC CICS SYNCPOINT command is not allowed. If
CICS is connected to a system which must act as LAST
AGENT, such as IMS, then this ABEND will be issued

from SYNCPOINT processing if a PREPARE has been
received on a link to another system. In order to
support syncpointing CICS must act as
COORDINATOR when it is directly connected to the
LAST AGENT, the COORDINATOR system may send
PREPARE syncpoint commands but never receives
them.
with a CICS transaction dump which includes terminal
control information. In particular, the dump contains
state information for the links used by this transaction.
handle this abend.
User Response: Ensure that the application issues an
EXEC CICS SYNCPOINT command only when its sync
level 2 conversations are in the correct state. The EXEC
CICS SYNCPOINT command may be issued only when
each conversation is in one of the following states:
SEND
PEND-RECEIVE (Not for MRO)
PEND-FREE
SYNC-RECEIVE
SYNC-SEND (Not for MRO)
SYNC-FREE
Module: DFHAPAC
ASP3
Explanation: An application has requested syncpoint,
either via EXEC CICS SYNCPOINT or implicitly via
EXEC CICS RETURN. The coordinator of the syncpoint
is not this CICS system but is remote. During the
syncpoint protocol the remote coordinator has decided
that the unit of work cannot be committed and must be
backed out.
This error can occur with external resource managers
connected to CICS via the resource manager interface
(RMI) as well as CICS systems connected via LU 6.2,
and MRO. If an external resource manager such as DB2
is the only recoverable resource updated in the
transaction, the recovery manager (RM) domain can
optimize the syncpoint protocol. In this instance, the
external resource manager becomes the syncpoint
coordinator. In this instance if the external resource
manager returns with a backed out response, an ASP3
abend results.
terminated and recoverable resources updated by the
unit of work are backed out. The EXEC CICS HANDLE
ABEND command cannot handle this abend.

User Response: Refer to the remote coordinator
system to determine why the unit of work was backed
out.
Module: DFHAPAC
ASP7
Explanation: A resource manager involved in
syncpoint protocols has replied �No� to a request to
�Prepare�. The resource manager may be local to this
CICS system, or may be a remote resource manager on
another CICS system, or an external resource manager
communicating through the resource manager interface
(RMI).
abnormally. Recoverable resources updated by the unit
of work are backed out. The EXEC CICS HANDLE
ABEND command cannot handle this abend.
If it is a local resource manager that has voted no,
message DFHAC2218 is sent to the terminal end user if
If it is a remote resource manager that has voted no,
message DFHAC2219 is sent to the terminal end user if
User Response: This abend is caused by a prior
problem. For example, the resource manager cannot
flush its buffers because of an I/O error, or it cannot
communicate with CICS because of a TP failure.
Correct the earlier problem. An ASP7 can also occur
during terminal or connection install if CICS is short on
storage. For instance if message DFHAC2248 shows the
transaction as CATA then look for earlier short on
storage messages.
Module: DFHAPAC
ASP8
Explanation: The transaction requested syncpoint
rollback, but was using a type of processing for which
syncpoint rollback is not supported.
abnormally. The EXEC CICS HANDLE ABEND
User Response: This error may be an application error
or a configuration error. Some communication sessions,
(for example, LU6.1) do not support syncpoint rollback,
and if CICS detects such a session during rollback
processing, the task is abended. This restriction is
described in the CICS Intercommunication Guide. To
resolve the problem, either:
v Change the application so that it does not issue
syncpoint rollback commands while the
non-supporting sessions are allocated (e.g. issue an
EXEC CICS FREE first), or
v Change the configuration so that either APPC or
MRO sessions are used for communication. These are
the only two session types which support syncpoint
rollback.
Alternatively, following a session failure during a
previous syncpoint, CICS may have decided to rollback
this unit-of-work in order to preserve data integrity.
Since the unit-of-work contains a session which does
not support syncpoint rollback, this abend ensues. In
this case, no action is required in response to this
abend, although action may be required to deal with
the original failure.
Module: DFHAPAC
ASP9
Explanation: The transaction requested syncpoint via
EXEC CICS SYNCPOINT, but this is not allowed in a
transaction that is acting on behalf of an Activity.
abnormally. EXEC CICS HANDLE ABEND command
to syncpoint the transaction.

Module: DFHEISP
ASQA
Explanation: The CLS2 transaction was processing
resynchronization work but the communications
session which it was using has failed.
System Action: The work is reexecuted on a new
session. If reexecution has has already been attempted,
the transaction terminates.
User Response: The error may be caused by the
failure of several sessions between communicating
systems during the resynchronization process. To
confirm this, examine the CSMT transient data queue
for the relevant period.
Another cause could be logic errors within the
resynchronization program, either on this system or on
the partner system, which caused the session to be
terminated. In this case, CSMT transient data messages
indicate the nature of the error.
Module: DFHCRRSY
ASQB
Explanation: The CLS2 transaction was executing
exchange log names or resynchronization with a remote
system when a logic error occurred.
Message DFHRS2158 may also be issued.
Module: DFHCRRSY
ASQC
Explanation: The CLS2 transaction was attached with
an unexpected start code. The transaction can be
attached due to terminal input (on a communications
session), or via a system attach. Neither of these
methods was used.
terminated.
to start the transaction.
Module: DFHCRRSY
ASQD
Explanation: The CLS2 transaction was attached but
could not use the transaction manager interface to
obtain input parameters.
terminated.
User Response: The error indicates a failure in the
transaction manager. See the exception trace entries
produced by the transaction managed to determine the
reason for the error.
Module: DFHCRRSY
ASQE
exchange log names with a remote system and 3 retry
attempts have failed to solicit a warm exchange log
names reply, in response to a warm exchange log
names request sent by CICS.
User Response: This abend indicates an error in the
remote system. It should have saved the log name sent
by CICS and, on receiving a later exchange lognames
request, should then respond with a warm reply.
Module: DFHCRRSY
ASQG
resynchronization work and has failed during the
receipt of data from remote system via an MRO
session. The data was longer than expected.
User Response: The abend indicates a CICS logic
error, possibly in the remote system. The transaction
storage in the dump shows the data received. The
transaction trace shows the preceding flows between
the systems, which should match those documented in
the SNA LU6.2 Reference: Peer Protocols manual,
SC30-6808.
Module: DFHCRRSY
ASQH
resynchronization work and has failed during the
receipt of data from remote system via an MRO
session. The data was shorter than the minimum length
expected.
System Action: The transaction is anormally
User Response: This indicates a CICS logic error,
possibly in the remote system. The transaction storage
in the dump shows the data received. You need further
on how to proceed.
Module: DFHCRRSY
ASQI
Explanation: The CLS2 transaction was executing the
exchange lognames process as part of the initialization
sequence for an APPC connection. An attempt to
invoke the CICS recovery manager to save a logname
failed.
Message DFHRS2157 may also be issued.
User Response: This indicates an error in the CICS
recovery manager which has produced its own
exception trace records. Look at the trace records and
the CSMT message log for further information about
the error.
Module: DFHCRRSY
ASQK
Explanation: The CLS2 transaction was processing
exchange lognames or resynchronization for a
connected partner identified by a netname. The
connection entry associated with the netname was
located and locked, but could not be unlocked in
subsequent processing. This indicates a CICS internal
logic error.
System Action: The transaction is abnomally
Message DFHRS2156 may also issued.
User Response: This indicates an error either in the
CICS table manager, (which may have produced its
own exception trace records) or in the
resynchronization program itself. Look at the trace
records and the CSMT message log for further
information which might have indicated an error in the
table manager program or in the table entry for the
connection. You need further assistance from IBM to
Module: DFHCRRSY
ASQL
Explanation: The CLS2 transaction was executing the
resynchronization of a unit of work with a connected
partner, and has locked the associated data managed by
the CICS recovery manager. The invocation of the
TERMINATE_RECOVERY command to unlock the data
failed.
Message DFHRS2154 is also issued.
User Response: This indicates an error either in the
CICS recovery manager (which may have produced its
own exception trace records) or in the
resynchronization program itself. Look at the trace
records and the CSMT message log for further
information. You need further assistance from IBM to
Module: DFHCRRSY
ASQM
Explanation: A CICS internal logic error has occurred
in the management of dynamic storage for the
resynchronization program.
User Response: This indicates that the
resynchronization program has exhausted the available
space for recording storage areas. The symptoms may
indicate that the program was looping without
executing the error recovery process. You need further
on how to proceed.
Module: DFHCRRSY
ASRA
Explanation: The task has terminated abnormally
because of a program check.
System Action: The task is abnormally terminated and
CICS issues either message DFHAP0001 or DFHSR0001.
Message DFHSR0622 may also be issued.
associated message or messages to determine and
correct the cause of the program check.
Module: DFHSRP
ASRB
Explanation: An operating system abend has occurred
and CICS has been able to abend the current
transaction.
CICS issues either message DFHAP0001 or DFHSR0001
associated message to determine the cause of the
original operating system abend, and take the
necessary corrective action.
Module: DFHSRP
ASRD
Explanation: The task has been abnormally terminated
for one of these reasons:
v A program contains an assembler macro call which is
no longer supported by CICS.
v An invalid attempt has been made to access the CSA
or TCA. This abend could be caused by an attempt
to address the CSA through OS/VS COBOL BLL
cells. For example:
When an OS/VS COBOL program is invoked by
CICS for MVS, CICS inserts the address of the
fetch-protected dummy CSA into the first of the
application-managed BLL cells. If an attempt is made
to access this storage before the application has
reinitialized the BLL cell, abend ASRD will occur.
v A non-assembler program has been wrongly defined
to CICS as an assembler program.
This error appears as a program check.
CICS issues message DFHSR0618, followed by either
DFHAP0001 or DFHSR0001.
associated messages to determine and correct the error.
It is likely that either R12 which usually addresses the
TCA or R13 which usually addresses the CSA is
pointing to an area of storage that you are not allowed
to access.
For more infomation about OS/VS COBOL BLL cells
and associated problems, see the CICS Problem
Determination Guide
Module: DFHSRP
ASRE
because an attempt has been made to access a
CICS-DB2 RCT load module.
The RCT nolonger exists as a load module and cannot
be accessed directly.
To access information held in the RCT use the CICS SPI
commands EXEC CICS INQUIRE/SET DB2CONN,
EXEC CICS INQUIRE/SET DB2ENTRY and EXEC
CICS INQUIRE/SET DB2TRAN.
This error appears as a program check.
CICS issues message DFHSR0619, followed by either
DFHAP0001 or DFHSR0001.
User Response: Change the application to use the
CICS SPI commands to retrieve data from, or set fields
in, the RCT.
Module: DFHSRP
ASRK
Explanation: The AP domain recovery stub, DFHSR1,
has been invoked to deal with a program check,
operating system abend, or another error within a
transaction environment. However, DFHSR1 has been
unable to call the system recovery program, DFHSRP,
because register 12, which should be pointing to the
task control area (TCA), is null. This indicates that the
caller of DFHSR1, has not set the address of the TCA..
Module: DFHSR1
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
ATCA
Explanation: The system was in a final quiesce mode
when the CICS application program issued a DFHTC
macro.
System Action: The task requesting the I/O is
Module: DFHZARQ
ATCB
Explanation: The CICS application program issued
two consecutive DFHTC writes or two consecutive
DFHTC reads, but in either case did not issue an
intervening wait.
Problem Determination: A transaction dump is
provided with this abend. In the dump, register 12
addresses the current TCA, and register 10 and the
field TCAFCAAA address the TCTTE associated with
this task. In TCATPOS2, bit TCATPOWR (X�01�)
indicates that a write is requested by the DFHTC
macro, and bit TCATPORR (X�10�) indicates that a read
is requested. In TCTTEOS, bit TCTTEOWR (X�01�)
indicates that a write is in progress, and bit TCTTEORR
(X�10�) indicates that a read is in progress.
Analysis:
R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byte
R12=@TCA (TCZAQ1W) TCATPOS2, and bit TCTTEOWR
is on in byte TCTTEOS.
R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byte
R12=@TCA (TCZAQ2W) TCATPOS2, and bit TCTTEORR
R10=@TCTTE TCZARQ12 Bit TCATPORR is on in byte
R12=@TCA TCATPOS2, and bit TCTTEORR
User Response: Take corrective action within the
program being executed.
This is almost certainly an application program error.
Determine the flow of control through the application
and determine why an intervening wait is not issued.
The trace table may be useful to discover where the
application is issuing the read and write requests. If
necessary, start trace or auxiliary trace using the master
terminal command and rerun the transaction to obtain
a trace. The output of the auxiliary trace can be printed
using the trace utility program, DFHTU620.
Module: DFHZARQ
ATCC
Explanation: An application program, using a pipeline
session, has either issued more than one write request
or issued a read request.
that it will not issue more than one consecutive WRITE
to a pipeline session terminal.
Module: DFHZARQ
ATCD
Explanation: This abend code is used whenever a
CTYPE request or a QUEUE request is issued and
VTAM or a ZCP function has not been included in the
system.
It is also used to abend a task that issues an APPC
command when the CICS system is not at a level to
support APPC.
User Response: Correct the transaction so that it does
not issue a CTYPE macro instruction if VTAM is not
generated into the system, or include the ZCP function
for which the CTYPE or QUEUE request was issued.
Modules: DFHZDSP, DFHZERH
ATCE
Explanation: A CICS application program has issued a
DFHTC request without specifying the address of a
TIOA, but the request is not an ERASE ALL
UNPROTECTED or a READBUF request for a 3270
data stream terminal.
Problem Determination: A transaction dump is
provided with this abend. In the dump, register 12
addresses the current TCA, and register 10 and the
field TCAFCAAA addresses the TCTTE associated with
this task. Register 8 and TCTTEDA should contain the
address of the TIOA to be used in the I/O request, but
actually they contain zero. For a 3270 data stream
terminal, byte TCTETDST has bit TCTETTSI (X�01�) set.
An erase-all-unprotected request is indicated by the
setting of bit TCTTEEUI (X�40�) in byte TCTTEEUB,
and a read buffer request is indicated by the setting of
bit TCTTERBI (X�80�) in byte TCTTERBB. Analysis:
R10=@TCTTE TCZARQ41 NIOABAR (register Cool
contains zero.
R8=0 Register 8 has been loaded
field TCTTEDA of the TCTTE
associated with this task.
User Response: Correct the error in the user program
by ensuring that a terminal input/output area (TIOA)
is provided at write time.
This is almost certainly an application program error.
Determine the flow of control through the application
and determine why a TIOA has not been specified.
Module: DFHZARQ
ATCF
Explanation: A DFHTC CTYPE macro was issued to a
non-VTAM terminal control table terminal entry
(TCTTE), or a DFHTC CTYPE=COMMAND or
RESPONSE macro was issued to a VTAM 3270 TCTTE.
User Response: Ensure that the program issues
CTYPE macros to VTAM terminals only, and does not
issue CTYPE=COMMAND or RESPONSE to a VTAM
3270.
Module: DFHZCRQ
ATCG
Explanation: A CICS application program has issued a
DFHTC request for a terminal that it does not own. The
problem of ownership may be because the task
previously issued a WRITE,LAST request (which would
have detached the terminal from that task) or because
the task incorrectly specified the terminal to which the
request is directed.
current TCA and register 10 contains the address of the
TCTTE. The address of the TCTTE was obtained either
from TCAFCAAA in the case of a non-ISC transaction,
or from TCATPTA if bit TCATPTTA (X�40�) is on in
byte TCATPOC3 (this indicates that TERM=YES was
specified on the DFHTC request and that this is an ISC
transaction). In the TCTTE thus located, the field
TCTTECA does not contain the address of the TCA,
indicating that this TCA is not owned by this task.
Analysis: A DFHTC request has been issued specifying
a TCTTE in which the field TCTTECA does not contain
the address of the TCA.
R10=@TCTTE TCZARQ05 TCTTECA is not equal
to register 12.
User Response: This is most probably an application
error (unless storage has been completely overwritten).
Determine the flow from the trace table and when a
request to the DFHZCP detach routine, DFHZDET, or a
DFHTC WRITE,LAST was issued.
Module: DFHZARQ
ATCH
Explanation: The task was purged before a domain
call was able to complete successfully. The task that
exception trace.
for the transaction, or by CICS issuing a purge request.
When CICS purges a task, it does so to allow an
operation to complete which would be held up by the
presence of active tasks, or to ensure data integrity. For
example, CICS will purge a task which has made
recoverable updates to a coupling facility data table if it
determines that the coupling facility data table server
for the pool in which that table resides has recycled, to
ensure that all updates in the unit of work will be
backed out.
Modules: DFHBSM62 DFHBSS DFHBSSZ DFHBSTZ
DFHBSTZV DFHBSTZ1 DFHBSTZ2 DFHTBSB
DFHTBSBP DFHTBSD DFHTBSDP DFHTBSL
DFHTBSLP DFHTBSQ DFHTBSR DFHTBSRP
DFHTBSSP DFHTCRP DFHTOASE DFHTOATM
DFHTOLCR DFHTOLUI DFHTRZCP DFHTRZIP
DFHTRZPP DFHTRZXP DFHTRZYP DFHTRZZP
DFHZCQCH DFHZCQDL DFHZCQIQ DFHZCQIS
DFHZCQRS DFHZCQ00 DFHMRXM DFH62XM
ATCI
call to module DFHRTSU. The module 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).
the module that detected the original error.
Modules: DFHZSUP DFHMRXM DFH62XM
ATCJ
Explanation: This abend is issued by DFHZATA in the
following circumstances:
v Transaction CATA is issued from a terminal
v The address of the AWE (TCAFCAAA) is 0
v The AWE is invalid (TCTWETYP should be
TCTTEAWE)
v An abend is issued early in DFHZATA.
This abend is issued by DFHZATD in the following
circumstances:
v Transaction CATD is issued from a terminal
v The address of the AWE (TCAFCAAA) is 0
v TCAFCAAA is an AWE and not a terminal
v An abend is issued early in DFHZATD.
This abend is issued by DFHZATR in the following
circumstances:
v Transaction CATR is issued from a terminal
v An abend is issued early in DFHZATD.
System Action: CICS rejects the request.
User Response: Determine the issuing program and
the reason for the abend and take the appropriate
action as follows:
Do not try to invoke CATA, CATD or CATR from a
terminal.
If the address in TCAFCAAA is incorrect, the calling
mechanism has failed. This is a CICS logic error.
If an abend has been issued, use the transaction dump
to determine where the abend occurred. This is a CICS
logic error.
Modules: DFHZATA DFHZATD DFHZATR
ATCK
Explanation: An application program has issued a
WRITE to a VTAM terminal specifying CCOMPL=NO
without being authorized to do so.
User Response: Specify CHAINCONTROL in the
transaction profile.
Module: DFHZARQ
ATCL
Explanation: An error has occurred either during
automatic journaling or automatic logging of terminal
messages to or from this transaction. The message
being logged will be one associated with an explicit
READ or WRITE in the application program.
X�8001� - WRITE
X�8003� - PUT
Analysis:
journal or log record could not be written correctly. If a
journal record length error is indicated, TIOATDL may
have been corrupted.
Modules: DFHETL, DFHTCPCM, DFHZARQ
ATCN
Explanation: An error has occurred during the
automatic journaling or automatic logging of the initial
input message of this transaction. This input message is
the message that actually caused the transaction to be
invoked.
X�8001� - WRITE
X�8003� - PUT
Analysis:
R4=@JCA TCZARQJP JCAJCRC is nonzero.
TCZSUPJW Journal error.
log record could not be written correctly.
If a journal record length error is indicated, TIOATDL
(X�08�) may have been corrupted.
Modules: DFHZSUP DFH62XM DFHTFXM
ATCO
Explanation: An application program has attempted
to perform a function not supported by a terminal or
system.
Possible errors are:
1. SIGNAL not supported.
A DFHTC TYPE=SIGNAL request with the

WAIT=YES option was issued to a VTAM logical
unit that CICS does not support for the receipt of
the SIGNAL indicator.
2. WRITE STRUCTURED FIELD not supported.
This write may have been attempted as a result of a
SEND command with the STRFIELD keyword to a
device that does not support this function.
3. APPC mapped conversation not supported.
The application has attempted to perform a normal
terminal control command on a session that is in
use for an APPC unmapped conversation. (Only
EXEC CICS GDS commands are permitted.)
User Response: Correct the application program.
Module: DFHZARQ
ATCQ
Explanation: The application program issued a write
operation to a terminal that was in send status. In
order to allow this write to proceed, a signal command
was sent, and DFHZCP started to read data from the
terminal waiting for the change direction indication. As
each data record is received, it is placed on temporary
storage and, for one of these operations, a temporary
storage error has occurred.
current TCA. TCACCSV1 contains a saved copy of
TCATSTR containing the temporary storage response
code. The temporary storage response code may be one
of:
X�04� - IOERROR - I/O error
X�08� - NOSPACE - No temporary storage space
X�20� - INVREQ - Invalid request.
The temporary storage identification is constructed by
concatenating the character string �DFHQ� with the
terminal identification from TCTTETI. The temporary
storage identification is placed in TCATSDI.
Register 8 and field TCTTEDA address the TIOA that is
being written to temporary storage. The address passed
to temporary storage is that of TIOATDL.
Analysis: After the DFHTS TYPE=PUTQ, the
temporary storage response code was not zero.
R12=@TCA ZRAQ60 TCATSTR is nonzero.
User Response: Check that temporary storage has
been included in the system and that it has sufficient
space.
If an invalid request is indicated, check that the length
of the data being written to temporary storage is not
greater than the VSAM control interval size minus 84.
The length of the data is in TIOATDL (which is 8
greater than the length of the data that is read in by
DFHZCP).
Module: DFHZRAQ
ATCR
Explanation: An application program has issued a
read operation, after a previous write operation has
caused DFHZCP to read-ahead data from the terminal
in order to avoid a lock-out. DFHZCP has now issued a
DFHTS GETQ to retrieve the saved data from
temporary storage, and an error has occurred.
current TCA. TCACCSV1 contains a saved copy of
TCATSTR that contains the temporary storage response
code. The temporary storage response code may be one
of:
X�01� - ENERROR - Entry error
X�02� - IDERROR - Identification error
X�04� - IOERROR - I/O error
The temporary storage identification is constructed by
concatenating the character string �DFHQ� with the
terminal identification from TCTTETI. The temporary
storage identification is placed in TCATSDI.
Analysis: After the DFHTS TYPE=GETQ, the
temporary storage response code was not zero.
R12=@TCA ZRAR90 TCATSTR is not zero.
User Response: Determine the cause of the temporary
storage error and correct it.
If a temporary storage identification error is indicated,
examine TCTTETI for a valid terminal identification.
Module: DFHZRAR
ATCS
Explanation: An application program attempted to
send data to a logical unit after a SIGNAL data flow
command with an RCD (request change direction) has
been received. This condition arises when the
application handles the IGREQCD exceptional
condition incorrectly.
User Response: Handle the IGREQCD exceptional
condition correctly.
Module: DFHZARQ
ATCT
Explanation: An attempt to build a surrogate TCTTE
to represent a remotely-owned terminal failed.
ATCU
Explanation: An application program attempted to
send data to a logical unit, but was in receive mode
(EIBRECV is set), and read-ahead queuing was not
specified in installed profile definition (RAQ=NO).
User Response: Either change the application program
to issue receives until EIBRECV is not set, or specify
RAQ=YES in the installed profile definition (If
RAQ=YES is specified, ensure that all input messages
are read before the transaction is terminated.)
Module: DFHZARQ
ATCV
Explanation: An application attempted an operation
on a logical unit, but was not in the correct mode for
one of the following reasons:
1. When issued by DFHZARQ, CICS cannot perform
the current request because another request is
outstanding (EIBSYNC is set). This holds for APPC
or non-APPC systems
2. When issued by DFHETL, the application is
communicating with an APPC system, and is not in
the correct state to perform the attempted operation.
This holds for APPC systems only
3. When issued by DFHZISP, a TCTTE free was
requested, and there is an outstanding sync point
request. This holds for non-APPC systems only
4. When issued by DFHZISP, a TCTTE free was
requested, the TCTTE is in receive mode, and
RAQ=NO was specified in the installed profile
definition. This holds for non-APPC systems only.
current TCA. Register 10 and field TCAFCAAA address
TCTTE. The terminal byte TCTTECRE has bit
TCTEUCOM (X�02�) set if sync point is required, and
TCTEUFRT (X�04�) set if Free Session is required;
TCTESMDI has TCTEUSMD (X�02�) set if the
application is in SEND mode. TCTERCVI has
TCTEURCV (X�01�) set if the application is in RECEIVE
mode. Bit TCTESRAQ (X�80�) in byte TCTEIRAQ
indicates that read-ahead queuing is coded on the
installed profile definition for this transaction.
The type-of-request bits in the TCA are set as follows:
v TCATPOS1 TCATPIS (X�01�) Signal requested.
� TCATPFRE (X�03�) Free TCTTE.
v TCATPOS2 TCATPORR (X�10�) Receive requested.
� TCATPOWR (X�01�) Send requested.
Analysis:
Number Label Description
DFHZARQ
1. TCZAQW8 Attempting to receive
when sync point or Free
Session outstanding.
2. TCZAQ2W Attempting to send while
in receive mode.
3. ZARQNOPG Issuing SIGNAL while in
send mode.
DFHZISP
4. ZISPVTCK Attempting to free session
while sync point request is
outstanding.
User Response: The response depends on the reason
for the error as follows:
1. Issue a sync point and then issue the request.
2. Issue the free request and reallocate the session.
3. Either change the application to issue receives until
EIBRECV is not set, or specify RAQ=YES in the
installed profile definition. (If you specify
RAQ=YES in the installed profile definition, ensure
that all input messages are read before the
transaction is terminated.)
4. See the CICS Distributed Transaction Programming
Guide where rules for the correct use of commands
are given. Then correct the application.
The application program has attempted an operation
on a logical unit that is invalid, because the program�s
current status on the session with that logical unit does
not permit it. An investigation of the TCTTE (that is,
Session), status bytes, and TCA type of request bytes
will reveal which of the above problems are relevant.
When the cause of the problem has been ascertained,
the application program should be changed to ensure
that the session-oriented information is acted upon
before any further requests are sent across that session.
The session status information is made available to the
application program in the exec interface block (EIB)
immediately following the execution of RECEIVE,
CONVERSE, or RETRIEVE requests across the session.
The relevant bytes must be tested, strictly in the order
shown, and acted upon, before any further operations
are attempted on the session. In addition, the status
information bytes themselves are necessarily volatile in
that they are reset before the execution of every EXEC

CICS... statement. Thus it is good programming
practice to save them into application user storage after
a RECEIVE, CONVERSE, or RETRIEVE for later
testing. The states are:
1. EIBSYNC
the application must take a syncpoint
2. EIBFREE
the application must free the session (or
terminate when the session will be freed
automatically)
3. EIBRECV
the application must continue receiving data
by issuing further RECEIVE commands; by
definition, data cannot be sent while in this
state.
Some of these status tests can sometimes be omitted
(for example, testing of the EIBSYNC status is not
essential if it is known that the application program on
the remote system never issues sync point requests
itself). However, the tests should always be carried out,
particularly if the remote application might be
amended at a future date, in which event the session
handling logic may well be altered. Also, it may be that
the remote transaction itself causes an unsuspected
flow on the session. For example, if the remote
program issues EXEC CICS SEND..... LAST across the
session, followed by RETURN, a syncpoint request
(RQD2) will be added onto the transmitted data. (The
application programmer is referred to the CICS
Distributed Transaction Programming Guide for a
discussion of this topic). As a result of this addition, an
unsuspected syncpoint request is received by the local
application, which abend if the session is freed without
the sync point request being honored.
Note: An ATCV abend is also raised by module
DFHETL if a state error occurs during processing
of an APPC mapped application (that is, the
program attempts to perform an operation while
in the wrong state). The handling of APPC
mapped applications is described in the CICS
Diagnosis Reference. Some commands are
processed by DFHZARQ, as above, and others
by various other modules invoked by DFHETL.
Rules for using commands for APPC are given in
the CICS Distributed Transaction Programming
Guide. Reference to this guide should reveal the
programming error.
Modules: DFHETL, DFHZARQ, DFHZISP
ATCW
Explanation: The system has been generated without
an installed profile definition for an LU6.1 or APPC
session.
User Response: Notify the system programmer of the
error.
ATCX
An application program that issues terminal control
requests after an ATCX abend may cause further
problems.
Modules: DFHBSMIR, DFHBSMPP, DFHBSM62,
DFHBSS, DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ,
DFHBSTZB, DFHBSTZO, DFHBSTZR, DFHBSTZV,
DFHBSTZ1, DFHBSTZ2, DFHBSZZS, DFHAPRT,
DFHCRP, DFHQRY, DFHZARL, DFHZARQ,
DFHZERH, DFHZGET, DFHZFRE, DFHZNAC,
DFHZRVS, DFHZSUP, DFHMRXM, DFH62XM
DFHZTSP, DFHZXST
ATCY
processing of an inbound function management header
(FMH). Either a length error has been detected, for
example, incomplete FMH received, or an invalid field
has been detected within the FMH.
error. The problem is probably in the remote system
that has sent the invalid FMH.
If the inbound FMH is from a system with an earlier
release of CICS then you may need to set
USEDFLTUSER. See �Attach Time Security and the
USEDFLTUSER option� in chapter 12 of the CICS RACF
Security Guide.
Modules: DFHZARQ, DFHZSUP DFHMRXM
DFH62XM
ATCZ
EXCEPTION response) has occurred on the
SET_NETWORK_IDENTIFIER call to the security
domain as part of opening the CICS VTAM ACB (for
example, EXEC CICS SET VTAM OPEN or CEMT SET
VTAM OPEN). The domain that detected the original
error provides an exception trace, a console message,
and depending on the options specified in the dump
table, a system dump.
with a CICS transaction dump. The VTAM ACB is
closed.
User Response: Use the dump, the trace and the
console message to diagnose and correct the original
error. Retry the command when the earlier error is
resolved.
Module: DFHZSLS
ATC1
Explanation: The CICS terminal control restart task
could not complete because a necessary step failed. The
task has done some essential recovery operations and
abnormally terminated itself with code ATC1.
the terminal control restart task.
CICS sends two messages to the console, one to
identify the error detected by the terminal control
restart task, and DFHTC1001 to report that the task has
failed. A third message follows either to say that CICS
has terminated abnormally with a dump, or to ask you
to reply GO or CANCEL. Depending on the nature of
the original error, you may see messages from some
other system component (for example, an access
method).
User Response: First, if CICS has requested a
response, you must reply. If you reply �GO�, CICS
continues processing, but without terminal control. If
you reply �CANCEL�, CICS terminates abnormally with
a dump.
Use the messages and dumps to find out the cause of
the failure.
Module: DFHTCRP
ATC2
Explanation: A CICS SET VTAM OPEN command has
failed due to VTAM rejecting a CICS request.
System Action: Message DFHZC2302, DFHZC2304 or
DFHZC2307 is sent to the console, and CICS terminates
the transaction abnormally with a transaction dump.
User Response: The RPL with the VTAM request code
and return code can be found in the RA pool addressed
from TCTVRVRA. Use the VTAM Programming manual,
to determine the cause of the error and the actions
necessary to correct it. After correcting the error, either
retry the request or terminate CICS and restart the
network in your own time.
Module: DFHZSLS
ATC3
Explanation: A write to a TLX device was issued with
a data length of 0 causing TIOA data length
(TIOATDL) to be zero.
User Response:
For an error writing to a TLX device correct the error in
the user program by ensuring that a data length for
data to be placed in the terminal input/output area
(TIOA) is provided at write time.
Modules: DFHZARL DFHZARQ
ATC4
Explanation: A serious CAVM error has occurred. The
XRF TCB has abended.
System Action: CICS abnormally terminates with a
system dump.
User Response: Use the dump and the guidance in
any messages issued by other system components to
diagnose and correct the original error.
See the CICS Problem Determination Guide for further
guidance on using system dumps.
Module: DFHTCRP
ATC5
during APPC mapped processing. The conversation
state maintained by DFHZARL does not match the
state which is jointly maintained by DFHETL and
DFHZARM.
This problem could also arise when CICS is receiving
application data. CICS may receive and end of chain
notification before receiving all the data expected.
continues.
Module: DFHETL
ATC6
Explanation: DFHETL has a SEND DATA request with
a data length greater than 65 528 bytes which is the
maximum that it can process.
User Response: This is a CICS internal logic error. You

Module: DFHETL
ATC7
Explanation: DFHZSUP has detected a bad response
from an INITIAL-CALL request to DFHZARL. This
response is returned to DFHZSUP in the DFHLUC
parameter list.
User Response: Examine field LUCCDRCD in the
DFHLUC parameter list. This appears in the
ENTRY/EXIT trace points for DFHZARL. If trace is
switched off, then it can be found in DFHZSUP�s LIFO
entry in the transaction dump.
v LUCCDRCD = �A0000100� - session failure
v LUCCDRCD = �A0010100� - read timeout
v LUCCDRCD = �A0010000� - deadlock timeout.
(The offset for LUCCDRCD can be found in CICS Data
Areas).
If LUCCDRCD is X�00000000�, the error is the result of
a connection failure. In this case examine the CSMT log
for further diagnostic information.
Module: DFHZSUP
ATC8
processing of an inbound function management header
(FMH). Either a length error has been detected, for
example, incomplete FMH received, or an invalid field
has been detected within the FMH.
error. The problem is probably in the remote system
that has sent the invalid FMH.
Module: DFHETL
ATC9
Explanation: A DFHKC RESUME macro call has been
issued for a task without first issuing DFHKC
SUSPEND. DFHKC RESUME must be preceded by
DFHKC SUSPEND.
User Response: Examine the trace entry to locate the
error.
Module: DFHZNCE
ATDC
Explanation: A transaction has issued an EXEC CICS
READQ, WRITEQ or DELETEQ command against a
logically recoverable transient data queue. The task was
enqueued because another task currently owns the
enqueue. While waiting to obtain the enqueue, the task
was purged.
User Response: Investigate why the transaction was
purged. It may have been purged via CEMT or
automatically, by DTIMEOUT for example.
Module: DFHETD
ATDY
Explanation: Transient data initialization has failed. A
console message, DFH12xx, gives the reason for the
failure.
System Action: Transient data initialization terminates
abnormally. This abend is always followed by an ATDZ
abend for the failing function, and by message
DFHSI1521 (if CICS abends unconditionally), or
message DFHSI1522, which prompts you to reply GO
or CANCEL.
User Response: See the associated console message for
information regarding the cause of the failure. Then
respond to message DFHSI1522, if it has been issued.
Module: DFHTDRP
ATDZ
Explanation: A CICS function invoked by transient
data initialization has failed. If the failing function is a
transient data routine, this abend is preceded by a
console message and an ATDY abend.
System Action: Transient data initialization terminates
abnormally. This abend is always followed by message
DFHSI1521 (if CICS abends unconditionally), or
message DFHSI1522, which asks you to reply GO or
CANCEL.
User Response: Refer to the associated console
message for further information regarding the cause of
the failure. Then respond to message DFHSI1522, if it
has been issued.
Module: DFHTDRP
ATFE
Explanation: A FREEMAIN request to the storage
manager has failed while CICS was executing a CEDA
CHECK or CEDA INSTALL command.
User Response: Use the dump and any associated
messages issued by the storage manager to investigate
the FREEMAIN failure.
Module: DFHTOUT1
ATGE
Explanation: A GETMAIN request to the storage
manager has failed while CICS was executing a CEDA
CHECK or CEDA INSTALL command.
User Response: Use the dump and any associated
messages issued by the storage manager to investigate
the GETMAIN failure.
Module: DFHTOUT1
ATMA
the purged condition will have provided an exception
trace.
presence of active tasks.
Module: DFHTMP
ATMB
the dump table).
Module: DFHTMP
ATNA
Explanation: A terminal operator entered the
transaction identification for NACP.
User Response: Do not reenter the NACP transaction
identification (CSNE).
Module: DFHZNAC
ATNB
Explanation: The application program has issued a
terminal control request for a terminal for which a
previous request was terminated with an abend AZCT,
because of a read timeout condition. The terminal
control blocks are not in a fit state to allow a new
request to be processed.
issue an abend when handling an abend AZCT.
Module: DFHZARQ
ATNC
Explanation: The application program has issued a
terminal control request for a terminal for which a
previous terminal control request was terminated with
an abend ATCH, because the task was purged. The
terminal control blocks are not in a fit state to allow a
new request to be processed.
issue an abend when handling an abend ATCH.
Module: DFHZARQ
ATND
Explanation: The node error program (NEP) or NACP
decides that a task should abnormally terminate, but
the task is at a critical point of processing and
immediate termination would put the integrity of the
system at risk.
with a CICS transaction dump when the task next

requests any action against the terminal, or issues a
sync point request involving the terminal.
User Response: Check destination CSMT for possible
further information. Use the dump to determine why
the task was abnormally terminated by NEP.
Modules: DFHZARQ, DFHZARL, DFHZSUP
ATNI
Explanation: There are two forms of this abend:
VTAM form
The node error program (NEP) or NACP
decides the task should be abnormally
terminated. DFHZNAC informs the request
module to abend the transaction after the TC
unit has completed.
Non-VTAM form
The terminal error program (TEP) or terminal
abnormal condition program (TACP) decides
the task should be abnormally terminated.
DFHTACP informs DFHZARQ to abend the
transaction after the TC unit has completed.
User Response: This usually occurs when, due to a
hardware failure, a network device rejects the data
stream sent to it. The device itself may indicate an error
code that will give a specific reason for the rejection.
Check the CSMT log for further information.
This abend can also result from an error in a connected
system such as a mirror transaction abend.
Abend ATNI can occur if a user application does not
correctly handle an error return code from an external
resource manager, such as DB2.
For the NEP (VTAM) form, run a VTAM trace
type=BUF for the logical unit and repeat the error.
For the TEP (non-VTAM) form, run a link trace for the
line or local channel address for the device.
Examine the data stream and error response to
determine the cause of the error.
This type of error occurs if the definitions in the TCT
do not match the attributes of the actual device.
Modules: DFHZARL, DFHZARM, DFHZARQ,
DFHZRAQ, DFHZSUP
ATOA
Explanation: You have attempted to invoke the CESC
transaction with a terminal as principal facility. This is
not allowed.
System Action: CICS terminates the CESC transaction.
No dump is produced.
User Response: Ensure that the CESC transaction is
not run against a terminal.
Module: DFHCESC
ATOB
Explanation: CICS has received an abnormal response
from an EXEC CICS START TRANSACTION(CESC)
request. This is caused by an internal error.
System Action: CICS terminates the CESC transaction
with a dump.
Module: DFHCESC
ATOC
from a request to DFHZCUT to timeout a local userid
table (LUIT). This is caused by an internal error in
DFHZCUT.
with a dump.
Module: DFHCESC
ATOD
from an EXEC CICS CANCEL TRANSACTION(CESC)
request.
with a dump.
Module: DFHCESC
ATOE
Explanation: CICS cannot determine the time at which
an XRF takeover began.
with a dump.
Module: DFHCESC
ATOF
from an EXEC CICS DELAY TRANSACTION(CESC)
request.
with a dump.
Module: DFHCESC
ATOG
from an EXEC CICS START TRANSACTION(CEGN)
request. This is caused by an internal error.
System Action: CICS terminates the CEGN transaction
with a dump.
Module: DFHCESC
ATOH
Explanation: An attempt has been made to invoke the
CESC transaction with an invalid function code. The
CESC transaction should only be invoked by CICS.
Valid codes are TERM_TIMEOUT, XRF_TIMEOUT, and
ENABLE_TIMEOUT.
The most likely cause of this error is an invalid attempt
by a user to invoke CESC.
User Response: Determine how CESC was invoked. If
it was invoked by CICS, you will need further
assistance from IBM to resolve this problem. You need
Module: DFHCESC
ATOT
Explanation: An error has occurred in the invocation
of the CEGN transaction. CEGN has issued an EXEC
CICS RETRIEVE command to retrieve the CEGN
parameter list. Either the EXEC CICS RETRIEVE
command has failed or it has succeeded but the
retrieved data is invalid.
The most likely cause of this error is an invalid attempt
by a user to invoke CEGN (for example, from a
terminal or via an EXEC CICS START request).
System Action: CICS terminates the CEGN transaction
User Response: Determine how CEGN was invoked.
If it was invoked by CICS, you will need further
assistance from IBM to resolve this problem. You need
Module: DFHCEGN
ATOU
Explanation: The CEGN transaction has attempted to
issue an EXEC CICS RETURN but the command has
failed.
dump.
Module: DFHCEGN
ATOV
Explanation: The CEGN transaction has attempted to
issue an EXEC CICS GETMAIN, ASSIGN, or SEND but
the command has failed.
dump.
Module: DFHCEGN
ATPA
Explanation: An error occurred when trying to
estimate the length of a CICS message owned by the
message domain.
dump.
Module: DFHTPR.
ATPB
retrieve a CICS message from the message domain.
dump.

Module: DFHTPR.
ATPC
estimate the length of a CICS message owned by the
message domain.
dump.
Module: DFHTPQ.
ATPD
retrieve a CICS message from the message domain.
dump.
Module: DFHTPQ.
ATPE
trace.
presence of active tasks.
Modules: DFHTPQ, DFHTPR.
ATPF
the dump table).
Modules: DFHTPQ, DFHTPR.
ATRA
Explanation: The field engineering global trap exit
program, DFHTRAP, requested task abnormal
termination. However, the currently active task was not
a system task (for example, task dispatcher) and it was
not about to abend.
System Action: CICS disables the trap exit so that it
will not be reentered, and terminates the currently
active task abnormally.
User Response: This is a user-requested task abend.
If you want to use the trap again, you must reactivate
it as follows:
CSFE DEBUG,TRAP=ON
You should use the global trap exit only in
consultation with an IBM support representative.
Module: DFHTRP
ATSA
Explanation: The transaction CTSD was attached other
than by an internal request from the TS domain.
User Response: Investigate why the CTSD transaction
was started. This transaction is intended for CICS
internal use only and should not be started by a user or
from a terminal.
Module: DFHTSDQ
ATSB
Explanation: The transaction CTSD was attached with
invalid parameters.
to resolve this problem. You need further assistance
to proceed.
Module: DFHTSDQ
ATSC
Explanation: The task was canceled during execution
of a temporary storage command.
canceled. The task has been canceled by the master
terminal operator or automatically by either the
deadlock timeout (DTIMEOUT) mechanism or the read
timeout (RTIMOUT) mechanism.
Modules: DFHEITS, DFHICP, DFHTSP
ATSD
Explanation: An INVALID or DISASTER response was
received from a request to the Temporary Storage (TS)
Domain.
which lead to the response from TS. Investigate the
earlier failure (which is accompanied by a console
message and a system dump).
Modules: DFHEITS, DFHICP, DFHTSP
ATSP
Explanation: A task has attempted to issue a WRITEQ
TS request for a recoverable TS queue that has already
been deleted in the same unit of work.
User Response: Correct the application to avoid
issuing a WRITEQ TS request to a recoverable queue in
a unit of work in which the queue has already been
deleted.
Modules: DFHEITS, DFHTSP
ATSQ
Explanation: A move of data to or from temporary
storage has failed. The probable reason is that the size
of the area being passed to CICS is inconsistent with
the data length being used.
User Response: Identify the failing temporary storage
request in the application and verify whether the length
supplied on the request agrees with the data area size.
Correct the application as appropriate.
Note: If the error occurs in DFHTSP and not in
DFHETS, there is probably an internal logic error
in temporary storage. In this case you will 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: DFHEITS
ATUF
Explanation: Insufficient space exists to build the
parameter list for the DYNALLOC SVC.
a dump is taken.
Module: DFH99KO
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
AUEL
Explanation: Internal logic error in CICS user exit
management. This arises when an attempt to obtain or
release the lock on the chain of EPB�s fails
unexpectedly.
Modules: DFHUEM, DFHERM.
AUEP
because a return code of UERCPURG has been sent to
the User Exit Handler by a User Exit Program. The
value of UERCPURG is defined by the macro
DFHUEXIT TYPE=EP, ID=xxxxxxxx, where xxxxxxxx is
the exit point by which the exit program is enabled.
This code does not apply to exit points in domains. The
exit program returns this value when it has made a
request for CICS services using the exit programming
Interface (XPI) and when the XPI call has had a
RESPONSE code of PURGED. Exit programs must not
set UERCPURG return code under any other
circumstance.
User Response: Refer to the CICS Customization Guide
for the use of this return code.
Module: DFHUEH
AUXA
Explanation: An unexpected error occurred when one
of the Transaction Affinities Utility Detector exit
programs called Detector program CAUTABM.
Transaction CAFB issues this abend on behalf of the
exit program.
System Action: The Detector is stopped.
User Response: Refer to message DFHAU4100.
Module: CAUCAFB1
AUXB
Explanation: The Transaction Affinities Utility
Detector dataspace has filled up. If the situation was
detected by a Detector exit program, transaction CAFB
issues this abend on its behalf.
User Response: message DFHAU4200.
Modules: CAUCAFF3, CAUCAFF6, CAUCAFB1
AUYA
Detector transaction CAFB received an unrecognizable
request from another Detector component (CAFF or a
Detector exit program).
Module: CAUCAFB1
AUYC
Detector transaction CAFB received a request from
another Detector component (CAFF or an exit program)
to abend because of an unexpected error.
Module: CAUCAFB1
AUYE
Explanation: A Transaction Affinities Utility Detector
program found an invalid affinity file number in an
internal array in the Detector global work area (GWA).
Modules: CAUCAFB2, CAUCAFF3
AUYF
Detector transaction CAFB was not started by
transaction CAFF.
Module: CAUCAFB1
AUYG
Detector transaction CAFB was still running at CICS
termination.
Module: CAUCAFB1
AUYH
Explanation: A Transaction Affinities Utility Detector
program has found that the address held in the
Detector global work area (GWA) for one of the
Detector internal modules is invalid.
AUYI
Explanation: An unexpected error occurred when
Transaction Affinities Utility Detector transaction CAFF
or CAFB called Detector program CAUTABM to access
affinity table data in the dataspace.
Modules: CAUCAFB2, CAUCAFF6
AUYJ
Explanation: One of the Transaction Affinities Utility
affinity data files is full.
Module: CAUCAFB2
AUZA
or CAFB issued an EXEC CICS command.
Modules: CAUCAFF1, CAUCAFF2, CAUCAFF3,
CAUCAFF4, CAUCAFF5, CAUCAFF6, CAUCAFF7,
CAUCAFB1, CAUCAFB2, CAUCAF41
AUZB
or CAFB issued a VSAM file control EXEC CICS
command.
CAUCAFF4, CAUCAFF5, CAUCAFF6, CAUCAFB1,
CAUCAFB2
AUZC
Explanation: The internal field holding the Transaction
Affinities Utility Detector state has an invalid value.
Modules: CAUCAFF1, CAUCAFF2
AUZD
Explanation: One of the Transaction Affinities Utility
files contains a CICS APPLID that does not match the
APPLID of the CICS system.

AUZF
or CAFB issued a Detector user exit related EXEC CICS
command. The command is either ENABLE, DISABLE
or EXTRACT EXIT.
CAUCAFF4, CAUCAFF5, CAUCAFF6, CAUCAFB1
AUZH
called Detector program CAUTABM to create the MVS
dataspace to hold the affinity data.
Module: CAUCAFF3
AUZI
called Detector program CAUTABM to create an
affinity table in the dataspace.
AUZJ
called Detector program CAUTABM to add an element
to an affinity table in the dataspace.
Module: CAUCAFF3
AUZK
was attempting to initialize the internal trace table.
Module: CAUCAFF3
AUZL
was attempting to release the internal trace table.
Module: CAUCAFF4
AUZN
called Detector program CAUTABM to destroy the
dataspace.
Module: CAUCAFF4
AUZO
called Detector program CAUTABM to destroy a table
in the dataspace.
Module: CAUCAFF6
AUZQ
called Detector program CAUCAFP to create its MVS
CPOOL storage.
Module: CAUCAFF3
AUZR
or CAFB called Detector program CAUCAFP to access
its MVS CPOOL storage.
AUZS
called Detector program CAUCAFP to destroy its MVS
CPOOL storage.
Module: CAUCAFF4
AUZU
calculated what percentage of the dataspace is occupied
by affinity data.
Module: CAUCAFF1
AUZV
Explanation: The method of initiating Transaction
Affinities Utility Detector transaction CAFF is incorrect.
Module: CAUCAFF1
AUZY
or CAFB called Detector program CAUTABM to
replace a table element in the dataspace.
Modules: CAUCAFF3, CAUCAFB2
AUZZ
called a Detector subroutine to update the termid table
(TT) or userid table (UT).
AUZ1
Explanation: When the Transaction Affinities Utility
Detector was being started by transaction CAFF, the
header record could not be found on one of the VSAM
affinity data files.
Module: CAUCAFF3
Abend codes AWxx
AWBA
Explanation: CICS Web Receive process has received
an exception response from the Web Send Receive
function, DFHWBSR, which could be one of the
following errors:
v An error in the Analyzer program
v No Analyzer program specified
v Unable to link to Analyzer program
v An Analyzer data length error
v An Analyzer header length error
v A codepage conversion error
v A storage error occurred
v An error that the connection has been closed
v A sockets receive error
System Action: An error message is sent to the client
and the CWBO transient data queue.
User Response: Refer to any error messages
accompanying this abend to determine why the abend
has occurred.
Module(s): DFHWBXN
AWBB
Explanation: The incoming parameter list to the CICS
Web Business Logic Interface program is not in the
expected format. At present, the structure is assumed to
be fixed and only a single version level is recognized.
System Action: The CICS Web Business Logic
Interface program is not executed.
User Response: Ensure that the program receives a
parameter list in the correct format.
Module(s): DFHWBBLI
AWBC
Explanation: No commarea was passed to a CICS Web
Interface utility program. One of the utility programs
supplied with the CICS Web Interface was executed,
but the commarea that was passed was absent or was
too short to contain valid information.
System Action: The CICS Web Interface utility is not
executed.
User Response: Ensure that the program passes a
commarea that is long enough to contain the expected
parameters for the utility you are invoking.
Module(s): DFHWBENV, DFHWBTL
AWBE
Explanation: The CICS Web Interface detected that a
Converter program attempted to change the address of
the response buffer when it was not allowed to do so.
System Action: The data in the new response buffer is
not returned to the Web browser. A CICS transaction
dump is taken.
User Response: The Converter program is only
allowed to replace the response buffer if the
converter_volatile flag in the Converter parameter list
is set to �1�. Check that your Converter program is not
trying to return a new response buffer when this flag is
set to �0�.
Module(s): DFHWBBLI
AWBF
Explanation: The CICS Web Interface alias detected an
error in its initialization. The alias was not started by
EXEC CICS START, or there was an error in the EXEC
CICS RETRIEVE command for the start data.
System Action: If there is an error in EXEC CICS

RETRIEVE, message DFHWB0103 is written to the
CWBO destination. A CICS transaction dump is taken.
User Response: If the alias was not started by EXEC
CICS START, check if it is being started from a
terminal. This is not allowed. Otherwise, see the
associated message for guidance.
Module(s): DFHWBA
AWBH
Explanation: The CICS Web Interface alias detected a
logic error.
System Action: An exception trace entry 454F is
written. Message DFHWB0106 is written to the CWBO
destination. A CICS transaction dump is taken.
User Response: Use related diagnostics to determine
the user response.
Module(s): DFHWBA
AWBI
Explanation: The CICS Web Interface alias received an
unexpected response from EXEC CICS ASSIGN
STARTCODE
System Action: An exception trace entry 4544 is
destination.
to proceed.
Module(s): DFHWBA
AWBJ
Explanation: The CICS Web Interface alias received an
unexpected response when it switched to the RP TCB.
System Action: An exception trace entry 454E is
destination. A transaction dump is taken.
User Response: See the associated message for
guidance.
Module(s): DFHWBA
AWBK
abend in the converter or the CICS program servicing
the request.
destination.
the user response.
Module(s): DFHWBA
AWBL
error in an EXEC CICS LINK command for program
DFHWBBLI.
destination. A transaction dump is taken.
guidance.
Module(s): DFHWBA
AWBM
Explanation: The CICS Web Interface alias detected
error response from the Business Logic Interface
program DFHWBBLI.
System Action: Message DFHWB0101 is written to the
CWBO destination. A transaction dump is taken.
guidance.
Module(s): DFHWBA
AWBO
Explanation: The CICS Web Interface alias program
has received a non-HTTP request for an HTTP service
or a SSL request has been sent to a non-SSL
TCPIPSERVICE.
CWBO transient data destination and a transaction
dump is taken. An exception trace entry, 4567, is also
written.
guidance.
Module(s): DFHWBA
AWBQ
Explanation: The CICS Web Business Logic Interface
program detected an error in its parameter list.
System Action: If the abend was issued from the
Business Logic Interface program, DFHWBBLI, an
exception trace entry �4581� is made and message
DFHWB0119 is written to the CWBO transient data
destination. If the abend was issued from the Web
Interface program, DFHWBA1, an exception trace entry
�4560� is written and message DFHWB0124 is sent to
the CWBO destination. A transaction dump is taken.
guidance.
Module(s): DFHWBA1, DFHWBBLI
AWBR
Explanation: The CICS Web Business Logic Interface
program detected a logic error.
System Action: If the abend was issued from the
Business Logic Interface program, DFHWBBLI, an
exception trace entry �4583� is made and message
DFHWB0118 is written to the CWBO transient data
destination. If the abend was issued from the Web
Interface program, DFHWBA1, an exception trace entry
�4558� is written and message DFHWB0123 is sent to
the CWBO destination.
the user response.
Module(s): DFHWBA1, DFHWBBLI
AWBU
Explanation: The CICS Web Interface connection
manager could not get storage to send a message to the
terminal.
System Action: Processing continues.
the user response.
Module(s): DFHWBC01
AWBV
manager detected an error response on EXEC CICS
DEQ.
destination.
to proceed.
Module(s): DFHWBC04
AWBX
manager was started against an invalid terminal type.
destination.
guidance.
Module(s): DFHWBC01
AWBZ
manager detected a NOTAUTH response to EXEC CICS
EXTRACT EXIT.
CWBO destination.
guidance.
Module(s): DFHWBC0B
AWB2
Explanation: The CICS Web Interface has encountered
an error while performing a transaction attach call for
the alias task.
System Action: Message DFHWB0727 describing the
error is written to the CWBO transient data destination
and a trace entry is made.
guidance.
Module(s): DFHWBXN
AWB3
Explanation: CICS Web transaction, CWXN, has been
illegally started either with data, or by a user at a
terminal, with the wrong start code.
System Action: The CICS Web Interface is not started.
User Response: CICS Web Transaction Execution
should only ever be started by Sockets Domain using
DFHXMAT ATTACH, not by a user at a terminal or
with data.
Module(s): DFHWBXN
AWB4
Explanation: The CICS Web Transaction Execution has
received a bad response from an
INQUIRE_TRANSACTION call to determine the start
code for the CWXN transaction.
System Action: The CICS Web Interface is not started.
User Response: CICS Web Transaction Execution
should only ever be started by Sockets Domain using
DFHXMAT ATTACH, not by a user at a terminal or
with data.
Module(s): DFHWBXN
AWB5
Explanation: The CICS Web Interface Server
Controller could not continue with enable processing
because the requested port is not available.
written, and message DFHWB0131 is issued.
User Response: Terminate the TCP/IP application
which is using the requested port, and use CBWB to
enable the feature again, or use CWBC to enable the
CICS web Interface using a different port number.
Module(s): DFHWBM
AWB7
Explanation: The CICS Web Interface environment
variables program was invoked, but the invoking
transaction does not appear to be executing in a valid
Web environment.
System Action: The program writes an exception trace
point 4623.
User Response: Determine how the environment
variables program was invoked. It is only meaningful
to execute the program from a transaction that has been
initiated from the Web, either through the CICS Web
Interface or through the Business Logic Interface.
Module(s): DFHWBENV
AWB8
Explanation: The CICS Web Interface environment
garbage collection task CWBG has been started directly
from a terminal. This is not permitted.
Module(s): DFHWBGB
AWB9
manager failed due to lack of storage.
System Action: A transaction dump is taken.
to proceed.
Module(s): DFHWBC01
AWC1
Explanation: The CICS Web Interface 3270 bridge exit
DFHWBLT could not establish a partnership with the
Web terminal translation task which started the
abended transction.
the user response.
Module(s): DFHWBLT
AWC2
DFHWBLT was passed an invalid state token by attach
processing.
System Action: An exception trace entry 410C is
the user response. On a busy CICS region, the most
likely cause is that the bridged transaction started after
the state data had been discarded by Web 3270 garbage
collection process.
Module(s): DFHWBLT
AWC3
Explanation: An application using the CICS Web 3270
function issued an unsupported combination of BMS
and Terminal Control commands.
System Action: An exception trace entry is written.
the user response.
Module(s): DFHWBLT
AWC4
DFHWBLT has been reinvoked after returning an
earlier error.
System Action: An exception trace entry is written.
the user response.
Module(s): DFHWBLT
AWC5
DFHWBLT abended during attach processing because it
could not getmain a brxa user area.
System Action: Message DFHWB0132 is issued, and
an exception trace entry 410D is written.
the user response. The most likely cause of this abend
is that CICS is having storage problems.
Module(s): DFHWBLT
AWC6
DFHWBLT has detected an inconsistency in its request
parameters or state data.
System Action: Message DFHWB0133 is issued, and
an exception trace entry is written.
is a storage overwrite.
Module(s): DFHWBLT
AWC7
Explanation: CICS detected an error during
transaction initialization for a CICS Web alias
transaction.
System Action: Message DFHWB0360 is issued. No
transaction dump is taken for this abend.
is an invalid userid being passed to CICS by the CICS
Web Interface Analyzer user replaceable module. The
userid is invalid if:
v It is not defined in the external security manager
v It is revoked
v It is not authorized to access this CICS region
Module(s): DFHWBXM
AWC8
Explanation: CICS detected an error during
transaction initialization for a CICS Web alias
transaction.
System Action: A transaction dump is taken for this
abend.
the user response.
Module(s): DFHWBXM
AWKY
Explanation: A request to PURGE or WRITE a record
using the global catalog during warm keypointing has
failed.
User Response: Check for problems with the global or
local catalog. See any DFHCCnnnn messages issued by
the CICS catalog domain for further guidance.
Module(s): DFHWKP
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
with quote
AXFA
Explanation: The key length for a file control request
that is to be sent to a remote system has to be obtained
from the file control table, and has proved to be zero.
User Response: Ensure that the key length has been
defined either in the remote file definition that is being
used, or as a length option from the application
program that is using it.
Module: DFHXFP
AXFB
Explanation: An unacceptable function management
header (FMH) type has been found. It must be type 05,
type 06, or type 43.
Module: DFHXFP
AXFC
Explanation: The request passed to the data
transformation program is unknown to CICS. This
abend can also occur in an MRO/IRC system as a
result of an invalid EXEC CICS START request issued
from the user�s node error program (DFHZNEP).
User Response: See the CICS Customization Guide for
restrictions on the use of EXEC CICS commands from
within an NEP. If this is not the cause of the abend,
you will need further assistance from IBM. You need
Module: DFHXFP
AXFD
Explanation: The request that is passed to the data
transformation program cannot be sent to a remote
system; for example, a storage control request.

Module: DFHXFP
AXFE
Explanation: The transformation requested does not
exist; for example, a DL/I schedule reply is not
recognized by the outbound request processor in the
data transformation program.
Module: DFHXFP
AXFF
Explanation: An unacceptable queue organization has
been found in a queue model function management
header (FMH).
Module: DFHXFP
AXFG
Explanation: An unacceptable argument number has
been found in the data following a function
management header (FMH) of type 43.
Module: DFHXFP
AXFH
Explanation: The argument number in the data
following a function management header (FMH) of
type 43 is acceptable, however, the argument itself is
not expected.
Module: DFHXFP
AXFI
Explanation: The data length for a WRITEQ TD or
READQ TD, which is determined from the destination
control table, is zero. The abend can also occur when
determining the length for file control requests from the
file control table.
Module: DFHXFP
AXFJ
Explanation: The error code held in UIBFCTR and
UIBDLTR cannot be converted to an equivalent SNA
error code.
Module: DFHXFP
AXFL
Explanation: Transformers 2 and 4 expect to receive a
function management header (FMH), possibly followed
by user data. A null chain of data has been received.
Module: DFHXFP
AXFM
Explanation: The ISCINVREQ condition has been
raised. This can happen when the resource proves to be
on yet another remote system, that is, when
daisy-chaining is active.
User Response: Check that daisy-chaining of requests
is intended and that all relevant intersystem links are in
service.
Module: DFHXFP
AXFO
Explanation: The check on the DS and DBA
parameters in an attach function management header
(FMH) has failed. This abend represents a user error
resulting from a mismatch in the system definitions for
both ends of an intersystem link.
Module: DFHXFP
AXFP
Explanation: CICS requires a second function
management header (FMH) to follow an attach FMH.
No second FMH was received.
Module: DFHXFP
AXFQ
Explanation: Either the function management header
(FMH) just received is too short or too long to be a
valid FMH, or an expected FMH is not present.
User Response: Check that the transaction profile
parameter, INBFMH, is set to ALL. If communicating
across a distributed program link, ensure that the
requested function is supported on the partner system.
Module: DFHXFP
AXFR
Explanation: The CICS command level interface
imposes a maximum length of 32 767 for data. The
length of the data just received exceeds this limit.
Module: DFHXFP
AXFS
Explanation: A PSB has been scheduled successfully.
However, the maximum possible length of an I/O area
exceeded 65 535. This abend is likely to occur if path
calls are used to retrieve large segments, and/or if FLS
causes excessive expansion of segments.
Module: DFHXFP
AXFT
Explanation: An estimate of the size of the output I/O
area has been made, and it exceeds the maximum
possible size of 65 535.
Note: While the estimated size may exceed the actual
size, the difference will only be a few bytes.
This abend is likely to occur if a database calls, inserts,
or replaces multiple segments, and many qualified
segment search arguments are specified.
Module: DFHXFP
AXFU
Explanation: A two-level cursor is present in a
function management header (FMH) relating to a linear
(temporary storage) queue. However, these cursors are
valid only for hierarchical queues that are not
supported by CICS.
Module: DFHXFP
AXFW
Explanation: An invalid length specification has been
given in a CICS command-level request corresponding
to one of the data variables.
The CICS-architected FMH is followed by zero or more
self-describing data variables for each parameter
specified.
User Response: Check for an invalid or zero length
specified in a CICS command-level request, or for data
truncation in a user-written node error program (NEP).
Module: DFHXFP
AXFX
Explanation: A function shipping request by an APPC
link failed because
v the remote system does not support full syncpoint

protocols, or
v the exchange log name sequence could have failed,
resulting in a mismatch, or
v the request has not completed within the allocated
time (10 seconds).
User Response: Check that the request was directed to
the correct remote system, and that the remote system
is set up to support full syncpoint protocols (synclevel
2).
Module: DFHXFP
AXFY
Explanation: An APPC conversation failure has
occurred when an attach between CICS systems was
issued.
Module: DFHXFP
AXF0
Explanation: A task has been purged due to lack of
storage in a dynamic storage area (DSA).
User Response: Try the transaction again later.
If the short-on-storage condition persists, consider
increasing the size limit of the CICS DSAs. You can
vary the DSAs dynamically using the DSALIM and
EDSALIM parameters on the CEMT master terminal
command.
Module: DFHXFP
AXF1
Explanation: The storage manager module,
DFHSMGF, has returned a condition not expected by
DFHXFP.
User Response: Look for any related CICS messages
and abends to determine if there has been a prior
failure in CICS storage.
Module: DFHXFP
AXF2
Explanation: A task has been purged due to lack of
storage in the DSA.
User Response: Try the transaction again later.
If the short-on-storage condition persists, increase the
size of the dynamic storage area using the DFHSIT
DSA parameter.
Module: DFHXFP
AXF3
Explanation: The storage manager module
DFHSMMC has returned a condition not expected by
DFHXFP.
User Response: Look for any related CICS messages
and abends to determine if there has been a prior
failure in CICS storage.
Module: DFHXFP
AXF4
Explanation: The task was purged before a
GET_BUFFER request to the EXEC interface service
routines module (DFHEISR), was able to complete
condition provides an exception trace.
Module: DFHXFX
AXF5
call to the EXEC interface service routines
module(DFHEISR). The domain that detected the
original error provides an exception trace, a console
message, and possibly, a system dump (depending on
the options specified the dump table).
Module: DFHXFX
AXF8
Explanation: A keyword such as TOKEN,
CONSISTENT, REPEATABLE, UNCOMMITTED, or
NOSUSPEND has been specified on a file control
command for shipping to a system which does not
support these functions.
User Response: Ensure that CICS in the file-owning
region is at the correct level.
Module: DFHXFX
AXMA
within the transaction manager domain.
control is invoked which issues message DFHXM0002
with a system dump. DFHXM0002 reports the module
DFHXM0002 for further guidance.
Modules: DFHXMAT, DFHXMBD, DFHXMCL,
DFHXMDD, DFHXMFD, DFHXMLD, DFHXMQD,
DFHXMST, DFHXMTA, DFHXMXD, DFHXMXE
AXMB
within the transaction manager domain.
DFHXM0002 with a system dump. DFHXM0002 reports
Modules: DFHXMAT, DFHXMBD, DFHXMCL,
DFHXMDD, DFHXMFD, DFHXMLD, DFHXMQD,
DFHXMST, DFHXMTA, DFHXMXD, DFHXMXE
AXMC
Explanation: An severe error has occurred allocating a
unique transaction number to a new transaction.
DFHXM0002 with a system dump. DFHXM0002 reports
Modules: DFHXMAT, DFHXMXE
AXMD
CICS internal task CSXM as a user transaction.
transaction dump.
made to run CSXM as a user transaction.
Module: DFHXMAB
AXMU
Explanation: During transaction attach the userid that
had been assigned to the transaction was found to be
invalid.
transaction dump.
User Response: Determine how the invalid userid had
been assigned to the transaction. It might have been
output by a user-replaceable module.
Module: DFHXMAT
AXMY
Explanation: During transaction attach an unexpected
error occurred obtaining transaction class membership.
System Action: The transaction is no longer
considered for class membership. It is then abnormally
User Response: Use the dump to determine why the
transaction failed to obtain membership of its
transaction class.
Module: DFHXMAT
AXMZ
Explanation: A serious failure in another component
has been detected by the transaction manager domain.
System Action: The task in control is abnormally
terminated with a transaction dump. Further
diagnostics should have been taken by the failing

component.
User Response: Look for earlier messages identifying
the source of the problem. Refer to the descriptions of
these messages for further guidance.
Module: DFHXMTA
AXSA
Explanation: The CICS security control task could not
complete because a necessary step failed. The task has
done some essential recovery operations and
abnormally terminated itself with code AXSA.
the security control restart task.
CICS sends messages to the console, one to identify the
error detected by the security control task, and, if the
error occurred during initialization, one to say that
security initialization or CEMT PERFORM SECURITY
REBUILD has failed. A third message follows either to
say that CICS has terminated abnormally with a dump,
or to ask you to reply GO or CANCEL. Depending on
the nature of the original error, you may see messages
from some other system component (for example, an
access method).
User Response: First, if CICS has requested a
response, you must reply. If you reply �GO�, CICS
continues processing, but without support for the
external security manager. CICS security still operates.
If you reply �CANCEL�, CICS terminates abnormally
with a dump.
Use the messages and dumps to find out the cause of
the failure.
Module: DFHXSMN
AXSC
trace.
Module: DFHXSMN
AXSD
Module: DFHTCRP
AXTA
Explanation: The calculation of the length of data to
be shipped has failed.
Module: DFHXTP
AXTB
Explanation: An attempt to obtain a TIOA to ship
data has failed.
Module: DFHXTP
AXTC
Explanation: An attempt to transform data ready for
shipment has failed.
Module: DFHXTP
AXTD
Explanation: No TIOA received message was received
from a remote system.
Module: DFHXTP
AXTE
Explanation: Incorrect data was received from a
remote system. The data was not long enough.
Module: DFHXTP
AXTF
Explanation: No relay process function management
header (FMH) was received from the remote system.
Module: DFHXTP
AXTG
Explanation: Transformation of data received from
remote system failed.
User Response: Check that the reason for failure of
the transformation process was not incorrect definition
of the remote terminal. In particular check that the user
area length specified for the terminal is the same in
both local and remote systems. If the terminal
definitions are correct, you need further assistance to
proceed.
Module: DFHXTP
AXTH
Explanation: An attempt to locate terminal identifier
failed.
Module: DFHXTP
AXTI
Explanation: The major request byte LUCOPN0 of the
DFHLUC parameter list specified to the
transaction-routing transformer is invalid, or
corresponds to a request that is not shipped to a remote
system. The parameter list will be found in the
dynamic storage of XTP�s caller and may be located
using the output from auxiliary trace.
Module: DFHXTP
AXTJ
Explanation: An unexpected combination of bit
settings in the fields XTSSTAT and XTSTCOPC in the
parameter list of the transaction-routing transformer
was made.
Module: DFHXTP
AXTK
Explanation: An APPC conversation failure occurred
when an attach between CICS systems was issued.
Module: DFHXTP
AXTL
requires the generation of an APPC 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.
defined with parallel sessions
v The remote system is capable of supporting a sync
level of 2.
v Exchange lognames has completed for the
connection. You can use the command CEMT
INQUIRE CONNECTION to do this. See the CICS
Intercommunication Guide for more details of the
exchange lognames process.
v The correct sync level has been requested.
Module: DFHXTP
AXTM
Explanation: An attempt has been made to route a
message-protected transaction over an APPC link
bound at sync level 1. The attempt has failed because
such transactions can be routed only over an APPC link
that has been bound at sync level 2.
User Response: If the transaction is to be routed to
CICS OS/2 (which is bound at synclevel 1), remove the
message protection option. If the transaction is to be
routed to another host system and message protection
is required, the link must be redefined so that it can be
bound at synclevel 2.
Module: DFHXTP
AXTN
Explanation: Module DFHXTP detected that the
application buffer chained off a TCTTE at offset
TCTERCSA has a corrupted header. This is caused
either by a CICS logic error or by a storage overwrite.
Module: DFHETL
AXTO
Explanation: An exception response has been returned
to the DFHXTP module from the CICS security
manager. Prior to the call to the CICS security manager,
the DFHXTP module detected that a shipped terminal
definition had preset security. DFHXTP then invoked
the CICS security manager in order to perform a preset
security signon for the userid sent with the shipped
terminal information. It is this preset security signon
attempt which failed.
System Action: The transaction routing request is
terminated and a message is sent to the terminal
owning region (TOR) to indicate that the transaction
routing request has failed. The CICS security manager
issues a DFHSNxxxx message to the transient data
queue, CSCS.
User Response: The most likely cause of this abend is
that the terminal being shipped to the application
owning region (AOR) has preset security with a userid
which is not valid in the AOR. To confirm this, check
the associated DFHSNxxxx message on the CSCS
transient data queue in the AOR which gives the
precise reason for the failure of the preset security
signon request. This could be the result of an
unauthorized transaction routing request.
Module: DFHXTP
AXTP
to the DFHXTP module from DFHCCNV
FUNCTION(CONVERT_DS3270_FOR_SBCS). The
module was called for a CICS client virtual terminal
which requested conversion from ASCII to EBCDIC for
data coming from the client. However, the conversion
failed.
issues a DFHSNnnnn message to the transient data
queue, CSCS.
User Response: Examine the response and reason
returned in the DFHCCNV commarea DFHC32. The
client and server codepages will have already been
validated so this may be a CICS error. You may need to
contact IBM for further assistance. You need further
on how to proceed.
Module: DFHXTP
AXTQ
to the DFHXTP module from DFHCCNV
FUNCTION(CONVERT_DS3270_FOR_SBCS). The
module was called for a CICS client virtual terminal
which requested conversion from EBCDIC to ASCII for
data to be sent to the client. However the conversion
failed.
queue, CSCS.
returned in the DFHCCNV commarea DFHC32. The
client and server codepages will have already been
validated so this may be a CICS error. You may need to
contact IBM for further assistance. You need further
on how to proceed.
Module: DFHXTP
AXTR
to the DFHXTP module from DFHPGLE
FUNCTION(LOAD_EXEC) whilst trying to load EXEC
program DFHCCNV.
queue, CSCS.
returned from DFHPGLE to determine why CICS was
unable to call DFHCCNV.
Module: DFHXTP
Abend codes AZxx
AZAB
Explanation: DFHZARM has a SEND DATA request
with a data length greater than 65 528 bytes which is
the maximum that it can process.
Module(s): DFHZARM
AZAD
Explanation: DFHZCN1 has been started from an
unexpected system. The CCIN transaction can only be
issued by a client.
terminated. Exception trace point AP3008 is written.
Data1 holds the XMIQ start type.
User Response: Issue the CCIN transaction only from
a client.
Module(s): DFHZCN1
AZAE
Explanation: DFHZCN1 was started from a terminal
facility, but not an LU6.2 session. The CCIN transaction
may only be issued by a client.
terminated.
User Response: Issue the CCIN transaction only from
a client.
Module(s): DFHZCN1
AZAF
Explanation: DFHZCN1 was started for transaction
CCIN. However either the environment is wrong or the
client architecture has been violated. This abend is
always issued in conjunction with a DFHZC32nn
message which explains the problem in more detail.
System Action: Exception trace point AP30xx is
written. The transaction is abnormally terminated.
User Response: Look for a DFHZC32nn message on
the console or CSNE and look for exception trace
points AP30xx. Use these to diagnose the problem.
Module(s): DFHZCN1
AZAG
Explanation: DFHZCT1 has been started from an
unexpected system. The CTIN transaction can only be
issued by a client.
terminated with a CICS transaction dump. Exception
trace point AP302A is written. Data1 holds the XMIQ
start type.
User Response: Issue the CTIN transaction only from

a client.
Module(s): DFHZCT1
AZAH
Explanation: DFHZCT1 was started from a terminal
facility, but not an LU62 session. The CTIN transaction
can only be issued by a client.
terminated with a CICS transaction dump. Exception
trace point AP3032 is written. Data1 holds the principal
facility address.
User Response: Issue the CTIN transaction only from
a client.
Module(s): DFHZCT1
AZAI
Explanation: DFHZCT1 was started for transaction
CTIN. However either the environment is wrong or the
client architecture has been violated. This abend is
always issued in conjunction with a DFHZC32nn
message which explains the problem in more detail.
System Action: Exception trace point AP30xx is
User Response: Look for a DFHZC32nn message on
the console or CSNE and look for exception trace
points AP30xx. Use these to diagnose the problem.
Module(s): DFHZCT1
AZAJ
Explanation: DFHZCN1 was started for transaction
CCIN. However, the CCIN transaction is being started
on a surrogate, which means that it has been defined as
a remote transaction. CCIN must be a local transaction
and be run on a CICS region which is directly
connected to a client.
System Action: Exception trace point AP3041 is
User Response: Either use the default definitions for
CCIN or ensure that it is defined as a local transaction.
Module(s): DFHZCN1
AZAK
Explanation: DFHZCT1 was started for transaction
CTIN. However, the CTIN transaction is being started
on a surrogate, which means that it has been defined as
a remote transaction. CTIN must be a local transaction
and be run on a CICS region which is directly
connected to a client.
System Action: Exception trace point AP3039 is
User Response: Either use the default definitions for
CTIN or ensure that it is defined as a local transaction.
Module(s): DFHZCT1
AZCA
during APPC mapped processing. The conversation
state maintained by DFHZARL does not match that
maintained jointly by DFHETL and DFHZARM.
The problem may also arise when CICS is assembling
application data and receives end of chain before
receiving all of the data that is expected.
continues.
Module(s): DFHZARM
AZCB
Explanation: CICS has received sense code X'088901xx'
during APPC mapped processing. This should be
followed by an error data GDS (generalized data
stream) variable.
CICS has attempted to receive the error data. However
this attempt has failed because no data has been
received or because the data received is not for an CICS
ISSUE ERROR of the correct length.
CICS expects the error data to indicate that the other
system does not recognize GDS ID X�12F2� (function
management data).
The erroneous GDS ID is returned to the remote system
for further analysis there.
User Response: Check for session failure and for
abend by the transaction in the other system.
Module(s): DFHZARM
AZCC
Explanation: The failing transaction has sent function
management data to a transaction running in a system
that does not provide support for application function
management data.
User Response: Check that the remote system can
support application function management data.
Module(s): DFHZARM
AZCD
Explanation: A possible intersystem logic error has
been detected during APPC mapped processing. The
length of application data that is to be received (as
determined from the LL fields and concatenation flags)
does not match the length actually received. CICS
determines the length of application data that is to be
received from the LL fields and concatenation flags.
However, CICS has not received all of the data that is
expected.
This abend can be caused by a loss of data following
the failure of a persistent sessions restart in a partner
system. In this case, no logic error has occurred because
any updates are backed out.
User Response: If this abend is not caused by the
failure of a persistent sessions restart in a partner
system, you will need further assistance from IBM. You
Modules: DFHETL, DFHZARM
AZCE
Explanation: An intersystem error has been detected
during APPC mapped processing. The length of
application data that is to be received (as determined
from the LL fields and concatenation flags) exceeds the
CICS implementation limit of 32 767, for receive and
converse commands, or 65 000 for CICS transaction
routing or function shipping requests.
User Response: Reduce the amount of data that the
transaction in the remote system is transmitting to
CICS.
AZCF
during APPC mapped processing. An invalid request
has been passed to DFHZARL.
Module: DFHZARM
AZCG
during APPC mapped processing. DFHZARM expects
the TCTTE passed to have been defined as APPC,
TCTEILUC (TCTELUC) set on, and TCTECVT set to
TCTEMAPD (to indicate a mapped conversation).
Module: DFHZARM
AZCH
Explanation: Sense code X'0889xxxx' has been received
unexpectedly during the processing of APPC mapped
data.
This represents a violation of the APPC architecture by
the remote system.
AZCI
requires generation of an APPC attach function
management header (FMH) with default values. In
particular, the sync level requested is defaulted to 2.
However, the session that is to be used has been bound
with a sync level of 1.
defined with parallel sessions.
v The remote system is capable of supporting a sync
level of 2.
v Exchange lognames has completed for the
connection. You can use the CEMT INQUIRE
CONNECTION to do this. See the CICS
Intercommunication Guide for details of the exchange
lognames process.
Modules: DFHETL, DFHZARM, DFHZARQ
AZCJ
Explanation: An APPC structured field with GDS ID
X�12F1� (null data) has been sent to a remote system
that does not support the receipt of these fields. The
remote system has responded negatively and has
terminated the conversation.
User Response: The problem is in the remote system.
Module: DFHZARM
AZCK
during error recovery for APPC mapped processing.
The conversation was being switched to RECEIVE state
by an internal CICS SEND INVITE, but the
conversation had already been FREEd by the partner.
continues.
Module: DFHZARM
Back to top
Vamsi99
Active Member
Joined: 05 Nov 2008

Posts: 184
Useful Post
0 votes
Not an useful post
0 salutes
PostPosted: Mon Oct 18, 2010 12:32 am Post subject: Reply with quote
AZCL
Explanation: CICS has received sense code X'088901xx'
during APPC mapped processing. The generalized data
stream (GDS) should contain a valid GDS identity in
the error data but CICS does not recognize the value.
The values recognized by CICS are:
X�12F1�null data
X�12F2�function management data
X�12FF�application data.
User Response: Check for session failure and for an
abend by the transaction in the other system.
Module: DFHZARM
AZCM
Module: DFHZARM
AZCN
Explanation: The task has been purged before a
GETMAIN request to the storage manager (SM)
domain was able to complete successfully. The task that
exception trace.
Module: DFHZARM
AZCO
Explanation: The VTAM persistent sessions
initialization transaction CGRP has been started directly
from a terminal. This is not permitted. This transaction
can only be started internally by CICS.
Module: DFHZCGRP
AZCP
Explanation: A logic error has been detected in ZCP.
An allocation request for a starting task cannot be
satisfied.
Modules: DFHZSUP DFH62XM
AZCQ
call to the recovery manager (RM) domain to change
the recovery status of an intercommunication session.
The domain provides an exit trace, and possibly a
console message and a system dump (depending on
User Response: This failure is either the result of a
task purge, or it represents a CICS logic error and you
will need assistance from IBM.
See the related diagnostic material produced by the
recovery manager domain.
AZCR
Explanation: A logic or protocol error has been
detected during processing of an APPC SYNCPOINT
ROLLBACK request. An attempt has been made to
restore the conversation state to what it was after
completion of the last successful unit of work. This
saved state does not match flows received from the
partner.
The problem arises during rollback in one of the
following situations:
v The saved state is receive, and the partner sent
change direction on the last flow, indicating that the
partner expects CICS to be in send state
v The saved state is send, and the partner did not send
the change-direction indicator on the last flow,
indicating that the partner expects CICS to be in
receive state.
with a CICS transaction dump. Other processing
continues.
User Response: The problem can arise because of a
failure in CICS, or a failure in the partner. To determine
which is failing, analyze the flows at the last successful
syncpoint. Try to determine the states the two LUs
were in at this point. Look at the last syncpoint flow
into CICS from the partner, before the abend. From this
flow, calculate whether the change-direction indicator
on the SPCMOD modifier byte is on. ( See the SNA
Formats manual for further information on the
SPCMOD modifier byte.) The indicator must only be
set when the saved CICS conversation state is send. If
the last CICS state was send, and the indicator is on,
CICS is at fault. Similarly, if the last CICS state was
receive, and the indicator is off, CICS is at fault.
If the last CICS state was send and the indicator is off,
or the last CICS state was receive, and the indicator is
on, CICS has received a change-direction indicator
when it was not expecting one. In this case, examine
the partner for a logic error.
Module: DFHZARL
AZCT
Explanation: A terminal read-time-out condition has
been detected. The transaction has been waiting for a
terminal input message for an interval longer than
specified in the RTIMOUT value for that transaction.
Coding RTIMOUT in the PROFILE entry causes the
task to be abnormally terminated if the terminal does
not send input within the specified time.
terminated. A dump is not provided unless the dump
table entry for transaction dump code AZCT indicates
that one should be taken.
User Response: If a HANDLE ABEND command has
been issued for this task, the read that was timed-out is
still outstanding. In order to cancel this read, issue an
ABEND command at the end of the user exit routine so

that CICS can clean up the terminal�s TCTTE. No
further terminal control commands should be issued.
Module: DFHZARQ
AZCU
Explanation: The COVR transaction has been started
directly from a terminal, or by a START command. This
is not permitted. This transaction can only be started
internally by CICS.
terminated. No transaction dump is taken.
Module: DFHZCOVR
AZCV
Explanation: A logic error has been detected in the
COVR transaction while trying to connect to VTAM.
Module: DFHZCOVR
AZCW
CICS internal task CSTP as a user transaction.

transaction dump.
made to run CSTP as a user transaction.
Module: DFHZCSTP
AZIA
Explanation: The transaction attempted to acquire or
free storage during MRO processing. The response
from the CICS storage manager (SM) domain indicated
that the request was invalid.
with a dump.
Module: DFHZIS2
AZIB
Explanation: The transaction was purged whilst
waiting for storage to receive MRO data from a
connected subsystem. The purge may have been the
result of operator action, such as CEMT SET TASK
PURGE, or as the result of the waiting time exceeding
the DTIMOUT value for the transaction.
with a dump.
User Response: If the condition is caused by time-out,
examine the DTIMOUT value for the failing transaction
and increase it if it is too low.
Module: DFHZIS2
AZIC
storage manager domain (DFHSMGFM) to FREEMAIN
a CRB control block.
exception trace, a console message, and possibly a
system dump.
User Response: Please see the related message from
Module: DFHZIS2
AZID
call to the storage manager domain (DFHSMGFM) to
FREEMAIN a CRB control block.
exception trace.
Module: DFHZIS2
AZIE
Explanation: An interregion communication (IRC)
ISSUE-ERROR or ISSUE-ABEND flow has been
received in violation of IRC protocols. This can be
caused by:
v A CICS logic error. IRC protocols are not available to
MRO distributed transaction processing applications.
They are for CICS internal use only.
v A transaction abend on a connected system. This
results in an FMH 7 flow over an LU6.2 connection
and causes this abend to be issued.
User Response: Check whether a mixture of mapped
and unmapped conversations are being used as this can
cause this abend. Check for any other reasons for
transactions to be abending on the attached system.
If a CICS logic error is involved, you will need further
proceed.
Module: DFHZARQ
AZIF
call to the recovery manager (RM) domain to change
the recovery status of an intercommunication session.
The domain provides an exit trace, and possibly a
console message and a system dump (depending on
This is either the result of a task purge, a CICS logic
error, or of the inappropriate use of the indoubt test
transaction, CIND. CIND should be activated only on
the CICS system where the syncpoint processing was
initiated. In particular, CIND should not be used on
any of the CICS mirror transactions.
User Response: Determine whether CIND has been
activated for a transaction that did not initiate the
syncpoint processing. If CIND is not being used see the
related diagnostic material produced by the recovery
manager domain and determine the reason for the
failure.
In the case of a CICS logic error, you need further
proceed.
Module: DFHZARQ
AZI1
Explanation: An IRC data transmission request has
been issued, but cannot be completed because the
transmission protocol has been violated.
If the session is not used for distributed transaction
processing, that is if it is used for function shipping or
transaction routing, then the problem is caused by a
CICS logic error.
If the session is used for distributed transaction
processing, then the following are possible causes of
the abend:
v An invalid terminal control command, such as ISSUE
SIGNAL, was issued
v A send request was issued but the session was not in
send state, or a read request was issued but the
session was not in receive state.
User Response: Determine the cause of the abend and
if appropriate, correct the application. For further
guidance, refer to the section on the EXEC Interface
block (EIB) in the CICS Intercommunication Guide. The
EIB describes the state of the session after a request has
been issued.
Module: DFHZARQ
AZI2
been issued but cannot be completed. Possible causes
of the problem include:
v The transaction running in the connected system has
been purged, or
v The transaction running in the connected system has
been timed out, or
v The abending transaction has attempted to SEND
while in RECEIVE state, or
v The abending transaction has attempted to RECEIVE
while in SEND state.
If the abend was caused by DFHIRP rejecting the
transmission request, the dump will contain DFHIRP�s
return code in the field TCTEIRET for the TCTTE
representing the failed IRC session. The address of this
TCTTE is in field B of the trace entry representing the
DFHTC data transmission request.
The meanings of the DFHIRP return codes are given in
the copybook, DFHIRSDS.
User Response: If the cause of the error was a purge
or a time-out, no further action is required.
If the error was caused by a condition such as an
attempted SEND while in RECEIVE state or vice versa,
analyze the dump and correct the protocol violation.
Module: DFHZARQ
AZI3
Explanation: A terminal control request issued by an
application to a remotely-owned terminal failed
because the conversation with the other system failed.
Module: DFHZARQ
AZI4
been issued, but cannot be completed because the other
system has become unavailable for interregion
communication.
User Response: Rerun the transaction when IRC is
available.
Module: DFHZARQ
AZI5
been issued, but the data sent by the connected system
in response to the request violated IRC protocols.
Module: DFHZARQ
AZI6
Explanation: The transaction was connected to
another transaction in another CICS system via an IRC
link. This other transaction has abnormally terminated.
User Response: Correct the cause of the abend in the
connected transaction.
Module: DFHZARQ
AZI7
Explanation: The transaction was processing an MRO
request which involved waiting for a response from a
connected subsystem. The �wait� request was rejected
by the CICS dispatcher.
terminated with a dump.
Module: DFHZIS2
AZI8
Explanation: The error log data received with an
ISSUE-ABEND flow on an IRC connection was not in
the correct format.
Module: DFHZIS1
AZI9
Explanation: The transaction was processing an MRO
request which involved waiting for a response from a
connected subsystem. During the wait, the failing
transaction was purged. The purge can only have been
the result of operator action, such as a CEMT SET
TASK PURGE.
with a dump.
User Response: Investigate the reason the transaction
was purged.
Module: DFHZIS2
AZRA
Explanation: DFHZARRC detected that the address of
an FMH in the APPC was not in the receive buffer. The
cause could either be a storage overwrite or a CICS
1 and 2 trace of the TC component would aid problem
determination. Check the TCTTE in the transaction
dump for printable characters or other signs of a
storage violation error.
Module: DFHZARRC
AZRB
Explanation: Module DFHZARR0 was called with an
invalid first parameter. The first parameter should be
the code of the function to be performed. This is a
CICS logic error.
User Response: If this problem is reproducible, then a
level 1 and 2 trace of the TC component would aid
problem determination. You need further assistance
to proceed.
Module: DFHZARR0
AZRD
Explanation: The logical and physical APPC receive
buffers have become out of step. This problem is
caused either by a storage overwrite or by a CICS
problem determination. Check the TCTTE in the
transaction dump for printable characters or other signs
of a storage violation error.
Module: DFHZARR0
AZRE
Explanation: The logical APPC receive buffer
(addressed by TCTERBLA) starts before or after the
physical receive buffer (addressed by TCTERBLA). This
is not valid as the logical receive buffer is the part of
the physical receive buffer that is yet to be processed.
This problem could be caused either by a storage
overwrite or by a CICS internal logic error.
User Response: If this problem is reproducible then a
problem determination. Check the TCTTE in the
transaction dump for printable characters or other signs
of a storage violation error.
Module: DFHZARR0
AZRF
Explanation: The DFHZUSR state machine has
returned an invalid state error at a point where it
should not be possible. This is a CICS internal logic
error.
to proceed.
Module: DFHZARRF
AZRG
Explanation: The DFHZUSR state machine has
returned an invalid state error at a point where it
should not be possible. This is a CICS internal logic
error.
to proceed.
Module: DFHZARR
AZRH
Explanation: The DFHZARR state variable
RECEIVE_TYPE, used to control receive processing, has
been set to an invalid value. The only other module
that has access to this variable is DFHZARRF. This is a
to proceed.
Module: DFHZARR
AZRI
Explanation: One of the parameters passed to
DFHZARR1. was invalid. This is a CICS internal logic
error.
to proceed.
Module: DFHZARR1
AZRJ
Explanation: The length of a record that DFHZARR0
has been requested to remove from the APPC receive
buffer, is longer than the buffer itself. This problem
could be caused either by a storage overwrite or by a
Module: DFHZARR0
AZRK
Explanation: The DFHLUC parameter list passed back
from DFHZERH to DFHZARRF contained an invalid
combination of LUCCIERR, LUCCIFRE, and
LUCCIRBK fields. This is a CICS internal logic error.

determination. You need further assistance from IBM to
Module: DFHZARRF
AZRL
Explanation: Module DFHZARRF was called with an
Module: DFHZARRF
AZRM
Explanation: Module DFHZARR called one of its own
internal routines at the wrong time. This is a CICS
Module: DFHZARR
AZRN
Explanation: The DFHLUC parameter list passed back
from DFHZERH to DFHZARRF did not have
LUCCIERR set on. This is a CICS internal logic error.
Module: DFHZARRF
AZRO
Explanation: Module DFHZARER was called with an
Module: DFHZARER
AZRP
Explanation: Module DFHZARER detected an invalid
response from DFHZNAC. This is a CICS internal logic
error.
Module: DFHZARER
AZRQ
Explanation: Module DFHZARRA was called with an
invalid parameter. This is a CICS internal logic error.
Module: DFHZARRA
AZRR
Explanation: Module DFHZARRA detected that the
application buffer chained off of a TCTTE at offset
TCTERCSA had a corrupted header. This is caused
either by a CICS logic error or by a storage overwrite.
The exception trace point that accompanies this abend
code gives the TCTTE address.
Module: DFHZARRA
AZRS
Explanation: Module DFHZARRA is unable to acquire
main memory for a new application buffer into which
it is supposed to copy some data. This is because the
DFHLUC receive request is SUBTYPE=LLID, SET=YES
and DFHZARRA does not know the length to acquire
on the GETMAIN. DFHZARRA requires the length of
the record currently being received, but it has been set
to 0 in error. This is a CICS logic error. The exception
trace point that accompanies this abend code gives the
TCTTE address.
Module: DFHZARRA
AZRT
Explanation: Module DFHZARRA has detected that
the application buffer, into which it is supposed to copy
some data, is invalid. This is either because the address
of the buffer is zero or because its length is less than
that of the data to be copied into it. This is a CICS logic
error. The exception trace point that accompanies this
abend code gives the buffer address and length plus
the data address and length.
Module: DFHZARRA
AZRU
Explanation: Module DFHZARRF detected an
unexpected response from DFHZARR0. This is a CICS
logic error. The exception trace point that accompanies
this abend code gives the invalid response code.
to proceed.
Module: DFHZARRF
AZRV
Explanation: Module DFHZARR1 detected an
unexpected response from DFHZARR0. This is a CICS
Module: One of the parameters passed to DFHZARR1
AZRW
Explanation: Module DFHZARRA detected a negative
record length in the TCTTE (field TCTELLC). This is
caused either by a CICS logic error or by a storage
overwrite. The exception trace point that accompanies
this abend code gives the TCTTE address and the value
of TCTELLC.
Module: DFHZARRA
AZRY
Explanation: Module DFHZARR detected an
unexpected response from DFHZARRC. This is a CICS
Module: DFHZARR
AZRZ
Explanation: Module DFHZARR detected an
unexpected response from an internal subroutine. This
is a CICS logic error. The exception trace point that
accompanies this abend code gives the invalid response
code.
Module: DFHZARR
AZR2
Explanation: Module DFHZARRA is unable to acquire
main memory for a new application buffer because the
storage manager GETMAIN failed.
User Response: Use the trace to identify the failing
return from the storage manager and analyze the
reason for failure.
Module: DFHZARRA
AZR3
Explanation: During a GETMAIN request, the storage
domain detected that the task has been purged.
User Response: Use the trace to investigate why the
task was purged. Check if the master terminal operator
was responsible.
Module: DFHZARRA
AZR4
Explanation: An unexpected response has been
received from a dispatcher domain call.
Module: DFHZARER
AZR5
Explanation: An unexpected response has been
received from a dispatcher domain call.
Module: DFHZARR1
AZR6
Explanation: An exception condition was raised as the
result of a request from the APPC communications
routine DFHZARL to the CICS recovery manager
domain. This is either caused by a CICS logic error or
by the inappropriate use of the indoubt test transaction,
CIND. CIND should be activated only on the CICS
system where the syncpoint processing was initiated. In
particular, CIND should not be used on any of the
CICS mirror transactions.
User Response: Determine whether CIND has been
activated for a transaction that did not initiate the
syncpoint processing. If CIND is not being used, you
will need further assistance from IBM to resolve the
Module: DFHZARER
AZS0
Explanation: An invalid request was passed via the
DFHZSTAM macro to the processing DFHZSTAP
program. This is a CICS internal logic error.
Module: DFHZSTAP
AZS1
Explanation: No TCTTE pointer was passed via the
DFHZSTAM macro to the processing DFHZ program.
This is a CICS internal logic error.
Module: DFHZSTAP
AZS2
Explanation: The TCTTE passed via the DFHZSTAM
macro to the processing DFHZSTAP program does not
relate to an MRO or an APPC Conversation. This is a
Module: DFHZSTAP
AZS3
Explanation: The TCTTE passed via the DFHZSTAM
macro to the processing DFHZSTAP program for an
APPC Conversation, but the LUC Extension Control

Block was not located. This is a CICS internal logic
error.
Module: DFHZSTAP
AZS4
Explanation: While processing a DFHZSTAM request
in DFHZSTAP, the DFHZUSRM LUC State Machine
was found to have an invalid setting. This is a CICS
Module: DFHZSTAP
AZS5
Explanation: Whilst processing a DFHZSTAM request
in DFHZSTAP, the Internal State number was found to
have an invalid setting. This is a CICS internal logic
error.
Module: DFHZSTAP
AZS6
Explanation: Whilst processing a DFHZSTAM request
in DFHZSTAP, the Internal State number was found to
have an invalid setting. This is a CICS internal logic
error.
Module: DFHZSTAP
AZTA
Explanation: The task does not own a terminal as its
principal facility.
Module: DFHZTSP
AZTB
Explanation: An attempt to install or delete a remote
terminal in this CICS system has failed. This abend can
also occur if the CITS/CDTS/CMTS/CFTS transactions
are not available (that is , if the transactions have not
been installed).
System Action: DFHZTSP is abnormally terminated
User Response: Verify that the listed transactions exist
and have been installed. If they have, you need further
assistance to resolve this problem. You need further
on how to proceed.
Module: DFHZTSP
AZTC
Explanation: An attempt to install or delete a remote
terminal in this system has failed. This is because a
short-on-storage (SOS) condition has caused the failure
of a GETMAIN for the attach of CITS, CDTS, or CFTS.
User Response: Investigate the reason for the SOS
condition. See the CICS Problem Determination Guide for
guidance on dealing with the SOS condition.
Retry the transaction later.
Module: DFHZTSP
AZTF
Explanation: DFHZTSP tried to GETMAIN or
FREEMAIN a TCTTE whose length (TCTTETEL) is
longer than the largest TCTTE SUBPOOL and is
therefore invalid. This implies a storage violation or a
User Response: Use the transaction dump to identify
the TCTTE in error. First, check whether this is a
storage overwrite. If so, check in your statistics to see if
you are getting a number of storage violations caused
by the same transaction. If this is the case, then a
user-supplied application is probably causing the
problem.
If it is not a storage violation problem, or if there is a
random storage violation, there might be an error in
CICS. In this case, you need further assistance to
resolve the problem. You need further assistance from
proceed.
Module: DFHZTSP
AZTG
Explanation: An attempt has been made to attach a
task on a remotely-owned terminal without an
intersystem TCTTE as its principal facility.
Module: DFHZTSP
AZTH
Explanation: An error response was received from the
remote terminal control macro.
Module: DFHZTSP
AZTI
task on a remotely-owned terminal, but the terminal is
not defined in this system as a remotely-owned
terminal.
Alternatively, another task holds a lock on this
terminal.
User Response: Check the terminal control table
definitions in the systems involved. If the definitions
are correct, check that no other tasks have locks held
on the terminal (CECI, for example).
Module: DFHZTSP
AZTL
task to a remotely-owned terminal that cannot be used
to run this transaction.
Check the terminal control table definitions in the
systems involved.
Module: DFHZTSP
AZTM
Explanation: The data received from the remote
system does not contain an FMH (function
management header).
Module: DFHZTSP
AZTN
Explanation: Conversation with a remote system has
been unexpectedly terminated.
Module: DFHZTSP
AZTO
Explanation: The TCTTE ownership chain is in error.
Module: DFHZTSP
AZTP
Explanation: A BMS TYPE=STORE request issued on
behalf of a remote transaction failed.
System Action: The task abnormally terminates with a
Check that the required BMS support has been
generated.
Module: DFHZTSP
AZTQ
Explanation: Invalid BMS data received from remote
system.
Module: DFHZTSP
AZTR
Explanation: A BMS TYPE=PAGEOUT request issued
on behalf of a remote system failed.
User Response: Ensure that the required BMS support
has been generated.
Module: DFHZTSP
AZTS
Explanation: An attempt to ship data to a remote
system failed.
User Response: Investigate why the conversations
with the remote system failed. The transaction on the
remote system has probably been abnormally
terminated or the session has failed.
Module: DFHZTSP
AZTT
Explanation: An attempt was made to attach a task on
a remote system, but the connection with the remote
system is not an APPC or MRO connection.
User Response: Redefine the connection as APPC or
MRO, or avoid using transaction routing on this
connection.
Module: DFHZTSP
AZTU
Explanation: The task does not own the link TCTTE
after a sync point has been taken.
Module: DFHZTSP
AZTV
Explanation: An invalid function management header
(FMH) has been received from the remote system.
Module: DFHZTSP
AZTW
Explanation: An attempt was made to attach a task on
a remotely-owned terminal that was already running a
task.
User Response: Check the terminal control table
definitions in the systems involved.
Module: DFHZTSP
AZTY
Explanation: A session TCT entry for a remotely
owned APPC terminal or connection could not be
created because to do so would exceed the maximum
number of APPC sessions permitted.
The maximum number of sessions depends on whether
the PTF shipped for APAR PQ27823 is installed. The
basic limit is 46656 and the names are in the range
-AAA to -999. The APAR doubles this limit to 93312
giving an additional range of AAA- to 999-.
User Response: Inform the system programmer. Either
wait for the system to become less busy, or delete some
APPC sessions.
The system programmer should consider increasing the

number of CICS TORs.
Module: DFHZTSP
AZTZ
Explanation: The CICS relay program DFHCRT has
been attached in an unsupported manner.
User Response: The relay transaction executes with an
MRO session or an LU type 6.2 conversation as its
principal facility. Ensure that the transaction is being
attached by APPC terminal sharing logic and not
directly by a user transaction.
If the transaction is being attached by APPC terminal
sharing logic, you need further assistance to resolve
this problem. You need further assistance from IBM to
Module: DFHZTSP
AZT1
Explanation: The task has been attached improperly in
the application-owning region when transaction
routing.
User Response: The conversation with the routing
system should be an MRO session or an LU type 6.2
conversation. Ensure that the transaction is being
attached by the CICS relay program in the connected
system and not by a user program.
If the transaction is being attached by the CICS relay
program in the connected system, you need further
assistance to resolve this problem. You need further
on how to proceed.
Module: DFHZTSP
AZT3
Explanation: The task is being routed back to the
region from where it came.
User Response: Correct the transaction definition.
Module: DFHZTSP
AZT6
Explanation: The task in the application-owning
region has received a ROLLBACK request from the
terminal-owning region, but the conversation is
continuing. The terminal-owning region has violated
the transaction routing protocol.
Module: DFHZTSP
AZT7
Explanation: A session terminal control table (TCT)
entry for a remotely owned APPC terminal or
connection could not be added to the TCT.
Module: DFHZTSP
AZT8
connection could not be deleted from the TCT.
Module: DFHZTSP
AZT9
connection could not be deleted from the TCT because
it is locked by another task.
User Response: The other task may be transitory in
nature, and if so, another attempt will succeed.
Module: DFHZTSP
AZVA
Explanation: DFHZTSP has timed out waiting for
service transaction CITS to complete during the
creation of a remote terminal while attaching a task in
the application-owning region.
The probable cause of this is that the
application-owning region is very busy, so the CITS
transaction has been waiting to be dispatched for
longer than the timeout value allowed by DFHZTSP.
Lack of storage on the target system is one possible
reason why CITS has not been dispatched, or has been
dispatched but has not completed.
User Response: Retry the transaction when the system
becomes less busy. For more information on improving
transaction throughput on the target system, see the
CICS Performance Guide.
Module: DFHZATS
AZVB
Explanation: DFHZCQ has failed to create the remote
terminal definition. A previous message or messages
should indicate the reason for the failure.
User Response: See the previous message or messages
for further guidance.
Module: DFHZATS
AZVC
Explanation: An unexpected error has occurred in
DFHZATS. This is probably caused by DFHZATS being
unable to address the CSA, EIB or the TCA. It can also
occur if DFHZATS is called with an EXEC CICS START
command for transactions CITS, CFTS, CMTS or CDTS.
These are internal CICS transactions and should not be
called in this way.
Module: DFHZATS
AZVD
Explanation: An unexpected error has occurred in the
install procedure of DFHZATS.
User Response: This is a CICS logic error. You need
Module: DFHZATS
AZVE
Explanation: DFHZATS is trying to install a remote
terminal with the same terminal id as an existing TCT
entry.
User Response: Change the terminal names to ensure
that a duplicate does not occur in the same system.
Module: DFHZATS
AZVF
Explanation: One of the remote install or delete
transactions of DFHZATS (CITS, CFTS, CMTS or CDTS)
has been started directly from a terminal. This is not
permitted. These transactions can only be started
internally by CICS.
Module: DFHZATS
AZVG
Explanation: An error has occurred in the remote
delete routines.
Module: DFHZATS
AZVH
delete routine during the mass deletion of remote
terminals.
Module: DFHZATS
AZVI
delete routine while an attempt was being made to
delete a single remote terminal.
User Response: Check the CADL transient data queue
for any associated messages indicating the reason for
the error. If you cannot resolve the problem, you will
need assistance from IBM. You need further assistance
to proceed.
Module: DFHZATS
AZVJ
Explanation: An error has occurred during the mass
deletion of remote terminals. This is caused by a CICS
logic error.
Module: DFHZATS
AZVK
received from the remote delete routine during the
deletion of a single remote terminal.
User Response: Look for an accompanying
DFHZC6911 message indicating the reason for the
delete failure, and take appropriate action.
Module: DFHZATS
AZVL
Explanation: An error has occurred during the mass
flagging of remote terminals for deletion.
Module: DFHZATS
AZVM
Explanation: An error has occurred in DFHZATMF.
This is probably caused by DFHZATMF being unable
to address the CSA, EIB, or the TCA.
Module: DFHZATMF
AZVN
Explanation: The remote delete flag transaction of
DFHZATMF (CRMF) has been started directly from a
terminal. This is not permitted. This transaction can
Module: DFHZATMF
AZVO
Explanation: The remote delete transaction of
DFHZATMD (CRMD) has been started directly from a
terminal. This is not permitted. This transaction can
Module: DFHZATMD
AZVP
Explanation: An error has occurred in DFHZATMD.
This is probably caused by DFHZATMD being unable
to address the CSA, EIB, or the TCA.
Module: DFHZATMD
AZVQ
Explanation: A request to install a shipped terminal
definition has been rejected by the autoinstall user
program.
User Response: Retry the transaction when the system
is less busy.
Module: DFHZATS
AZVR
Explanation: An attempt to install a shipped terminal
definition has failed because the autoinstall user
program has issued an unexpected return code.
User Response: Examine the autoinstall user program
to determine why this return code was issued.
Module: DFHZATS
AZVS
Explanation: An attempt to install a shipped terminal
definition has failed because an error has occurred in
the autoinstall user program.
User Response: Examine the autoinstall user program
to determine the reason for the failure.
Module: DFHZATS
AZVU
Explanation: DFHZATS was attempting to autoinstall
a shipped terminal, a virtual terminal or a shipped
connection and the autoinstall URM was called.
However the autoinstall failed for one of the following
reasons:
v The name returned by the URM in
SELECTED_SHIPPED_TERMID started with one of
these characters:
<
>
-
v The value in the SIT VTPREFIX parameter contained
imbedded blanks or a character that is not allowed
for terminal names.
Module: DFHZATS
AZXA
Explanation: An unexpected error, with reason code 5,
has been detected in the catchup program, DFHZXCU.
See the description of message DFHXG6492 for further
details.
System Action: Console message DFHXG6492 is
issued, and CICS continues after abending the
transaction.
User Response: Refer to message DFHXG6492.
Module: DFHZXCU
AZXB
Explanation: An unexpected error, with reason code 4,
has been detected in the catchup program, DFHZXCU.
See the description of message DFHXG6492 for further
details.
System Action: Console message DFHXG6492 is
issued, and CICS continues after abending the
transaction.
User Response: Refer to message DFHXG6492.
Module: DFHZXCU
Back to top

CICS Abend Codes

Uploaded by

Copyright:

Available Formats

CICS Abend Codes

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CICS Abend Codes

Uploaded by

Copyright:

Available Formats

AACA

Explanation: An invalid error code has been passed to

<B> AALM </B>

ALLOCATE request in that modegroup.

ALLOCATE QUEUE request.

ALLOCATE request in that modegroup.

You need further assistance from IBM to resolve this

Explanation: DFHZARL, or a module called by

ABEND was issued from DFHTPR or DFHTPP then

ABEND then examine the transaction dump for bad

Joined: 05 Nov 2008

ALLOCATE command, or you have not installed the

User Response: You need further assistance from IBM

System Action: An exception trace is made of the

v In a CICS environment, the CEDA transaction is

CICS Problem Determination Guide for guidance on how

Joined: 05 Nov 2008

ACUX and ACUZ.

ACUQ, ACUS and ACU1.

Joined: 05 Nov 2008

ABEND meaning that new transactions that attempt to

AD2V. If DB2 is indoubt about the outcome of the

AD2W. The CICS recovery manager will supersede the

AD2W abend code with abend code ASPR. A

AEID to AEI9, AEXC, AEXF, AEXG, AEXI to AEXL,

AEXV to AEXX, AEX0 to AEX9, AEYA to AEYC, AEYE

Joined: 05 Nov 2008

Joined: 05 Nov 2008

Joined: 05 Nov 2008

Problem Determination Guide for guidance on how to

AJH2 * Abend code AJH2 modified by MPU MEKF

with a CICS transaction dump.

because deadlock timeout is based on total elapsed

ASRA abend is presented to the application. Otherwise,

ASRB abend is presented to the application. Otherwise,

AICA abend is presented to the application. Otherwise,

AICA abend is presented to the application. Otherwise,

Storage Manager domain where the original error was

Joined: 05 Nov 2008

User Response: See the related error message

ANSA An error has occurred obtaining the

with the attribute AMODE(31).

ABEND program is not usable at the time an abend

ACQUIRE error ensure the associated module is in a

Guide for guidance on how to proceed.

APUM, APUN and APUO.

3. The CSD manager (DFHDMP) has passed an

ACTIVITYERR or PROCESSERR (RESP2 27).

Joined: 05 Nov 2008

syncpoint processing. As a result this CICS system is in

ALTERED BY APAR PQ47569 ----------------

AGENT, such as IMS, then this ABEND will be issued

ABEND command cannot handle this abend.

to syncpoint the transaction.

Joined: 05 Nov 2008

A DFHTC TYPE=SIGNAL request with the

that they are reset before the execution of every EXEC

need further assistance from IBM to resolve this

with a CICS transaction dump when the task next