Codigos Cics PDF

IBM z/VSE
Messages and Codes

Volume 3
Version 5
SC34-2634-02
IBM z/VSE
Messages and Codes

Volume 3
Version 5
SC34-2634-02
Note
Before using this information and the product it supports, be sure to read the general information under “Notices” on page
v.
This edition applies to Version 5 of IBM z/Virtual Storage Extended (z/VSE), Program Number 5609-ZV6, and to all
subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SC34-2634-01.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are
not stocked at the addresses given below.
A form for readers' comments is provided at the back of this publication. If the form has been removed, address
your comments to:
IBM Deutschland Research & Development GmbH
Department 3282
Schoenaicher Strasse 220
D-71032 Boeblingen
Federal Republic of Germany
You may also send your comments by FAX or via the Internet:
Internet: s390id@de.ibm.com
FAX (Germany): 07031-16-3456
FAX (other countries): (+49)+7031-16-3456
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright IBM Corporation 1999, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . v DFHLDxxxx messages . . . . . . . . . . 176
Trademarks. . . . . . . . . . . . . . . v DFHLMxxxx messages . . . . . . . . . . 179
DFHMCxxxx messages . . . . . . . . . . 180
Accessibility . . . . . . . . . . . . vii DFHMExxxx messages . . . . . . . . . . 180
DFHMNxxxx messages . . . . . . . . . . 189
Using Assistive Technologies . . . . . . . . vii
DFHPAxxxx messages . . . . . . . . . . 195
z/VSE Information . . . . . . . . . . . . vii
DFHPCxxxx messages . . . . . . . . . . 201
Documentation Format . . . . . . . . . . vii
DFHPDxxxx messages . . . . . . . . . . 202
DFHPGxxxx messages . . . . . . . . . . 205
About This Book. . . . . . . . . . . ix DFHPRxxxx messages . . . . . . . . . . 209
Organization of the Manual . . . . ix . . . . . DFHRCxxxx messages . . . . . . . . . . 210
Where to Find More Information . . ix . . . . . DFHRDxxxx messages . . . . . . . . . . 214
The Message Format . . . . . . ix . . . . . DFHRMxxxx messages . . . . . . . . . . 215
The Message Text Syntax . . . . . xi . . . . . DFHRTxxxx messages . . . . . . . . . . 216
When You Get a Message . . . . . . . . . xii DFHRUxxxx messages . . . . . . . . . . 218
Online Message Descriptions . . . . . . . . xiii DFHSIxxxx messages . . . . . . . . . . . 221
DFHSKxxxx messages . . . . . . . . . . 232
Summary of Changes . . . . . . . . xv DFHSMxxxx messages . . . . . . . . . . 232
DFHSNxxxx messages . . . . . . . . . . 237
DFHnn-Prefix Messages (CICS DFHSOxxxx messages . . . . . . . . . . 243
Transaction Server for VSE/ESA) . . . . 1 DFHSRxxxx messages . . . . . . . . . . 248
DFHSTxxxx messages . . . . . . . . . . 250
Message identifiers . . . . . . . . . . . . 1
DFHSZxxxx (FEPI) messages . . . . . . . . 255
Format of information . . . . . . . . . . . 3
DFHTCxxxx messages . . . . . . . . . . 263
VSE user abend codes . . . . . . . . . . . 5
DFHTDxxxx messages . . . . . . . . . . 268
DFH7xxx (DFHExP) command-level translator
DFHTFxxxx messages . . . . . . . . . . 281
diagnostic messages . . . . . . . . . . . . 7
DFHTIxxxx messages. . . . . . . . . . . 282
DFHACxxxx messages . . . . . . . . . . . 8
DFHTMxxxx messages . . . . . . . . . . 283
DFHAIxxxx messages . . . . . . . . . . . 17
DFHTOxxxx messages . . . . . . . . . . 284
DFHAKxxxx messages. . . . . . . . . . . 17
DFHTPxxxx messages . . . . . . . . . . 287
DFHAMxxxx messages . . . . . . . . . . 18
DFHTRxxxx messages . . . . . . . . . . 293
DFHAPxxxx messages . . . . . . . . . . . 26
DFHTSxxxx messages . . . . . . . . . . 297
DFHBRxxxx messages . . . . . . . . . . . 31
DFHUSxxxx messages . . . . . . . . . . 303
DFHCAxxxx messages. . . . . . . . . . . 31
DFHWBxxxx messages . . . . . . . . . . 305
DFHCCxxxx messages . . . . . . . . . . . 56
DFHWKxxxx messages . . . . . . . . . . 316
DFHCExxxx messages . . . . . . . . . . . 59
DFHXAxxxx messages . . . . . . . . . . 316
DFHCPxxxx messages . . . . . . . . . . . 63
DFHXCxxxx messages . . . . . . . . . . 322
DFHCRxxxx messages . . . . . . . . . . . 72
DFHXGxxxx (XRF general) messages . . . . . 329
DFHDDxxxx messages . . . . . . . . . . 73
DFHXMxxxx messages . . . . . . . . . . 341
DFHDFxxxx messages . . . . . . . . . . . 73
DFHXOxxxx messages . . . . . . . . . . 349
DFHDHxxxx messages . . . . . . . . . . 98
DFHXSxxxx messages . . . . . . . . . . 350
DFHDLxxxx messages . . . . . . . . . . . 99
DFHZCxxxx messages . . . . . . . . . . 356
DFHDMxxxx messages . . . . . . . . . . 101
DFHZExxxx messages . . . . . . . . . . 444
DFHDSxxxx messages . . . . . . . . . . 103
DFHZNxxxx messages . . . . . . . . . . 444
DFHDUxxxx messages . . . . . . . . . . 105
DFHDXxxxx messages . . . . . . . . . . 112
DFHERxxxx messages . . . . . . . . . . 112 Transaction Abend Codes (CICS
DFHEVxxxx messages . . . . . . . . . . 114 Transaction Server for VSE/ESA) . . . 453
DFHEXxxxx messages . . . . . . . . . . 115 abend codes . . . . . . . . . . . . . . 453
DFHFCxxxx messages . . . . . . . . . . 117 Format of information . . . . . . . . . . 454
DFHFExxxx messages . . . . . . . . . . 147 Transaction abend codes. . . . . . . . . . 486
DFHICxxxx messages . . . . . . . . . . 148 System dump codes . . . . . . . . . . . 557
DFHIRxxxx messages. . . . . . . . . . . 150 DHxx (DL/I DOS/VS) abend codes . . . . . . 557
DFHJCxxxx messages . . . . . . . . . . 155 01xx (translator) abend codes . . . . . . . . 558
DFHKCxxxx messages . . . . . . . . . . 171 02xx (DFHPD410) abend codes . . . . . . . 558
DFHKExxxx messages . . . . . . . . . . 172 03xx (DFHCSDUP) abend codes . . . . . . . 558
© Copyright IBM Corp. 1999, 2014 iii

04xx (external CICS interface) abend codes . . . 561
iv z/VSE V5R2 Messages and Codes, Volume 3

Notices
References in this publication to IBM products, programs, or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any of
the intellectual property rights of IBM may be used instead of the IBM product,
program, or service. The evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, are the
responsibility of the user.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785, U.S.A.
Any pointers in this publication to non-IBM websites are provided for convenience
only and do not in any manner serve as an endorsement. IBM accepts no
responsibility for the content or use of non-IBM websites specifically mentioned in
this publication or accessed through an IBM website that is mentioned in this
publication.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Deutschland GmbH
Dept. M358
IBM-Allee 1
71139 Ehningen
Germany
Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
© Copyright IBM Corp. 1999, 2014 v

UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
IPv6/VSE is a registered trademark of Barnard Software, Inc.
vi z/VSE V5R2 Messages and Codes, Volume 3

Accessibility
Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in z/VSE enable users to:
v Use assistive technologies such as screen readers and screen magnifier software
v Operate specific or equivalent features using only the keyboard
v Customize display attributes such as color, contrast, and font size
Using Assistive Technologies

Assistive technology products, such as screen readers, function with the user
interfaces found in z/VSE. Consult the assistive technology documentation for
specific information when using such products to access z/VSE interfaces.
z/VSE Information
z/VSE information is accessible using screen readers with the BookServer/Library
Server versions of z/VSE books in the Internet library at:
http://www.ibm.com/systems/z/os/zos/bkserv/vse.html
One exception is command syntax that is published in railroad track format. If

required, screen-readable copies of z/VSE books with that syntax information are
separately available in HTML zipped file form upon request to s390id@de.ibm.com.
Documentation Format
The publications for this product are in Adobe Portable Document Format (PDF)
and should be compliant with accessibility standards. If you experience difficulties
when you use the PDF files and want to request a web-based format for a
publication, you can either write an email to s390id@de.ibm.com, or use the Reader
Comment Form in the back of this publication or direct your mail to the following
address:
IBM Deutschland Research & Development GmbH
Department 3282
D-71032 Boeblingen
Federal Republic of Germany
In the request, be sure to include the publication number and title.
When you send information to IBM, you grant IBM a nonexclusive right to use or
distribute the information in any way it believes appropriate without incurring any
obligation to you.
© Copyright IBM Corp. 1999, 2014 vii

viii z/VSE V5R2 Messages and Codes, Volume 3
About This Book
This volume of the z/VSE Messages and Codes manual documents the messages
and codes of the CICS Transaction Server for VSE/ESA. The manual describes
which action, if any, should be taken in reply to a message or a code received.
The message and code descriptions are grouped into sections by prefix. The
sections are in alphabetical prefix order, numeric prefixes first.
Organization of the Manual

This manual comprises of three volumes and is separated as follows.
Table 1. z/VSE Messages and Codes Volumes
Volume Prefix
z/VSE Messages and Codes, Volume 1 Prefix 0- through 8-, A- through BSTxxxx -Messages,
VSE/Advanced Functions Codes and SVC Errors,
z/VSE Interactive Interface Codes.
z/VSE Messages and Codes, Volume 2 Prefix DIT- through VMCF- Messages, VSE/VSAM
Return and Error Codes.
z/VSE Messages and Codes, Volume 3, DFHxxnnnn Messages (CICS® Transaction Server
Messages), CICS Transaction Server Abend Codes.
There are three binders available for this book. You can still order these binders
using the following form number: SX33-9020.
Where to Find More Information

This manual references other manuals whenever appropriate.
z/VSE Home Page
z/VSE has a home page on the World Wide Web, which offers up-to-date
information about VSE-related products and services, new z/VSE functions, and
other items of interest to VSE users.
You can find the z/VSE home page at
http://www.ibm.com/systems/z/os/zvse/
You can also find VSE User Examples (in zipped format) at
http://www.ibm.com/systems/z/os/zvse/downloads/samples.html
The Message Format

Each message comprises a partition identifier, a reply ID, the message code, and
the message text. The general format is shown below.
© Copyright IBM Corp. 1999, 2014 ix

. . .
partition + reply message text of the

ID - ID code message
. . .
Type and operator codes

for 0E/0Pxxx messages.
The message code is in the form:

CCCnnnnnA, where:
CCC = Component Identifier (1 to 3
alphanumeric characters).
nnnnn = Message Number (3 to 5
alphanumeric characters).
A = Action Indicator (1 character),
where:
A = Action
D = Decision
E = Eventual Action
I = Information
W = Wait
The action indicator is explained
in more detail below.
The reply-ID is a number between 000

and 999. The operator must use this
number in his reply to the system.
+ = A reply is required immediately.

- = A reply is required.
An * precedes the partition-ID of
those messages that require a reply.
The partition-ID (2 alphanumerics):

BG = Background partition
Fn = Foreground partition
(n = number of this partition)
xn = Dynamic partition
(for example, P1)
AR = Attention Routine
SP = Spervisor
For example, the message:

F1 010 1V17A LST2 SUSPENDED FOR FORMS MOUNT
is to be interpreted in the following way:

F1 indicates that this message is issued by a program executing in the
foreground 1 partition.
010 is the reply-ID for the operator response.
1V indicates that VSE/POWER issued the message.
17 is the message number.
A indicates that an operator response is required.
LST2 SUSPENDED FOR FORMS MOUNT
is the message text.
x z/VSE V5R2 Messages and Codes, Volume 3

In this example, the operator can respond by either restarting or ending the list
writer task LST2.
The Action Indicator

The action indicator specifies the type of action required and can be one of the
following:
Action Indicator
Meaning
A = Action:
The operator must take action before continuing; for example, mounting a
magnetic tape or readying an I/O device.
D = Decision:
The operator must make a logical decision before continuing.
E = Eventual Action:
The operator need not do anything immediately, but will have to
eventually.
I = Information:
Such a message does not require an (immediate) response. It informs the
operator about a condition detected or about the completion of a job, for
example. Certain conditions, however, need to be corrected or removed;
either to run a job successfully or to ensure full system availability again.
In many cases this is a task for the system programmer or the person
responsible for a job rather than for the operator.
W = Wait:
Due to a hardware or system malfunction, the system has entered the wait
state. If, for example, a hardware failure has occurred, the operator may
have to set hardware switches and/or run error recovery programs before
restarting the system via IPL.
For Action Indicators A and D, the program that issued the message usually waits
until the operator enters a response, or performs an action such as readying a
device.
Type/Operator Action Codes

The “t” (type) and “o” (operator action) codes occur in some categories of
supervisor messages. When a message has the following format:
cccct o (message text)
-refer to the beginning of the “cccc” message section for the meanings of “t” and
“o” for those messages.
The Message Text Syntax

Some message texts contain meta-tags, such as square brackets ([]), curly brackets
({}), or the vertical bar (|).
Read these meta-tags like this:

[] (square brackets)
The square brackets surround optional text. The text can be selected one or
zero time.
{} (curly brackets)
The curly brackets surround options separated by vertical bars. One option
must be selected.
About This Book xi

| (vertical bar)
The vertical bar separates different options.
For example, the message text:

PAGEABLE AREA [nnnK] TOO SMALL, INCREASE VALUE OF 'SIZE'
COMMAND/OPERAND [{(JOB-|OUT-|NET-|XMT-|J+O-|N+X-}EXIT
INCLUDED)]
means
v PAGEABLE AREA TOO SMALL, INCREASE VALUE OF 'SIZE'
COMMAND/OPERAND or
COMMAND/OPERAND (JOB-EXIT INCLUDED) or
COMMAND/OPERAND (OUT-EXIT INCLUDED) or
COMMAND/OPERAND (NET-EXIT INCLUDED) or
COMMAND/OPERAND (XMT-EXIT INCLUDED) or
COMMAND/OPERAND (J+O-EXIT INCLUDED) or
COMMAND/OPERAND (N+X-EXIT INCLUDED) or
v PAGEABLE AREA nnnK TOO SMALL, INCREASE VALUE OF 'SIZE'
COMMAND/OPERAND or
COMMAND/OPERAND (JOB-EXIT INCLUDED) or
COMMAND/OPERAND (OUT-EXIT INCLUDED) or
COMMAND/OPERAND (NET-EXIT INCLUDED) or
COMMAND/OPERAND (XMT-EXIT INCLUDED) or
COMMAND/OPERAND (J+O-EXIT INCLUDED) or
COMMAND/OPERAND (N+X-EXIT INCLUDED)
When You Get a Message

Always look up a message, unless you are sure you know the correct response.
You may not have encountered the circumstances of the message before and a
different action may be required. Be sure you read the complete message
description.
If the explanation itself does not seem complete, look at the beginning of the
(sub)component group to which the message belongs. Some groups of messages
follow specific rules.
For example, the messages of component 1 can have a variable digit n in the
fourth character position which indicates the error field in the job control
statement.
Some messages under 0Pxx have additional information attached to them, which is
explained at the beginning of the section covering subcomponent P of component
0.
xii z/VSE V5R2 Messages and Codes, Volume 3

If a message appears repeatedly, and you are unable to continue normal operation,
you should also refer to z/VSE Guide for Solving Problems. This manual describes
problem situations and shows possible solutions.
Online Message Descriptions

When using the z/VSE console , you can display online the message descriptions
shown in the z/VSE Messages and Codes manuals by doing either of the
following:
1. Move your cursor under the message number on the console display and press
the EXPLAIN-key, or:
2. Type in the message number in the command field (==>), then press the
EXPLAIN-key.
Attention:
If you enter the message number in the command field, be sure that you entered a
valid message number before taking any action recommended by the message
description. If the number you entered is not valid, z/VSE may give you a
description of the closest matching number. The action recommended for that
message may not be correct for your task.
If the message description refers to another message, you can view that message's
description by moving the cursor under the message number in the first
description and then pressing the EXPLAIN-key. You can also see online
VSE/VSAM return codes by entering one of the following appropriate actions in
the command line, and pressing the EXPLAIN-key:
v VSAMOPEN
v VSAMCLOS
v VSAMREQU
v VSAMXXCB
With VSE/ESA 2.4 several dummy messages were introduced in messages where
formerly the message explanation referred to the hardcopy manual. These dummy
messages have the prefix VSE followed by 5 digits (e.g. VSE00001) and are used in
message explanations for referring to additional text. The VSE-prefix messages can
not be found in the z/VSE Messages and Codes manuals.
About This Book xiii

xiv z/VSE V5R2 Messages and Codes, Volume 3
Summary of Changes
This volume has been updated to reflect enhancements and changes that are
implemented with z/VSE® 5.2 .
Editorial changes have also been made to various messages and codes.
© Copyright IBM Corp. 1999, 2014 xv

xvi z/VSE V5R2 Messages and Codes, Volume 3
DFHnn-Prefix Messages (CICS Transaction Server for
VSE/ESA)
While CICS is running, it can produce several types of messages:
v Console messages advise the system operator of execution progress, or request a
decision.
v Certain CICS-supplied support programs communicate directly with terminal
operators.
v CICS management modules and support programs log significant events and
error occurrences to transient data destinations, for example, to the control
system master terminal (CSMT).
v The CICS message switching program (DFHMSP) generates message switching
responses (described in the CICS-Supplied Transactions manual).
v CICS directs informational macro notes (mnotes) to programmers (these are not
documented).
v Messages produced by CICS utility programs such as DFH$MOLS and
DFHMNDUP. These messages are self-explanatory and are not documented.
Message identifiers
Message identifiers are of two types. Both are prefixed with "DFH", the IBM®
assigned identifier for CICS modules.
DFH7nnn identifiers
These consist of the prefix "DFH7" followed by a three digit message number. They
indicate messages that have been issued by command-level translators/termc
processing programs.
DFHccnnnn identifiers
These consist of the prefix "DFH" followed by a two-letter component identifier
(cc), and a four-digit message number (nnnn). The component identifier shows the
domain or the component which issues the message. Here is a list of component
identifiers with associated domains and components:
AC The abnormal condition program component
AI The auto-install terminal model manager (AITM)
AK The activity keypoint component
AM The RDO allocation manager
AP The application domain
BR Bridging to 3270 transactions
CA DFHCSDUP and EXEC CICS CREATE
CC The CICS catalog domain (local and global)
CE The sign on program component
CP The CPI Communications component
CR The ISC remote scheduler component
DD The directory manager
DL The DL/I interface component
DM The domain manager domain
DS The dispatcher domain
DU The dump domain
DX The CICS database control component
ER The user backout program
© Copyright IBM Corp. 1999, 2014 1

DFHnn-Prefix messages
EV The sequential I/O component

EX The external CICS interface
FC The file control component
FE The FE terminal test program component
IC The interval control program
IR The interregion component
JC The online journal control component
KC The transaction/profile manager
KE The kernel domain
LD The loader domain
LM The lock manager domain
MC The BMS message control program component
ME The message domain
MN The monitor domain
PA The parameter manager domain
PC The program control program component
PD The print dump exit routine DFHPDX
PG The program manager domain
PR The partner resource manager
RC The Report Controller
RD The RDO allocation manager
RM The recovery manager
RT The ISC transaction routing component
RU The recovery utility program
SI The system initialization component
SK The sub task control program component
SM The storage manager domain
SN The signon component
SO The CICS Sockets domain
SR The system recovery component
ST The statistics domain
SZ The front end programming interface (FEPI)
TC The terminal control program component
TD The transient data component
TF The terminal facility manager
TI The timer domain
TM The system termination program component
TO The terminal object resolution program component
TP The BMS terminal page retrieval program component
TR The trace domain
TS The temporary storage control program component
US The user domain
WB The CICS Web Interface
WK The warm keypoint component
XA The XRF alternate component
XC The XRF CICS availability manager
XG The XRF general component
XM The transaction manager
XO The XRF CICS availability manager
XS The CICS security component
ZC The terminal control working set component
ZE The TCP error message writer component
ZN The syncpoint component
Example: The CICS message DFHAP0002 is issued from the application domain,
identified by the two-character identifier AP.
2 z/VSE V5R2 Messages and Codes, Volume 3

Action codes
Certain messages (for example, DFHFC0922A) include an action code after the
message identifier. Action codes give guidance to the operator of the type of action
needed when the message appears on the system console. The following action
codes are used:
A Immediate action (for example, mount a tape)
D Immediate decision (reply to a request, for example, enter "GO" or
"CANCEL")
E Eventual – action is required, but does not have to be taken immediately
I No action required (If issued via the message domain, these messages can
be suppressed by specifying MSGLVL=0 as a system initialization
override.)
Severity codes
Certain messages, especially those associated with messages to terminal operators
and messages which come from CICS utilities, have a severity code. (DFHST0210 I,
is an example.) A severity code indicates to the operator whether a message is
associated with an error, and if so, how serious it is. The following severity codes
are used:
E Error. Something has gone wrong and action is required of the user before
CICS processing can continue.
I Information only. No action is required.
W Warning. Something may have gone wrong, a program loop for example,
but CICS processing continues.
S Severe error. Something serious has gone wrong and immediate action is
required. CICS processing is suspended until action has been taken.
Format of information
Information about each message is presented in the following format:
v Message identifier – in the form DFHnnnn or DFHccnnnn
v Message text – the words and inserts which make up the message as displayed
in CICS
v Explanation – the events leading to or following the production of the message
v System action – the action that has been or will be taken by CICS
v User response – the action recommended for the user (the console or terminal
operator or system programmer)
v Destination – the device or log to which the message is sent. This is one of the
following:
– Console – refers to a terminal type attached to CICS. (Route codes are 2 and
11 unless otherwise stated.)
– Terminal end user
– SYSLST (System printer)
– One of the following transient data queues:
CADL VTAM® resource definition log
CAIL Autoinstall terminal model manager (AITM) log
CCPI Common programming interface for communications (CPI
Communications) messages
CDUL Transaction dump messages
CMIG Migration log for messages reporting the use of functions that are no
longer supported
CRDI Log for installed resource definitions
CSDL CEDA command log
CSCS Sign on/off security log
CSFL File allocation and related messages
DFHnn-Prefix Messages (CICS Transaction Server for VSE/ESA) 3

CSKL Log for transaction and profile resource definitions

CSMT Write term errors and abends from DFHTACP and DFHACP
CSPL Log for program resource definitions
CSRL Log for partner resource definitions
CSSL Statistics log
CSTL Term I/O error messages from DFHTACP
CSML Sign on/off messages
CSNE Terminal error messages issued from DFHZNAC
CSPW CEPW message log
CSPA Report controller audit log
CSZL FEPI message queue.
v Module(s) – the name(s) of the module or modules that determined that the
message should be sent. (This is not necessarily the module that issued the
macro to write the message.)
XMEOUT parameters –
Messages that can drive the XMEOUT global user exit include a list of XMEOUT
parameters. The XMEOUT exit allows you to suppress or reroute messages that
use the message domain.
A number of console messages should not be rerouted to a transient data queue.

These include all DFHTDnnnn messages and certain DFHXMnnnn and
DFHUSnnnn messages. A note to this effect is included in the descriptions of these
messages.
For programming information about the XMEOUT user exit see the CICS
Customization Guide.
Route codes –
Console messages can be sent to a number of console types. The type of console to
which a particular message is sent is determined by the route code. Each route
code maps onto one console type. The meanings of the route codes normally used
by CICS are as follows:
Code Meaning
1 Master console action – indicates a change in system status demanding
operator action
2 Master console information – indicates a change in system status (system
default)
3 Tape pool status or other tape related information
4 Direct access pool status or other related information
5 Tape library information
6 Disk library information
7 Unit record pool information
8 Teleprocessing control status
9 System security checking
Note: This route code suppresses the operator's reply on the screen and on
SYSLOG
10 System error or maintenance information
11 Programmer information for the VSE log
Unless otherwise stated, console messages have the route codes '2' and '11'.

Terminal identifiers –
Some messages include a terminal identifier (termid) in the message text. This is
normally shown as a 4-character identifier. However, when CICS cannot
completely identify a terminal – for example, when intersystem communication is
taking place, the terminal identifier is prefixed by the application identification
(applid) of the system owning the terminal.
Abend code inserts –

The transaction abend code insert (abcode) in some CICS messages is displayed as
'????' when neither the EXEC CICS ABEND request nor the DFHPC
TYPE=ABEND macro request specifies an abend code.
Dumps –
A dump is generally available for printing when a CICS system abend or abnormal
termination occurs, provided the relevant data set has been specified. The dump
can be used for problem determination.
Terminology –
The terms “abnormally terminates” and “abnormal termination” are frequently
used in a general sense to relate, as applicable, to one of the following:
v The termination of CICS as a result of a VSE ABEND macro. (The term “abend”
may also be used.)
v The termination of a transaction (task) as a result of a CICS transaction ABEND
macro.
VSE user abend codes

DFH messages which accompany a CICS system, utility, or subtask abend have an
associated VSE user abend code. Where possible, the value of this code is the
numeric part of the corresponding DFH message. Thus DFH0305 has an 0305 user
abend code. If a VSE abend code is issued but not the associated CICS message,
the problem probably does not originate with CICS.
The highest possible value of a VSE user abend code is 4095, therefore any DFH
message with a number higher than 4095 has a VSE user abend code that does not
follow the above convention. The following are lists of the abend codes for
messages with numbers above 4095, in order of abend code, and in order of
message number.
Ordered by abend code
0108 DFHCA5263 0185 DFHJC4530

0111 DFHJC4511 0190 DFHXG6450
0112 DFHJC4512 0191 DFHXG6451
0113 DFHJC4501 0192 DFHXG6452
0114 DFHJC4514 0193 DFHXG6453
0115 DFHJC4580 0194 DFHXG6454
0116 DFHJC4582 0195 DFHXG6440
0117 DFHJC4596 0196 DFHXG6441
0118 DFHJC4515 0197 DFHXG6442
0119 DFHJC4519 0198 DFHXG6443

0121 DFHCA5100 0200 DFHXA6540

0123 DFHCA5175 0201 DFHXA6541
0125 DFHCA5180 0202 DFHXG6444
0126 DFHCA5184 0203 DFHXG6430
0127 DFHCA5148 0204 DFHXA6530
0150 DFHER5724 0205 DFHXG6439
0151 DFHER5725 0206 DFHXG6415
0161 DFHAK5802 0207 DFHXA6523
0162 DFHAK5803 0209 DFHXG6427
0170 DFHPS5394 0210 DFHXA6528
0180 DFHJC4597 0213 DFHXG6524
0182 DFHJC4509 0214 DFHXA6580
0183 DFHJC4516 0220 DFHXO6714
0184 DFHJC4534 0221 DFHXO6715
Ordered by message identifier

DFHAK5802 0161
DFHAK5803 0162
DFHJC4501 0113
DFHJC4509 0182
DFHJC4511 0111
DFHJC4512 0112
DFHJC4514 0114
DFHJC4515 0118
DFHJC4516 0183
DFHJC4519 0119
DFHJC4530 0185
DFHJC4534 0184
DFHJC4580 0115
DFHJC4582 0116
DFHJC4596 0117
DFHJC4597 0180
DFHPS5394 0170
DFHXA6523 0207
DFHXA6528 0210
DFHXA6530 0204
DFHXA6540 0200
DFHXA6541 0201
DFHXA6580 0214
DFHXG6415 0206
DFHXG6427 0209
DFHXG6430 0203
DFHXG6439 0205
DFHXG6440 0195
DFHXG6441 0196
DFHXG6442 0197
DFHXG6443 0198
DFHXG6444 0202
DFHXG6450 0190
DFHXG6451 0191

DFHXG6452 0192
DFHXG6453 0193
DFHXG6454 0194
DFHXG6524 0213
DFHXO6714 0220
DFHXO6715 0221
DFHCA5100 0121
DFHCA5148 0127
DFHCA5175 0123
DFHCA5180 0125
DFHCA5184 0126
DFHCA5263 0108
DFHER5724 0150
DFHER5725 0151
Note:
1. All messages which appear in the VSE/POWER job log are prefixed by a time
stamp and job number. Because of this, some messages will have their message
text truncated. If the full message text is required, consult the VSE log as all
messages in the VSE/POWER log are duplicated in the VSE system log.
2. User abend 0225 is internal to CICS. It is issued by DFHDTES when, during
backout, an entry in a hash table has been marked empty where it should not
be possible. This causes the CICS region to be abnormally terminated. If this
abend occurs, you will need help to resolve the problem. See Part 4 of the CICS
Problem Determination Guide for guidance on how to proceed.
DFH7xxx (DFHExP) command-level translator diagnostic messages

Diagnostic messages may be issued by the command-level translator (DFHEAPIø
for assembler language, DFHECPIø for COBOL, DFHEDPIø for C, and DFHEPPIø
for PL/I) in the course of processing programs written in assembler language,
COBOL, C, or PL/I. Assembler-language messages are inserted as macro notes
(MNOTES) in the translator output file and can be seen by either printing or
assembling the translator output file. COBOL, C, and PL/I messages are delivered
to SYSPRINT.
A diagnostic message can have three components: a message number, a severity

code, and message text. Each message is of the form DFH7nnnI c line text where
v nnn is a number,
v I is the information message identifier,
v c is the severity code
v line is the line number of the error and
v text is the text of the message.
In assembler language, COBOL, C, and PL/I, diagnostic messages can be allocated
a severity code. This severity code is represented by a letter that, if present, will
appear in the message immediately following the message number and preceding
the message text. There are five levels of severity. Those for assembler language
and PL/I are different from those for COBOL. The meanings of the codes and the
associated return codes for the languages are as follows:
Assembler, C or PL/I Return code COBOL

U = Unrecoverable 16 D = Disaster
S = Severe 12 E = Error
E = Error 8 C = Conditional

DFH7000I • DFHAC2006
Assembler, C or PL/I Return code COBOL

W = Warning 4 W = Warning
I = Information 0 I = Information
The message text consists of the message itself, which may or may not include
inserts. The inserts are positions within the message text where, in the actual
message, specific information is given on the reasons for the diagnostic message.
Not all the diagnostic messages, however, require inserts.
Messages issued by the command-level translator are usually self-explanatory, and

DFH7000 is an example of this type of message.
is active, the output is directed to SYSLIST.

DFH7000I LISTING FILE CANNOT BE OPENED
User response: Ensure the JCL is correct, or determine what
Explanation: The listing data set was not opened.
is causing the error and preventing opening.
System action: The command-level translator is abnormally
Module: DFHEAPIø (for assembler language), DFHECPIø
terminated and a dump is produced. If the job control option
(for COBOL), DFHEDPIø (for C), DFHEPPIø (for PL/I)
SYSDUMP is active, the output of the dump is directed to the
Destination: Console
dump sublibrary of the partition. If the NOSYSDUMP option
DFHACxxxx messages
Module: DFHACP
DFHAC2001 date time applid Transaction 'tranid' is not
recognized. Check that the transaction name XMEOUT Parameters: date, time,applid, termid, tranid, userid
is correct. Destination: CSMT
Explanation: Either transaction tranid does not exist as an
installed transaction definition, or it is disabled, or it contains
invalid characters. DFHAC2004 time applid Transaction tranid has failed with
abend AKCC. Resource backout was
Note that destination CSMT is used for non-terminal successful.
transactions only. Explanation: Transaction tranid is abnormally terminated
System action: Processing continues. with abend AKCC.
User response: Enter a valid transaction identifier. System action: The transaction (task) is purged.
Module: DFHACP User response: Resubmit the transaction later.
XMEOUT Parameters: date, time,applid, tranid Module: DFHACP
Destination: CSMT and Terminal End User Destination: Terminal End User
DFHAC2002 date time applid To use this transaction tranid DFHAC2005 time applid Transaction tranid has failed with
you must sign on or have the right security abend abcode.
level. Explanation: Transaction tranid has been defined with
Explanation: You are signed on using the default user ID but INDOUBT(WAIT) or INDOUBT(COMMIT) and has been in
this user ID does not have access to the requested transaction. communication with a partner APPC system. A session failure
System action: CICS does not initialize the invoked has occurred while the session was INDOUBT during an
transaction. Other processing continues and message explicit or implicit syncpoint. An immediate resync was
DFHAC2003 is sent to destination CSMT. attempted but could not be completed.
User response: Sign on with an authorized user ID. System action: The task is abnormally terminated with a
Module: DFHACP transaction dump. Unless overridden, APPC resynchronization
Destination: Terminal End User is retried when the remote system is available.
User response: For more information, see “Transaction
Abend Codes (CICS Transaction Server for VSE/ESA)” on
DFHAC2003 date time applid Security violation has been page 453 for a description of the abend code abcode. If
detected term id = termid, trans id = tranid, necessary, resubmit the transaction after the cause of the
userid = userid. abend has been removed.
Explanation: The operator with user ID userid has invoked a Module: DFHACP
transaction tranid at terminal termid for which the operator is Destination: Terminal End User
not authorized.
System action: CICS does not initialize the invoked
transaction. Other CICS processing continues and either DFHAC2006 date time applid Transaction tranid program
message DFHAC2002 or DFHAC2033 is sent to the terminal program name abend primary abcode at termid.
operator. Explanation: The system was unable to execute transaction
User response: Refer to the userid in the preceding message, tranid. termid identifies the terminal which initiated transaction
DFHXS1111 on the CSCS log, to determine the identity of the tranid. If there is no associated terminal, termid appears as
person trying to invoke transaction tranid and the reason for “????”. Program progname is the highest level program and is
the attempt.

DFHAC2007 • DFHAC2015
taken from the installed program definition. abcode is the CICS terminals but the input came from a non-VTAM terminal.
abend code. System action: The input is ignored.
System action: The task is abnormally terminated with a User response: If transaction tranid is to be entered from
dump. terminal termid, ensure that the installed transaction definition
User response: Refer to “Transaction Abend Codes (CICS value of DVSUPRT is compatible with the DFHTCT entry.
Transaction Server for VSE/ESA)” on page 453 for further Module: DFHACP
information on abend code abcode and guidance on how to Destination: Terminal End User
solve the problem. If the code is not available, it is a user code
generated by an EXEC CICS ABEND ABCODE(abcode)
command. This command has been issued by a user program DFHAC2012 date time applid Remote transaction tranid
or by an IBM program (for example, a programming language cannot be run on the local system.
library module). Explanation: Transaction tranid is specified as remote. An
Module: DFHACP attempt to route the transaction to a remote system failed
either because there is no MRO/ISC defined in the running
XMEOUT Parameters: date, time,applid, tranid, program CICS system, or because the remote system name specified in
name,primary abcode, termid the definition of the transaction is the same as that of the local
Destination: CSMT system.
Note that destination CSMT is used for non-terminal
DFHAC2007 date time applid Transaction tranid cannot run transactions only.
as CICS shutdown is in progress. System action: The task is abnormally terminated.
Explanation: Transaction tranid cannot be run during system User response: Ensure that:
quiesce. v MRO/ISC support is correctly defined
System action: The system is in quiesce mode. v The remote transaction definition is correct.
Module: DFHACP
transactions only. XMEOUT Parameters: date, time,applid, tranid
User response: Retry the transaction when CICS is in normal Destination: CSMT and Terminal End User
execution mode, or place an entry for this transaction in the
transaction list table (XLT).
Module: DFHACP DFHAC2014 date time applid Transaction tranid is not
executable because system sysid is not
XMEOUT Parameters: date, time,applid, tranid
available.
Destination: CSMT and Terminal End User
Explanation: Transaction tranid is specified as remote. An
attempt to route the transaction to a remote system failed
DFHAC2008 date time applid Transaction tranid has been because the link is out of service.
disabled and cannot be used.
Explanation: Terminal tranid has been disabled.
transactions only.
Note that destination CSMT is used for non-terminal System action: CICS continues.
transactions only. User response: Wait until the link is available.
System action: Other processing continues. Module: DFHACP
User response: Notify the programmer responsible for this
area that transaction tranid has been disabled. XMEOUT Parameters: date, time,applid, tranid, sysid
Module: DFHACP Destination: CSMT and Terminal End User

Destination: CSMT and Terminal End User DFHAC2015 date time applid Console consname has not been
defined to CICS. Input is ignored.
Explanation: The console operator at the console named
DFHAC2009 date time applid Invalid non-terminal consname has directed a MSG command to the CICS region,
transaction tranid. but no terminal definition for that console is installed in the
Explanation: Transaction tranid has been entered. No terminal
region.
is associated with this transaction. It may be that transaction
System action: The MSG command from the console is
tranid is a disabled transaction, or is one that cannot be run
ignored.
during system quiesce. Alternatively, an invalid transaction
User response: Notify the system programmer, who should
identifier may have been entered.
System action: Other processing continues. use RDO to DEFINE and INSTALL a console definition that
User response: Determine and correct the reason for matches the name of the console.
transaction tranid's invalidity. The system programmer may also consider using 'pooled'
Module: DFHACP consoles by defining TERMINAL definitions with a
XMEOUT Parameters: date, time,applid, tranid CONSNAME of DFHCONxx, or increasing the number of
Destination: CSMT pooled consoles.
Module: DFHACP
DFHAC2010 time applid Transaction tranid is not executable XMEOUT Parameters: date, time,applid, consname
on terminal termid. Destination: CSMT and Terminal End User
Explanation: A conflict has been detected between the
options specified for transaction tranid's definition and those
specified on terminal termid's DFHTCT table entry. For
example, transaction tranid is reserved for the use of VTAM


DFHAC2016 date time applid Transaction tranid cannot run
because program program name is not
available. DFHAC2019 date time applid Transaction tranid does not
Explanation: Transaction tranid is not executable because the support unmapped conversations.
initial program for transaction tranid is not available. Possible Explanation: Transaction tranid received an attach request
reasons for this are: that required the use of the generalized data stream (GDS) to
1. The program is missing. access unmapped conversations, but transaction tranid does
2. The installed program definition is missing. not support the use of the GDS interface.
3. The program is disabled. System action: CICS rejects the attach request.
4. The program name in the installed transaction definition is
invalid. Note that destination CSMT is used for non-terminal
5. The installed transaction has been defined as remote and transactions only.
therefore has no program name, but the name of the User response: Inspect the subsystem that sent the attach
remote system is the same as that of the local system. header to see if the correct transaction was requested. If the
request was correct, check the CICS transaction definition.
Module: DFHACP
transactions only. XMEOUT Parameters: date, time,applid, tranid
System action: Other processing continues. Destination: CSMT and Terminal End User
User response: Determine the cause of the error using the list
given in the Explanation. The response depends on the reason
as follows: DFHAC2020 time applid The conversation type requested
1. Load the program into the CICS program library. by node netname was not recognized.
2. Create an installed program definition for the program. Explanation: CICS received a conversation-type field in an
3. Enable the program. attach header that was not TYPE=MAPPED or
4. Use a valid program name in the installed transaction TYPE=UNMAPPED.
definition. System action: The attach request is rejected.
5. Carry out whichever of the following is appropriate: User response: Notify the system programmer. The validity
v Use a local version of this transaction. of the attach function management header (FMH) should be
v Use the correct remote version of this transaction. checked and the cause of the error identified.
v Log on to the correct system and retry the transaction. Module: DFHACP
Module: DFHACP Destination: Terminal End User
XMEOUT Parameters: date, time,applid, tranid, program name

Destination: CSMT and Terminal End User DFHAC2021 time applid An unsupported Data Blocking
Algorithm (DBA) field in the attach Function
Management Header (FMH) has been
DFHAC2017 date time applid Transaction tranid cannot run received from node netname.
because terminal profile profname for the Explanation: The received attach header contained a value
transaction is not available. for the reserved data blocking algorithm (DBA) field.
Explanation: Transaction tranid is not executable because the System action: The attach request is rejected.
terminal profile for the transaction is not available. This is User response: Notify the system programmer. The validity
because it has not been defined, or it has not been installed. of the attach function management header (FMH) should be
Note that destination CSMT is used for non-terminal checked and the cause of the error identified.
transactions only. Module: DFHACP
System action: Other processing continues. Destination: Terminal End User
User response: Notify the system programmer or system
administrator. DFHAC2022 date time applid Transaction tranid has initiated
Module: DFHACP an incorrect sync point level request.
XMEOUT Parameters: date, time,applid, tranid, profname Explanation: The requested Synclevel does not match the
Destination: CSMT and Terminal End User synclevel negotiated in the Bind request, or Synclevel 2 was
requested, but Lognames were not exchanged.
DFHAC2018 date time applid An unrecognized Process Note that destination CSMT is used for non-terminal
Initialization Parameter (PIP) has been transactions only.
received in ATTACH for transaction tranid. System action: The attach request is rejected.
Explanation: CICS has received an LU type 6.2 attach header User response: Notify the system programmer. The
with invalid process initialization parameters (PIPs). subsystem that sent the attach header should be inspected to
determine that the correct transaction was requested. If it was,
Note that destination CSMT is used for non-terminal the CICS transaction definition should be checked.
transactions only. Module: DFHACP
System action: CICS rejects the attach request.
User response: Inspect the received PIP data and its XMEOUT Parameters: date, time,applid, tranid
associated generalized data stream (GDS) header to determine Destination: CSMT and Terminal End User
why the parameters are invalid.
Module: DFHACP

DFHAC2023 time applid An invalid sync point level has DFHAC2027 date time applid Transaction tranid does not
been requested by node netname. support conversation restart.
Explanation: The synchronization level requested in the Explanation: CICS will not accept LU type 6.2 attach headers
attach header is invalid for the session being used. with restart requested.
System action: The attach request is rejected.
User response: Notify the system programmer. The validity Note that destination CSMT is used for non-terminal
transactions only.
of the attach function management header (FMH) should be
checked and the cause of the error identified. The value of the
synchronization level in the attach header and the bind should User response: Notify the system programmer. The
subsystem that sent the attach header should be inspected to
be compared.
Module: DFHACP determine why restart was requested.
Module: DFHACP
Destination: Terminal End User
DFHAC2024 date time applid A request from node netname
has invalid security parameters.
Explanation: The received attach header did not match the DFHAC2028 date time applid Transaction tranid cannot be
required security parameters specified in the bind. used and has been ignored.
Explanation: The transaction code CSAC or CESC, was
entered from a terminal. This is not allowed.
transactions only.
System action: If the transaction is CSAC, the transaction is
run with no effect. If the transaction is CESC, the transaction
User response: Notify the system programmer. The validity
is abnormally terminated with abend code ATOA.
User response: Ensure that these transactions are not entered
checked and the cause of the error identified. The value of the
from a terminal.
ACC requirements in the attach header and the bind should
Module: DFHACP
be compared.
Module: DFHACP XMEOUT Parameters: date, time,applid, tranid
XMEOUT Parameters: date, time,applid, netname
Destination: CSMT
DFHAC2029 date time applid Transaction tranid is not
DFHAC2025 time applid An invalid Unit of Work executable. The system specified by the
Identification (UOWID) has been supplied dynamic routing program is unavailable.
by node netname. Explanation: Transaction tranid is specified as remote AND
Explanation: The received attach header contained an invalid dynamic. An attempt to dynamically route transaction tranid
unit of work ID (UOWID). Either the format was wrong, or no to the remote system specified by the dynamic routing
UOWID was received when the sync point level required it. program has failed because the link is out of service.
This error may also be raised if no conversation correlator is Note that destination CSMT is used for non-terminal
supplied when it is needed. transactions only.
System action: The attach request is rejected. System action: CICS continues.
User response: Notify the system programmer. The validity User response: Wait until the link becomes available, then try
of the attach function management header (FMH) should be to dynamically route the transaction again.
checked and the cause of the error identified. The value of the Module: DFHACP
UOWID/conversation correlator and the sync point level in
the attach header should be compared. XMEOUT Parameters: date, time,applid, tranid
Module: DFHACP Destination: CSMT and Terminal End User
DFHAC2030 date time applid All sessions are busy. Please
DFHAC2026 time applid An invalid Function Management try again.
Header (FMH) has been supplied by node Explanation: Transaction tranid is specified as remote AND
netname. dynamic. An attempt to dynamically route transaction tranid
Explanation: The length field in the attach header was to the remote system specified by the dynamic routing
invalid. program has failed because no sessions are immediately
System action: The attach request is rejected. available.
User response: Notify the system programmer. The validity Note that destination CSMT is used for non-terminal
transactions only.
checked and the cause of the error identified.
System action: CICS continues.
Module: DFHACP User response: Wait until a session becomes available, then
try to dynamically route the transaction again.
Module: DFHACP
XMEOUT Parameters: date, time,applid


DFHAC2033 time applid You are not authorized to use DFHAC2037 date time applid Transaction tranid is not
transaction tranid. Check that the transaction executable on terminal termid.
name is correct. Explanation: A conflict has been detected between the
Explanation: Either an operator has attempted to execute options specified for the definition of transaction tranid and
transaction tranid while not authorized, or another transaction those specified on terminal termid's DFHTCT table entry. For
attempted to start transaction tranid, which was not authorized example, transaction tranid is reserved for the use of VTAM
for this terminal. terminals but the input came from a non-VTAM terminal.
System action: Other processing continues. Message System action: The input is ignored.
DFHAC2003 is sent to CSMT. User response: If transaction tranid is to be entered from
User response: Either determine why the operator was trying terminal termid, ensure that the installed transaction definition
to execute transaction tranid or enter an authorized transaction value of DVSUPRT is compatible with the DFHTCT entry.
identifier. Module: DFHACP
Module: DFHACP
XMEOUT Parameters: date, time,applid, tranid, termid
Destination: CSMT
DFHAC2034 time applid CICS Logic Error. An invalid error

DFHAC2038 date time applid The conversation type
code has been passed to DFHACP.
requested by node netname was not
Transaction: tranid Terminal: termid.
recognized.
Explanation: An invalid error code has been passed to
Explanation: CICS received a conversation-type field in an
DFHACP.
attach header that was not TYPE=MAPPED or
System action: Transaction tranid is terminated with a
TYPE=UNMAPPED.
transaction dump. The dump code is AACA. Message
DFHAC2035 is sent to CSMT.
User response: Notify the system programmer. The validity
User response: You need further assistance from IBM to
resolve this problem. See Part 4 of the CICS Problem
checked and the failing subsystem identified.
Determination Guide for guidance on how to proceed.
Module: DFHACP
Module: DFHACP
Destination: Terminal End User XMEOUT Parameters: date, time,applid, netname
Destination: CSMT
DFHAC2035 date time applid An invalid error code has
been passed to DFHACP. Transaction tranid is DFHAC2039 date time applid An unsupported Data
terminated. Terminal termid. Blocking Algorithm (DBA) field in the attach
Explanation: An invalid error code has been passed to Function Management Header (FMH) has
DFHACP. been received from node netname.
System action: Transaction tranid is terminated with a Explanation: The received attach header contained a value
transaction dump. A transaction dump is taken. The dump for the reserved data blocking algorithm (DBA) field.
code is AACA. Message DFHAC2034 is sent to the terminal System action: The attach request is rejected.
user.
Message DFHME0116 is normally produced containing the
Message DFHME0116 is normally produced containing the symptom string for this problem.
symptom string for this problem. User response: Notify the system programmer. Check the
User response: You need further assistance from IBM to validity of the attach function management header (FMH), and
resolve this problem. See Part 4 of the CICS Problem identify the failing subsystem.
Determination Guide for guidance on how to proceed. Module: DFHACP
Module: DFHACP
XMEOUT Parameters: date, time,applid, tranid, termid Destination: CSMT
Destination: CSMT
DFHAC2040 date time applid An invalid sync point level

DFHAC2036 date time applid Transaction tranid has failed has been requested by node netname.
with abend AKCC. Resource backout was Explanation: The synchronization level requested in the
successful. attach header is invalid for the session being used.
Explanation: Transaction tranid has abended AKCC. System action: The attach request is rejected.
System action: The transaction (task) is purged.
User response: Resubmit the transaction later. Message DFHME0116 is normally produced containing the
Module: DFHACP symptom string for this problem.
User response: Notify the system programmer. Check the
XMEOUT Parameters: date, time,applid, tranid validity of the attach function management header (FMH), and
Destination: CSMT identify the failing subsystem. Compare the value of the
synchronization level in the attach header and the bind.
Module: DFHACP
Destination: CSMT

DFHAC2041 date time applid An invalid Unit of Work DFHAC2044 date time applid An error occurred while trying
Identification (UOWID) has been supplied to send SYNCPOINT ROLLBACK to
by node netname. terminal termid.
Explanation: The received attach header contained an invalid Explanation: An attempt was made to send a SYNCPOINT
unit of work ID (UOWID). Either the format was wrong, or no ROLLBACK request. A nonzero return code was received by
UOWID was received when the sync point level required it. the sender of the request.
This error may also be raised if no conversation correlator is System action: ABORT processing is initiated for terminal
supplied when it is needed. termid.
System action: The attach request is rejected. User response: Notify the system programmer. Use trace to
find the value of the return code from the SYNCPOINT
Message DFHME0116 is normally produced containing the ROLLBACK request. For IRC, the meaning of the return code
symptom string for this problem.
can be found in the CICS Data Areas.
User response: Notify the system programmer. The validity Module: DFHZIS1
checked and the failing subsystem identified. The value of the XMEOUT Parameters: date, time,applid, termid
UOWID/conversation correlator and the sync point level in Destination: CSMT
the attach header should be compared.
Module: DFHACP
DFHAC2047 date time applid While performing an attach
XMEOUT Parameters: date, time,applid, netname for node netname a security violation was
Destination: CSMT detected.
Explanation: A request to attach a remote transaction failed
due to a security problem. The security fields extracted from
DFHAC2042 date time applid An invalid Function
the attach FMH5 were passed to the security domain to sign
Management Header (FMH) has been
on the user in the remote system, but the signon call failed.
supplied by node netname.
Explanation: The length field in the attach header was
User response: Refer to previous security messages which are
invalid.
written to TDQ CSCS such as DFHSN1604 for further
information and guidance. If no previous messages were
Message DFHME0116 is normally produced containing the issued, examine the trace to determine the reason for the
symptom string for this problem. signon failure. If the userid, password or profile are passed on
User response: Notify the system programmer. Check the the attach FMH5, ensure that they are valid.
validity of the attach function management header (FMH), and Module: DFHACP
identify the failing subsystem.
Module: DFHACP
Destination: CSMT
DFHAC2050 time applid An invalid function management
header (FMH) has been supplied by node
DFHAC2043 date time applid Transaction has been rejected - netname.
CICS system is being recovered. Please wait Explanation: The access security information length field in
for completion of recovery. the attach header is invalid.
Explanation: A request to initiate a transaction was received System action: An exception trace entry containing the
while the CICS system was in the process of recovering the invalid FMH5 is issued. The attach request is rejected.
session following an XRF takeover or persistent sessions User response: Notify the system programmer. Check the
restart. The error is detected by DFHZSUP, which then drives validity of the attach function management header and
DFHACP to issue this message. identify the cause of the error.
Module: DFHACP
Note that destination CSMT is used for non-terminal Destination: Terminal End User
transactions only.
System action: Depending upon the recovery notification
requested for this terminal, the system will send either the DFHAC2051 date time applid An invalid Function
recovery message or initiate the recovery transaction specified Management Header (FMH) has been
on the RECOVNOTIFY option of the typeterm definition for supplied by node netname.
this terminal (see the CICS Resource Definition Guide for Explanation: The Access Security Information length field in
details). the attach header was invalid.
User response: After the recovery notification has been System action: An exception trace entry containing the
received, the user is able to continue operations. invalid FMH5 has been issued. The attach request is rejected.
Module: DFHACP
XMEOUT Parameters: date, time,applid symptom string for this problem.
Destination: CSMT and Terminal End User User response: Notify the system programmer. Check the
validity of the attach function management header (FMH), and
identify the failing subsystem.
Module: DFHACP
Destination: CSMT

Destination: CSMT
DFHAC2052 time applid While performing an attach for
node netname a security violation was
detected. DFHAC2056 time applid You are not authorized to access
Explanation: A password was required in the attach FMH5, this system.
but was missing. A user ID was found, however, because the Explanation: The attach header that was sent to the remote
attach did not specify already verified (AV) or persistent system did not conform to the APPC protocol.
signed-on (PV1), a password should have been present. System action: The attach request is rejected by the remote
System action: An exception trace entry is issued tracing the system and the session is unbound. The remote system will
invalid FMH5. The attach request is rejected. produce messages DFHAC2057 on CSMT and DFHZC4947 on
User response: Notify the system programmer. Inspect the CSNE.
subsystem that sent the attach header to determine why the User response: Inform the system programmer. Investigate
password was not sent. the reason why the attach request failed. See messages
Module: DFHACP DFHAC2057 on CSMT and DFHZC4947 on CSNE issued by
Destination: Terminal End User the remote system for more diagnostic information.
Module: DFHACP
DFHAC2053 date time applid While performing an attach
for node netname a security violation was
detected. DFHAC2057 date time applid While performing an attach
Explanation: A password was required in the attach FMH5, for node netname a security violation was
but was missing. A user ID was found, however, since the detected.
attach did not specify already verified (AV). Explanation: A request to attach a task has been received
System action: An exception trace entry is issued tracing the across an APPC link. However, the FMH attach parameters do
invalid FMH5. The attach request is rejected. not conform to the APPC protocol.
User response: Notify the system programmer. Inspect the System action: The attach request is rejected and the session
subsystem that sent the attach header to determine why the is unbound. An exception trace point (number 1737) for
password was not sent. component TF is issued tracing the invalid attach header
Module: DFHACP (FMH type 5). Message DFHZC4947 is issued.
User response: Investigate the cause of the error which is in
the remote system. Use the FMH5 in the exception trace to
Destination: CSMT
determine why the remote system sent an invalid attach
request. See message DFHZC4947 on CSNE which contains
DFHAC2054 time applid You are not authorized to access sense information to help identify the reason for the failure.
this system.
If the remote system has an earlier release of CICS or CICS on
Explanation: The attach header that was sent to the remote
another platform, you may need to set USEDFLTUSER.
system did not match the required security parameters
Module: DFHACP
specified in the bind.
System action: The attach request is rejected by the remote XMEOUT Parameters: date, time,applid, netname
system and the session is unbound. The remote system issues Destination: CSMT
messages DFHAC2055 on CSMT and DFHZC4946 on CSNE.
User response: Inform the system programmer. Investigate
the reason why the attach request failed. See messages DFHAC2206 time applid Transaction tranid has failed with
DFHAC2055 on CSMT and DFHZC4946 on CSNE issued by abend abcode. Resource backout was
the remote system for more diagnostic information. successful. condmsg
Module: DFHACP Explanation: Transaction tranid is abnormally terminated
Destination: Terminal End User with abend code abcode. All recoverable resources have been
successfully backed out following the abnormal termination.
DFHAC2055 date time applid An attach request from node abcode is either a CICS transaction abend code or a user abend
netname has sent BIND/FMH5 security data code generated by a CICS ABEND ABCODE(abcode)
that is invalid. command. This command is issued either by a user program
Explanation: A request to attach a task has been received or by an IBM program (for example, a programming language
across an APPC link. However, there is an error in the FMH library module).
attach parameters. An attach parameter is present that is not If possible, a conditional message condmsg from the
authorized by the bind security indicators. terminating system will be appended to this message.
System action: The attach request is rejected and the session System action: Message DFHAC2236 is sent to the master
is unbound. An exception trace point (number 1737) for terminal operator (destination CSMT). Normal abend
component TF is issued, tracing the invalid attach header processing continues.
(FMH type 5). Message DFHZC4946 on CSNE contains sense User response: Use the abend code, abcode, to diagnose the
information to help identify the reason for the failure. problem. If the abend is issued by an IBM program product
User response: Investigate the cause of the error which is in other than CICS, the code is documented in the library of that
the remote system. Use the FMH5 in the exception trace, to other product.
request. Resubmit the transaction after the cause of the original abend
Module: DFHACP has been removed.
Module: DFHACP
XMEOUT Parameters: date, time,applid, netname Destination: Terminal End User

'jobname.execname.syslogid' and identifies the EXCI client.

DFHAC2207 time applid Transaction tranid has failed with
Terminal termid represents the connection between the EXCI
abend abcode. Resource backout was
client and CICS rather than a real terminal.
incomplete. condmsg
Explanation: Transaction tranid is abnormally terminated In the case of an MRO or an ISC APPC (parallel sessions),
with abend code abcode. Some changes to recoverable connected system, termid is a terminal identifier (transaction
resources could not be backed out. Other message(s) sent to routing) or a session identifier. The display ends with the
the master terminal operator identify the failure(s) more termination message condmsg issued by the linked CICS
precisely. system.
If possible, a conditional message condmsg from the When this message is issued in the Terminal Owning region
terminating system is appended to this message. because a remote transaction has failed, there may be no
System action: Message DFHAC2237 is sent to the master recoverable resources to be backed out in the local system. In
terminal operator (destination CSMT). Normal abend this case, the conditional message will tell you whether or not
processing continues. resources in the remote system have been backed out.
User response: Examine the CSMT messages for more System action: If possible, message DFHAC2206 is sent to
information. If necessary, disable the affected resources until the terminal user. Normal abend processing continues.
they can be recovered off-line. User response: See the description of the abend code abcode
Module: DFHACP in “Transaction Abend Codes (CICS Transaction Server for
Destination: Terminal End User VSE/ESA)” on page 453 for guidance on how to solve the
problem. If abcode is not a CICS abend, it is a user code, in
which case consult the programmer responsible for this area.
DFHAC2208 time applid Transaction tranid has failed with Module: DFHACP
abend abcode1. Resource backout has also
failed with abend abcode2. condmsg XMEOUT Parameters: date, time,applid, tranid, secondary
Explanation: Transaction tranid is abnormally terminated abcode,program name, termid, {1=EXCI id = }, exci_id, condmsg
with abend code abcode1. Destination: CSMT
An unrecoverable error occurred during backout of the

resources changed by the transaction. This resulted in the DFHAC2237 date time applid Transaction tranid abend
backout failing with abend code abcode2. secondary abcode in program program name term
termid backout failed {EXCI id = }exci_id.
If possible, a conditional message condmsg from the
condmsg
terminating system is appended to this message.
Explanation: Transaction tranid is abnormally terminated
System action: Message DFHAC2238 is sent to the master
with abend code abcode. Some changes to recoverable
terminal operator (destination CSMT). Abend processing
resources could not be backed out due to errors. Other
continues as if dynamic transaction backout had not been
messages sent to the master terminal operator (destination
specified.
CSMT) identify the failure more precisely.
User response: If necessary, disable the affected resources
until they can be recovered off-line. EXCI ID=exci_id is added to the message only when transid is
Module: DFHACP a server transaction running on behalf of a non CICS job using
Destination: Terminal End User the external CICS interface (EXCI). The exci_id consists of
'jobname.execname.syslogid' and identifies the EXEC client
job. Terminal termid represents the connection between the
DFHAC2230 date time applid Transaction tranid terminal
EXCI client and CICS rather than a real terminal.
termid not executed due to I/O error at session
System action: If possible, message DFHAC2207 is sent to
startup. message
the terminal user. Normal abend processing continues.
Explanation: Transaction tranid could not be executed
User response: Examine the CSMT messages for more
because an I/O error occurred in the start up program on
information. If necessary, disable the affected resources until
terminal termid.
they can be recovered off-line.
System action: Transaction tranid is not executed.
Module: DFHACP
User response: Correct the cause of the I/O error, which is
probably due to the terminal not being powered on. XMEOUT Parameters: date, time,applid, tranid, secondary
Module: DFHACP abcode,program name, termid, {1=EXCI id = }, exci_id, condmsg
Destination: CSMT
XMEOUT Parameters: date, time,applid, tranid, termid, message
Destination: CSMT
DFHAC2238 date time applid Transaction tranid abend
primary abcode in program program name term
termid backout abended secondary abcode{ EXCI
secondary abcode in program program name term
id = }exci_id. condmsg
termid backout successful{ EXCI id = }exci_id.
condmsg
with abend code abcode1. An unrecoverable error occurred
during the backout of the resources changed by the
with abend code abcode in program progname. Any changes to
transaction. This resulted in the backout itself failing with
recoverable resources in the local system that have been
abend code abcode2.
performed by the current unit of work are backed out.
EXCI ID=exci_id is added to the message only when transid is
EXEC ID=exci_id is added when tranid is a server transaction
a server transaction running on behalf of a non CICS job using
running on behalf of a non-CICS job using the external CICS
the external CICS interface (EXCI). The exci_id consists of
interface (EXCI). The exci_id consists of the

'jobname.execname.syslogid' and identifies the EXEC client

DFHAC2262 date time applid System sysid sent message
job. Terminal termid represents the connection between the
(sense code cccccccc). tacbmsg
EXCI client and CICS rather than a real terminal.
Explanation: A transaction, which has abnormally
System action: If possible, message DFHAC2208 is sent to
terminated, has received a negative response and an
the terminal user. Abend processing continues as if dynamic
explanatory warning message from system sysid. The message
transaction backout had not been specified.
tacbmsg is supplied from the remote system.
User response: If necessary, disable the affected resources
System action: Processing continues.
until they can be recovered off-line.
User response: Correct the reason for the abnormal
Module: DFHACP
termination in the remote system and run the transaction
XMEOUT Parameters: date, time,applid, tranid, primary again.
abcode,program name, termid, secondary abcode, {1= EXCI id = }, Module: DFHACP
exci_id, condmsg
XMEOUT Parameters: date, time,applid, sysid, cccccccc, tacbmsg
Destination: CSMT
Destination: CSMT

termid DFHPEP not linked.
termid DFHPEP has abnormally terminated.
Explanation: Transaction tranid has abended and the
with abend code abcode. An error occurred in attempting to
abnormal completion program (DFHACP) has linked to the
link to the user-written program error program (DFHPEP).
user-written error program (DFHPEP). The error program has
The error prevented DFHPEP from being given control.
also abended.
If CICS terminates abnormally because of a program control System action: Processing continues.
restart failure, this message can appear during shutdown. User response: The transaction abend code abcode gives the
System action: Depending on the reason for the failure, CICS reason for the original transaction failure. Correct the cause of
may abnormally terminate or continue. the abnormal termination in the error program and run the
User response: The transaction abend code, abcode, gives the transaction again.
reason for the original transaction failure. Module: DFHACP
Determine why DFHPEP could not be invoked. It may be XMEOUT Parameters: date, time,applid, tranid, primary
disabled. abcode,program name, termid
Module: DFHACP Destination: CSMT
XMEOUT Parameters: date, time,applid, tranid, primary

abcode,program name, termid DFHAC2603 Syst.sense systsense,termid,taskid, No
Destination: CSMT authorization
Explanation: An operator has attempted to execute a
transaction for which the operator was not authorized.
DFHAC2260 date time applid Transaction tranid disabled by Alternatively, the operator's authorization was set to the
DFHPEP. capability of the default user and the requested transaction has
Explanation: Transaction tranid, which has abnormally a security value greater than 1.
terminated, has been disabled. This is either as a result of user System action: Other processing continues.
code in DFHPEP, or because the transaction has abended with User response: Either sign on or confirm authority to enter
abend ASRD and DISMACP=YES has been specified (or this transaction as appropriate. See messages DFHAC2002 and
allowed to default) in the system initialization parameters. No DFHAC2003 for further information.
further use can be made of transaction tranid. Module: DFHACP
System action: Processing continues. Destination: Terminal End User
User response: Correct the cause of the abnormal termination
and enable the transaction.
Module: DFHACP DFHAC2605 Syst.sense systsense,termid,taskid, Insufficient
resource
XMEOUT Parameters: date, time,applid, tranid Explanation: The system was unable to execute the
Destination: CSMT transaction at this time.
System action: The transaction is purged.
DFHAC2261 System sysid sent message (sense code User response: Resubmit the transaction later.
cccccccc). 'tacbmsg'. Module: DFHACP
Explanation: A transaction, which has abnormally Destination: Terminal End User
terminated, has received a negative response and an
explanatory warning message from system sysid. The message DFHAC2606 Syst.sense systsense,termid,taskid, Function not
tacbmsg is supplied from the remote system. executable
System action: Processing continues. Explanation: Either the transaction was not valid during
User response: Correct the reason for the abnormal system quiesce, or the transaction has been disabled.
termination in the remote system and run the transaction System action: The system action is error specific. For an
again. invalid transaction during system quiesce, refer to the System
Module: DFHACP Action of message DFHAC2007.
For a transaction that has been disabled, refer to the System

DFHAI0101I • DFHAK5803
Action of message DFHAC2008. has been disabled, refer to the User Response of message
User response: The user response is error specific. DFHAC2008.
Module: DFHACP
For an invalid transaction during system quiesce, refer to the Destination: Terminal End User
User Response of message DFHAC2007. For a transaction that
DFHAIxxxx messages
Explanation: This is an audit log message indicating that a
DFHAI0101I applid AITM initialization has started.
record of the dynamic replacement of autoinstall terminal
Explanation: This is an informational message indicating that
model modelname has been made in the transient data
autoinstall terminal model manager (AITM) initialization has
destination.
begun.
System action: The system continues normally.
System action: Initialization continues.
User response: None.
Module: DFHAITM
Module: DFHAIIN
XMEOUT Parameters: date, time,applid, modelname
XMEOUT Parameter: applid
Destination: CAIL
DFHAI0202I date time applid Terminal Model modelname has

DFHAI0102I applid AITM initialization has ended.
been installed.
autoinstall terminal model manager (AITM) initialization has
record of the dynamic addition of autoinstall terminal model
completed.
modelname has been made in the transient data destination.
System action: CICS initialization continues.
Module: DFHAIIN
Module: DFHAITM
Destination: CAIL
DFHAI0103I applid AITM initialization has failed.

Explanation: Autoinstall terminal model manager (AITM)
been discarded.
initialization has failed.
System action: Message DFHSI1521 is issued and
record of the dynamic deletion of autoinstall terminal model
initialization is terminated. An error message from another
modelname has been made in the transient data destination
domain may also be issued.
using the DISCARD command.
User response: This error is identified by a trace entry. Refer
to DFHSI1521, and any other error message issued, for further
guidance.
Module: DFHAITM
Module: DFHAIIN
Destination: CAIL

been re-installed.
DFHAKxxxx messages
unavailable. The first attempt to take a keypoint causes an
DFHAK5801 date time applid Activity keypoint number nnn
abend with this message.
at time
Explanation: This is a time-stamp message for activity If the cause of the failure is not obvious, use the CICS trace to
keypoint number nnn. determine which CICS service was being invoked at the time
System action: Processing continues. of failure, and which abend code was issued. Read the
User response: None. description of the abend for an explanation of the failure and
Module: DFHAKP suggested action.
Module: DFHAKP
XMEOUT Parameters: date, time,applid, nnn, time
Destination: CSMT XMEOUT Parameter: applid
DFHAK5802 applid Activity keypoint abend
Explanation: An abnormal condition has occurred during DFHAK5803 applid Journal buffer too small for activity
activity keypointing. DFHAKP issues this message when it keypoint
intercepts an abend in any of the CICS services it uses. Explanation: While taking a keypoint, CICS could not write
System action: CICS terminates abnormally with a dump. an essential part of a CICS table to the system journal because
User response: Check any earlier messages for a possible the journal buffer was too small.
cause of this failure. For example, check if the system log is System action: CICS terminates abnormally with a dump.

DFHAM4800I • DFHAM4811E
User response: Reassemble the JCT with a larger BUFSIZE XMEOUT Parameter: applid
specification for the system journal, and restart CICS. Destination: Console
Module: DFHAKP
DFHAMxxxx messages
DFHAM4800I New group grpname created.
Explanation: A new group grpname has been created on the
CSD. DFHAM4806E applid Group name grpname exists as a LIST
System action: Processing continues. name.
User response: None. Explanation: The GRPLIST system initialization parameter
Module: DFHAMP names a list that contains an unusable group name grpname.
Destination: Terminal End User The group name cannot be used because a list of the same
name already exists in the CSD.
DFHAM4801I New list lstname created.
Explanation: A new list lstname has been created on the CSD. Note: A group and a list cannot coexist with the same name.
System action: Processing continues. System action: CICS issues the request 'IS START-UP TO BE
User response: None. CONTINUED? REPLY GO OR CANCEL'.
Module: DFHAMP
If you reply 'GO', CICS is initialized with all the valid
definitions in the list.
User response: If you do not require group grpname, enter
DFHAM4802E applid name is an invalid name. 'GO'.
Explanation: The name name in the command is invalid.
System action: Processing continues. If group grpname is essential, enter 'CANCEL', correct the
User response: Specify a valid name. GRPLIST system initialization parameter and reinitialize CICS.
Module: DFHAMP Then use the CEDA transaction to review and correct the
faulty list.
XMEOUT Parameters: applid, name Module: DFHAMP
Destination: Console and Terminal End User
XMEOUT Parameters: applid, grpname
DFHAM4803E applid Install failed because an existing
definition for file filename could not be
deleted. DFHAM4808E Object already exists in this group.
Explanation: An attempt was made to install file filename. File Explanation: An attempt has been made to define an object
filename already exists and cannot be deleted. This condition in a group, but an object with the same name already exists.
can occur if an existing file definition in an FCT or on the System action: The definition on the CSD is presented to the
CSD, was installed as enabled or open. user to overtype.
System action: The install fails. User response: Reenter the command with a different object
User response: Rectify the problem and try the install again. name, or change the existing definition.
Module: DFHAMP Module: DFHAMP
XMEOUT Parameters: applid, filename Destination: Terminal End User
DFHAM4809E Date/time fields do not match (object
DFHAM4804E applid Invalid LIST name listname. updated by another user).
Explanation: The GRPLIST system initialization parameter Explanation: The definition of an object on the CSD has been
specifies a list name listname that contains characters changed while the user was altering the definition.
unacceptable to RDO. System action: Processing continues.
System action: CICS issues the request 'ENTER User response: Reenter the command.
ALTERNATIVE NAME OR CANCEL'. Module: DFHAMP
User response: Enter a valid list name or enter 'CANCEL', Destination: Terminal End User
correct the GRPLIST system initialization parameter and
reinitialize CICS.
Module: DFHAMP DFHAM4810E Object not found (deleted by another user).
Explanation: The definition of an object on the CSD has been
XMEOUT Parameters: applid, listname deleted while the user was altering the definition.
Destination: Console and Terminal End User System action: Processing continues.
User response: Determine why the definition has been
DFHAM4805E Unable to perform operation: name is locked deleted. Recreate and update the object if necessary.
to APPLID applid, OPID opid to prevent Module: DFHAMP
updating. Destination: Terminal End User
Explanation: An attempt has been made to lock, or update, a
group or a list that is currently locked to another user.
DFHAM4811E applid name1 does not contain name2.
User response: Reenter the command when the group or the Explanation: The required object name2 could not be found
list is not locked. on the CSD in group name1.
Module: DFHAMP System action: Processing continues.

DFHAM4814E • DFHAM4825S
User response: Determine why the definition cannot be

DFHAM4820S Unable to perform request - CSD full.
found.
Explanation: The CSD file DFHCSD is full.
Module: DFHAMP
XMEOUT Parameters: applid, name1,name2 User response: Reenter the command when more space is
Destination: Console and Terminal End User available.
Module: DFHAMP
DFHAM4814E applid List name listname exists as a group
name.
Explanation: The GRPLIST system initialization parameter DFHAM4821S applid Unable to perform request - I/O error
specifies an invalid list name listname. CICS cannot find the to CSD.
list because a group of the same name already exists in the Explanation: An error occurred while the CSD file was being
CSD. accessed during CICS initialization. This may be because the
disk containing the CSD file was mounted incorrectly.
Note: A group and a list cannot coexist with the same name. System action: CICS terminates.
System action: CICS issues the request 'ENTER User response: Retry the CICS initialization. If the problem
ALTERNATIVE NAME OR CANCEL'. persists, a hardware fault probably exists, and you should
User response: Enter a valid list name, or enter 'CANCEL', load a backup copy of the CSD file.
correct the GRPLIST system initialization parameter and Module: DFHAMP
reinitialize CICS. XMEOUT Parameter: applid
Module: DFHAMP Destination: Console and Terminal End User
XMEOUT Parameters: applid, listname
Destination: Console and Terminal End User DFHAM4823S applid Unable to perform request - DFHCSD
not open.
DFHAM4815E Group grpname not found in this list. Explanation: The CSD file (DFHCSD) is not open.
Explanation: The AFTER/BEFORE name entered in the System action: Other processing continues.
command could not be found in this list. The definition could User response: Ask the master terminal operator to open the
have been deleted while the user was viewing the outcome of file. The DFHCSD is defined via system initialization
an EXPAND command. parameters. See the CICS System Definition and Operations
System action: Processing continues. Guide for further details on how to define the CSD file.
User response: Reenter the command with a group name Module: DFHAMP
that exists on this list. XMEOUT Parameter: applid
Module: DFHAMP Destination: Console and Terminal End User
DFHAM4824S applid Unable to perform request -

DFHAM4816E applid Unable to install group grpname - group Insufficient function in file definition for
not found. DFHCSD.
Explanation: The GRPLIST system initialization parameter Explanation: During initialization, CICS has found a
names a list that contains an unusable group name grpname. GRPLIST system initialization parameter, but cannot access the
CICS cannot find group grpname because no resources are CSD file because of an error in the file definition entry for
defined as belonging to it. DFHCSD.
System action: CICS issues the request 'IS START-UP TO BE
CONTINUED? REPLY GO OR CANCEL'. The most likely cause of this error is an incorrectly coded
CSDACC system initialization parameter for the DFHCSD. See
If you reply 'GO', CICS is initialized with all the valid the CICS System Definition and Operations Guide for further
definitions in the list. details.
User response: If you do not require group grpname, enter System action: CICS terminates.
'GO'. User response: Before the next CICS initialization, correct the
If group grpname is essential, enter 'CANCEL', correct the error in the system initialization parameters for DFHCSD.
GRPLIST system initialization parameter and reinitialize CICS. Module: DFHAMP
Then use the CEDA transaction to review and correct the XMEOUT Parameter: applid
faulty list. Destination: Console and Terminal End User
Module: DFHAMP
XMEOUT Parameters: applid, grpname DFHAM4825S applid Unable to perform request - File
Destination: Console and Terminal End User Control has returned an INVREQ response.
Explanation: The file control file request handler (DFHFCFR)
DFHAM4819E Group already exists in this list. does not have sufficient function to support the command
Explanation: The group already exists in the list. entered.
System action: Processing continues. System action: The command is ignored.
User response: Determine why the group exists and reenter User response: You need further assistance from IBM to
the command, perhaps with a different group name. resolve this problem. See Part 4 of the CICS Problem
Module: DFHAMP Determination Guide for guidance on how to proceed.
Destination: Terminal End User Module: DFHAMP

DFHAM4826S • DFHAM4841E

DFHAM4830E restype resname already exists in the target
group.
Explanation: The COPY operation could not be performed, as
DFHAM4826S applid Unable to perform request - CSD a duplicate has been found in the target group.
corrupted or not initialized. System action: The COPY command is ignored.
Explanation: During initialization, CICS found a GRPLIST User response: Reenter the command with the MERGE or the
system initialization parameter but cannot access the CSD file REPLACE option.
because: Module: DFHAMP
1. the CSD file has not been initialized, or Destination: Terminal End User
2. CSD initialization did not complete successfully, or
3. the CSD file has been corrupted.
DFHAM4831E The new name name is longer than the four
System action: CICS terminates.
characters allowed for restype names.
User response: If you have not used the CSD file before,
Explanation: The specified name name is invalid because it is
initialize it using the offline utility, DFHCSDUP, and check the
longer than four characters.
output listing from the utility for successful completion.
System action: The command is ignored.
If you have used the CSD file before, it has probably been User response: Enter a valid name.
corrupted. In this case, load a backup copy of the CSD file and Module: DFHAMP
use it in place of the corrupted file. Destination: Terminal End User
Module: DFHAMP
XMEOUT Parameter: applid DFHAM4839E applid List listname not found.

Destination: Console and Terminal End User Explanation: The system initialization table (SIT) used for
CICS initialization contains a GRPLIST parameter, but CICS
cannot find the list listname in the CSD file.
DFHAM4827S applid Unable to perform request - DFHCSD System action: CICS issues the request 'ENTER
could not be installed. ALTERNATIVE NAME OR CANCEL'.
Explanation: During initialization, CICS finds a GRPLIST User response: Enter a valid list name.
system initialization parameter, but cannot access the CSD file
because file control failed to install it. If no suitable user-defined list exists, you can initialize a
System action: CICS terminates. minimum-function system with GRPLIST=DFHLIST, then use
User response: Before the next CICS initialization, ensure the CEDA transaction to review and correct the faulty list, to
that you have specified the correct system initialization install the required group, and to rebuild a suitable list.
parameters for the definition of the DFHCSD file. Finally, cancel CICS, correct the GRPLIST system initialization
parameter, and reinitialize CICS.
Assemble a new SIT if necessary. Module: DFHAMP
Module: DFHAMP
XMEOUT Parameters: applid, listname
XMEOUT Parameter: applid Destination: Console and Terminal End User
DFHAM4840W Group grpname not appended - group

DFHAM4828E applid Group grpname not found. already exists in target list.
Explanation: The group name grpname in the command could Explanation: The group grpname already exists in the target
not be found. list.
System action: The command is ignored. System action: That definition is not appended.
User response: Retry the command with a group name that User response: None.
exists. Module: DFHAMP
Module: DFHAMP Destination: Terminal End User
XMEOUT Parameters: applid, grpname
Destination: Console and Terminal End User DFHAM4841E applid Install failed because definition of
restype resname is in use by task no. taskno
DFHAM4829S applid Storage violation. CSD primary control (transaction id. tranid).
record not updated. Explanation: An attempt was made to install object definition
Explanation: The in-store version of the CSD file primary restype resname on the CICS system, but the installation failed
record was corrupted. because a read lock was held on that definition by task taskno.
System action: The version on the CSD file was not updated System action: No definitions have been installed.
and is not necessarily affected. User response: Try the command again later.
User response: None. Module: DFHAMP
Module: DFHAMP XMEOUT Parameters: applid, restype,resname, taskno, tranid
XMEOUT Parameter: applid Destination: Console and Terminal End User

DFHAM4842E • DFHAM4852W
DFHAM4842E applid Install failed because restype resname is DFHAM4847W RELOAD(YES) has been specified for
currently in use. program progname referenced by transaction
Explanation: An attempt was made to install object definition tranid in group grpname.
restype resname on the CICS system, but the installation failed Explanation: The CHECK command found a transaction
because the object was in use. definition that referenced a program for which RELOAD=YES
System action: No definitions have been installed. was specified.
User response: Try the command again later. System action: If the definition is installed, CICS will not
Module: DFHAMP release storage for the first program invoked by a transaction.
User response: Specify RELOAD (NO).
XMEOUT Parameters: applid, restype,resname
Module: DFHAMP
Destination: Console and Terminal End User Destination: Terminal End User
DFHAM4843W applid tttttttt nnnnnnnn is internally locked

DFHAM4848W Program progname in group grpname
to OPID opid APPLID applid.
specifies language RPG which is no longer
Explanation: An install has been attempted but the group or
supported on VSE.
list tttttttt nnnnnnnn is internally locked to operator opid on
Explanation: The CHECK command encountered an RPG II
CICS system applid. This could occur at a cold start when the
program definition. RPG II is not supported by CICS
CSD is shared between several CICS regions and operations
Transaction Server for VSE/ESA.
on that group or list are incomplete.
System action: If the definition is installed, the program will
System action: The install continues.
be overwritten and unpredictable results will occur.
User response: Check that the installed definitions
User response: Change or remove the definition.
correspond to your requirements.
Module: DFHAMP
Module: DFHAMP
XMEOUT Parameters: applid, tttttttt, nnnnnnnn, opid, applid
DFHAM4849W NETNAME netname of {CONNECTION |
TERMINAL} rsrcname1 in group grpname1
DFHAM4844W restype resname1 in group grpname1 has the duplicates that of {CONNECTION |
same name as a restype later in group TERMINAL} rsrcname2 in group grpname2.
grpname2. Explanation: The CHECK command found a connection or
Explanation: The CHECK command encountered a duplicate terminal definition with a NETNAME that is the same as the
object name. NETNAME defined in another connection or terminal
System action: None in the CHECK command, but the definition.
earlier definition will be ignored when the definitions are System action: None in the CHECK command. However, it is
installed, because they both belong to the same CICS table in not possible to install two terminals or a terminal and a
which duplicate entries may not exist. connection with the same NETNAME. Also, you cannot have
User response: Determine why the duplicate condition exists two or more APPC links with the same NETNAME, an APPC
and rectify it if necessary. link and an LUTYPE6.1 link with the same NETNAME or two
Module: DFHAMP or more IRC connections with the same NETNAME.
Destination: Terminal End User User response: Determine why the duplication exists and
rectify the problem.
Module: DFHAMP
DFHAM4845W restype1 resname1 referenced by restype2 Destination: Terminal End User
resname2 in group grpname cannot be found.
Explanation: The CHECK command found a reference in a
transaction definition to an object definition that does not DFHAM4850W Transaction ID tranid begins with 'C'. Such
exist. transaction IDs are reserved and may be
System action: None in the CHECK command, but errors redefined by CICS.
may occur if that definition is installed and used. Explanation: Transaction starting with the letter C should be
User response: Determine why the object definition cannot avoided because they are reserved and could be redefined by
be found and rectify it if necessary. CICS.
Module: DFHAMP System action: Processing continues.
Destination: Terminal End User User response: Specify a different transaction identifier.
Module: DFHAMP
DFHAM4846W The xxxxxxxx of transaction tranid1 in group
grpname duplicates that of transaction tranid2
in group grpname. DFHAM4852W restype name resname begins with 'DFH'.
Explanation: The CHECK command found a transaction Such names are reserved and may be
definition with the same alias as another transaction. redefined by CICS.
System action: No system action occurs for the CHECK Explanation: A name beginning with DFH was specified.
command. However, errors may occur if that definition is System action: If the definition is installed, errors may occur.
installed and used. User response: Names beginning with "DFH" are reserved
User response: Determine why the duplicate situation occurs and may be redefined by CICS. You should avoid starting
and rectify it if necessary. names with "DFH".
Destination: Terminal End User Destination: Terminal End User

DFHAM4855W • DFHAM4865S

DFHAM4855W DVSUPRT(VTAM) must be specified for
PROFILE profname referenced by transaction
tranid in group grpname. DFHAM4862W transaction id tranid in group grpname
Explanation: The CHECK command found a definition for a duplicates XTRANID of transaction tranid in
CICS-supplied transaction tranid without DVSUPRT(VTAM) group grpname.
specified in profile progname. Explanation: The check command found a transaction tranid
System action: Unpredictable results will occur if the in group grpname whose XTRANID duplicated a previous
definition is installed and used. transaction ID.
User response: Specify DVSUPRT(VTAM). System action: No system action occurs for the CHECK
Module: DFHAMP command. However, the first transaction in the message will
Destination: Terminal End User be ignored if the definitions are installed.
User response: Determine why the duplication exists and
DFHAM4856W INBFMH(ALL) must be specified for
Module: DFHAMP
PROFILE profname referenced by transaction
tranid in group grpname.
Explanation: The CHECK command found a definition for a
CICS-supplied transaction tranid without INBFMH(ALL) DFHAM4863I name is now locked. No group or list of that
specified in profile progname. name exists.
System action: The system abnormally terminates with abend Explanation: The LOCK command executed successfully, but
code AXFO if the definition is installed and used. no group or list with name name was found on the CSD file.
User response: Specify INBFMH(ALL). System action: The name is locked.
Module: DFHAMP User response: None.
DFHAM4858S applid Unable to perform request - DFHCSD
not enabled. DFHAM4864S applid Unable to perform operation -
Explanation: The GRPLIST system initialization parameter is DFHCSD cannot be opened.
specified, but CICS cannot use the CSD file because it is Explanation: The GRPLIST system initialization parameter is
disabled. specified, but CICS cannot use the CSD file for one of the
System action: CICS terminates. following reasons:
User response: If you want to use the CSD file, ensure that 1. The startup JCL does not contain the definition of the CSD
the system initialization parameters for DFHCSD and your file (DFHCSD).
JCL are specified correctly before the next CICS initialization. 2. The file name or data set name of the CSD file is
Module: DFHAMP incorrectly coded in the startup JCL.
3. VSAM has diagnosed that the CSD file cannot be opened.
User response: The action to solve the problem depends on
the cause as follows:
DFHAM4859S applid Unable to perform request - The value 1. Correct the JCL.
of the CSDSTRNO system initialization 2. Correct the JCL.
parameter is too small. 3. Check the system operator's console for VSAM messages,
Explanation: Insufficient VSAM strings are available to allow and correct all VSAM errors.
CEDA to proceed. Module: DFHAMP
System action: No CEDA commands may be executed.
User response: Wait until other CEDA users have terminated
their sessions, or specify a value for the CSDSTRNO system
initialization parameter of twice the number of concurrent
CEDA transactions. DFHAM4865S applid Unable to perform operation -
Module: DFHAMP DFHCSD currently accessed by another user.
Explanation: The GRPLIST system initialization parameter is
specified, but CICS cannot get read access to the CSD file
because another region is accessing it, and the CSD cluster is
defined to VSAM with SHAREOPTIONS(1).
DFHAM4861W XTRANID of transaction tranid in group System action: CICS terminates.
grpname duplicates transaction ID tranid in User response: To avoid a recurrence of this problem,
group grpname. recreate the CSD file specifying SHAREOPTIONS(2). See the
Explanation: The check command found a transaction tranid CICS System Definition and Operations Guide for further details.
in group grpname whose XTRANID duplicated a previous Module: DFHAMP
transaction ID.
System action: No system action occurs for the CHECK
command. However, the alias will be ignored if the definitions
are installed.
Module: DFHAMP

DFHAM4866E • DFHAM4877W
User response: Set the file using the CEMT SET FILE
DFHAM4866E Unable to perform operation: name is IBM
command.
protected.
Module: DFHAMP
Explanation: The user has attempted to change the contents
of a group or list whose name begins with "DFH". These are XMEOUT Parameters: applid, filename, filename
IBM-protected. Destination: Console and Terminal End User
System action: The command is not executed.
User response: You can copy from IBM-supplied groups or
lists and change the copied group or list. DFHAM4872S applid Unable to connect to CICS catalog.
Module: DFHAMP Explanation: DFHAMP was unable to connect to the CICS
Destination: Terminal End User catalog while attempting to install terminals.
DFHAM4867E File name DFHCSD is reserved and must not resolve this problem. See Part 4 of the CICS Problem
be modified. Determination Guide for guidance on how to proceed.
Explanation: You cannot define the CSD on the CSD itself. Module: DFHAMP
User response: Define DFHCSD via the CSDxxxx system XMEOUT Parameter: applid
initialization parameters. See the CICS System Definition and Destination: Console and Terminal End User
Operations Guide for further details.
Module: DFHAMP DFHAM4873S applid Unable to disconnect the CICS catalog.
Destination: Terminal End User Explanation: DFHAMP was unable to disconnect the CICS
catalog while attempting to install terminals.
DFHAM4868W The LSRPOOLID of the LSRPOOL lsrname System action: CICS terminates.
in group grpname duplicates that of User response: You need further assistance from IBM to
LSRPOOL lsrname in group grpname. resolve this problem. See Part 4 of the CICS Problem
Explanation: When invoking the CEDA CHECK command, Determination Guide for guidance on how to proceed.
an LSRPOOL definition lsrname in group grpname was found Module: DFHAMP
which duplicated the LSRPOOLID of another LSRPOOL. XMEOUT Parameter: applid
System action: Processing continues. Destination: Console and Terminal End User
Module: DFHAMP DFHAM4875E Unable to perform operation: name is
Destination: Terminal End User currently being updated by APPLID applid
OPID opid - please retry later.
Explanation: The command which you issued cannot be
DFHAM4869E Single resource install of restype resname in performed because another user of CEDA is currently
group grpname is not allowed. changing the contents of the group/list to which you referred.
Explanation: The install of restype resname is not allowed via System action: The command is not executed.
single resource install. It must be installed via group install. User response: Try the command again.
System action: The command is not executed. Module: DFHAMP
User response: Install group grpname via group install. Destination: Terminal End User
Module: DFHAMP
DFHAM4876W PARTNER partnername specifies NETNAME
netname which is not found in any
DFHAM4870E applid Install failed for program progname - CONNECTION definition that specifies
language RPG is no longer supported under access method = VTAM.
VSE. Explanation: There is no VTAM connection within the
Explanation: The GRPLIST parameter of the system current group for the netname referenced in the specified
initialization table (SIT) names a list in which a group contains partner.
a program progname that was defined with LANGUAGE(RPG). System action: Other processing continues.
RPG programs are no longer supported. User response: None.
System action: CICS initialization continues. The definition in Module: DFHAMP
error is ignored. Destination: Terminal End User
User response: Redefine program progname with the correct
LANGUAGE definition.
Module: DFHAMP DFHAM4877W PARTNER partnername specifies a
NETNAME and PROFILE for which there is
XMEOUT Parameters: applid, progname no common implied SESSIONs definition.
Destination: Console and Terminal End User Explanation: The netname in a partner definition implies an
associated connection definition which is in turn associated
DFHAM4871W applid File filename has been installed but set with a session definition. The profile definition referenced in a
filename failed. partner definition specifies a modename which can be
Explanation: Setting DSNAME and ENABLED for the associated with a sessions definition.
installed file filename has failed. Within the current group, there is no common sessions
System action: The file is installed but its state is not set. definition implied by the specified partner definition.

DFHAM4879W • DFHAM4887I
System action: Other processing continues.

DFHAM4883I List listname deleted.
Explanation: The list listname has been deleted from the CSD.
Module: DFHAMP
User response: Ensure that the deleted list is not referenced
by any GRPLIST system initialization parameter.
DFHAM4879W Group grpname has been partially installed. Module: DFHAMP
Explanation: During the execution of an INSTALL command Destination: Terminal End User
for the group grpname, some of the elements in the group
installed successfully, but at least one failed.
DFHAM4884S restype name resname is reserved by CICS.
System action: Messages are produced indicating why the
Explanation: The name resname you have selected for
element or elements failed to install.
resource type restype is reserved by CICS and cannot be user
User response: Use the messages already produced to
defined.
determine why the install failed and to rectify the problem.
System action: The command is rejected.
Module: DFHAMP
User response: Redefine resname and resubmit the command.
Module: DFHAMP
DFHAM4880S applid Unable to perform operation - not
allowed by file attributes for DFHCSD.
DFHAM4886I applid Installing list listname which matches
Explanation: The CSDACC system initialization parameter
specified generic list genlist.
for the DFHCSD does not allow CEDA to complete the
Explanation: The GRPLIST system initialization parameter
command entered. The CSDACC parameter specifies the type
specifies a list name genlist that contains generic characters.
of access permitted to the file. This can be one of the
While searching the CSD file, the list name listname was found
following:
to match the specified generic list.
READWRITE
System action: The list name listname is installed.
READONLY
In order for a particular command to function, the access must Module: DFHAMP
be set appropriately.
XMEOUT Parameters: applid, listname, genlist
System action: The CEDA command is ignored.
User response: Correct the value specified for the CSDACC
system initialization parameter.
Module: DFHAMP DFHAM4887I applid Unrecognized resource type found in
the CSD file and has been ignored.
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
DFHAM4881I Group name deleted. can occur for one of the following reasons:
Explanation: The group name has been deleted from the CSD. 1. You are using a CICS release that does not support a type
System action: Processing continues. of definition that was created on the CSD file by a later
User response: Check that the deleted group is not present CICS release.
on any list. 2. The language definition table (DFHEITSP or DFHEITCU) is
Module: DFHAMP invalid for this CICS release.
Destination: Terminal End User 3. The CSD manager (DFHDMP) has passed an invalid CSD
record buffer to DFHPUP. This is a CICS internal logic
error.
DFHAM4882W The {TPNAME | XTPNAME} of transaction System action: The resource is ignored and the operation
tranid in group grpname duplicates the continues.
{TPNAME | XTPNAME} of transaction tranid User response: Determine which of the possible reasons
in group grpname. caused the error. If you can eliminate reasons 1 and 2, you can
Explanation: The CHECK command found a transaction assume that reason 3 applies.
whose XTPNAME matches the TPNAME of another
transaction. Take action corresponding to the reason you have established
System action: No system action occurs for the CHECK as follows:
command, but the XTPNAME or TPNAME for the first 1. Ignore the message.
transaction in the message is ignored if the definitions are 2. Ensure that the library contains versions of DFHEITSP and
installed. DFHEITCU that are valid for the CICS release you are
User response: Determine why the duplication exists. To running.
rectify the problem, rename either the TPNAME or the 3. You need further assistance from IBM to resolve this
XTPNAME. problem. See Part 4 of the CICS Problem Determination
Module: DFHAMP Guide for guidance on how to proceed.

DFHAM4888I • DFHAM4908E
XMEOUT Parameters: applid, tcpipservice,portno

DFHAM4888I Group groupname removed from list listname.
Explanation: During the execution of a DELETE command,
the group groupname was deleted from the CSD. As a result of DFHAM4905E applid Install failed for resource. Option opt is
that, the list listname was updated to remove the deleted not available on this system.
group from it. Explanation: The install of the resource resource has failed
System action: Processing continues. because the current CICS system has not been configured to
User response: None. support the specified option opt.
Module: DFHAMP System action: The install fails.
Destination: Terminal End User User response: Reconfigure the CICS system by specifying
appropriate system initialization parameters to support the
specified option. Then restart CICS.
DFHAM4889S applid Unable to open DFHCSD for
read/write access as CSD has been
Module: DFHAMDH
UPGRADED to CICS release cicsrel.
Explanation: An attempt has been made to open the CSD file XMEOUT Parameters: applid, resource,opt
DFHCSD but the CSD's control record shows that it has been
upgraded to CICS release cicsrel. To prevent loss of data
updates to this CSD can no longer be made by this CICS DFHAM4906W applid Opening TCPIPSERVICE tcpipservice
system. has failed because port portno is not
System action: The command is not executed. authorized.
User response: If the CICS system does not require write Explanation: Opening TCPIPSERVICE tcpipservice has failed
access to the CSD then specify a value of READONLY for the because the specified port number is not authorized.
CSDACC system initialization parameter. Otherwise, make the System action: The resource is installed and left in the closed
necessary changes to the CSD from a cicsrel CICS system. state. The message DFHSO0111 is written to the transient data
Module: DFHAMP queue CSOO.
Destination: Terminal End User User response: Select a port that is authorized. See the
description of message DFHSO0111 for more information.
DFHAM4897W applid The definition of {TCPIPSERVICE} Module: DFHAMP
resourcename specified {STATUS=OPEN} but
the open failed. XMEOUT Parameters: applid, tcpipservice,portno
Explanation: An attempt to install the resource resourcename
on the CICS system has succeeded but the resource cannot be DFHAM4907W applid Opening TCPIPSERVICE tcpipservice
opened. has failed because the IP address is not
System action: The definition is installed. known.
User response: Determine the cause of the failure and then Explanation: Opening TCPIPSERVICE tcpipservice has failed
open the resource. because the specified IP address is not known.
Destination: Console and Terminal End User System action: The resource is installed but left in the closed
Module: DFHAMP state. The message DFHSO0110 is written to the transient data
XMEOUT Parameters: applid, {7=TCPIPSERVICE},resourcename, queue CSOO.
{7=STATUS=OPEN} User response: Select an IP address which is known. Refer to
the description of message DFHSO0110 for more information.
DFHAM4903E applid Install for TCPIPSERVICE tcpipservice Module: DFHAMP
has failed because the service is open.
Explanation: The install of TCPIPSERVICE tcpipservice has XMEOUT Parameters: applid, tcpipservice
failed because the service is open.
System action: The install fails. DFHAM4908E applid Install of DOCTEMPLATE doctemplate1
User response: Close the service and retry the install. failed because TEMPLATENAME(template)
Destination: Console and Terminal End User already exists in DOCTEMPLATE
Module: DFHAMP doctemplate2.
XMEOUT Parameters: applid, tcpipservice Explanation: The install of DOCTEMPLATE doctemplate1 has
failed because the TEMPLATENAME selected is already in use
as the full template name for document template doctemplate2.
DFHAM4904W applid Opening TCPIPSERVICE tcpipservice System action: The install fails.
has failed because port portno is already in User response: Either select a different TEMPLATENAME for
use. doctemplate1, or discard the document template definition for
Explanation: Opening TCPIPSERVICE tcpipservice has failed doctemplate2.
because the specified port number is in use. Destination: Console and Terminal End User
System action: The resource is installed but left in the closed Module: DFHAMDH
state. Message DFHSO0109 is issued to the transient data
queue CSOO. XMEOUT Parameters: applid, doctemplate1,template, doctemplate2
User response: Check that the port number specified is not
already in use. Refer to the description of the message
DFHSO0109 for more information.
Module: DFHAMP

DFHAM4909E • DFHAP0002
DFHAM4909E applid Install of DOCTEMPLATE doctemplate DFHAM4910E applid Install of DOCTEMPLATE doctemplate
failed. LIBRARY(library) not found. failed. MEMBER(membername) not found in
Explanation: The install of DOCTEMPLATE doctemplate has LIBRARY library.
failed because the LIBRARY(library) selected is not the name of Explanation: The install of DOCTEMPLATE doctemplate has
a VSE sublibrary in the JCL for the current CICS job. library failed because member membername was not found in the VSE
should be the name of a VSE sublibrary containing document library library.
templates to be used by the Document Handler domain. System action: The install fails.
System action: The install fails. User response: Ensure that member membername exists in the
User response: Either select a LIBRARY that does exist in the template library before installing the DOCTEMPLATE that
JCL for the current CICS job, or stop and restart CICS with the references it.
required sublibrary added to the LIBDEF statement for the Destination: Console and Terminal End User
CICS job. Module: DFHAMDH
XMEOUT Parameters: applid, doctemplate,membername, library
Module: DFHAMDH
XMEOUT Parameters: applid, doctemplate,library
DFHAPxxxx messages
v If the CICS code is alphameric (for example AKEA), it is a
DFHAP0001 applid An abend (code aaa/bbbb) has occurred
CICS transaction abend code.
at offset X'offset' in module modname.
Explanation: An abnormal end (abend) or program check has v If the CICS code is numeric (for example 1310), it refers to a
occurred in module modname. This implies that there may be CICS message (DFHTS1310 in our example).
an error in CICS code. If the user abend code is from another product refer to the
Alternatively: appropriate messages and codes manual to determine the
v Unexpected data has been input, cause of the abend.
v Storage has been overwritten, or
v There has been a program check within a user program. The entries in the appropriate manuals will give the user
guidance regarding the nature of the error, and may also give
The code aaa is, if applicable, a 3-digit hexadecimal VSE some guidance concerning the appropriate user response.
system completion code, for example 0C1. If an VSE code is
not applicable, this field is filled with three hyphens. The Note: The program check may have occurred in a user
4-digit code bbbb, which follows aaa, is a user abend code program. If this is the case, the program check is usually
produced either by CICS or by another product on the user's followed by an ASRA or an ASRB transaction abend and a
system. transaction dump.
If you want to suppress system dumps that precede ASRA
If X'offset' contains the value X'FFFF', then module modname and ASRB abends, you must specify this on an entry in the
was in control at the time of the abend, but the program status dump table, using either CEMT or an EXEC CICS command.
word (PSW) was not addressing this module. Further guidance on suppressing system dumps can be found
System action: An exception entry is made in the trace table. in the CICS System Definition and Operations Guide.
A system dump is taken, unless you have specifically
suppressed dumps in the dump table. You may need further assistance from IBM to resolve this
problem. See Part 4 of the CICS Problem Determination Guide
Either this is a critical error and CICS is terminated, even if for guidance on how to proceed.
you have specified in the dump table that CICS should not
terminate.
Note: Do not attempt to reroute this message to a transient
Or CICS will continue unless you have specified in the dump data queue.
table that CICS should terminate. Message DFHME0116 is Module: DFHABAB, DFHAFMT, DFHAPDM, DFHAPDN,
normally produced containing the symptom string for this DFHAPEX, DFHAPIQ, DFHAPJC, DFHAPNT, DFHAPSM,
problem. DFHAPST, DFHAPSI, DFHAPRM, DFHAPXM, DFHAPXME,
User response: Notify the system programmer. DFHEDFE, DFHEISR, DFHICXM, DFHSAIQ, DFHSIPLT,
DFHSRP, DFHSTDT, DFHSTFC, DFHSTJC, DFHSTLK,
Look up the VSE code aaa, if there is one, in "OS/390 API DFHSTLS, DFHSTSZ, DFHSTTD, DFHSTTM, DFHSTTR,
Abend Codes" in section "VSE/Advanced Functions Codes & DFHSTTS, DFHSUEX, DFHTDXM, DFHTMP, DFHTSUT
SVC Errors" of z/VSE Messages and Codes - Volume 1.
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
If the modname insert contains the value ????, CICS was Destination: Console
unable to determine which module has abnormally
terminated. In this case, examine the system dump to
determine which area of code has caused the program check. DFHAP0002 applid A severe error (code X'code') has
occurred in module modname.
The user should examine other messages to determine what
Explanation: An error has been detected in module modname.
the module which issued this message was doing at the time
The code X'code' is the exception trace point id which uniquely
the abend occurred. From these messages they can deduce
identifies what the error is and where the error was detected.
which product has produced the abend code bbbb. If bbbb is
System action: An exception entry is made in the trace table
identified as a CICS code, it may be either alphameric or
(X'code' in the message). A system dump is taken, unless you
numeric.

DFHAP0003 • DFHAP0004
have specifically suppressed dumps in the dump table.

DFHAP0004 applid A possible loop has been detected at
If this message is issued from DFHAPEX or DFHSUEX, and offset X'offset' in module modname.
the exit point is XDUREQ, then a system dump is not taken in Explanation: A CICS function is taking more time to process
order to prevent recursive dumping. than CICS expects. A possible loop has been detected in
module modname at offset X'offset'. This is the offset of the
Either this is a critical error and CICS is terminated, even if instruction which was executing at the time the error was
you have specified in the dump table that CICS should not detected.
terminate. System action: An exception entry is made in the trace table.
Or CICS will continue unless you have specified in the dump A system dump is taken, unless you have specifically
table that CICS should terminate. Message DFHME0116 is suppressed dumps in the dump table.
normally produced containing the symptom string for this If this message is issued from DFHAPEX or DFHSUEX, and
problem. the exit point is XDUREQ, then a system dump is not taken in
User response: Notify the system administrator. This failure order to prevent recursive dumping.
indicates a serious error in CICS. If you have not requested
termination in the dump table, you may want to terminate Either this is a critical error and CICS is terminated, even if
CICS. For further information about CICS exception trace you have specified in the dump table that CICS should not
entries, see the CICS Problem Determination Guide. terminate.
You need further assistance from IBM to resolve this problem. Or CICS will continue unless you have specified in the dump
See Part 4 of the CICS Problem Determination Guide for table that CICS should terminate. Message DFHME0116 is
guidance on how to proceed. normally produced containing the symptom string for this
problem.
Note: Do not attempt to reroute this message to a transient User response: Notify the system programmer. If CICS has
data queue. not been terminated, it will be necessary to decide whether the
Module: DFHABAB, DFHAFMT, DFHAPDM, DFHAPDN, problem is serious enough to bring CICS down.
DFHAPEX, DFHAPJC, DFHAPRM, DFHAPSI, DFHAPSIP, Since some CICS functions can use a lot of processor time, this
DFHAPSM, DFHAPST, DFHAPTI, DFHAPTIM, DFHAPTIX, message may have been caused by a long-running function. So
DFHAPXM, DFHAPXME, DFHERM, DFHEISR, DFHICXM, there may not be an error here. Usually, CICS will purge a
DFHPCPG, DFHSIPLT, DFHSTDT, DFHSTFC, DFHSTJC, CICS function which exceeds the runaway task time interval
DFHSTLK DFHSTLS, DFHSTSZ, DFHSTTD, DFHSTTM, which you have specified on the ICVR system initialization
DFHSTTR, DFHSTTS, DFHSUEX, DFHSUZX, DFHTMP, parameter (ICVR is measured in milliseconds). This means
DFHTDXM, DFHXCPA, DFHXSWM, DFHZCUT that the module modname will be terminated and CICS will
XMEOUT Parameters: applid, X'code',modname continue.
Destination: Console But if you have declared ICVR=0 and you consider that
module modname has gone into a loop, you will have to
DFHAP0003 applid Insufficient storage (code X'code') in terminate CICS in order to terminate the runaway function.
module modname. If CICS has terminated module modname, and you consider
Explanation: A CICS GETMAIN was issued by module that it was not a runaway, you should increase the ICVR time
modname, but there was insufficient storage available to satisfy interval. You will have to bring CICS down at a suitable time
the request. to do this permanently. But you can change the ICVR time
The code X'code' is the exception trace point id which uniquely interval temporarily online, using the CEMT transaction.
identifies the place where the error was detected. If raising the ICVR time does not solve the problem, you need
System action: An exception entry is made in the trace table further assistance from IBM to resolve this problem. See Part 4
(code X'code' in the message). A system dump is taken, unless of the CICS Problem Determination Guide for guidance on how
you have specifically suppressed dumps in the dump table. to proceed.
CICS will continue unless you have specified in the dump
table that CICS should terminate.
If appropriate, an error return code is sent to the caller of this data queue.
domain. In this case, CICS could be terminated by the caller Module: DFHAFMT, DFHAPDM, DFHAPDN, DFHAPEX,
(for example, the domain manager, DFHDMDM). A message DFHAPIQ, DFHAPJC, DFHAPSM, DFHAPST, DFHAPSI,
will be issued to this effect. Message DFHME0116 is normally DFHAPRM, DFHAPXM, DFHAPXME, DFHEDFE, DFHEISR,
produced containing the symptom string for this problem. DFHICXM, DFHSAIQ, DFHSIPLT, DFHSTDT, DFHSTFC,
User response: Inform the system programmer. DFHSTJC, DFHSTLK, DFHSTLS, DFHSTSZ, DFHSTTD,
DFHSTTM, DFHSTTR, DFHSTTS, DFHSUEX, DFHTDXM,
Try increasing the size of the DSA or EDSA. See the CICS DFHTSUT
System Definition Guide or the CICS Customization Guide for
further information on controlling CICS storage. XMEOUT Parameters: applid, X'offset', modname
You may need further assistance from IBM to resolve this
for guidance on how to proceed.
Module: DFHAPDM, DFHAPSIP
XMEOUT Parameters: applid, X'code',modname


Module: DFHSIB1
DFHAP0005 applid A hardware error has occurred (module
modname, code X'code'). VSE Store Clock XMEOUT Parameters: applid, modname
found inoperative. Destination: Console
Explanation: A hardware error has occurred during the
running of module module. The store clock facility is the
timing mechanism for the operating system. DFHAP0501 date time applid Program progname has issued
an ADDRESS CSA command that is no
The code X'code' is the exception trace point ID which
longer supported.
uniquely identifies the place where the error was detected.
Explanation: The program progname has attempted to address
System action: An exception entry (code code in the message)
is made in the trace table. A system dump is taken, unless you the CSA. This function is no longer supported. The address
have specifically suppressed dumps in the dump table. returned is now fetch protected. Any attempt to reference this
address results in an abend.
This is a critical error and CICS is terminated, even if you System action: CICS continues.
have specified in the dump table that CICS should not User response: Remove this command from the application
terminate. program. Translate and compile. Remove any references to the
Message DFHME0116 is normally produced containing the address that was previously returned.
symptom string for this problem. Module: DFHEEI
User response: Investigate the store clock to determine XMEOUT Parameters: date, time,applid, progname
whether it is working properly. If this is the cause, you should Destination: CMIG
take the appropriate action to have it repaired or replaced.
In the unlikely event that this is not a hardware problem, you
DFHAP0601 applid Force purge of transaction id tranid
need further assistance from IBM. See Part 4 of the CICS
transaction number trannum has been
Module: DFHZCUT deferred because the transaction is executing
post commit syncpoint processing.
XMEOUT Parameters: applid, modname,X'code' Explanation: CICS has received a request to force purge a
Destination: Console transaction. The target of the force purge request is part way
through processing the second phase of a two phase
syncpoint. If the purge was accepted at this time, the target
DFHAP0100 applid Suffixed module modname cannot be
transaction would be abended and this would cause CICS to
loaded. Enter new suffix, 'YES'(unsuffixed),
fail with a U0408 abend. There is no way of purging the target
'NONE'(dummy), or 'CANCEL'
Explanation: During AP domain initialization, a suffixed transaction while it is in this state. Transactions should only
CICS module or table could not be loaded. remain in this state for a short period of time. A subsequent
System action: The AP domain initialization routines wait for attempt to force purge the transaction may preempt the
the operator to: deferred abend issued by the system when this condition was
v Enter an alternative two-character suffix, detected. This would result in the transaction being purged
v Enter 'YES' to request the unsuffixed version, from the system faster than if the deferred purge is left to take
v Enter 'NONE' to request that a dummy version of the effect.
program or table be loaded, or System action: CICS defers the purge until the target
v Enter 'CANCEL'. transaction is no longer protected against purge.
User response: Retry the purge after a short interval if the
If 'CANCEL' is entered, CICS is abnormally terminated at
target transaction has not ended.
the end of the nucleus process.
User response: Determine whether the suffix is correct. If it is
not, enter one of the replies listed in the "System Action". Note: Do not attempt to reroute this message to a transient
data queue.
If you enter 'CANCEL', correct the error by adding the Module: DFHAPXME
module to the appropriate library and then restart CICS.
Module: DFHSIB1 XMEOUT Parameters: applid, tranid,trannum
XMEOUT Parameters: applid, modname
DFHAP0602 applid Force purge of transaction id tranid
transaction number trannum has been
DFHAP0101 applid Suffixed module modname cannot be deferred because the transaction is executing
loaded. transaction backout.
Explanation: During AP domain initialization, a suffixed Explanation: CICS has received a request to force purge a
CICS module or table could not be loaded. This message is transaction. The target of the force purge request is part way
issued for all suffixable modules which cannot be located after through transaction backout processing (either as a result of an
CANCEL has been specified in response to a preceding earlier transaction abend, or a syncpoint rollback request). If
DFHAP0100 message. the purge was accepted at this time, the target transaction
System action: The AP domain initialization continues until would be abended and this would cause CICS to fail with a
the end of the nucleus load process. CICS is then abnormally U0405 abend. There is no way of purging the target
terminated with a dump. transaction while it is in this state. Transactions should only
User response: Determine whether the suffix is correct. If it is remain in this state for a short period of time. A subsequent
not, either correct the SIT or name the correct suffix via an attempt to force purge the transaction may preempt the
override for the next initialization of CICS. Otherwise correct deferred abend issued by the system when this condition was
the error by adding the module to the appropriate library. detected. This would result in the transaction being purged

from the system faster than if the deferred purge is left to take program progname. DISABLE the exit program from all exit
effect. points by using the EXITALL operand in the EXEC CICS
System action: CICS defers the purge until the target DISABLE command, and correct the error.
transaction is no longer protected against purge.
Refer to the CICS Customization Guide for further information
User response: Retry the purge after a short interval if the
about coding user exit programs.
target transaction has not ended.
If you think there is no loop, you can increase the runaway
Note: Do not attempt to reroute this message to a transient task time interval by using the CEMT SET SYSTEM
data queue. RUNAWAY() command. This is explained in the CICS-Supplied
Module: DFHAPXME Transactions manual.
Module: DFHSUEX, DFHUEH
XMEOUT Parameters: applid, tranid,trannum
Destination: Console XMEOUT Parameters: applid, progname, xxxxxxxx
DFHAP0701 applid An abend (code abcode) has occurred in

exit program progname at exit point xxxxxxxx. DFHAP0705W date time applid The enable of task related
Explanation: An abnormal end (abend) or program check has user exit program progname has caused CICS
occurred in the program progname. This implies that there is to force taskdataloc(below) for all
an error in the error program, that unexpected data has been transactions.
input, or storage has been overwritten. Explanation: Task-related user exit program progname has
been enabled with options TASKSTART and LINKEDITMODE,
The code is a three digit hexadecimal VSE code (if applicable), and progname has been linkedited AMODE 24. This ensures
followed by a four digit alphanumeric CICS code. The VSE that it is always invoked in AMODE 24. An AMODE 24
code is a system completion code, for example 0C1. If an VSE task-related user exit program can only be invoked if the
code is not applicable, this field is filled with three hyphens. calling transaction is defined with TASKDATALOC(BELOW).
The CICS code is an abend code or a number referring to a
CICS message (for example, AKEA is a CICS abend code; 1310 By enabling the AMODE 24 task-related user exit for task
refers to message DFHTS1310). start, the user has forced CICS to force all subsequent
System action: CICS makes an exception entry in the trace transactions to run with TASKDATALOC(BELOW).
table and returns a zero return code to the exit point. CICS System action: CICS continues, but for the remainder of the
also produces a system dump unless: CICS run, CICS insists that all transactions run with
v You have specifically suppressed dumps in the dump table, TASKDATALOC(BELOW).
or User response: To avoid all transactions having to run with
v The exit point is XDUREQ. No dump is taken in order to TASKDATALOC(BELOW), modify the task-related user exit so
avoid recursive dumping. that it is capable of running AMODE(31) when invoked for
task start.
Either CICS continues unless you have specified in the dump Ideally the task-related user exit should be modified so that it
table that CICS should terminate. always runs AMODE 31 for whoever is the caller. In this case
the exit program can be linkedited with the AMODE 31
Or This is a critical error and CICS is terminated, even if you attribute, and enabled with the LINKEDITMODE option. This
have specified in the dump table that CICS should not ensures CICS always invokes it in AMODE 31.
terminate. If this is the case, a zero return code is returned to
Alternatively the task-related user exit could be modified so it
the CICS management module. is capable of being invoked in either addressing mode. In this
User response: There might be a logic error in the user exit case the exit should be enabled without the LINKEDITMODE
program progname. DISABLE the exit program from all exit option. This means the exit will be invoked in the amode of its
points, by using the EXITALL operand in the EXEC CICS caller. For CICS calls such as task start, this will always be
DISABLE command, and correct the error. AMODE 31, but it does allow the exit to be invoked AMODE
24 for calls from an AMODE 24 application if this is desired.
For programming information about coding user exit
programs see the CICS Customization Guide. See the CICS Resource Definition Guide for more information on
Module: DFHSUEX, DFHUEH the TASKDATALOC option.
XMEOUT Parameters: applid, abcode,progname, xxxxxxxx See the CICS Customization Guide for programming
Destination: Console information on the LINKEDITMODE option when enabling
task-related user exits.
Module: DFHUEM
DFHAP0704 applid A possible loop has been detected in
exit program progname at exit point xxxxxxxx. XMEOUT Parameters: date, time,applid, progname
Explanation: The exit program progname was in control and Destination: Console and Transient Data Queue CSMT
the transaction has consumed more CPU time than has been
specified in the ICVR. There is probably a loop. DFHAP0706 applid A probable loop has been detected in
System action: CICS returns a zero return code to the exit task related user exit program progname.
point. CICS also produces a system dump unless Explanation: The task related user exit program progname
v You have specifically suppressed dumps in the dump table, was in control and the transaction has consumed more CPU
or time than the value specified for the ICVR system
v The exit point is XDUREQ. No dump is taken in order to initialization parameter. There is probably a loop.
avoid recursive dumping. System action: CICS produces a system dump unless you
User response: There is a probable logic error in the user exit have specifically suppressed dumps in the dump table.

User response: There is a probable logic error in the task v The required modules in the CSD have been defined (these
related user exit program progname. DISABLE the exit program modules are listed in the file CEECCSD which is supplied
and correct the error. in the z/VSE sublibrary PRD2.SCEEBASE).
Module: DFHAPLI
Refer to the CICS Customization Guide for programming
information about task-related user exit programs. XMEOUT Parameters: applid, rc
If there is no loop, you can avoid this problem by increasing
the runaway task time interval using the CEMT SET SYSTEM
RUNAWAY() command. This is explained in the CICS-Supplied DFHAP1203I applid Language Environment for z/VSE is
Transactions manual.
being initialized.
Module: DFHERM
Explanation: This is an informatory message indicating that
XMEOUT Parameters: applid, progname CICS is initializing support for the Language Environment for
Destination: Console z/VSE.
System action: System initialization continues.
User response: None. You can suppress this message with
DFHAP0707 applid An abend (code abcode) has occurred in the system initialization parameter, MSGLVL=0.
task related user exit program progname. Module: DFHAPLI
Explanation: An abnormal end (abend) or program check has
occurred in the task related user exit program progname. This XMEOUT Parameter: applid
implies that there is an error in the exit program, that Destination: Console
unexpected data has been input, or storage has been
overwritten.
DFHAP1212 date time applid The program program_name
The code is a three digit hexadecimal VSE code (if applicable), was defined as language1 but CICS has
followed by a four digit alphanumeric CICS code. The VSE redefined it as language2.
code is a system completion code, for example X'0C1'. If an Explanation: You have defined program program_name as
VSE code is not applicable, this field is filled with three
language1. During validation CICS determined that language1 is
hyphens. The CICS code is an abend code or a number
not a valid language for program_name and has redefined the
referring to a CICS message (for example, AKEA is a CICS
program with language2.
abend code; 1310 refers to message DFHTS1310).
System action: CICS makes an exception entry in the trace CICS is able to determine the program language automatically.
table and produces a system dump unless you have It is therefore not necessary for users to pass the language of a
specifically suppressed dumps in the dump table. program to CICS via an autoinstall exit.
CICS continues unless you have specified in the dump table System action: Processing continues.
that CICS should terminate. User response: None. This message is issued for information
User response: There might be a logic error in the task only.
related user exit program progname. DISABLE the task related Module: DFHAPLI
user exit program and correct the error.
XMEOUT Parameters: date, time,applid, program_name,
For programming information about coding task related user language1,language2
exit programs see the CICS Customization Guide. Destination: CSTL
Module: DFHERM
XMEOUT Parameters: applid, abcode,progname DFHAP1213 applid An unexpected error has occurred
Destination: Console during language initialization.
Explanation: An error was detected when CICS tried to load
one of the required language interface modules.
DFHAP1200 applid A CICS request to the Language
Environment for z/VSE has failed. Reason During the language initialization phase of CICS startup, an
code rc. unexpected error has occurred while CICS was initializing the
Explanation: CICS has attempted to communicate with necessary support. Possibly CICS has determined that there is
Language Environment for z/VSE, but due to an error, the insufficient storage to enable run-time language support to be
function requested by CICS could not be performed. correctly installed. Application program execution is likely to
System action: If the error occurs during system be severely restricted if CICS continues.
initialization, then the initialization continues but without
support for the Language Environment for z/VSE. If the error
User response: You should examine the console log for any
occurs in a user application program, then the transaction is
error messages which may have been issued by the operating
abnormally terminated.
system immediately preceding this CICS message. If no
User response: For an explanation of the Language
Environment for z/VSE return code rc, refer to the IBM operating system messages were issued, it is likely that there
Language Environment for z/VSE, Debugging Guide and Run-Time is insufficient storage for CICS to continue and you should
Messages restart CICS with a larger value specified for the DSALIM
If the error occurs during system initialization, check that the Module: DFHAPLI
Language Environment for z/VSE modules and the modules
required for the languages supported by that environment XMEOUT Parameter: applid
have been correctly installed. In particular ensure that: Destination: Console
v The interface module CEECCICS has been placed in a
sublibrary specified in the LIBDEF search chain of the CICS
startup job stream

DFHBR0201 • DFHCA5104W
DFHBRxxxx messages
User response: Use the abend code abcode to diagnose the
DFHBR0201 date time applid Transaction tranid abend abcode
problem. If the abend is issued by an IBM program product
in bridge exit brexit bridge transaction bridge
other than CICS, the code is documented in the library of that
Explanation: The Bridge exit brexit terminated abnormally
other product.
with abend code abcode.
Alternatively, there might be a logic error in the bridge exit
abcode is either a CICS transaction abend code or a user abend
program brexit.
code generated by a CICS ABEND ABCODE(abcode)
command. This command is issued either by a user program For programming information about coding bridge exit
or by an IBM program (for example, a programming language programs see the CICS Customization Guide.
library module). Module: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC,
DFHBRXM, DFHBRRM
Unless the abend occurred whilst the bridge exit was
processing the termination or abend call, this abend will also XMEOUT Parameters: date, time, applid, tranid, abcode, brexit,
result in CICS issuing a ABRQ abend. In this case a bridge
DFHAC2236 abend message will follow this message. See that Destination: CSMT
message for details about recoverable resources.
System action: Abend ABRQ will be issued unless the
transaction is calling the bridge exit for termination or abend
processing.
DFHCAxxxx messages
DFHCA5100S date time applid netname tranid Severe error in DFHCA5103I Error(s) occurred while processing command
module modname. Abend code: abcode command.
Explanation: An internal error has occurred in module Explanation: The CSD utility either found a syntax error in
modname, when invoked by a CSD utility command. the utility command command, or the command command
System action: Processing terminates abnormally with an failed to execute correctly.
operating system dump and abend code abcode. The CSD System action: Utility command execution is terminated.
utility attempts to:
1. Close any files previously opened internally. If commands are being read from a SYSIPT data stream by the
2. Unload any extract exit routines that were dynamically utility, subsequent commands (except LIST) are checked for
syntax only. (If the primary CSD file cannot be opened, LIST is
loaded.
not processed either.)
3. Invoke the termination exit routine (if supplied).
4. Return control to the invoker of the utility. If commands are being read from a get-command exit, then
User response: See the description of abend code abcode in DFHCSDUP attempts to process subsequent commands.
“Transaction Abend Codes (CICS Transaction Server for User response: If the command failed because of syntax
VSE/ESA)” on page 453 for guidance on how to solve the errors, correct the command.
problem.
If the command failed to execute correctly, this may have been
Module: DFHCAP, DFHCSDUP
caused by a previous error. In such a situation, an associated
XMEOUT Parameters: date, time,applid, netname, tranid, error message, such as DFHCA5275, should have been issued.
modname, abcode Refer to these error messages for further guidance.
Destination: CSMT Correct all errors before trying to open the CSD file again.
Module: DFHCSDUP
DFHCA5101I command command executed successfully. Destination: SYSLST
Explanation: The execution of a CSD utility command
command completed successfully. DFHCA5104W Subsequent commands (except LIST) are not
System action: Normal processing continues. executed because of error(s) above.
User response: None. Explanation: After the CSD utility program encounters an
Module: DFHCSDUP error, it ceases to execute any further commands read from a
Destination: SYSLST data stream (as opposed to supplied by a Put-Message exit
routine). However, it continues to check the syntax of
DFHCA5102I Warning messages issued while processing subsequent commands. The exception is the LIST command,
command command. which will still be executed if the primary CSD file can be
Explanation: The CSD utility issued messages during opened.
syntax-checking and execution of the command command. System action: Subsequent CSD utility commands (except
System action: Normal utility processing continues to the LIST) are ignored.
end of the job. User response: Check for a syntax error in the commands
User response: Review the warning messages to see how used and correct it.
they have affected utility processing. Then decide whether you There should be associated error messages which identify the
need to submit a further CSD utility job. problem that caused DFHCSDUP to halt active processing.
Module: DFHCSDUP These messages should appear in DFHCSDUP output before
Destination: SYSLST message DFHCA5104 is issued.
Module: DFHCSDUP
Destination: SYSLST

DFHCA5105W • DFHCA5120I
Destination: SYSLST
DFHCA5105W command Command not executed because of
previous error(s).
Explanation: If a syntax error (or an execution error) DFHCA5114S The {primary | secondary} CSD has not been
occurred in a command read from a data stream and initialized. Command not executed.
processed earlier, no further commands (except for LIST Explanation: The primary CSD file must be initialized before
commands) are executed. If the primary CSD file could not be any CSD utility command (other than the INITIALIZE or
opened, the LIST command is not executed either. SERVICE commands) can be processed. If a secondary CSD
System action: The CSD utility command is not executed. file is used, it must always be initialized before this command
User response: Check for syntax errors or execution errors in can be processed. CICS issues this message if you try to break
commands processed earlier. either of these rules, or if an attempt to initialize a CSD file
Correct the invalid commands. fails to complete successfully
Module: DFHCSDUP System action: The CSD utility ignores the command.
Destination: SYSLST User response: Initialize the CSD file. You may first have to
determine why a previous initialization attempt failed.
Module: DFHCSDUP
DFHCA5107I Commands executed successfully: nn Destination: SYSLST
Commands giving warnings: nn Commands
in error: nn
Explanation: The CSD utility has completed input command DFHCA5115S The primary CSD is already initialized.
processing. Command not executed.
Explanation: An INITIALIZE or a SERVICE command was
Commands giving warnings may or may not have been encountered but the primary CSD file has already been
executed successfully. initialized.
System action: Normal processing continues to the end of the System action: The INITIALIZE or SERVICE command is
job. ignored.
User response: If any CSD utility commands in error were User response: Confirm that the correct CSD file was
executed, decide if the results are what you want. specified.
Module: DFHCSDUP
If they are NOT what you want, correct them and resubmit Destination: SYSLST
them in another job.
If any commands were not executed, you must resubmit them.
DFHCA5116S The primary CSD has been defined with an
(See message DFHCA5108.)
invalid key length. Processing is terminated.
Module: DFHCSDUP
Explanation: The CSD utility cannot initialize the CSD file
Destination: SYSLST
because it has been defined to VSAM with an invalid key
length.
DFHCA5108I Commands not executed after error(s): nn System action: The CSD file remains uninitialized, and no
Explanation: The CSD utility has completed input command utility commands are processed.
processing. The number of commands not executed because of User response: Delete the CSD file, using VSAM Access
errors is indicated by nn. Method Services (AMS). In the JCL defining the CSD cluster,
System action: Normal processing continues to the end of the change the AMS control statements to specify KEYS(22 0). Use
job. this JCL to redefine the CSD file, and use the CSD utility to
User response: Correct the commands in error and resubmit reinitialize it.
them in another job. Module: DFHCSDUP
Module: DFHCSDUP Destination: SYSLST
Destination: SYSLST
DFHCA5117S The primary CSD has been defined with an
DFHCA5109I End of DFHCSDUP utility job. Highest invalid record size. Processing is terminated.
return code was: retcode Explanation: The CSD utility cannot initialize the CSD file,
Explanation: The CSD utility job is complete. because it has been defined to VSAM with an invalid record
System action: Control returns to the invoker, that is, either length.
the operating system or to an invoking program. System action: The CSD file remains uninitialized, and no
User response: None. utility commands are processed.
Module: DFHCSDUP User response: Delete the CSD file, using VSAM Access
Destination: SYSLST Method Services (AMS). In the JCL defining the CSD cluster,
change the AMS control statements to specify
RECORDSIZE(100 500). Use this JCL to redefine the CSD file,
DFHCA5110W Error found in 'PARM=' parameter data on and use the CSD utility to reinitialize it.
EXEC job step. This data is ignored. Module: DFHCSDUP
Explanation: The value of the PARM parameter on the EXEC Destination: SYSLST
job in the JCL to run the DFHCSDUP utility is incorrect.
System action: The PARM parameter is ignored. The CSD is
opened for read and write operations. DFHCA5120I {primary | secondary} CSD opened;
User response: Correct the erroneous PARM value. The FILENAME: filename
incorrect value can be found in the job step. Explanation: The VSAM data set specified in the JCL has
been successfully opened, and is identified as the primary or
The CICS Operations and Utilities Guide describes how to code secondary CSD file. (All utility commands processed will use
the PARM parameter. the same primary CSD file. Different secondary CSD files may
Module: DFHCSDUP be accessed by different utility commands.)

DFHCA5121S • DFHCA5129S
System action: Normal processing continues.

DFHCA5125S Error occurred while closing the CSD. File is
full; FILENAME: filename
Module: DFHCSDUP
Explanation: After processing the CSD utility commands, the
Destination: SYSLST
CSD control records are updated before closing the data set.
Updating failed because data set filename was full.
DFHCA5121S I/O error while opening {primary | secondary} System action: Utility command processing is terminated.
CSD; FILENAME: filename User response: Initialize a new primary CSD file with a
Explanation: An I/O error occurred when reading or writing larger data set size. Then use the VSAM Access Method
control records of the VSAM data set identified in the JCL as Services (AMS) IMPORT and EXPORT commands to restore
the primary or secondary CSD file. the CSD file onto a larger data set.
System action: The utility command is not executed. Module: DFHCSDUP
User response: Retry the utility command that failed. If the Destination: SYSLST
problem persists, restore the CSD file from your own backup
procedures.
Module: DFHCSDUP DFHCA5126S I/O error while closing the {Primary |
Destination: SYSLST Secondary} CSD; FILENAME: filename
Explanation: An I/O error occurred when reading or writing
the control records of the CSD file, before closing VSAM data
DFHCA5122S VSAM error while opening {primary | set filename.
secondary} CSD; FILENAME: filename System action: No further utility commands are executed.
Explanation: A VSAM error occurred when opening the data User response: Resubmit the utility commands that failed. If
set identified in the JCL as a primary or secondary CSD file. the problem persists, restore the CSD file from your own
System action: The utility command is not executed. backup procedures.
User response: Refer to the VSAM diagnostics output in Module: DFHCSDUP
message DFHCA5179 for further information and guidance. Destination: SYSLST
Module: DFHCSDUP
Destination: SYSLST
DFHCA5127S VSAM error while closing {Primary |
Secondary} CSD; FILENAME: filename
DFHCA5123I {primary | secondary} CSD closed; FILENAME: Explanation: A VSAM error occurred when closing the data
filename set filename in the JCL as the primary or secondary CSD file.
Explanation: The VSAM data set used as the primary or System action: No further CSD utility commands are
secondary CSD file has been successfully closed, with control executed.
records updated if necessary. (The primary CSD file is closed User response: Refer to the VSAM diagnostics output in
after all the utility commands have been processed; the message DFHCA5179 for further information and guidance.
secondary CSD file is closed after the command for which it Module: DFHCSDUP
was opened.) Destination: SYSLST
Module: DFHCSDUP DFHCA5128S Processing terminated. {Primary | Secondary}
Destination: SYSLST CSD accessed by another user and could not
be shared. FILENAME: filename
Explanation: The CSD cluster has been defined with
DFHCA5124S Processing terminated. Corrupted CSD SHAREOPTIONS that restrict its concurrent use. The offline
control record detected while closing CSD; utility program is currently unable to open the CSD file.
FILENAME: filename System action: The utility command is not executed.
Explanation: A storage corruption is preventing the CSD User response: Wait until the CSD file becomes available
control records from being updated when the CSD file is being again (in accordance with the SHAREOPTIONS rules defined
closed. for the cluster).
System action: No further CSD utility commands are
processed.
User response: Obtain a dump from DFHCSDUP together Note: You can also specify PARM=CSD(READONLY) if LIST
with a listing of the DFHCSDUP run and its JCL. Also try to is the only command you want to execute.
obtain a print out of the CSD, using either the VSAM Access Module: DFHCSDUP
Method Services (AMS) PRINT command or the DFHCSDUP Destination: SYSLST
command LIST ALL. The LIST will indicate where the errors
have occurred because they do not print and are therefore
DFHCA5129S {Primary " Secondary} CSD filename has been
easily identifiable.
upgraded to CICS release cicsrel.
Using the information available, determine the cause of the Explanation: An attempt has been made to open data set
errors and correct them. filename as the primary or secondary CSD file but the CSD's
control record shows that it has been upgraded to CICS
Resubmit the CSD utility commands that failed.
release cicsrel. To prevent loss of data updates to this CSD can
If you cannot resolve the problem, or if the problem persists, no longer be made by this CICS system.
you will need further help from IBM. See Part 4 of the CICS System action: The utility command is not executed.
Problem Determination Guide for guidance on how to proceed. User response: If the DFHCSDUP job does not require write
Module: DFHCSDUP access to the CSD then re-run the DFHCSDUP job specifying
Destination: SYSLST PARM=CSD(READONLY). However, if the DFHCSDUP job
does require write access to the CSD then use the CICS cicsrel

DFHCA5130E • DFHCA5142E
version of DFHCSDUP to make the necessary updates to the repeat the INITIALIZE request. If this fails, you will need
CSD. further assistance from IBM. See Part 4 of the CICS Problem
Module: DFHCSDUP Determination Guide for guidance on how to proceed.
Destination: SYSLST Module: DFHCSDUP
Destination: SYSLST
DFHCA5130E Unable to locate module DFHCICS. Primary

CSD not initialized. DFHCA5135I Group grpname added to list listid
Explanation: The DFHCICS module is missing from the Explanation: A group definition grpname has been
library. satisfactorily created on the CSD file in list listid.
System action: Processing of the INITIALIZE command is System action: Processing continues.
terminated. User response: None.
User response: Ensure that the DFHCICS module is present Module: DFHCSDUP
in the library. Destination: SYSLST
Module: DFHCSDUP
Destination: SYSLST
DFHCA5136W Group grpname is already a member of list
listid
DFHCA5131I List listid created. Explanation: Group grpname already exists in list listid. CICS
Explanation: The INITIALIZE command has created the does not create a duplicate entry.
header for an IBM-protected list. System action: Normal utility processing continues.
System action: Normal processing continues. User response: None.
User response: None. Module: DFHCSDUP
Destination: SYSLST
DFHCA5140I Total xxxxxxxx definitions created: nn

DFHCA5132S Unable to create list listid Explanation: CICS issued this message after migrating a
Explanation: The INITIALIZE command has failed when CICS table. nn definitions of type xxxxxxxx have been created
calling the CSD manager routing program, DFHDMP, to create on the CSD file.
a new list listid on the CSD file for the IBM-protected groups. System action: Normal utility processing continues.
The CSD file may be full or corrupt. User response: None.
System action: Processing of the INITIALIZE command is Module: DFHCSDUP
terminated. Destination: SYSLST
User response: Check that the data set size for the CSD file is
large enough. If it is not, allocate more space.
DFHCA5141S Unable to create new group grpname
If there is ample space and you suspect that the CSD file is Explanation: The MIGRATE command failed when calling
corrupt, you need further assistance from IBM. See Part 4 of the CSD manager routing program, DFHDMP, to create a new
the CICS Problem Determination Guide for guidance on how to group grpname on the CSD file for the data in the table being
proceed. migrated. The CSD file may be full, corrupt, or not initialized.
Module: DFHCSDUP The group name may be invalid.
Destination: SYSLST System action: Processing of the MIGRATE command is
terminated.
User response: Check the group name in the TOGROUP
DFHCA5133S CSD contains one or more lists. No lists may
parameter. Reinitialize the CSD file with the INITIALIZE
be present on the CSD when the INITIALIZE
command, providing a larger data set size if necessary.
command is issued.
Module: DFHCSDUP
Explanation: The CEDA transaction was used to create a list
Destination: SYSLST
while the INITIALIZE command was executing.
System action: Processing of the INITIALIZE command is
terminated. DFHCA5142E Command not executed. lgname was not
User response: Redefine the data set and re-run the updated because of a previous update failure.
INITIALIZE command. The CEDA transaction must not be Explanation: The list or group lgname cannot be used because
used until the initialization of the CSD file has been an operation to update it, using the DFHCSDUP offline utility,
successfully completed. failed to execute to completion.
Module: DFHCSDUP
Destination: SYSLST This has probably happened in a previous execution of
DFHCSDUP.
System action: The command is not executed, and the
DFHCA5134S Error occurred while adding group grpname to execution of subsequent DFHCSDUP commands in the job
list listid stream is suppressed.
Explanation: A call to the CSD manager routing program, User response: Use the DFHCSDUP VERIFY command to
DFHDMP, to write the definition of group grpname to the CSD remove the in-flight flag detected when this message is
file as a member of an IBM-protected list listid created an produced.
error. The CSD file may be full or corrupt. Module: DFHCSDUP
System action: Processing of the INITIALIZE command is Destination: SYSLST
terminated.
User response: Increase the data set size for the CSD file and

DFHCA5143I • DFHCA5151W
DFHCA5143I Group grpname created. DFHCA5147E Command not executed. lgname already exists
Explanation: A new CSD group, grpname, has been created as a {GROUP | LIST}
for the data in the table being migrated. Explanation: The name chosen for the target group (or list)
System action: Migration continues. duplicates that of an existing group or list on the CSD file.
User response: None. System action: Processing of the utility command is
Module: DFHCSDUP terminated.
Destination: SYSLST User response: Choose a different name for the target group.
Module: DFHCSDUP
Destination: SYSLST
DFHCA5144I Migration of table table in progress. Default
group is grpname
Explanation: The parameters for the MIGRATE utility DFHCA5148E Unable to get storage for {PPT | PCT |FCT |
command are all valid, and the table has been loaded RDT | LD} table named table
successfully. Explanation: There is insufficient storage to satisfy a request
System action: Migration continues. for table table.
User response: None. System action: The system action depends on the table
Module: DFHCSDUP specified as follows:
Destination: SYSLST LD (language definition table)
The CSD utility cannot process any commands, and
terminates with a dump. The VSE user abend code
DFHCA5145E Command not executed. lgname has been is 0327.
locked by APPLID: applid, OPID:opid to PPT, PCT, FCT and RDT
prevent updating. The CSD utility cannot migrate the table, and
Explanation: The list or group lgname cannot be used because terminates processing of the utility command.
a user of the CEDA or CEDB transaction has enforced a LOCK User response: Allocate additional storage. If your TCT
command to prevent updating by other users. assembly and link-editing is successful, the RDT should be in
System action: The command is not executed. the library. The LD is in the load library of the supplied
If commands are being read from a SYSIPT data stream, pregenerated CICS system.
subsequent commands (except the LIST command) are Module: DFHCSDUP
checked for syntax only. (If the primary CSD file cannot be Destination: SYSLST
opened, the LIST command is not processed either.)
If commands are being read from a get-command exit, then DFHCA5149E Command not executed. xxxxxxxx is
the DFHCSDUP utility attempts to process subsequent IBM-protected.
commands. Explanation: A user attempted to add a definition to an
User response: Negotiate with the user with the specified IBM-supplied group or list (groups or lists beginning with
OPID and APPLID, or create a new group or list by taking a DFH). This is not allowed.
copy of the definitions in the locked one. System action: The CSD utility does not create a definition.
Module: DFHCSDUP User response: Change the input command or TCT source
Destination: SYSLST data to name a target group or list whose name does not
begin with DFH.
Module: DFHCSDUP
DFHCA5146E Command not executed. lgname is currently Destination: SYSLST
being updated by APPLID:applid, OPID:opid
Explanation: The list or group lgname cannot be used
because: DFHCA5150W Parameter ignored. xxxxxxxx yyyyyyyy was
v A user of the CEDA or CEDB transaction is currently originally defined with zzzzzzzz (No longer
running a command to update it supported)
v A previous operation to update it using CEDA or CEDB Explanation: When the original table entry was created, the
failed to execute to completion. parameter zzzzzzzz was used. This parameter is not supported
System action: The command is not executed. for resource definition online (RDO). xxxxxxxx is the resource
type and yyyyyyyy is the resource name.
If commands are being read from a SYSIPT data stream, System action: The unsupported field is not included in the
subsequent commands (except the LIST command) are resource definition created on the CSD file. (All the supported
checked for syntax only. (If the primary CSD file cannot be fields are migrated.)
opened, the LIST command is not processed either.) User response: None.
Module: DFHCSDUP
If commands are being read from a get-command exit, then
Destination: SYSLST
the DFHCSDUP utility attempts to process subsequent
commands.
User response: Resubmit the utility job to retry the command DFHCA5151W OPTGRP parameter ignored. transaction
that failed. Perform the subsequent commands that were tranid was originally defined with parm (No
suppressed. longer supported.)
If this fails to resolve the problem, run the DFHCSDUP Explanation: This message is issued when you have:
VERIFY command to remove the in-flight flag detected when 1. DFHPCT TYPE=ENTRY macro instructions that reference a
this message is produced. message option group, specified by the TYPE=OPTGRP
Module: DFHCSDUP parameter, and
Destination: SYSLST

DFHCA5152W • DFHCA5158W
2. the TYPE=OPTGRP parameter specifies the MSGPOPT 2. Keep the data migrated to the CSD file, and use the CEDA
parameter. transaction to define the resources that were not migrated.
System action: The system action is dependent on the Take care to use names that are unique.
parameters specified on the TYPE=OPTGRP macro. Module: DFHCSDUP
1. If the TYPE=OPTGRP macro contains the MSGPREQ Destination: SYSLST
parameter, and this specifies the same operand values as
the MSGPOPT parameter, the MIGRATE command creates
a PROFILE containing the attributes specified on the DFHCA5155W {PPT entry | Transaction | Profile} xxxxxxxx has
MSGPREQ parameter. The MSGPOPT group is ignored. same name as an IBM supplied definition in
The transaction will refer to this profile. group grpname
2. If the TYPE=OPTGRP macro contains the MSGPOPT Explanation: The name of the migrated table entry, xxxxxxxx,
parameter without an equivalent MSGPREQ parameter, the matches the name of an IBM-supplied resource in
OPTGRP definitions are ignored. The transaction will refer IBM-protected group grpname, created by the INITIALIZE
to a profile that has MSGINTEG, ONEWTE, PROTECT and command.
CHAINCONTROL set to the default values. System action: CICS migrates this entry normally.
User response: No action is required. User response: If necessary, rename the resource, using the
CEDA transaction.
For further information about changes to online and macro Module: DFHCSDUP
resource definition options, refer to the CICS Transaction Server Destination: SYSLST
for OS/390: Migration Guide.
Module: DFHCSDUP
Destination: SYSLST DFHCA5156W {PPT entry | Transaction | Profile} did not
migrate. It's properties match an
IBM-supplied definition in group grpname
DFHCA5152W Default profile DFHCICSx not found in the Explanation: The properties of the resource defined in the
PCT user's table entry are the same as those of the IBM-supplied
Explanation: DFHCICSx is the name of the IBM-supplied resource of the same name contained in IBM-protected group
profile that should be present in the user's assembled PCT. grpname.
System action: An equivalent profile is generated with the System action: The entry for the user's resource is not
required properties, if necessary. It will have a name derived migrated.
from a transaction name, and may be used by other User response: None.
transactions migrated to the CSD file. Module: DFHCSDUP
User response: No action essential for migration to take place Destination: SYSLST
is required. (You may rename the generated equivalent
profile.)
Module: DFHCSDUP DFHCA5157W Generated profile profile not created. name
Destination: SYSLST duplicates an existing profile
Explanation: The CSD utility creates a generated profile
profile whenever it migrates a transaction whose PROFILE
DFHCA5153W Assigned TASKREQ xxxxxxxx duplicates a properties differ from those of DFHCICST, DFHCICSA,
transaction name and did not migrate DFHCICSV, or one of the previously-generated profiles. The
Explanation: A transaction identified only by a TASKREQ name of the generated profile is derived from the transaction
will be assigned a primary transaction name automatically (for name. The utility issues this message when the derived name
example, 'PF11' for a TASKREQ X'7B'). If the assigned name is the same as that of an existing profile in the PCT.
conflicts with that of an existing transaction name in the PCT, System action: The generated profile is not written to the
no transaction definition will be created on the CSD file for CSD file.
the one identified by a TASKREQ. User response: Use the CEDA transaction to
System action: This transaction entry is not migrated. 1. define a profile for the transaction, with a unique profile
User response: Use the CEDA transaction to define the name, and
transaction for RDO with a name that does not conflict with 2. alter the PROFILE keyword field for the transaction
that of an existing transaction. If no existing profile is suitable affected, so that it uses this new profile.
for it, the user must also define a profile using CEDA. Module: DFHCSDUP
Destination: SYSLST
DFHCA5158W Definition of xxxxxxxx defaulted to

DFHCA5154W Duplicate {PPT Entry | Transaction |Profile} RESIDENT(YES) as
name - this table entry is not migrated RES=FIX|ALIGN|PGOUT is no longer
Explanation: The table has been assembled with a duplicated supported
name for a table entry. Explanation: The RES=... parameter specified in the DFHPPT
System action: Only one table entry with the duplicate name macro is not available in RDO.
is migrated to the CSD file. This is the one that is encountered System action: The RDO resource definition for xxxxxxxx is
first in the sequence of table entries. created with the attribute RESIDENT(YES).
User response: User response: None.
1. Erase the group created by migration. Reassemble the table Module: DFHCSDUP
without duplicated names, and submit the offline migrate Destination: SYSLST
routine again, or

DFHCA5159I • DFHCA5169S
User response: Use the CEDA transaction to define the

DFHCA5159I resource object defined in group grpname
resource with a unique name.
Explanation: The CSD utility has successfully added a
Module: DFHCSDUP
resource definition to a group, where:
Destination: SYSLST
v resource is the type of resource (PROGRAM, MAPSET,
PARTITIONSET, TRANSACTION, PROFILE, TERMINAL,
TYPETERM, SESSION, or CONNECTION). DFHCA5165S Processing is terminated. An error occurred
v object is the name of the object. while writing resource object to the CSD.
v grpname is the name of the group. Explanation: An error occurred when the CSD utility called
System action: Normal utility processing continues. DFHDMP to write the definition of the object object to the CSD
User response: None. file.
Module: DFHCSDUP
Destination: SYSLST The CSD file may be full or corrupted.
resource is the type of resource.
DFHCA5160W 'RES=' parameter ignored. Definition of System action: If the CSD is full, the CSD utility issues
xxxxxxx assumes RESIDENT(NO) as message DFHCA5176, and then terminates with a return code
USAGE=MAP is specified of 12 in message DFHCA5109.
Explanation: An invalid combination of parameters was If the CSD is not full, the CSD utility terminates abnormally
specified in the DFHPPT macro for this entry. with message DFHCA5175, usually accompanied by one or
System action: USAGE=MAP is assumed, and the resulting more of the explanatory messages, DFHCA5177, DFHCA5178,
RDO MAPSET definition is created with the attributes and DFHCA5179.
RESIDENT(NO) and USAGE(TRANSIENT). User response: Use the additional messages to determine the
User response: Check that this is what you want and is cause of the error and the appropriate user action required.
correct in the CSD. Module: DFHCSDUP
Destination: SYSLST
DFHCA5166E Disallowed character in resource name object

DFHCA5162I Transaction tranid uses profile profile Explanation: The call to module DFHDMP has failed to
Explanation: Every transaction in RDO must have a construct a valid key for the record created on the CSD file
corresponding profile. The PROFILE properties of the because of an invalid character, or the resource name for the
transaction tranid are compared with those of DFHCICST, migrated table entry may be invalid. resource is the type of
DFHCICSV, DFHCICSA, and the generated profiles. Profile resource, and object is the name of the object.
profile is the one used, because its profile properties match. System action: A CSD record is not created for this
System action: The transaction is migrated normally, and no definition. (If it is a transaction, a generated profile is not
new generated profile is created for it. The PROFILE field in created either.)
the transaction property list receives the name of the profile User response: Use the CEDA transaction to define the
that matched. resource with a valid name.
Destination: SYSLST
DFHCA5168S Table loaded from library member table is not

DFHCA5163I Transaction name tranid assigned to a valid {PPT | PCT | FCT | RDT |TCT}.
transaction identified by a TASKREQ Explanation: After loading the table table, the migration
Explanation: Every transaction in RDO must have a primary routine checks the VMNAME field in the DFHVM expansion
transaction name. Transaction tranid, previously identified only of the data area following the load point. This message is
by a TASKREQ, is assigned a primary transaction name produced if VMNAME is not that of a valid table (that is,
automatically (for example, PF11 for a TASKREQ X'7B'). DFHPPTxx or DFHPCTxx).
System action: The transaction is given the derived name System action: The MIGRATE command is not processed.
and migrated in the normal way. User response:
User response: None. 1. Ensure the table assembled and link-edited without errors.
Module: DFHCSDUP 2. Ensure that the correct table is present in the library, and
Destination: SYSLST that the TABLE parameter of the MIGRATE command is
correct.
DFHCA5164W No definition of resource object created. This 3. In the case of the PCT, the first ordered CSECT must be
duplicates an existing definition in group DFHSCAN. In the case of the PPT, the first ordered CSECT
grpname must be SCAN.
Explanation: The CSD utility detected a CSD record with a Module: DFHCSDUP
matching key before adding the definition to the CSD file, Destination: SYSLST
where:
v resource is the type of resource. DFHCA5169S Processing is terminated. Table table was
v object is the name of the object. assembled for CICS release rrr. Reassemble
v grpname is the name of the group. for release sss.
System action: The CSD utility does not migrate the resource Explanation: After loading the table table, the migration
definition to the CSD file. (If it is a transaction, a generated routine checks the VMVERS field in the DFHVM expansion of
profile is not created either.) the data area following the load point. This field indicates the

CICS release (rrr) for which the table was assembled, and is CICS Transaction Server for VSE/ESA Release 1 supports the
invalid for the CICS system (release sss) that is running. concept of empty files without the need to specify a separate
System action: The MIGRATE command is not processed. FCT entry with SERVREQ=REUSE in order to load the data
User response: Reassemble the table for the correct release of set. The SET FILE EMPTY command can be used for a file
CICS. allocated to a data set defined as reusable. It specifies that the
Module: DFHCSDUP data set is set empty the next time the file is opened. After the
Destination: SYSLST initial loading of a file, CICS file control handles internally the
closing and reopening of a file to take it out of VSAM load
mode.
DFHCA5170S Processing is terminated. Table table is too User response: Eliminate use of SERVREQ=REUSE files from
large to migrate your installation.
Explanation: The CSD utility cannot migrate the table Module: DFHCSDUP
DFHxxxx, because it contains too many entries. Destination: SYSLST
System action: The utility does not execute the MIGRATE
command, and suppresses execution of subsequent
commands. DFHCA5174W Processing is terminated. Command cannot
User response: Divide the table into smaller components, and be executed because
assemble each component. Migrate each assembled component 'PARM=CSD(READONLY)' was specified.
to the CSD as a separate table. Explanation: This command requires the CSD to be opened
for read-write access. Your job step specified read-only access
Note: Do NOT try to migrate a table with more than 2000 for the CSD in the DFHCSDUP utility job stream.
entries. System action: This command is not executed.
Module: DFHCSDUP
Destination: SYSLST If commands are being read from a SYSIPT data stream,
subsequent commands (except LIST) are checked for syntax
only. (If the primary CSD file cannot be opened, LIST is not
DFHCA5171E No definition for file DFHCSD created. The processed either.)
CSD should be defined in the SIT.
Explanation: The CSD utility detected an attempt to migrate If commands are being read from a get-command exit, then
a definition of the CSD to the CSD. DFHCSDUP attempts to process subsequent commands.
System action: The CSD utility creates no definition for User response: Amend the JCL to specify
DFHCSD. Normal utility processing continues with the utility 'PARM=CSD(READWRITE)'.
return code set to 8. Module: DFHCSDUP
User response: Remove the definition of the CSD from the Destination: SYSLST
FCT. Ensure that your definition of the CSD is added to the
SIT.
DFHCA5175S Processing is terminated. Unexpected
Module: DFHCSDUP
response from function in CSD manager.
Destination: SYSLST
Explanation: An invocation of the CSD manager, DFHDMP,
has resulted in an error. The name of the function that failed is
DFHCA5172W No definition for file file created. filetype files function.
are not supported by RDO. System action: DFHCSDUP issues additional messages and
Explanation: The CSD utility detected an attempt to migrate then
a definition of a DAM or DL/I data set to the CSD. DAM and v Terminates normally for CSD open/close errors, and the
DL/I data sets are not supported by RDO. CSD-full condition, or
System action: The migration request is ignored. A definition v Terminates abnormally for all other situations.
for the named DAM or DL/I data set is not created. Normal User response: Ensure that you have set up your CSD file
utility processing continues, but the utility return code will be correctly. If you have migrated your CSD file from a previous
set to 4. release, note that you should have increased your block size to
User response: DAM and DL/I data sets should be defined 500. If necessary, use the diagnostics in the additional
to CICS using the FCT. Re-assemble your FCT with messages.
MIGRATION=COMPLETE on the TYPE=INITIAL macro after Module: DFHCSDUP
all VSAM data sets have been migrated. Use the generated Destination: SYSLST
FCT as you would in a non-RDO environment.
Module: DFHCSDUP
DFHCA5176S Processing is terminated. CSD is full.
Destination: SYSLST
Explanation: The VSAM data set containing the CSD file is
full.
DFHCA5173 SERVREQ=REUSE is ignored in the System action: Execution of the CSD utility command is
definition of file filename because it is not terminated.
supported by RDO.
If commands are being read from a SYSIPT data stream,
Explanation: The CSD utility detected an attempt to migrate
subsequent commands (except LIST commands) are checked
to the CSD the definition of VSAM file filename with
for syntax only. (If the primary CSD file cannot be opened, the
SERVREQ=REUSE specified. RDO does not support files with
LIST command is not processed either.)
the SERVREQ=REUSE attribute.
System action: The SERVREQ=REUSE attribute of the file is If commands are being read from a get-command exit, then
ignored, and the file is migrated to the CSD without it. the DFHCSDUP utility attempts to process subsequent
Normal utility processing continues, but the utility return code commands.
is set to 4.

DFHCA5177S • DFHCA5183W
The DFHCSDUP utility leaves a system lock on the group User response: For the meaning of the VSAM return and
being created at the time of failure. This lock prevents error codes, refer to section "VSE/VSAM Codes" in z/VSE
processing of the group by the CSD utility or the CEDA Messages and Codes - Volume 2.
transaction.
When interpreting these diagnostics, ensure that the data set
User response: First, use the DFHCSDUP VERIFY process to
referenced in the JCL exists. Check whether the data set is
remove the system lock on the partly-created group. Normal
being concurrently accessed by CICS running in another
RDO processing of the group should then be possible,
region.
enabling the group (or any unwanted definitions) to be
Module: DFHCSDUP
deleted.
Destination: SYSLST
To recover the contents of the CSD file, define a larger data set
and use the VSAM Access Method Services (AMS) command.
Usually, you will be able to REPRO from the CSD file that DFHCA5180S Processing is terminated. Error occurred
became full. If you are unable to do this, use a backup copy. while CSD was being read by {SETBROWSE
(You may be able to transfer definitions from the CSD file that | GETNEXT} {SCANSETS | SCANOBJS}
filled up by using the DFHCSDUP COPY command with the Explanation: When the LIST command invoked DFHDMP to
FROMCSD option.) scan the objects on the CSD file, an error occurred during
Module: DFHCSDUP execution of the DFHDMP function.
Destination: SYSLST System action: The CSD utility terminates with an VSE
abend 0325.
User response: This error should be reported. You need
DFHCA5177S Processing is terminated. CSD I/O error further assistance from IBM to resolve this problem. See Part 4
occurred. of the CICS Problem Determination Guide for guidance on how
Explanation: An I/O error occurred when executing a READ to proceed.
or WRITE of a CSD record on the primary or secondary CSD Module: DFHCSDUP
file. Destination: SYSLST
System action: DFHCSDUP issues additional messages and
terminates abnormally.
User response: Restore the CSD file to a new data set from DFHCA5181W No match found for generic {group | list}
your own backup, or create the new CSD file by using the identifier xxxxxxxx
INITIALIZE, COPY, and APPEND commands to restore Explanation: The LIST command was executed with a
existing definitions. generic group or list name, but no qualifying group or list
Module: DFHCSDUP exists on the CSD file.
Destination: SYSLST System action: Normal processing continues.
Module: DFHCSDUP
DFHCA5178S Processing is terminated. Severe CSD error Destination: SYSLST
occurred.
Explanation: An error occurred during execution of the CSD
manager, DFHDMP, to access the primary or secondary CSD DFHCA5182W {group | list} xxxxxxxx does not exist.
file. Explanation: The LIST command or the DELETE command
System action: DFHCSDUP issues additional messages and was executed using the name of a group or list that does not
terminates abnormally. exist on the primary CSD file.
User response: See the VSAM diagnostics given in message System action: The LIST command or the DELETE command
DFHCA5179. is not processed. Subsequent commands may still be
Module: DFHCSDUP processed.
Destination: SYSLST User response: Correct the LIST command or the DELETE
command to use a valid group or list name.
DFHCA5179S VSAM error. Return code = nn error code = If a CSD upgrade is being performed, no user action is
ddd(yy) control block type = {RPL | ACB} required.
Explanation: VSAM returned the following diagnostics when Module: DFHCSDUP
an error occurred, where: Destination: SYSLST
v nn is the hexadecimal VSAM return code
v yy is the hexadecimal VSAM error code (ddd is its decimal DFHCA5183W {group | list} xxxxxxxx exists as a {group | list}
equivalent) name.
v CONTROL BLOCK TYPE points to the relevant error code Explanation: The LIST command or the DELETE command
subset as follows: was executed using a group name that is already in use as a
– RPL = Request macro responses from VSAM list name, or using a list name that is already in use as a
– ACB = OPEN/CLOSE responses group name.
The error code is: System action: The LIST command or the DELETE command
– For CONTROL BLOCK TYPE = RPL, the FDBK field in is not processed. Subsequent commands may still be
the RPL processed.
– For CONTROL BLOCK TYPE = ACB, the ERROR field in User response: Correct the LIST command or the DELETE
the ACB command to use a valid group or list name.
System action: The CSD utility terminates command Module: DFHCSDUP
processing, and in some situations, produces an operating Destination: SYSLST
system dump.

DFHCA5184S Processing is terminated. Invalid output from DFHCA5189I CSD VERIFY process completed successfully.
DFHPUP. Cannot format data for utility Explanation: The DFHCSDUP VERIFY command has been
listing. processed successfully, and any internal locks associated with
Explanation: There has been an internal logic error in the groups and lists on the CSD file have been removed.
DFHCSDUP utility program. The data in the back-translated System action: Normal processing continues.
output buffer is invalid. The length code may be out of range User response: None.
or the data fields in the wrong sequence. One or more of the Module: DFHCSDUP
data fields may be invalid. Destination: SYSLST
System action: The CSD utility terminates with an VSE
abend 0326.
User response: This error must be reported. DFHCA5190S Command is not executed. Unable to get
storage for service module progname
Obtain a dump from DFHCSDUP together with a listing of the Explanation: There is insufficient storage available to load
DFHCSDUP run and its JCL. Also try to obtain a print out of the service module progname, that is to be loaded and executed
the CSD, using either the VSAM Access Method Services by DFHCSDUP.
(AMS) PRINT command or the DFHCSDUP LIST ALL System action: Utility command execution is terminated.
command. The LIST will indicate where the error(s) have
occurred because they will refuse to print and are therefore If commands are being read from a SYSIPT data stream,
easily identifiable. subsequent commands (except LIST commands) are checked
for syntax only. (If the primary CSD file cannot be opened, the
You need further assistance from IBM to resolve this problem. LIST command is not processed either.)
See Part 4 of the CICS Problem Determination Guide for
guidance on how to proceed. If commands are being read from a get-command exit, then
Module: DFHCSDUP DFHCSDUP attempts to process subsequent commands.
Destination: SYSLST User response: Ensure that there is sufficient storage
allocated to load module progname.
Module: DFHCSDUP
DFHCA5186W No resources defined in group grpname or no Destination: SYSLST
groups defined in list lstid
Explanation: In executing a LIST command, the CSD utility
has found a group or list header on the CSD file for which no DFHCA5191I Service program progname is running.
corresponding group or list elements exist. Explanation: The service module progname has been loaded
System action: The utility continues to process the LIST correctly. Execution of the module has started.
command, but will not tabulate elements of the group or list System action: Normal processing continues.
named in the message. User response: None.
User response: Run the DFHCSDUP VERIFY utility. Module: DFHCSDUP
Destination: SYSLST
DFHCA5192S Command is not executed. CSD service level
DFHCA5187I resource is locked, but is not the name of a ttt is incompatible with current service level
group or list. sss
Explanation: The CSD utility detected a locked resource that Explanation: Either the LEVEL parameter specified in the
is not a group or list. The reason is that an interrupt or failure DFHCSDUP SERVICE command is wrong, or an incorrect
occurred during a CEDA transaction or a previous utility job. version of the CSD file is being used as the secondary (input)
A lock had been created but not the associated group or list. CSD file.
System action: The utility continues normal processing of the System action: The SERVICE command is not executed.
DFHCSDUP VERIFY command. If commands are being read from a SYSIPT data stream,
User response: None. subsequent commands (except LIST commands) are checked
Module: DFHCSDUP for syntax only. (If the primary CSD file cannot be opened, the
Destination: SYSLST LIST command is not processed either.)
DFHCA5188I {group | list | reserved name} resource is now DFHCSDUP attempts to process subsequent commands.
available for use. User response: The SERVICE command may upgrade the
Explanation: The DFHCSDUP VERIFY command discovered service level of the CSD file only in increments of one. Check
that the resource was not available for the CEDA transaction that the input CSD file is the intended one, and that the
or offline commands. The restriction on its availability, which LEVEL parameter takes the value one higher than the current
was due to the failure of some previous command affecting it, service level of the CSD file.
has now been removed. Module: DFHCSDUP
System action: Normal processing of the VERIFY command Destination: SYSLST
continues.
Module: DFHCSDUP DFHCA5193S Command is not executed. Service module
Destination: SYSLST progname is unable to upgrade CSD to target
service level ttt
Explanation: The LEVEL parameter specified in the
DFHCSDUP SERVICE command is incompatible with the

status of the service module progname being applied to the If commands are being read from a SYSIPT data stream,
CSD file. subsequent commands (except LIST) are checked for syntax
System action: The SERVICE command is not executed. only. (If the primary CSD file cannot be opened, LIST is not
processed either.)
subsequent commands (except LIST commands) are checked If commands are being read from a get-command exit, then
for syntax only. (If the primary CSD file cannot be opened, the DFHCSDUP attempts to process subsequent commands.
LIST command is not processed either.) User response: Ensure that the input and output data sets
have been correctly defined, and that the DLBL name for the
If commands are being read from a get-command exit, then secondary CSD file in the JCL corresponds to the FROMCSD
DFHCSDUP attempts to process subsequent commands. parameter in the SERVICE utility command.
User response: Ensure that the service module progname
being applied, is correctly updated with the service fix If the problem persists, you will need further help from IBM.
supplied by IBM. (It should have been amended so as to be First, obtain a dump from DFHCSDUP together with a listing
able to process SERVICE commands at the target level ttt.) of the DFHCSDUP run and its JCL. Also try to obtain a print
Module: DFHCSDUP out of the CSD using either IDCAMS or the DFHCSDUP LIST
Destination: SYSLST ALL option. The LIST indicates where the errors have
occurred because they do not print and are therefore easily
identifiable. See Part 4 of the CICS Problem Determination Guide
DFHCA5194I Upgrading service status of CSD from level for guidance on how to proceed.
sss to level ttt Module: DFHCSDUP
Explanation: The loaded service module is performing the Destination: SYSLST
required upgrade of the CSD file from service level sss to
service level ttt.
System action: Normal processing continues. DFHCA5198I CSD record modified for xxxxxxxx
User response: None. Explanation: The specified modification to a record on the
Module: DFHCSDUP CSD file has taken place.
Destination: SYSLST
The insert, xxxxxxxx, is the element type.
System action: Normal processing continues. If the modified
DFHCA5195I Execution of service program progname record is an element in a GROUP or LIST, its date-and-time
complete. field is updated when copied to the output (primary) CSD file.
Explanation: The loaded service program progname has run to User response: None.
completion. Control is being transferred back to the CSD Module: DFHCSDUP
offline utility program, DFHCSDUP. Destination: SYSLST
DFHCA5199W Invalid field encountered in existing record
Module: DFHCSDUP
for xxxxxxxx
Destination: SYSLST
Explanation: An unexpected value was found in one of the
fields of a CSD record that was to be modified for element
DFHCA5196S Command is terminated. Error occurred while xxxxxxxx.
reading control secondary CSD record. System action: Normal processing continues, and the invalid
Explanation: An I/O error has occurred on the specified CSD record is left unchanged on the new (primary) CSD file.
file. User response: None.
System action: The DFHCSDUP SERVICE command is Module: DFHCSDUP

subsequent commands (except LIST) are checked for syntax DFHCA5200S date time applid netname tranid Command not
only. (If the primary CSD file cannot be opened, LIST is not executed. No valid language table was
processed either.) loaded.
Explanation: The command analyser found that the RDO
If commands are being read from a get-command exit, then language table had not been loaded correctly, or that it
DFHCSDUP attempts to process subsequent commands. contained invalid data.
User response: Retry the command, ensuring that a System action: The analyser terminates because it cannot
sufficiently large data set size is specified for the output process any commands.
(primary) CSD file. User response: Check that the correct version of the RDO
Module: DFHCSDUP language table (DFHEITSP) is in the program library.
Destination: SYSLST Module: DFHCAP
XMEOUT Parameters: date, time,applid, netname, tranid
DFHCA5197S Command is terminated. Unrecognized Destination: CSMT
Control record encountered while secondary
CSD was being read.
Explanation: The contents of a control record of the
secondary input CSD are invalid.
System action: The DFHCSDUP SERVICE command is
terminated.

DFHCA5201S • DFHCA5213E
XMEOUT Parameters: date, time,applid, netname, tranid, xxxx

DFHCA5201S date time applid netname tranid 'command'
Destination: CSMT
command is not valid. Command not
executed.
Explanation: The command analyser does not recognize the DFHCA5207E date time applid netname tranid Command not
command. executed. 'xxxxxxxx' does not require a value.
System action: The analyser ignores the command. Explanation: The command analyser detected an input
User response: Correct the command. command coded with a value for option xxxxxxxx when no
Module: DFHCAP, DFHCSDUP value was required.
XMEOUT Parameters: date, time,applid, netname, tranid, System action: The command analyser does not process the
command command.
Destination: CSMT User response: Correct the command.
XMEOUT Parameters: date, time,applid, netname, tranid,
DFHCA5202S date time applid netname tranid Incorrect syntax
xxxxxxxx
for 'command' command. Command not
Destination: CSMT
executed.
Explanation: The syntax of the command is incorrect.
System action: The command analyser ignores the command. DFHCA5210E date time applid netname tranid Command not
User response: Correct the command. executed. Invalid value was specified for
Module: DFHCAP, DFHCSDUP 'xxxx'.
XMEOUT Parameters: date, time,applid, netname, tranid, Explanation: The command analyser detected an input
command command coded with an invalid value for option xxxx.
Destination: CSMT System action: The command is ignored.
User response: Correct the value.
DFHCA5203W date time applid netname tranid Right
parenthesis assumed after the value of 'xxxx'.
Destination: CSMT
Explanation: The syntax of the command was incorrect.
Either a right parenthesis has been omitted or a keyword
value in excess of 256 bytes has been specified. DFHCA5211E date time applid netname tranid Command not
System action: The command analyser executes the executed. Operand delimiter 'x' was
command as if the right parenthesis was present. misplaced.
User response: Confirm that the correction applied by the Explanation: The command analyser has detected an input
analyser generated the required command. command coded with a misplaced option delimiter x.
Module: DFHCAP, DFHCSDUP System action: The command analyser does not process the
XMEOUT Parameters: date, time,applid, netname, tranid, xxxx command.
Destination: CSMT User response: Place the delimiter correctly.
XMEOUT Parameters: date, time,applid, netname, tranid, x
DFHCA5204E date time applid netname tranid Command not
Destination: CSMT
executed. 'xxxx' keyword is not valid.
Explanation: The keyword xxxx is not valid on this
command. DFHCA5212E date time applid netname tranid Command not
System action: The command is ignored. executed. comptype 'string' is not uniquely
User response: Correct the command. identifiable.
Module: DFHCAP, DFHCSDUP Explanation: An ambiguous DFHCSDUP or CREATE
XMEOUT Parameters: date, time,applid, netname, tranid, xxxx command has been specified.
Destination: CSMT v comptype is the command component type
v string is the actual component.
DFHCA5205E date time applid netname tranid Command not User response: Correct the command syntax and retry. See
executed. No value was specified for 'xxxx'. accompanying message DFHCA5213 for further details of the
Explanation: The option xxxx is incomplete, possibly because command failure.
a value has been omitted. Module: DFHCAP, DFHCSDUP
User response: Correct the command. XMEOUT Parameters: date, time,applid, netname, tranid,
Module: DFHCAP, DFHCSDUP comptype, string
Destination: CSMT
Destination: CSMT
DFHCA5213E date time applid netname tranid Specified input
could be interpreted as match1 or match2
Explanation: An ambiguous DFHCSDUP or CREATE
executed. Duplicate specification of 'xxxx'.
command has been specified.
Explanation: Option xxxx appears twice on a single
v input is the ambiguous character string
command.
v match1 and match2 are two possible interpretations of input.
User response: Correct the command. System action: The command is not executed.
Module: DFHCAP, DFHCSDUP User response: Correct the command syntax and retry.

DFHCA5214W • DFHCA5227E

DFHCA5220E Command not executed. xxxxxxxx must be the
XMEOUT Parameters: date, time,applid, netname, tranid, input, first command.
match1, match2 Explanation: The CSD utility found an INITIALIZE
Destination: CSMT command after other commands.
System action: The CSD utility ignores the command.
User response: Confirm that the INITIALIZE command was
DFHCA5214W date time applid netname tranid keyword is an misplaced.
obsolete keyword. It is ignored. Module: DFHCSDUP
Explanation: The command analyser has detected an input Destination: SYSLST
command coded with an obsolete keyword. The keyword
specifies an option not valid for this release of CICS.
DFHCA5222E Command not executed. xxxxxxxx keyword
System action: The command analyser ignores the keyword.
was omitted or specified incorrectly.
User response: Confirm that the resulting command is Explanation: A required keyword xxxxxxxx was omitted from
correct for this release of CICS. a CSD utility command.
Module: DFHCAP, DFHCSDUP System action: The utility ignores the command.
XMEOUT Parameters: date, time,applid, netname, tranid, keyword User response: Specify keyword xxxxxxxx.
Destination: CSMT Module: DFHCSDUP
Destination: SYSLST
DFHCA5216E restype resname is not in group group.

DFHCA5223E Command not executed. xxxxxxxx keyword
Explanation: A nonexistent resource of type restype and name
conflicts with xxxxxxxx keyword.
resname, has been specified on an ALTER command.
Explanation: The syntax of the command is incorrect.
System action: The command is not executed. If commands
Conflicting keywords have been specified.
are being read from a SYSIPT data stream, subsequent
System action: The utility command is ignored.
commands (except LIST commands) are checked for syntax
User response: Correct the command.
only. If commands are being read from a get-command exit,
Module: DFHCSDUP
DFHCSDUP attempts to process subsequent commands.
Destination: SYSLST
User response: Correct the command syntax and retry.
Module: DFHCSDUP
Destination: SYSLST DFHCA5224E Command not executed. value of xxxxxxxx is
out of valid range.
Explanation: The CSD utility detected an input command
coded with a numeric value for value xxxxxxxx which was
executed. A closing bracket has been omitted
outside the valid range.
from a description keyword.
System action: The utility does not process the command.
Explanation: A closing bracket has been omitted from the
User response: Correct the value.
DESCRIPTION keyword on a DEFINE or CREATE command.
Module: DFHCSDUP
Destination: SYSLST
User response: Correct the command syntax and retry.
XMEOUT Parameters: date, time,applid, netname, tranid DFHCA5225E Command not executed. Same name specified
Destination: CSMT for 'to' and xxxxxxxx.
Explanation: This message is issued for one of the following
reasons:
DFHCA5218I Altering Resourcetype Resourcename in group 1. The utility COPY command has been coded with the same
Groupname group name for the source and target group.
Explanation: During the execution of a generic ALTER 2. The APPEND command has been coded with the same list
command, the CSD batch update utility scans the CSD file for name for the source and target list.
matches to the specified generic resource name and/or 3. The ADD command has been coded with the same group
GROUP keyword. For every match, the utility processes the name and list name.
request and informs the user of the resulting resourcename System action: The CSD utility or CICS ignores the
and/or groupname respectively. command.
System action: Normal processing continues. User response: Correct the name (or names) in error.
Destination: SYSLST
DFHCA5227E Command not executed. Use of generic name

DFHCA5219W No match found on CSD file for Resourcetype
conflicts with xxxxxxxx option.
Resourcename group Groupname
Explanation: A CSD utility command used a generic name;
Explanation: The ALTER command was executed with a
that is, one containing asterisk (*) or plus sign (+) characters,
generic resource and/or group name, but no qualifying
resource and/or group exist on the CSD file. in conjunction with an option that conflicted with the use of
System action: Normal processing continues. generic names.
User response: None. System action: The utility ignores the command.
Module: DFHCSDUP User response: Correct the command.
Destination: SYSLST Module: DFHCSDUP
Destination: SYSLST

DFHCA5228E • DFHCA5241S

DFHCA5228E Command not executed. Only one
Module: DFHCSDUP
resource-type keyword can be specified.
Destination: SYSLST
Explanation: The CSD utility detected an input command
coded with more than one resource-type keyword.
System action: The utility does not process the command. DFHCA5234E Command not executed. command is not
User response: Correct the command to refer to only one supported.
resource-type keyword. Explanation: The CSD utility detected a command command
Module: DFHCSDUP in its input which is not supported by RDO.
Destination: SYSLST System action: The utility does not process the command.
User response: Correct the command
Module: DFHCSDUP
DFHCA5229E Command not executed. xxxxxxxx is invalid
Destination: SYSLST
because a resource-type keyword was
specified.
Explanation: The CSD utility detected an input command DFHCA5235E Command not executed. GROUP or LIST
coded with a resource-type keyword (for example, must be specified.
PROGRAM, TRANSACTION) in a situation where a Explanation: A CSD utility EXTRACT command has been
resource-type keyword is invalid. submitted. A GROUP or LIST name must be specified with an
System action: The utility does not process the command. EXTRACT command.
User response: Correct the command and resubmit. System action: The utility command is not executed. This
Module: DFHCSDUP message is followed by DFHCA5104.
Destination: SYSLST User response: Correct the invalid command by adding a
valid GROUP or LIST name and rerun the utility job.
Module: DFHCSDUP
DFHCA5230I ERASE command is obsolete. Use the
Destination: SYSLST
DELETE command.
Explanation: The CSD utility detected the obsolete ERASE
command in its input. DFHCA5236I A user exit program has been specified on
System action: The utility processes the command as a the entry linkage and on the userprogram
DELETE command. keyword. The program specified on the entry
User response: In future, use the DELETE command instead linkage has been ignored.
of the ERASE command. Explanation: An EXTRACT user-exit program has been
Module: DFHCSDUP specified via the entry parameter list and on the
Destination: SYSLST USERPROGRAM keyword of the EXTRACT command.
System action: The program specified on the
USERPROGRAM keyword is used.
DFHCA5231E Command not executed. xxxxxxxx is
User response: Ensure that the user program used is the one
incompatible with the MIGRATE command
intended.
for table-type tables.
Module: DFHCSDUP
Explanation: An attempt has been made to execute the
Destination: SYSLST
MIGRATE command with an invalid table type and (or) an
invalid keyword specified.
System action: The CSD utility terminates. DFHCA5240S Processing terminated. Error occurred while
User response: Correct the command syntax and resubmit input utility command was being read.
the job. Explanation: The environment adaptor GETCARD utility
Module: DFHCSDUP cannot read an input utility command.
Destination: SYSLST System action: The CSD utility terminates abnormally
without processing the input commands.
User response: Check that the utility commands are prepared
DFHCA5232E Command not executed. xxxxxxxx parameter
correctly and located correctly in the JCL. Check also that the
must not begin with 'DFH'.
DLBL statement defining the output data set startup job
Explanation: In a CSD utility MIGRATE command, the
stream is correct. For JCL examples, refer to the CICS
xxxxxxxx parameter contained an invalid table name or group
Operations and Utilities Guide.
name.
Module: DFHCSDUP
Destination: SYSLST
User response: Resubmit with a valid table name or group
name.
Module: DFHCSDUP DFHCA5241S Processing terminated. Invalid record length
Destination: SYSLST on input utility command data stream.
Explanation: The CSD utility detected incorrectly formatted
input in the SYSIPT data stream.
DFHCA5233E Command not executed. xxx table type is not
System action: The CSD utility cannot process any
supported by RDO.
commands. The utility attempts to:
Explanation: The CSD utility detected a TABLE parameter
1. Close any files previously opened internally.
that referred to a CICS table type not supported by RDO.
2. Unload any extract exit routines that were dynamically
RDO supports program, transaction, and terminal definitions
loaded.
(RDT).
4. Return control to the invoker of the utility.

DFHCA5242E • DFHCA5259I
User response: Ensure that the output data set data stream is the name of the existing definition.
formatted with fixed length 80-byte records. Module: DFHCSDUP
Destination: SYSLST
DFHCA5255E List xxxxxxxx not found in CSD file -

DFHCA5242E Command not processed. Too many FILENAME: filename
continuation records for input utility Explanation: The CSD utility detected an APPEND or
command. REMOVE command that referred to a nonexistent list in the
Explanation: The CSD utility detected an input command CSD file specified in DLBL filename.
that was too long and extended over too many records. System action: The utility does not process the command.
System action: The utility does not process the command. User response: Either correct the list name in the command,
User response: This message may be caused by an error in or make sure that the specified CSD file is the correct one.
the rejected command or in the preceding or subsequent Module: DFHCSDUP
commands in the input stream. Correct the commands in Destination: SYSLST
error.
Module: DFHCSDUP
Destination: SYSLST DFHCA5256E No resources defined in group grpname.
Explanation: In executing a LIST command, the CSD utility
has found a group header on the CSD file for which no group
DFHCA5251I resource object in group grpname is replaced. elements exist.
Explanation: A resource definition existed in both source and System action: The CSD utility continues to process the LIST
target groups. Based on the CSD utility commands submitted, command, but will not list elements of the named group.
the utility has replaced the definition in the target group with User response: Run the DFHCSDUP VERIFY utility to verify
that from the source group. the group.
v resource is the type of the resource Module: DFHCSDUP
v object is the name of the object Destination: SYSLST
v grpname is the name of the group.
System action: Normal utility processing continues.
User response: None. DFHCA5257E Length of 'TO' prefix must be less than or
Module: DFHCSDUP equal to length of 'GROUP' prefix.
Destination: SYSLST Explanation: During the execution of a generic COPY
command, the batch update utility found the length of the
prefix of the generic group specified in the TO keyword to be
DFHCA5252I resource object copied to group grpname. greater than the length of the prefix of the generic GROUP
Explanation: The CSD utility has correctly copied a resource keyword.
definition to the specified group, where: System action: The utility ignores the command to prevent
v resource is the type of resource truncation of the TO group name.
v object is the name of the object User response: Correct the command.
v grpname is the name of the group. Module: DFHCSDUP
System action: Normal utility processing continues. Destination: SYSLST
Module: DFHCSDUP
Destination: SYSLST DFHCA5258I Copying group grpname1 to grpname2
Explanation: During the execution of a generic COPY
command, the CSD batch update utility scans the CSD file for
DFHCA5253E Group grpname not found in CSD file - matches to the generic GROUP keyword. For every match, the
FILENAME: filename utility resolves the generic TO keyword, and informs the user
Explanation: The CSD utility has detected a command that of the resulting grpname1 and grpname2 respectively.
attempted to retrieve definitions from the non-existent group, System action: Normal processing continues.
grpname, in the CSD specified in DLBL filename. User response: None.
System action: The utility does not process the command. Module: DFHCSDUP
User response: Either correct the group name in the Destination: SYSLST
command, or make sure that the specified CSD file is the
correct one.
Module: DFHCSDUP DFHCA5259I Unrecognized resource type found in the
Destination: SYSLST CSD file and has been ignored.
Explanation: CICS has found an unrecognized resource type
DFHCA5254E resource object already exists in the target any of the function codes in the language definition table. This
group. can occur for one of the following reasons:
Explanation: The CSD utility detected a command that 1. You are using a CICS release that does not support a type
attempted to add a definition to a group that already of definition that was created on the CSD file by a later
contained a definition of an object with the same name, where: CICS release.
v resource is the type of resource 2. The language definition table (DFHEITSP or DFHEITCU) is
v object is the name of the object. invalid for this CICS release.
System action: The CSD utility does not process the 3. The CSD manager (DFHDMP) has passed an invalid CSD
command. record buffer to DFHPUP. This is a CICS internal logic
User response: Change the name in the command, or alter error.

DFHCA5261W • DFHCA5266W
System action: The resource is ignored and the operation 4. Return control to the invoker of the utility.
continues.
Definitions that have already been migrated will remain on
User response: Determine which of the possible reasons
the CSD. The VSE user abend code is 0308
caused the error. If you can eliminate reasons 1 and 2, you can
User response:
assume that reason 3 applies.
1. Run the DFHCSDUP VERIFY utility.
Take action corresponding to the reason you have established 2. Delete the groups created by the failing MIGRATE
as follows: command.
1. Ignore the message. 3. Keep the assembly listing for the failing table and keep the
2. Ensure that the library contains versions of DFHEITSP and DFHCSDUP dump, if available. You need further
DFHEITCU that are valid for the CICS release you are assistance from IBM to resolve this problem. See Part 4 of
running. the CICS Problem Determination Guide for guidance on how
3. You need further assistance from IBM to resolve this to proceed.
problem. See Part 4 of the CICS Problem Determination Module: DFHCSDUP
Guide for guidance on how to proceed. Destination: SYSLST
Module: DFHCSDUP
Destination: SYSLST
DFHCA5264W Resource object not defined. Group grpname
not available.
DFHCA5261W RDT is empty. No VTAM resources in Explanation: During the migration of a TCT, the CSD utility
assembled table. could not define a resource object because the target group
Explanation: The CSD utility detected an attempt to migrate grpname was not available. The utility has issued a previous
a TCT that either contains no RDO-supported terminal or message indicating the reason.
sessions definitions, or whose TYPE=INITIAL entry specifies System action: The utility creates no definition for resource
MIGRATE=COMPLETE. object. Normal utility processing continues.
System action: The utility does not create any CSD User response: Review the original message. If necessary,
definitions. recode the TYPE=GROUP macro in the TCT source to name a
User response: Check the TCT source code to see if it suitable group.
contains any RDO-supported definitions. If it does, check that Module: DFHCSDUP
it has been correctly assembled (MIGRATE=YES specified) and Destination: SYSLST
link-edited.
Module: DFHCSDUP
Destination: SYSLST DFHCA5265W Action required to find a suitable
TYPETERM for terminal termid.
Explanation: While migrating a TCT, the CSD utility found a
DFHCA5262S Insufficient storage to build type-matching terminal definition for which it could not create a
chain. corresponding TYPETERM definition.
Explanation: During CSD utility processing, an internal error System action: The utility adds the terminal definition to the
has occurred in the migration of a TCT. This is because of lack CSD file, but it refers to a TYPETERM that may be unsuitable
of storage for TYPETERM definitions. for this device.
System action: The utility attempts to: User response: Use the CEDA transaction to define a suitable
1. Close any files previously opened internally. TYPETERM and alter the TERMINAL definition to refer to the
2. Unload any extract exit routines that were dynamically new TYPETERM.
loaded. Module: DFHCSDUP
3. Invoke the termination exit routine (if supplied). Destination: SYSLST
In any of the above cases, definitions that have already been DFHCA5266W sessions sessions not defined because of error
migrated will remain on the CSD. in associated connection.
User response: Explanation: An error has been detected during the
1. Run the DFHCSDUP VERIFY utility. migration of a TCT. When migrating a session, DFHCSDUP
2. Delete the groups created by the failing MIGRATE checks that the associated CONNECTION has been defined
command. successfully. If it has not, DFHCSDUP abnormally terminates
3. Allocate a larger region size in the utility JCL, and retry the session definition.
the command. System action: The specified SESSIONS resource is not
Module: DFHCSDUP migrated to the CSD. DFHCSDUP continues with the
Destination: SYSLST migration of subsequent TCT entries.
User response: Use the diagnostic information in the output
listing from the MIGRATE utility to determine why the
DFHCA5263S Error in input RDT. Incorrect sequence of
CONNECTION definition has failed. You can then use RDO to
commands.
DEFINE the CONNECTION and the SESSIONS to the CSD.
Explanation: During CSD utility processing, an internal error
Module: DFHCSDUP
has occurred in the migration of a TCT. This is because of
Destination: SYSLST
abnormal data in the assembled table.
System action: The utility attempts to:
2. Unload any extract exit routines that were dynamically
loaded.

DFHCA5267E • DFHCA5276I
Module: DFHCSDUP
DFHCA5267E resource object not migrated. Target group
Destination: SYSLST
grpname is locked to APPLID applid OPID opid
and cannot be updated at present
Explanation: It is not possible to put the resource resource DFHCA5272I resource object Deleted from group.
into group grpname, because the group is currently locked to Explanation: The CSD utility successfully deleted the named
APPLID applid and OPID opid. The group will be unlocked resource, where:
again when the other user's operation is complete. v resource is the type of resource
System action: The utility does not create definitions for the v object is the name of the object.
resources named in the DFHCA5274 messages which follow. System action: Normal utility processing continues.
Normal utility processing continues with the utility return User response: None.
code set to 8. Module: DFHCSDUP
User response: Resubmit the job later, or choose a different Destination: SYSLST
name for the target group. If the group remains locked,
consult with the user identified by APPLID and OPID. If the
lock remains set for no apparent reason, issue the VERIFY DFHCA5273W resource object is not in group grpname.
command and resubmit. Explanation: The CSD utility detected an attempt to delete a
Module: DFHCSDUP resource which did not exist in the named group, where:
Destination: SYSLST v resource is the type of resource
v object is the name of the object
v grpname is the name of the group.
DFHCA5268E resource object not migrated. grpname already System action: The utility does not process the DELETE
exists as a list. command.
Explanation: The name chosen for the target GROUP User response: Check that you have coded the group and
duplicates that of an existing LIST on the CSD. resource names correctly.
System action: The utility does not create definitions for the Module: DFHCSDUP
resources named in the DFHCA5274 messages which follow. Destination: SYSLST
Normal utility processing continues with the utility return
code set to 8.
User response: Choose a different name for the target group DFHCA5274W resource object not migrated. Group grpname is
and change the appropriate TYPE=GROUP macro in the FCT not available.
source. Explanation: During the migration of an FCT, the CSD utility
Module: DFHCSDUP could not define the resource resource because the target group
Destination: SYSLST grpname was not available. The utility has issued a previous
message indicating the reason why.
System action: The utility creates no definition for the
DFHCA5269E resource object not migrated. Group grpname is resource named object. Normal utility processing continues.
IBM protected. User response: Review the original message. If necessary
Explanation: An attempt was made to add a definition to an recode the TYPE=GROUP macro in the FCT source to name a
IBM supplied group (groups beginning with "DFH"). suitable group.
System action: The utility creates no definition for the Module: DFHCSDUP
resources named in the DFHCA5274 messages which follow. Destination: SYSLST
Normal utility processing continues with the utility return
code set to 8.
User response: Change the input source to name a different DFHCA5275S Command not executed. Group grpname is not
target group whose name does not begin with "DFH". the member of list listname.
Module: DFHCSDUP Explanation: The REMOVE command being executed names
Destination: SYSLST a GROUP that is not a member of LIST listname.
DFHCA5270I {group | list} xxxxxxxx deleted from the CSD. If commands are being read from a SYSIPT data stream,
Explanation: The CSD utility has successfully deleted a subsequent commands (except LIST commands) are checked
group or list from the primary CSD file. for syntax only. (If the primary CSD file cannot be opened, the
System action: Normal utility processing continues. LIST command is not processed either.)
Module: DFHCSDUP
Destination: SYSLST
User response: Correct the command and resubmit a
DFHCSDUP job to execute the failing command and any
DFHCA5271S Unable to delete {group | list} xxxxxxxx from subsequent commands that were suppressed.
the CSD. Module: DFHCSDUP
Explanation: During CSD utility processing, an error in Destination: SYSLST
accessing the CSD file caused a delete operation to fail.
System action: The utility does not process the DELETE DFHCA5276I Group grpname removed from list listname.
command. The group or list to be deleted remains on the CSD Explanation: The REMOVE command has successfully
file. removed group grpname from LIST listname.
User response: You need further assistance from IBM to System action: Normal execution continues.
resolve this problem. See Part 4 of the CICS Problem User response: None.

DFHCA5277I • DFHCA5286E
Module: DFHCSDUP
DFHCA5284E Error analyzing RDL subcommand: xxxxxxxx.
Destination: SYSLST
Explanation: The CSD utility found an internal error in the
data loaded while processing the indicated (truncated)
DFHCA5277I List list deleted from CSD. UPGRADE, INITIALIZE, or MIGRATE command.
Explanation: The final group has been removed from list System action: The utility attempts to:
listname. The list has therefore been deleted. 1. Close any files previously opened internally.
System action: Processing continues. 2. Unload any extract exit routines that were dynamically
User response: None. loaded.
Module: DFHCSDUP 3. Invoke the termination exit routine (if supplied).
Destination: SYSLST 4. Return control to the invoker of the utility.
DFHCA5280I Processing definitions from library member Determination Guide for guidance on how to proceed.
xxxxxxxx. Module: DFHCSDUP
Explanation: The CSD utility has successfully loaded data Destination: SYSLST
from the named library member.
System action: Normal utility processing continues.
User response: None. DFHCA5285E Invalid verb in RDL subcommand: xxxxxxxx.
Module: DFHCSDUP Explanation: The CSD utility found an internal error in the
Destination: SYSLST data loaded while processing the indicated (truncated)
UPGRADE, INITIALIZE, or MIGRATE command.
System action: The utility attempts to:
DFHCA5281S Data loaded from library member xxxxxxxx is 1. Close any files previously opened internally.
invalid. 2. Unload any extract exit routines that were dynamically
Explanation: The CSD utility has found an error in data loaded.
loaded from the named library member. 3. Invoke the termination exit routine (if supplied).
System action: The utility attempts to: 4. Return control to the invoker of the utility.
1. Close any files previously opened internally. User response: You need further assistance from IBM to
2. Unload any extract exit routines that were dynamically resolve this problem. See Part 4 of the CICS Problem
loaded. Determination Guide for guidance on how to proceed.
3. Invoke the termination exit routine (if supplied). Module: DFHCSDUP
4. Return control to the invoker of the utility. Destination: SYSLST
User response: Obtain a dump containing the failing library
member.
DFHCA5286E Unable to create resource definition on CSD
You need further assistance from IBM to resolve this problem. file, RDL subcommand: xxxxxxxx.
See Part 4 of the CICS Problem Determination Guide for Explanation: This message is issued during the processing of
guidance on how to proceed. the indicated (truncated) command for one of the following
Module: DFHCSDUP reasons:
Destination: SYSLST 1. The CSD is full (in which case, messages DFHCA5175 and
DFHCA5176 accompanies this one)
2. The CSD was defined as read-only (in which case, message
DFHCA5282E Unable to get storage for library member
DFHCA5174 accompanies this message)
xxxxxxxx.
3. The TCT being migrated contained a terminal entry with a
Explanation: There is insufficient storage available to load
name unacceptable to RDO (in which case, message
the library member xxxxxxxx.
System action: The utility terminates processing of the
4. A list or group cannot be used due to the failure of a
command that required access to the named library member.
previous update operation (in which case, message
User response: If the JCL EXEC statement specifies
SIZE=DFHCSDUP then you need to increase your partition
5. The resource definition list being used to INITIALIZE or
size by using the ALLOC command. For information on how
UPGRADE the CSD file contained a definition with an
to do this see the description of the ALLOC command in the
invalid resource name or group name
z/VSE System Control Statements manual.
6. A logic error occurred in DFHCSDUP or an internal error
Module: DFHCSDUP
was detected in the data contained in the loaded table.
Destination: SYSLST
System action: The system action depends on the reason the
message is issued, as follows.
DFHCA5283S RDL subcommand exceeds 1024 bytes: 1. Migration of the TCT table is terminated immediately.
xxxxxxxx. 2. Processing of the UPGRADE or INITIALIZE command is
Explanation: The CSD utility found an internal error in the terminated
data loaded while processing the indicated (truncated) 3. The utility attempts to:
UPGRADE, INITIALIZE, or MIGRATE command. a. Close any files previously opened internally.
System action: The CSD utility terminates abnormally. b. Unload any extract exit routines that were dynamically
User response: You need further assistance from IBM to loaded.
resolve this problem. See Part 4 of the CICS Problem c. Invoke the termination exit routine (if supplied).
Determination Guide for guidance on how to proceed. d. Return control to the invoker of the utility.
Module: DFHCSDUP 4. The command is not executed, and execution of further
Destination: SYSLST DFHCSDUP commands in the job stream is suppressed.

DFHCA5287 • DFHCA5507E
5. As in (3) above.
6. As in (3) above.
executed. xxxxxxx option conflicts with
yyyyyyy option and is ignored.
In ALL cases, all the definitions created by this command up Explanation: Two options, xxxxxxx and yyyyyyy, that are
to the point of failure remain on the CSD. mutually exclusive have been specified.
User response: The user response depends on the reason the System action: The command analyser ignores the command.
message is issued, as follows. User response: Correct the command.
1. See message DFHCA5175 and DFHCA5176. Module: DFHCAP, DFHCSDUP
2. See message DFHCA5174.
3. Change the name of the terminal and all references to it.
xxxxxxx, yyyyyyy
Also refer to the user response for message DFHCA5165.
Destination: CSMT
4. See message DFHCA5142.
5. This is a CICS logic error. See instruction for 6 below.
6. This is a CICS logic error. You need further assistance from DFHCA5504E date time applid netname tranid Command not
IBM to resolve this problem. See Part 4 of the CICS Problem executed. Use of xxxxxxx option implies
Determination Guide for guidance on how to proceed. A yyyyyyy option must be specified.
CICS background trace of the failure may aid them in Explanation: Option xxxxxxx requires another value, yyyyyyy.
problem diagnosis. System action: The command analyser ignores the command.
Module: DFHCSDUP User response: Specify yyyyyyy.
Destination: SYSLST Module: DFHCAP, DFHCSDUP
DFHCA5287 EXTRACT terminated at user's request xxxxxxx, yyyyyyy
RC=retcode. Destination: CSMT
Explanation: A batch job has issued a CSD utility EXTRACT
command. The EXTRACT command has been terminated DFHCA5505W date time applid netname tranid Program
because of a non-zero value in register 15 on return from a DFHMSP requires a TWASIZE of at least 528.
user exit program. Subsequent messages will indicate any Explanation: A DEFINE or CREATE TRANSACTION
further problems encountered by the utility. command for the message switching program, DFHMSP, has
System action: Execution of the utility command is given it a TWASIZE of less than 528 bytes. If it is to be a
terminated. This message is followed by DFHCA5104. definition for the CICS-supplied program of that name then it
User response: Determine the cause of the error detected by will not execute correctly.
the user exit program using the return code retcode provided System action: Normal processing continues.
and the relevant documentation of the user exit program. User response: Check that the resulting resource definition is
Module: DFHCSDUP as you expect.
Destination: SYSLST Module: DFHCAP, DFHCSDUP
DFHCA5501E date time applid netname tranid Command not Destination: CSMT
executed. keyword must be specified.
Explanation: A keyword keyword, which is required in the DFHCA5506E date time applid netname tranid Command not
command, has been omitted or was incorrectly specified. An executed. For xxxxxxx many options,
earlier message identifies if the latter case is applicable. including yyyyyyy, are meaningless.
System action: The command analyser ignores the command. Explanation: A keyword or value has been specified that is
User response: Correct the command. not consistent with another.
Module: DFHCAP, DFHCSDUP System action: The command analyser ignores the command.
XMEOUT Parameters: date, time,applid, netname, tranid, keyword User response: Correct the command.
Destination: CSMT Module: DFHCAP, DFHCSDUP
DFHCA5502W date time applid netname tranid xxxxxxx implies xxxxxxx, yyyyyyy
yyyyyyy. Destination: CSMT
Explanation: The value xxxxxxxx specified in a DEFINE or
CREATE command has caused another value yyyyyyyy, which DFHCA5507E date time applid netname tranid Command not
is not a normal default, to be assumed. executed. xxxxxxx value must be greater than
System action: Normal utility processing continues. yyyyyyy value.
User response: Check that the resulting resource definition is Explanation: A value has been specified that is not consistent
acceptable. If you accept this default, no further action is with another. xxxxxxx must be greater than yyyyyyy.
required. System action: The command analyser ignores the command.
If the resultant default is not acceptable, you must decide User response: Correct the command.
whether to modify the definition, or to delete it and start Module: DFHCAP, DFHCSDUP
again. XMEOUT Parameters: date, time,applid, netname, tranid,
Module: DFHCAP, DFHCSDUP xxxxxxx, yyyyyyy
XMEOUT Parameters: date, time,applid, netname, tranid, Destination: CSMT
xxxxxxx, yyyyyyy
Destination: CSMT

DFHCA5509E • DFHCA5518W
DFHCA5509E date time applid netname tranid Command not DFHCA5514E date time applid netname tranid Command not
executed. xxxxxxx name must not be the same executed. With SESSNAME there can only be
as yyyyyyy name. one COUNT and its value must be 1.
Explanation: Some values in DEFINE or CREATE commands Explanation: The use of SESSNAME in a DEFINE or
must not be the same as the name of the resource. xxxxxxx CREATE SESSIONS command means that a single-session,
must not have the same name as yyyyyyy. either for sending or receiving, is required.
System action: The command analyser ignores the command. System action: The command is ignored.
User response: Correct the command. User response: Correct the command.
Module: DFHCAP, DFHCSDUP Module: DFHCAP, DFHCSDUP
XMEOUT Parameters: date, time,applid, netname, tranid, XMEOUT Parameters: date, time,applid, netname, tranid
xxxxxxx, yyyyyyy Destination: CSMT
Destination: CSMT
DFHCA5515W date time applid netname tranid

DFHCA5510W date time applid netname tranid xxxxxxx names AUTOPAGE(NO) has been specified for a
beginning with yyyyyyy are reserved and may 3270 print device.
be redefined by CICS. Explanation: A DEFINE or CREATE TYPETERM command
Explanation: CICS supplies standard programs and has AUTOPAGE(NO) and DEVICE(3270P) or
transactions whose names you should usually avoid. DEVICE(LUTYPE3).
System action: Normal processing continues. System action: Normal processing continues.
User response: Check that the resulting resource definition is User response: Check that the resulting resource definition is
as you expect. as you expect.
Module: DFHCAP, DFHCSDUP Module: DFHCAP, DFHCSDUP
XMEOUT Parameters: date, time,applid, netname, tranid, XMEOUT Parameters: date, time,applid, netname, tranid
xxxxxxx, yyyyyyy Destination: CSMT
Destination: CSMT
DFHCA5516W date time applid netname tranid The values of

DFHCA5511W date time applid netname tranid xxxxxxx name DEVICE and SESSIONTYPE are equivalent
yyyyyyy is reserved and may be redefined by to DEVICE(devtype) and have been replaced.
CICS. Explanation: A DEFINE or CREATE TYPETERM command
Explanation: CICS supplies standard programs and has a valid but obsolete DEVICE and SESSIONTYPE
transactions whose names you should usually avoid. combination.
User response: Check that the resulting resource definition is This DEVICE and SESSIONTYPE combination has been
as you expect. replaced by a simpler equivalent indicated by devtype.
Module: DFHCAP, DFHCSDUP System action: Normal processing continues.
User response: Check that the resulting resource definition is
XMEOUT Parameters: date, time,applid, netname, tranid, as you expect. The CICS Resource Definition Guide provides
xxxxxxx, yyyyyyy further information about device equivalents.
XMEOUT Parameters: date, time,applid, netname, tranid, devtype
DFHCA5512W date time applid netname tranid Program name Destination: CSMT
begins with 'DFH' but transaction name does
not begin with 'C'.
Explanation: CICS supplies standard programs and DFHCA5517E date time applid netname tranid Command not
transactions whose naming conventions you should avoid. executed. prefix and COUNT together make
System action: Normal processing continues. more than four characters.
User response: Check that the resulting resource definition is Explanation: In a SESSIONS definition, the prefix parameter
as you expect. (SENDPFX or RECEIVEPFX) is used to generate session names
Module: DFHCAP, DFHCSDUP by adding numeric suffixes up to the corresponding count
value (SENDCOUNT or RECEIVECOUNT). Since the session
XMEOUT Parameters: date, time,applid, netname, tranid names cannot be longer than four characters, when the count
Destination: CSMT of sessions exceeds 99 the prefix can only be one character.
DFHCA5513E date time applid netname tranid Command not Module: DFHCAP, DFHCSDUP
executed. The second value of xxxxxxx must
not be greater than the first. XMEOUT Parameters: date, time,applid, netname, tranid, prefix
Explanation: Some keywords take pairs of values which are Destination: CSMT
essentially maximum and minimum values.
System action: The utility ignores the command.
User response: Correct the command. DFHCA5518W date time applid netname tranid XTRANIDS
Module: DFHCAP, DFHCSDUP xxxxxxx are reserved and may be redefined
by CICS.
XMEOUT Parameters: date, time,applid, netname, tranid, xxxxxxx Explanation: CICS supplies programs and transactions whose
Destination: CSMT names you should usually avoid.

User response: Check that the resulting resource definition is

as you expect.
executed. File DFHCSD must be defined in
the SIT and not the CSD.
XMEOUT Parameters: date, time,applid, netname, tranid, xxxxxxx Explanation: DFHCSD has been defined via a DEFINE or
Destination: CSMT CREATE command rather than in the SIT. This is not allowed.
User response: Correct the command. Define DFHCSD in the
DFHCA5519E date time applid netname tranid Command not SIT.
executed. xxxxxxx value contains an invalid y. Module: DFHCAP, DFHCSDUP
Explanation: All character values in DEFINE or CREATE
commands are subject to rules which, depending on the value, XMEOUT Parameters: date, time,applid, netname, tranid
disallow certain characters. Destination: CSMT
DFHCA5524W date time applid netname tranid BMS route for
The CICS Resource Definition Guide provides further console may cause unpredictable results if
information about these rules under the individual attributes maps or TEXT(ACCUM) used on device.
for the syntax of the DEFINE commands. Explanation: The routing of multiline maps or accumulated
Module: DFHCAP, DFHCSDUP text to the console is not supported.
XMEOUT Parameters: date, time,applid, netname, tranid, User response: Ensure that the unsupported console
xxxxxxx, y operations are disabled.
DFHCA5520W date time applid netname tranid The value of Destination: CSMT
DEVICE is equivalent to xxxxxxx and has
been replaced.
Explanation: A DEFINE or CREATE TYPETERM command DFHCA5525W date time applid netname tranid xxxxxxxx value
has a valid but obsolete DEVICE value which has been is not valid, yyyyyyyy has been assumed.
replaced by a simpler equivalent. Explanation: The value xxxxxxxx is not valid. The value
System action: Normal processing continues. yyyyyyyy has been assumed.
User response: Check that the resulting resource definition is System action: The command is ignored.
as you expect. User response: Correct the command.
The CICS Resource Definition Guide provides further
information about these simpler equivalent devices. XMEOUT Parameters: date, time,applid, netname, tranid,
Module: DFHCAP, DFHCSDUP xxxxxxxx, yyyyyyyy
Destination: CSMT
XMEOUT Parameters: date, time,applid, netname, tranid, xxxxxxx
Destination: CSMT
DFHCA5526E date time applid netname tranid xxxxxxxx must
have rows and columns specified.
DFHCA5521E date time applid netname tranid Command not Explanation: xxxxxxxx must have rows and columns
executed. xxxxxxx value yyyyyyy is invalid. specified.
Explanation: A value yyyyyyyy has been specified for System action: The command is ignored.
keyword xxxxxxxx which is not valid. It may for instance be User response: Correct the command.
non-numeric. Module: DFHCAP, DFHCSDUP
User response: Correct the command. XMEOUT Parameters: date, time,applid, netname, tranid,
Module: DFHCAP, DFHCSDUP xxxxxxxx
Destination: CSMT
xxxxxxx, yyyyyyy
Destination: CSMT DFHCA5527E date time applid netname tranid Command not
executed. Remote options are ignored for
programs starting with DFH.
DFHCA5522E date time applid netname tranid Command not Explanation: CICS supplies standard programs which are not
executed. Length of xxxxxxx value is more allowed to have remote attributes.
than allowed. System action: The command is ignored.
Explanation: All character values in DEFINE or CREATE User response: Correct the command by deleting the remote
commands are of limited length attributes from the program definition.
System action: The command is ignored. Module: DFHCAP, DFHCSDUP
Module: DFHCAP, DFHCSDUP XMEOUT Parameters: date, time,applid, netname, tranid
Destination: CSMT
XMEOUT Parameters: date, time,applid, netname, tranid, xxxxxxx
Destination: CSMT

DFHCA5528E • DFHCA5537W
DFHCA5528E date time applid netname tranid Command not DFHCA5533W date time applid netname tranid Specified
executed. Value of keyword is out of valid keyword1 value is less than keyword2 value.
range. The default value has been assumed.
Explanation: An invalid value has been supplied for the Explanation: A value has been specified for keyword1 that is
specified keyword. incompatible with the value for keyword2.
System action: The command is ignored. System action: The command analyser assumes the default
User response: Supply a valid keyword value and retry. value for keyword1 and processes the command.
Module: DFHCAP, DFHCSDUP User response: Ensure that the resulting resource definition is
acceptable.
XMEOUT Parameters: date, time,applid, netname, tranid, keyword Module: DFHCAP, DFHCSDUP
Destination: CSMT
keyword1, keyword2
DFHCA5529E date time applid netname tranid keyword or Destination: CSMT
keyword must be specified.
Explanation: Neither of the indicated keywords has been
specified. When defining a resource, you must specify one of DFHCA5534W When you change the value of DEVICE
these keywords. many other values may be changed for you.
System action: The command is ignored. Explanation: When ALTERing the DEVICE in a TYPETERM
User response: Supply one of the indicated keywords and resource definition, the batch update utility changes forced
retry. values that are incompatible with the new DEVICE. However,
Module: DFHCAP, DFHCSDUP dependent default values are not changed, and may now be
incompatible.
XMEOUT Parameters: date, time,applid, netname, tranid, System action: Normal utility processing continues.
keyword, keyword User response: Check that the resulting resource definition is
Destination: CSMT as you expect.
See the CICS Resource Definition Guide for more guidance.
DFHCA5530W date time applid netname tranid XTRANIDS Module: DFHCSDUP
ending with string are reserved and may be Destination: SYSLST
redefined by CICS.
Explanation: CICS supplies programs and transactions whose
names you should usually avoid. DFHCA5535E date time applid netname tranid Command not
System action: Normal processing continues. executed. restype name resname is reserved by
User response: Check that the resulting resource definition is CICS.
as you expect. Explanation: The user specified a resource name resname for
Module: DFHCAP, DFHCSDUP resource type restype which is reserved for use by CICS.
XMEOUT Parameters: date, time,applid, netname, tranid, string User response: Specify a different resource name.
XMEOUT Parameters: date, time,applid, netname, tranid, restype,
DFHCA5531W date time applid netname tranid XTRANIDS resname
beginning with string are reserved and may Destination: CSMT
be redefined by CICS.
Explanation: CICS supplies programs and transactions whose
names you should usually avoid. DFHCA5536W date time applid netname tranid keyword1 and
System action: Normal processing continues. keyword2 attributes are inconsistent if
User response: Check that the resulting resource definition is definition is being shared with a back-level
as you expect. release.
Module: DFHCAP, DFHCSDUP Explanation: keyword1 has been superceded by keyword2.
However, keyword1 has been kept for compatibility reasons.
XMEOUT Parameters: date, time,applid, netname, tranid, string After updating or creating the resource, the value specified for
Destination: CSMT keyword1 has become inconsistent with the value specified for
keyword2.
DFHCA5532E date time applid netname tranid Command not System action: The resource is created or updated.
executed. An invalid combination of rows User response: If sharing the resource with a back level
and columns has been specified for release, ensure that the resulting resource definition is
ALTSCREEN. acceptable. Otherwise, ignore the message.
Explanation: One of the specified values is zero and the Module: DFHCAP, DFHCSDUP
other is non-zero. This is an invalid combination. XMEOUT Parameters: date, time,applid, netname, tranid,
System action: The command is ignored. keyword1, keyword2
User response: Ensure that a valid combination of Destination: CSMT
ALTSCREEN rows and columns is specified. See the CICS
Resource Definition Guide for details of valid combinations.
Module: DFHCAP, DFHCSDUP DFHCA5537W date time applid netname tranid Prefix allowed
to default. Use of defaults is recommended
XMEOUT Parameters: date, time,applid, netname, tranid, for MRO sessions only.
ALTSCREEN Explanation: A null value has been accepted for a send or
Destination: CSMT receive prefix for an LU6.1 or MRO session. The default value
'>' is supplied by CICS for send sessions and '<' for receive

DFHCA5538W • DFHCA5603E
sessions. These values are the default prefixes for MRO

DFHCA5600E Unable to get storage for module DFHCICS.
session names. The use of these prefixes is allowed for LU6.1
Primary CSD has not been initialized.
sessions, but is not recommended if MRO session names with
the same prefixes are in use, because duplicate names may Explanation: There is insufficient storage to load module
occur if large numbers of sessions are defined. DFHCICS.
System action: CICS will generate session names using these System action: Processing of the INITIALIZE command is
prefixes. terminated.
User response: If this is an LU6.1 session it is recommended User response: Ensure that there is sufficient storage to load
that a different prefix should be chosen. the DFHCICS module.
Module: DFHCAP, DFHCSDUP Module: DFHCSDUP
Destination: SYSLST
Destination: CSMT
DFHCA5601E Unable to load the {PPT | PCT | FCT | RDT
| LD} table named table.
DFHCA5538W date time applid netname tranid resource names
Explanation: Table table cannot be loaded.
starting with x may conflict with system
System action: The system action depends on the type of
sessions names.
table.
Explanation: The resource resource has been given a name
LD DFHCSDUP cannot process the command. The
starting with the character x, which might be used for
system-generated SESSIONS names. utility attempts to:
System action: The definition is created. 1. Close any files previously opened internally.
User response: Ensure there is no conflict with the name 2. Unload any EXTRACT exit routines that were
given to the resource and SESSIONS names. dynamically loaded.
Module: DFHCAP, DFHCSDUP 3. Invoke the termination exit routine, if supplied.
XMEOUT Parameters: date, time,applid, netname, tranid, PPT, PCT, FCT or RDT
resource, x The CSD utility cannot load the table, and
Destination: CSMT terminates the processing of the utility command.
User response: Refer to any preceding message issued by the
DFHCA5539S date time applid netname tranid keyword is not operating system to determine the reason for the failure.
valid because it starts with the reserved If your table assembly and link-editing is successful, the PPT,
character or string string. PCT, FCT or RDT should be in the library. The LD is in the
Explanation: The name you have given to keyword keyword
load library of the supplied pregenerated CICS system.
is not valid because the name begins with a reserved character
Module: DFHCSDUP
or string such as "C" or "DFH".
Destination: SYSLST
System action: The definition is not created.
User response: Change the name of the keyword.
Module: DFHCAP DFHCA5602E Unable to unload the {PPT | PCT |FCT |
XMEOUT Parameters: date, time,applid, netname, tranid, RDT | LD} table named table.
keyword, string Explanation: Table table cannot be unloaded.
Destination: CSMT System action: The system action depends on the type of
table.
LD DFHCSDUP cannot process the command. The
DFHCA5544S date time applid netname tranid Command not utility attempts to:
executed. DSNAME value 'dsname' is invalid. 1. Close any files previously opened internally.
msg. 2. Unload any EXTRACT exit routines that were
Explanation: The DSNAME dsname is invalid because its dynamically loaded.
name does not conform to the VSAM data set naming rules. 3. Invoke the termination exit routine, if supplied.
See the VSE/VSAM Commands manual for more information
on VSAM dataset naming rules.
PPT, PCT, FCT or RDT
System action: The definition is not created. Message insert
The CSD utility cannot unload the table, and
msg gives an indication of the reason for the error. It is one of:
terminates the processing of the utility command.
INVALID CHARACTER x in DSNAME.
User response: Refer to any preceding message issued by the
Character x is not in the valid character set of A-Z
operating system to determine the reason for the failure.
0-9 $ @ # . and -.
INVALID SEGMENT LENGTH. If your table assembly and link-editing is successful, the PPT,
All name segments should be between 1 and 8 PCT, the FCT or RDT should be in the library. The LD is in
characters the load library of the supplied pregenerated CICS system.
SEGMENT NAME STARTS WITH CHARACTER x. Module: DFHCSDUP
A segment name must start with an alphabetic or Destination: SYSLST
national character (@ # $).
DSNAME ENDS WITH A PERIOD.
A DSNAME must not end in a period. DFHCA5603E Unable to locate the {PPT | PCT |FCT | RDT
User response: Correct the name specified. | LD} table named table.
Module: DFHCAP, DFHCSDUP Explanation: Table table cannot be located.
System action: The system action depends on the type of
XMEOUT Parameters: date, time,applid, netname, tranid, dsname, table specified.
msg
Destination: CSMT

LD DFHCSDUP cannot process the command. The Module: DFHCSDUP

utility attempts to: Destination: SYSLST
2. Unload any EXTRACT exit routines that were
dynamically loaded. DFHCA5607S Command is terminated. An error occurred
3. Invoke the termination exit routine, if supplied. while reading the first secondary CSD record.
4. Return control to the invoker of the utility. Explanation: An I/O error has occurred on the secondary
PPT, PCT, FCT or RDT CSD file.
The CSD utility cannot locate the table, and System action: The SERVICE command is terminated. If
terminates the processing of the utility command. commands are being read from a SYSIPT data stream by the
User response: Refer to any preceding message issued by the utility, subsequent commands are checked for syntax only.
operating system to determine the reason for the failure. User response: Check that the input and output data sets
If your table assembly and link-editing is successful, the PPT, secondary CSD file in the JCL corresponds to the FROMCSD
PCT, FCT or RDT should be in the library. The LD is in the parameter in the SERVICE utility command.
load library of the supplied pregenerated CICS system. Module: DFHCSDUP
Destination: SYSLST
DFHCA5608S Command is terminated. An error occurred

DFHCA5604E Unable to obtain storage for the while reading a secondary CSD record.
cross-reference table named table. Explanation: An I/O error has occurred on the secondary
Explanation: DFHCSDUP was unable to obtain storage for CSD file.
table table. System action: The SERVICE command is terminated. If
System action: DFHCSDUP cannot process the command. commands are being read from a SYSIPT data stream by the
utility, subsequent commands are checked for syntax only.
If commands are being read from a SYSIN data stream,
User response: Check that the input and output data sets
subsequent commands (except LIST) are checked for syntax
only. (If the primary CSD file cannot be opened, LIST is not
secondary CSD file in the JCL corresponds to the FROMCSD
processed either.)
parameter in the SERVICE utility command.
If commands are being read from a get-command exit,
If the problem persists, try to obtain a print out of the CSD,
using either the VSAM Access Method Services (AMS) PRINT
command or the DFHCSDUP LIST ALL command. The LIST
will indicate where errors have occurred because they will not
size. For information on how to do this see the description of
print and are therefore easily identifiable.
the ALLOC command in the z/VSE System Control Statements
Module: DFHCSDUP
manual.
Destination: SYSLST
Module: DFHCSDUP
Destination: SYSLST
DFHCA5609S Command is terminated. An error occurred
while writing a primary CSD record.
DFHCA5605E Disallowed character in group or list name
Explanation: An I/O error has occurred on the primary CSD
object.
file.
Explanation: The call to module DFHDMP has failed to
System action: The SERVICE command is terminated. If
construct a valid key for the record created on the CSD file.
commands are being read from a SYSIPT data stream by the
This is because the group or list name contains an invalid
character.
User response: Retry the command, ensuring that a
System action: A CSD record is not created for this
sufficiently large data set is specified for the output (primary)
definition. (If it is a transaction, a generated profile is not
CSD file.
created either.)
Module: DFHCSDUP
User response: Use the CEDA transaction to define the
Destination: SYSLST
resource with a valid name.
Module: DFHCSDUP
Destination: SYSLST DFHCA5611E Command not executed. parameter parameter
must begin with 'DFH'.
Explanation: In a CSD utility MIGRATE command, the
DFHCA5606S Command is not executed. Unable to load the
specified parameter contained an invalid table name or group
service module progname.
name.
Explanation: The service module, progname, cannot be loaded
due to insufficient storage.
User response: Resubmit the MIGRATE command with a
System action: Utility command execution is terminated. If
valid table name or group name.
commands are being read from a SYSIPT data stream by the
Module: DFHCSDUP
Destination: SYSLST
size. For information on how to do this see the description of
the ALLOC command in the z/VSE System Control Statements
manual. Then retry the utility command.

DFHCA5612I resource object in group grpname is unchanged. DFHCA5620E An Illegal Return Code (RC= ret-code) has
Explanation: A resource definition existed in both source and been returned from the {Initialization |
target groups. Based on the CSD utility commands submitted, Get-Command |Termination} exit.
the utility has replaced the resource definition in the target Explanation: The specified user-exit routine has returned a
group. disallowed return code.
System action: Normal utility processing continues. System action: Processing of the utility command is
User response: None. terminated. The exit is not disabled.
Module: DFHCSDUP User response: Investigate the specified exit routine for the
Destination: SYSLST cause of the return code.
Module: DFHCSDUP
Destination: SYSLST
DFHCA5613E Unable to locate the library member member.
Explanation: The member is not in the libraries named in the
JCL. DFHCA5621E A non-zero Return Code has been returned
System action: The utility terminates processing of the from the Put-Message Exit.
command that required access to library member member. Explanation: The put-message exit routine has returned a
User response: Ensure that the member is correctly disallowed return code.
link-edited into the library and resubmit the job. System action: Processing of the utility command is
Module: DFHCSDUP terminated and the put-message exit is disabled.
Destination: SYSLST User response: Investigate the put-message exit routine for
the cause of the return code.
Module: DFHCSDUP
DFHCA5614E Unable to load the library member member. Destination: SYSLST
Explanation: DFHCSDUP could not load library member
member.
System action: The utility terminates processing of the DFHCA5622S The secondary CSD has been closed during
command that required access to the library member. clean-up processing following the
User response: Ensure that the member is correctly interception of an ABEND.
link-edited into the library and resubmit the job. Explanation: An abend has occurred during DFHCSDUP
Module: DFHCSDUP processing. The secondary CSD has been closed during post
Destination: SYSLST abend clean up processing.
System action: Processing of the utility command is
terminated.
DFHCA5617S Command is terminated. An unrecognized User response: Refer to prior messages for further
type of record was encountered while information regarding this problem.
secondary CSD was being read. Module: DFHCSDUP
Explanation: The record-type field of an input CSD record is Destination: SYSLST
invalid.
System action: The SERVICE command is terminated. If
commands are being read from a SYSIPT data stream by the DFHCA5623S The primary CSD has been closed during
utility, subsequent commands are checked for syntax only. clean-up processing following the
User response: Check that the input and output data sets interception of an ABEND.
have been correctly defined, and that the DLBL name for the Explanation: An abend has occurred during DFHCSDUP
secondary CSD file in the JCL corresponds to the FROMCSD processing. The primary CSD has been closed during post
parameter in the SERVICE utility command. abend clean up processing.
System action: Processing of the utility command is
If the problem persists, try to obtain a print out of the CSD, terminated.
using either the VSAM Access Method Services (AMS) User response: Refer to prior messages for further
command or the DFHCSDUP LIST ALL command. The LIST information regarding this problem.
indicates where errors have occurred because they do not Module: DFHCSDUP
print and are therefore easily identifiable. Destination: SYSLST
Module: DFHCSDUP
Destination: SYSLST
DFHCA5624S The Extract exit program has been unloaded
during clean-up processing following the
DFHCA5619W An Invalid value of the PAGESIZE parameter
interception of an ABEND.
has been specified. The default value of 60
Explanation: An abend has occurred during the processing of
lines per page will be used.
an EXTRACT command. The extract exit program specified on
Explanation: A value of the PAGESIZE parameter outside the
the USERPROGRAM keyword of the EXTRACT utility
allowed range (4–9999) has been specified.
command has been unloaded during post-abend cleanup
System action: The default value of 60 lines per page is
processing.
taken.
System action: The EXTRACT command is terminated.
User response: Ensure that a valid PAGESIZE value is
User response: Refer to prior messages for guidance.
specified in future.
Module: DFHCSDUP
Module: DFHCSDUP
Destination: SYSLST
Destination: SYSLST

DFHCA5625 • DFHCC0100
System action: The default file name is used instead.

DFHCA5625 The user program has passed an invalid
User response: Correct the user program parameter list to
FILENAME parameter for filename to
pass a valid filename.
DFHCSDUP.
Module: DFHCSDUP
Explanation: The user program has supplied an alternative
filename as a parameter for either DFHCSD, SYSIPT or SYSLST.
The alternative file name is invalid because it begins with a
blank.
DFHCCxxxx messages
Explanation: A CICS function is taking more time to process
DFHCC0001 applid An abend (code aaa/bbbb) has occurred
than CICS expects. A possible loop has been detected in
at offset X'offset' in the {local | global} catalog,
module modname module modname at offset X'offset'. This is the offset of the
Explanation: An abnormal end (abend) or program check has instruction which was executing at the time the error was
occurred in module modname and will have occurred in either detected.
the local (DFHLCD) or the global (DFHGCD) catalog domains. During initialization, CICS may not have access to the user's
This implies that there may be an error in CICS code. applid coded in the SIT. If CICS produces this message in these
Alternatively, circumstances, it uses the default applid value DBDCCICS.
v Unexpected data has been input, or System action: An exception entry is made in the trace table.
v Storage has been overwritten.
The code aaa/bbbb is a three digit hexadecimal VSE code (if suppressed dumps in the dump table.
applicable), followed by a four digit alphanumeric CICS code.
This is a critical error and CICS is terminated, even if you
The VSE code is a system completion code, for example 0C1.
have specified in the dump table that CICS should not
If a VSE code is not applicable, this field is filled with three
terminate.
referring to a CICS message (for example, AKEA is a CICS Message DFHME0116 is normally produced containing the
abend code; 1310 refers to message DFHTS1310). symptom string for this problem.
User response: Notify the system programmer.
During initialization, CICS may not have access to the user's
You need further assistance from IBM to resolve this problem.
applid coded in the SIT. If CICS produces this message in these
circumstances, it uses the default applid value DBDCCICS.
guidance on how to proceed.
System action: An exception entry is made in the trace table,
Module: DFHCCDM, DFHCCCC
provided that trace is available at this time. A system dump is
taken, unless you have specifically suppressed dumps in the XMEOUT Parameters: applid, {1=local, 2=global}, X'offset',
dump table. modname
terminate. DFHCC0100 applid Global Catalog initialization failure.
{GENERATE ACB | OPEN ACB | GENERATE
RPL | OPEN, SHOWCB.} R15 = X'yy' VSAM
error code = X' zz'
User response: Notify the system programmer. Explanation: A VSAM error has occurred during global
Look up the VSE code, if there is one, in "OS/390 API Abend catalog initialization.
Codes" in section "VSE/Advanced Functions Codes & SVC The VSAM codes given are explained in section "VSE/VSAM
Errors" of z/VSE Messages and Codes - Volume 1. Codes" in z/VSE Messages and Codes - Volume 2.
Then look up the CICS alphanumeric code in “Transaction The possible versions of this message include the text:
Abend Codes (CICS Transaction Server for VSE/ESA)” on v "GENERATE ACB"
page 453. This will tell you, for example, whether the error v "GENERATE RPL"
was a program check, an abend, a runaway or a recovery
The GENCB failed with the R15 condition given in X'yy'.
percolation, and may give you some guidance concerning user
response. The X'zz' code is only meaningful if X'yy' is X'04' when: X'zz'
is the error code returned by VSAM Register 0 in response
You need further assistance from IBM to resolve this problem. to a GENCB macro.
See Part 4 of the CICS Problem Determination Guide for v "OPEN ACB"
OPEN has failed with the R15 condition code X'yy'. This
Module: DFHCCCC, DFHCCDM
was followed by a successful SHOWCB which has placed
XMEOUT Parameters: applid, aaa/bbbb, X'offset', {1=local, the OPEN error code into X'zz'. Also see the message that
2=global}, modname VSAM writes to the operator console and programmer's
Destination: Console listing.
v "OPEN, SHOWCB"
OPEN has failed with the R15 condition code X'yy'.
DFHCC0004 applid A possible loop has been detected in
the {local | global} catalog at offset X'offset' in
module modname

DFHCC0101 • DFHCC0200
This was followed by a SHOWCB which failed, and the R0 Destination: Console
return code from the SHOWCB is given in X'zz'. Also see
the message that VSAM writes to the operator console and
programmer's listing. DFHCC0102 applid Global Catalog data set is already in
use.
Explanation: The VSAM error reported in the previous
DFHCC0100 message suggests that the global catalog is
already being used, possibly by another CICS region. The
global catalog data set cannot be shared.
System action: A system dump is produced, then CICS is
System action: CICS is terminated.
terminated.
User response: Ensure that the DFHGCD DLBL statement for
Message DFHME0116 is normally produced containing the this CICS specifies a different global catalog data set from any
symptom string for this problem. CICS job that is already running.
User response: Look up the error codes in section
If CICS still fails, notify the system programmer. You need
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2,
further assistance from IBM to resolve this problem. See Part 4
correct the error and then retry.
of the CICS Problem Determination Guide for guidance on how
If this fails, notify the system programmer. You need further to proceed.
assistance from IBM to resolve this problem. See Part 4 of the Module: DFHCCDM
CICS Problem Determination Guide for guidance on how to
proceed.
Module: DFHCCDM
XMEOUT Parameters: applid, {1=GENERATE ACB, 2=OPEN
DFHCC0103 LOCAL CATALOG DATA SET IS ALREADY
ACB, 3=GENERATE RPL,4=OPEN, SHOWCB.}, yy, zz
IN USE.
Explanation: The VSAM error reported in the previous
DFHCC0101 message suggests that the local catalog is already
DFHCC0101 LOCAL CATALOG INITIALIZATION being used, possibly by another CICS region. The local catalog
ERROR. {GENERATE ACB | OPEN ACB | data set cannot be shared.
GENERATE RPL | OPEN, SHOWCB.} R15 = System action: CICS is terminated.
X'yy' VSAM ERROR CODE = X'zz' User response: Ensure that the DFHLCD DLBL statement for
Explanation: A VSAM error has occurred during local catalog this CICS specifies a different local catalog data set from any
initialization. CICS job that is already running.
The VSAM codes given are explained in section "VSE/VSAM If CICS still fails, notify the system programmer. You need
Codes" in z/VSE Messages and Codes - Volume 2. further assistance from IBM to resolve this problem. See Part 4
The possible versions of this message include the text: to proceed.
v "GENERATE ACB" Module: DFHCCDM
v "GENERATE RPL" Destination: Console
The GENCB failed with the R15 condition given in X'yy'.
The X'zz' code is only meaningful when X'yy' is X'04' when: DFHCC0104 AN ABEND HAS OCCURRED DURING
X'zz' is the error code returned by VSAM Register 0 in INITIALIZATION OF CATALOG DOMAIN
response to a GENCB macro. IN MODULE DFHCCDM.
v "OPEN ACB" Explanation: DFHCCDM's recovery routine received control
OPEN has failed with the R15 condition code X'yy'. This during pre-initialization of the local catalog (CC) domain.
was followed by a successful SHOWCB which has placed System action: A system dump with dump code
the OPEN error code into X'zz'. Also see the message that KERNDUMP is taken and CICS terminates.
VSAM writes to the operator console and programmer's User response: You need further assistance from IBM to
listing. resolve this problem. See Part 4 of the CICS Problem
v "OPEN, SHOWCB" Determination Guide for guidance on how to proceed.
OPEN has failed with the R15 condition code X'yy'. Module: DFHCCDM
This was followed by a SHOWCB which failed, and the R0
return code from the SHOWCB is given in X'zz'. Also see
the message that VSAM writes to the operator console and DFHCC0200 applid VSAM error on the {local |global}
programmer's listing. catalog data set. VSAM return code in R15 =
System action: A system dump is produced, then CICS is X'yy' RPL-FDBK=X'zz'.
terminated. Explanation: A catalog VSAM operation has produced the
User response: Look up the error codes in section VSAM error given.
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2,
correct the error and then retry. If this fails, notify the system An exception trace, code CC 2B60 or GC 2B60 has also been
programmer. made.
System action: A system dump is produced, then CICS is
You need further assistance from IBM to resolve this problem. terminated. This is a critical error and CICS is terminated,
See Part 4 of the CICS Problem Determination Guide for even if you have specified in the dump table that CICS should
guidance on how to proceed. not terminate.
Module: DFHCCDM

DFHCC0201 • DFHCC0300
Message DFHME0116 is normally produced containing the If CICS was not looping then notify the system programmer,
symptom string for this problem. who should increase the primary space allocated for this data
User response: If possible, correct the VSAM error and set during the next CICS cold start.
restart CICS. For the meaning of the return codes, refer to Module: DFHCCCC
section "VSE/VSAM Codes" in z/VSE Messages and Codes -
XMEOUT Parameters: applid, {1=local, 2=global}
Volume 2.
Inform the system programmer because this indicates a
possible error in CICS code. You may need further assistance
from IBM to resolve this problem. See Part 4 of the CICS DFHCC0203 applid The {local | global} catalog is full.
Problem Determination Guide for guidance on how to proceed. Explanation: The specified catalog data set (DFHLCD or
Module: DFHCCCC DFHGCD) is full. There are two possible reasons for this error:
v The system is in a loop which involves calls to the catalog
XMEOUT Parameters: applid, {1=local, 2=global}, yy, zz to write onto the catalog data set.
Destination: Console v Insufficient primary space was allocated for the catalog
when it was defined. This is the most likely cause if this
message is issued during or shortly after CICS initialization.
DFHCC0201 VSAM ERROR ON THE LOCAL CATALOG
System action: If the error occurs during initialization, a
DATA SET, VSAM RETURN CODE IN R15 =
system dump is produced then CICS is terminated. If the error
X'yy' FDBK=X'zz'.
occurs after initialization, the domain invoking the catalog
Explanation: A local catalog VSAM operation has produced
services will decide what action is appropriate.
the VSAM error given.
User response: Check for any other symptoms of looping
An exception trace, code CC 2B60 or GC 2B60 has also been and act accordingly.
made.
If CICS is not looping, notify the system programmer who
System action: A system dump is produced then CICS is
should increase the primary space allocated for this data set
terminated. This is a critical error and CICS is terminated,
during the next CICS cold start.
even if you have specified in the dump table that CICS should
not terminate. If CICS is looping, this indicates an error in CICS code. You
User response: If possible correct the VSAM error and restart may need further assistance from IBM to resolve this problem.
CICS. For the meaning of the return codes, refer to section See Part 4 of the CICS Problem Determination Guide for
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2. guidance on how to proceed.
Module: DFHCCCC
Inform the system programmer as this indicates a possible
error in CICS code. You may need further assistance from IBM XMEOUT Parameters: applid, {1=local, 2=global}
to resolve this problem. See Part 4 of the CICS Problem Destination: Console
Module: DFHCCCC
Destination: Console DFHCC0300 DFHCCUTL ERROR REPORT. ERROR
{OPENING DFHLCD.|WRITING TO
DFHLCD. R15 = X'yy' VSAM RPL
DFHCC0202 applid The {local | global} catalog has started to FEEDBACK CODE = X'zz'.}
use new secondary space allocation. Explanation: The initialization of the local catalog data set,
Explanation: Secondary space may be specified when the DFHLCD, has failed for the reasons given in the resulting job
catalog data sets DFHLCD and DFHGCD are defined. This output.
message is issued when the catalog starts using an additional System action: Job terminates.
space allocation. User response: For the meaning of the VSAM codes, refer to
section "VSE/VSAM Codes" in z/VSE Messages and Codes -
See the CICS System Definition and Operations Guide for more
Volume 2.
information about controlling CICS storage.
System action: An exception entry is made in the trace table, Correct cause of error indicated and retry.
provided that trace is available at this time. Module: DFHCCUTL
User response: There are two possibilities. Destination: SYSLST
v The system is in a loop which involves calls to the catalog
to write onto the catalog data set. This is the most likely
cause if the system suddenly starts to produce this message
repeatedly.
v Insufficient primary space was allocated for the catalog
when it was defined. This is the most likely cause if this
message is produced either:
– during or shortly after CICS initialization, or
– this message is only produced infrequently (and only a
few are ever produced).
Look for any other symptoms of possible looping, and act

accordingly. If looping has occurred then the system
programmer should redefine the catalog during the next CICS
cold start.

DFHCE3500 • DFHCE3526
DFHCExxxx messages
DFHCE3500 Unable to interpret keyword data. Sign-on is DFHCE3507 Your language code must be three characters.
terminated. Sign-on is terminated.
Explanation: The keyword data supplied when invoking the Explanation: The value of the LANGUAGE keyword is not a
signon transaction is invalid. three-letter code.
System action: Signon terminates. System action: Signon terminates.
User response: Use the correct format to invoke the signon User response: Use a valid language code.
transaction. The correct format is: Module: DFHSNP
CESN USERID=userid,GROUPID=groupid, Destination: Terminal End User
PS=password,NEWPS=new_password,
LANGUAGE=language_code
DFHCE3520 Please type your userid.
See the CICS-Supplied Transactions manual for further Explanation: The system requests a userid.
information on the CESN transaction. System action: None.
Module: DFHSNP User response: Enter your userid.
Destination: Terminal End User Module: DFHSNP
DFHCE3501 Invalid keyword. Sign-on is terminated.

Explanation: The keyword which was entered was invalid. DFHCE3521 CICS sign-on. Please type your userid.
System action: The signon transaction terminates. Explanation: The system requests a userid.
User response: Use a valid character keyword within the System action: The system waits for a response.
range 1-8. User response: Enter your userid.
Module: DFHSNP Module: DFHSNP
Destination: Terminal End User Destination: Terminal End User
DFHCE3502 Your userid must be 1-8 characters. Sign-on is DFHCE3522 CICS sign-on. Please type your userid==>
terminated. Explanation: The system requests a userid.
Explanation: The value of the USERID keyword has less than System action: The system waits for a response.
1 or more than 8 characters. User response: Enter your userid.
System action: Signon terminates. Module: DFHSNP
User response: Use a valid userid. Destination: Terminal End User
Module: DFHSNP
DFHCE3523 Please type your password.
Explanation: The system requests a password.
DFHCE3503 Your password must be 1-8 characters. System action: The system waits for a response.
Sign-on is terminated. User response: Enter your password.
Explanation: The value of the PS keyword has less than 1 or Module: DFHSNP
more than 8 characters. Destination: Terminal End User
System action: Signon terminates.
User response: Use a valid password.
DFHCE3524 Please type your password==>@@@@@@@@
Module: DFHSNP
Explanation: The system requests a password. @@@@@@@@
represents a character string provided by CICS to prevent the
password being seen.
DFHCE3504 Your new password must be 1-8 characters. System action: The system waits for a response.
Sign-on is terminated. User response: Enter your password.
Explanation: The value of the NEWPS keyword has less than Module: DFHSNP
1 or more than 8 characters. Destination: Terminal End User
User response: Use a valid new password.
DFHCE3525 Your password has expired. Please type your
Module: DFHSNP
new password.
Explanation: The system requires a new password.
System action: The system waits for a response.
DFHCE3506 Your groupid must be 1-8 characters. Sign-on User response: Enter a new password.
is terminated. Module: DFHSNP
Explanation: The value of the GROUPID keyword has less Destination: Terminal End User
than 1 or more than 8 characters.
DFHCE3526 Your password has expired. Please type your
User response: Use a valid group name.
new password==>@@@@@@@@
Module: DFHSNP
Explanation: The system requests a new password.
@@@@@@@@ represents a character string provided by CICS
to prevent the new password being seen.


DFHCE3532 Your password is invalid. Please retype.
User response: Enter a new password.
Explanation: The password entered was invalid.
Module: DFHSNP
User response: Enter a valid password.
Module: DFHSNP
DFHCE3527 Use your magnetic (OPID) card or press Destination: Terminal End User
ENTER to cancel.
Explanation: A magnetic card is required.
DFHCE3533 Your password is invalid. Please
System action: The system waits for an opid (magnetic) card.
retype==>@@@@@@@@
User response: Supply badge or terminate transaction.
Explanation: The password entered was invalid.
Module: DFHSNP
Module: DFHSNP
DFHCE3528 Signon failed during SECLABEL checking. Destination: Terminal End User
Explanation: The signon request has failed because the
external security manager (ESM) detected a critical error.
DFHCE3534 Your new password is invalid. Please retype.
System action: The signon transaction terminates.
Explanation: The new password entered was invalid.
User response: Refer to message DFHSN1108 on the CSCS
System action: None.
log for the information and actions necessary to resolve this
problem.
Module: DFHSNP
Module: DFHSNP
DFHCE3535 Your new password is invalid. Please

DFHCE3529 The ESM is currently not accepting signons.
retype==>@@@@@@@@
Please try later.
Explanation: The new password entered was invalid.
Explanation: The signon request has failed because the
external security manager (ESM) was in a tranquil state. When
in a tranquil state, only signons from special users are
Module: DFHSNP
accepted.
User response: The ESM has probably been put into a
tranquil state to allow for ESM database maintenance. DFHCE3536 Invalid OPID. Please enter a valid card or
Determine whether maintenance is currently occurring and press ENTER to cancel.
how long it will take. When maintenance is finished the Explanation: The OPID entered is invalid.
tranquil state should be removed from the ESM which will System action: The system waits for a response.
allow you to sign on to CICS. If the ESM has not been put User response: Enter a valid card or press ENTER to cancel
into a tranquil state then, refer to message DFHSN1108 on the the signon.
CSCS log for the information and actions necessary to resolve Module: DFHSNP
this problem. Destination: Terminal End User
Module: DFHSNP
DFHCE3537 Language is invalid. Please retype.
Explanation: The language code entered is invalid.
DFHCE3530 Your userid is invalid. Please retype. System action: The system waits for a response.
Explanation: Your userid is invalid. User response: Enter a valid language code.
The system requests a userid. Module: DFHSNP
System action: The system waits for a response. Destination: Terminal End User
User response: Enter a valid userid.
Module: DFHSNP DFHCE3538 Language is invalid. Please retype==>
Destination: Terminal End User Explanation: The language code entered is invalid.
DFHCE3531 Your userid is invalid. Please retype==> User response: Enter a valid language code.
Explanation: Your userid is invalid. Module: DFHSNP
The system requests a userid.
User response: Enter a valid userid. DFHCE3539 Please reenter the new password for
Module: DFHSNP verification.
Destination: Terminal End User Explanation: You have entered a new password in the new
password field and you are now being prompted to reenter
the same password to assure yourself of the new password
data.
User response: Reenter the new password in the password
field.

Module: DFHSNP
DFHCE3546 Your signon {userid | group access} has been
revoked. Signon is terminated.
Explanation: The response from the external security
DFHCE3541 Security interface error (rc). Sign-on is manager indicates that either the userid that you use to sign
terminated. on to CICS, or your access to the group that contains it, has
Explanation: An error has been detected in an external been revoked by the system.
security manager. rc is the return code from the external System action: The signon transaction terminates.
security manager. User response: Contact your security administrator.
System action: Signon terminates. Module: DFHSNP
User response: See the appropriate manual for details of the Destination: Terminal End User
macro return codes. The return codes are macro specific.
Module: DFHSNP
DFHCE3547 Security is not active. Sign-on cannot be
performed.
Explanation: A request to sign on to the CICS system was
DFHCE3542 Sign-on is not allowed at this terminal. Your rejected because the CICS security system was not active.
sign-on is ignored.
A user can only sign on to CICS when CICS security is active.
Explanation: The sign on transaction cannot be executed at
the current terminal for one of the following reasons: The CICS security system is activated using the system
v The terminal is defined with a preset userid that cannot be initialization parameter SEC=YES.
changed by signing on System action: The signon transaction terminates.
v The terminal is a surrogate of a terminal in another CICS User response: None.
region, but the sign on transaction is not executing within a Module: DFHSNP
session established by the CRTE transaction. Destination: Terminal End User
User response: Do not use the signon transaction at this
terminal. DFHCE3548 date time applid Critical error has occurred in
Module: DFHSNP DFHSNP. Codes: 1,2,3,4,5.
Destination: Terminal End User Explanation: The signon program, DFHSNP, is abnormally
terminated due to a critical error.
DFHCE3543 You have cancelled your sign-on request. The five codes indicate the cause of the error and where the
Sign-on is terminated. error occurred.
Explanation: The user has pressed ENTER when an OPID Code 1 is an abend code. It can be one of ASNA, ASNB or
card was requested or has entered PF3 on a 3270 terminal ASNC.
device.
System action: The signon transaction terminates. Codes 2, 3, 4 and 5 are codes which help IBM to identify the
User response: Retry the signon procedure. source of the error. They are id_location, EIBFRCODE,
Module: DFHSNP EIBRESP and EIBRESP2.
Destination: Terminal End User System action: DFHSNP is abnormally terminated with a
transaction dump. Message DFHAC2206 is normally issued,
but if no terminal is associated with the task, DFHAC2236
DFHCE3544 Terminal authorization failed. Sign-on is may be issued instead.
terminated. User response: Refer to message DFHAC2206 or
Explanation: The external security manager has responded DFHAC2236. If DFHAC2236 has been issued, the absence of a
negatively to a signon request. terminal is probably the reason for the abend.
User response: Inform the systems programmer, who should Use the abend code given in the message to determine the
refer to message DFHSN1118 on the CSCS log for the relevant reason for the error and the course of action to take. This
information and actions necessary to resolve this problem. enables you to determine whether the abend was caused by
Module: DFHSNP user error or by an error in CICS code. (An error in CICS code
Destination: Terminal End User is signalled by abend code ASNA.)
If you suspect an error in CICS code, you need further
DFHCE3545 Application authorization failed. Sign-on is assistance from IBM to resolve the problem. See Part 4 of the
terminated. CICS Problem Determination Guidefor guidance on how to
Explanation: The external security manager has responded proceed.
negatively to a signon request. Module: DFHSNP
System action: The signon transaction terminates. XMEOUT Parameters: date, time,applid, 1, 2, 3, 4, 5
User response: Inform the systems programmer, who should Destination: CSMT
refer to message DFHSN1119 on the CSCS log for the relevant
information and actions necessary to resolve this problem.
Module: DFHSNP DFHCE3549 Sign-on is complete (Language language).
Destination: Terminal End User Explanation: The user has successfully signed on to the CICS
system.
System action: CICS is ready to receive user transactions.
User response: Use terminal as required for CICS
transactions.

Module: DFHSNP
DFHCE3587 You cannot signon at this terminal at this
time.
Explanation: You cannot signon at this terminal at this time.
DFHCE3550 Sign-off option must be LOGOFF or The SNSCOPE initialization parameter disallows signon to
GOODNIGHT. Sign-off is ignored. more than one terminal at a time. An internal failure during
Explanation: An option other than LOGOFF|GOODNIGHT SNSCOPE checking means that CICS is unable to confirm if
was detected. the user is already signed on elsewhere.
System action: The signoff transaction terminates. System action: The signon transaction terminates. Message
User response: Specify the correct option when invoking DFHUS0120 will have been written to the console. See the
signoff. explanation of this message for further information.
Module: DFHSFP User response: Please report this problem to your CICS
Destination: Terminal End User systems programmer.
Module: DFHSNP
DFHCE3551 date time applid termid DFHSNP has detected
an invalid COMMAREA. It has been
ignored. The data is lost. DFHCE3588 You are already signed on at another
Explanation: While processing a CESN transaction DFHSNP terminal. Signon cannot be performed.
was passed a commarea that was not its own. This may be the Explanation: You cannot sign on at the current terminal
result of an application issuing the EXEC CICS RETURN because you are already signed on at another terminal. The
TRANSID(...) COMMAREA(...) with a transid of nulls SNSCOPE system initialization parameter for the CICS system
(X'00000000'). This could be because the pointer to the transid does not allow you to sign on to more than one terminal at a
is incorrectly set up or may be part of the system design. time.
System action: DFHSNP continues with CESN transaction System action: The signon transaction terminates.
processing. User response: Sign off from the other terminal before you
User response: Investigate whether this message is issued attempt to sign on again.
validly as part of the system design, in which case the Module: DFHSNP
message can be ignored, or is an error. Investigate the Destination: Terminal End User
previous transaction at this terminal.
Module: DFHSNP
DFHCE3589 The external security manager is inactive.
XMEOUT Parameters: date, time,applid, termid Signon cannot be performed.
Destination: CSMT Explanation: You cannot sign on because the external
security manager is not active.
DFHCE3560 Sign-off is not allowed at this terminal. User response: Wait until the external security manager has
Sign-off is ignored. been reactivated before attempting to sign on again.
Explanation: The sign-off transaction cannot be executed at Module: DFHSNP
the current terminal for one of the following reasons: Destination: Terminal End User
v The terminal is defined with a preset userid that cannot be
changed by signing off
v The terminal is a surrogate of a terminal in another CICS DFHCE3590 Sign-off is complete.
region, but the sign-off transaction is not executing within a Explanation: If the user issued a CESN command to sign on
session established by the CRTE transaction. to the system, signoff has been successful. If the user was not
System action: The signoff transaction terminates. signed on, and CICS security was active (SEC=YES system
User response: Do not use the signoff transaction at this initialization parameter) then message DFHSN1213 is written
terminal. to the CSCS log to indicate that the user has logged off but
Module: DFHSFP has not been allowed to sign off.
Destination: Terminal End User System action: Other processing continues.
User response: Use the terminal as required for CICS
transactions.
DFHCE3570 Your groupid is invalid. Please retype. Module: DFHSFP
Explanation: Your group identifier is invalid. Destination: Terminal End User
The system requests a group identifier.
System action: The system waits for a response. DFHCE3591 Sign-off is complete. LOGOFF option is
User response: Enter a valid group identifier. invalid when using CRTE.
Module: DFHSNP Explanation: The terminal is now signed off. The LOGOFF
Destination: Terminal End User option which was specified has been ignored as it is invalid
when using CRTE.
DFHCE3571 Your groupid is invalid. Please retype==> System action: The CICS system, to which the user has
Explanation: Your group identifier is invalid. connected via CRTE, has been signed off.
User response: Do not use the LOGOFF option when signing
The system requests a group identifier. off via CRTE.
System action: The system waits for a response. Module: DFHSFP
User response: Enter a valid group identifier. Destination: Terminal End User
Module: DFHSNP

DFHCE3592 • DFHCP0702I
source of the error. They are id_location (in hexadecimal),

DFHCE3592 Sign-off is complete. GOODNIGHT option is
EIBFRCODE, EIBRESP and EIBRESP2.
invalid when using CRTE.
System action: DFHSFP is abnormally terminated with a
Explanation: The terminal is now signed off. The
transaction dump. Message DFHAC2206 is normally issued,
GOODNIGHT option which was specified has been ignored as
but if no terminal is associated with the task, DFHAC2236
it is invalid when using CRTE.
may be issued instead.
System action: The CICS system, to which the user has
User response: Refer to message DFHAC2206 or
connected via CRTE, has been signed off.
DFHAC2236. If DFHAC2236 has been issued, the absence of a
User response: Do not use the GOODNIGHT option when
terminal is probably the reason for the abend.
signing off via CRTE.
Module: DFHSFP Use the abend code given in the message to determine the
Destination: Terminal End User reason for the error and the course of action to take. This will
enable you to determine whether the abend was caused by
user error or by an error in CICS code. (An error in CICS code
DFHCE3598 date time applid Critical error has occurred in
is signalled by abend code ASFA.)
DFHSFP. Codes: 1,2,3,4,5.
Explanation: The signoff program, DFHSFP, will abnormally If you suspect an error in CICS code, you need further
terminate due to a critical error. assistance from IBM to resolve the problem. See Part 4 of the
The five codes indicate the cause of the error and where the proceed.
error occurred.
Module: DFHSFP
Code 1 is an abend code. It can be ASFA, ASFB or ASFC.
XMEOUT Parameters: date, time,applid, 1, 2, 3, 4, 5
Codes 2, 3, 4 and 5 are codes which help IBM to identify the Destination: CSMT
DFHCPxxxx messages
DFHCP0101I applid CPI initialization has started. DFHCP0701I date time applid tranid program name CPI-C verb
Explanation: This is an informational message indicating the verb used unrecognized CONVERSATION_ID
start of CPI initialization. Conversation_ID.
System action: Initialization continues. Explanation: The application program has used an
User response: None. You can suppress this message with unrecognized conversation_ID on one of its calls to CPI This
the system initialization parameter MSGLVL=0. could mean that:
Module: DFHCPIN1 v The application program has not created a conversation
successfully using either the CMINIT
(Initialize_Conversation) or the CMACCP
(Accept_Conversation) verbs, or
v The application program has used the conversation_ID
DFHCP0102I applid CPI initialization has ended. supplied to it by CPI incorrectly.
Explanation: This is an informational message indicating that System action: CICS returns control to the application
CPI initialization has completed successfully. program with return_code
System action: Initialization continues. CM_PROGRAM_PARAMETER_CHECK.
the system initialization parameter MSGLVL=0. The CPI verb has no effect on either the conversation or the
Module: DFHCPIN1 conversation characteristics.
User response: Determine which error has occurred and
XMEOUT Parameter: applid amend the application program accordingly.
The Common Programming Interface Communications Reference
provides a detailed description of all the CPI verbs and how
DFHCP0103I applid CPI initialization has failed. they should be called.
Explanation: CPI has failed to initialize successfully. Module: DFHCPIC
System action: Message DFHSI1522 follows this message.
CICS terminate or continues initialization depending upon the XMEOUT Parameters: date, time,applid, tranid, program
operator's response to message DFHSI1522. name,verb, Conversation_ID
Destination: CCPI
An exception trace entry is written at the time the failure is
detected.
DFHCP0702I date time applid tranid program name
Other CICS components called by CPI initialization may also
Conversation_ID CPI-C verb verb was
issue messages or write trace entries.
User response: Decide whether CICS can continue execution disallowed because of the conversation state
without CPI support, and respond accordingly to message state.
DFHSI1522. Explanation: The CPI state machine detected a state error.
This means that the conversation was in the wrong state to
You should also investigate why CPI failed to initialize. issue this verb.
Module: DFHCPIN1 System action: CICS returns control to the application
XMEOUT Parameter: applid program with return_code CM_PROGRAM_STATE_CHECK.
Destination: Console The CPI verb has no effect on either the conversation or the
conversation characteristics.

DFHCP0705I • DFHCP0709I
User response: Use the state machine defined in the Common

Programming Interface Communications Reference manual, and
conversation_ID the supplied
the CICS trace information to determine the sequence of CPI
conversation_type parameter
calls issued that caused the state error. Amend the application
CM_MAPPED_CONVERSATION conflicts
program in accordance with the supplied guidelines.
with the current setting of log_data.
Module: DFHCPIC
Explanation: The application program has called CMSCT
XMEOUT Parameters: date, time,applid, tranid, program (Set_Conversation_Type) with a conversation_type parameter
name,Conversation_ID, verb, state of CM_MAPPED_CONVERSATION when it had previously
Destination: CCPI used the CMSLD (Set_Log_Data) verb to create some Log
Data.
DFHCP0705I date time applid tranid program name This is not allowed in CPI.
Conversation_ID invalid conversation_type System action: CICS returns control to the application
parameter (X'conv_type') supplied on the program with return_code
CMSCT (Set_Conversation_Type) verb. CM_PROGRAM_PARAMETER_CHECK.
The CPI verb has no effect on either the conversation or the
(Set_Conversation_Type) with an invalid conversation_type
parameter value.
User response: Amend the application program so that it
System action: CICS returns control to the application
does not use these two verbs in this invalid combination.
program with return_code
CM_PROGRAM_PARAMETER_CHECK. The Common Programming Interface Communications Reference
they should be called.
Module: DFHCPCSA
User response: Amend CMSCT in the application program to
use a valid conversation_type parameter. XMEOUT Parameters: date, time,applid, tranid, program
name,conversation_ID
Destination: CCPI
Module: DFHCPCSA DFHCP0708I date time applid tranid program name
conversation_ID invalid deallocate_type
XMEOUT Parameters: date, time,applid, tranid, program
parameter (X'deallocate_type') supplied on the
name,Conversation_ID, X'conv_type'
CMSDT (Set_Deallocate_Type) verb.
Destination: CCPI
Explanation: The application program has called CMSDT
(Set_Deallocate_Type) with an invalid deallocate_type
DFHCP0706I date time applid tranid program name parameter.
conversation_ID the supplied System action: CICS returns control to the application
conversation_type parameter of program with return_code
CM_MAPPED_CONVERSATION conflicts CM_PROGRAM_PARAMETER_CHECK.
with the current setting of the fill
characteristic CM_FILL_BUFFER.
User response: Amend CMSDT in the application program to
(Set_Conversation_Type) with a conversation_type parameter
use a valid deallocate_type parameter.
of CM_MAPPED_CONVERSATION when it had previously
used the CMSF (Set_Fill) verb to set the fill characteristic. The Common Programming Interface Communications Reference
This is not allowed in CPI.
Module: DFHCPCSB
CM_PROGRAM_PARAMETER_CHECK. XMEOUT Parameters: date, time,applid, tranid, program
name,conversation_ID, X'deallocate_type'
Destination: CCPI
does not use these two verbs in this invalid combination. DFHCP0709I date time applid tranid program name
conversation_ID the supplied deallocate_type
parameter deallocate_type conflicts with the
current setting of the sync_level characteristic
sync_level.
Module: DFHCPCSA
Explanation: The application program has called CMSDT
XMEOUT Parameters: date, time,applid, tranid, program (Set_Deallocate_Type) with a deallocate_type of deallocate_type
name,conversation_ID and with the sync_level characteristic set to sync_level.
Destination: CCPI System action: CICS returns control to the application
CM_PROGRAM_PARAMETER_CHECK.

The CPI verb has no effect on either the conversation or the The CPI verb has no effect on either the conversation or the
conversation characteristics. conversation characteristics.
User response: Amend the application program to remove User response: Amend the application program to remove
this conflict. this conflict.
The Common Programming Interface Communications Reference The Common Programming Interface Communications Reference
provides a detailed description of all the CPI verbs and how provides a detailed description of all the CPI verbs and how
they should be called. they should be called.
Module: DFHCPCSB Module: DFHCPCSD
XMEOUT Parameters: date, time,applid, tranid, program XMEOUT Parameters: date, time,applid, tranid, program
name,conversation_ID, deallocate_type, sync_level name,conversation_ID
Destination: CCPI Destination: CCPI
DFHCP0710I date time applid tranid program name DFHCP0713I date time applid tranid program name
conversation_ID invalid error_direction conversation_ID CMSLD (Set_Log_Data) call
parameter (X'error_direction') supplied on the conflicts with the current conversation_type
CMSED (Set_Error_Direction) verb. of CM_MAPPED_CONVERSATION.
Explanation: The application program has called CMSED Explanation: The application program has called CMSLD
(Set_Error_Direction) with an invalid error_direction (Set_Log_Data) when the conversation_type is
parameter. CM_MAPPED_CONVERSATION.
System action: CICS returns control to the application System action: CICS returns control to the application
program with return_code program with return_code
CM_PROGRAM_PARAMETER_CHECK. CM_PROGRAM_PARAMETER_CHECK.
The CPI verb has no effect on either the conversation or the The CPI verb has no effect on either the conversation or the
conversation characteristics. conversation characteristics.
User response: Amend CMSED in the application program to User response: Amend the application program to remove
use a valid error_direction parameter. this conflict.
Module: DFHCPCSC
XMEOUT Parameters: date, time,applid, tranid, program provides a detailed description of all the CPI verbs and how
name,conversation_ID, X'error_direction' they should be called.
Destination: CCPI Module: DFHCPCSE
DFHCP0711I date time applid tranid program name name,conversation_ID
conversation_ID invalid fill parameter (X'fill') Destination: CCPI
supplied on the CMSF (Set_Fill) verb.
Explanation: The application program has called CMSF
(Set_Fill) with an invalid fill parameter fill.
conversation_ID log_data_length
(log_data_length) supplied on CMSLD
(Set_Log_Data) verb is not in the range 0-512.
Explanation: The application program has called CMSLD
The CPI verb has no effect on either the conversation or the (Set_Log_Data) with a log_data_length parameter that is not in
conversation characteristics. the range 0–512.
User response: Amend CMSF in the application program to System action: CICS returns control to the application
use a valid fill parameter. program with return_code
provides a detailed description of all the CPI verbs and how The CPI verb has no effect on either the conversation or the
they should be called. conversation characteristics.
Module: DFHCPCSD User response: Amend CMSLD in the application program to
use a valid log_data_length parameter.
name,conversation_ID, X'fill' The Common Programming Interface Communications Reference
Destination: CCPI provides a detailed description of all the CPI verbs and how
Module: DFHCPCSE
conversation_ID CMSF (Set_Fill) call conflicts XMEOUT Parameters: date, time,applid, tranid, program
with the current conversation_type of name,conversation_ID, log_data_length
CM_MAPPED_CONVERSATION. Destination: CCPI
Explanation: The application program has called CMSF
(Set_Fill) when the conversation_type is
CM_MAPPED_CONVERSATION.


conversation_ID invalid mode_name_length
parameter (mode_name_length) supplied on the
Module: DFHCPCSH
CMSMN (Set_Mode_Name) verb.
Explanation: The application program has called CMSMN XMEOUT Parameters: date, time,applid, tranid, program
(Set_Mode_Name) with a mode_name_length parameter name,conversation_ID, X'ptr_type'
outside the range of 0–8. Destination: CCPI
CM_PROGRAM_PARAMETER_CHECK. DFHCP0725I date time applid tranid program name
conversation_ID the supplied
The CPI verb has no effect on either the conversation or the prepare_to_receive_type parameter
conversation characteristics. CM_PREP_TO_RECEIVE_CONFIRM is
User response: Amend CMSMN in the application program incompatible with the current setting of the
to use a valid mode_name_length parameter. sync_level characteristic CM_NONE.
Explanation: The application program has called CMSPTR
(Set_Prepare_To_Receive_Type) with a prepare_to_receive_type
parameter of CM_PREP_TO_RECEIVE_CONFIRM and with
the sync_level characteristic set to CM_NONE.
Module: DFHCPCSF
XMEOUT Parameters: date, time,applid, tranid, program program with return_code
name,conversation_ID, mode_name_length CM_PROGRAM_PARAMETER_CHECK.
Destination: CCPI
DFHCP0721I date time applid tranid program name User response: Amend the application program to remove
conversation_ID the partner_lu_name_length this conflict.
(partner_lu_name_len) supplied on the
CMSPLN (Set_Partner_LU_Name) verb is not
in the range 1-17.
Explanation: The application program has called CMSPLN
Module: DFHCPCSH
(Set_Partner_LU_Name) with a partner_lu_name_length
parameter outside the range 1–17. XMEOUT Parameters: date, time,applid, tranid, program
System action: CICS returns control to the application name,conversation_ID
program with return_code Destination: CCPI
The CPI verb has no effect either on the conversation or DFHCP0726I date time applid tranid program name
conversation characteristics. conversation_ID invalid receive_type parameter
User response: Amend CMSPLN in the application program (X'receive_type') supplied on the CMSRT
to use a partner_lu_name_length parameter within the range (Set_Receive_Type) verb.
1-17. Explanation: The application program has called CMSRT
(Set_Receive_Type) with an invalid receive_type parameter.
Module: DFHCPCSG
name,conversation_ID, partner_lu_name_len
User response: Amend CMSRT in the application program to
Destination: CCPI
use a valid receive_type parameter.
conversation_ID invalid
prepare_to_receive_type parameter
Module: DFHCPCSI
(X'ptr_type') supplied on the CMSPTR
(Set_Prepare_To_Receive_Type) verb. XMEOUT Parameters: date, time,applid, tranid, program
Explanation: The application program has called CMSPTR name,conversation_ID, X'receive_type'
(Set_Prepare_To_Receive_Type) with an invalid Destination: CCPI
prepare_to_receive_type parameter.
program with return_code DFHCP0727I date time applid tranid program name
CM_PROGRAM_PARAMETER_CHECK. conversation_ID invalid return_control
parameter (X'return_control') supplied on the
The CPI verb has no effect on either the conversation or the CMSRC (Set_Return_Control) verb.
conversation characteristics. Explanation: The application program has called CMSRC
User response: Amend CMSPTR in the application program (Set_Return_Control) with an invalid return_control parameter.
to use a valid prepare_to_receive_type parameter. System action: CICS returns control to the application


conversation_ID invalid sync_level parameter
The CPI verb has no effect on either the conversation or the (X'sync_level') supplied on the CMSSL
conversation characteristics. (Set_Sync_Level) verb.
User response: Amend CMSRC in the application program to Explanation: The application program has called CMSSL
use a valid return_control parameter. (Set_Sync_Level) with an invalid sync_level parameter.
The Common Programming Interface Communications Reference program with return_code
provides a detailed description of all the CPI verbs and how CM_PROGRAM_PARAMETER_CHECK.
Module: DFHCPCSJ The CPI verb has no effect on either the conversation or the
XMEOUT Parameters: date, time,applid, tranid, program User response: Amend CMSSL in the application program to
name,conversation_ID, X'return_control' use a valid sync_level parameter.
Destination: CCPI
DFHCP0728I date time applid tranid program name they should be called.
conversation_ID invalid send_type parameter Module: DFHCPCSL
(X'send_type') supplied on the CMSST
(Set_Send_Type) verb. XMEOUT Parameters: date, time,applid, tranid, program
Explanation: The application program has called CMSST name,conversation_ID, X'sync_level'
(Set_Send_Type) with an invalid send_type parameter. Destination: CCPI
conversation_ID the supplied sync_level
The CPI verb has no effect on either the conversation or the parameter CM_NONE is incompatible with
conversation characteristics. the current setting of the send_type
User response: Amend CMSST in the application program to characteristic CM_SEND_AND_CONFIRM.
use a valid send_type parameter. Explanation: The application program has called CMSSL
(Set_Sync_Level) with a sync_level parameter of CM_NONE.
The Common Programming Interface Communications Reference The send_type is CM_SEND_AND_CONFIRM.
provides a detailed description of all the CPI verbs and how System action: CICS returns control to the application
they should be called. program with return_code
Module: DFHCPCSK CM_PROGRAM_PARAMETER_CHECK.
XMEOUT Parameters: date, time,applid, tranid, program The CPI verb has no effect on either the conversation or the
name,conversation_ID, X'send_type' conversation characteristics.
Destination: CCPI User response: Amend the application program to remove
this conflict.
DFHCP0729I date time applid tranid program name The Common Programming Interface Communications Reference
conversation_ID the supplied send_type provides a detailed description of all the CPI verbs and how
parameter CM_SEND_AND_CONFIRM is they should be called.
incompatible with the current setting of the Module: DFHCPCSL
sync_level characteristic CM_NONE.
Explanation: The application program has called CMSST XMEOUT Parameters: date, time,applid, tranid, program
(Set_Send_Type) with a send_type parameter of name,conversation_ID
CM_SEND_AND_CONFIRM and with the sync_level Destination: CCPI
characteristic set to CM_NONE.
conversation_ID the supplied sync_level
parameter sync_level is incompatible with the
The CPI verb has no effect on either the conversation or the current setting of the deallocate_type
conversation characteristics. characteristic deallocate_type.
User response: Amend the application program to remove Explanation: The application program has called CMSSL
this conflict. (Set_Sync_Level) with a sync_level parameter of sync_level.
The deallocate_type is deallocate_type.
The Common Programming Interface Communications Reference System action: CICS returns control to the application
provides a detailed description of all the CPI verbs and how program with return_code
they should be called. CM_PROGRAM_PARAMETER_CHECK.
Module: DFHCPCSK
XMEOUT Parameters: date, time,applid, tranid, program conversation characteristics.
name,conversation_ID User response: Amend the application program to remove
Destination: CCPI this conflict.

provides a detailed description of all the CPI verbs and how program with return_code CM_PROGRAM_STATE_CHECK.
Module: DFHCPCSL
XMEOUT Parameters: date, time,applid, tranid, program User response: Ensure that there is an incoming conversation
name,conversation_ID, sync_level, deallocate_type to accept.
Destination: CCPI
DFHCP0733I date time applid tranid program name they should be called.
conversation_ID the supplied sync_level Module: DFHCPCAC
parameter CM_NONE is incompatible with
XMEOUT Parameters: date, time,applid, tranid, program name
the current setting of the
Destination: CCPI
prepare_to_receive_type characteristic
CM_PREP_TO_RECEIVE_CONFIRM.
Explanation: The application program has called CMSSL DFHCP0741I date time applid tranid program name Duplicate
(Set_Sync_Level) with a sync_level parameter of CM_NONE. call to CMACCP (Accept_Conversation).
Explanation: The application program has called CMACCP
CM_PREP_TO_RECEIVE_CONFIRM is the
(Accept_conversation) more than once.
prepare_to_receive_type.
program with return_code CM_PROGRAM_STATE_CHECK.
CM_PROGRAM_PARAMETER_CHECK. The CPI verb has no effect on either the conversation or the
only calls CMACCP once.
User response: Amend the application program to remove
this conflict. The Common Programming Interface Communications Reference
Module: DFHCPCAC
Module: DFHCPCSL XMEOUT Parameters: date, time,applid, tranid, program name
Destination: CCPI
Destination: CCPI DFHCP0742I date time applid tranid program name Session is
not available for CPI-C as it is already in use
DFHCP0734I date time applid tranid program name by another process.
conversation_ID tp_name_length parameter Explanation: The application program has called CMACCP
(tp_name_length) supplied on the CMSTPN (Accept_conversation) when it was already using the session
(Set_TP_Name) verb is not in the range 1-64. for another process, for example, EXEC Interface DTP.
Explanation: The application program has called CMSTPN System action: CICS returns control to the application
(Set_TP_Name) with an tp_name_length parameter outside the program with return_code CM_PRODUCT_SPECIFIC_ERROR.
range 1–64. User response: Ensure that the application uses only CPI on
System action: CICS returns control to the application this session.
program with return_code Module: DFHCPCAC
CM_PROGRAM_PARAMETER_CHECK. XMEOUT Parameters: date, time,applid, tranid, program name
The CPI verb has no effect on either the conversation or the Destination: CCPI
User response: Amend CMSTPN in the application program DFHCP0743I date time applid tranid program name Unable to
to use a valid tp_name_length parameter. use CPI-C as this transaction was initiated by
The Common Programming Interface Communications Reference ATI.
provides a detailed description of all the CPI verbs and how Explanation: The application program has called CMACCP
they should be called. (Accept_conversation) after it was started by Automatic
Module: DFHCPCSM Transaction Initiation (ATI). This is not supported.
XMEOUT Parameters: date, time,applid, tranid, program program with return_code CM_PRODUCT_SPECIFIC_ERROR.
name,conversation_ID, tp_name_length
Destination: CCPI The CPI verb has no effect on either the conversation or the
User response: Ensure that applications abide by this
DFHCP0740I date time applid tranid program name No restriction.
incoming conversation to accept. Module: DFHCPCAC
Explanation: The application program has called CMACCP
(Accept_conversation) when there is no incoming XMEOUT Parameters: date, time,applid, tranid, program name
conversation. Destination: CCPI


conversation_ID CMCFM (Confirm) call
conflicts with sync_level CM_NONE. In addition, the CICS Resource Definition Guide gives further
Explanation: The application program has called CMCFM information on partner resource definitions.
(Confirm) when the sync_level is set to CM_NONE. This is Module: DFHCPCIC
not allowed.
System action: CICS returns control to the application XMEOUT Parameters: date, time,applid, tranid, program
program with return_code name,profile_name, sym_dest_name
CM_PROGRAM_PARAMETER_CHECK. Destination: CCPI

conversation characteristics. DFHCP0751I date time applid tranid program name
User response: Amend the application program so this conversation_ID invalid requested_length
conflict no longer occurs. parameter requested_length supplied on
CMRCV (Receive).
The Common Programming Interface Communications Reference Explanation: The application program has called CMRCV
provides a detailed description of all the CPI verbs and how (Receive) with a requested_length parameter that has a value
they should be called. greater than 32767.
Module: DFHCPCCM System action: CICS returns control to the application
XMEOUT Parameters: date, time,applid, tranid, program CM_PROGRAM_PARAMETER_CHECK.
Destination: CCPI The CPI verb has no effect on either the conversation or the
User response: Amend the application program to use a
DFHCP0749I date time applid tranid program name valid value for the requested_length parameter.
Unrecognized sym_dest_name
(sym_dest_name) supplied on the CMINIT
(Initialize_Conversation) verb.
Explanation: The application program has called CMINIT Module: DFHCPCRI, DFHCPCRW
(Initialize_Conversation). The sym_dest_name parameter is
unrecognized. XMEOUT Parameters: date, time,applid, tranid, program
System action: CICS returns control to the application name,conversation_ID, requested_length
program with return_code Destination: CCPI
The CPI verb has no effect on either the conversation or the DFHCP0752I date time applid tranid program name
conversation characteristics. conversation_ID data passed on call to
User response: Amend the application program and the CMSEND contains an invalid GDS record.
partner resource definition to ensure that the sym_dest_name Explanation: The application program has called CMSEND
parameter is correct. (Send_Data). Data passed on this call contains an invalid
generalized data stream (GDS) record.
The CICS Resource Definition Guide explains how to use the
partner resource correctly. Note: This message is only issued on a basic conversation.
That is, when conversation_type is set to
The Common Programming Interface Communications Reference CM_BASIC_CONVERSATION.
provides a detailed description of all the CPI verbs and how System action: The data is not sent.
CICS returns control to the application program with
Module: DFHCPCIC
return_code CM_PROGRAM_PARAMETER_CHECK.
XMEOUT Parameters: date, time,applid, tranid, program The CPI verb has no effect on either the conversation or the
name,sym_dest_name conversation characteristics.
Destination: CCPI User response: Amend the application program to ensure
that this parameter is correct.
DFHCP0750I date time applid tranid program name The Common Programming Interface Communications Reference
Unrecognized profile profile_name supplied in provides a detailed description of all the CPI verbs and how
partner resource sym_dest_name. they should be called together with information about GDS
Explanation: The application program has called CMINIT records.
(Initialize_Conversation). The profile found in the
The CICS Distributed Transaction Programming Guide provides
sym_dest_name supplied is unrecognized.
additional information about GDS records.
Module: DFHCPCLR
program with return_code CM_PRODUCT_SPECIFIC_ERROR.
conversation characteristics. Destination: CCPI
User response: Amend the application program and the
partner resource definition to ensure that the sym_dest_name
parameter is correct.

on a remote system was unrecognized. This is for one of two

reasons:
conversation_ID invalid send_length parameter
send_length supplied on CMSEND v A protocol error, or
(send_data). v The partner program is running on a later release and new
Explanation: The application program has called CMSEND sense codes have been added to the APPC architecture.
(Send_Data) with a send_length parameter that is not in the System action: CICS returns control to the application
range 0–32767 bytes. program with either return_code CM_DEALLOCATE_ABEND
System action: CICS returns control to the application or CM_PROGRAM_ERROR_PURGING. This depends on
program with return_code whether the unrecognized sense code has been interpreted as
CM_PROGRAM_PARAMETER_CHECK. an error or interpreted as a conversation abend.
User response: The send_length parameter should not exceed
32767 bytes. Amend CMSEND to send data that is within the Note: tp_name is present only if this message is being issued
range 0–32767 bytes. This may entail sending the data in two on the front-end system.
chunks. User response: Use the sense code provided in the message
The SAA CPI Reference manual provides a detailed description and your knowledge of the two communicating systems to
of all the CPI verbs and how they should be called. determine which of the two possible cases documented above
Module: DFHCPCN1, DFHCPCN2, DFHCPCN3, is the error.
DFHCPCN4, DFHCPCN5
If the error is a protocol error, you need further assistance
XMEOUT Parameters: date, time,applid, tranid, program from IBM to resolve this problem. See Part 4 of the CICS
name,conversation_ID, send_length Problem Determination Guide for guidance on how to proceed.
Destination: CCPI Module: DFHCPCLR
DFHCP0754I date time applid tranid program name name,conversation_ID, X'sense_code', {2=program, 1=program - },
conversation_ID data sent so far is currently in tp_name
the middle of a GDS record so cannot send Destination: CCPI
CMDEAL, CMCFM or CMPTR requests.
Explanation: The application is using a basic conversation
(that is, the conversation_type characteristic has been set to DFHCP0757I date time applid tranid program name
CM_BASIC_CONVERSATION). conversation_ID unrecognized netname netname
supplied for CMALLC (Allocate) verb.
The application has not sent all the data associated with the Explanation: The allocation of a session for this conversation
last Generalized Data Stream (GDS) record. failed due to an unrecognized netname netname.
However, the application has tried to send one of the This value is derived from the partner_lu_name specified
following requests:
either in the partner resource for the conversation, or on a CPI
v a CMDEAL (Deallocate),
CMSPLN (set_partner_lu_name) verb.
v a CMCFM (Confirm), or
v a CMPTR (Prepare_to_receive).
program with return_code CM_PARAMETER_ERROR.
program with return_code CM_PROGRAM_STATE_CHECK. No session is allocated.
recognized netname.
Module: DFHCPCLR
User response: Inspect the data sent to determine why the
previous send was in error. Check if the error was caused by XMEOUT Parameters: date, time,applid, tranid, program
the application truncating the last record or if there was an name,conversation_ID, netname
error in one of the length fields which caused CPI to Destination: CCPI
misinterpret the data-stream and amend the application
program accordingly.
The SAA CPI Reference manual provides a detailed description conversation_ID unrecognized mode_name
of all the CPI verbs and how they should be called together mode_name supplied for CMALLC (Allocate)
with information about GDS records. verb.
Explanation: The allocation of a session for this conversation
TheCICS Distributed Transaction Programming Guide provides
failed due to an unrecognized mode name mode_name.
additional information about GDS records.
Module: DFHCPCLR This value is specified either in the profile named in the
partner resource for the conversation, or on a CPI CMSMN
(Set_mode_name) verb.
Destination: CCPI
No session is allocated.
DFHCP0756 date time applid tranid program name
conversation_ID received an unrecognized
recognized mode_name.
sense_code X'sense_code' from the partner
Module: DFHCPCLR
{program | program - }tp_name.
Explanation: A sense code received from the partner program XMEOUT Parameters: date, time,applid, tranid, program
name,conversation_ID, mode_name

Destination: CCPI CICS returns control to the application program with

return_code CM_PARAMETER_ERROR.
DFHCP0759I date time applid tranid program name uses a different mode_name.
conversation_ID invalid use of the SNA service Module: DFHCPCAL
TP X'tp_name'
Explanation: The allocation of a session for conversation XMEOUT Parameters: date, time,applid, tranid, program
conversation_id failed because the transaction program (TP) name,conversation_ID, mode_name
specified in the conversation control block (CPC) is an SNA Destination: CCPI
service TP. This is not allowed.
conversation_ID the mode_name mode_name
specified for the CMALLC (Allocate) verb is
uses a different TP.
unknown to VTAM.
Module: DFHCPCAL
Explanation: The allocation of a session for conversation
XMEOUT Parameters: date, time,applid, tranid, program conversation_ID has failed. This is because the mode_name
name,conversation_ID, X'tp_name' specified in the conversation control block (CPC) is known to
Destination: CCPI the remote system, but is unknown to VTAM.
System action: No session is allocated.
DFHCP0760I date time applid tranid program name CICS returns control to the application program with return
conversation_ID an invalid partner_lu_name code CM_PARAMETER_ERROR.
partner_lu_name was specified for the User response: Amend the application program so that it
CMALLC (Allocate) verb. uses a different mode_name.
Explanation: The allocation of a session has failed. This is Module: DFHCPCLR
because the partner_lu_name specified in the conversation
control block (CPC) does not conform to the following rules.
name,conversation_ID, mode_name
1. The partner_lu_name may take one of the following forms:
Destination: CCPI
v Netname (1-8 characters long), or
v Network.netname (where network and netname are
EACH 1-8 characters long). DFHCP0764I date time applid tranid program name Partner
2. Netname and network both consist of the following Resource Manager is unavailable.
character sets, where the first character is always Explanation: The application program has called CMINIT
alphabetic. (Initialize_Conversation), but the partner resource manager
v A-Z (which provides access to the partner resource table) is not
v a-z available.
v @ System action: CICS returns control to the application
v $ program with return_code CM_PRODUCT_SPECIFIC_ERROR.
v # User response: First determine whether message DFHPR0106
v 0-9 was issued during CICS initialization; if so, refer to the advice
Note: Lower case letters are translated to uppercase. given for that message. Otherwise it appears that CICS-owned
System action: The session is not allocated. storage (either the static storage address list, or the PR static
storage) has been overlaid. Refer to the CICS Problem
CICS returns control to the application program with Determination Guide for guidance on how to deal with storage
return_code CM_PARAMETER_ERROR. violations.
User response: Depending on the application, the Module: DFHCPCIC
partner_lu_name either comes from the partner resource
(specified on the CMINIT (initialize_conversation) verb in the XMEOUT Parameters: date, time,applid, tranid, program name
sym_dest_name parameter) or an optional CMSPLN Destination: CCPI
(set_partner_lu_name) verb. This value needs to be changed to
conform to the rules above.
Module: DFHCPCAL
conversation_ID CPI-C verb verb was
XMEOUT Parameters: date, time,applid, tranid, program disallowed because of the
name,conversation_ID, partner_lu_name BACKOUT-REQUIRED program state.
Destination: CCPI Explanation: The CPI state machine has detected a state
error. The verb verb cannot be issued in BACKOUT-
REQUIRED program state.
DFHCP0761I date time applid tranid program name System action: CICS returns control to the application
conversation_ID an invalid mode_name program with return code CM_PROGRAM_STATE_CHECK.
mode_name was specified for the CMALLC User response: Amend the application program in
(Allocate) verb. accordance with the supplied guidelines. See the SAA CPI
Explanation: The allocation of a session for conversation Reference which contains a description of CPI verbs and how
conversation_id has failed. This is because the mode_name they should be called.
mode_name specified in the conversation control block (CPC) is Module: DFHCPIC
not allowed.
System action: No session is allocated. XMEOUT Parameters: date, time,applid, tranid, program
name,conversation_ID, verb

Destination: CCPI
DFHCRxxxx messages
termid. The request could not be honored because terminal
DFHCR4300 date time applid Transaction tranid not executed
termid is not defined on this system.
on terminal termid on system sysid.
Transaction invalid on that system
User response: Ensure that terminal termid and transaction
Explanation: A request was made to schedule a task on
tranid are defined on both systems.
remote system sysid. The request could not be executed
Module: DFHCRS
because transaction tranid is not defined on system sysid.
System action: Other processing continues. XMEOUT Parameters: date, time,applid, sysid, tranid, termid
User response: Ensure that terminal termid and transaction Destination: CSMT
tranid are defined on system sysid.
Module: DFHCRS
DFHCR4312 date time applid Request from system sysid to
XMEOUT Parameters: date, time,applid, tranid, termid, sysid initiate transaction tranid on that system on
Destination: CSMT terminal termid was not executed. Schedule
request failed
Explanation: A request was received from remote system
sysid to initiate transaction tranid on system sysid on terminal
on terminal termid on system sysid. Terminal
termid. The request could not be honored because the schedule
invalid on that system
request failed.
remote system sysid. The request could not be executed
User response: Check the system definition tables of the local
because terminal termid is not defined on system sysid.
system to determine why schedule requests might not be
honored.
Module: DFHCRS
tranid are defined on system sysid.
Module: DFHCRS XMEOUT Parameters: date, time,applid, sysid, tranid, termid
Destination: CSMT
XMEOUT Parameters: date, time,applid, tranid, termid, sysid
Destination: CSMT
DFHCR4314 date time applid Request to initiate transaction
tranid on remotely owned terminal termid has
been purged. Request was not deliverable to
on terminal termid on system sysid. Schedule
system sysid within the ATI purge delay time
request failed on that system
interval.
Explanation: A request to initiate transaction tranid was not
remote system sysid. The request could not be executed.
delivered to system sysid, probably because a link to system
sysid had not been made available.
User response: Check the system definition tables of the
remote system to determine why schedule requests might not
User response: Ensure that a link to system sysid is made
be honored.
available between issuing the transaction initiation request and
Module: DFHCRS
the elapse of the ATI purge delay time interval.
XMEOUT Parameters: date, time,applid, tranid, termid, sysid Module: DFHCRQ
Destination: CSMT
XMEOUT Parameters: date, time,applid, tranid, termid, sysid
Destination: CSMT
initiate transaction tranid on that system on
DFHCR4315 date time applid Request to initiate transaction
terminal termid was not executed. Transaction
tranid on remotely owned terminal termid has
invalid on this system.
been purged. System sysid has not responded
within the ATI purge delay time interval.
Explanation: A request to initiate transaction tranid was sent
termid. The request could not be honored because transaction
to system sysid. System sysid acknowledged the request but
tranid is not defined in this system.
did not respond within the ATI purge delay time interval
because:
v The task started and abnormally terminated, or
tranid are defined on both systems.
v The task failed a security check, or
Module: DFHCRS
v System sysid abnormally terminated and all details of the
XMEOUT Parameters: date, time,applid, sysid, tranid, termid request were lost.
Destination: CSMT System action: If system sysid eventually responds, the task
is not executed.
User response: Determine why system sysid did not respond.
Module: DFHCRQ
initiate transaction tranid on that system on
terminal termid was not executed. Terminal XMEOUT Parameters: date, time,applid, tranid, termid, sysid
invalid on this system. Destination: CSMT

DFHDD0001 • DFHDF0004
DFHDDxxxx messages
If you cannot resolve the problem, you will need further
DFHDD0001 applid An abend (code aaa/bbbb) has occurred
assistance from IBM. See Part 4 of the CICS Problem
Explanation: An unexpected program check or abend
Module: DFHDDDM, DFHDDDI, DFHDDLO, DFHDDBR
occurred with abend code aaa/bbbb.
The program status word (PSW) at the time of the program
check or abend indicated that CICS was executing at offset
X'offset' in module modname. This may have been caused by
corruption of CICS code or control blocks. DFHDD0002 applid A severe error (code X'code') has
The code aaa/bbbb is a three digit hexadecimal VSE code (if occurred in module modname.
applicable), followed by a four digit alphanumeric CICS code. Explanation: The directory domain has received an
The VSE code is a system completion code, for example 0C1. unexpected error response from some other part of CICS. The
If a VSE code is not applicable, this field is filled with three operation requested by the directory domain is described by
hyphens. The CICS code is an abend code or a number code X'code'.
referring to a CICS message (for example, AKEA is a CICS For further information about CICS exception trace entries,
abend code; 1310 refers to message DFHTS1310). refer to the CICS Problem Determination Guide.
During initialization, CICS may not have access to the user's System action: A system dump is taken and the system
applid coded in the SIT. If CICS produces this message in these attempts to continue operation unless specifically inhibited by
circumstances, it uses the default applid value DBDCCICS. dump table entries.
System action: A system dump is taken and the system Message DFHME0116 is normally produced containing the
attempts to continue operation unless otherwise directed by symptom string for this problem.
entries in the dump table. User response: Investigate the cause of the problem as
Message DFHME0116 is normally produced containing the follows:
symptom string for this problem. v Determine if the problem can be explained by any previous
User response: Notify the system programmer. messages output from some other part of CICS.
v Examine the symptom string.
Look up the VSE code, if there is one, in "OS/390 API Abend v Examine the dump.
Codes" in section "VSE/Advanced Functions Codes & SVC
Errors" of z/VSE Messages and Codes - Volume 1. If you cannot resolve the problem, you will need further
assistance from IBM. See Part 4 of the CICS Problem
Then look up the CICS alphanumeric code in “Transaction Determination Guide for guidance on how to proceed.
Abend Codes (CICS Transaction Server for VSE/ESA)” on Module: DFHDDDM, DFHDDDI, DFHDDLO, DFHDDBR
page 453. This will tell you, for example, whether the error
was a program check, an abend, a runaway or a recovery XMEOUT Parameters: applid, X'code',modname
percolation, and may give you some guidance concerning user Destination: Console
response.
DFHDFxxxx messages
DFHDF0001 Data management facility is started. DFHDF0003 Data management facility has been unable to
Explanation: The data management facility (DMF) has establish the PC environment. Return code is
successfully initialized. X'rc' from macro macro.
System action: DMF continues. Explanation: When the data management facility (DMF)
User response: None. attempted to create the PC environment, the macro macro
Module: DFHDFSIP. failed with return code rc.
Destination: Console System action: DMF will terminate with a return code of 12.
User response: DMF establishes the PC environment by
issuing the macro SUBSID IDENTIFY, which has failed for the
DFHDF0002 Data management facility is in the incorrect reason rc. You need further assistance from IBM to resolve this
state. Enter 'CANCEL' to terminate, or 'GO' to problem. See Part 4 of the CICS Problem Determination Guide
continue. for guidance on how to proceed.
Explanation: The data management facility (DMF) has Module: DFHDFSIP.
detected that another instance of DMF may be active in the Destination: Console
system. This is not allowed.
System action: DMF will wait for operator to reply. If
'CANCEL' is entered, DMF will terminate with a return code DFHDF0004 Data management facility has been unable to
of 12. If 'GO' is entered, initialization of DMF continues. create DMF control blocks. Return code is
User response: Check to see if another instance of DMF is X'rc' from macro macro.
active in the system. If there is one you must enter 'CANCEL'. Explanation: When the data management facility (DMF)
If there are no instances of DMF active you may enter 'GO' or attempted to create the control blocks needed for successful
'CANCEL'. initialization, the macro macro failed with return code rc. macro
Module: DFHDFSIP. may be either:
Destination: Console v DSPSERV, or
v ALESERV

DFHDF0005 • DFHDF0010
Note: If macro is DSPSERV, then the format of rc is xxyyyyyy

DFHDF0007 This startup is using suffix suffix.
where xx is the register 15 value and yyyyyy is the reason code
Explanation: The data management facility (DMF) has used
as passed back in register 0.
the start up table with the suffix suffix.
System action: DMF will terminate with a return code of 12.
System action: DMF initialization continues.
User response: Determine the reason why the macro macro
User response: None
failed, and take steps to correct the error. See the z/VSE System
Module: DFHDFSIP.
Macros Reference for further guidance.
Module: DFHDFSIP.
DFHDF0008 Data management facility has been unable to
load program program.
DFHDF0005 Invalid suffix specified for initialization table
Explanation: The data management facility (DMF) has been
- suffix. Please enter a two character suffix,
unable to load the program program because:
enter 'CANCEL' to terminate DMF, or enter
v the program does not exist
'ACCEPT' to continue with the default
v the program does exist but not in a library in the LIBDEF
values.
chain
Explanation: The suffix entered for this start up - suffix - is
v there is not enough GETVIS storage available in the partition
invalid, because either it:
to load the program
1. is too long (more than two characters), or
System action: DMF will terminate with a return code of 12
2. contained illegal characters
User response: Take one of the following actions:
System action: DMF will wait for the operator to reply. If the
1. Ensure the LIBDEF chain includes the library that contains
reply is 'CANCEL', DMF will terminate with a return code of
the program.
12. If the reply is 'ACCEPT', DMF will continue with
2. Increase the partition size.
initialization using default values. For any other reply, DMF
3. Specify a SIZE parameter on the EXEC card for DFHDFSIP. A
will attempt to continue initializing using a start up table with
suitable expression would be SIZE=DFHDFSIP.
the supplied suffix.
4. You need further assistance from IBM to resolve this
problem. See Part 4 of the CICS Problem Determination
1. Reenter the suffix but make sure it is no longer than two
Guide for guidance on how to proceed.
characters.
Module: DFHDFSIP.
2. Reenter the suffix using valid characters. Valid characters
are '@', the range 'A' through 'Z' and '0' through '9'.
3. Accept the default start up values by entering 'ACCEPT'.
4. Terminate this run of DMF by entering 'CANCEL'. DFHDF0009 Data management facility has been unable to
Module: DFHDFSIP. create the DMF anchor block.
Destination: Console Explanation: The data management facility (DMF) was
unable to obtain sufficient 31-bit system GETVIS storage to
hold the DMF Anchor Block.
DFHDF0006 Unable to find initialization table with suffix
suffix. Please enter a two character suffix,
User response: Increase the size of the 31-bit system GETVIS
enter 'CANCEL' to terminate DMF, or enter
area.
'ACCEPT' to continue with the default
Module: DFHDFSIP.
values.
Explanation: The data management facility (DMF) has been
unable to load the initialization table with the suffix suffix
because either it: DFHDF0010 Invalid over-ride parameter has been
1. does not exist, or specified. Please enter a two character suffix,
2. does exist but not in a library in the LIBDEF chain enter 'CANCEL' to terminate DMF, or enter
System action: DMF will wait for the operator to reply. If the 'ACCEPT' to continue with default values.
reply is 'CANCEL', DMF will terminate with a return code of Explanation: The over-ride parameter entered for this start
12. If the reply is 'ACCEPT', DMF will continue with up in the SYSIPT data stream is invalid. The valid format for
initialization using default values. For any other reply, DMF an over-ride is 'SUFFIX=xx'.
will continue initializing using a start up table with the System action: DMF will wait for the operator to reply. If the
supplied suffix. reply is 'CANCEL', DMF will terminate with a return code of
User response: Take one of the following actions: 12. If the reply is 'ACCEPT', DMF will continue with
1. Create a table with the appropriate suffix. initialization using default values. For any other reply, DMF
2. Ensure the LIBDEF chain includes the library that contains will continue initializing using a start up table of the supplied
the initialization table. suffix.
3. Enter another suffix. Characters in the suffix should be User response: Take one of the following actions:
either '@', or in the ranges 'A' through 'Z' and '0' through 1. Enter a new suffix using valid characters. Characters
'9'. should be either '@', in the range 'A' through 'Z', or in the
4. Accept the default start up values by entering 'ACCEPT'. range '0' through '9'.
5. Terminate this run of DMF by entering 'CANCEL'. 2. Accept the default values by entering 'ACCEPT'.
Module: DFHDFSIP. 3. Terminate this run of DMF by entering 'CANCEL'.
Destination: Console 4. Correct the SYSIPT data stream.
Module: DFHDFSIP.

DFGF_GET_FAILURE
DFHDF0011 Data management facility was unable to
indicates that a request to get storage failed.
initialize its lock manager. Reason is
DFLM_GET_FAILURE
{INVALID_FORMAT | INVALID_FUNCTION |
indicates that an internal call to the lock manager
INVALID_ANCHOR | DFGF_GET_FAILURE |
could not be handled because the lock manager was
GETVIS_EXHAUSTED | PFIX_FAILED}.
unable to get storage for a lock.
Explanation: The data management facility (DMF) tried to
DFLM_DEFINE_FAILURE
initialize the lock manager DFHDFLM. However, one of the
following occurred:
returned an unexpected response.
INVALID_FORMAT
GETVIS_EXHAUSTED
indicates that the parameter list passed to the lock
indicates that a request for storage failed because
manager was not a valid parameter list for the lock
there was no more partition GETVIS storage
manager.
available.
INVALID_FUNCTION
PFIX_FAILED
indicates that the parameter list passed to the lock
indicates that the partition GETVIS storage requested
manager contained an invalid request.
could not be PFIXed by z/VSE.
INVALID_ANCHOR
DUPLICATE_RESOURCE
indicates that the DMF Anchor Block could not be
verified.
could not be handled because an attempt was made
DFGF_GET_FAILURE
to define an already defined resource.
indicates that a request to get storage failed.
TRACE_INITIALIZED
GETVIS_EXHAUSTED
indicates that the trace facility has already been
initialized.
System action: DMF will terminate with a return code of 12.
available.
PFIX_FAILED
System action: DMF will terminate with return code 12.
Module: DFHDFSIP
Guide for guidance on how to proceed. DFHDF0013 Data management facility was unable to
Module: DFHDFSIP. initialize its report facility. Reason is
Destination: Console {INVALID_FORMAT | INVALID_FUNCTION |
INVALID_ANCHOR | DFGF_GET_FAILURE |
DFLM_DEFINE_FAILURE |
GETVIS_EXHAUSTED | PFIX_FAILED}.
initialize its trace facility. Reason is
Explanation: The Data Management Facility (DMF) tried to
initialize the report facility DFHDFTR. However, one of the
INVALID_ANCHOR |
following occurred:
INVALID_DFLM_ANCHOR |
INVALID_FORMAT
DFGF_GET_FAILURE | DFLM_GET_FAILURE
indicates that the parameter list passed to the report
| DFLM_DEFINE_FAILURE |
manager was not a valid parameter list for the
GETVIS_EXHAUSTED | PFIX_FAILED |
report manager.
DUPLICATE_RESOURCE |
INVALID_FUNCTION
TRACE_INITIALIZED}.
indicates that the parameter list passed to the report
Explanation: The Data Management Facility (DMF) tried to
initialize the trace facility DFHDFTR. However, one of the
INVALID_ANCHOR
following occurred:
indicates that the DMF anchor block could not be
INVALID_FORMAT
verified.
indicates that the parameter list passed to the trace
DFGF_GET_FAILURE
manager was not a valid parameter list for the trace
indicates that an internal call to the storage manager
manager.
INVALID_FUNCTION
DFLM_DEFINE_FAILURE
INVALID_ANCHOR
GETVIS_EXHAUSTED
indicates that the DMF anchor block could not be
verified.
INVALID_DFLM_ANCHOR
available.
PFIX_FAILED
could not be handled because the lock manager
anchor block could not be verified.

System action: DMF will terminate with a return code of 12. Macros Reference for further guidance.
User response: Take one of the following actions: Module: DFHDFSIP.
1. Increase the partition size. Destination: Console
3. You need further assistance from IBM to resolve this DFHDF0016 Data management facility has loaded
problem. See Part 4 of the CICS Problem Determination program phase, which has entry point
Guide for guidance on how to proceed. X'entry_address'.
Module: DFHDFSIP Explanation: Data management facility (DMF) has loaded the
Destination: Console program called phase, and this program has an entry point as
shown in entry_address. If the high order bit of the address is
on, the program has been link edited with the Addressing
DFHDF0014 Data management facility was unable to mode (AMODE) set to 31.
open the console report. Reason is System action: DMF continues.
{INVALID_FORMAT | INVALID_FUNCTION | User response: None - this is an informational message only.
INVALID_TOKEN | REPORT_TITLE_INVALID Module: DFHDFSIP, DFHDFOCX.
| REPORT_HEADING_INVALID | Destination: Console
DFLM_RESERVE_FAILURE
|DFLM_RELEASE_FAILURE | REPORT_OPEN
| IODEV_OPEN}. DFHDF0017 Data management facility has been unable to
Explanation: The Data Management Facility (DMF) tried to create the cell pool storage.
open the console report. However, one of the following Explanation: The data management facility (DMF) was
occurred: unable to obtain sufficient 31-bit storage from the partition
INVALID_FORMAT GETVIS area to hold the callable cell pool storage. DMF will
indicates that the parameter list passed to the report accept an allocation of GETVIS storage from 24-bit storage.
manager was not a valid parameter list for the System action: DMF will terminate with a return code of 12
report manager. User response: You will need to increase the size of the
INVALID_FUNCTION partition GETVIS that DMF can acquire. You can do this by
indicates that the parameter list passed to the report either:
manager contained an invalid request. 1. Reducing the SIZE parameter that controls how much
INVALID_TOKEN program storage is allocated in the partition, or
indicates that the parameter list passed to the report 2. Increasing the size of the partition that DMF is being
manager contained a token that was invalid. started in.
REPORT_TITLE_INVALID Module: DFHDFSIP.
indicates that the parameter list passed to the report Destination: Console
manager contained a title for the console report that
was invalid. DFHDF0018 Data management facility has been unable to
REPORT_HEADING_INVALID acquire storage for DFHDFCR to use.
indicates that the parameter list passed to the report Explanation: The data management facility (DMF) was
manager contained a heading for the console report unable to obtain sufficient 24-bit GETVIS storage to hold the
that was invalid. SYSIPT parameter read by DFHDFCR.
DFLM_RESERVE_FAILURE System action: DMF will terminate with a return code of 12
indicates that an internal call to the lock manager User response: Increase the size of the 24-bit GETVIS area, by
returned an unexpected response. increasing the partition size, or reducing the SIZE parameter
DFLM_RELEASE_FAILURE on the EXEC DFHDFSIP statement.
indicates that an internal call to the lock manager Module: DFHDFSIP.
returned an unexpected response. Destination: Console
REPORT_OPEN
indicates that the request failed because the console
report was already open. DFHDF0019 Data management facility has been unable to
IODEV_OPEN acquire storage for the statistics block.
indicates that the request failed because the console Explanation: The data management facility (DMF) was
device was already open. unable to obtain sufficient 31-bit GETVIS storage to hold the
System action: DMF will terminate with a return code of 12. DMF Statistics Block.
User response: You need further assistance from IBM to System action: DMF will terminate with a return code of 12
resolve this problem. See Part 4 of the CICS Problem User response: Increase the size of the 31-bit GETVIS area.
Determination Guide for guidance on how to proceed. Module: DFHDFSIP.
Module: DFHDFSIP Destination: Console

DFHDF0015 Data management facility issued CALL load phase DFHDFFM.
function which failed. Response is X'rc'. Explanation: The data management facility (DMF) was
Explanation: When the data management facility (DMF) unable to load the File Manager subtask program DFHDFFM.
issued a CALL function, it failed with return code rc. System action: DMF will terminate with a return code of 12
System action: DMF will terminate with a return code of 12. User response: You need further assistance from IBM to
User response: Determine the reason why the CALL function resolve this problem. See Part 4 of the CICS Problem
failed, and take steps to correct the error. See the z/VSE System Determination Guide for guidance on how to proceed.

Module: DFHDFSIP.
DFHDF0026 Data management facility cannot continue -
OS390 not specified on EXEC statement
Explanation: The data management facility (DMF) requires
DFHDF0021 Data management facility has been unable to OS390 emulation to work correctly.
acquire storage for the File Manager sub task System action: DMF will terminate with a return code of 12
save area. User response: Specify OS390 on the EXEC DFHDFSIP
Explanation: The data management facility (DMF) was statement.
unable to obtain sufficient 24-bit GETVIS storage to be used as Module: DFHDFSIP.
the File Manager sub task save area. Destination: Console
User response: Increase the size of the 24-bit GETVIS area,
DFHDF0027 Data Management Facility has called the
either by increasing the partition size, or by specifying a
trace facility with the function call
reduced SIZE parameter on the EXEC DFHDFSIP statement.
{START_TRACE | PAUSE_TRACE
Module: DFHDFSIP.
|RESUME_TRACE} but this failed for reason
INVALID_ANCHOR |
DFHDF0022 Data management facility has been unable to INVALID_DFLM_TOKEN |
acquire storage for the File Manager Request DFGF_GET_FAILURE |
Block. Shutdown will be forced to DFLM_RESERVE_FAILURE |
Immediate. DFLM_RELEASE_FAILURE |
Explanation: The data management facility (DMF) was GETVIS_EXHAUSTED | PFIX_FAILED |
unable to obtain sufficient 31-bit or 24-bit GETVIS storage to RESOURCE_BUSY | TRACE_ACTIVE
be used as a File Manager Request Block. Consequently DMF |TRACE_INACTIVE | TRACE_PAUSED}.
will not be able to complete a normal shutdown. Explanation: Data management facility (DMF) has called the
System action: DMF will initiate an Immediate Shutdown. trace facility to set the trace status to that defined in the start
User response: Increase the size of the 31-bit GETVIS area. up table. The call was one of:
Module: DFHDFSIP. START_TRACE
Destination: Console Start the trace facility
PAUSE_TRACE
Temporarily suspend the trace facility
DFHDF0023 Data management facility has been unable to RESUME_TRACE
acquire storage for the abend handlers save Resume the trace facility
areas.
Explanation: The data management facility (DMF) was However, one of the following occurred:
unable to obtain sufficient 31-bit GETVIS storage to hold the INVALID_FORMAT
save areas required for its abend handlers. indicates that the parameter list passed to the trace
System action: DMF will terminate with a return code of 12 facility was not a valid parameter list.
User response: Increase the size of the 31-bit GETVIS area. INVALID_FUNCTION
Module: DFHDFSIP. indicates that the parameter list passed to the trace
Destination: Console facility contained an invalid request.
INVALID_ANCHOR
DFHDF0024 Data management facility has calculated indicates that the DMF Anchor Block could not be
there is insufficient data space available. validated.
Explanation: The data management facility (DMF) has INVALID_DFLM_TOKEN
calculated that there is not sufficient data space available to indicates that the lock manager could not validate
create its data space. DMF requires at least 4 MB of data space the lock token representing the trace facility lock.
to be available. DFGF_GET_FAILURE
System action: DMF will terminate with a return code of 12 indicates that a request to get storage failed.
User response: Increase the amount of data space available DFLM_RESERVE_FAILURE
by using the SYSDEF DSPACE command. See the z/VSE System indicates that an internal call to the lock manager
Control Statements for further information. returned an unexpected response.
Module: DFHDFSIP. DFLM_RELEASE_FAILURE
Destination: Console indicates that an internal call to the lock manager
GETVIS_EXHAUSTED
DFHDF0025 Data management facility has created indicates that a request for storage failed because
dataspace named dspacename, which is there was no more partition GETVIS storage
dspacesizeM bytes in size. available.
Explanation: Data management facility (DMF) has created a PFIX_FAILED
dataspace called dspacename, and the size of the dataspace is indicates that the partition GETVIS storage request
dspacesizeM bytes in size. could not be PFIXed by z/VSE.
System action: DMF continues. RESOURCE_BUSY
User response: None - this is an informational message only. indicates that the internal request to lock the trace
Module: DFHDFSIP. facility returned with a response that showed the
Destination: Console resource was already locked.

TRACE_ACTIVE for the DMF job the dump is suppressed, otherwise

indicates that the trace facility determined that the the dump is redirected to SYSLST.
trace was already active. SDUMPX RETURN CODE X'nn' REASON X'mm'
TRACE_INACTIVE SYSDUMP LIBRARY IS FULL
indicates that the trace facility determined that the The SYSDUMP library defined for the DMF job is
trace was already inactive. full. If the SYSDUMPC job control option is in effect
TRACE_PAUSED for the DMF job the dump is suppressed, otherwise
indicates that the trace facility determined that the the dump is redirected to SYSLST.
trace was already paused. SDUMPX RETURN CODE X'nn' REASON X'mm'
System action: DMF continues. VSE rejected the SDUMPX request for some other
User response: You need further assistance from IBM to reason than those listed above. X'nn' gives the
resolve this problem. See Part 4 of the CICS Problem hexadecimal SDUMPX return code and X'mm' gives
Determination Guide for guidance on how to proceed. the hexadecimal SDUMPX reason code.
Module: DFHDFSIP System action: DMF proceeds as if the dump had been
Destination: Console successful.
User response: The user response depends on the reason for
the failure. For:
DFHDF0028 Data management facility trace status is set to SDUMPX RETURN CODE X'nn' ONLY PARTIAL DUMP
status. Use VSE problem determination methods to
Explanation: Data management facility (DMF) has determine why a partial dump was taken. See the
determined that the start up table has defined that trace z/VSE System Macros Reference manual for a
should be set to status and this has been actioned. description of this return code.
System action: DMF continues. SDUMPX RETURN CODE X'nn' REASON X'mm' NO
User response: None. SYSDUMP LIBRARY AVAILABLE
Module: DFHDFSIP Define a SYSDUMP library for the DMF job and
Destination: Console then cause the SDUMPX request to be reissued. See
the z/VSE Diagnosis Tools manual for a description of
how to define a SYSDUMP library.
DFHDF0029 Data management facility is about to take a
SDUMPX RETURN CODE X'nn' REASON X'mm'
SDUMPX. (Module modname).
SYSDUMP LIBRARY IS FULL
Explanation: Data Management Facility (DMF) is about to
Clear some dumps from the dump library and cause
issue an SDUMPX request in response to an immediate
the SDUMPX request to be reissued. See the z/VSE
shutdown request. modname indicates the module that has
Diagnosis Tools manual for a description of how to
issued the message.
delete or offload a dump from the SYSDUMP
System action: DMF takes a system dump.
library.
User response: Inform the system programmer. See the
associated dump and error messages for further guidance.
No action is required if the dump was suppressed
Module: DFHDFABX, DFHDFPCX, DFHDFSIP
deliberately. If the dump failed because of an error
in the VSE SDUMPX routine, use VSE problem
determination methods to fix the error and then
DFHDF0030 Data management facility SDUMPX cause the SDUMP request to be reissued.
complete. (Module modname). Module: DFHDFABX, DFHDFPCX, DFHDFSIP, DFHDFTR
Explanation: Data Management Facility (DMF) has received a Destination: Console
good response from the SDUMPX request. modname identifies
the module issuing the message.
DFHDF0032 Data management facility will not issue any
System action: DMF will terminate, unless the dump was
SDUMPX macros in this run.
requested from the DMF global trap program DFHDFTRP.
Explanation: Data Management Facility (DMF) will not issue
User response: Print off the system dump if required. A
any SDUMPX macros during this run. This is because either
previous VSE message identifies the SYSDUMP library name
STDOPT SYSDUMP=NO or // OPTION NOSYSDUMP is in effect.
and which member of the SYSDUMP library contains the
dump. DMF issues SDUMPX macros in cases of failure, in response to a
Module: DFHDFABX, DFHDFPCX, DFHDFSIP, DFHDFTR SETDMF SHUTDOWN,IMMEDIATE request, or in response to a
Destination: Console request from the global trap program. These SDUMPX dumps
may then be used to assist with problem determination.
System action: DMF continues.
DFHDF0031 DMF SDUMPX request failed. (Module
User response: If it is acceptable to run DMF without the
modname) - reason.
capability of taking SDUMPX dumps, then you may ignore this
Explanation: A VSE SDUMPX request from CICS signalled
message. However, if you want DMF to take SDUMPX dumps,
by message DFHDF0029 has failed to complete successfully.
you should shutdown DMF, and add // OPTION SYSDUMP to
The possible reasons reason for the failure are detailed below.
the JCL that starts DMF, or change the standard option using
SDUMPX RETURN CODE X'nn' ONLY PARTIAL DUMP
STDOPT SYSDUMP=YES, before restarting DMF.
The number of storage areas to be dumped exceeds
the maximum allowed for one SDUMPX request. See the z/VSE System Control Statements for further information
SDUMPX RETURN CODE X'nn' REASON X'mm' NO on the OPTION and STDOPT statements.
SYSDUMP LIBRARY
No SYSDUMP library is defined for the DMF job. If See the z/VSE System Macros Reference for further information
the VSE SYSDUMPC job control option is in effect on the SDUMPX macro.
Module: DFHDFSIP

DFHDF1002 Data management facility supports two
operator commands: 'SETDMF' changes the
DFHDF0033 Data management facility has suppressed an state of the DMF system, 'DISPLAY' reflects
SDUMPX macro. Module (modname). the current state of the DMF system. To end
Explanation: Data Management Facility (DMF) was about to communication with DMF at any time, enter
issue an SDUMPX macro, but has suppressed the taking of the EOB (End of Block). At the prompt you may
system dump. This is either because one has just been taken enter a DMF command, or request further
(as requested by the global trap program), or because DMF assistance by entering a '?' followed by one
earlier detected that the SYSDUMP option is not in effect. of the commands (for example ?SETDMF).
modname identifies the module issuing the message. Explanation: The operator has requested that online help be
System action: DMF suppresses the taking of a system displayed.
dump. System action: DMF will wait for the operator to reply to
User response: None. DFHDF0000, and then perform one of the following actions:
Module: DFHDFABX, DFHDFPCX, DFHDFSIP, DFHDFTR v If the reply is EOB (Enter pressed) then communication
Destination: Console with DMF will be terminated.
v If the reply is '?' then message DFHDF1002 will be
displayed.
DFHDF0034 Data Management Facility has been passed v If the reply is '?SETDMF' then message DFHDF1003 will be
an invalid parm statement displayed.
Explanation: Data Management Facility (DMF) was started v If the reply is '?DISPLAY' then message DFHDF1004 will be
with a PARM parameter specified on the EXEC DFHDFSIP displayed.
statement. However, the data passed was of an incorrect v Otherwise the action requested will be taken.
format. User response: Take one of the following actions:
System action: DMF will terminate with a return code of 12. 1. Enter a null response by pressing enter to end
User response: You should correct the parm value in the communication with DMF.
DMF start-up JCL and resubmit the job. Refer to the CICS 2. Enter a '?' for on line help information.
Operations and Utilities Guide for details on coding the parm 3. Enter a '?' followed by a command for help information
values for DMF. relating to the command.
Destination: Console 4. Enter a command from the following list:
Module: DFHDFSIP v Display [O]
v Setdmf Active
v Setdmf Flush
DFHDF1001 Data management facility is ready for
v Setdmf Interval(mmss)
communication. At the prompt you may enter
v Setdmf NOActive
a DMF command, or request assistance by
v Setdmf NOTrace
entering a '?'
v Setdmf SHutdown[,I]
Explanation: The operator has requested communication with
v Setdmf Switch
the data management facility by executing a MSG pn
v Setdmf Trace
command (where pn represents the partition in which DMF is
Module: DFHDFOCX
executing).
System action: DMF will wait for the operator to reply to
DFHDF0000, and then perform one of the following actions:
v If the reply is null (Enter pressed) then communication with DFHDF1003 SETDMF changes the state of the DMF
DMF will be terminated. system as follows: 'ACTIVE' resumes
v If the reply is '?' then message DFHDF1002 will be recording, 'FLUSH' writes data to the current
displayed. data set, 'INTERVAL' changes the DMF
v Otherwise the action requested will be taken. wakeup value, 'NOACTIVE' suspends
User response: Take one of the following actions: recording, 'NOTRACE' suspends trace,
1. Enter a null response by pressing enter to end 'SHUTDOWN' terminates DMF, 'TRACE'
communication with DMF. resumes trace and 'SWITCH' causes DMF to
2. Enter a '?' for on line help information. switch to another data set. At the prompt you
3. Enter a command from the following list: may enter a DMF command, or request
v Display [O] further assistance by entering a '?' followed
v Setdmf Active by one of the commands (for example
v Setdmf Flush ?SETDMF'), or an operand (for example
v Setdmf Interval(mmss) ?ACTIVE').
v Setdmf NOActive Explanation: The operator has requested that online help be
v Setdmf NOTrace displayed for the DMF command SETDMF.
v Setdmf SHutdown[,I] System action: DMF will wait for the operator to reply to
v Setdmf Switch DFHDF0000, and then perform one of the following actions:
v Setdmf Trace v If the reply is EOB (Enter pressed) then communication
Module: DFHDFOCX with DMF will be terminated.
Destination: Console v If the reply is '?' then message DFHDF1002 will be
displayed.
v If the reply is '?SETDMF' then message DFHDF1003 will be
displayed.

v If the reply is '?DISPLAY' then message DFHDF1004 will be v If the reply is '?NOACTIVE' then message DFHDF1008 will
displayed. be displayed.
v If the reply is '?ACTIVE' then message DFHDF1005 will be v If the reply is '?NOTRACE' then message DFHDF1009 will
v If the reply is '?FLUSH' then message DFHDF1006 will be v If the reply is '?SHUTDOWN' then message DFHDF1010
displayed. will be displayed.
v If the reply is '?INTERVAL' then message DFHDF1007 will v If the reply is '?TRACE' then message DFHDF1011 will be
be displayed. displayed.
v If the reply is '?NOACTIVE' then message DFHDF1008 will v If the reply is '?SWITCH' then message DFHDF1028 will be
v If the reply is '?NOTRACE' then message DFHDF1009 will v Otherwise the action requested will be taken.
be displayed. User response: Take one of the following actions:
v If the reply is '?SHUTDOWN' then message DFHDF1010 1. Enter a null response by pressing enter to end
will be displayed. communication with DMF.
v If the reply is '?TRACE' then message DFHDF1011 will be 2. Enter a '?' for on line help information.
displayed. 3. Enter a '?' followed by a command or operand for help
v If the reply is '?SWITCH' then message DFHDF1028 will be information relating to the command or operand.
displayed. 4. Enter a command from the following list:
v Otherwise the action requested will be taken. v Display [O]
User response: Take one of the following actions: v Setdmf Active
1. Enter a null response by pressing enter to end v Setdmf Flush
communication with DMF. v Setdmf Interval(mmss)
2. Enter a '?' for on line help information. v Setdmf NOActive
3. Enter a '?' followed by a command or operand for help v Setdmf NOTrace
information relating to the command or operand. v Setdmf SHutdown[,I]
4. Enter a command from the following list: v Setdmf Switch
v Display [O] v Setdmf Trace
v Setdmf Active Module: DFHDFOCX
v Setdmf Flush Destination: Console
v Setdmf NOActive
v Setdmf NOTrace DFHDF1005 ACTIVE causes DMF to resume recording
v Setdmf SHutdown[,I] data in its data space. ACTIVE is only
v Setdmf Switch actioned if DMF is not currently in an active
v Setdmf Trace state. At the prompt you may enter a DMF
Module: DFHDFOCX command, or request further assistance by
Destination: Console entering a '?' followed by one of the
commands (for example ?SETDMF'), or an
operand (for example ?ACTIVE').
DFHDF1004 DISPLAY reflects the current state of the Explanation: The operator has requested that online help be
DMF system. Entered on its own it displays displayed for the DMF operand ACTIVE.
the current data set and its status. Entered System action: DMF will wait for the operator to reply to
with the operand 'O' it displays the current DFHDF0000, and then perform one of the following actions:
settings of DMF. At the prompt you may v If the reply is EOB (Enter pressed) then communication
enter a DMF command, or request further with DMF will be terminated.
assistance by entering a '?' followed by one v If the reply is '?' then message DFHDF1002 will be
of the commands (for example ?SETDMF'), or displayed.
an ope rand (for example ?ACTIVE'). v If the reply is '?SETDMF' then message DFHDF1003 will be
Explanation: The operator has requested that online help be displayed.
displayed for the DMF command DISPLAY. v If the reply is '?DISPLAY' then message DFHDF1004 will be
System action: DMF will wait for the operator to reply to displayed.
DFHDF0000, and then perform one of the following actions: v If the reply is '?ACTIVE' then message DFHDF1005 will be
v If the reply is EOB (Enter pressed) then communication displayed.
with DMF will be terminated. v If the reply is '?FLUSH' then message DFHDF1006 will be
v If the reply is '?' then message DFHDF1002 will be displayed.
displayed. v If the reply is '?INTERVAL' then message DFHDF1007 will
v If the reply is '?SETDMF' then message DFHDF1003 will be be displayed.
displayed. v If the reply is '?NOACTIVE' then message DFHDF1008 will
v If the reply is '?DISPLAY' then message DFHDF1004 will be be displayed.
displayed. v If the reply is '?NOTRACE' then message DFHDF1009 will
v If the reply is '?ACTIVE' then message DFHDF1005 will be be displayed.
displayed. v If the reply is '?SHUTDOWN' then message DFHDF1010
v If the reply is '?FLUSH' then message DFHDF1006 will be will be displayed.
displayed. v If the reply is '?TRACE' then message DFHDF1011 will be
v If the reply is '?INTERVAL' then message DFHDF1007 will displayed.
be displayed. v If the reply is '?SWITCH' then message DFHDF1028 will be
displayed.

v Otherwise the action requested will be taken. v Setdmf Active

User response: Take one of the following actions: v Setdmf Flush
1. Enter a null response by pressing enter to end v Setdmf Interval(mmss)
communication with DMF. v Setdmf NOActive
2. Enter a '?' for on line help information. v Setdmf NOTrace
3. Enter a '?' followed by a command or operand for help v Setdmf SHutdown[,I]
information relating to the command or operand. v Setdmf Switch
4. Enter a command from the following list: v Setdmf Trace
v Display [O] Module: DFHDFOCX
v Setdmf Active Destination: Console
v Setdmf Flush
v Setdmf NOActive DFHDF1007 INTERVAL(mmss) causes DMF to set the
v Setdmf NOTrace wakeup interval to the value in mmss. The
v Setdmf SHutdown[,I] wakeup interval is the minimum time that
v Setdmf Switch DMF will wait between writing data from
v Setdmf Trace the data space to the currently open data set.
Module: DFHDFOCX At the prompt you may enter a DMF
Destination: Console command, or request further assistance by
entering a '?' followed by one of the
commands (for example ?SETD MF'), or an
DFHDF1006 FLUSH causes DMF to write all records operand (for example ?ACTIVE').
currently stored in its data space to the Explanation: The operator has requested that online help be
currently open data set. FLUSH will only be displayed for the DMF operand INTERVAL.
actioned when there is a data set available. System action: DMF will wait for the operator to reply to
At the prompt you may enter a DMF DFHDF0000, and then perform one of the following actions:
command, or request further assistance by v If the reply is EOB (Enter pressed) then communication
entering a '?' followed by one of the with DMF will be terminated.
commands (for example ?SETDMF'), or an v If the reply is '?' then message DFHDF1002 will be
operand (for example ?ACTI VE'). displayed.
Explanation: The operator has requested that online help be v If the reply is '?SETDMF' then message DFHDF1003 will be
displayed for the DMF operand FLUSH. displayed.
System action: DMF will wait for the operator to reply to v If the reply is '?DISPLAY' then message DFHDF1004 will be
DFHDF0000, and then perform one of the following actions: displayed.
v If the reply is EOB (Enter pressed) then communication v If the reply is '?ACTIVE' then message DFHDF1005 will be
with DMF will be terminated. displayed.
v If the reply is '?' then message DFHDF1002 will be v If the reply is '?FLUSH' then message DFHDF1006 will be
displayed. displayed.
v If the reply is '?SETDMF' then message DFHDF1003 will be v If the reply is '?INTERVAL' then message DFHDF1007 will
v If the reply is '?DISPLAY' then message DFHDF1004 will be v If the reply is '?NOACTIVE' then message DFHDF1008 will
v If the reply is '?ACTIVE' then message DFHDF1005 will be v If the reply is '?NOTRACE' then message DFHDF1009 will
v If the reply is '?FLUSH' then message DFHDF1006 will be v If the reply is '?SHUTDOWN' then message DFHDF1010
v If the reply is '?INTERVAL' then message DFHDF1007 will v If the reply is '?TRACE' then message DFHDF1011 will be
v If the reply is '?NOACTIVE' then message DFHDF1008 will v If the reply is '?SWITCH' then message DFHDF1028 will be
v If the reply is '?NOTRACE' then message DFHDF1009 will v Otherwise the action requested will be taken.
v If the reply is '?SHUTDOWN' then message DFHDF1010 1. Enter a null response by pressing enter to end
will be displayed. communication with DMF.
v If the reply is '?TRACE' then message DFHDF1011 will be 2. Enter a '?' for on line help information.
displayed. 3. Enter a '?' followed by a command or operand for help
v If the reply is '?SWITCH' then message DFHDF1028 will be information relating to the command or operand.
v Otherwise the action requested will be taken. v Display [O]
User response: Take one of the following actions: v Setdmf Active
1. Enter a null response by pressing enter to end v Setdmf Flush
communication with DMF. v Setdmf Interval(mmss)
2. Enter a '?' for on line help information. v Setdmf NOActive
3. Enter a '?' followed by a command or operand for help v Setdmf NOTrace
information relating to the command or operand. v Setdmf SHutdown[,I]
4. Enter a command from the following list: v Setdmf Switch
v Display [O] v Setdmf Trace

Module: DFHDFOCX operand (for example ?ACTIVE').

Destination: Console Explanation: The operator has requested that online help be
displayed for the DMF operand NOTRACE.
DFHDF1008 NOACTIVE causes DMF to stop recording DFHDF0000, and then perform one of the following actions:
data in its data space. NOACTIVE is only v If the reply is EOB (Enter pressed) then communication
actioned when DMF is currently in an with DMF will be terminated.
ACTIVE state. At the prompt you may enter v If the reply is '?' then message DFHDF1002 will be
a DMF command, or request further displayed.
assistance by entering a '?' followed by one v If the reply is '?SETDMF' then message DFHDF1003 will be
of the commands (for example ?SETDMF'), or displayed.
an operand (for example ?ACTIVE'). v If the reply is '?DISPLAY' then message DFHDF1004 will be
displayed for the DMF operand NOACTIVE. v If the reply is '?ACTIVE' then message DFHDF1005 will be
DFHDF0000, and then perform one of the following actions: v If the reply is '?FLUSH' then message DFHDF1006 will be
with DMF will be terminated. v If the reply is '?INTERVAL' then message DFHDF1007 will
v If the reply is '?' then message DFHDF1002 will be be displayed.
v If the reply is '?ACTIVE' then message DFHDF1005 will be will be displayed.
v If the reply is '?FLUSH' then message DFHDF1006 will be displayed.
displayed. v If the reply is '?SWITCH' then message DFHDF1028 will be
v If the reply is '?INTERVAL' then message DFHDF1007 will displayed.
be displayed. v Otherwise the action requested will be taken.
v If the reply is '?NOACTIVE' then message DFHDF1008 will User response: Take one of the following actions:
be displayed. 1. Enter a null response by pressing enter to end
v If the reply is '?NOTRACE' then message DFHDF1009 will communication with DMF.
be displayed. 2. Enter a '?' for on line help information.
v If the reply is '?SHUTDOWN' then message DFHDF1010 3. Enter a '?' followed by a command or operand for help
will be displayed. information relating to the command or operand.
v If the reply is '?TRACE' then message DFHDF1011 will be 4. Enter a command from the following list:
displayed. v Display [O]
v If the reply is '?SWITCH' then message DFHDF1028 will be v Setdmf Active
displayed. v Setdmf Flush
v Otherwise the action requested will be taken. v Setdmf Interval(mmss)
User response: Take one of the following actions: v Setdmf NOActive
1. Enter a null response by pressing enter to end v Setdmf NOTrace
communication with DMF. v Setdmf SHutdown[,I]
2. Enter a '?' for on line help information. v Setdmf Switch
3. Enter a '?' followed by a command or operand for help v Setdmf Trace
information relating to the command or operand. Module: DFHDFOCX
4. Enter a command from the following list: Destination: Console
v Display [O]
v Setdmf Active
v Setdmf Flush DFHDF1010 SHUTDOWN causes DMF to terminate.
v Setdmf Interval(mmss) Entered on its own, it causes DMF to stop
v Setdmf NOActive recording data in its data space and write all
v Setdmf NOTrace data to the currently open data set before
v Setdmf SHutdown[,I] terminating. Entered with the optional 'I'
v Setdmf Switch parameter, it causes DMF to terminate
v Setdmf Trace immediately. At the prompt you may enter a
Module: DFHDFOCX DMF command, or request further assistance
Destination: Console by entering a '?' followed by one of the
operand (for example ?ACTIVE').
DFHDF1009 NOTRACE causes DMF to stop gathering Explanation: The operator has requested that online help be
trace information. NOTRACE is only displayed for the DMF operand SHUTDOWN.
actioned when DMF trace is in an ACTIVE System action: DMF will wait for the operator to reply to
state. At the prompt you may enter a DMF DFHDF0000, and then perform one of the following actions:
command, or request further assistance by v If the reply is EOB (Enter pressed) then communication
entering a '?' followed by one of the with DMF will be terminated.

v If the reply is '?' then message DFHDF1002 will be v If the reply is '?INTERVAL' then message DFHDF1007 will
v If the reply is '?SETDMF' then message DFHDF1003 will be v If the reply is '?NOACTIVE' then message DFHDF1008 will
v If the reply is '?DISPLAY' then message DFHDF1004 will be v If the reply is '?NOTRACE' then message DFHDF1009 will
v If the reply is '?ACTIVE' then message DFHDF1005 will be v If the reply is '?SHUTDOWN' then message DFHDF1010
v If the reply is '?FLUSH' then message DFHDF1006 will be v If the reply is '?TRACE' then message DFHDF1011 will be
displayed. displayed.
v If the reply is '?INTERVAL' then message DFHDF1007 will v If the reply is '?SWITCH' then message DFHDF1028 will be
v If the reply is '?NOACTIVE' then message DFHDF1008 will v Otherwise the action requested will be taken.
v If the reply is '?NOTRACE' then message DFHDF1009 will 1. Enter a null response by pressing enter to end
be displayed. communication with DMF.
v If the reply is '?SHUTDOWN' then message DFHDF1010 2. Enter a '?' for on line help information.
will be displayed. 3. Enter a '?' followed by a command or operand for help
v If the reply is '?TRACE' then message DFHDF1011 will be information relating to the command or operand.
v If the reply is '?SWITCH' then message DFHDF1028 will be v Display [O]
displayed. v Setdmf Active
v Otherwise the action requested will be taken. v Setdmf Flush
User response: Take one of the following actions: v Setdmf Interval(mmss)
1. Enter a null response by pressing enter to end v Setdmf NOActive
communication with DMF. v Setdmf NOTrace
2. Enter a '?' for on line help information. v Setdmf SHutdown[,I]
3. Enter a '?' followed by a command or operand for help v Setdmf Switch
information relating to the command or operand. v Setdmf Trace
4. Enter a command from the following list: Module: DFHDFOCX
v Display [O] Destination: Console
v Setdmf Active
v Setdmf Flush
v Setdmf Interval(mmss) DFHDF1012 The command you have entered - command -
v Setdmf NOActive could not be understood. At the prompt you
v Setdmf NOTrace may enter a DMF command, or request
v Setdmf SHutdown[,I] further assistance by entering a '?' followed
v Setdmf Switch by one of the commands (for example
v Setdmf Trace ?SETDMF'), or an operand (for example
Module: DFHDFOCX ?ACTIVE').
Destination: Console Explanation: The operator has entered the command
command but this is not a valid DMF command.
DFHDF1011 TRACE causes DMF to resume gathering DFHDF0000, and then perform one of the following actions:
trace information. TRACE is only actioned if v If the reply is EOB (Enter pressed) then communication
the trace was in an INACTIVE state. At the with DMF will be terminated.
prompt you may enter a DMF command, or v If the reply is '?' then message DFHDF1002 will be
request further assistance by entering a '?' displayed.
followed by one of the commands (for v If the reply is '?SETDMF' then message DFHDF1003 will be
example ?SETDMF'), or an operand (for displayed.
example ?ACTIVE'). v If the reply is '?DISPLAY' then message DFHDF1004 will be
displayed for the DMF operand TRACE. v If the reply is '?ACTIVE' then message DFHDF1005 will be
DFHDF0000, and then perform one of the following actions: v If the reply is '?FLUSH' then message DFHDF1006 will be
with DMF will be terminated. v If the reply is '?INTERVAL' then message DFHDF1007 will
v If the reply is '?' then message DFHDF1002 will be be displayed.
v If the reply is '?ACTIVE' then message DFHDF1005 will be will be displayed.
v If the reply is '?FLUSH' then message DFHDF1006 will be displayed.
displayed.

v If the reply is '?SWITCH' then message DFHDF1028 will be v Setdmf Active

displayed. v Setdmf Flush
v Otherwise the action requested will be taken. v Setdmf Interval(mmss)
User response: Take one of the following actions: v Setdmf NOActive
1. Enter a null response by pressing enter to end v Setdmf NOTrace
communication with DMF. v Setdmf SHutdown[,I]
2. Enter a '?' for on line help information. v Setdmf Switch
3. Enter a '?' followed by a command or operand for help v Setdmf Trace
information relating to the command or operand. Module: DFHDFOCX
4. Enter a command from the following list: Destination: Console
v Display [O]
v Setdmf Active
v Setdmf Flush DFHDF1014 The DMF Console file is not open, and so
v Setdmf Interval(mmss) DMF is not able to handle communications.
v Setdmf NOActive Explanation: Data management facility (DMF) has
v Setdmf NOTrace determined that the console file needed for communication
v Setdmf SHutdown[,I] with the operator is closed, and so cannot continue with
v Setdmf Switch operator communication.
v Setdmf Trace System action: DMF will terminate this communication
Module: DFHDFOCX request.
Destination: Console User response: You need further assistance from IBM to
DFHDF1013 The operand you have entered - operand - Module: DFHDFOCX
could not be understood. At the prompt you Destination: Console
may enter a DMF command, or request
further assistance by entering a '?' followed
by one of the commands (for example DFHDF1015 Data Management Facility Version X'version',
?SETDMF'), or an operand (for example the wake up interval is set to mm minutes, ss
?ACTIVE'). seconds, the trace status is status, the data
Explanation: The operator has entered the operand operand space is named dspname, and the current
but this is not a valid DMF operand. recording state is state.
System action: DMF will wait for the operator to reply to Explanation: Data management facility (DMF) has been
DFHDF0000, and then perform one of the following actions: requested to display information about the current settings by
v If the reply is EOB (Enter pressed) then communication the operator.
with DMF will be terminated. System action: DMF displays the current status and
v If the reply is '?' then message DFHDF1002 will be continues.
displayed. User response: None.
v If the reply is '?SETDMF' then message DFHDF1003 will be Module: DFHDFOCX
displayed. Destination: Console
v If the reply is '?DISPLAY' then message DFHDF1004 will be
displayed. DFHDF1016 Data Management Facility will terminate.
v If the reply is '?ACTIVE' then message DFHDF1005 will be Shutdown option is option.
displayed. Explanation: Data management facility (DMF) has been
v If the reply is '?FLUSH' then message DFHDF1006 will be requested to terminate by the operator. Additionally, the
displayed. option option has been specified, or allowed to default.
v If the reply is '?INTERVAL' then message DFHDF1007 will System action: DMF terminates, either normally or
be displayed. immediately.
v If the reply is '?NOACTIVE' then message DFHDF1008 will User response: None.
be displayed. Module: DFHDFOCX
v If the reply is '?NOTRACE' then message DFHDF1009 will Destination: Console
be displayed.
v If the reply is '?SHUTDOWN' then message DFHDF1010
will be displayed. DFHDF1017 Data Management Facility has called the
v If the reply is '?TRACE' then message DFHDF1011 will be trace facility with the function call
displayed. {START_TRACE | PAUSE_TRACE
v If the reply is '?SWITCH' then message DFHDF1028 will be |RESUME_TRACE | QUERY_TRACE} but this
displayed. failed for reason {INVALID_FORMAT |
v Otherwise the action requested will be taken. INVALID_FUNCTION | INVALID_ANCHOR |
User response: Take one of the following actions: INVALID_DFLM_TOKEN |
1. Enter a null response by pressing enter to end DFGF_GET_FAILURE |
communication with DMF. DFLM_RESERVE_FAILURE |
2. Enter a '?' for on line help information. DFLM_RELEASE_FAILURE |
3. Enter a '?' followed by a command or operand for help GETVIS_EXHAUSTED | PFIX_FAILED |
information relating to the command or operand. RESOURCE_BUSY | TRACE_ACTIVE
4. Enter a command from the following list: |TRACE_INACTIVE | TRACE_PAUSED}.
v Display [O] Explanation: Data management facility (DMF) has been

requested to alter its trace facility status by the operator. The Module: DFHDFOCX
call was one of: Destination: Console
START_TRACE
Start the trace facility
PAUSE_TRACE DFHDF1019 Data Management Facility Trace is already
Temporarily suspend the trace facility Active.
RESUME_TRACE Explanation: Data management facility (DMF) has been
Resume the trace facility requested to set its trace facility to Active by the operator.
QUERY_TRACE However, the trace facility is already active.
Query the status of the trace facility System action: DMF continues.
Module: DFHDFOCX
However, one of the following occurred:
INVALID_FORMAT
facility was not a valid parameter list. DFHDF1020 Data Management Facility Trace is not
INVALID_FUNCTION Active.
indicates that the parameter list passed to the trace Explanation: Data management facility (DMF) has been
facility contained an invalid request. requested to set its trace facility to Notrace by the operator.
INVALID_ANCHOR However, the trace facility is not active.
indicates that the DMF Anchor Block could not be System action: DMF continues.
validated. User response: None.
INVALID_DFLM_TOKEN Module: DFHDFOCX
indicates that the token representing the trace facility Destination: Console
was invalid.
DFGF_GET_FAILURE
indicates that a request to get storage failed. DFHDF1021 Data Management Facility Interval has been
DFLM_RESERVE_FAILURE set to mm minutes, ss seconds.
indicates that an internal call to the lock manager to Explanation: Data management facility (DMF) has set its
reserve a lock returned an unexpected response. wake up interval to mm minutes and ss seconds.
DFLM_RELEASE_FAILURE System action: DMF continues.
indicates that an internal call to the lock manager to User response: None.
release a lock returned an unexpected response. Module: DFHDFOCX
GETVIS_EXHAUSTED Destination: Console
DFHDF1022 Data Management Facility currently has no
available.
open data sets.
PFIX_FAILED
Explanation: This messages is issued in response to a
DISPLAY command issued to Data management facility
(DMF). However, there are currently no open data sets.
RESOURCE_BUSY
indicates that the internal request to lock the trace
facility returned with a response that showed the
Module: DFHDFOCX
resource was already locked.
TRACE_ACTIVE
indicates that the trace facility determined that the
trace was already active. DFHDF1023 Data Management Facility is currently using
TRACE_INACTIVE data set dataset.
indicates that the trace facility determined that the Explanation: This message is issued in response to a
trace was already inactive. DISPLAY command issued to data management facility
TRACE_PAUSED (DMF). The currently open data set being used by DMF is
indicates that the trace facility determined that the dataset.
trace was already paused. System action: DMF continues.
System action: DMF continues. User response: None.
User response: You need further assistance from IBM to Module: DFHDFOCX
resolve this problem. See Part 4 of the CICS Problem Destination: Console
Module: DFHDFOCX
Destination: Console DFHDF1024 Data Management Facility was unable to
change its recording status. Reason is
DFHDF1018 Data Management Facility trace status is now INVALID_STATUS}.
status. Explanation: This message is issued in response to a
Explanation: Data management facility (DMF) has been SETDMF ACTIVE or SETDMF NOACTIVE command. Data
requested to change its trace status by the operator. The trace management facility (DMF) has attempted to change its
has now been set to status. recording state. However, one of the following occurred:

INVALID_FORMAT PFIX_FAILED
indicates that the parameter list passed to the queue indicates that the partition GETVIS storage requested
manager was not a valid parameter list for the could not be PFIXed by z/VSE.
queue manager. System action: DMF continues
INVALID_FUNCTION User response: You may:
indicates that the parameter list passed to the queue 1. Increase the partition size
manager contained an invalid request. 2. Specify a SIZE parameter on the EXEC card for DFHDFSIP. A
INVALID_STATUS suitable expression would be SIZE=DFHDFSIP
indicates that an attempt has been made to change 3. You need further assistance from IBM to resolve this
the recording state to NOACTIVE (and the state was problem. See Part 4 of the CICS Problem Determination
not previously ACTIVE) or to change the recording Guide for guidance on how to proceed.
state to ACTIVE (and the state was not previously Module: DFHDFOC
NOACTIVE). Destination: Console
1. Issue DISPLAY O to determine the current recording state DFHDF1028 SWITCH causes DMF to close the currently
2. You need further assistance from IBM to resolve this open data set (if there is an open data set)
problem. See Part 4 of the CICS Problem Determination and open the next suitable data set. At the
Guide for guidance on how to proceed. prompt you may enter a DMF command, or
Module: DFHDFOCX request further assistance by entering a '?'
Destination: Console followed by one of the commands (for
example ?SETDMF'), or an operand (for
example ?ACTIVE').
DFHDF1025 Data Management Facility recording state has Explanation: The operator has requested that online help be
been set to state. displayed for the DMF operand SWITCH.
Explanation: This message is issued in response to a System action: DMF will wait for the operator to reply to
SETDMF ACTIVE or SETDMF NOACTIVE command issued DFHDF0000, and then perform one of the following actions:
to data management facility (DMF). The recording state of v If the reply is EOB (Enter pressed) then communication
DMF has been set to state. with DMF will be terminated.
System action: DMF continues. v If the reply is '?' then message DFHDF1002 will be
User response: None. displayed.
Module: DFHDFOCX v If the reply is '?SETDMF' then message DFHDF1003 will be
Destination: Console displayed.
displayed.
DFHDF1026 Data Management Facility has passed the v If the reply is '?ACTIVE' then message DFHDF1005 will be
request request to the File Manager. displayed.
Explanation: This message is issued in response to a v If the reply is '?FLUSH' then message DFHDF1006 will be
SETDMF command issued to data management facility (DMF). displayed.
The request may be either Switch or Flush. v If the reply is '?INTERVAL' then message DFHDF1007 will
System action: DMF continues. be displayed.
User response: None. v If the reply is '?NOACTIVE' then message DFHDF1008 will
Module: DFHDFOCX be displayed.
Destination: Console v If the reply is '?NOTRACE' then message DFHDF1009 will
be displayed.
DFHDF1027 Data Management Facility has called the v If the reply is '?SHUTDOWN' then message DFHDF1010
storage manager to acquire storage, but this will be displayed.
has failed for reason {INVALID_FORMAT | v If the reply is '?TRACE' then message DFHDF1011 will be
INVALID_FUNCTION | displayed.
SEVERE_STORAGE_ERROR | v If the reply is '?SWITCH' then message DFHDF1028 will be
GETVIS_EXHAUSTED | PFIX_FAILED}. displayed.
Explanation: Data management facility (DMF) has been v Otherwise the action requested will be taken.
requested to acquire storage for a request block to be passed User response: Take one of the following actions:
to the File Manager. However, one of the following occurred: 1. Enter a null response by pressing enter to end
INVALID_FORMAT communication with DMF.
indicates that the parameter list passed to the 2. Enter a '?' for on line help information.
storage manager was not a valid parameter list. 3. Enter a '?' followed by a command or operand for help
INVALID_FUNCTION information relating to the command or operand.
indicates that the parameter list passed to the 4. Enter a command from the following list:
storage manager contained an invalid request. v Display [O]
SEVERE_STORAGE_ERROR v Setdmf Active
indicates that an error has occurred in storage v Setdmf Flush
management that DMF is unable to recover from. v Setdmf Interval(mmss)
GETVIS_EXHAUSTED v Setdmf NOActive
indicates that a request for storage failed because v Setdmf NOTrace
there was no more partition GETVIS storage v Setdmf SHutdown[,I]
available. v Setdmf Switch

v Setdmf Trace
Module: DFHDFOCX
perform the requested action. The reason is
that the DEBUG facility is status.
Explanation: The data management facility (DMF) was
DFHDF1029 DEBUG,ON causes DMF to load DFHDFTRP unable to carry out the DEBUG function requested. The
which will now be called at every trace call. DEBUG facility was found to have a status from one of the
DEBUG,OFF causes DMF to stop calling following:
DFHDFTRP and to delete the phase. At the v ALREADY ACTIVE, or
prompt you may enter a DMF command, or v NOT ACTIVE
request further assistance by entering a '?' System action: DMF will continue.
followed by one of the commands (for User response: Take one of the following actions:
example ?SETDMF'), or an operand (for 1. If you entered SETDMF DEBUG,ON then enter SETDMF
example ?ACTIVE'). DEBUG,OFF followed by SETDMF DEBUG,ON if you wish to
Explanation: The operator has requested that online help be enable a new version of DFHDFTRP
displayed for the DMF operand DEBUG. 2. If you entered SETDMF DEBUG,OFF then you need take no
System action: DMF will wait for the operator to reply to further action.
DFHDF0000, and then perform one of the following actions: Module: DFHDFOCX
v If the reply is EOB (Enter pressed) then communication Destination: Console
with DMF will be terminated.
v If the reply is '?' then message DFHDF1002 will be
displayed.
load phase DFHDFTRP.
v If the reply is '?SETDMF' then message DFHDF1003 will be
Explanation: The data management facility (DMF) was
displayed.
unable to load the Debug Facility program DFHDFTRP.
System action: DMF will continue, but will not enable the
displayed.
DEBUG facility.
v If the reply is '?ACTIVE' then message DFHDF1005 will be
displayed.
v If the reply is '?FLUSH' then message DFHDF1006 will be
displayed.
Module: DFHDFOCX.
v If the reply is '?INTERVAL' then message DFHDF1007 will
be displayed.
v If the reply is '?NOACTIVE' then message DFHDF1008 will
be displayed. DFHDF1032 Data management facility has determined
v If the reply is '?NOTRACE' then message DFHDF1009 will that phase DFHDFTRP has not been link
be displayed. edited with AMODE(31).
v If the reply is '?SHUTDOWN' then message DFHDF1010 Explanation: The data management facility (DMF) has loaded
will be displayed. the Debug Facility program DFHDFTRP, but has determined
v If the reply is '?TRACE' then message DFHDF1011 will be that the program was not link edited with AMODE(31)
displayed. specified.
v If the reply is '?SWITCH' then message DFHDF1028 will be System action: DMF will continue, but will not enable the
displayed. DEBUG facility.
v If the reply is '?DEBUG' then message DFHDF1029 will be User response: Re-link edit DFHDFTRP with AMODE(31)
displayed. specified, and re-issue the DEBUG,ON command to DMF.
v Otherwise the action requested will be taken. Module: DFHDFOCX.
User response: Take one of the following actions: Destination: Console
1. Enter a null response by pressing enter to end
communication with DMF.
2. Enter a '?' for on line help information. DFHDF1033 DFHDFTRP Version version, assembled by id.
3. Enter a '?' followed by a command or operand for help Assembled at HH/MM=hh/mm on
information relating to the command or operand. MM/DD=mm/dd. Latest PTF/APAR applied is
4. Enter a command from the following list: ptfno.
v Display [O] Explanation: Data management facility (DMF) has loaded its
v Setdmf Active Debug Facility program DFHDFTRP. This is an informational
v Setdmf Flush message that displays assembly information for the program.
v Setdmf Interval(mmss) v id is either USER or IBM to indicate who assembled the
v Setdmf NOActive program.
v Setdmf NOTrace v hh/mm is the time (hours and minutes of the 24 hour clock)
v Setdmf SHutdown[,I] that the program was assembled.
v Setdmf Switch v mm/dd is the date (month and day) that the program was
v Setdmf Trace assembled.
v Setdmf Debug,ON|OFF v ptfno is the latest APAR or PTF applied to the program (if
Module: DFHDFOCX the program was assembled by IBM).
Destination: Console System action: DMF continues.
Module: DFHDFOCX

DFHDF1034 Data management facility has been unable to DFHDF2051 DMF Global trap exit has been disabled by
acquire storage for the Global Work Area for DFHDFTRP.
DFHDFTRP. Explanation: The data management facility (DMF) global trap
Explanation: The data management facility (DMF) was exit program (DFHDFTRP) requested that the exit should be
unable to obtain sufficient 31-bit GETVIS storage to hold the disabled.
Global Work Area for the DMF Debug Facility program System action: DMF disables the trap exit so that it will not
DFHDFTRP. be reentered.
System action: DMF will continue, but the Debug Facility User response: Determine why DFHDFTRP has requested
will not be enabled. that it be disabled and act accordingly. You should use the
User response: Increase the size of the 31-bit GETVIS area. global trap exit only in consultation with an IBM support
Module: DFHDFOCX. representative.
Destination: Console Module: DFHDFTR
DFHDF1035 Data management Debug facility is now ON.

Explanation: The data management facility (DMF) has DFHDF2052 DMF system dump requested by global trap
successfully enabled its Debug Facility. exit DFHDFTRP.
System action: DMF continues. Explanation: The user-coded global trap exit program
User response: None. (DFHDFTRP) has requested a system dump in its return
Module: DFHDFOCX. action settings.
Destination: Console System action: DMF takes a system dump and continues
with the global trap still active.
User response: Analyse the requested dump.
DFHDF1036 Data management Debug facility is now OFF.
Explanation: The data management facility (DMF) has You should use the global trap exit only in consultation with
terminated its Debug Facility. an IBM support representative.
System action: DMF continues. Module: DFHDFTR
User response: None. Destination: Console
Module: DFHDFOCX.
DFHDF2053 DMF abend requested by global trap exit
DFHDFTRP.
DFHDF2001 Data Management Facility has detected that Explanation: The Data Management Facility (DMF) global
no datasets are currently open. Data may be trap exit program (DFHDFTRP) requested termination of
being lost. You should format a DMF dataset DMF.
and issue SETDMF SWITCH as soon as System action: DMF disables the trap exit so that it will not
possible. be reentered, takes a system dump and terminates DMF.
Explanation: Data Management Facility (DMF) has detected User response: Determine why DFHDFTRP has requested
that no dataset is currently open. This message is issued DMF termination and act accordingly. You should use the
periodically by DMF. global trap exit only in consultation with an IBM support
System action: DMF continues representative.
User response: You should make a dataset ready for DMF to Module: DFHDFTR
use by running DFHDFOU and then enter SETDMF SWITCH so that Destination: Console
DMF will start to use the dataset to write records to. If you do
not do so, then the data space used by DMF to collect records
DFHDF2054 Program check occurred within global trap
may fill up and data may subsequently be lost.
exit - DFHDFTRP now marked unusable by
Module: DFHDFIT
DMF.
Explanation: After making a trace entry, the Data
Management Facility (DMF) trace function called the global
DFHDF2002 Data Management Facility has detected that trap exit program (DFHDFTRP). A program check occurred
an abend has occurred while in Cross during execution of DFHDFTRP.
Memory Mode. System action: DMF marks the currently active version of
Explanation: Data Management Facility (DMF) has detected DFHDFTRP unusable, and will ignore it on future calls to the
that an abend has occurred while a record was being written trace function. DMF then takes a dump and continues
in Cross Memory Mode. execution. Trace entries from DMF will still be made.
System action: DMF sets its state such that no further records User response: Use the dump to find the cause of the
will be accepted, takes a system dump, and attempts to write program check. To replace the currently active but unusable
all records in the data space to the currently open dataset, DFHDFTRP by a new version in the DMF program library,
before terminating. issue the following command:
User response: You need further assistance from IBM to SETDMF DEBUG,ON (to activate the new version of the
resolve this problem. See Part 4 of the CICS Problem trap)
You should use the global trap exit only in consultation with
Module: DFHDFIT
an IBM support representative.
Module: DFHDFTR

DFHDF3001 Data set status report. DFHDF3005 Data Management Facility dataset
Explanation: The operator has requested that data set dataset_name is open.
information be displayed during the startup of Data Explanation: The data management facility has opened
Management Facility. This message is accompanied by dataset dataset_name and is ready to start writing records to it.
message DFHDF3002, a number of DFHDF3003 messages and System action: Data management facility continues.
by message DFHDF3004. User response: None.
System action: Data Management Facility continues to write Module: DFHDFFM.
the requested dataset status information to the console. Destination: Console
Module: DFHDFFM.
Destination: Console DFHDF3006 Data Management Facility dataset
dataset_name is closed.
Explanation: The data management facility has closed dataset
DFHDF3002 Data Set Name Status Avail(%) dataset_name.
Explanation: The operator has requested that data set System action: Data management facility continues.
information be displayed during the startup of Data User response: The data on the dataset dataset_name should
Management Facility. This message is accompanied by now be processed by DFHDFOU and cleared so that data
message DFHDF3001, a number of DFHDF3003 messages and management facility may reuse the dataset.
by message DFHDF3004. Module: DFHDFFM.
System action: Data Management Facility continues to write Destination: Console
the requested dataset status information to the console.
Module: DFHDFFM. DFHDF3007 Data Management Facility cannot find a
Destination: Console dataset to open. Reply 'GO' to cause DMF to
continue operating but without a dataset
(data will still be recorded in the data space),
DFHDF3003 dataset_name status usage or 'RETRY' to cause DMF to retry its attempt
Explanation: The operator has requested that data set to open a data set
information be displayed during the startup of Data Explanation: The data management facility has exhausted its
Management Facility. list of dataset names, and is unable to find a dataset in a
suitable state for writing records to.
Data Management Facility produces one DFHDF3003 message
per dataset listed in the DMF startup table that is currently A dataset should be made ready for use by data management
being used. The information is as follows: facility, by using the program DFHDFOU. If data management
v dataset_name is the name of the data set facility cannot find a dataset to use there is the possibility that
v status may be one of: the data space will fill up, and data will be lost. This message
NOTESDS is accompanied by message DFHDF0000, to which a response
the data set is not a VSAM ESDS dataset should be made.
INVREC System action: Data management facility waits for the
the data set has not been defined with a operator to reply.
sufficiently large maximum record length User response: If you cannot make a dataset ready now,
OPNFAIL enter 'GO' to the subsequent DFHDF0000 message. Otherwise,
the data set could not be opened to extract all the make a dataset ready and then enter 'RETRY' to the subsequent
required information DFHDF0000 message.
INIT the file is ready for use Module: DFHDFFM.
PARTIAL Destination: Console
the file has been partially used by DMF
FULL the file is full, and must be emptied before DMF
can use it. DFHDF3009 Data Management Facility has been unable
v usage is the percentage of the file used to build VSAM control block control_block.
System action: Data Management Facility continues to write The return code from VSAM for the GENCB
the requested dataset status information to the console. request was X'rc'.
User response: None. Explanation: The data management facility has attempted to
Module: DFHDFFM. construct the necessary VSAM control blocks but one of these
Destination: Console has not been built successfully.
control_block may be one of:
DFHDF3004 Data set status report is complete. v ACB
Explanation: The operator has requested that data set v EXLST
information be displayed during the startup of Data v RPL
Management Facility. This message is accompanied by System action: Data management facility terminates with a
message DFHDF3001, message DFHDF3002 and a number of dump.
DFHDF3003 messages. User response: Take one of the following actions:
System action: Data Management Facility continues. 1. Increase the partition size
User response: None. 2. Specify a SIZE operand on the EXEC card for DFHDFSIP. A
Module: DFHDFFM. suitable expression would be SIZE=DFHDFSIP

3. You need further assistance from IBM to resolve this rc may be one of:
problem. See Part 4 of the CICS Problem Determination 0 indicates normal response
Guide for guidance on how to proceed. 1 indicates DDNAME does not exist
Module: DFHDFFM. 2 invalid request
Destination: Console 4 no GETVIS storage available
5 DFHEVLBS internal error
6 subarea not available
DFHDF3010 Data Management Facility has been unable 7 invalid subarea
to add a label for VSAM catalog catalog_name. 8 invalid access method
The return code from DFHEVSLV was X'rc'. 9 delete for wrong dataset
Explanation: The data management facility has attempted to B inconsistent access method
add a label for the user supplied catalog catalog_name but this System action: Data management facility continues.
has failed. The return code from DFHEVLSV was rc. User response: None.
rc may be one of: Module: DFHDFFM.
0: normal response Destination: Console
2 invalid request
3 no space in label area DFHDF3013 Data Management Facility has been unable
4 no GETVIS storage available to find a suitable dataset to open.
5 DFHEVLBS internal error Explanation: The data management facility has attempted to
6 subarea not available open a dataset from the list of datasets but was not able to
7 invalid subarea find one suitable.
8 invalid access method System action: Data management facility continues.
A already allocated User response: Make a dataset available by using the DFHDFOU
B inconsistent access method program and then issue a request to DMF to open a dataset.
System action: Data management facility terminates with a Module: DFHDFFM.
dump. Destination: Console
1. Increase the partition size
2. Specify a SIZE operand on the EXEC card for DFHDFSIP. A DFHDF3014 Data Management Facility has been asked to
suitable expression would be SIZE=DFHDFSIP open a dataset but DMF already has an open
3. You need further assistance from IBM to resolve this dataset.
problem. See Part 4 of the CICS Problem Determination Explanation: The data management facility has been
Guide for guidance on how to proceed. requested to open a dataset, but already has an open dataset.
Module: DFHDFFM. System action: Data management facility continues.
Destination: Console User response: None.
Module: DFHDFFM.
DFHDF3011 Data Management Facility has been unable
to add a label for VSAM dataset dataset_name.
The return code from DFHEVSLV was X'rc'. DFHDF3015 Data Management Facility attempted to open
Explanation: The data management facility has attempted to dataset dataset_name but this failed. The
add a label for the dataset named dataset_name but this has return code from VSAM for the OPEN
failed. The return code from DFHEVLSV was rc. request was X'rc'.
Explanation: The data management facility has attempted to
rc may be one of:
open dataset dataset_name. However, the OPEN failed for the
0 normal response
reason given in rc.
2 invalid request
3 no space in label area The VSAM codes given are explained in the section
4 no GETVIS storage available "VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2.
5 DFHEVLBS internal error System action: Data management facility continues.
6 subarea not available User response: None.
7 invalid subarea Module: DFHDFFM.
8 invalid access method Destination: Console
A already allocated
B inconsistent access method
System action: Data management facility continues. DFHDF3016 Data Management Facility attempted to close
User response: None. dataset dataset_name but this failed. The
Module: DFHDFFM. return code from VSAM for the CLOSE
Destination: Console request was X'rc'.
Explanation: The data management facility has attempted to
close dataset dataset_name. However, the CLOSE failed for the
DFHDF3012 Data Management Facility has been unable reason given in rc.
to delete a label for VSAM dataset
dataset_name. The return code from The VSAM codes given are explained in the section
DFHEVSLV was X'rc'. "VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2
Explanation: The data management facility has attempted to System action: Data management facility continues.
delete a label for the dataset named dataset_name but this has User response: None.
failed. The return code from DFHEVLSV was rc. Module: DFHDFFM.

Destination: Console 3. You need further assistance from IBM to resolve this
DFHDF3017 Data Management Facility has been asked to Module: DFHDFFM.
close a dataset but DMF does not have an Destination: Console
open dataset
Explanation: The data management facility has been
requested to close a dataset, but does not have an open DFHDF3021 An abend code X'abcode' has been detected by
dataset. DFHDFFM.
System action: Data management facility continues. Explanation: The Data Management Facility (DMF) has
User response: None. detected an abend with the z/VSE Cancel code abcode. This
Module: DFHDFFM. has occurred in the File Manager sub task of DMF.
Destination: Console System action: If DMF was recording to a data set, the data
set will be closed, and the File Manager sub-task will issue a
CANCEL ALL macro.
DFHDF3018 Data Management Facility has been asked to User response: You need further assistance from IBM to
reduce space in the data space, but there is resolve this problem. See Part 4 of the CICS Problem
no open dataset Determination Guide for guidance on how to proceed.
Explanation: The data management facility has been Module: DFHDFFM
requested to reduce space in the data space, but does not have Destination: Console
an open dataset to be able to write the data out.
There is a possibility in this situation that data may be lost. DFHDF3022 A program check has been detected by
System action: Data management facility continues. DFHDFFM PC exit at DFHDFFMP.
User response: Ready a DMF dataset by using the DFHDFOU Explanation: The Data Management Facility (DMF) File
program, and issue a SETDMF SWITCH request to cause a dataset Manager PC exit has been driven. This has occurred in the
to be opened. File Manager sub task of DMF.
Module: DFHDFFM. System action: If DMF was recording to a data set, the data
Destination: Console set will be closed, and the File Manager sub-task will issue a
CANCEL ALL macro.
DFHDF3019 Data Management Facility has been asked to User response: You need further assistance from IBM to
flush the data from the data space, but there resolve this problem. See Part 4 of the CICS Problem
is no open dataset Determination Guide for guidance on how to proceed.
Explanation: The data management facility has been Module: DFHDFFM
requested to flush the data from the data space to the VSAM Destination: Console
dataset, but does not have an open dataset to be able to write
the data out. DFHDF3023 Data Management Facility has processed the
There is a possibility in this situation that data may be lost. FLUSH request.
System action: Data management facility continues. Explanation: The Data Management Facility (DMF) has
User response: Ready a DMF dataset by using the DFHDFOU completed the FLUSH request This may be as the result of an
program, and issue a SETDMF SWITCH request to cause a dataset operator command, or as the result of internal processing
to be opened, and then issue a SETDMF FLUSH request. (during SHUTDOWN processing, for example).
Module: DFHDFFM. System action: DMF continues.
Destination: Console Destination: Console
Module: DFHDFFM
DFHDF3020 Data Management Facility has been unable

to acquire a buffer area. The reason code DFHDF4001 Data management facility has determined
from DFHDFGF was X'reason'. that the Anchor Block is Invalid.
Explanation: The data management facility has attempted to Explanation: The Data Management Facility (DMF) has
acquire a buffer area for use with VSE/VSAM, but this has entered its abend handler, and has determined that the DMF
failed. The reason code from DFHDFGF was reason. Anchor Block is invalid.
System action: DMF will take an SDUMPX and initiate an
reason may be one of: immediate shutdown of the DMF partition.
1 - Invalid_Format User response: You need further assistance from IBM to
2 - Invalid_Function resolve this problem. See Part 4 of the CICS Problem
3 - Severe_Storage_Error Determination Guide for guidance on how to proceed.
4 - GETVIS_Exhausted Module: DFHDFABX
5 - PFIX_Failed Destination: Console
System action: Data management facility terminates with a
dump.
User response: If reason is 4 then you may take one of the DFHDF4002 A Program Check has occurred in a message
following actions: handling module.
1. Increase the partition size Explanation: The Data Management Facility (DMF) has
2. Specify a SIZE operand on the EXEC DFHDFSIP statement. A detected a program check, and has also determined that the
suitable expression would be SIZE=DFHDFSIP. abend occurred in a message module (either DFHMEBM or
DFHDFRM).

immediate shutdown of the DMF partition.

DFHDF5001 Data management facility has determined
that the Anchor Block is Invalid.
Explanation: The Data Management Facility (DMF) has
entered its abend handler, and has determined that the DMF
Module: DFHDFABX
Anchor Block is invalid.
DFHDF4003 A program check has occurred at X'psw' in User response: You need further assistance from IBM to
module modulename. resolve this problem. See Part 4 of the CICS Problem
Explanation: The Data Management Facility (DMF) has Determination Guide for guidance on how to proceed.
detected a program check, and has also determined that the Module: DFHDFPCX
abend occurred with the PSW set to psw which pointed to Destination: Console
module modulename.
DFHDF5002 A Program Check has occurred in a message
handling module.
detected a program check, and has also determined that the
abend occurred in a message module (either DFHMEBM or
Module: DFHDFABX
DFHDFRM).
DFHDF4004 An abend code X'abcode' has been detected by User response: You need further assistance from IBM to
DMF. resolve this problem. See Part 4 of the CICS Problem
Explanation: The Data Management Facility (DMF) has Determination Guide for guidance on how to proceed.
detected an abend with the z/VSE Cancel code abcode. Module: DFHDFPCX
System action: DMF will take an SDUMPX and initiate an Destination: Console
DFHDF5003 A program check has occurred at X'psw' in
module modulename.
Module: DFHDFABX
detected a program check, and has also determined that the
abend occurred with the PSW set to psw which pointed to
module modulename.
DFHDF4005 DMF has detected that a CANCEL ALL System action: DMF will take an SDUMPX and initiate an
macro has been issued by the DFHDFFM immediate shutdown of the DMF partition.
sub-task. User response: You need further assistance from IBM to
Explanation: The Data Management Facility (DMF) has resolve this problem. See Part 4 of the CICS Problem
detected that a sub-task (DFHDFFM) has issued a CANCEL Determination Guide for guidance on how to proceed.
ALL macro. Module: DFHDFPCX
System action: DMF will take an SDUMPX and initiate an Destination: Console
DFHDF6001 Invalid keyword found
Explanation: While processing the SYSIPT input parameters,
DFHDFOU read in a keyword that could not be identified.
Module: DFHDFABX
System action: DFHDFOU will continue to validate the
SYSIPT input parameters, without processing the files. After
validating the SYSIPT parameters, DFHDFOU will issue
DFHDF4006 Cancel code xxx (X'yy') detected by DMF. DFHDF6030 and return to z/VSE with a return code of 8,
Explanation: The Data Management Facility (DMF) has unless a more serious error is detected later.
detected that the cancel code xxx (its hexadecimal equivalent User response: You will have to correct your SYSIPT data
is yy) has been issued by z/VSE. See the "VSE/Advanced and supply a valid keyword. Valid keywords are:
Functions Cancel Codes" in section "VSE/Advanced Functions INDD
Codes & SVC Errors" of z/VSE Messages and Codes - Volume 1 OUTDD
for an explanation of the cancel codes. DATE
System action: This is an informatory message. DMF will START
attempt to handle the cancel code and will issue further END
messages explaining its subsequent actions. SID
Refer to the CICS Operations and Utilities Guide for details on
Module: DFHDFABX
coding the input parameters to DFHDFOU.
Module: DFHDFOU
Destination: SYSLST

DFHDF6002 ( expected DFHDF6006 DUMP, CLEAR or ALL expected

Explanation: While processing the SYSIPT input parameters, Explanation: While processing the SYSIPT input parameters,
DFHDFOU expected to find the character ( but did not. DFHDFOU expected to find the string DUMP, or CLEAR or
System action: DFHDFOU will continue to validate the ALL but did not.
SYSIPT input parameters, without processing the files. After System action: DFHDFOU will continue to validate the
validating the SYSIPT parameters, DFHDFOU will issue SYSIPT input parameters, without processing the files. After
DFHDF6030 and return to z/VSE with a return code of 8, validating the SYSIPT parameters, DFHDFOU will issue
unless a more serious error is detected later. DFHDF6030 and return to z/VSE with a return code of 8,
User response: You will have to correct your SYSIPT data, unless a more serious error is detected later.
and resubmit the job. Refer to the CICS Operations and Utilities User response: You will have to correct your SYSIPT data,
Guide for details on coding the input parameters to and resubmit the job. Refer to the CICS Operations and Utilities
DFHDFOU. Guide for details on coding the input parameters to
Module: DFHDFOU DFHDFOU.
Destination: SYSLST Module: DFHDFOU
Destination: SYSLST
DFHDF6003 filename expected

Explanation: While processing the SYSIPT input parameters, DFHDF6007 ) expected
DFHDFOU expected to find a value for filename but did not. Explanation: While processing the SYSIPT input parameters,
System action: DFHDFOU will continue to validate the DFHDFOU expected to find the character ) but did not.
Destination: SYSLST
DFHDF6004 OPTIONS expected

Explanation: While processing the SYSIPT input parameters, DFHDF6008 filename too long
DFHDFOU expected to find the string OPTIONS but did not. Explanation: While processing the SYSIPT input parameters,
System action: DFHDFOU will continue to validate the DFHDFOU determined that the length of the value specified
SYSIPT input parameters, without processing the files. After for filename is greater than 7 characters in length.
validating the SYSIPT parameters, DFHDFOU will issue System action: DFHDFOU will continue to validate the
DFHDF6030 and return to z/VSE with a return code of 8, SYSIPT input parameters, without processing the files. After
unless a more serious error is detected later. validating the SYSIPT parameters, DFHDFOU will issue
User response: You will have to correct your SYSIPT data, DFHDF6030 and return to z/VSE with a return code of 8,
and resubmit the job. Refer to the CICS Operations and Utilities unless a more serious error is detected later.
Guide for details on coding the input parameters to User response: You will have to correct your SYSIPT data,
DFHDFOU. and resubmit the job. Refer to the CICS Operations and Utilities
Module: DFHDFOU Guide for details on coding the input parameters to
Destination: SYSLST DFHDFOU.
Module: DFHDFOU
Destination: SYSLST
DFHDF6005 , expected
DFHDFOU expected to find the character , but did not. DFHDF6009 TYPE or NOTYPE expected
System action: DFHDFOU will continue to validate the Explanation: While processing the SYSIPT input parameters,
SYSIPT input parameters, without processing the files. After DFHDFOU expected to find the string TYPE or NOTYPE but
validating the SYSIPT parameters, DFHDFOU will issue did not.
DFHDF6030 and return to z/VSE with a return code of 8, System action: DFHDFOU will continue to validate the
unless a more serious error is detected later. SYSIPT input parameters, without processing the files. After
User response: You will have to correct your SYSIPT data, validating the SYSIPT parameters, DFHDFOU will issue
and resubmit the job. Refer to the CICS Operations and Utilities DFHDF6030 and return to z/VSE with a return code of 8,
Guide for details on coding the input parameters to unless a more serious error is detected later.
DFHDFOU. User response: You will have to correct your SYSIPT data,
Module: DFHDFOU and resubmit the job. Refer to the CICS Operations and Utilities
Destination: SYSLST Guide for details on coding the input parameters to
DFHDFOU.
Module: DFHDFOU
Destination: SYSLST

Destination: SYSLST
DFHDF6010 yyyyddd expected
DFHDFOU determined that the value specified for one of the DFHDF6014 Multiple START parameter found - ignored
yyyyddd values for the DATE parameter was not numeric. Explanation: While processing the SYSIPT input parameters,
System action: DFHDFOU will continue to validate the DFHDFOU determined that there was more than one START
SYSIPT input parameters, without processing the files. After parameter specified.
validating the SYSIPT parameters, DFHDFOU will issue System action: DFHDFOU will continue to validate the
DFHDF6030 and return to z/VSE with a return code of 8, SYSIPT input parameters, without processing the files. After
unless a more serious error is detected later. validating the SYSIPT parameters, DFHDFOU will issue
User response: You will have to correct your SYSIPT data, DFHDF6030 and return to z/VSE with a return code of 8,
and resubmit the job. Refer to the CICS Operations and Utilities unless a more serious error is detected later.
Guide for details on coding the input parameters to User response: You will have to correct your SYSIPT data,
DFHDFOU. and resubmit the job. Refer to the CICS Operations and Utilities
Module: DFHDFOU Guide for details on coding the input parameters to
Destination: SYSLST DFHDFOU.
Module: DFHDFOU
Destination: SYSLST
DFHDF6011 hhmm expected
DFHDFOU determined that the value specified for the hhmm DFHDF6015 Multiple END parameter found - ignored
value specified for the START or END parameter was not Explanation: While processing the SYSIPT input parameters,
numeric. DFHDFOU determined that there was more than one END
System action: DFHDFOU will continue to validate the parameter specified.
and resubmit the job Refer to the CICS Operations and Utilities User response: You will have to correct your SYSIPT data,
Destination: SYSLST
DFHDF6012 cccc expected
Explanation: While processing the SYSIPT input parameters, DFHDF6016 Type value expected
DFHDFOU determined that the value specified for the cccc Explanation: While processing the SYSIPT input parameters,
value for the SID parameter (the system identifier) was not DFHDFOU determined that one of the type values specified in
alphanumeric. Alphanumeric values may contain digits (0 - 9) the list for a TYPE or NOTYPE parameter was not numeric.
or characters (a - z, A -Z). System action: DFHDFOU will continue to validate the
System action: DFHDFOU will continue to validate the SYSIPT input parameters, without processing the files. After
SYSIPT input parameters, without processing the files. After validating the SYSIPT parameters, DFHDFOU will issue
validating the SYSIPT parameters, DFHDFOU will issue DFHDF6030 and return to z/VSE with a return code of 8,
DFHDF6030 and return to z/VSE with a return code of 8, unless a more serious error is detected later.
unless a more serious error is detected later. User response: You will have to correct your SYSIPT data,
User response: You will have to correct your SYSIPT data, and resubmit the job. Refer to the CICS Operations and Utilities
and resubmit the job. Refer to the CICS Operations and Utilities Guide for details on coding the input parameters to
Guide for details on coding the input parameters to DFHDFOU.
DFHDFOU. Module: DFHDFOU
Module: DFHDFOU Destination: SYSLST
Destination: SYSLST
DFHDF6017 Type value too long

DFHDF6013 Multiple DATE parameter found - ignored Explanation: While processing the SYSIPT input parameters,
Explanation: While processing the SYSIPT input parameters, DFHDFOU determined that one of the type values specified in
DFHDFOU determined that there was more than one DATE the list for a TYPE or NOTYPE parameter contained more
parameter specified. than 3 digits. Each value in the list can be up to 3 digits in
System action: DFHDFOU will continue to validate the length.
DFHDFOU.
Module: DFHDFOU

DFHDFOU.
Module: DFHDFOU
DFHDF6018 Type value too large Destination: SYSLST
DFHDFOU determined that one of the type values specified in
the list for TYPE or NOTYPE parameter was greater than 255. DFHDF6022 Days value is less than 1
Valid values are 0 - 255. Explanation: While processing the SYSIPT input parameters,
System action: DFHDFOU will continue to validate the DFHDFOU determined that one of the date values in the
SYSIPT input parameters, without processing the files. After DATE parameter was such that the days portion was less than
validating the SYSIPT parameters, DFHDFOU will issue one.
DFHDFOU.
Module: DFHDFOU
DFHDF6019 Second type value in range smaller than first Destination: SYSLST
type value
DFHDFOU determined that the value specified for the second DFHDF6023 Time value is incorrect length
value in a range of type values was smaller than the first Explanation: While processing the SYSIPT input parameters,
value in the range. DFHDFOU determined that the time value specified in the
System action: DFHDFOU will continue to validate the START or END parameter was not 4 digits long. The
Destination: SYSLST
DFHDF6020 Date value is incorrect length

Explanation: While processing the SYSIPT input parameters, DFHDF6024 Hour value in specified time value is greater
DFHDFOU determined that one of the date values in the than 23
DATE parameter was not 7 digits long. Explanation: While processing the SYSIPT input parameters,
System action: DFHDFOU will continue to validate the DFHDFOU determined that the time values specified in a
SYSIPT input parameters, without processing the files. After START or END parameters was such that the hours portion
validating the SYSIPT parameters, DFHDFOU will issue exceeded 23.
DFHDFOU.
Module: DFHDFOU
DFHDF6021 Days value is greater than 366 Destination: SYSLST
DFHDFOU determined that one of the date values in the
DATE parameter was such that the days portion exceeded 366.
SYSIPT input parameters, without processing the files. After
validating the SYSIPT parameters, DFHDFOU will issue
DFHDF6030 and return to z/VSE with a return code of 8,

Destination: SYSLST
DFHDF6025 Minute value in specified time value is
greater than 59
Explanation: While processing the SYSIPT input parameters, DFHDF6029 OUTDD filename already exists - filename
DFHDFOU determined that the time value specified in a Explanation: While processing the SYSIPT input parameters,
START or END parameters was such that the minutes portion DFHDFOU determined that the OUTDD value filename had
exceeded 59. already been specified, either in an INDD or OUTDD
System action: DFHDFOU will continue to validate the parameter.
SYSIPT input parameters, without processing the files. After System action: DFHDFOU will continue, after discarding this
validating the SYSIPT parameters, DFHDFOU will issue OUTDD parameter. This error does not cause DFHDFOU to
DFHDF6030 and return to z/VSE with a return code of 8, terminate its processing of the files, but a return code of 4 will
unless a more serious error is detected later. be set, which will be passed back to z/VSE on completion of
User response: You will have to correct your SYSIPT data, DFHDFOU, unless a more severe error occurs.
and resubmit the job. Refer to the CICS Operations and Utilities User response: You should remove the duplicate parameter
Guide for details on coding the input parameters to from the SYSIPT data stream. Refer to the CICS Operations and
DFHDFOU. Utilities Guide for details on coding the input parameters to
Destination: SYSLST
DFHDF6026 SID value too long
Explanation: While processing the SYSIPT input parameters, DFHDF6030 Syntax error has been detected. Run aborted.
DFHDFOU determined that the value specified for a SID was Explanation: While processing the SYSIPT input parameters,
greater than 4 characters in length. DFHDFOU has encountered a syntax error which prohibits
System action: DFHDFOU will continue to validate the further processing.
SYSIPT input parameters, without processing the files. After System action: DFHDFOU will now terminate and pass to
validating the SYSIPT parameters, DFHDFOU will issue z/VSE a return code of 8.
DFHDF6030 and return to z/VSE with a return code of 8, User response: This message will be accompanied by earlier
unless a more serious error is detected later. error messages which you should use to determine what the
User response: You will have to correct your SYSIPT data, error was, and to help with correcting the problem.
and resubmit the job. Refer to the CICS Operations and Utilities Module: DFHDFOU
Guide for details on coding the input parameters to Destination: SYSLST
DFHDFOU.
Module: DFHDFOU
Destination: SYSLST DFHDF6031 Open failed for OUTDD filename - filename,
rc = yyyy (decimal)
Explanation: While processing the data, DFHDFOU1 (part of
DFHDF6027 SID value already exists - cccc DFHDFOU) attempted to open file referred to by filename, but
Explanation: While processing the SYSIPT input parameters, received return code yyyy from the open request.
DFHDFOU determined that the SID value cccc had already System action: DFHDFOU1 will continue processing the
been specified. data, but will set a return code of 8 which will be passed to
System action: DFHDFOU will continue, after discarding this z/VSE at the end of the job (unless a higher return code is set
SID value. This error does not cause DFHDFOU to terminate later in the program).
its processing of the files, but a return code of 4 will be set, User response: This message will be accompanied by further
which will be passed back to z/VSE on the completion of informational messages appearing on the system console with
DFHDFOU, unless a more severe error occurs. the prefix DFHEV. Please refer to these messages for further
User response: You should remove the duplicate SID assistance and take any necessary actions.
parameter from the SYSIPT data stream. Refer to the CICS Module: DFHDFOU1
Operations and Utilities Guide for details on coding the input Destination: SYSLST
parameters to DFHDFOU.
Module: DFHDFOU
Destination: SYSLST DFHDF6032 OUTDD filename - filename - is defined as a
VSAM ESDS data set
Explanation: DFHDFOU1 (part of DFHDFOU) has checked
DFHDF6028 INDD filename already exists - filename the VSAM catalog for the file-id referred to by filename and
Explanation: While processing the SYSIPT input parameters, has discovered that the file is defined as an ESDS object. All
DFHDFOU determined that the INDD value filename had output files from DFHDFOU must be either sequential files, or
already been specified, either in an INDD or OUTDD SAM ESDS files.
parameter. System action: DFHDFOU1 will not attempt to open this file
System action: DFHDFOU will continue, after discarding this but will continue processing any other files it can and sets a
INDD parameter. This error does not cause DFHDFOU to return code of 8 which will be passed to z/VSE at the end of
terminate its processing of the files, but a return code of 4 will the job (unless a higher return code is set later in the
be set, which will be passed back to z/VSE on the completion program).
of DFHDFOU, unless a more severe error occurs. User response: There is either:
User response: You should remove the duplicate parameter 1. an error in the JCL, such that the DLBL for filename
from the SYSIPT data stream. Refer to the CICS Operations and references the wrong VSAM object. In this case, you
Utilities Guide for details on coding the input parameters to should correct the JCL and resubmit the job, or
DFHDFOU.
Module: DFHDFOU

2. an error in the definition of the VSAM object referred to by Module: DFHDFOU1

filename. In this case, you should correct the VSAM Destination: SYSLST
definition for the VSAM object and resubmit the job
Module: DFHDFOU1
Destination: SYSLST DFHDF6037 Write failed for OUTDD filename - filename,
exit exit_name was driven
Explanation: While processing the data set filename
DFHDF6033 No DLBL or TLBL found for INDD filename DFHDFOU1 (part of DFHDFOU) attempted to write a record
- filename to the file, and during this process, an error occurred, causing
Explanation: DFHDFOU1 (part of DFHDFOU) has checked the exit exit_name to be driven.
the label area for the file referred to by filename and has System action: DFHDFOU1 will continue processing the
discovered that no DLBL or TLBL for the file exists. data, but will set a return code of 4 which will be passed to
System action: DFHDFOU1 will not attempt to open this file z/VSE at the end of the job (unless a higher return code is set
but will continue processing any other files it can and sets a later in the program).
return code of 8 which will be passed to z/VSE at the end of User response: The exit_name will be either:
the job (unless a higher return code is set later in the v SYNAD - indicating that the SYNAD error has been driven -
program). in this case, this is equivalent to a wrong-length-record or
User response: Ensure that a DLBL or TLBL for filename is end-of-extent. Try defining a larger extent for the file
added to the job stream and resubmit the job. filename and resubmit the job. If the problem persists you
Module: DFHDFOU1 will need help from IBM.
Destination: SYSLST v EODAD - indicating that the EODAD exit has been driven - in
this case, this is equivalent to end-of-data for filename and
should not occur. You need further assistance from IBM to
DFHDF6034 Year less than 1900 resolve this problem. See Part 4 of the CICS Operations and
Explanation: While processing the SYSIPT input parameters, Utilities Guide for guidance on how to proceed.
DFHDFOU determined that one of the values specified for the Module: DFHDFOU1
DATE parameter was such that the year portion was less than Destination: SYSLST
1900.
SYSIPT input parameters, without processing the files. After DFHDF6038 An OUTDD parameter had an error and there
validating the SYSIPT parameters, DFHDFOU will issue was a request to clear an input file. Run
DFHDF6030 and return to z/VSE with a return code of 8, aborted.
unless a more serious error is detected later. Explanation: While processing the SYSIPT input parameters,
User response: You will have to correct your SYSIPT data, DFHDFOU has encountered an error with an OUTDD
and resubmit the job. Refer to the CICS Operations and Utilities parameter. In addition, an INDD parameter has been found
Guide for details on coding the input parameters to with OPTIONS(CLEAR) or OPTIONS(ALL) specified, or no
DFHDFOU. INDD parameter was specified and the default INDD
Module: DFHDFOU parameter is being used - the default is INDD (DUMPIN,
Destination: SYSLST OPTIONS(ALL)).
System action: DFHDFOU will now terminate and pass to
z/VSE a return code of 16.
DFHDF6035 Unable to acquire storage for statistics block User response: You should correct the OUTDD parameter
Explanation: DFHDFOU has attempted to acquire storage to and resubmit the job. Refer to the CICS Operations and Utilities
hold the run-time statistics from the partition GETVIS, but this Guide for details on coding the input parameters to
has failed. DFHDFOU.
System action: DFHDFOU will terminate with return code 16 Module: DFHDFOU
before processing the data. Destination: SYSLST
User response: Increase the size of GETVIS available to the
program by:
1. Running in a larger partition, or DFHDF6039 INDD filename - filename - is defined as a
2. Reducing the SIZE parameter on the // EXEC DFHDFOU VSAM file, but is not ESDS or SAM ESDS
card Explanation: DFHDFOU1 (part of DFHDFOU) has checked
Module: DFHDFOU the VSAM catalog for the file-id referred to by filename and
Destination: SYSLST has discovered that the object is defined as other than ESDS or
SAM ESDS.
System action: DFHDFOU1 will not attempt to open this file
DFHDF6036 No DLBL or TLBL found for OUTDD but will continue processing any other files it can and sets a
filename - filename return code of 8 which will be passed to z/VSE at the end of
Explanation: DFHDFOU1 (part of DFHDFOU) has checked the job (unless a higher return code is set later in the
the label area for the file referred to by filename and has program).
discovered that no DLBL or TLBL for the file exists. User response: There is either:
System action: DFHDFOU1 will not attempt to open this file v an error in the JCL, such that the DLBL for filename
but will continue processing any other files it can and sets a references the wrong VSAM object. In this case, you should
return code of 8 which will be passed to z/VSE at the end of correct the JCL and resubmit the job, or
the job (unless a higher return code is set later in the v an error in the definition of the VSAM object referred to by
program). filename. In this case, you should correct the VSAM
User response: Ensure that a DLBL or TLBL for filename is definition for the VSAM object and resubmit the job
added to the job stream and resubmit the job. Module: DFHDFOU1

DFHDF6040 • DFHDH0004
Destination: SYSLST Module: DFHDFOU1

Destination: SYSLST
DFHDF6040 OUTDD filename - filename - is defined as a

VSAM file, but is not ESDS or SAM ESDS DFHDF6041 Invalid parm statement passed to DFHDFOU.
Explanation: DFHDFOU1 (part of DFHDFOU) has checked Run terminated.
the VSAM catalog for the file-id referred to by filename and Explanation: DFHDFOU was started with a PARM parameter
has discovered that the object is defined as other than ESDS or specified on the EXEC DFHDFOU statement. However, the data
SAM ESDS. passed was of an incorrect format.
System action: DFHDFOU1 will not attempt to open this file System action: DFHDFOU will terminate with a return code
but will continue processing any other files it can and sets a of 16.
return code of 8 which will be passed to z/VSE at the end of User response: You should correct the parm value in the
the job (unless a higher return code is set later in the DFHDFOU JCL and resubmit the job. Refer to the CICS
program). Operations and Utilities Guide for details on coding the parm
User response: There is either: values for DFHDFOU.
v an error in the JCL, such that the DLBL for filename Destination: SYSLST
references the wrong VSAM object. In this case, you should Module: DFHDFOU
correct the JCL and resubmit the job, or
v an error in the definition of the VSAM object referred to by
filename. In this case, you should correct the VSAM
definition for the VSAM object and resubmit the job
DFHDHxxxx messages
DFHDH0001 applid An abend (code aaa/bbbb) has occurred
Modules: DFHDHDH, DFHDHDM, DFHDHSL
Explanation: An abnormal end (abend) or program check has XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
occurred in module modname. This implies that there may be
an error in the CICS code. Alternatively, unexpected data has
been input, or storage has been overwritten. DFHDH0002 applid A severe error (code X'code') has
The code aaa/bbbb is a 3-digit hexadecimal VSE code (if Explanation: An error has been detected in module modname.
applicable), followed by a 4-digit alphanumeric CICS code. The code X'code' is the exception trace point ID which
The VSE code is a system completion code, for example 0C1. uniquely identifies what the error is and where the error was
If an VSE code is not applicable, this field is filled with three detected.
hyphens. The CICS code is an abend code or a number System action: An exception entry (code X'code' in the
referring to a CICS message (for example, AKEA is a CICS message) is made in the trace table. A system dump is taken,
abend code; 1310 refers to message DFHTS1310). unless you have specifically suppressed dumps in the dump
System action: An exception entry is made in the trace table. table.
suppressed dumps in the dump table. CICS continues unless you have specified in the dump table
that CICS should terminate. If appropriate, an error return
CICS continues unless you have specified in the dump table code is sent to the caller of this domain. In this case, CICS
that CICS should terminate. If appropriate, an error return could be terminated by the caller (for example, the domain
code is sent to the caller of this domain. In this case CICS manager, DFHDMDM). A message is issued to this effect.
could be terminated by the caller (for example, the domain
manager, DFHDMDM). A message is issued to this effect. Message DFHME0116 is normally produced containing the
Message DFHME0116 is normally produced containing the User response: This indicates a possible error in CICS code.
symptom string for this problem. The severity of its impact depends on the importance of the
User response: Notify the system programmer. If CICS is still function being executed at the time of the error.
running, it is necessary to decide whether to terminate CICS.
CICS may not have been terminated. If the message occurs
Look up the VSE code, if there is one, in "OS/390 API Abend once and module modname is not crucial to the running of
Codes" in section "VSE/Advanced Functions Codes & SVC your CICS system, you may decide to continue to run and
Errors" of z/VSE Messages and Codes - Volume 1. bring CICS down at a convenient time to resolve the problem.
Next, look up the CICS alphanumeric code. This tells you, for If the message recurs or if you cannot run without the full use
example, whether the error was a program check, an abend, or of module modname, you should bring CICS down in a
a runaway, and may give you some guidance concerning user controlled shutdown.
response.
If module modname is not crucial to the running of your CICS See Part 4 of the CICS Problem Determination Guide for
system, you may decide to continue to run and bring CICS guidance on how to proceed.
down at a convenient time to resolve the problem. If you Destination: Console
cannot run without the full use of module modname you Modules: DFHDHDH, DFHDHDM, DFHDHSL
should bring CICS down in a controlled shutdown.
guidance on how to proceed. DFHDH0004 applid A possible loop has been detected at

DFHDH0100I • DFHDL3927
offset X'offset' in module modname. document domain initialization has completed successfully.
Explanation: A CICS function is taking more time to process System action: System initialization continues.
than CICS expects. A possible loop has been detected in User response: None. The message can be suppressed with
module modname at offset X'offset'. This is the offset of the the system initialization parameter MSGLVL=0.
instruction which was executing at the time the error was Destination: Console
detected. Module: DFHDHDM
System action: An exception entry is made in the trace table.
A system dump is taken, unless you have specifically XMEOUT Parameter: applid
suppressed dumps in the dump table.
CICS continues unless you have specified in the dump table DFHDH0105 date time applid Document template definition
that CICS should terminate. If appropriate, an error return doctemplate has been added as
code is sent to the caller of this domain. In this case CICS {LIBRARY-MEMBER |FILE | PROGRAM |
could be terminated by the caller (for example, the domain TSQUEUE | TDQUEUE |
manager, DFHDMDM). A message is issued to this effect. EXITPGM}(resourcename) with template name
templatename.
Message DFHME0116 is normally produced containing the Explanation: The document template definition doctemplate
symptom string for this problem. has been successfully added to the Document Handler
User response: Notify the system programmer. If CICS has domain. The template definition maps on to one of the
not been terminated, it is necessary to decide whether the following resources named resourcename:
problem is serious enough to bring CICS down. LIBRARY-MEMBER
A member of a z/VSE Sub-Library
Since some CICS functions can use a lot of processor time, this
FILE A CICS file
message may have been caused by a long-running function, so
there may not be an error here. Usually, CICS purges a CICS PROGRAM
function which exceeds the runaway task time interval which A CICS program
you have specified in the ICVR system initialization TSQUEUE
parameter, which is measured in milliseconds. This means that A CICS Temporary Storage queue
module modname in the message is terminated and CICS TDQUEUE
continues. A CICS Transient Data queue
EXITPGM
But if you have specified ICVR=0 you consider that module A User-replaceable program that reads in a template
modname is looping, you must terminate CICS in order to of its own specification.
terminate the runaway function.
If CICS has terminated module modname, and you consider The document template is assigned a template name of
that it was not a runaway, you should increase the ICVR templatename.
system initialization parameter. You can change the System action: The definition is cataloged in the CICS Global
RUNAWAY time interval temporarily using the CEMT Catalog and will be restored on a CICS warm start.
transaction. User response: Application programs can now use the
template using the name templatename.
If raising the ICVR time does not solve the problem, you will
need further assistance from IBM. See Part 4 of the CICS Destination: CSDH
Problem Determination Guide for guidance on how to proceed. Module: DFHDHTM
Destination: Console XMEOUT Parameters: date, time, applid, doctemplate,
Module: DFHDMTM {1=LIBRARY-MEMBER, 2=FILE, 3=PROGRAM, 4=TSQUEUE,
XMEOUT Parameters: applid, X'offset', modname 5=TDQUEUE, 6=EXITPGM}, resourcename, templatename
DFHDH0100I applid Document domain initialization has DFHDH0106 date time applid Document template definition
started. doctemplate has been deleted.
Explanation: This is an informational message indicating that Explanation: The document template definition doctemplate
document domain initialization has started. has been successfully deleted from the Document Handler
System action: System initialization continues. domain.
User response: None. The message can be suppressed with System action: The definition is removed from the CICS
the system initialization parameter MSGLVL=0. Global Catalog and will be not be restored on a CICS warm
Destination: Console start.
Module: DFHDHDM User response: Application programs can no longer use the
XMEOUT Parameter: applid template using the name templatename.
Destination: CSDH
Module: DFHDHTM
DFHDH0101I applid Document domain initialization has
ended. XMEOUT Parameters: date, time,applid, doctemplate
DFHDLxxxx messages
CICS cannot find DFHDLRP in any sublibrary of the LIBDEF
DFHDL3927 applid Program DFHDLRP cannot be found
search chain for the CICS startup job stream.
Explanation: DFHDLRP, the CICS program for DL/I restart,
System action: CICS terminates abnormally with a system
cannot be found.
dump.

DFHDL3928 • DFHDL4543A
User response: To correct this error, make DFHDLRP

DFHDL4540A applid DLI I/O ERROR ON DBD dbdname -
available in one of the sublibraries of the LIBDEF search chain
ABEND requested
for the CICS job.
Explanation: DLI has detected an IO ERROR on database
Module: DFHSII1
dbdname and DLIOER=ABEND has been coded in the SIT.
XMEOUT Parameter: applid System action: CICS is abnormally terminated, if XRF is in
Destination: Console use the standby system is also terminated.
User response: Use off-line DL/I utilities to recover the
database and restart CICS.
DFHDL3928 applid DL/I restart failed Module: DFHJCP
Explanation: The CICS DL/I restart task could not complete
because a necessary step failed. The task has done some XMEOUT Parameter: applid, dbdname
essential recovery operations and has abnormally terminated Destination: Console
itself with abend code ADLH.
System action: CICS writes a transaction dump for the DL/I
DFHDL4541A applid DLI I/O ERROR ON DBD dbdname -
restart task.
database closed
CICS sends two messages to the console, one to identify the Explanation: DLI has detected an IO ERROR on database
error detected by the DL/I restart task, and one, DFHDL3928, dbdname and DLIOER=CONTINUE has been coded in the
to say that the task has failed. A third message follows either SIT.
message to say that CICS has terminated abnormally with a System action: DLI flags the database internally as I/O
dump, or to ask you to reply GO or CANCEL. Depending on error-stopped. This prevents any further access.
the nature of the original error, you may see messages from User response: Use the DLI STOP command to close the
some other system component (for example, an access associated ACB(s) and use the off-line DL/I utilities, or take
method). appropriate recovery action to recover the database. Restart
User response: Use the messages and dumps to find out the the database by using the DLI STRT command.
cause of the failure. Module: DFHJCP
Module: DFHDLRP
XMEOUT Parameter: applid, dbdname
XMEOUT Parameter: applid Destination: Console
DFHDL4542A applid Unable to record Database closed-I/O
DFHDL3929 applid Program DFHDLBP cannot be found - error on Global Catalog
DL/I databases cannot be backed out Explanation: CICS is unable to write database I/O error on
Explanation: DFHDLBP, the CICS program for DL/I backout, the Global Catalog.
cannot be found. System action: CICS is abnormally terminated
User response: Find out why write to catalog has failed
CICS cannot find DFHDLBP in any sublibrary of the LIBDEF (probably an I/O error indicated by other messages) and
search chain for the CICS startup job stream. correct the problem.
System action: CICS terminates abnormally with a dump. Module: DFHJCP
User response: To correct this error, make DFHDLBP
available in one of the sublibraries of the LIBDEF search chain XMEOUT Parameter: applid
for the CICS job. Destination: Console
Module: DFHDLRP
XMEOUT Parameter: applid DFHDL4543A applid Unable to delete database stopped
Destination: Console record in the Global Catalog
Explanation: CICS has encountered an error when accessing
the Global Catalog to delete an I/O error STOP record.
DFHDL3931I W applid DL/I support requested but there are System action: CICS is abnormally terminated.
no Journals defined User response: Find out why the catalog delete operation has
Explanation: The initiated CICS system specifies DL/I failed (probably an I/O error indicated by other messages)
support, but does not define any journals, probably because and correct the problem.
you have specified JCT=NO as a system initialization Module: DFHJCP
parameter.
System action: CICS continues. However, if CICS or a XMEOUT Parameter: applid
transaction fails, CICS does not back out any uncommitted Destination: Console
updates to DL/I databases.
User response: This is a warning message which you can
ignore. If you want to protect the integrity of your DL/I data
bases, terminate CICS, define at least a system log, and restart
CICS.
Module: DFHDLRP

DFHDM0001 • DFHDM0004
DFHDMxxxx messages
DFHDM0001 applid An abend (code aaa/bbbb) has occurred
terminate. This action is taken by DFHDMDM, DFHDMDS
Explanation: An abnormal end (abend) or program check has and DFHDMWQ.
occurred in the module modname. This implies that there may Message DFHME0116 is normally produced containing the
be an error in CICS code. symptom string for this problem.
Alternatively, User response: This indicates a possible error in the CICS
v Unexpected data has been input, or code. You need further assistance from IBM to resolve this
v Storage has been overwritten. problem. See Part 4 of the CICS Problem Determination Guide
The code aaa/bbbb is a three digit hexadecimal VSE code (if Module: DFHDMDM, DFHDMIQ, DFHDMDS, DFHDMWQ
The VSE code is a system completion code, for example 0C1. XMEOUT Parameters: applid, X'code',modname
If a VSE code is not applicable, this field is filled with three Destination: Console
DFHDM0003 applid Insufficient storage to satisfy
GETMAIN (code X'code') in module modname.
Explanation: A CICS GETMAIN was issued by module
modname, but there was insufficient storage available to satisfy
the request.
Either CICS will continue unless you have specified in the
dump table that CICS should terminate. This action will be
identifies the place where the error was detected.
taken by DFHDMIQ.
This error has occurred above the 16Mb line.
Or this is a critical error and CICS is terminated, even if you
(code code in the message). A system dump is taken, unless
you have specifically suppressed dumps in the dump table.
and DFHDMWQ.
Either CICS continues unless you have specified in the dump
table that CICS should terminate. This action is taken by
DFHDMIQ.
User response: Look up the VSE code, if there is one, in
"OS/390 API Abend Codes" in section "VSE/Advanced Or this is a critical error and CICS is terminated, even if you
Functions Codes & SVC Errors" of z/VSE Messages and Codes - have specified in the dump table that CICS should not
Volume 1. terminate. This action is taken by DFHDMDM and
DFHDMWQ.
Then look up the CICS alphanumeric code in “Transaction
Abend Codes (CICS Transaction Server for VSE/ESA)” on Message DFHME0116 is normally produced containing the
page 453. This tells you, for example, whether the error was a symptom string for this problem.
program check, an abend, a runaway or something else and User response: Try increasing the size limits of the DSAs or
may give you some guidance concerning user response. EDSAs. See the CICS System Definition and Operations Guide or
the CICS Performance Guide for further information on CICS
storage.
Module: DFHDMDM, DFHDMIQ, DFHDMWQ
Module: DFHDMDM, DFHDMIQ, DFHDMDS, DFHDMWQ XMEOUT Parameters: applid, X'code',modname
DFHDM0004 applid A possible loop has been detected at
offset X'offset' in module modname.
DFHDM0002 applid A severe error (code X'code') has
module modname at X'offset'. This is the offset of the instruction
The code code is the exception trace point ID which uniquely
which was executing at the time the error was detected.
For further information about CICS exception trace entries, A system dump is taken, unless you have specifically
refer to the CICS Problem Determination Guide. suppressed dumps in the dump table.
System action: An exception entry (code in the message) is
Either CICS continues unless you have specified in the dump
made in the trace table. A system dump is taken, unless you
table that CICS should terminate. This action is taken by
DFHDMIQ.
Either CICS will continue unless you have specified in the
Or this is a critical error and CICS is terminated, even if you
dump table that CICS should terminate. This action will be
taken by DFHDMIQ.
Or, this is a critical error and CICS is terminated, even if you and DFHDMWQ.

DFHDM0005 • DFHDM0104

DFHDM0101I applid CICS is initializing.
Explanation: This message is for information only.
User response: If CICS has not been terminated, it is
necessary to decide whether the problem is serious enough to CICS initialization has started. The domain (DM) manager is
bring CICS down. about to attach an initialization task for each domain defined
in the local CICS catalog, DFHLCD.
Since some CICS functions can use a lot of CPU time, this System action: Processing continues.
message may have been caused by a long-running function. So User response: None. You can suppress this message with
there may not be an error here. Usually, CICS purges a CICS the system initialization parameter, MSGLVL=0.
function which exceeds the runaway task time interval which Module: DFHDMDM
you have specified on the ICVR system initialization
parameter (ICVR is measured in milliseconds). This means XMEOUT Parameter: applid
that the module modname is terminated and CICS continues. Destination: Console
But if you have declared ICVR=0 in the SIT and you consider
that module modname has gone into a loop, you have to DFHDM0102I applid CICS is quiescing.
terminate CICS in order to terminate the runaway function. Explanation: This message is for information only.
The controlled shutdown of CICS has started. The domain
If CICS has terminated module modname and you consider
(DM) manager is about to attach a quiesce task for each CICS
that it was not a runaway, you should increase the ICVR time
component.
interval. You have to bring CICS down at a suitable time to do
this permanently. But you can change the ICVR time interval
temporarily online, using the CEMT transaction. the SIT parameter, MSGLVL=0.
If raising the ICVR time does not solve the problem, you will Module: DFHDMDM
need further assistance from IBM to resolve the problem. See XMEOUT Parameter: applid
Part 4 of the CICS Problem Determination Guide for guidance on Destination: Console
how to proceed.
Module: DFHDMDM, DFHDMIQ, DFHDMDS, DFHDMWQ
DFHDM0103 applid Unsuccessful quiesce of domain domain.
XMEOUT Parameters: applid, X'offset', modname CICS will terminate.
Destination: Console Explanation: A domain has failed to quiesce.
System action: CICS terminates. An exception trace and a
dump are issued by the domain in error.
DFHDM0005 applid A hardware error has occurred (module
modname, code X'code'). The Time-of-Day clock Message DFHME0116 is normally produced containing the
is invalid. symptom string for this problem.
Explanation: A hardware error has occurred during the User response: You need further assistance from IBM to
running of module modname. The time-of-day clock facility is resolve this problem. See Part 4 of the CICS Problem
the timing mechanism for the operating system. Determination Guide for guidance on how to proceed.
Module: DFHDMDS
The code code is the exception trace point id which uniquely
identifies the place where the error was detected. XMEOUT Parameters: applid, domain
System action: An exception entry (code code in the message) Destination: Console
is made in the trace table. A dump is taken, unless you have
specifically suppressed dumps in the dump table. DFHDM0104 applid Unsuccessful load of program domain.
This is a critical error and CICS is terminated, even if you CICS will terminate.
have specified in the dump table that CICS should not Explanation: The domain (DM) manager has called the
terminate. loader to load a program for an initialization task but the load
has failed. Either the module was not found in any sublibrary
Message DFHME0116 is normally produced containing the of the LIBDEF search chain for the CICS job, or if the module
symptom string for this problem. name given in the message is not a legitimate CICS module,
User response: This is in all probability a hardware error and the CICS catalog could be corrupted.
you should in the first instance investigate the store clock and System action: CICS terminates. A system dump with dump
find out whether it is working properly. If this is the cause, code DM0104 is taken unless you have suppressed dumps in
you should take the appropriate action to have it repaired or the dump table.
replaced. An exception trace is issued by the domain manager. Message
In the unlikely event that this is not a hardware problem, you DFHME0116 is normally produced containing the symptom
need further assistance from IBM to resolve the problem. See string for this problem.
Part 4 of the CICS Problem Determination Guide for guidance on
how to proceed.
Module: DFHDMDM, DFHDMWQ, DFHDMDS
Module: DFHDMDM
XMEOUT Parameters: applid, modname,X'code'
XMEOUT Parameters: applid, domain

DFHDM0105 • DFHDS0002
example, the domain manager records may not be present.

DFHDM0105 applid Unsuccessful initialization of domain
domain. CICS will terminate. This message may follow message DFHDM0002.
Explanation: A domain has failed to initialize. System action: This is a critical error and CICS terminates,
System action: CICS terminates. even if you have specified in the dump table that CICS should
not terminate.
Diagnostics are issued by the domain in error. Message
DFHME0116 is normally produced containing the symptom A system dump is taken, unless you have specifically
string for this problem. suppressed dumps in the dump table.
User response: Review the diagnostics and take remedial
action for any installation-related problems. See Part 4 of the Message DFHME0116 is normally produced containing the
CICS Problem Determination Guide for guidance on how to symptom string for this problem.
proceed. User response: Try reinitializing the local CICS catalog,
Module: DFHDMDS DFHLCD, using DFHCCUTL, and cold start CICS.
XMEOUT Parameters: applid, domain If this does not solve the problem, you will need further
Destination: Console assistance from IBM. See Part 4 of the CICS Problem
Module: DFHDMDM
DFHDM0106 applid The Domain Manager records on the
CICS Catalog may have been corrupted. XMEOUT Parameter: applid
Explanation: A problem was detected when calling the CICS Destination: Console
catalog to browse the domain (DM) manager records. For
DFHDSxxxx messages
DFHDS0001 applid An abend (code aaa/bbbb) has occurred
occurred in module modname. This implies that there may be DFHDS0002 applid A severe error (code X'code') has
an error in CICS code. Alternatively, unexpected data has been
input, or storage has been overwritten.
The code aaa/bbbb is a three digit hexadecimal VSE code (if The code X'code' is the exception trace point ID which
applicable), followed by a four digit alphanumeric CICS code. uniquely identifies what the error is and where the error was
The VSE code is a system completion code, for example 0C1. detected. For further information about CICS exception trace
If a VSE code is not applicable, this field is filled with three entries, see the CICS Problem Determination Guide.
hyphens. The CICS code is an abend code or a number System action: An exception entry (code code in the message)
referring to a CICS message (for example, AKEA is a CICS is made in the trace table. If code is X'0056', CICS takes a
abend code; 1310 refers to message DFHTS1310). kernel domain system dump, which is not suppressible.
System action: An exception entry is made in the trace table. Otherwise, CICS takes a normal system dump, unless you
A system dump is taken, unless you have specifically have specifically suppressed dumps in the dump table.
suppressed dumps in the dump table. CICS continues unless
you have specified in the dump table that CICS should Either CICS will continue unless you have specified in the
terminate. dump table that CICS should terminate.
Message DFHME0116 is normally produced containing the If appropriate, an error return code is sent to the caller of this
symptom string for this problem. domain. In this case, CICS could be terminated by the caller
User response: If CICS is still running, it is necessary to (for example, the domain manager, DFHDMDM). A message
decide whether to terminate CICS. will be issued to this effect.
1. Look up the VSE code, if there is one, in "OS/390 API
Abend Codes" in section "VSE/Advanced Functions Codes Or this is a critical error and CICS is terminated, even if you
& SVC Errors" of z/VSE Messages and Codes - Volume 1. have specified in the dump table that CICS should not
2. Next, look up the CICS alphanumeric code in “Transaction terminate.
Abend Codes (CICS Transaction Server for VSE/ESA)” on The system action taken depends on the context.
page 453. This tells you, for example, whether the error
was a program check, an abend, or a runaway, and may Message DFHME0116 is normally produced containing the
give you some guidance concerning user response. symptom string for this problem.
3. If module modname is not crucial to the running of your User response: Inform the system programmer. This indicates
CICS system, you may decide to continue to run and bring a possible error in CICS code. The severity of its impact will
CICS down at a convenient time to resolve the problem. depend on the importance of the function being executed at
4. If you cannot run without the full use of module modname the time of the error.
you should bring CICS down in a controlled shutdown.
CICS may not have been terminated.
If the message occurs once and module modname is not crucial
to the running of your CICS system, you may decide to
continue to run and bring CICS down at a convenient time to
Module: DFHDSAT, DFHDSBR, DFHDSDM, DFHDSDS2,
resolve the problem.
DFHDSDS3, DFHDSDS4, DFHDSIT, DFHDSKE, DFHDSSM,
DFHDSSR, DFHDSST, DFHDSTCB, DFHDSUE If the message recurs or if you cannot run without the full use

DFHDS0003 • DFHDS0005
of module modname, you should bring CICS down in a

DFHDS0004 applid A possible loop has been detected at
controlled shutdown.
You need further assistance from IBM to resolve this problem. Explanation: A CICS function is taking more time to process
See Part 4 of the CICS Problem Determination Guide for than CICS expects. A possible loop has been detected in
guidance on how to proceed. module modname at offset X'offset'. This is the offset of the
instruction which was executing at the time the error was
Note: When code is X'0056', this message cannot be detected.
manipulated by the Global User exit XMEOUT. System action: An exception entry is made in the trace table.
Module: DFHDSAT, DFHDSBR, DFHDSDM, DFHDSDS2, A system dump is taken, unless you have specifically
DFHDSDS3, DFHDSDS4, DFHDSIT, DFHDSKE, DFHDSSM, suppressed dumps in the dump table. CICS will continue
DFHDSSR, DFHDSST, DFHDSTCB, DFHDSUE unless you have specified in the dump table that CICS should
terminate. Message DFHME0116 is normally produced
XMEOUT Parameters: applid, X'code',modname containing the symptom string for this problem.
Destination: Console User response: Inform the system programmer. If CICS has
not been terminated, it will be necessary to decide whether the
problem is serious enough to bring CICS down.
DFHDS0003 applid Insufficient storage (code X'code') in
module modname. Since some CICS functions can use a lot of CPU time, this
Explanation: A CICS GETMAIN was issued by module message may have been caused by a long-running function. So
modname but there was insufficient storage available to satisfy there may not be an error here. Usually, CICS will purge a
the request. CICS function which exceeds the runaway task time interval
which you have specified on the ICVR system initialization
The code X'code' is the exception trace point id which
parameter (ICVR is measured in milliseconds). This means
that module module will be terminated and CICS will continue.
This error has occurred above the 16MB line.
System action: An exception entry is made in the trace table But if you have declared ICVR=0 and you consider that
(code code in the message). A system dump is taken, unless module modname has gone into a loop, you will have to
you have specifically suppressed dumps in the dump table. terminate CICS in order to terminate the runaway function.
table that CICS should terminate. If CICS has terminated module modname, and you consider
If appropriate, an error return code is sent to the caller of this interval. You will have to bring CICS down at a suitable time
domain. In this case, CICS could be terminated by the caller to do this permanently. But you can change the ICVR time
(for example, the domain manager, DFHDMDM). A message interval temporarily online, using the CEMT transaction.
will be issued to this effect.
Message DFHME0116 is normally produced containing the need further assistance from IBM. See Part 4 of the CICS
symptom string for this problem. Problem Determination Guide for guidance on how to proceed.
User response: Inform the system programmer. If CICS has Module: DFHDSAT, DFHDSBR, DFHDSDM, DFHDSDS2,
been terminated by another module, look out for the relevant DFHDSDS3, DFHDSDS4, DFHDSIT, DFHDSKE, DFHDSSM,
termination messages (from, for example, the domain DFHDSSR, DFHDSST, DFHDSTCB, DFHDSUE
manager), and look up the user response suggested for these
messages. XMEOUT Parameters: applid, X'offset', modname
If CICS is still running, the problem may be a temporary one
which will right itself if more storage becomes available. If
you can manage without module modname, you may decide to DFHDS0005 applid A hardware error has occurred (code
continue and bring CICS down at a convenient time to resolve X'code', module modname). The Time-of-Day
the problem. If the message recurs or if you cannot run clock is invalid.
without the full use of all CICS modules, you should bring Explanation: A hardware error has occurred during the
CICS down in a controlled shutdown. running of module module. The store clock facility is the
timing mechanism for the operating system.
Try increasing the overall size limits of the DSAs or EDSAs. If
CICS is not already terminated, you will need to bring CICS The code X'code' is the exception trace point ID which
down to do this. See the CICS System Definition Guide or the uniquely identifies the place where the error was detected.
CICS Performance Guidefor more information on CICS storage. System action: An exception entry (code code in the message)
is made in the trace table. A system dump is taken, unless you
You may need further assistance from IBM to fully resolve this have specifically suppressed dumps in the dump table. This is
problem. See Part 4 of the CICS Problem Determination Guide a critical error and CICS is terminated, even if you have
for guidance on how to proceed. specified in the dump table that CICS should not terminate.
Module: DFHDSBR
XMEOUT Parameters: applid, X'code',modname symptom string for this problem.
Destination: Console User response: Inform the system programmer. This is in all
probability a hardware error and you should in the first
instance investigate the store clock and find out whether it is
working properly. If this is the cause, you should take the
appropriate action to have it repaired or replaced.

DFHDS0006 • DFHDU0001
will need further assistance from IBM. See Part 4 of the CICS continue and bring CICS down at a convenient time to resolve
Problem Determination Guide for guidance on how to proceed. the problem. If the message recurs or if you cannot run
Module: DFHDSTCB without the full use of all CICS modules, you should bring
CICS down in a controlled shutdown.
Destination: Console You can get diagnostic information about the VSE return code
from the "OS/390 API Return Codes" in section
"VSE/Advanced Functions Codes & SVC Errors" of z/VSE
DFHDS0006 applid Insufficient storage to satisfy Messages and Codes - Volume 1.
VSE code vsecode. Try decreasing the overall size limits of the DSAs or EDSAs.
Explanation: A CICS GETMAIN request was issued by Or, try increasing the size of the CICS partition, if it is not
module modname but there was insufficient storage available. already at maximum size. If CICS is not already terminated,
you will need to bring CICS down to do this. See the CICS
The code code is the exception trace point ID which uniquely System Definition and Operations Guide or the CICS Performance
identifies the place where the error was detected. Guide for more information on CICS storage.
This error may occur either above or below the 16MB line. You may need further assistance from IBM to fully resolve this
This depends on context. problem. See Part 4 of the CICS Problem Determination Guide
System action: An exception entry is made in the trace table for guidance on how to proceed.
(code code in the message). A system dump is taken, unless Module: DFHDSAT, DFHDSDM, DFHDSDS2, DFHDSSR
you have specifically suppressed dumps in the dump table.
XMEOUT Parameters: applid, X'code',modname, vsecode
Either CICS will continue unless you have specified in the Destination: Console
dump table that CICS should terminate.
If appropriate, an error return code is sent to the caller of this DFHDS0101 applid Dispatcher cannot enable the CICS
domain. In this case, CICS could be terminated by the caller post exit.
(for example, the domain manager, DFHDMDM). A message Explanation: The dispatcher has been unable to to enable the
will be issued to this effect. CICS post-exit. This is probably because the CICS post-exit
Or this is a critical error and CICS is terminated, even if you stub is not in the SVA.
have specified in the dump table that CICS should not System action: An exception entry is made in the trace table.
terminate. A system dump is taken, unless you have specifically
The system action depends on the context.
Message DFHME0116 is normally produced containing the have specified in the dump table that CICS should not
symptom string for this problem. terminate.
User response: Inform the system programmer. If CICS has
been terminated by another module, look out for the relevant Message DFHME0116 is normally produced containing the
termination messages (from, for example, the domain symptom string for this problem.
manager), and look up the user response suggested for these User response: Ensure that the CICS post-exit stub
messages. (DFHDSPEX) is in the SVA.
Module: DFHDSDM
which will right itself if more storage becomes available. If XMEOUT Parameter: applid
you can manage without module modname, you may decide to Destination: Console
DFHDUxxxx messages
you have specified in the dump table that CICS should
DFHDU0001 applid An abend (code aaa/bbbb) has occurred
terminate.
Explanation: An abnormal end (abend) or program check has For module DFHDUTM, a system dump is taken. This dump
occurred in module modname. This implies that there may be cannot be suppressed. CICS processing continues.
input, or storage has been overwritten. For module DFHDUDU, a system dump is taken. This dump
cannot be suppressed.
The code aaa/bbbb is a three digit hexadecimal VSE code (if
applicable), followed by a four digit alphanumeric CICS code. CICS processing continues.
The VSE code is a system completion code, for example 0C1. For other modules, a system dump is taken.
If an VSE code is not applicable, this field is filled with three
hyphens. The CICS code is an abend code or a number CICS processing continues.
abend code; 1310 refers to message DFHTS1310). Message DFHME0116 is normally produced containing the
System action: An exception entry is made in the trace table. symptom string for this problem.
User response: Notify the system programmer. If CICS is still
For module DFHDUDT, a system dump is taken unless you running, it is necessary to decide whether to terminate CICS.
have specifically suppressed the dumps (by a user exit
program at the XDUREQ exit, in the dump table or by global Look up any VSE code in the "OS/390 API Abend Codes" in
system dump suppression). CICS processing continues unless section "VSE/Advanced Functions Codes & SVC Errors" of
z/VSE Messages and Codes - Volume 1.

DFHDU0002 • DFHDU0004
Then look up the CICS alphanumeric code in “Transaction If the error occurred in modules DFHDUDT or DFHDUTM,
Abend Codes (CICS Transaction Server for VSE/ESA)” on the dump table may not be available. Therefore, any EXEC
page 453. This tells you, for example, whether the error was a API commands relating to dump codes may fail and any
program check, an abend, a runaway or a recovery dumps taken may be processed using default information (for
percolation, and may give you some guidance concerning user example, whether to terminate CICS or not) rather than
response. information you may have put on the dump table for specific
dump codes.
If module modname is not crucial to the running of your CICS
system, you may decide to continue to run and bring CICS You need further assistance from IBM to resolve this problem.
down at a convenient time to resolve the problem. See Part 4 of the CICS Problem Determination Guide for
If you cannot run without the full use of module modname, Module: DFHDUDT, DFHDUTM
If the abend occurred in modules DFHDUDT or DFHDUTM, Destination: Console
the dump table is not available. Therefore, any EXEC API
commands relating to dump codes fail and any dumps taken
are processed using default information (for example, whether DFHDU0004 applid A possible loop has been detected at
to terminate CICS or not) rather than information you may offset X'offset' in module modname.
have put on the dump table for specific dump codes. Explanation: A CICS function is taking more time to process
instruction which happened to be executing at the time when
the error was detected.
Module: DFHDUDT, DFHDUTM, DFHDUDU, DFHDUXD,
DFHDUIO, DFHDUSU, DFHDUXW, DFHPCXDF, DFHSAXDF,
DFHXDXDF, DFHXRXDF, DFHTCXDF, DFHTRXDF, For module DFHDUDT, a system dump is taken unless you
DFHFCXDF have specifically suppressed the dumps (by a user exit
program at the XDUREQ exit, in the dump table or by global
system dump suppression). CICS processing continues unless
you have specified in the dump table that CICS should
terminate.
DFHDU0002 applid A severe error (code X'code') has For module DFHDUTM, a system dump is taken. This dump
occurred in module modname. cannot be suppressed. CICS processing continues.
The code code is the exception trace point ID which uniquely Message DFHME0116 is normally produced containing the
identifies what the error is and where the error was detected. symptom string for this problem.
For further information about CICS exception trace entries, User response: Notify the system programmer. If CICS has
refer to the CICS Problem Determination Guide. not been terminated, it will be necessary to decide whether the
System action: An exception entry (code code in the message) problem is serious enough to bring CICS down.
is made in the trace table.
Since some CICS functions can use a lot of CPU time, this
For module DFHDUDT, a system dump is taken unless you message may have been caused by a long-running function. So
have specifically suppressed the dumps (by a user exit there may not be an error here. Usually, CICS will purge a
program at the XDUREQ exit, in the dump table or by global CICS function which exceeds the runaway task time interval
system dump suppression). CICS processing continues unless which you have specified on the ICVR system initialisation
you've specified in the dump table that CICS should parameter (ICVR is measured in milliseconds). This means
terminate. that module modname will be terminated and CICS will
continue.
For module DFHDUTM, a system dump is taken. This dump
cannot be suppressed. CICS processing continues. If you have declared ICVR=0 and you consider that module
modname has gone into a loop, you will have to terminate
If appropriate, an error return code is sent to the caller of this CICS in order to terminate the runaway function.
domain. In this case, CICS could be terminated by the caller. A
message will be issued to this effect. If CICS has terminated module modname, and you consider
Message DFHME0116 is normally produced containing the interval. You will have to bring CICS down at a suitable time
symptom string for this problem. to do this permanently. But you can change the ICVR time
User response: Inform the system programmer. This indicates interval temporarily online, using the CEMT transaction.
a possible error in CICS code. The severity of its impact will
depend on the importance of the function being executed at If raising the ICVR time does not solve the problem, you will
the time of the error. need further assistance from IBM. See Part 4 of the CICS
CICS may not have been terminated. Module: DFHDUDT, DFHDUTM, DFHDUXD, DFHDUIO,
If the message occurs once and module modname is not crucial DFHDUSU, DFHDUXW, DFHPCXDF, DFHSAXDF,
to the running of your CICS system, you may decide to DFHXDXDF, DFHXRXDF, DFHTCXDF, DFHTRXDF,
continue to run and bring CICS down at a convenient time to DFHFCXDF
resolve the problem. XMEOUT Parameters: applid, X'offset', modname
If the message recurs or if you cannot run without the full use Destination: Console
of module modname you should bring CICS down in a

DFHDU0006 • DFHDU0203I

DFHDU0006 applid Insufficient storage to satisfy Getmain
(code X'code') in module modname. VSE code
vsecode.
Module: DFHDUDU
Explanation: A OS/390 GETMAIN was issued by module
modname, but there was insufficient storage available to satisfy XMEOUT Parameter: applid
the request. Destination: Console
uniquely identifies the place where the error was detected. DFHDU0201 applid About to take SDUMP. Dumpcode:
This error has occurred above the 16M line. dumpcode, Dumpid: dumpid.
The code vsecode is the OS/390 GETMAIN return code. Explanation: An error, possibly signaled by a previous
System action: An exception entry is made in the trace table message, has caused a call to the CICS dump (DU) domain.
(code code in the message) and a system dump is taken. This The dump domain issues this message immediately before
dump cannot be suppressed. CICS processing continues. calling the VSE SDUMP facility if the following conditions are
User response: Inform the system programmer. If CICS has satisfied:
been terminated by another module, look out for the relevant v The system initialization parameter, DUMP=YES, for
termination messages (from, for example, the domain SDUMPS has been specified.
manager), and look up the user response suggested for these v The dump table entry for dump code dumpcode specifies
messages. that a system SDUMP is required.
v The maximum dump limit for this dump code in the dump
If CICS is still running, the problem may be a temporary one table entry has not been exceeded.
which will right itself if more storage becomes available. If v The user exit XDUREQ does not suppress the taking of this
you can manage without module modname, you may decide to dump.
continue and bring CICS down at a convenient time to resolve
the problem. If the message recurs or if you cannot run
without the full use of all CICS modules, you should bring The dump code dumpcode is an 8-character system dump code
CICS down in a controlled shutdown. identifying the CICS problem. However some of these
characters may be blanks. A system dump code is a CICS
As the problem is in module DFHDUTM, EXEC API message number with the DFH prefix removed.
commands for browsing the dump tables may not work, or
additions to the dump tables may not work. The dumpid is the unique 9-character string identifying this
You can get diagnostic information about the OS/390 dump.
GETMAIN return code in "OS/390 API Return Codes" in System action: When the dump is complete, message number
section "VSE/Advanced Functions Codes & SVC Errors" of DFHDU0202 is issued.
z/VSE Messages and Codes - Volume 1. User response: Inform the system programmer, who should
refer to the CICS message indicated by dumpcode to resolve the
Try decreasing the size limit of the DSAs or EDSAs. Or, try problem.
increasing the size of the CICS partition, if it is not already at
Module: DFHDUDU
maximum size. If CICS is not already terminated, you need to
bring CICS down to do this.
Module: DFHDUTM
Destination: Console DFHDU0202 applid SDUMP complete.
Explanation: This message is issued on successful completion
DFHDU0102 applid DFHDUIO could not be loaded. of an SDUMP.
Transaction dump is inoperative. System action: Processing continues unless a CICS shutdown
Explanation: CICS could not locate module DFHDUIO is requested by either the dump table entry for this dump or
during initialization. the dump call to the dump (DU) domain.
System action: An exception trace entry is produced, and User response: Print off the system dump if required. A
CICS continues with the transaction dump facility inoperative. previous VSE message identifies the SYSDUMP library name
and which member of the SYSDUMP library contains the
Message DFHME0116 is normally produced containing the dump.
symptom string for this problem. Module: DFHDUDU
User response: Use the exception trace entry and any other Destination: Console
relevant messages to determine why module DFHDUIO was
not available.
Module: DFHDUDM DFHDU0203I date time applid A transaction dump was taken
XMEOUT Parameter: applid for dumpcode: dumpcode, Dumpid: dumpid.
Destination: Console Explanation: A CICS transaction has abnormally terminated,
possibly signaled by a previous message, and the CICS dump
(DU) domain has taken a transaction dump.
DFHDU0103 applid An abend has occurred during
initialization of dump domain in module The dump code dumpcode is normally the 4-character CICS
DFHDUDM. transaction abend code if the dump was requested as a result
Explanation: A dump domain has failed to initialize. of a transaction abend. It may also be the value of the
System action: CICS terminates. DUMPCODE operand on an EXEC CICS DUMP
TRANSACTION request.
An exception trace and a kernel dump are issued by the dump
domain. Message DFHME0116 is normally produced The dump ID dumpid is the unique 9-character string
containing the symptom string for this problem. identifying this dump

DFHDU0205 • DFHDU0210
System action: A transaction dump is written to the current v If the user exit, XDUREQ, has suppressed the dump, either
CICS dump data set, either DFHDMPA or DFHDMPB. inactivate this exit, or as a more permanent measure, change
the user exit program so that it does not suppress the
CICS may terminate if the dump table entry for the specified dump.
abend code specifically requests it. v If the dump table has suppressed the dump, use CEMT or
User response: Print off the transaction dump if required. CECI to browse and update the dump table entry for dump
Module: DFHDUDU code dumpcode.
XMEOUT Parameters: date, time,applid, dumpcode, dumpid Module: DFHDUDU
Destination: CDUL XMEOUT Parameters: date, time,applid, dumpcode, reason
Destination: CDUL
DFHDU0205 applid A system dump for dumpcode:
dumpcode was suppressed by the reason. DFHDU0207I date time applid Transaction and system dumps
Explanation: An error, possibly signaled by a previous for dumpcode: dumpcode were suppressed by
message, has caused a call to the CICS (DU) dump domain, the reason.
which failed to take a system dump for reason reason. Reason Explanation: A CICS transaction has abnormally terminated,
reason indicates what has caused dump suppression. possibly signaled by a previous message, and the CICS dump
v The XDUREQ user exit. (DU) domain has failed to take a transaction dump nor a
v The dump table option for dump code dumpcode. system dump for reason reason. Reasons reason indicates what
v The global system dump suppression option. caused dump suppression.
v XDUREQ user exit.
The dump code dumpcode is an 8-character system dump code v Dump table option for this dump code.
identifying the CICS problem. However some of these
characters may be blanks. A system dump code is a CICS The dump code dumpcode is the 4-character CICS transaction
message number with the DFH prefix removed. abend code.
System action: A system dump is not produced. However, System action: Neither a transaction nor a system dump is
CICS will be terminated if the dump table entry for this dump produced. However, CICS is terminated if the dump table
code or the caller of the dump domain requests CICS entry for this dump code or the caller of the dump domain
termination. specifically requests such.
User response: If a system dump is required for this dump User response: If a transaction dump and/or a system dump
code, perform the user action appropriate to the reason reason is required for this dump code, perform the user action
given in the message. appropriate to the reason reason given in the message:
v If the user exit XDUREQ has suppressed the dump, either v If the user exit XDUREQ has suppressed the dump, either
inactivate this exit, or as a more permanent measure change inactivate this exit, or, as a more permanent measure
the user exit program not to suppress the dump. change, the user exit program so it does not suppress the
v If the dump table has suppressed the dump, use CEMT or dump.
CECI to browse and update the dump table entry for dump v If the dump table has suppressed the dump, use CEMT or
code dumpcode. CECI to browse and update the dump table entry for this
v If the global system dump suppression option has dump code.
suppressed the dump, specify the system initialization Module: DFHDUDU
parameter DUMP=YES to allow future system dumps to be
taken. XMEOUT Parameters: date, time,applid, dumpcode, reason
Module: DFHDUDU Destination: CDUL
DFHDU0210 applid SDUMPX REQUEST FAILED - reason.

DFHDU0206I date time applid A transaction dump for Explanation: A VSE SDUMPX request from CICS signaled by
dumpcode: dumpcode was suppressed by the message DFHDU0201 has failed to complete successfully. The
reason. possible reasons, (reason) for the failure are as follows:
Explanation: A CICS transaction has abnormally terminated, SDUMPX RETURN CODE X'nn' ONLY PARTIAL DUMP.
possibly signaled by a previous message, and the CICS dump The number of storage areas to be dumped exceeds
(DU) domain has failed to take a transaction dump for the the maximum allowed for one SDUMPX request.
reason reason. Reasons reason indicates the reason for dump SDUMPX RETURN CODE X'nn' REASON X'mm' NO
suppression. SYSDUMP LIBRARY AVAILABLE
v XDUREQ user exit. No SYSDUMP library is defined for the CICS job. If
v Dump table option for this dump code. the VSE SYSDUMPC job control option is in effect
then the dump will be suppressed, otherwise the
The dump code dumpcode is the 4-character CICS transaction dump will be redirected to SYSLST.
abend code. SDUMPX RETURN CODE X'nn' REASON X'mm'
System action: A transaction dump is not produced. SYSDUMP LIBRARY IS FULL
However, CICS is terminated if the dump table entry for this The SYSDUMP library defined for the CICS job is
dump code or the caller of the dump domain specifically full. If the SYSDUMPC job control option is in effect
requests such. then the dump will be suppressed, otherwise the
User response: If a transaction dump is required for this dump will be redirected to SYSLST.
dump code, perform the user action appropriate to the reason SDUMPX RETURN CODE X'nn' REASON = X'mm'
reason given in the message. VSE has rejected the SDUMPX request for some

DFHDU0211 • DFHDU0302I
other reason than those listed above. X'nn' gives the

DFHDU0211 applid THE XDUREQ USER EXIT IS NOT
SDUMPX return code and X'mm' gives the SDUMPX
CALLED FOR DUMPCODE dumpcode.
reason code.
Explanation: Because of a severe system error, the XDUREQ
NOT AUTHORIZED IN CICS
user exit (which allows you to suppress system dumps) has
SDUMPX is not authorized for this CICS run.
not been called for system dump dumpcode.
INSUFFICIENT STORAGE
System action: The XDUREQ user exit is not called.
CICS issued a OS/390 GETMAIN for storage during
the processing of the SDUMPX request. The OS/390 DFHDU0211 is followed either by message DFHDU0201,
GETMAIN has been rejected by VSE. indicating that dump dumpcode was taken, or by message
DFHDUSVC FESTAE FAILED. FESTAE RETURN CODE DFHDU0205, indicating that dump dumpcode was suppressed.
X'nn' CICS issued a OS/390 FESTAE request from Message DFHDU0201 or DFHDU0205 is followed by message
DFHDUSVC during the processing of the SDUMPX DFHDU0309 if CICS terminates.
request. The request has been rejected by VSE.
System action: CICS proceeds as if the dump had been The XDUREQ user exit is called for subsequent system
successful. dumps.
User response: The user response depends on the reason, User response: You need further assistance from IBM to
(reason), for the failure. resolve this problem. See Part 4 of the CICS Problem
SDUMPX RETURN CODE X'nn' ONLY PARTIAL DUMP. Determination Guide for guidance on how to proceed.
Use the return code to determine why a partial Module: DFHDUDU
dump was taken. See the z/VSE System Macros Destination: Console
Reference manual for an explanation of the SDUMPX
return code X'nn'. DFHDU0212 applid Requested transaction dump code
SDUMPX RETURN CODE X'nn' REASON X'mm' NO dumpcode is invalid.
SYSDUMP LIBRARY AVAILABLE Explanation: A requested transaction dump code has
Define a SYSDUMP library for the CICS job and unprintable characters, or has leading or imbedded blanks.
then cause the SDUMP request to be reissued. See System action: A transaction dump is produced unless
the z/VSE Diagnosis Tools manual for a description of suppressed by the user exit XDUREQ. However, no dump
how to define a SYSDUMP library. statistics are committed. The transaction dump is complete
SDUMPX RETURN CODE X'nn' REASON X'mm' when message DFHDU0203 is issued. The invalid dump code
SYSDUMP LIBRARY IS FULL is shown in dump domain (DU) trace points X'0600' and
Clear some dumps from the dump library and cause X'0601'.
the SDUMP to be reissued. See the z/VSE Diagnosis User response: Print off the transaction dump and determine
Tools manual for a description of how to delete or how an abend or EXEC CICS request was issued with an
offload a dump from the SYSDUMP library. invalid dump code.
SDUMPX RETURN CODE X'nn' REASON X'mm' Module: DFHDUDU
No action is required if the dump was suppressed
deliberately. If the dump has failed because of an XMEOUT Parameters: applid, dumpcode
error in the SDUMPX routine, use the return code to Destination: Console
fix the error and then cause the SDUMPX request to
be reissued. See the z/VSE System Macros Reference
manual for an explanation of the SDUMPX return DFHDU0302I applid Transaction Dump Data set dataset to be
code X'nn' and reason code X'mm' closed due to text-descr
NOT AUTHORIZED IN CICS Explanation: This message is output when attempting to
This reason is unlikely to occur because SDUMPX is write a record to the transaction dump data set. text-descr is
unconditionally authorized during CICS one of the following:
initialization, and should be authorized throughout v I/O ABEND
the CICS run. If you do get this reason, the CICS v TASK TIMEOUT
AFCB (authorized function control block) has v TASK CANCEL
probably been accidentally overwritten. System action: None unless text-descr is I/O ABEND, in
INSUFFICIENT STORAGE which case an exception entry is made in the trace table and a
Ensure sufficient partition storage is available for system dump is taken.
OS/390 GETMAIN requests. User response: Notify the system programmer.
DFHDUSVC FESTAE FAILED. FESTAE RETURN CODE In the case of I/O ABEND, there is normally an accompanying
X'nn' Use the return code to determine why the OS/390 VSE error message to help identify the problem with the data
FESTAE failed and then cause the SDUMPX request set.
to be reissued. See "OS/390 API Return Codes" in
section "VSE/Advanced Functions Codes & SVC If the problem is not due to a major corruption of CICS,
Errors" of z/VSE Messages and Codes - Volume 1 for an successful switching of dump data sets will reinstate the
explanation of the OS/390 FESTAE return code. transaction dump environment. Otherwise, the transaction
Module: DFHDUDU dump environment is available only if the XDUOUT user-exit
Destination: Console is active.
Module: DFHDUIO
XMEOUT Parameters: applid, dataset,text-descr


DFHDU0303I • DFHDU0308I
User response: Print or copy the completed dump data set,

DFHDU0303I applid Transaction Dump Data set dataset
and if required, reissue the command CEMT SET DUMP
closed.
AUTO.
Explanation: This message is issued in one of the following
Module: DFHDUSU
situations:
v A request to close the dump data set is issued by the XMEOUT Parameters: applid, filename
operator. Destination: Console
v The CICS system is shut down.
v A request to switch between dump data sets is issued by
the operator. DFHDU0306 applid Unable to open Transaction Dump
v A transaction dump data set becomes full. Data set dataset - text-descr
Explanation: This message occurs when attempting to open a
The insert dataset indicates the name of the data set being transaction dump data set.
closed.
System action: Processing continues. text-descr is one of:
OPEN ERROR
If autoswitching of the transaction dump data set is not active, An attempt was made to open the dump data set,
the transaction dump environment is available only if the and an abend exit was invoked. This condition is
XDUOUT user-exit is active. usually accompanied by VSE system messages.
If autoswitching is enabled, this message is followed by
A OS/390 GETMAIN was issued to obtain storage
DFHDU0304 and DFHDU0305 to indicate that the data set
below the 16MB line. This request was unsuccessful.
switch is successful.
If the switch is unsuccessful, this message is followed by
In both cases, the transaction dump data set is not open, and
DFHDU0306.
unless the XDUOUT exit is active, the transaction dump is
inoperative.
Module: DFHDUSU
XMEOUT Parameters: applid, dataset
User response: See any associated VSE messages for further
guidance.
DFHDU0304I applid Transaction Dump Data set dataset Module: DFHDUIO
opened.
XMEOUT Parameters: applid, dataset,text-descr
Explanation: This message is output when any of the
following situations occur:
v A request to open the dump data set is issued by the
operator. DFHDU0307 applid Module DFHDUIO is unavailable.
v The CICS system is brought up. Transaction dump is inoperative.
v A request to switch between dump data sets is issued by Explanation: This message is issued either when an attempt
the operator. is made to open or close a dump data set, or when switching
v Automatic switching between dump data sets is being between dump data sets, to remind the user that CICS could
performed. not locate module DFHDUIO during initialization. CICS issues
message DFHDU0102 during initialization to warn the user of
dataset in the message indicates the name of the data set being
this condition.
opened.
System action: CICS continues with the transaction dump
facility inoperative.
User response: If necessary, refer to the user response for
Module: DFHDUSU
message DFHDU0102.
XMEOUT Parameters: applid, dataset Module: DFHDUSU
DFHDU0305I applid Transaction Dump Data set switched to
filename
DFHDU0308I applid CICS will terminate because the Dump
Explanation: This message is issued when one of the
Table entry for the transaction dump code:
following situations occurs:
dumpcode specifies shutdown.
v A command is issued by the operator to switch dump data
Explanation: This message is issued when a transaction
sets.
dump has been requested for the transaction dump code
v Automatic switching is being performed between dump
dumpcode and the associated dump table entry specifies that
data sets due to a dump data set being full.
CICS should be terminated.
This message is always preceded by message DFHDU0304 and
This message records that it was a transaction dump table
also, if the old dump data set was open, by message
entry which requested the termination of CICS.
DFHDU0303.
User response: Process any transaction dump in the normal
filename in the message indicates the file name of the active way.
transaction dump data set (either DFHDMPA or DFHDMPB).
System action: Processing continues. On a warm or emergency start, explicitly defined dump table

DFHDU0309I • DFHDU1610
entries are restored from the catalog. If the dump table entry being processed has been used before in the current CICS
for dumpcode was explicitly defined, it can be modified to execution.
prevent CICS from terminating, if desired, using CEMT or Module: DFHDU410
EXEC API commands. Destination: Console
Implicitly defined dump table entries are not recorded on the

catalog and are therefore not restored. On a cold start, CICS DFHDU1603 NO DLBL CARD FOR {DUMP | PRINT}
does not restore the dump table from the catalog. DATA SET {DFHDUMP | DFHPRNT}, DUMP
Module: DFHDUDU UTILITY TERMINATED.
Explanation: A dump or a print data set was not successfully
XMEOUT Parameters: applid, dumpcode
opened.
System action: If it was a dump data set that failed to open
successfully, the system prints the message on the print data
DFHDU0309I applid CICS will terminate because the Dump set and terminates execution with a return code of 12.
Table entry for the system dump code:
If it was the print data set that failed to open successfully, the
dumpcode specifies shutdown.
system terminates execution with a return code of 16.
Explanation: This message is issued when a system dump
User response: If the JCL is correct with the stated file names
has been requested for the system dump code dumpcode and
as in the message, determine why the data set cannot be
the associated dump table entry specifies that CICS should be
opened. The return codes are issued by DFHDU410. They only
terminated.
identify whether a dump or print data set failed.
This message records that it was a system dump table entry Module: DFHDU410
which requested the termination of CICS. Destination: Console
User response: Print off any system dump if required.
DFHDU1604 END OF FILE ENCOUNTERED, LAST
On a warm or emergency start, explicitly defined dump table DUMP MAY BE INCOMPLETE.
entries are restored from the catalog. If the dump table entry Explanation: The dump data set has been filled.
for dumpcode was explicitly defined, it can be modified to System action: The dump utility program DFHDU410
prevent CICS from terminating using CEMT or EXEC API terminates.
commands. User response: Check that the dump is complete and that no
incomplete message is at the end of it. If there is an
Implicitly defined dump table entries are not recorded on the incomplete message at the end of the dump, the last dump in
catalog and are therefore not restored. On a cold start, CICS the data set may not contain all the information required. You
does not restore the dump table from the catalog. should recreate the problem to try and get a complete dump.
Module: DFHDUDU If dump data set auto-switching was active at the time the
Destination: Console dump was taken, a complete version of the dump is present
on the alternate dump data set.
DFHDU1601 DATA SET READ ERROR. Module: DFHDU410
Explanation: The access method has indicated a read error. Destination: SYSLST
The dump data set may not have been opened during the
most recent CICS execution. DFHDU1609 36 CONSECUTIVE INVALID READ
System action: The record is skipped. ERRORS. DUMP UTILITY TERMINATED.
User response: Either ensure that the JCL is correct, or Explanation: The access method has indicated 36 consecutive
determine the reason for the read errors. invalid records in the dump data set. The most probable cause
Module: DFHDU410 of this problem is an invalid end-of-file marker which caused
Destination: Console the access method to attempt to read beyond the last record in
the data set. This problem may also have been caused if:
DFHDU1602 36 CONSECUTIVE UNIDENTIFIABLE v DFHDU410 has been run with a data set that has never
RECORDS, DUMP UTILITY TERMINATED. been accessed by CICS before. The data set may contain an
Explanation: An identification record has an incorrect code or invalid type of record format.
format. The most common reasons for this error include the v DFHDU410 has been run with a data set that has been
following. copied with the wrong block size and record format.
v The wrong data set is being processed. System action: The dump utility execution is terminated with
v The dump data set that the utility is trying to process has a return code of 8 from DFHDU410.
not been used in the current CICS execution. User response: Determine and correct the reason for the
access failure. Recreate the dump if necessary.
In the latter case, the error would arise because no dumps Module: DFHDU410
were produced in the current execution or because the data Destination: Console
sets had been switched.
System action: Records are skipped and execution is
terminated with a return code of 8. DFHDU1610 DUMP FORMATTING HAS
User response: Ensure that the correct data set is being ENCOUNTERED AN INVALID TRACE
processed. Alternatively, check for a possible error in the BLOCK. TRACE ENTRIES MAY BE LOST.
dump control program, DFHDCP. Explanation: The dump utility program, DFHDU410, has
detected an error while copying trace records from the trace
If two dump data sets are being used, check that the data set data set. Trace records may be omitted from the formatted
output.

DFHDU1611 • DFHER5721
System action: DFHDU410 attempts to read the next trace on the data set at which the trace data started. It is therefore
block and continues formatting trace records. not possible to return to the start of the trace data after the
User response: You need further assistance from IBM to abbreviated trace has been formatted in order to print the
resolve this problem. See Part 4 of the CICS Problem trace with format FULL.
Determination Guide for guidance on how to proceed. System action: Transaction dump formatting continues with
Module: DFHDU410 only abbreviated trace for this dump.
Destination: Console User response: If only the full trace is required, rerun the
DFHDU410 job with the NOABBREV parameter. Otherwise
attempt to recreate the dump. If the problem recurs, you will
DFHDU1611 FILE ERROR, FULL TRACE FAILED. DUMP need assistance from IBM. See Part 4 of the CICS Problem
FORMATTING WILL CONTINUE WITH Determination Guide for guidance on how to proceed.
ABBREVIATED TRACE. Module: DFHDU410
Explanation: Due to an error in the NOTE macro, the dump Destination: Console
utility program, DFHDU410, was unable to note the position
DFHDXxxxx messages
The active and alternate CICS systems continue, but the
DFHDX8310I applid Initiating catch-up tasks.
alternate will be less effective in the event of a takeover.
Explanation: The catch-up transaction, CXCU, has received
User response: Retry by entering 'CXCU' from a terminal. If
control.
the error persists check that the routine DFHZXCU is present
System action: The catch-up transaction is about to initiate
in the CICS load library.
the catch-up tasks for specific functional areas.
Module: DFHCXCU
User response: None. This is simply a "work is in progress"
message. You can suppress this message with the system XMEOUT Parameter: applid
initialization parameter, MSGLVL=0. Destination: Console
Module: DFHCXCU
XMEOUT Parameter: applid DFHDX8313I applid Catch-up transaction failed.
Destination: Console Explanation: The catch-up transaction, CXCU, running on the
CICS system with specific applid given, has failed. CXCU runs
either in response to a transaction request from an end-user, or
DFHDX8311I applid System initialized with XRF=NO.
automatically by an active CICS system in response to the
Catch-up transaction CXCU took no action.
appearance of an alternate CICS system. Its purpose is to
Explanation: The catch-up transaction, CXCU, was invoked
inform the alternate of the active's state regarding terminals.
but the CICS system specified XRF=NO. Catchup functions are
System action: The CXCU transaction abends with a dump
not relevant.
and transaction abend code ACXA.
System action: The catch-up transaction terminates normally
without taking any action. Both active and alternate CICS systems continue, but the
User response: None. alternate will be less effective in the event of a takeover. For
Module: DFHCXCU example, terminal backup sessions may not be established.
XMEOUT Parameter: applid Message DFHME0116 is normally produced containing the
Destination: Console symptom string for this problem.
the error persists diagnose problem from the dump.
DFHDX8312I applid Catch-up transaction failed to run Module: DFHCXCU
program DFHZXCU. Catch-up is incomplete.
Explanation: The catch-up transaction, CXCU, running on the XMEOUT Parameter: applid
CICS system with specific applid given, was unable to call the Destination: Console
terminal catch-up service routine DFHZXCU.
System action: The catch-up associated with routine
DFHZXCU is not performed.
DFHERxxxx messages
DFHER2813I applid Program DFHRCEX cannot be found DFHER5721 applid DL/I data on DFHRSD, but no DL/I
Explanation: CICS cannot find DFHRCEX in any sublibrary support on the system. Reply 'GO' or
specified in the LIBDEF search chain for the CICS startup job 'CANCEL'.
stream. Explanation: DL/I backout data exists on the restart data set
System action: CICS terminates abnormally with a dump. DFHRSD, but DL/I support has not been included in this
User response: To correct this error, place DFHRCEX in a execution of CICS. (The system initialization table (SIT) or
sublibrary specified in the LIBDEF search chain. override specified DLI=NO.)
Module: DFHDLBP, DFHTCBP, DFHUSBP System action: The system waits for the operator to reply. If
the reply is 'GO', all DL/I data on the restart data set is
XMEOUT Parameter: applid ignored. If the reply is 'CANCEL', CICS terminates abnormally
Destination: Console with a dump.
User response: Reply 'GO' or 'CANCEL'.
Module: DFHDLBP

DFHER5722 • DFHER5754
DFHER5732 applid User recovery completed
Explanation: During emergency restart, CICS issues this
DFHER5722 applid Backout data present for following message when the CICS module DFHUSBP finishes
{PSB | DMB}(s), but they could not be processing. DFHUSBP presents active user records to the user
scheduled: list. Reply 'GO' or 'CANCEL'. exit, XRCINPT. (Active user records are all user journal
Explanation: DL/I backout data exists on the restart data set records that relate to in-flight tasks, or that have the high
for the listed program specification blocks (PSBs) or data order bit set in the JCRUTRID (user header) field.)
management blocks (DMBs), but the control blocks in question System action: Processing continues.
cannot be scheduled. User response: None.
System action: The system waits for the operator to reply. If Module: DFHUSBP
the reply is 'GO', all the data on the restart data set for the XMEOUT Parameter: applid
PSBs in question (or for the PSBs that reference the DMBs in Destination: Console
question) is ignored. If the reply is 'CANCEL', CICS terminates
abnormally with a dump.
User response: Reply 'GO' or 'CANCEL'. DFHER5750 applid DL/I backout beginning
Module: DFHDLBP Explanation: During emergency restart, CICS issues this
Destination: Console message when the CICS module DFHDLBP starts processing.
(DFHDLBP backs out changes to DL/I databases that were
made by in-flight tasks, that is tasks that were incomplete
DFHER5723 applid Unable to backout for PSB filename. when the preceding abnormal termination occurred).
Backout terminated. Reply 'GO' or System action: Processing continues.
'CANCEL'. User response: None.
Explanation: An error occurred when attempting to backout Module: DFHDLBP
data for the specified program specification block (PSB)
filename. The DL/I error exit, if any, was given control and it XMEOUT Parameter: applid
decided that the operator should be given the opportunity to Destination: Console
cancel the startup.
System action: The system waits for the operator to reply. If
the reply is 'GO', backout continues with the next backout DFHER5751 applid No DL/I backout required
record. If the reply is 'CANCEL', CICS terminates abnormally Explanation: During emergency restart, CICS issues this
with a dump. message when the CICS module DFHDLBP finds no changes
User response: Reply 'GO' or 'CANCEL'. to DL/I databases that need to be backed out. (DFHDLBP
Module: DFHDLBP backs out changes to DL/I databases that were made by
in-flight tasks, that is tasks that were incomplete when the
XMEOUT Parameters: applid, filename preceding abnormal termination occurred).
Destination: Console System action: Processing continues.
Module: DFHDLBP
DFHER5730 applid User recovery beginning
Explanation: During emergency restart, CICS issues this XMEOUT Parameter: applid
message when the CICS module DFHUSBP starts processing. Destination: Console
DFHUSBP presents all active user journal records in the
system log to the user exit, XRCINPT. (Active user records are
all user journal records that relate to in-flight tasks, or that DFHER5752 applid DL/I backout complete
have the high order bit set in the JCRUTRID (user header) Explanation: During emergency restart, CICS issues this
field). message when the CICS module DFHDLBP finishes
System action: Processing continues. processing. (DFHDLBP backs out changes to DL/I databases
User response: None. that were made by in-flight tasks, that is tasks that were
Module: DFHUSBP incomplete when the preceding abnormal termination
occurred).
XMEOUT Parameter: applid System action: Processing continues.
Destination: Console User response: None.
Module: DFHDLBP
DFHER5731 applid No active user records on the system XMEOUT Parameter: applid
log Destination: Console
message when the CICS module DFHUSBP finds no active
user journal records in the system log. (Active user records are DFHER5754 applid Backout data present for following
all user journal records that relate to in-flight tasks, or that PSB(s) but no PDIR entry exists: psblist.
have the high order bit set in the JCRUTRID (user header) Reply 'GO' or 'CANCEL'.
field. DFHUSBP presents active user records to the user exit Explanation: During emergency restart, CICS has found
XRCINPT.) backout records that require PSBs (DL/I program specification
System action: Processing continues. blocks) that have no entries in the PDIR (PSB directory list).
User response: None. The most likely reason for this error is that you are
Module: DFHUSBP inadvertently using a different PDIR from the one that was in
use during the previous CICS run that terminated abnormally.
XMEOUT Parameter: applid System action: If you reply 'GO', CICS ignores the records
Destination: Console for undefined PSBs, and continues restart. If you reply
'CANCEL', CICS terminates abnormally with a system dump.
User response: The safest response is 'CANCEL'. Before you

DFHER5760 • DFHEV9930S
restart CICS, either correct the PDIR, or specify the correct Module: DFHTCBP
suffix in the SIT option or override, PDIR.
Module: DFHDLBP XMEOUT Parameter: applid
DFHER5760 applid Message and ISC state recovery DFHER5762 applid Message and ISC state recovery
beginning completed
Explanation: During emergency restart, CICS issues this Explanation: The CICS module DFHTCBP has finished
message when the CICS module DFHTCBP starts processing. processing. (DFHTCBP recovers terminal messages and the
(DFHTCBP recovers terminal messages and the intersystem intersystem coupling state for use during session
coupling state for use during session resynchronization.) resynchronization.)
System action: Processing continues. System action: Processing continues.
User response: None. User response: None.
Module: DFHTCBP Module: DFHTCBP
XMEOUT Parameter: applid XMEOUT Parameter: applid

DFHER5761 applid No message or ISC state recovery DFHER5763 applid Message and ISC state recovery failed.
required CICS logic error.
Explanation: The previous system recovery did not occur at a Explanation: The CICS module DFHTCBP has failed.
time when session synchronization was affected, therefore the System action: CICS terminates with abend code ABP3.
CICS module, DFHTCBP, does not need to do any recovery. User response: None.
(DFHTCBP recovers terminal messages and the intersystem Module: DFHTCBP
coupling state for use during session resynchronization.) XMEOUT Parameter: applid
System action: Processing continues. Destination: Console
DFHEVxxxx messages
DFHEV1020S filename Logical Unit lunit is either invalid for DFHEV9910W filename Unable to allocate storage for DTF.
this partition or is set to UA or IGN. Explanation: The LE build of the DTF for file filename failed
Explanation: The logical unit, lunit, was found to be either as it was unable to allocate the storage required for the DTF.
not valid or defined as UA or IGN in the DLBL when No I/O operations will be able to be performed for this file
attempting to open file filename. since there is no DTF for it.
System action: The open will not be attempted and a return System action: Returns to calling module with return code
code of at least 8 will be returned to the module that set to a minimum value of 8.
requested the open. User response: It is up to the module requesting the OPEN
User response: Check the DLBL for the file to see if it is to handle the error. Check message DFHEV9920 to confirm the
defined as UA or IGN. If so, change it and resubmit the job. LE return code and check for additional messages and a
Module: DFHEVOP possible abend from the calling module.
There is probably insufficient GETVIS space available. Increase
the GETVIS area by either setting the SIZE parameter of the
DFHEV4020S filename PUT failed. Unsupported mode. JCL EXEC statement, if not set, or by increasing the size of the
Explanation: The PUT operation for file filename failed as it partition before restarting the job.
was not possible to determine whether a PUT LOCATE or a Module: DFHEVOP
PUT MOVE was required. Destination: Console
System action: Error returned to module requesting the PUT
User response: It is up to the module requesting the PUT to
handle the error. Either the file was not opened for put DFHEV9920S filename DTF Builder failed: reason Error code:
operations or there has been a storage overwrite. Check for rc.
additional messages and a possible abend. Explanation: The LE build of the DTF for file filename failed
Module: DFHEVPG due to reason with an error code of rc
Destination: Console System action: The Open fails with a return code set to a
minimum value of 8.
User response: It may be possible to continue without this
DFHEV4030S filename GET failed. Unsupported mode. file. The program requesting the open should handle the open
Explanation: The GET operation for file filename failed as it failure and take the appropriate action.
was not possible to determine whether a GET LOCATE or a
Check the LE Builder error code and take the necessary
GET MOVE was required.
corrective action to avoid repetition of the problem.
System action: Error returned to module requesting the GET
Module: DFHEVOP
User response: It is up to the module requesting the GET to
handle the error. Either the file was not opened for put
operations or there has been a storage overwrite. Check for
additional messages and a possible abend. DFHEV9930S filename DCB does not have an associated
Module: DFHEVPG DFHSIOCT Structure.
Destination: Console Explanation: The code to handle the creation of a DTF for the

DFHEX0001 • DFHEX0101
file filename has detected an error in the definition of the file. that issued the open request to take the appropriate action.
The DFHSIOCT structure could not be located.
System action: The OPEN fails and there turn code is set to a Check for additional messages and a possible abend.
minimum of 8. Module: DFHEVOP
User response: Depending on which file fails to open, this Destination: Console
may or may not be a critical problem. It is up to the program
DFHEXxxxx messages
external CICS interface code. For further information about the
DFHEX0001 An abend (code aaa/bbbb) has occurred in
EXCI exception trace entries, refer to the CICS Problem
module modname.
Determination Guide.
Explanation: An unexpected program check or abend
aaa/bbbb has occurred in module modname. This implies that You need further assistance from IBM to resolve this problem.
there may be an error in external CICS interface code. See Part 4 of the CICS Problem Determination Guide for
Alternatively, unexpected data has been passed on an external
Module: DFHXCPRH, DFHXCEIP
CICS interface call or storage has been overwritten.
The code aaa is, if applicable, a 3-digit hexadecimal VSE
system completion code aaa ,for example 0C1. If a VSE code is
not applicable, this field is filled with three hyphens. The DFHEX0003 A GETMAIN request in module modname
4-digit code bbbb, which follows aaa is, if applicable, a user (code X'code') has failed. Reason X'rc'.
abend code produced by the external CICS interface. If the Explanation: A storage request was issued by module
user abend code is not applicable, this field is filled with four modname, but it failed with return code rc.
hyphens. The code X'code' is the exception trace point ID which
System action: An exception entry is made in the external uniquely identifies the place where the request was issued.
CICS interface internal trace table and a SDUMP is taken. System action: An exception entry is made in the EXCI
The external CICS interface terminates the current request, and internal trace table (code X'code' in the message). This is a
attempts to recover to a consistent state so that further EXCI critical error and the EXCI request is terminated. The external
requests can be serviced. For an application using the EXCI CICS interface attempts to recover to a consistent state so that
CALL API, a response of EXCI_SYSTEM_ERROR with a further EXCI requests can be issued.
REASON of ESTAE_INVOKED is returned to the application. For applications using the EXCI CALL API, the
For an application using the EXCI EXEC API, an EXEC_RESP EXCI_REASON returned to the application indicates the point
of LINKERR is returned to the application, together with an of failure.
EXEC_RESP2 of ESTAE_INVOKED or
EXEC_ESTAE_INVOKED, depending on whether the call level For applications using the EXCI EXEC API, the point of failure
ESTAE routine, or the EXEC level ESTAE routine was invoked. is returned in the EXEC_RESP2 field of the RETCODE area.
User response: Look up the VSE code aaa, if there is one, in
For EXCI_REASON and EXCI_RESP of 603, the EXCI module
"OS/390 API Abend Codes" in section "VSE/Advanced
DFHXCPRH also issues abend 0410 which drives the ESTAE
Functions Codes & SVC Errors" of z/VSE Messages and Codes -
exit. Message DFHEX0001 is issued and a SDUMP is taken
Volume 1.
User response: Look up the VSE return code rc in "OS/390
If applicable, see the description of abend code bbbb in API Return Codes" in section "VSE/Advanced Functions
“Transaction Abend Codes (CICS Transaction Server for Codes & SVC Errors" of z/VSE Messages and Codes - Volume 1.
VSE/ESA)” on page 453 for further guidance.
If the reason is insufficient storage, try increasing the size of
You may need further assistance from IBM to resolve this the region for the batch EXCI job.
Module: DFHXCPRH, DFHXCEIP
Module: DFHXCPRH, DFHXCTRI
DFHEX0002 A severe error (code X'code') has occurred in
module modname.
DFHEX0004 Jobname: jobname, Execname: execname,
Syslogid: syslogid, Applid: applid.
Explanation: This message accompanies message DFHEX0001
uniquely identifies what the error is and where the error was
and will provide the jobname, execname, syslogid, and applid to
detected.
which the EXCI job is connecting to. If an insert value is
System action: An exception entry is made in the EXCI
unknown or not specified then the message insert will read
internal trace table (X'code' in the message). A system dump is
Unknown. For example, execname is not mandatory in an
taken.
EXCI job, if it were omitted and DFHEX0004 was issued then
This is a critical error and the EXCI request is terminated. The the inserts for execname will read Unknown.
external CICS interface attempts to recover to a consistent System action: Follow system action for DFHEX0001.
state so that further EXCI requests can be issued. For User response: Follow user response for DFHEX0001.
applications using the EXCI CALL API, the EXCI_REASON Destination: Console
returned to the application indicates the reason for the error. Modules: DFHXCPRH, DFHXCEIP
For applications using the EXCI EXEC API, the reason is
returned in the EXEC_RESP2 field of the RETCODE area.
User response: This failure indicates a serious error in the DFHEX0101 Unable to start interregion communication

DFHEX0110 • DFHEX0114
because DFHIRP services are down level. User response: The user response depends on the reasons,
Explanation: The version of DFHIRP being used is at a lower (reason), for the failure.
level than that of the External CICS Interface (EXCI) module ONLY PARTIAL DUMP
DFHXCPRH. Use VSE problem determination methods to
System action: The EXCI allocate pipe request is rejected, determine why a partial dump was taken. See the
and a return code passed back to the batch application. z/VSE System Macros Reference manual for a
User response: Update the level of the DFHIRP module in description of the SDUMPX return code.
the SVA such that it matches the level of the latest CICS NO SYSDUMP LIBRARY AVAILABLE
version in use. Define a SYSDUMP library for the CICS job and
Module: DFHXCPRH then cause the SDUMP request to be reissued. See
the z/VSE Diagnosis Tools manual for a description of
DFHEX0110 EXCI SDUMP has been taken. Dumpcode: SYSDUMP LIBRARY IS FULL
dumpcode, Dumpid: dumpid. Clear some dumps from the dump library and cause
Explanation: This message is issued on successful completion the SDUMP request to be reissued. See the z/VSE
of a VSE SDUMP issued by external CICS interface module Diagnosis Tools manual for a description of how to
DFHXCDMP. An error, signaled by a previous message, delete or offload a dump from the SYSDUMP
caused a call to be made to DFHXCDMP to take a system library.
dump. REJECTED BY VSE, REASON = X'nn'
No action is required if the dump is suppressed
The dump code dumpcode is an 8-character system dump code
deliberately. If the dump has failed because of an
identifying the external CICS interface problem. A system
error in the VSE SDUMPX routine, use VSE problem
dump code is the EXCI message number with the DFH prefix
removed.
cause the SDUMPX request to be reissued. See the
dumpid is the unique 9-character string identifying this dump. z/VSE System Macros Reference for an explanation of
System action: The EXCI request is terminated. the SDUMPX reason code X'nn'.
User response: See the EXCI message indicated by dumpcode NOT AUTHORIZED FOR EXCI
for further guidance. This reason is unlikely because SDUMPX is
unconditionally authorized during EXCI
problem. See Part 4 of the CICS Problem Determination Guide initialization, and should be authorized throughout
for guidance on how to proceed. the EXCI run. If you do get this reason, the EXCI
Module: DFHXCDMP. AFCB (authorized function control block) has
Destination: Console probably been accidentally overwritten.
Ensure sufficient partition storage is available to
DFHEX0112 SDUMPX request failed - reason X'nn'. OS/390 GETMAIN requests.
Explanation: A VSE SDUMPX request issued from the Module: DFHXCDMP
external CICS interface has failed to complete successfully. The Destination: Console
possible reasons, (reason) for the failure are as follows:
ONLY PARTIAL DUMP
The number of storage areas to be dumped exceeds DFHEX0113 EXCI trace Initialization has failed.
the maximum allowed for one SDUMPX request. Explanation: An attempt to initialize external CICS interface
NO SYSDUMP LIBRARY AVAILABLE (EXCI) trace facilities during EXCI initialization has failed.
No SYSDUMP library is defined for the CICS job. If System action: The EXCI request continues without trace
the VSE SYSDUMPC job control option is in effect facilities. An earlier message identifies the cause of the failure.
the dump will be suppressed, otherwise it will be User response: Refer to the earlier message to determine the
redirected to SYSLST. cause of the failure.
SYSDUMP LIBRARY IS FULL Module: DFHXCTRI
The SYSDUMP library defined for the CICS job is Destination: Console
full. If the VSE SYSDUMPC job control option is in
effect the dump will be suppressed, otherwise it will
be redirected to SYSLST. DFHEX0114 Incorrect data has been passed for EXCI
REJECTED BY VSE, REASON = X'nn' tracing causing a program check in
VSE has rejected the SDUMPX request because of DFHXCTRP.
user action (for example, specifying NOSYSDUMP Explanation: Some data passed to the external CICS interface
on the OPTIONS statement for the CICS job) or (EXCI) trace module DFHXCTRP for addition to the EXCI
because of an I/O error or terminating error in the internal trace table caused a program check to occur when an
SDUMPX routine. X'nn' is the SDUMPX reason code. attempt was made to access it.
NOT AUTHORIZED FOR EXCI The most likely cause of this error is incorrect data passed on
SDUMPX is not authorized for the external CICS an EXCI CALL API request that the trace program
interface. DFHXCTRP is attempting to access.
INSUFFICIENT STORAGE System action: The EXCI request is terminated and a system
The EXCI issued a OS/390 GETMAIN for storage dump is taken.
during the processing of the SDUMPX request. The User response: Examine the dump to determine the source of
GETMAIN has been rejected by VSE. the incorrect data.
System action: The EXCI proceeds as if the dump had been
successful. You may need further assistance from IBM to resolve this

DFHEX0115 • DFHFC0002

DFHEX0116 Program check occurred within global trap
Module: DFHXCTRI
exit - DFHXCTRA now marked unusable.
Explanation: After making a trace entry, the external CICS
interface (EXCI) trace program DFHXCTRP called the EXCI
DFHEX0115 EXCI trace services have been disabled due field engineering global trap program DFHXCTRA. A program
to a previous error. check occurred during execution of DFHXCTRA.
Explanation: An error occurred in the external CICS interface System action: The EXCI marks the currently active version
(EXCI) trace module DFHXCTRP indicated by message of DFHXCTRA as unusable and ignores it on subsequent calls
DFHEX0001. In trying to recover from the error, module to DFHXCTRP for all subsequent calls made under this TCB.
DFHXCTRI determined that the error was not caused by The EXCI request is terminated, and a system dump is taken.
accessing incorrect data passed to DFHXCTRP, but was due to User response: Use the dump to find the cause of the
a program check in DFHXCTRP. program check.
System action: The EXCI trace facilities are disabled to
prevent further errors. A system dump is taken.
User response: See the DFHEX0001 message and the SDUMP
to determine the cause of the error.
Module: DFHXCTRI
Module: DFHXCTRI
DFHFCxxxx messages
Note: In cases where standard message inserts such as opid or termid are undefined
or cannot be determined, the inserts are replaced by dashes.
system, you may decide to continue to run and bring CICS
DFHFC0001 applid An abend (code aaa/bbbb) has occurred
down at a convenient time to resolve the problem.
Explanation: An abnormal end (abend) or program check has If you cannot run without the full use of module modname,
occurred in module modname. This implies that there may be you should bring CICS down in a controlled shutdown.
an error in CICS code.
Alternatively, See Part 4 of the CICS Problem Determination Guide for
v Unexpected data has been input, or guidance on how to proceed.
v Storage has been overwritten. Module: DFHEFRM, DFHFCBF, DFHFCDN, DFHFCFR,
The code aaa/bbbb is a three digit hexadecimal VSE code (if DFHFCFS, DFHFCJL DFHFCMT, DFHFCRL, DFHFCRM,
applicable), followed by a four digit alphanumeric CICS code. DFHFCRP, DFHFCSD, DFHFCST
The VSE code is a system completion code, for example 0C1. XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
If a VSE code is not applicable, this field is filled with three Destination: Console
abend code; 1310 refers to message DFHTS1310). DFHFC0002 applid A severe error (code X'code') has
System action: An exception entry is made in the trace table. occurred in module modname.
A system dump is taken, unless you have specifically Explanation: An error has been detected in module modname.
suppressed dumps in the dump table. The code code is the exception trace point ID which uniquely
CICS continues unless you have specified in the dump table
that CICS should terminate. To discover the cause of the problem, examine the exception
trace entry and immediately preceding entries. For further
information about CICS exception trace entries, see the CICS
Problem Determination Guide.
is made in the trace table. If the error code is X'046A' then no
Look up the VSE code, if there is one, in "OS/390 API Abend system dump will be produced. Otherwise, a system dump is
Codes" in section "VSE/Advanced Functions Codes & SVC taken, unless you have specifically suppressed dumps in the
Errors" of z/VSE Messages and Codes - Volume 1. dump table.
Then look up the CICS alphanumeric code in “Transaction If module modname is DFHFCBF, it abends the CICS system
Abend Codes (CICS Transaction Server for VSE/ESA)” on with a dump, after issuing this message. This is a critical error
page 453. This tells you, for example, whether the error was a and CICS is terminated, even if you have specified in the
program check, an abend, or a runaway, and may give you dump table that CICS should not terminate.
some further guidance.
If module modname is not crucial to the running of your CICS symptom string for this problem.
User response: Inform the system programmer. This indicates

DFHFC0003 • DFHFC0005
a possible error in CICS code. The severity of its impact Module: DFHFCRP
depends on the importance of the function being executed at
the time of the error.
If the message occurs once and module modname is not crucial DFHFC0004 applid A possible loop has been detected at
to the running of your CICS system, you may decide to offset X'offset' in module modname.
continue to run and bring CICS down at a convenient time to Explanation: A CICS function is taking more time to process
resolve the problem. than CICS expects. A possible loop has been detected in
If the message recurs or if you cannot run without the full use
detected.
If module modname in the message is DFHFCBF, investigate A system dump is taken, unless you have specifically
the problem, using the dump and also possibly messages suppressed dumps in the dump table. CICS continues unless
issued before this message. Correct the problem, and restart you have specified in the dump table that CICS should
CICS with START=AUTO, which CICS then resolves into an terminate.
emergency restart.
You need further assistance from IBM to resolve this problem. symptom string for this problem.
See Part 4 of the CICS Problem Determination Guide for User response: Notify the system programmer. If CICS has
guidance on how to proceed. not been terminated, it is necessary to decide whether the
Module: DFHEFRM, DFHFCBF, DFHFCDN, DFHFCDTS, problem is serious enough to bring CICS down.
DFHFCEI, DFHFCFR, DFHFCFS, DFHFCJL, DFHFCL,
DFHFCM, DFHFCMT, DFHFCN, DFHFCRL, DFHFCRM,
message may have been caused by a long-running function. So
DFHFCRP, DFHFCSD, DFHFCST
there may not be an error here. Usually, CICS purges a CICS
XMEOUT Parameters: applid, X'code',modname function which exceeds the runaway task time interval which
Destination: Console you have specified on the ICVR system initialization
that module modname is terminated and CICS continues.
DFHFC0003 applid Insufficient storage (code X'code') in
module modname. But if you have declared ICVR=0 as a system initialization
Explanation: A CICS GETMAIN was issued by module parameter and you consider that module modname has gone
modname, but there was insufficient storage available to satisfy into a loop, you have to terminate CICS in order to terminate
the request. the runaway function.
The code X'code' is the exception trace point ID which If CICS has terminated module modname, and you consider
uniquely identifies the place where the error was detected. that it was not a runaway, increase the ICVR time interval.
System action: An exception entry is made in the trace table You have to bring CICS down at a suitable time to do this
(code code in the message). A system dump is taken, unless permanently. But you can change the ICVR time interval
you have specifically suppressed dumps in the dump table. temporarily online, using the CEMT transaction.
that CICS should terminate.
require further assistance from IBM. See Part 4 of the CICS
If appropriate, an error return code is sent to the caller of this Problem Determination Guide for guidance on how to proceed.
domain. In this case, CICS could be terminated by the caller Module: DFHEFRM, DFHFCBF, DFHFCDN, DFHFCFR,
(for example, the domain manager, DFHDMDM). A message is DFHFCFS, DFHFCJL, DFHFCMT, DFHFCRL, DFHFCRM,
issued to this effect. DFHFCRP, DFHFCSD, DFHFCST
Message DFHME0116 is normally produced containing the XMEOUT Parameters: applid, X'offset', modname
symptom string for this problem. Destination: Console
User response: Inform the system programmer. If CICS has
been terminated by another module, look out for the relevant
DFHFC0005 applid A hardware error has occurred (module
termination messages (from the domain manager, for
modname, code X'code'). The Time-of-Day clock
example), and look up the user response for these messages.
is invalid.
If CICS is still running, the problem may be a temporary one Explanation: A hardware error has occurred during the
which rights itself if more storage becomes available. If you running of module modname. The store clock facility is the
can manage without module modname, you may decide to timing mechanism for the operating system.
the problem.
If the message recurs or if you cannot run without the full use System action: An exception entry (code code in the message)
of all CICS modules, you should bring CICS down in a is made in the trace table. A system dump is taken, unless you
controlled shutdown. have specifically suppressed dumps in the dump table. CICS
continues unless you have specified in the dump table that
Try increasing the size limits of the DSAs or EDSAs. See the CICS should terminate. If appropriate, an error return code is
CICS System Definition and Operations Guide or the CICS sent to the caller of this domain. In this case, CICS could be
Performance Guide for further information on CICS storage. terminated by the caller (for example, the domain manager,

DFHFC0100I • DFHFC0107D
DFHDMDM). A message to this effect is issued. Module: DFHFCIN1, DFHFCRP, DFHFCFS
Message DFHME0116 is normally produced containing the XMEOUT Parameters: applid, modname
User response: Notify the system programmer. This is in all
probability a hardware error and you should in the first
instance investigate the store clock and find out whether it is DFHFC0104 applid Unexpected catalog error.
working properly. If this is the cause, you should take the Explanation: File control issued a request to the catalog (CC)
appropriate action to have it repaired or replaced. domain which failed. This is probably caused by an I/O error
on the catalog.
In the unlikely event that this is not a hardware problem, you System action: A system dump is produced with code
will require further assistance from IBM. See Part 4 of the FC0104.
proceed. Message DFHME0116 is normally produced containing the
Module: XMEOUT Parameters: applid, modname,X'code' symptom string for this problem.
Destination: Console User response: Determine the cause of the error from the
messages issued from the catalog domain.
Module: DFHFCRP
DFHFC0100I applid File Control initialization has started.
Explanation: This is an informational message indicating the XMEOUT Parameter: applid
start of file control initialization. Destination: Console
User response: None. You can suppress this message with DFHFC0105 applid Entry for file filename cannot be located
the system initialization parameter, MSGLVL=0. in the CICS catalog.
Module: DFHFCRP Explanation: During file control initialization, an error
XMEOUT Parameter: applid occurred either while the table manager was linking the AFCT
Destination: Console entries to the FCT entries, or while the table manager was
searching for the FCTs in order to connect them to the dsname
blocks.
DFHFC0101I applid File Control initialization has ended. System action: CICS initialization is abnormally terminated
Explanation: File control initialization has completed and a trace entry is made.
successfully.
System action: Initialization continues. Message DFHME0116 is normally produced containing the
User response: None. You can suppress this message with symptom string for this problem.
the system initialization parameter, MSGLVL=0. User response: Investigate why the catalog has no FCT entry.
Module: DFHFCRP. If this is not the cause of the problem, determine why the FCT
could not be found.
XMEOUT Parameter: applid Module: DFHFCRP
XMEOUT Parameters: applid, filename
DFHFC0102 applid File Control initialization has failed.
Explanation: File Control has failed to initialize correctly.
DFHFC0106I applid Insufficient storage to satisfy
System action: Message DFHSI1521 is issued and
GETMAIN request in module modname.
initialization is terminated.
User response: The error can be identified by a trace entry, Explanation: The storage (SM) domain has insufficient space
to satisfy a GETMAIN request made during CICS
and possibly by a prior message. You should then take action
initialization.
that is appropriate to the error.
Module: DFHFCRP System action: A system dump is produced.
XMEOUT Parameter: applid the system initialization parameter MSGLVL=0.
Destination: Console Module: DFHFCRP
DFHFC0103 applid Required module modname could not be Destination: Console
loaded.
Explanation: Module modname is required by file control. It
DFHFC0107D applid Unable to load File Control table
could not be loaded because it is missing from the LIBDEF
DFHFCTxx. Enter either an alternative suffix,
search chain.
or 'YES', or 'NO'.
System action: The system terminates with a system dump
Explanation: The file control table, DFHFCTxx could not be
and code FC0103.
found in the LIBDEF search chain during a cold start of CICS.
Message DFHME0116 is normally produced containing the System action: File control initialization waits for a reply to
symptom string for this problem. this message.
User response: Ensure that module modname is in the LIBDEF User response:
search chain. v Reply to this message with a 1 or 2 character suffix to cause
file control to load DFHFCTxx, or
If this is not the cause of the problem you will require further v Reply 'YES' to load an unsuffixed FCT, or
assistance from IBM. See Part 4 of the CICS Problem v Reply 'NO' to initialize file control without an FCT.
Determination Guide for guidance on how to proceed. Module: DFHFCRP

DFHFC0108 • DFHFC0203I
XMEOUT Parameters: applid, xx

DFHFC0112 applid Install of remote FCT entry filename
failed. SYSID sysid, specified in the entry, is
the local SYSID.
DFHFC0108 applid Invalid reply to message DFHFC0107D. Explanation: DFHFCRP attempted to install file filename from
A 1 or 2 character suffix, or YES or NO is the assembled FCT. The install failed because the file was
required defined as TYPE=REMOTE but the SYSIDNT specified, sysid,
Explanation: The reply to message DFHFC0107 was invalid. was the system identifier of this local system.
The reply may have been too long or may have contained System action: File filename is not installed and file control
invalid characters. initialization continues.
System action: Message DFHFC0107 is reissued and User response: Examine the entry for filename in the FCT and
initialization waits for a reply. either make the entry a local entry (TYPE=FILE) or correct the
User response: Reply to message DFHFC0107. SYSIDNT specified.
Module: DFHFCRP Module: DFHFCRP
XMEOUT Parameter: applid XMEOUT Parameters: applid, filename, sysid

DFHFC0109A applid Cold start specified when backout DFHFC0200I date time applid File filename has been allocated
failure processing is incomplete. Data to data set dataset.
integrity is at risk. Explanation: This message provides a record of the dynamic
Explanation: The previous CICS run detected a backout allocation of the file filename to the data set dataset.
failure. CICS started processing to handle the backout failure System action: Processing continues.
so that the affected data sets could be taken offline to be User response: None.
recovered, however this processing was not complete when Module: DFHFCN.
CICS failed. CICS has been cold started and backout failure XMEOUT Parameters: date, time,applid, filename, dataset
processing from the previous CICS run is not complete. CICS Destination: CSFL
should have been emergency started to allow backout failure
processing to complete. Backout failure processing cannot be
completed when CICS is cold started, and so an offline DFHFC0201I date time applid File filename has been
backout utility cannot be run. deallocated.
System action: The affected VSAM data set is marked as Explanation: This message provides a record of the dynamic
BACKOUT FAILED to prevent further access to the data set deallocation of the file filename.
via CICS files. System action: Processing continues.
Message DFHFC0305, which follows this message, identifies
Module: DFHFCN
the VSAM data set involved.
User response: Take the affected data sets offline to recover XMEOUT Parameters: date, time,applid, filename
the data. If RECOVERY=ALL was specified, the data set can Destination: CSFL
be forward recovered up to the point of failure using both an
offline forward recovery utility and the archived forward
recovery logs. An offline backout utility cannot be used in this DFHFC0202I date time applid terminal userid tranid FCT entry
instance. Some other method of restoring the data to a for filename has been added.
consistent point must be used. When the data set has been Explanation: This message provides the system with a record
recovered use the CEMT SET DSNAME NORMAL command of the dynamic addition of FCT entry, filename.
to reset the backout failure state and to allow CICS files to System action: Processing continues.
access the data set. User response: None.
Module: DFHFCRP Module: DFHFCMT.
XMEOUT Parameter: applid XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
Destination: Console filename
Destination: CSFL
DFHFC0110 applid Error, a xxxx version of DFHFCTxx has

been loaded. DFHFC0203I date time applid terminal userid tranid FCT entry
Explanation: DFHFCRP loaded DFHFCTxx that was for filename has been deleted.
assembled for CICS release xxxx. It is not valid to run CICS Explanation: This message provides a record of the dynamic
with an FCT assembled against a previous release. deletion of FCT entry filename.
System action: File control initialization, and hence CICS This occurs when a file, which already exists in the system, is
cold start, is terminated. being installed using RDO. It should be followed by message
User response: Reassemble DFHFCTxx for the CICS release DFHFC0202 indicating that the new file definition has been
being used. Cold start CICS. added.
Module: DFHFCRP System action: Processing continues.
XMEOUT Parameters: applid, xxxx,DFHFCTxx User response: None.
Destination: Console Module: DFHFCMT.
XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
filename

DFHFC0204I • DFHFC0301
Destination: CSFL VSAM Catalog for data sets allocated to this LSR pool.
In this message CI_SIZE relates to the values specified in
DFHFC0204I date time applid terminal userid tranid FCT entry DATA BUFFERS and INDEX BUFFERS in the resource
for filename has been updated. definition for LSRPOOL. See the CICS Resource Definition Guide
Explanation: This message provides a record of updates to an for details on defining an LSRPOOL.
FCT entry other than OPEN, CLOSE, ENABLE and DISABLE. System action: CICS will issue VSAM SHOWCAT requests to
obtain the information necessary to calculate the LSR pool
An FCT entry is updated by an EXEC CICS SET FILE size. If any data sets have been migrated the SHOWCAT could
command or by a CEMT SET FILE command. take longer than expected.
System action: Processing continues. User response: If there are severe delays due to SHOWCAT
User response: None. processing, you will have to wait for migrated data sets to be
Module: DFHFCMT. recalled, and for the calculation of the LSR pool size to
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, complete. If you wish to avoid similar problems in the future,
filename consider defining the LSR pool explicitly. The missing
Destination: CSFL parameters are contained in this message.
Normally, you will not experience delays, in which case no

user action is required.
DFHFC0205I date time applid terminal userid tranid SHRCTL
block for LSR pool lsrpool has been updated. You can suppress this message with the system initialization
Explanation: This message provides a record of the updates parameter, MSGLVL=0.
to a SHRCTL block. Module: DFHFCL
A SHRCTL block exists for VSAM LSR pools 1–15 and is XMEOUT Parameters: applid, lsr_pool_id, 'CI_SIZE', 'STRINGS',
updated by an RDO install of an LSRPOOL object. 'MAXKEYLENGTH'
System action: Processing continues. Destination: Console
Module: DFHFCRL.
DFHFC0300 applid (tranid termid) purge deferred due to
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, incomplete I/O operation on VSAM file
lsrpool 'filename'.
Destination: CSFL Explanation: An attempt has been made to purge a
transaction using FORCE. Transaction tranid is currently
DFHFC0206 date time applid terminal userid tranid AFCT waiting for completion of an I/O operation on the VSAM file
entry for filename has been added. filename. termid identifies the terminal running this transaction.
Explanation: This message provides the system with a record The data set name appears in message DFHFC0305 which
of the dynamic addition of a remote file filename. follows this message.
System action: Processing continues. System action: The transaction waits until the I/O operation
User response: None. is completed before the purge is allowed to take effect. This is
Module: DFHAFMT done to avoid a risk to data integrity. After the I/O completes
the transaction is terminated with transaction abend code
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, AFCY.
filename User response: If the transaction does not terminate within a
Destination: CSFL few seconds, it may be that the I/O wait is genuine (for
example, another CPC has reserved the DASD volume). If this
is the case, wait until the I/O situation is relieved before
DFHFC0207 date time applid terminal userid tranid AFCT trying again.
entry for filename has been deleted.
Explanation: This message provides a record of the dynamic Alternatively, there may be a system problem that warrants
deletion of a remote file filename. terminating CICS and using emergency restart to guarantee
data integrity. If this is the case, terminate CICS and perform
This occurs when a remote file, which already exists in the an emergency restart.
system, is being deleted using RDO. Module: DFHFCVR
User response: None. XMEOUT Parameters: applid, tranid,termid, filename
Module: DFHAFMT Destination: Console

filename DFHFC0301 applid (tranid termid) purge deferred due to
Destination: CSFL incomplete I/O operation on DAM file
'filename'.
Explanation: An attempt has been made to purge a
DFHFC0208I applid LSR pool lsr_pool_id is being built transaction using FORCE. Transaction tranid is currently
dynamically by CICS because the following waiting for completion of an I/O operation on the VSAM file
are not defined: 'CI_SIZE' 'STRINGS' filename. termid identifies the terminal running this transaction.
'MAXKEYLENGTH'. A delay is possible. The data set name appears in message DFHFC0305 which
Explanation: If one or more of the parameters, CI size, follows this message.
strings and maxkeylength are not defined for a LSR pool, then System action: The transaction waits until the I/O operation
CICS will calculate the size by using information from the is completed before the purge is allowed to take effect. This is

done to avoid a risk to data integrity. After the I/O operation

DFHFC0304 applid Dump taken in module_name due to a
is completed, the transaction is terminated with transaction
file control OPEN/CLOSE error.
abend code AFCY.
Explanation: This message is issued after DFHFCFS has
User response: If the transaction does not terminate within a
made an OPEN or CLOSE request which has completed with
few seconds, the I/O wait might be genuine (for example,
an error. The specific error is identified by another message. In
another CPC has reserved the DASD volume). If this is the
most cases the other message appears before this message, but
case, wait until the I/O situation is relieved before trying
if the error occurs during the building of a shared resources
again.
pool, the other message appears after this message.
Alternatively, there may be a system problem that warrants
The failure is identified as one of the following:
terminating CICS and using emergency restart to guarantee
v An invalid request (not OPEN or CLOSE) has been sent
data integrity. If this is the case, terminate CICS and perform
v There has been a subtask failure
an emergency restart.
v There has been a system failure other than "DSNAME NOT
Module: DFHFCBD
FOUND" or "VSAM CATALOG DOMAIN NOT FOUND".
XMEOUT Parameters: applid, tranid,termid, filename v There has been a failure during shared resources pool
Destination: Console building.
System action: A trace entry is made and a dump is taken
with dumpcode FC0304.
DFHFC0302 applid (tranid termid) CICS terminating. Failure User response: Locate the fault by examining the trace entry
while waiting for I/O operation on VSAM and the dump.
file 'filename'. Module: DFHFCL, DFHFCM, DFHFCN
Explanation: A DISASTER type error occurred when the
transaction tranid was waiting for the completion of an I/O XMEOUT Parameters: applid, module_name
operation on the VSAM file whose file name and data set Destination: Console
name appear in message DFHFC0305 which follows this
message. termid identifies the terminal running this
DFHFC0305 applid Message msgno file 'filename' dsname
transaction.
'dataset'.
System action: CICS is terminated with a system dump
Explanation: This message follows message DFHFC0109,
(dump code FC0302).
DFHFC0300, DFHFC0302 or DFHFC0307. It identifies the
User response: This problem was caused by an earlier error.
VSAM data set name referred to in those messages.
Look for earlier messages and return codes (for example, from
the dispatcher domain) and associated trace entries and If this message follows DFHFC0109, it is issued from
dumps. DFHFCRP. In this case, the filename insert is set to unknown as
it is irrelevant.
If the problem cannot be traced to an application error, you
will require further assistance from IBM. See Part 4 of the If this message follows DFHFC0300 or DFHFC0302, it is issued
CICS Problem Determination Guide for guidance on how to from DFHFCVR.
proceed.
Module: DFHFCVR If this message follows DFHFC0307, it is issued from
DFHFCVS.
XMEOUT Parameters: applid, tranid,termid, filename System action: Processing continues in the way specified in
Destination: Console message DFHFC0109, DFHFC0300, DFHFC0302 or
DFHFC0307, whichever is applicable.
User response: Find the earlier message to which this
DFHFC0303 applid (tranid termid) CICS terminating. Failure
information refers and follow the user response for that
while waiting for I/O operation on DAM file
message.
'filename'.
Module: DFHFCRP, DFHFCVR, DFHFCVS
Explanation: A DISASTER type error occurred when
transaction tranid was waiting for the completion of an I/O XMEOUT Parameters: applid, msgno,filename, dataset
operation on DAM file filename. Destination: Console
termid identifies the terminal running this transaction.
System action: CICS is terminated with a system dump DFHFC0306 applid Update via file filename rejected.
(dump code FC0303). Associated data set has failed backout.
User response: This problem was caused by an earlier error. Explanation: A task attempted to update file filename that
Look for earlier messages and return codes (for example, from was associated with a data set which has failed backout.
the dispatcher domain) and associated trace entries and
dumps. To preserve data integrity, the update request has been
rejected.
If the problem cannot be traced to an application error, you System action: The task is abnormally terminated, with
will need further assistance from IBM. See Part 4 of the CICS abend code AFC9, and an exception trace is produced.
Problem Determination Guide for guidance on how to proceed. User response: The data set needs to be recovered before any
Module: DFHFCBD further updates can be made to it. Refer to the earlier backout
failure messages for further information.
XMEOUT Parameters: applid, tranid,termid, filename
Module: DFHFCVS


DFHFC0307 applid I/O error on file 'filename', component
Messages and Codes - Volume 1 for an explanation of the SAF
code X'code'. File is temporarily disabled.
return code.
Explanation: An I/O error was reported by VSAM after a
request to update VSAM file filename. The values of X'ff' are
X'01' Access was refused by an AUTH security check.
The file has been specified with LSR so VSAM has not
X'02' Access was refused by a FASTAUTH security check.
released the buffers it assigned to process the request.
System action: CICS continues normally but no other CICS
Therefore, CICS must take special action to release them.
systems are able to share any data tables it creates until
The name of the data set associated with the file is in message authority is granted and a table is subsequently opened.
DFHFC0305 which follows, although the error may have been User response: Ensure that CICS has the necessary
encountered elsewhere. This is indicated by the value of the authorization to provide shared access to data tables.
component code X'code'. Its possible values and the Module: DFHFCFS
corresponding error locations are as follows:
XMEOUT Parameters: applid, X'code'
v X'00' or X'01'—base cluster.
v X'02' or X'03'—alternate index.
v X'04' or X'05'—upgrade set.
System action: The file is quiesced, closed and then reopened DFHFC0401 applid This CICS system is now authorized to
in order to release the VSAM output buffers. Until the close provide shared access to data tables.
has completed successfully, the file appears 'UNENABLED' to Explanation: CICS is about to open a data table. On a
new would-be users and they receive a 'NOTOPEN' response previous occasion message DFHFC0400 was issued because
to requests to use the file. The application request which authorization checks failed preventing this CICS system from
encountered the error receives an 'IOERR' response. making provision for sharing its data tables with any other
User response: The installation should follow its standard CICS system. The check has been retried successfully.
procedure for I/O errors. No special additional action is System action: CICS continues normally. Subject to specific
required to respond to this particular message although the authorization checks, other CICS systems are now able to
data set name and component code may help in identifying share this system's data tables.
the problem. User response: None.
Module: DFHFCVS Module: DFHFCFS
XMEOUT Parameters: applid, filename, X'code' XMEOUT Parameter: applid
DFHFC0313I applid VSAM has returned an error with an DFHFC0406 applid This CICS system is not authorized for
RPL feedback - return code: X'rc' component shared access to any data tables owned by
code: X'cc' error code: X'ec' for file: filename the CICS system with applid applid2 - reason
and dsname: dataset. The data set may be out code X'code'.
of synch with its Alternate Indices. Explanation: A file request for a remote file resource is about
Explanation: VSAM has returned an error for VSAM file to be passed to a CICS system with the specified applid. The
filename. The application will have been returned an ILLOGIC remote system has registered as a shared data table server, but
response. This is indicated by the value of the component this system cannot access any of its tables because a security
code X'cc'. Its possible values and the corresponding error check for read access to the resource name DFHAPPL.applid2
locations are as follows. has failed, where applid2 is the applid of the data table owning
v X'00' or X'01' – base cluster. CICS system. The value of the reason code, X'code', provides
v X'02' or X'03' – alternate index. further information on the reason for the failure of the bind
v X'04' or X'05' – upgrade set. security check. It has the format X'ffrraaaa' where ff identifies
System action: An ILLOGIC response is returned to the the authorization check which failed. rr gives the register 15
application. return code from SAF, and aaaa is the ESM return code. See
User response: You may need to delete, redefine and re-build "BSM Return Codes" in section "VSE/Advanced Functions
your alternate indices based on this file. Codes & SVC Errors" of z/VSE Messages and Codes - Volume 1
Module: DFHFCVS for an explanation of the SAF return code.
XMEOUT Parameters: applid, X'rc',X'cc', X'ec', filename, dataset The values of X'ff' are:
Destination: Console X'01' Access was refused by an AUTH security check.
X'02' Access was refused by a FASTAUTH security check.
System action: CICS continues normally and function ships
DFHFC0400 applid This CICS system is not authorized to
this and subsequent requests directed to the specified remote
provide shared access to data tables - reason
system until authority is granted. Access is retried after about
code X'code'.
10 minutes.
Explanation: CICS is about to open a data table but has been
User response: If it was intended that this CICS system
unable to make provision for sharing the table with other
should be able to access data tables owned by the system
CICS systems because a security check for update access to the
applid2, change the necessary security definitions of your
resource name DFHAPPL.applid has failed. The value of the
external security manager.
reason code, X'code', provides further information on the
reason for the failure of the security check. It has the format XMEOUT Parameters: applid, applid2, X'code'
X'ffrraaaa' where ff identifies the authorization check which Module: DFHFCFS
failed, rr gives the register 15 return code from SAF, and aaaa Destination: Console
is the ESM return code. See "BSM Return Codes" in section


DFHFC0407 applid This CICS system is now authorized
for shared access to data tables owned by the
CICS system with applid applid2.
Explanation: The security check which failed earlier and was DFHFC0410 applid Data table cannot be opened. Data
reported in message DFHFC0406, has now succeeded. This table initialization has failed for reason
system can now attempt to access shared data tables owned X'code'.
by the CICS system with applid applid2. Explanation: CICS is about to open a data table but has been
System action: CICS continues normally. Subject to specific unable to initialize shared data table services. The value of the
resource authorization checks, shared data tables owned by reason code, X'code', provides further information about why
the remote CICS system can now be accessed by this system. CICS was unable to initialize shared data table services.
Module: DFHFCFS The format of the reason code is either: X'ffaaaaaa', in which ff
is a value less than X'80' that identifies the type of failure, and
XMEOUT Parameters: applid, applid2 aaaaaa is additional information provided for some of the
Destination: Console failures, or when an abnormal termination (abend) has
occurred, X'axxxrrrr' in which a is a value greater than or
equal to X'8' that categorizes the type of abend, rrrr contains
DFHFC0408 applid This CICS system is not authorized for
any register 15 abend reason code, and xxx contains the
shared access to remote file filename - reason
system or user completion code as three hexadecimal digits.
code X'code'.
Explanation: A file request to the specified remote file When X'code' < X'80000000', the values of X'ff' are:
resource, which is a shared data table, has just been processed. X'01' An unexpected failure occurred. This code is
This system was unable to gain shared access to the table reported when the data tables SVC detects an
because it failed a security check, but function shipped access unexpected error.
was not similarly prevented. X'06' An error was returned by the CICS SVC. The first
byte of the additional information, X'aa0000' is the
The value of the reason code, X'code', provides further
register 15 return code from the attempt to call the
information on the reason for the failure of the file security
CICS SVC.
check. It has the format X'ffrraaaa'; where ff identifies the
X'08' An error was returned by the VSE DSPSERV macro.
userid that was refused access, rr gives the register 15 return
The additional information in the reason code
code from SAF, and aaaa is the ESM return code. See "BSM
consists of 1 byte containing the register 15 return
Return Codes" in section "VSE/Advanced Functions Codes &
code followed by 2 bytes containing the middle
SVC Errors" of z/VSE Messages and Codes - Volume 1 for an
bytes from the register 0 reason code returned by
explanation of the SAF return code.
DSPSERV.
The values of X'ff' are X'09' An error was returned by the VSE ALESERV macro,
X'01' The requesting system's own userid was refused called to create an access list entry either for the
read access to the remote file filename. data space or for references to the primary address
X'02' The default userid of the CICS system which owns space. The additional information in the reason code
the remote file filename was used in the security consists of one byte containing the register 15 return
check for read access to the file, and access was code followed by two bytes containing the
refused. ALESERV function code (service type) and qualifier
System action: CICS continues normally and function ships (options) which identify the failing request.
this and subsequent requests directed to the specified remote X'0E' An attempt to serialize the use of shared data table
file until authority to use shared access is granted. Access is services (thus ensuring that only one TCB per
retried after about 10 minutes. address space can use the services) has failed. The
User response: Check whether shared access from this first byte of additional information contains the
system to the specified file is intended. If it is, use the OS/390 ENQ return code.
additional information provided in the reason code to
determine what changes to the security definitions or setup When X'code' = X'80000000', the values of X'a' are formed from
are required. combinations of:
X'8' An abend was detected.
See the CICS Shared Data Tables Guide for an explanation of the
X'4' A user abend was detected, in which case xxx
rules determining which userid is used for a file security
contains the hexadecimal equivalent of the user
check.
completion code (otherwise, xxx contains the
Module: DFHFCEI
hexadecimal system completion code).
XMEOUT Parameters: applid, filename, X'code' X'2' An abend was detected but could not be analyzed
Destination: Console fully because no SDWA was available.
X'1' An asynchronous abend was detected (otherwise,
the abend was synchronous or could not be
DFHFC0409 applid This CICS system is now authorized classified because there was no SDWA).
for shared access to remote file filename. System action: CICS continues normally. This message is
Explanation: The security check which failed earlier, and was followed either by message DFHFC0931 or by DFHFC0932.
reported in message DFHFC0408, has now succeeded. This The following message indicates the action taken for the table
system can now use shared access to the specified table. involved. A system dump is taken for unexpected errors (X'ff'
System action: CICS continues normally. =X'01') and for abends (if dumps are requested for that abend
User response: None. code).
Module: DFHFCFS User response: The response depends on the reason for the

failure as indicated in the first byte of the reason code: GETVIS and the storage is owned by the requesting
X'01' Use the system dump to help you determine the task. The storage is fetch-protected.
cause of the problem. X'04' Private storage from subpool 0 for a pool for file
X'06' The most likely reason for a failure of the CICS SVC blocks. This subpool is allocated in partition GETVIS
call is that the data tables SVC module DFHDTSVC and the storage is owned by the requesting task. The
could not be loaded, in which case the return code storage is fetch-protected.
value is X'02'. If this is the case, check that the X'08' z/VSE data space storage.
DFHDTSVC module is in the SVA. If the module is X'09' Private storage from subpool 252 (key 0) for a region
in the correct location, investigate why it could not anchor. This subpool is allocated in partition
be loaded. There might be a hardware fault on the GETVIS and the storage is owned by the job step.
disk. Another less likely value for the return code is The storage is not fetch-protected.
X'06', which implies that DFHDTSVC has been X'11' Private storage from subpool 0 for a dummy
relink-edited and not marked reentrant. recovery block. This subpool is allocated in partition
X'08' Refer to the documentation of the VSE DSPSERV GETVIS and the storage is owned by the requesting
macro in z/VSE System Macros Reference to interpret task. The storage is fetch-protected.
the register 0 and register 15 return codes reported X'12' Storage from subpool 252 required to load the
in the additional information part of the reason DFHDTAM load module. This subpool is allocated
code. in partition GETVIS and the storage is owned by the
X'09' The function code (service type) and qualifier job step. The storage is not fetch-protected.
(options) reported in the reason code can be used to X'13' Private storage from subpool 230 (CICS key) for a
determine which ALESERV request was being parameter list used by the data tables SVC. This
attempted. Refer to the VSE ALESERV subpool is allocated in partition GETVIS and the
documentation and macro to interpret the function storage is owned by the requesting task. The storage
code, qualifier, and register 15 return code reported is not fetch-protected.
in the reason code. X'14' Private storage from subpool 252 (key 0) for a new
X'0E' This might indicate that the limit on the number of ALET list section. This subpool is allocated in
OS/390 ENQs per address space has been reached, partition GETVIS and the storage is owned by the
or that another TCB running in this CICS address job step. The storage is not fetch-protected.
space has already initialized as a requester of shared System action: CICS continues normally. This message is
data table services. followed either by message DFHFC0931 or by DFHFC0932.
= X'80' When the reason code indicates that an abend has The following message indicates the action taken for the table
been detected, use the additional information involved.
provided in the reason code to find out what the User response: The response depends on the type of storage
abend was, and refer to information on that abend indicated by the reason code. If it indicates private storage,
code to determine the cause. you should reconsider the various region size parameters
Module: DFHFCFS which have been specified on the CICS job. It might be
necessary to take an SDUMP of the CICS job in order to
XMEOUT Parameters: applid, X'code' investigate the way in which storage has been allocated to the
Destination: Console various subpools.
If it indicates data space storage, check whether the size of
DFHFC0411 applid Data table cannot be opened. Data data spaces in this VSE system has been limited by use of the
table initialization has failed owing to a IEFUSI installation exit.
storage failure - reason code X'code'. Module: DFHFCFS
unable to initialize shared data table services because of a XMEOUT Parameters: applid, X'code'
failure to obtain storage. The value of the reason code, X'code', Destination: Console
provides further information about the type of storage which
could not be obtained.
DFHFC0412 applid Data table cannot be opened. Data
The format of the reason code is X'ttnnnnnn' in which tt table initialization has failed owing to a
identifies the type of storage and, for some of the codes, module loading failure - reason code X'code'.
nnnnnn gives the hexadecimal size in bytes of the storage Explanation: CICS is about to open a data table but a module
which could not be obtained. For fixed-length storage blocks, loading failure has prevented the initialization of shared data
the reason code does not usually report the size. table services. The value of the reason code, X'code', provides
further information about which module was being loaded,
The values of X'tt' are: and what went wrong with the attempt to load it.
X'01' Private storage from subpool 230 (key 0) for a work
area used by the data tables SVC. This subpool is The format of the reason code is X'mfrraaaa' in which m
allocated in partition GETVIS and the storage is identifies the module and f is a code for the type of failure.
owned by the requesting task. The storage is not For some failures, rr contains the register 15 return code from
fetch-protected. the failing macro call, and aaaa might contain additional
X'02' Private storage from subpool 0 for the local header information.
block used by a shared data table server. This
The value of X'm' can be:
subpool is allocated in partition GETVIS and the
X'1' DFHDTFOR
storage is owned by the requesting task. The storage
X'2' DFHDTAM
is fetch-protected.
X'8' DFHDTSAN
X'03' Private storage from subpool 0 for a pool for data
table blocks. This subpool is allocated in partition

DFHFC0415
The values of X'f' are: perform the initialization required to act as a requester of
X'1' module not found by a OS/390 LOAD, OS/390 shared data table services.
BLDL or DFHCSVQU macro
The format of the reason code is either: X'ffaaaaaa' in which ff
X'2' an error was returned by the OS/390 LOAD macro.
is a value less than X'80' that identifies the type of failure, and
The two bytes X'aaaa' of additional information in
aaaaaa is additional information provided for some of the
the reason code contain the abend code from the
failures; or, when an abnormal termination (ABEND) has
OS/390 LOAD. X'rr' is the register 15 reason code.
occurred, X'axxxrrrr' in which a is a value greater than or
X'3' an error was returned by the DFHCSVQU macro.
equal to X'8' that categorizes the type of abend, rrrr contains
X'rr' is the register 15 return code.
any register 15 abend reason code, and xxx contains the
X'4' an error was returned by the OS/390 BLDL macro.
system or user completion code as three hexadecimal digits.
The two bytes X'aaaa' of additional information in
the reason code contain the R0 reason code returned When X'code' < X'80000000', the values of X'ff' are:
by BLDL. X'01' An unexpected failure occurred. This code is
X'5' the module is not reentrant. reported when the data tables SVC detects an error
X'6' the module had the wrong AMODE. which should never occur.
X'7' the module had the wrong RMODE. X'06' An error was returned by the CICS SVC. The first
System action: CICS continues normally. This message is byte of the additional information, aa0000, is the
followed either by message DFHFC0931 or by DFHFC0932. register 15 return code from the attempt to call the
The following message indicates the action taken for the table CICS SVC.
involved. X'0E' An attempt to serialize the use of shared data table
User response: The response depends on the reason for the services (thus ensuring that only one TCB per
failure as indicated in the second hex digit of the reason code: address space can use the services) has failed. The
X'1' Use the first hex digit to determine which module first byte of additional information contains the
could not be found, and ensure that it is in the OS/390 ENQ return code.
correct library.
X'2' Refer to "OS/390 API Abend Codes" in section When X'code' = X'80000000', the values of X'a' are formed from
"VSE/Advanced Functions Codes & SVC Errors" of combinations of:
z/VSE Messages and Codes - Volume 1 to interpret the X'8' An abend was detected.
OS/390 LOAD abend and reason codes reported in X'4' A user abend was detected, in which case xxx
the message. There might also be a message from contains the hexadecimal equivalent of the user
the OS/390 LOAD which explains the reason for the completion code (otherwise, xxx contains the
failure. hexadecimal system completion code).
X'3' This indicates an error has occurred while executing X'2' An abend was detected but could not be analyzed
the DFHCSVQU macro. This macro is used to locate fully because no SDWA was available.
programs, either in a z/VSE sublibrary or in the X'1' An asynchronous abend was detected (otherwise,
SVA. The second byte of X'code' can contain: the abend was synchronous or could not be
X'8' Program not found, or not in the SVA classified because there was no SDWA).
when required to be. System action: CICS continues normally and function ships
X'10' Internal failure while executing the this and subsequent remote file requests. Initialization is
function. retried after about 10 minutes. A system dump is taken for
X'14' An error was detected while validating the unexpected errors (X'ff' =X'01') and for abends (if dumps are
input for the function. requested for that abend code).
X'4' This indicates an I/O error or a storage allocation User response: The response depends on the reason for the
failure. Refer to "OS/390 API Return Codes" in failure as indicated in the first byte of the reason code:
section "VSE/Advanced Functions Codes & SVC X'01' Use the system dump to help you determine the
Errors" of z/VSE Messages and Codes - Volume 1 to cause of the problem.
interpret the OS/390 BLDL reason code X'code'. X'06' The most likely reason for a failure of the CICS SVC
X'5', X'6', X'7' call is that the data tables SVC module DFHDTSVC
Use the first digit of the reason code to determine could not be loaded, in which case the return code
the name of the module, then check the status of value is X'02'. If this is the case, check that the
that module. These errors imply that it is either not DFHDTSVC module is in the SVA. If the module is
the module which was supplied with CICS or that it in the correct location, then investigate why it could
has become corrupted. not be loaded; possibly there might be a hardware
Module: DFHFCFS fault on the disk. Another less likely value for the
XMEOUT Parameters: applid, X'code' return code is X'06', which implies that DFHDTSVC
Destination: Console has been relink-edited and not marked reentrant.
X'0E' This might indicate that the limit on the number of
OS/390 ENQs per address space has been reached,
DFHFC0415 applid Remote data tables cannot be accessed. or that another TCB running in this CICS address
Shared data table initialization has failed for space has already initialized as a requester of shared
reason X'code'. data table services.
Explanation: CICS is about to access a remote file resource. = X'80' When the reason code indicates that an abend has
However, shared data tables cannot be used to access any been detected, use the additional information
remote tables because CICS has been unable to initialize data provided in the reason code to find out what the
table services. The value of the reason code, X'code', provides abend was, and refer to information on that abend
further information about why this CICS region was unable to code to determine the cause.
Module: DFHFCFS

XMEOUT Parameters: applid, X'code' information about which module was being loaded, and what
Destination: Console went wrong with the attempt to load it.
The format of the reason code is X'mfrraaaa' in which m
DFHFC0416 applid Remote data tables cannot be accessed. identifies the module and f is a code for the type of failure.
Shared data table initialization has failed For some failures, rr contains the register 15 return code from
owing to a storage failure - reason code the failing macro call, and aaaa might contain additional
X'code'. information.
Explanation: CICS is about to access a remote file resource.
The value of X'm' can be:
However, a failure to get storage has prevented CICS from
X'3' DFHDTAOR
initializing shared data table services. The value of the reason
X'4' DFHDTCV
code, X'code', provides further information about the type of
storage which could not be obtained:
The values of f are:
The format of the reason code is X'ttnnnnnn' in which tt X'1' module not found by OS/390 LOAD
identifies the type of storage and, for some of the codes, X'2' an error was returned by the OS/390 LOAD macro.
nnnnnn gives the hexadecimal size in bytes of the storage The two bytes X'aaaa' of additional information in
which could not be obtained. For storage blocks whose length the reason code contain the completion code from
is fixed, the reason code does not usually report the size. the LOAD. X'rr' contains the register 15 return code
X'5' the module is not reentrant.
The values of X'tt' are:
X'6' the module had the wrong AMODE.
X'02' Private storage from subpool 0 for the shared data
table header block required for this CICS to act as a
this and subsequent remote file requests. Initialization is
data tables requester. This subpool is allocated in
retried after about 10 minutes.
partition GETVIS and the storage is owned by the
User response: The response depends on the reason for the
requesting task. The storage is fetch-protected.
failure as indicated in the second hex digit of the reason code:
X'09' Private storage from subpool 252 (key 0) for a region
X'1' Use the first hex digit to determine which module
anchor. This subpool is allocated in partition
could not be found, and ensure that it is in the
GETVIS and the storage is owned by the job step.
correct library.
The storage is not fetch-protected.
X'2' Refer to the documentation of the OS/390 LOAD
X'0A' System GETVIS storage from subpool 241 (key 0) for
macro in "OS/390 API Abend Codes" in section
a qualified subsystem block. This subpool is
"VSE/Advanced Functions Codes & SVC Errors" of
allocated in system GETVIS and the storage is
z/VSE Messages and Codes - Volume 1 to interpret the
owned by the system. The storage is not
return and completion codes reported in the
fetch-protected.
message. There might also be a message from the
X'0E' Private storage from subpool 230 (key 0) for a
OS/390 LOAD which explains the reason for the
connect header block. This subpool is allocated in
failure.
partition GETVIS and the storage is owned by the
X'5', X'6' Use the first digit of the reason code to determine
requesting task. The storage is not fetch-protected.
the name of the module, then check the status of
that module. This error implies that it is either not
this and subsequent remote file requests. Initialization is
the module which was supplied with CICS or that it
retried after about 10 minutes.
has become corrupted.
User response: The response depends on the type of storage
Module: DFHFCFS
indicated by the reason code.
If it indicates private storage, you should reconsider the
various partition size parameters which have been specified
on the CICS job. It might be necessary to take an SDUMP of
the CICS job in order to investigate the way in which VSE DFHFC0420 applid Shared access to data tables cannot be
storage has been allocated to the various subpools. provided by this CICS system because it has
not been registered as a shared data table
If it indicates System GETVIS storage, you should review the
server - reason code X'code'.
GETVIS size specified in the SET SDL statement on
initialization of the VSE system.
unable to do so because this CICS system has not been
Module: DFHFCFS
registered as a shared data table server. The value of the
XMEOUT Parameters: applid, X'code' reason code, X'code', provides further information about why
Destination: Console this CICS system was unable to register (LOGON) as a shared
data table server.
DFHFC0417 applid Remote data tables cannot be accessed. The format of the reason code is either: X'ffaaaaaa' in which ff
Shared data table initialization has failed is a value less than X'80' that identifies the type of failure, and
owing to a module loading failure - reason aaaaaa is additional information provided for some of the
code X'code'. failures; or, when an abnormal termination (ABEND) has
Explanation: CICS is about to access a remote file resource. occurred, X'axxxrrrr' in which a is a value greater than or
However, shared data tables cannot be used to access any equal to X'8' that categorizes the type of ABEND, rrrr contains
remote tables because a module loading failure prevents CICS any register 15 ABEND reason code, and xxx contains the
from initializing data table services. system or user completion code as three hexadecimal digits.
The value of the reason code, X'code', provides further When X'code' < X'80000000', the values of X'ff' are:

DFHFC0421
X'01' This code is reported when the data tables SVC X'11' This error might indicate that service has been
detects an unexpected error. applied which requires PTFs to both base CICS and
X'02' Another region within the VSE image with the same the shared data tables code, and only one has been
APPLID as this region is already registered (logged correctly updated, or that some corruption of the
on) as a shared data tables server. system has occurred, or that there is an error in
X'03' DFHDTRM has supplied the data tables SVC with CICS.
an invalid address for the PC vector, or the PC = X'80' When the reason code indicates that an ABEND has
vector specifies an invalid number of entry table been detected, use the additional information
entries (ETEs). In the latter case, X'aaaaaa' contains provided in the reason code to find out what the
the number of ETEs that were requested. ABEND was, and refer to information on that
X'06' An error was returned by the CICS SVC. The first ABEND code to determine the cause.
byte of the additional information, X'aa0000' is the Module: DFHFCFS
register 15 return code from the attempt to call the
CICS SVC. XMEOUT Parameters: applid, X'code'
X'0D' An error occurred when issuing an OS/390 ENQ to Destination: Console
ensure that, at any given time, only one server per
VSE system can be active for a given APPLID. The DFHFC0421 applid Shared access to data tables cannot be
first byte of the additional information, X'aa0000' provided by this CICS system because a
contains the return code from ENQ. storage failure has prevented it from
X'10' An attempt to create the environment for shared registering as a shared data table server -
data tables connect security checks has found that reason code X'code'.
the security environment has already been set up. Explanation: CICS is about to open a data table but cannot
X'11' There is a disparity between the actual version of do so because a failure to acquire storage has prevented the
the CICS security block and the version which was register of this CICS system as a shared data table server. The
used to assemble the shared data tables module value of the reason code, X'code', provides further information
DFHDTXS. about the type of storage which could not be obtained:
When X'code' = X'80000000', the values of X'a' are formed from The format of the reason code is X'ttnnnnnn' in which tt
combinations of: identifies the type of storage and, for some of the codes,
X'8' An ABEND was detected. nnnnnn gives the hexadecimal size in bytes of the storage
X'4' A user ABEND was detected, in which case xxx which could not be obtained. For storage blocks whose length
contains the hexadecimal equivalent of the user is fixed, the reason code does not usually report the size.
completion code (otherwise, xxx contains the The values of X'tt' are:
hexadecimal system completion code). X'01' private storage from subpool 230 (key 0) for a work
X'2' An ABEND was detected but could not be analyzed area used by the data tables SVC LOGON
fully because no SDWA was available. processing. This subpool is allocated in partition
X'1' An asynchronous ABEND was detected (otherwise, GETVIS and the storage is owned by the requesting
the abend was synchronous or could not be task. The storage is not fetch-protected.
classified because there was no SDWA). X'0A' System GETVIS storage from subpool 241 (key 0) for
System action: CICS continues normally and attempts to a qualified subsystem block. This subpool is
open the table for local use only. A system dump is taken for allocated in system GETVIS and the storage is
unexpected errors (X'ff' =X'01') and for ABENDs (if dumps are owned by the system. The storage is not
requested for that ABEND code). fetch-protected.
User response: The response depends on the reason for the X'0C' System GETVIS storage from subpool 241 (key 0) for
failure as indicated in the first byte of the reason code: a server element. This subpool is allocated in system
X'01' Use the system dump to help you determine the GETVIS and the storage is owned by the system.
cause of the problem. The storage is not fetch-protected.
X'02' There cannot be more than one region with a given X'0D' System GETVIS storage from subpool 241 (key 0) for
APPLID acting as a shared data table server within a security block. This subpool is allocated in system
the same VSE image. GETVIS and the storage is owned by the system.
X'03' This error might indicate that some corruption of the The storage is not fetch-protected.
system has occurred, or that there is an error in System action: CICS continues normally and attempts to
CICS code. open the table for local use only.
X'06' Server initialization should have been completed User response: The response depends on the type of storage
before LOGON is issued, so CICS SVC errors indicated by the reason code.
associated with the loading of the data tables SVC
module DFHDTSVC should not be encountered. If it indicates private storage then you should probably
Therefore this error probably indicates a logic reconsider the various partition size parameters which have
problem or corruption of your system. been specified on the CICS job. It might be necessary to take
X'0D' Refer to "OS/390 API Return Codes" in section an SDUMP of the CICS job in order to investigate the way in
"VSE/Advanced Functions Codes & SVC Errors" of which VSE storage has been allocated to the various subpools.
z/VSE Messages and Codes - Volume 1 to interpret the
If it indicates system GETVIS storage, you should review the
OS/390 ENQ return code reported in the additional
GETVIS size specified in the SET SDL statement on
information part of the reason code.
initialization of the VSE system.
X'10' This error might indicate that some corruption of the
Module: DFHFCFS
system has occurred, or that there is an error in
CICS code. XMEOUT Parameters: applid, X'code'

Destination: Console corruption of your system. You may need further assistance
from IBM to resolve this problem. See Part 4 of the CICS
DFHFC0422 applid Shared access to data tables cannot be Module: DFHFCFS
provided by this CICS system because a
module loading failure has prevented it from XMEOUT Parameters: applid, filename, X'code'
registering as a shared data table server - Destination: Console
reason code X'code'.
Explanation: CICS is about to open a data table but cannot
DFHFC0431 applid Data table open request for file filename
do so because a module loading failure has prevented the
has failed owing to a storage failure - reason
register of this CICS system as a shared data table server.
code X'code'.
The value of the reason code, X'code', provides further Explanation: CICS has attempted to create a data table for
information about which module was being loaded, and what file resource filename but has been unable to do so owing to a
went wrong with the attempt to load it. failure to get storage. There is insufficient storage above the
16MB line and the value of the reason code, X'code, provides
The format of the reason code is X'mfrraaaa' in which m further information about the type of storage which could not
identifies the module and f is a code for the type of failure. be obtained.
For some failures, rr contains the register 15 return code from
the failing macro call, and aaaa might contain additional The format of the reason code is X'ttnnnnnn in which tt
information. identifies the type of storage and, for some of the codes,
nnnnnn gives the hexadecimal size in bytes of the storage
The value of X'm' can be: which could not be obtained. For storage blocks whose length
X'5' DFHDTXS is fixed, the reason code does not usually report the size.
X'8' DFHDTSAN
The values of X'tt are:
The values of X'f' are: X'03' private storage from subpool 0 for a data table
X'1' module not found by OS/390 LOAD block. This subpool is allocated in partition GETVIS
X'2' an error was returned by the OS/390 LOAD macro. and the storage is owned by the requesting task. The
The two bytes X'aaaa' of additional information in storage is fetch-protected.
the reason code contain the abend code from the X'04' private storage from subpool 0 for a file block. This
OS/390 LOAD. X'rr' contains the register 15 reason subpool is allocated in partition GETVIS and the
code. storage is owned by the requesting task. The storage
X'5' the module is not reentrant. is fetch-protected.
X'6' the module had the wrong AMODE. X'05' private storage from subpool 0 for a pool of backout
System action: CICS continues normally and attempts to cells (the pool is created if the file being opened is
open the table for local use only. the first recoverable user-maintained table to be
User response: The response depends on the reason for the opened in this CICS run). This subpool is allocated
failure as indicated in the second hex digit of the reason code: in partition GETVIS and the storage is owned by the
X'1' Use the first hex digit to determine which module requesting task. The storage is fetch-protected.
could not be found, and ensure that it is in the X'06' private storage from subpool 0 for a pool of table
correct library. entry descriptor blocks, or for a descriptor block to
X'2' See "OS/390 API Abend Codes" in section be used when loading the table. This subpool is
"VSE/Advanced Functions Codes & SVC Errors" of allocated in partition GETVIS and the storage is
z/VSE Messages and Codes - Volume 1 to interpret the owned by the requesting task. The storage is
OS/390 LOAD abend and reason codes reported in fetch-protected.
the message. There might also be a message from X'07' private storage from subpool 0 for data table index
the OS/390 LOAD which explains the reason for the storage. This subpool is allocated in partition
failure. GETVIS and the storage is owned by the requesting
X'5', X'6' Use the first digit of the reason code to determine task. The storage is fetch-protected.
the name of the module, then check the status of X'08' storage for a pool of data table records in the z/VSE
that module. This error implies that it is either not data space
the module which was supplied with CICS or that it System action: CICS continues normally. This message is
has become corrupted in some way. followed either by message DFHFC0931 or by DFHFC0932.
Module: DFHFCFS The following message indicates the action taken for the table
involved.
XMEOUT Parameters: applid, X'code' User response: The response depends on the type of storage
Destination: Console indicated by the reason code.
If it indicates private storage then you should probably
DFHFC0430 applid Data table open request for file filename reconsider the various partition size parameters which have
has failed for reason X'code'. been specified on the CICS job. It might be necessary to take
Explanation: CICS has attempted to create a data table for an SDUMP of the CICS job in order to investigate the way in
file resource filename but has been unable to do so. which VSE storage has been allocated to the various subpools.
System action: CICS continues normally. This message is
followed either by message DFHFC0931 or by DFHFC0932. If it indicates data space storage then check whether the size
The following message indicates the action taken for the of data spaces in this VSE system has been limited by use of
specified table. the SYSDEF DSPACE command.
User response: This indicates an internal error or a Module: DFHFCFS

XMEOUT Parameters: applid, filename, X'code' X'01' Use the system dump to help you determine the
Destination: Console cause of the problem.
X'06' Requester initialization should have been completed
before CONNECT is issued, so CICS SVC errors
DFHFC0435 applid Data table access request for remote associated with the loading of the data tables SVC
file filename has failed for reason X'code'. module DFHDTSVC should not be encountered.
Explanation: An error has occurred while the requesting Therefore this error probably indicates a logic
region was attempting to establish a connection to the remote problem or corruption of your system.
file filename owned by the serving region. The value of the X'07' Some changes to your system configuration should
reason code, X'code', provides further information about why be made, as this requesting region is trying to access
CICS was unable to connect to the remote file. too many shared data tables owned by other
The format of the reason code is either: X'ffaaaaaa' in which ff regions. It is necessary either to reduce the number
is a value less than X'80' that identifies the type of failure, and of remote files being used, or to split the requesting
aaaaaa is additional information provided for some of the CICS region into a number of smaller regions.
failures; or, when an abnormal termination (ABEND) has X'0A' This indicates corruption of subpool 0 storage in the
occurred, X'axxxrrrr' in which a is a value greater than or server region.
equal to X'8' that categorizes the type of ABEND, rrrr contains X'0B' This indicates that either the requesting region
any register 15 ABEND reason code, and xxx contains the contains more than 232 - 1 remote file definitions, all
system or user completion code as three hexadecimal digits. of which refer to the same file in the server region,
or that storage has been corrupted.
When X'code' < X'80000000', the values of X'ff' are: X'0C' Same response as X'07'.
X'01' An unexpected failure occurred. This code is X'0F' Refer to "OS/390 API Return Codes" in section
reported when the data tables SVC detects an error "VSE/Advanced Functions Codes & SVC Errors" of
which should never occur. z/VSE Messages and Codes - Volume 1 to interpret the
X'06' An error was returned by the CICS SVC. The first OS/390 ENQ return code reported in the additional
byte of the additional information, aa0000, is the information part of the reason code.
register 15 return code from the attempt to call the = X'80' When the reason code indicates that an ABEND has
CICS SVC. been detected, use the additional information
X'07' The connection index returned by the data tables provided in the reason code to find out what the
SVC exceeds the maximum value supported by the ABEND was, and refer to information on that
calling module (220 - 1). ABEND code to determine the cause.
X'0A' The scan of the chain of files owned by the serving Module: DFHFCFS
region has failed because there is a permanently
invalid entry on the chain which indicates that the XMEOUT Parameters: applid, filename, X'code'
chain has become damaged. Destination: Console
X'0B' The number of connections by this requesting CICS
region to the remote file is already at the allowed DFHFC0436 applid Data table access request for remote
maximum (232 - 1). file filename has failed because of a storage
X'0C' The vector which records details of all connections failure - reason code X'code'.
to shared data tables by this requesting CICS region Explanation: CICS has attempted to access the remote file
needs expanding, but this would cause it to equal or resource filename but cannot do so because of a failure to get
exceed a size of 16MB.
storage.
X'0F' An attempt to serialize with termination of the
server has failed because the number of OS/390 The value of the reason code, X'code', provides further
ENQs has reached the address space limit. The first information about the type of storage which could not be
byte of the additional information, X'aa0000', obtained:
contains the return code from the ENQ.
The format of the reason code is X'ttnnnnnn' in which tt
identifies the type of storage and, for some of the codes,
When X'code' = X'80000000', the values of X'a' are formed from
nnnnnn gives the hexadecimal size in bytes of the storage
combinations of:
which could not be obtained. For storage blocks whose length
X'8' An ABEND was detected. is fixed, the reason code does not usually report the size.
X'4' A user ABEND was detected, in which case xxx
contains the hexadecimal equivalent of the user The values of X'tt' are:
completion code (otherwise, xxx contains the X'01' Private storage from subpool 230 (key 0) for a work
hexadecimal system completion code). area used by module DFHDTXS or for a work area
X'2' An ABEND was detected but could not be fully used by data tables SVC CONNECT processing. This
analyzed because no SDWA was available. subpool is allocated in partition GETVIS and the
X'1' An asynchronous ABEND was detected (otherwise, storage is owned by the requesting task. The storage
the abend was synchronous or could not be is not fetch-protected.
classified because there was no SDWA). X'0F' Private storage from subpool 230 (key 0) for a
System action: CICS continues normally and function ships connect vector. This subpool is allocated in partition
this and subsequent remote file requests. Use of shared tables GETVIS and the storage is owned by the requesting
is retried after about 10 minutes. A system dump is taken for task. The storage is not fetch-protected.
unexpected errors (X'ff' =X'01') and for ABENDs (if dumps are System action: CICS continues normally and function ships
requested for that ABEND code). this and subsequent remote file requests. Use of shared tables
User response: The response depends on the reason for the is retried after about 10 minutes.
failure as indicated in the first byte of the reason code:

User response: The response depends on the type of storage region size parameters which have been specified on the CICS
indicated by the reason code. job. It may be necessary to take an SDUMP of the CICS job in
order to investigate the way in which VSE storage has been
As it indicates private storage, you should probably reconsider allocated to the various subpools.
the various region size parameters which have been specified Module: DFHFCFS
on the CICS job. It might be necessary to take an SDUMP of
the CICS job in order to investigate the way in which VSE XMEOUT Parameters: applid, filename, X'code'
storage has been allocated to the various subpools. Destination: Console
Module: DFHFCFS
XMEOUT Parameters: applid, filename, X'code' DFHFC0445 applid Data table disconnect request for
Destination: Console remote file filename has failed for reason code.
Explanation: CICS has attempted to disconnect from the
remote data table filename but has been unable to do so.
DFHFC0440 applid Data table close request for file filename
has failed for reason X'code'. An error has occurred while the requesting region was
Explanation: CICS has attempted to close a data table for file attempting to break the connection to the remote file filename
resource filename but has been unable to do so. owned by the serving region. The value of the reason code,
System action: CICS continues normally. The table is treated X'code', provides further information about why CICS was
as having been closed. unable to disconnect from the remote file.
A system dump is taken for unexpected errors (X'ff' =X'01') The format of the reason code is either: X'ffaaaaaa' in which ff
and for abends (if dumps are requested for that abend code). is a value less than X'80' that identifies the type of failure, and
User response: The response depends on the reason for the aaaaaa is additional information provided for some of the
failure as indicated in the first byte of the reason code: failures; or, when an abnormal termination (ABEND) has
X'01' Use the system dump to help you determine the occurred, X'axxxrrrr' in which a is a value greater than or
cause of the problem. equal to X'8' that categorizes the type of ABEND, rrrr contains
X'06' Server initialization should have been completed any register 15 ABEND reason code, and xxx contains the
before LOGON is issued, so CICS SVC errors system or user completion code as three hexadecimal digits.
module DFHDTSVC should not be encountered. When X'code' < X'80000000', the values of X'ff' are:
Therefore this error probably indicates a logic X'01' An unexpected failure occurred. This code is
problem or corruption of your system. reported when the data tables SVC detects an error
X'09' The function code (service type) and qualifier which should never occur.
(options) reported in the reason code can be used to X'06' An error was returned by the CICS SVC. The first
determine which ALESERV request was being byte of the additional information, aa0000, is the
attempted. Refer to the VSE ALESERV register 15 return code from the attempt to call the
documentation in the z/VSE System Macros Reference CICS SVC.
to interpret the function code, qualifier, and register
15 return code reported in the reason code. When X'code' = X'80000000', the values of X'a' are formed from
= X'80' When the reason code indicates that an ABEND has combinations of:
been detected, use the additional information X'8' An ABEND was detected.
provided in the reason code to find out what the X'4' A user ABEND was detected, in which case xxx
ABEND was, and refer to information on that abend contains the hexadecimal equivalent of the user
code to determine the cause. completion code (otherwise, xxx contains the
Module: DFHFCFS hexadecimal system completion code).
X'2' An ABEND was detected but could not be analyzed
XMEOUT Parameters: applid, filename, X'code' fully because no SDWA was available.
Destination: Console X'1' An asynchronous ABEND was detected (otherwise,
the abend was synchronous or could not be
classified because there was no SDWA).
DFHFC0441 applid Data table close request for file filename
System action: CICS continues normally. The table is treated
has failed owing to a storage failure - reason
as having been disconnected from the requesting CICS system.
code X'code'.
A system dump is taken for unexpected errors (X'ff' =X'01')
Explanation: CICS has attempted to close a data table for file
and for ABENDs (if dumps are requested for that ABEND
resource filename but has been unable to do so owing to a
code).
failure to release storage.
User response: The response depends on the reason for the
The format of the reason code is X'ttnnnnnn' in which tt failure as indicated in the first byte of the reason code:
identifies the type of storage and, for some of the codes, X'01' Use the system dump to help you determine the
nnnnnn gives the hexadecimal size in bytes of the storage cause of the problem.
which could not be obtained. For storage blocks whose length X'06' Requester initialization should have been completed
is fixed, the reason code does not usually report the size. before DISCONNECT is issued, so CICS SVC errors
The values of X'tt' are: module DFHDTSVC should not be encountered.
X'14' private storage from subpool 252 (key 0) for a new Therefore this error probably indicates a logic
ALET list section problem or corruption of your system.
System action: CICS continues normally. The table is treated = X'80' When the reason code indicates that an ABEND has
as having been closed. been detected, use the additional information
User response: You should probably reconsider the various provided in the reason code to find out what the

ABEND was, and refer to information on that

DFHFC0921 applid Open of file fileid failed. Batch backout
ABEND code to determine the cause.
needed. Error codes: eeee,cccc,dddd
Module: DFHFCFS
Explanation: It was not possible to open file fileid since the
XMEOUT Parameters: applid, filename, code base cluster block was found to have the 'Backout Failed' flag
Destination: Console set on. A batch backout utility should be run to correct the
base cluster data, and then the flag must be set off via a SET
DSNAME(....) NORMAL command.
DFHFC0446 applid Data table disconnect request for
remote file filename has failed because of a The value of eeee is 8512, and this represents the CICS internal
storage failure - reason code X'code'. error code.
Explanation: CICS has attempted to disconnect from the
The values of cccc and dddd represent VSAM codes, and these
remote data table filename but has been unable to do so owing
are zero.
to a failure to release storage.
System action: The file remains closed.
System action: CICS continues normally. The table is treated
User response: If the file is not the CSD, run a batch backout
as having been disconnected from the requesting CICS system.
utility, check the data in the base cluster, and issue a SET
User response: This indicates an internal error or a
DSNAME(....) NORMAL command.
corruption of the system. You need further assistance from
IBM to resolve this problem. See Part 4 of the CICS Problem If the file is the CSD, run a batch backout utility, delete and
Determination Guide for guidance on how to proceed. redefine the CICS global catalog (DFHGCD). This forces a cold
Module: DFHFCFS start.
Module: DFHFCFS
XMEOUT Parameters: applid, filename, X'code'
Destination: Console XMEOUT Parameters: applid, fileid,eeee, cccc, dddd
DFHFC0490 applid Unable to use data table for file

filename. DFHFC0922A applid Base data set closed, batch backout
Explanation: The data set to which file filename relates has an needed for base dsname
associated data table but CICS is unable to make use of the Explanation: This message is preceded by messages
table data owing to a lack of storage. DFHFC4600 and DFHFC4601 or by messages DFHFC5712 and
System action: CICS continues normally. Performance of DFHFC5713 which have been issued because file backout has
read-only accesses to the file is degraded because records been unable to back-out uncommitted changes made to this
cannot be retrieved from the table. base cluster data set.
User response: Ensure that there is sufficient storage in the
All files open against this data set have now been closed (or
CICS region outside the EDSA.
are in a 'close requested' state).
See the CICS Shared Data Tables Guide for further guidance.
A special 'end' type of 'Backout Failed' record has been written
Module: DFHFCFS
to the system journal to inform a batch backout utility of this
XMEOUT Parameters: applid, filename fact. The base cluster control block has been flagged 'Backout
Destination: Console Failed'. You cannot open a file against this base cluster data
set until the flag has been reset via a CEMT or EXEC CICS
SET DSNAME(base) NORMAL command. You may now
DFHFC0920 applid Open of empty file filename failed. switch the system log, archive it, and backout the
VSAM codes - eeee,rrrr,cccc uncommitted changes offline from CICS.
Explanation: CICS file control issued an open command for System action: The system continues as normal.
VSAM file filename but the command failed with VSAM return User response: Use the CEMT INQUIRE DSNAME FAILED
code cccc. The CICS internal error code eeee has a value of 8509 command to check if any other data sets are in a 'Backout
and rrrr is the return code in register 15. Failed' or a 'Backout Failing' state. If any are in a 'Backout
This open failure is probably caused by the file not being Failing' state, wait until they change to a 'Backout Failed' state
loaded before use by CICS. (that is, when all files open against them are closed). You
System action: CICS continues processing with file filename should then switch the system log and archive it, so that it can
closed and its state UNENABLED. Any transaction attempting be used in an offline backout utility run.
to use this file is sent a NOTOPEN condition. Module: DFHFCBF
Message DFHME0116 is normally produced containing the XMEOUT Parameters: applid, base dsname
VSAM issues a console error message.

User response: Check whether the file has been loaded DFHFC0931 applid OPEN of data table name failed for
before being accessed by CICS. This condition is probably the reason n.
result of a user error in passing an empty file to CICS. Explanation: CICS was unable to OPEN the user-maintained
data table name for reason n, where n may have one of the
For the meaning of the VSAM return code, see section following values:
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2. 1 The data table support initialization module
Module: DFHFCFS DFHDTINT could not be loaded.
2 A data table support module other than DFHDTINT
XMEOUT Parameters: applid, filename, eeee, rrrr, cccc
could not be loaded.

3 The source data set for the data table is not a KSDS
DFHFC0934 applid OPEN of data table name1 was
base data set.
incomplete. Data table name2 already open
4 The data table OPEN module DFHDTOC failed.
with same source.
System action: The data table remains closed and is
Explanation: CICS was unable to treat data table name1 as a
DISABLED. CICS processing continues.
CICS-maintained data table because the data set to be used as
User response: The appropriate user response depends on
its source was already in use as the source of the
the reason code n as follows:
CICS-maintained data table name2.
1 Check that the data table feature has been installed
System action: CICS opens the data table's source data set
in your system, and that DFHDTINT is present in
for access as a normal VSAM data set, but file name1 is able to
the library.
access the CICS-maintained table created as a result of
2 Look for an VSE console message indicating failure
opening name2. CICS processing continues.
to load module DFHDTxxx. Ensure that this module
User response: Investigate the reason why this clash has
is present in the library.
occurred. You may have misspelled a name, or you may not
3 Check whether the data table has been associated
have intended for the tables to be open concurrently, or one
with the intended source data set.
table may have been associated with the wrong data set by
4 Check whether the total storage necessary to run
either the JCL or the DSNAME parameter of the RDO FILE
data tables and any other functions exceeds the total
resource definition or the DFHFCT TYPE=CICSTABLE entry.
private area for the VSE task.
Module: DFHFCFS
Module: DFHFCFS
XMEOUT Parameters: applid, name1,name2
XMEOUT Parameters: applid, name,n
DFHFC0935 applid SHAREOPTIONS of the source for

DFHFC0932 applid OPEN of data table name was
data table name allow inconsistencies
incomplete for reason n.
between table and source.
Explanation: CICS was unable to treat name as a
Explanation: The cross region SHAREOPTION for the source
CICS-maintained data table for reason n.
data set associated with the data table name is 3 or 4, or the
System action: The data table's source data set is opened for
SHAREOPTION is 2 and the table is being opened only for
access as a normal VSAM data set, and no main storage table
read access. It is possible for another job in this VSE system to
is built. CICS processing continues.
update the source without notifying CICS. The result of this is
that the data table may no longer match the source data set.
the reason code n. Refer to message DFHFC0931 for a list of
System action: Opening and loading of the data table
reason codes and their appropriate user responses.
continues normally. CICS processing continues.
Urgent action is probably not necessary when this message User response: Check that the SHAREOPTION is specified
occurs, as no function has been lost. However, READ correctly.
performance may be adversely affected.
Note that source data set changes are reflected in the data
Module: DFHFCFS
table only when the changes are made by the CICS system
XMEOUT Parameters: applid, name,n which owns the table.
Destination: Console Module: DFHFCFS
XMEOUT Parameters: applid, name
DFHFC0933 applid FREEMAIN failure detected during Destination: Console
CLOSE of data table name.
Explanation: An OS/390 FREEMAIN, issued while CICS was
DFHFC0936 applid Initiation of loading of data table name
attempting to release the storage associated with data table
has failed.
name, returned the error response R15=4. Some storage in the
Explanation: An attempt to initiate the table loading
CICS address space has not been freed. The error is probably
transaction for the data table name has failed.
the result of some earlier overwriting of data table control
System action: CICS processing continues. The effect this has
areas.
is that the table always appears to be in the process of being
System action: CICS closes data table name. CICS processing
loaded and the load completion exit, XDTLC, is not invoked.
continues.
User response: This condition does not adversely affect the One consequence of this is that the table is effectively demand
data tables function. However, if the problem recurs take a loaded. This means that an entry is only made in the table
system dump (SDUMP) as soon as possible after the when a transaction refers to it explicitly. A further
appearance of this message. For example, by means of a consequence is that, for user maintained tables, API requests
CEMT PERFORM SNAP command. (other than READ) always result in a LOADING condition.
Module: DFHFCFS User response: Take remedial action after determining the
cause of the failure from the trace of the OPEN request and
XMEOUT Parameters: applid, name
from any related messages and dumps. It may be that the
system action of leaving the table open, but not loaded,
adversely affects your application. For example, if the
application depends on being able to update a user
maintained table as soon as loading is complete. If so, closing
and reopening the data table may be successful as an
immediate response, if the problem was simply a temporary
lack of resources.

DFHFC0937 • DFHFC0943E
Module: DFHFCFS the add entry (from DASD) service, due to a failure
to get storage for the record.
XMEOUT Parameters: applid, name System action: The user exit XDTLC is invoked, if enabled,
Destination: Console unless file control has requested that the load be abandoned
(reason code X'FB'). The value of the UEPDTORC parameter
DFHFC0937 applid OPEN of name1 as a data table was not passed to the exit indicates that loading completed
possible. The file has been opened and will abnormally. No more records are loaded into the data table.
use data table name2 which has the same The user exit may ask for the file to be closed.
source. If the table is CICS-maintained, provided that the user exit has
Explanation: File name1 could not be opened as a NOT requested that the file be closed, those records which
CICS-maintained data table (CMT) because another CMT were not added are retrieved from the source data set to
name2 is already open for the source data set specified in the satisfy API requests.
file definition of name1. However, name1 is still able to benefit
from shared data tables support by accessing the already open If the table is user-maintained, requests to access any record
CMT. which was not added results in a "not found" response code. If
System action: name1 is opened as a normal CICS file, and the table has been closed, then API requests result in an
therefore automatically uses the existing data table name2 "unenabled" response code.
whenever possible.
CICS processing continues.
User response: This is not normally a problem, but you
should ensure that the data table name2 has the required
the reason code. User responses are as follows:
characteristics in terms of its maximum number of records and
X'FB' no action necessary
in the behavior of any data table user exits that refer to it.
X'FD' increase the size specified for the data table, either
Module: DFHFCFS
using the SIZE parameter in the FCT entry or the
XMEOUT Parameters: applid, name1,name2 MAXNUMRECS field in the RDO FILE definition
Destination: Console X'FE' increase the available storage above the 16MB line.
Module: DFHDTLDX
DFHFC0940I date time applid CICS data table load has XMEOUT Parameters: date, time,applid, name, X'xx'
started for data table name. Destination: Console and Transient Data Queue CSFL
Explanation: CICS file control has detected that an open
request has been issued for data table name, and a task has
DFHFC0943E date time applid CICS data table load has
been attached to load the data table.
terminated abnormally for data table name,
System action: CICS processing continues.
reason code = X'xx'.
Explanation: The CICS task that is loading data table name
Module: DFHDTLDX
has received an unexpected return code from CICS file control
XMEOUT Parameters: date, time,applid, name while browsing the source data set. The reason code X'xx'
Destination: CSFL should be one of the following.
X'02' ILLOGIC—A VSAM error which does not fall into
one of the other categories.
DFHFC0941I date time applid CICS data table load has X'0C' NOTOPEN—The file is CLOSED and UNENABLED,
completed successfully for data table name. or still open and in use, but a CLOSE request has
Explanation: The task that was attached to load the data been received.
table name has successfully completed loading. X'0D' DISABLED—The file is disabled.
System action: The user exit XDTLC is invoked, if enabled, X'80' IOERR—I/O error.
with the parameter UEPDTORC set to indicate a successful System action: The user exit XDTLC is invoked, if enabled,
load. CICS processing continues. with the parameter UEPDTORC set to indicate that loading
User response: None. completed abnormally. No more records are loaded into the
Module: DFHDTLDX data table. The user exit may ask for the file to be closed.
XMEOUT Parameters: date, time,applid, name If the table is CICS-maintained, provided that the user exit has
Destination: CSFL NOT requested that the file be closed, those records which
were not added are retrieved from the source data set to
satisfy API requests.
terminated abnormally for data table name, If the table is user maintained, requests to access any record
reason code = X'xx'. which was not added results in a "not found" response code. If
Explanation: The CICS task that is loading data table name the table has been closed, API requests result in an
has received a reason code X'xx', where X'xx' has one of the "unenabled" response code.
following values:
X'FB' CICS file control has requested that the data table CICS processing continues.
load be abandoned. This may occur, for example, if User response: Investigate the reason for the return code
a close request has been made against the data table from CICS file control. For further information about the
X'FD' an attempt has been made to add more entries to reason code, see the description of exception conditions for the
the data table than the maximum specified in the STARTBR and READNEXT commands, in the CICS Application
table definition Programming Reference.
X'FE' a shortage of virtual storage has been reported by Module: DFHDTLDX
XMEOUT Parameters: date, time,applid, name, X'xx'

DFHFC0945E • DFHFC0948E
Destination: Console and Transient Data Queue CSFL symptom string for this problem.
User response: Determine the cause of the failure of the
domain call using the diagnostic information provided by file
DFHFC0945E date time applid CICS data table load has control.
terminated abnormally for data table name. Module: DFHDTLDX
Explanation: The special CICS transaction that was loading
data table name has detected an abnormal termination. XMEOUT Parameters: date, time,applid, name, n
System action: Depending on the cause of this abnormal Destination: Console and Transient Data Queue CSFL
termination, CICS may produce either a system dump or a
transaction dump.
The user exit XDTLC is invoked, if enabled, with the failed to close data table name, a call to FCFS
parameter UEPDTORC set to indicate that loading completed has failed for reason code = n.
abnormally. CICS then terminates the loading transaction with Explanation: The CICS task that is loading data table name
abend code AFCM. No more records are loaded into the data has failed while trying to close the file at the request of an exit
table. The user exit may ask for the file to be closed. program invoked at exit point XDTLC. The value of reason
code n indicates the type of failure as follows:
If the table is CICS-maintained, provided that the user exit has 1. Response from FCFS was INVALID.
NOT requested that the file be closed, those records which 2. Response from FCFS was DISASTER.
were not added, are retrieved from the source data set to 3. Response from FCFS was PURGED.
satisfy API requests. 4. FCFS failed for some unexpected reason.
If the table is user-maintained, requests to access any record System action: CICS terminates the loading transaction with
which was not added result in a "not found" response code. If abend code AFCM.
the table has been closed, then API requests result in an Message DFHME0116 is normally produced containing the
"unenabled" response code. symptom string for this problem.
CICS processing continues. User response: It is unlikely that the user exit invoked at the
User response: Look at the system log for related CICS XDTLC exit point would request that the file should be closed
messages to determine the original abend detected by the unless a previous problem had occurred with the load.
loading transaction. Refer to the description of abend code Determine the cause of any such previous problem by
AFCM for further information about the cause of the original checking for earlier messages which may have been issued
termination. referring to data table name. Diagnostic information provided
by file control may be used to investigate the failure of the
For more information on how to determine system problems, close file call.
refer to the CICS Problem Determination Guide.
Module: DFHDTLDX CICS processing continues.
XMEOUT Parameters: date, time,applid, name Report the details of the symptom string given in message
Destination: Console and Transient Data Queue CSFL DFHME0116.
Module: DFHDTLDX
DFHFC0946E date time applid CICS data table load has XMEOUT Parameters: date, time,applid, name, n
terminated abnormally for data table name, a Destination: Console and Transient Data Queue CSFL
call to FCFR has failed for reason code = n.
Explanation: The CICS task that is loading data table name DFHFC0948E date time applid CICS data table load for data
has failed while calling file control to browse the source data table name has failed to free storage, a call to
set. The value of the reason code n indicates the type of failure SMGF has failed for reason code = n.
as follows: Explanation: The CICS task that is loading data table name
1. Response from FCFR was INVALID. has failed while calling the storage manager to free storage.
2. Response from FCFR was DISASTER. The value of reason code n indicates the type of failure as
3. Response from FCFR was PURGED. follows:
4. FCFR failed for some unexpected reason. 1. Response from SMGF was INVALID.
System action: The user exit XDTLC is invoked, if enabled, 2. Response from SMGF was DISASTER.
with parameter UEPDTORC set to indicate that loading has 3. Response from SMGF was PURGED.
completed abnormally. CICS then terminates the loading 4. SMGF failed for some unexpected reason.
transaction with abend code AFCM. No more records are System action: CICS terminates the loading transaction with
loaded into the data table. The user exit may ask for the file to abend code AFCM.
be closed.
If the table is CICS-maintained, provided that the user exit has symptom string for this problem.
NOT requested that the file be closed, records which were not User response: This condition does not adversely affect the
added are retrieved from the source data set to satisfy API data tables function. It means that a small amount of above
requests. If the table is user-maintained, requests to access any the line storage, which was used for a parameter list, has not
record which was not added result in a "not found" response been freed. If this situation occurs regularly, determine the
code. If the table has been closed, API requests result in an cause of the failure of the storage manager FREEMAIN call by
"unenabled" response code. using the diagnostic information provided by the storage
CICS processing continues. manager domain.
Module: DFHDTLDX
XMEOUT Parameters: date, time,applid, name, n

Destination: Console and Transient Data Queue CSFL X'0438' A label for this file does not exist in the
label area
X'0460' The file id on a delete label request is
DFHFC0950 applid Warning. File filename Opened with incorrect
VSAM SHROPT 3 or 4. CICS cannot prevent
concurrent updates
For the last three codes. You need further assistance
Explanation: VSAM share options 3 and 4 permit updating
from IBM to resolve this problem. See Part 4 of the
of a data set from multiple regions. Under these
CICS Problem Determination Guide for guidance on
circumstances, CICS cannot prevent concurrent updates.
how to proceed.
The file is being opened for update against a data set defined 10 A z/VSE LABEL macro function failed. In this case
with share options 3 or 4, and the file has been defined with the additional return code has has two components:
the following automatic journaling options: Byte 1 is the LABEL macro function which failed
Byte 2 is LABEL macro return code for the failed
Either: JREQ=WU or WN if the file is defined using the FCT function
macro,
Or: JNLADD = BEFORE, AFTER, OR ALL if the file is defined Refer to the VSE/ESA IPL and Job Control Diagnosis
using RDO. Reference Manual for the meaning of these codes.
System action: The file is opened and a warning message is
issued. You need further assistance from IBM to resolve this problem.
User response: None. See Part 4 of the CICS Problem Determination Guide for
Module: DFHFCN guidance on how to proceed.
Module: DFHFCFS
Destination: Console XMEOUT Parameters: applid, filename, rrrr, cccc
DFHFC0951 applid Open of file filename failed. DSNAME

not available from JCL or FCT DFHFC0953 applid Open or close of file filename failed.
Explanation: A CICS attempt to open file filename failed CICS logic error eeee,cccc
because neither the JCL nor the FCT specified the data set Explanation: While processing a request to open or close file
name. filename, CICS detected an internal logic error in the file
control services program. The value of eeee identifies the error
CICS file control did not open file filename, because:
as follows:
1. At initialization time, the startup JCL did not include a
8105 The DFHFCFS set base dsname block failed. cccc is
DLBL statement, and
the return code from DFHFCFS.
2. The FCT does not contain a DSNAME parameter to enable
8302 Request to DFHFCN for a pool that is not in the
CICS to allocate the file dynamically.
FCT.
System action: CICS continues processing with file filename
8701 Request to DFHFCN is not OPEN or CLOSE.
closed and its state UNENABLED. Any transaction attempting
8704 Request to DFHFCL is not BUILD or DELETE.
to use this file is sent a NOTOPEN condition.
8705 Request to DFHFCL is for invalid pool number cccc.
User response: Before resubmitting the transaction, you must
8706 Request to DFHFCL is for pool number cccc that is
supply the data set name in the JCL or the FCT. You can set
not in the FCT.
the name in the FCT while CICS is running by using the
8707 DFHFCL failed to build BLDVRP parameters. cccc is
CEMT transaction or the EXEC CICS SET command or by
the pool number.
using the CEDA transaction to correct and reinstall the FCT
8798 Logic error at OPEN detected in DFHFCN at offset
entry.
cccc.
Module: DFHFCFS
System action: CICS terminates the task abnormally,
XMEOUT Parameters: applid, filename produces a dump and continues processing with the status of
Destination: Console file filename unchanged.
DFHFC0952 applid Dynamic allocation of file filename symptom string for this problem.
failed. Return code rrrr,cccc User response: This is probably a logic error in CICS. You
Explanation: While dynamically adding a label definition for should note, however, that terminating CICS with an
file filename, a failure occurred with return code cccc. rrrr is the immediate shutdown while opening or closing files may cause
additional return code in register 15. such logic errors to happen as a normal occurrence. This is
System action: CICS continues with file filename closed and because CICS terminated immediately without regard to
its state UNENABLED. Any transaction attempting to use this running tasks.
file is sent a NOTOPEN condition.
It is also possible for this error to occur if CICS has to
User response: The return code has the following meanings:
calculate parameters for the BLDVRP macro, (this happens if
4 The label could not be added. The additional return
you do not supply an LSR pool definition on either a RDO
code has the following meanings
LSRPOOL resource definition or a DFHFCT TYPE=SHRCTL
X'0204' Insufficient virtual storage available
macro). All attempts to access the VSAM catalog for files in
X'0238' The temporary label subarea for the
this LSR pool fail. Other messages are issued for the
partition is full
individual catalog failures.
X'0410' A label for this file already exists in the
Module: DFHFCFS
label area

XMEOUT Parameters: applid, filename, eeee, cccc

DFHFC0959 applid Open or close of file filename failed.
CICS detected an error. Return code - eeee,cccc
Explanation: CICS did not open/close file filename because
DFHFC0955 applid Associated data set is dataset the open/close VSE subtask failed. Possible causes of the
Explanation: This message follows DFHFC0952. It identifies failure include:
the VSAM data set referred to in that message. v VSE attempted to abend the task due to a failure in VSAM
System action: Processing continues in the way specified in or VSE code.
DFHFC0952. v A CICS logic failure in subtask code.
User response: Follow the user response for message v A transaction attempted to open or close a file during CICS
DFHFC0952. shutdown, after the subtask had terminated.
Module: DFHFCFS
cccc is the return code from DFHSKP. The value of eeee is as
XMEOUT Parameters: applid, dataset
follows:
8801 DFHSKP failure during RDJFCB call
8802 DFHSKP failure during ALLOCATE call
DFHFC0956 applid Open of file filename failed. VSAM 8803 DFHSKP failure during CDLOAD call
catalog error. Return code - eeee,cccc 8804 DFHSKP failure during DAM OPEN call
Explanation: While reading the VSAM catalog to open the 8805 DFHSKP failure during OPEN VSAM call
VSAM data set filename, CICS file control received the return 8806 DFHSKP failure during SHOWCAT call
code cccc from a SHOWCAT macro. The value of eeee is an 8807 DFHSKP failure during VSAM GET call
error code from DFHFCN as follows: 8808 DFHSKP failure during DAM CLOSE call
8112 SHOWCAT for the AIX® of a path failed. 8809 DFHSKP failure during VSAM CLOSE call
8113 SHOWCAT for the data component of a base failed. 880A DFHSKP failure during DEALLOCATE call
8116 SHOWCAT for the base of a path failed. 880C DFHSKP failure during VSAM OPEN call
8117 SHOWCAT for an upgrade member failed. 880D DFHSKP failure during VSAM CLOSE call
System action: CICS writes a system dump, and continues 880D DFHSKP failure during ALLOCATE call
processing, with file filename closed and its state 880E DFHSKP failure during DEALLOCATE call
UNENABLED. Any transaction attempting to use this file is 8816 DFHSKP failure during FCL RDJFCB call.
sent a NOTOPEN condition. System action: CICS terminates the task abnormally, takes a
system dump, and continues processing with the status of file
Message DFHME0116 is normally produced containing the filename unchanged.
User response: For the meaning of the return code, see If the return code from DFHSKP is 001C, dynamically
section "VSE/VSAM Codes" in z/VSE Messages and Codes - allocated data sets might not be deallocated and the LSR pool
Volume 2. might not be deleted.
Module: DFHFCFS Message DFHME0116 is normally produced containing the
XMEOUT Parameters: applid, filename, eeee, cccc symptom string for this problem.
Destination: Console User response: This is probably a logic error in CICS or
another IBM program. You should note, however, that
terminating CICS with an immediate shutdown while opening
DFHFC0958 applid Open of file filename failed. VSAM or closing files may cause such logic errors to happen as a
resource usage conflict with open file normal occurrence. This is because CICS terminated
Explanation: CICS did not open file filename because it found immediately without regard to running tasks.
that its access method control block (ACB) specified a different
buffer/string resource (NSR or LSR pool) from that specified You may need further assistance from IBM to resolve this
by another ACB that is already open for the same base cluster. problem. See Part 4 of the CICS Problem Determination Guide
VSAM provides integrity for different ACBs open for the same Module: DFHFCFS
base cluster only if they use the same buffer/string resource.
System action: CICS writes a system dump and continues XMEOUT Parameters: applid, filename, eeee, cccc
processing with file filename closed and its state UNENABLED. Destination: Console
Any transaction attempting to use this file is sent a NOTOPEN
condition. DFHFC0960 applid Open of file filename failed. Unable to
User response: Determine the correct buffer/string resource build its LSR pool n. Return code - cccc
and change the FCT. Explanation: CICS has requested VSAM to build the local
Alternatively, if you specify DSNSHR=UPDATE in the FCT shared resource (LSR) pool specified in the FCT entry for file
and open the file for read only, CICS permits the use of filename. However, VSAM was unable to complete the request.
different buffer/string resources because no integrity exposure n is the pool number, and cccc is the VSAM BLDVRP return
exists. code.
Module: DFHFCFS System action: CICS continues processing with file filename
XMEOUT Parameters: applid, filename to use this file is sent a NOTOPEN condition.
Note: The first time this error occurs, CICS writes a system
dump before continuing.

Message DFHME0116 is normally produced containing the processing with the pool still in existence.
User response: For the meaning of the BLDVRP return code,
see the VSE/VSAM User's Guide and Application Programming
User response: For the meaning of the DLVRP return code,
manual.
Module: DFHFCFS
manual.
XMEOUT Parameters: applid, filename, n, cccc Module: DFHFCFS
XMEOUT Parameters: applid, n,cccc
DFHFC0961 date time applid Calculation of LSR pool n
parameters incomplete. Filename filename has
DFHFC0964 applid Open of file filename failed. VSAM
no DSNAME
codes - eeee,rrrr,cccc
Explanation: While dynamically calculating the parameters
Explanation: CICS file control issued an open for a VSAM
for the local shared resource pool (LSR) n, CICS found an FCT
file, filename. The open has failed with VSAM return code, cccc.
entry for which no DSNAME exists (either the FCT entry has
eeee has a value of 8502 and represents the CICS internal error
no DSNAME, or no DLBL statement exists in the CICS startup
code and rrrr is the return code in register 15.
job stream).
System action: CICS processing continues. System action: CICS continues processing, with file filename
Without a DSNAME, CICS cannot use the VSAM catalog to to use this file is sent a NOTOPEN condition.
determine the file attributes. Therefore, in the LSR calculation,
CICS uses the number of strings specified in the STRNO Message DFHME0116 is normally produced containing the
parameter of the FCT entry.
User response: VSAM will have issued a console error
User response: Ensure that each FCT entry has either a
message. Use the VSAM message and the VSAM return code
DSNAME, or a DLBL statement corresponding to its
DATASET name in the CICS startup job stream. in the CICS message to solve the problem.
Module: DFHFCFS For the meaning of the VSAM return code, see section
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2.
XMEOUT Parameters: date, time,applid, n, filename
Module: DFHFCFS
Destination: Console and Transient Data Queue CSMT
DFHFC0962 date time applid Calculation of LSR pool n
parameters incomplete for file filename.
VSAM catalog access error. Return code - cccc DFHFC0965 applid Open of DAM file filename failed
Explanation: While CICS was dynamically calculating the Explanation: CICS file control issued an open for a BDAM
parameters for the local shared resource (LSR) pool n, a VSAM file, filename. The open failed.
SHOWCAT or a VSAM catalog locate (using IKQVCAT) failed System action: CICS continues processing, with file filename
with return code cccc. Parameters for file filename are closed and with its state UNENABLED. Any transaction
incomplete. attempting to use this file is sent a NOTOPEN condition.
System action: CICS retains the accumulated LSR parameters
for file filename and continues processing. No further attempts Message DFHME0116 is normally produced containing the
at calculating LSR parameters for file filename are made. symptom string for this problem.
User response: DAM will have issued a console error
An exception trace is taken which identifies the failing VSAM message. Refer to the DAM message for further guidance to
request and its return code. solve the problem.
User response: For the meaning of a SHOWCAT return code, Module: DFHFCFS
manual, for the meaning of catalog locate return code see XMEOUT Parameters: applid, filename
section "IDCAMS Codes" in z/VSE Messages and Codes - Volume Destination: Console
2.
This error indicates a corrupted VSAM catalog. If you cannot DFHFC0966 applid Open of file filename failed. Unable to
restore the catalog, you will need further assistance from IBM position ESDS. Error codes: eeee,rrrr,cccc
to resolve the problem. See Part 4 of the CICS Problem Explanation: Before opening the VSAM ESDS file filename for
Determination Guide for guidance on how to proceed. output, CICS file control could not determine the end-of-data
Module: DFHFCL relative byte address (RBA) correctly. During the positioning
process, CICS may perform any of the following steps, each of
XMEOUT Parameters: date, time,applid, n, filename, cccc which can fail:
Destination: Console and Transient Data Queue CSMT v Determine which VSAM catalog owns the file.
v Open the base cluster for control interval (CI) processing
DFHFC0963 applid LSR pool n not deleted. Code - cccc v Read the last CI in the file
Explanation: CICS requested VSAM to delete a local shared v Determine the end-of-data in the file
resource (LSR) pool n. During processing of the request, a v Close the base cluster
VSAM DLVRP macro failed with return code cccc. (cccc is the v Dynamically deallocate the base cluster.
VSAM DLVRP return code.)
System action: CICS takes a system dump and continues The value of eeee in the message indicates the error or the
failing function as follows:

8503 Open base cluster. rrrr is the VSAM return code in

DFHFC0969 applid Close of file filename failed. CICS logic
register 15. cccc is the error field in the VSAM ACB.
error - 8799 rrrr,cccc
8504 Read last control interval (CI). rrrr is the VSAM
Explanation: While attempting to close file filename, CICS
return code in register 15. cccc is the FDBK field in
detected internal logic error 8799 in the file control services
the VSAM RPL.
program. cccc is the offset in DFHFCN at which the error
8505 Last CI middle of spanned record.
occurred.
8506 Close base cluster. rrrr is the VSAM return code in
System action: CICS terminates the task abnormally, takes a
register 15. cccc is the error field in the VSAM ACB.
system dump, and continues processing with the status of file
8507 Insufficient storage to get CI
filename unchanged.
8508 Dynamic allocation of base. rrrr is the VSE return
code in register 15. cccc is the VSAM return code. Message DFHME0116 is normally produced containing the
System action: CICS continues processing with file filename symptom string for this problem.
closed and its state UNENABLED. Any transaction attempting User response: You need further assistance from IBM to
to use this file is sent a NOTOPEN condition. resolve this problem. See Part 4 of the CICS Problem
Module: DFHFCFS
User response: For the meaning of the VSAM return codes, XMEOUT Parameters: applid, filename, rrrr, cccc
see section "VSE/VSAM Codes" in z/VSE Messages and Codes - Destination: Console
Volume 2.
CICS file control uses control interval processing when DFHFC0970 applid Warning. Recoverable file filename,
opening a VSAM ESDS. Therefore, ensure that you have Opened with VSAM SHAROPT 3 or 4. CICS
specified ACCESS(CONTROL) for the data set. cannot ensure integrity
Module: DFHFCFS Explanation: While opening the recoverable VSAM file
filename for update, CICS detected that it was defined with
SHAREOPTION 3 or 4, which allows updating from multiple
regions. CICS issues this message to warn you that it cannot
ensure data integrity.
DFHFC0967 applid Error detected while closing file System action: CICS opens file filename and continues
filename - VSAM codes rrrr,cccc processing.
Explanation: CICS file control issued a close for VSAM file User response: If this integrity exposure is acceptable, no
filename. The close failed with VSAM return code cccc. rrrr is further user action is required.
the return code in register 15.
If this integrity exposure is unplanned and unacceptable,
System action: CICS processing continues. CICS marks file
cancel CICS, redefine file filename with a different
filename as closed because VSAM will have closed the access
SHAREOPTION, and restart.
method control block (ACB).
Module: DFHFCFS
User response: Use the VSAM return code, cccc and the
preceding VSAM console message to determine the cause of
the problem. DFHFC0971 applid Open of file filename warning. In
positioning ESDS. Error codes: rrrr,cccc
For the meaning of the VSAM return code, see section
Explanation: Before opening the VSAM ESDS file filename for
output, CICS file control had to determine the end-of-data
Module: DFHFCFS
relative byte address (RBA). The positioning process involved
XMEOUT Parameters: applid, filename, rrrr, cccc the dynamic allocation and deallocation of the base cluster to
Destination: Console DLBL name DFHESDS. The deallocation failed.
The VSAM return code is cccc. rrrr is the additional return

DFHFC0968 applid Close of DAM file filename failed code in register 15.
Explanation: CICS file control issued a close for a DAM file, System action: CICS opens the file filename and continues
filename. The close failed. processing.
System action: CICS continues, with file filename still open.
symptom string for this problem. User response: For the meaning of the VSAM return codes,
User response: DAM will have issued a console error see section "VSE/VSAM Codes" in z/VSE Messages and Codes -
message. Use the DAM message to solve the problem. Volume 2.
Module: DFHFCFS Module: DFHFCFS
XMEOUT Parameters: applid, filename XMEOUT Parameters: applid, filename, rrrr, cccc

XMEOUT Parameters: applid, filename, rrrr, cccc

DFHFC0972 applid Open of file filename failed. VSAM
catalog entry not found, return code - 8111
cccc
Explanation: While opening a VSAM file filename, CICS file DFHFC0974 date time applid Calculation of LSR pool n
control attempted to retrieve information from the VSAM parameters incomplete for file filename.
catalog using the file name given in the JCL or the FCT. This VSAM catalog inconsistency - oooo
initial retrieval failed with VSAM return code cccc from the Explanation: While dynamically calculating local shared
SHOWCAT macro. 8111 indicates where within CICS file resource (LSR) parameters for file filename, CICS found that a
control the error was detected. VSAM SHOWCAT macro gave a normal return code, but the
System action: CICS continues processing with file filename object retrieved was logically incorrect. n is the pool number,
closed and its state UNENABLED. Any transaction attempting and oooo is the VSAM object type in error.
to use this file is sent a NOTOPEN condition. System action: CICS retains the accumulated LSR parameters
User response: You have probably specified DSNAME for file filename, and continues processing. No further attempts
incorrectly in the FCT. If DSNAME is correctly specified, see at calculating LSR parameters for file filename are made.
the explanation of the SHOWCAT return code in the User response: This error indicates a corrupted VSAM
VSE/VSAM User's Guide and Application Programming manual. catalog. If you cannot restore the catalog, you will need
Module: DFHFCFS further assistance from IBM. See Part 4 of the CICS Problem
XMEOUT Parameters: applid, filename, cccc
Module: DFHFCL
XMEOUT Parameters: date, time,applid, n, filename, oooo
DFHFC0973 applid Dynamic deallocation of file filename
failed. Return code - rrrr,cccc
Explanation: While closing file filename, CICS file control DFHFC0975 applid LSR pool n already exists
attempted to delete the label from the VSE label area. Explanation: CICS requested VSAM to build the local shared
(Deallocation). The attempt failed with return code, cccc. rrrr is resource (LSR) pool n. However, this pool already exists.
the additional return code in register 15. System action: CICS continues processing. If the existing
System action: CICS continues with the file closed, but still pool is unsuitable, subsequent file OPENs may fail.
allocated.
symptom string for this problem. User response: Examine the system console log and the LSR
User response: If you change the DSNAME in the FCT, and statistical data for pool creation and deletion times, and in the
then reopen the file in the same CICS run, CICS may open the case of the log, for possible pool delete failures. (The simplest
original data set. and most likely reason for this error is the failure of a
previous attempt to delete pool n.)
The return code has the following meanings:
Module: DFHFCL
4 The label could not be deleted The additional return
code has the following meanings: XMEOUT Parameters: applid, n
X'0204' Insufficient virtual storage available Destination: Console
X'0238' The temporary label subarea for the
partition is full.
X'0410' A label for this file already exists in the DFHFC0976 applid File filename not opened. DSNAME =
label area. DUMMY
X'0438' A label for this file does not exist in the Explanation: CICS could not open file filename, because the
label area. DSNAME in the DLBL statement was DUMMY.
X'0460' The file id on a delete label request is System action: CICS continues processing with file filename
incorrect. closed and its state UNENABLED. Any transaction attempting
For the last three codes. You need further assistance User response: None.
from IBM to resolve this problem. See Part 4 of the Module: DFHFCN
CICS Problem Determination Guide for guidance on XMEOUT Parameters: applid, filename
how to proceed. Destination: Console
10 A z/VSE LABEL macro function failed. In this case
the additional return code has has two components:
Byte 1 is the LABEL macro function which failed DFHFC0977 applid Open of file filename failed. VSAM
Byte 2 is LABEL macro return code for the failed catalog error. Return code - eeee,cccc
function Explanation: While CICS was opening file filename and
retrieving information from the VSAM catalog, a catalog locate
Refer to the VSE/ESA IPL and Job Control Diagnosis function failed with return code cccc. eeee is the DFHFCN
Reference Manual for the meaning of these codes. return code, as follows:
8114 Catalog locate (using IKQVCAT) failed on index or
data.
8115 Catalog locate (using IKQVCAT) failed on base
cluster.
Module: DFHFCFS

to use this file is sent a NOTOPEN condition. symptom string for this problem.
User response: For the meaning of the return code, see User response: You need further assistance from IBM to
section "IDCAMS Codes" in z/VSE Messages and Codes - Volume resolve this problem. See Part 4 of the CICS Problem
2. Determination Guide for guidance on how to proceed.
Module: DFHFCFS Module: DFHFCM
XMEOUT Parameters: applid, filename, eeee, cccc XMEOUT Parameters: applid, filename, eeee, cccc
DFHFC0978 applid Open of file filename failed. VSAM DFHFC0982 applid Open of base for file filename failed.
catalog error. Return code - eeee VSAM codes - rrrr,cccc
Explanation: While CICS was opening file filename and Explanation: While trying to open the VSAM KSDS base of a
retrieving information from the VSAM catalog, the CICS file path through which a record insert has been requested for file
control open/close routine (DFHFCN) detected a CICS logic filename, CICS file control issued an OPEN which failed with
error. eeee is as follows: the VSAM error code cccc from the ACB. rrrr is the VSAM
8118 A VSAM catalog entry for a path does not have a return code in register 15.
base cluster or an AIX as its first association. System action: CICS takes a system dump and terminates the
8119 In a VSAM catalog entry for an AIX, either the data transaction abnormally.
association or the base cluster association is missing. User response: VSAM issues a console error message. Use
811A In a VSAM catalog entry for a base cluster, the data the VSAM message and the VSAM return code in the CICS
association or the index association is missing. message to solve the problem.
closed and its state UNENABLED. Any transaction attempting For the meaning of the VSAM return code, see section
to use this file is sent a NOTOPEN condition. "VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2.
User response: Obtain a VSAM LISTCAT listing for file Module: DFHFCM
filename. You need further assistance from IBM to resolve this XMEOUT Parameters: applid, filename, rrrr, cccc
problem. See Part 4 of the CICS Problem Determination Guide Destination: Console
Module: DFHFCFS
DFHFC0983 applid Close of base for file filename failed.
XMEOUT Parameters: applid, filename, eeee CICS logic error eeee,cccc
Destination: Console Explanation: While trying to close the VSAM KSDS base of a
path through which a record insert has been requested for file
DFHFC0979 date time applid LSR pool n parameters filename, CICS has detected an error. eeee is as follows:
incomplete for file filename Entry not found. 8E05 Failure in DFHFCM to close VSAM base. cccc is the
RC - rrrr error code from the VSAM ACB.
Explanation: While dynamically calculating VSAM local System action: CICS takes a system dump and continues
shared resource (LSR) parameters, CICS attempted to retrieve processing, with base left open.
information from the VSAM catalog using the data set name Message DFHME0116 is normally produced containing the
in the FCT entry for file filename. The catalog access failed symptom string for this problem.
with the VSAM return code rrrr from the SHOWCAT macro. User response: You need further assistance from IBM to
System action: CICS continues processing, but does not use resolve this problem. See Part 4 of the CICS Problem
any parameters for file filename in calculations for the LSR Determination Guide for guidance on how to proceed.
pool. Module: DFHFCM
User response: Ensure that you have correctly specified the
JCL for the file, and that the catalog containing the file is XMEOUT Parameters: applid, filename, eeee, cccc
included in the JCL. If these checks do not reveal the error, see Destination: Console
the meaning of the SHOWCAT return code, rrrr, in the
VSE/VSAM User's Guide and Application Programming manual.
DFHFC0986 applid Open of base for file filename failed.
Module: DFHFCFS
CICS detected error eeee,cccc
XMEOUT Parameters: date, time,applid, n, filename, rrrr Explanation: CICS did not open/close the base for file
Destination: CSMT filename because the open/close VSE subtask failed while
opening or closing the KSDS (VSAM key-sequenced data set)
base of a path through which a record insert had been
DFHFC0980 applid Open of base for file filename failed. requested.
CICS logic error eeee,cccc
Explanation: While trying to open the VSAM ESDS base of a Possible causes of the failure include:
path through which a record insert has been requested for file v VSE attempted to abend the task due to a failure in VSAM
filename, CICS has detected an internal logic error. eeee is as or VSE code.
follows: v A CICS logic failure in subtask code.
8E01 Request to DFHFCM is not OPEN or CLOSE. v A transaction attempted to open or close a file during CICS
8E99 Logic error during DFHFCM processing at offset shutdown, after the subtask had terminated.
cccc.
System action: CICS takes a system dump and terminates the cccc is the return code from DFHSKP. The value of eeee is as
transaction abnormally. follows:
8E11 DFHSKP failure on DFHFCM ALLOCATE call.

8E12 DFHSKP failure on DFHFCM OPEN call.

DFHFC0990 applid Open of file filename failed. Recovery
8E13 DFHSKP failure on DFHFCM CLOSE call.
specified, but the path is not in the upgrade
8E14 DFHSKP failure on DFHFCM DEALLOCATE call.
set. Base data set dsname
System action: CICS terminates the task abnormally, takes a
Explanation: An attempt was made to open a recoverable
system dump, and continues processing.
file, associated with a VSAM path over an alternate index, for
Message DFHME0116 is normally produced containing the update processing (SERVREQ=ADD, DELETE or UPDATE
symptom string for this problem. set). However, the alternate index is not in the upgrade set of
User response: This is a probably a logic error in CICS or the base. CICS detects this condition and does not attempt to
another IBM program. You need further assistance from IBM open the file.
to resolve this problem. See Part 4 of the CICS Problem
If the alternate index is not in the upgrade set of the base, any
updates made via the base are not reflected in the alternate
Module: DFHFCM
index and so updates made via the path may compromise
XMEOUT Parameters: applid, filename, eeee, cccc data integrity. Note the open of the path fails if
Destination: Console RECOVERY=ALL or RECOVERY=BACKOUTONLY is
specified on the path FCTE entry, or on the base data set.
DFHFC0987 applid Open of file filename failed: Not The base takes the recovery attributes of the first file to open
available for type of processing. VSAM codes for update against it since a cold start. Those attributes remain
- 0008, 00A8 in force on the data set, and consistency checks are performed
Explanation: When CICS attempted to open the VSAM file between the FCT entry and the data set at file open time.
filename, the OPEN failed with the VSAM return codes shown System action: CICS continues processing with file filename
in the message text. The probable reason for the failure is that closed and not enabled.
the data set is in use by another region or another ACB in the User response: Take the data set offline and redefine the
CICS region, and that the VSAM share options prohibit the alternate index with the UPGRADE option. Run a BLDINDEX
level of sharing needed to permit the OPEN. job to bring the alternate index up to date with the base data
System action: CICS continues processing, with the file left set and then retry the open of the file.
closed and its state UNENABLED. Any transaction attempting Module: DFHFCFS
XMEOUT Parameters: applid, filename, dsname
Message DFHME0116 is normally produced containing the Destination: Console
User response: If the data set is in use by another user, wait
DFHFC0991 applid Open of file filename failed. Recovery
until it is free and then retry the OPEN.
attributes conflict with those on the VSAM
If the problem recurs and you cannot resolve the problem, you data set - cccc. Base data set dsname
will need further assistance from IBM. See Part 4 of the CICS Explanation: An attempt was made to open a file filename for
Problem Determination Guide for guidance on how to proceed. update processing. (SERVREQ=ADD, DELETE or UPDATE
Module: DFHFCFS set), CICS detected that the recovery attributes on the file were
inconsistent with those in force on the VSAM base data set.
XMEOUT Parameters: applid, filename The file was not opened in order to maintain data integrity.
The data set takes the recovery attributes of the first file to
open for update against it since a cold start. Code cccc
DFHFC0988 applid Open of file filename failed. This data identifies the inconsistency found and takes the following
set type is not supported by CICS. values:
Explanation: An attempt to open file filename has failed 8514 Both the file and the data set have RECOVERY=ALL
because the file referenced a data set of a type not supported specified, but the forward recovery logs specified are
by CICS. different.
CICS File Control supports opening VSAM KSDS, ESDS and 8515 The data set has RECOVERY=BACKOUTONLY or
RRDS data sets, paths over KSDS and ESDS data sets, and RECOVERY=NONE specified, and the file is trying
DAM data sets. No other data set types are supported. For to open with RECOVERY=ALL.
example, CICS does not support opening a VSAM VRDS data 8516 The data set has RECOVERY=NONE specified. The
set. file is attempting to open with
System action: CICS continues processing with filename RECOVERY=BACKOUTONLY.
closed and its state UNENABLED. Any transaction attempting 851B The file specified RECOVERY=NONE or
to use this file is sent a NOTOPEN condition. BACKOUTONLY. The VSAM data set had
RECOVERY=ALL specified.
Message DFHME0116 is normally produced containing the 851C The file specified RECOVERY=NONE. The VSAM
symptom string for this problem. data set had BACKOUTONLY specified.
User response: You have probably specified DSNAME System action: CICS continues processing with file filename
incorrectly in the file definition. Correct the file definition. closed and not enabled.
Module: DFHFCFS User response: Ensure that files referencing the same VSAM
data set have the same recovery attributes specified.
Destination: Console Alter the FCT entries using the CEDA ALTER FILE command
and reinstall the group, or alter the FCT macro definition of
the file. Note that this reassembled FCT only takes effect at the
next CICS COLD start.

To nullify the recovery attribute set for the base data set, the An INQUIRE on the RECOVSTATUS for the data set from this
user can issue a CEMT SET DSNAME REMOVE or EXEC point onwards returns a NOTRECOVABLE response. The data
CICS SET DSNAME REMOVE command. This deletes the set is marked as not recoverable until the next CEMT SET
base cluster block, and leaves CICS with no record of prior DSNAME REMOVE, EXEC CICS SET DSNAME REMOVE
recovery settings for this VSAM data set. The first file to command or COLD START.
subsequently open against this data set causes a new base System action: CICS opens file filename and continues
cluster block to be built. If the file is opened for update processing using the recovery setting from the file definition
processing, the recovery attributes of this file are copied into to determine whether backout logging should be performed.
the base cluster block. User response: Ensure that it is correct for the backout
recovery attribute inconsistency to be ignored for this data set.
If you want to have files referencing the same VSAM data set
with different backout recovery attributes you should use If the backout recovery attribute inconsistency should not have
global user exit XFCNREC. been ignored, ensure that files referencing the same VSAM
Module: DFHFCFS data set have the same recovery attributes. If they do not,
either alter the FCT entries using the CEDA ALTER FILE
XMEOUT Parameters: applid, filename, cccc, dsname command and reinstall the group, or alter the FCT macro
Destination: Console definition of the file. Note that this reassembled FCT only
takes effect at the next CICS COLD start.
DFHFC0996 date time applid {Open | Close | Enable | To nullify the recovery attribute set for the base data set, issue
Disable} of file filename suppressed due to a CEMT SET DSNAME REMOVE or EXEC CICS SET
intervention of User Exit. DSNAME REMOVE command. This deletes the base cluster
Explanation: An open, close, enable or disable, request has block and leaves CICS with no record of prior recovery
been issued against the specified file. An exit program enabled settings for this VSAM data set. The first file to subsequently
at the global user exit point XFCSREQ in CICS file control has open against this data set causes a new base cluster block to
directed CICS not to carry out the request. be built. If the file is opened for update processing, the
System action: If the request being issued is an enable, recovery attributes of this file are copied into the base cluster
disable, or close request, the file state remains unchanged, that block.
is, it remains in the same state as before the request was Module: DFHFCN
issued.
XMEOUT Parameters: applid, filename, X'code', dsname
If the request is an open request, the state remains unchanged Destination: Console
unless the file was in a closed, enabled state. In this state, the
open request could be an implicit open request, (that is, the
file is being opened as part of a file API request). If it is an DFHFC0999 applid Open of BASE for file filename failed.
implicit open request, the file state is changed to closed CICS logic error eeee,cccc
unenabled to ensure the file API request is halted, and a Explanation: While trying to open the VSAM KSDS base of a
NOTOPEN condition is returned to the application. path through which a record insert has been requested for file
User response: Examine the reason for the command being filename, CICS has detected an error. eeee is as follows:
suppressed. This is installation specific. 8E03 Failure in LABEL macro request (GETLBL for file)
Module: DFHFCFS 8E06 Failure in LABEL macro request (GETLBL for
catalog)
XMEOUT Parameters: date, time,applid, {1=Open,
2=Close,3=Enable, 4=Disable}, filename
cccc is the LABEL macro return code.
System action: CICS takes a system dump and terminates the
transaction abnormally.
DFHFC0998 applid User exit XFCNREC is causing file
filename to be opened even though a file
recovery inconsistency of type X'code' exists.
User response: See "System Function Return Codes" in
CICS cannot guarantee data integrity for base
section "VSE/Advanced Functions Codes & SVC Errors" of
data set dsname
z/VSE Messages and Codes - Volume 1 for diagnostic information
Explanation: An attempt was made to open file filename for
about the LABEL macro return code cccc. You need further
update processing, (SERVREQ=ADD, DELETE or UPDATE),
assistance from IBM to resolve this problem. See Part 4 of the
and CICS detected that the backout recovery attribute on the
file was inconsistent with that on the VSAM base data set.
proceed.
Normally CICS would fail the open on detection of an
Module: DFHFCM
inconsistency. However, a program running at user exit
XFCNREC has indicated that the open should continue even XMEOUT Parameters: applid, filename, eeee, cccc
though an inconsistency has been detected. CICS can no Destination: Console
longer guarantee the integrity of the data on the associated
data set. Code X'code' identifies the inconsistency and can take
one of the following values: DFHFC2813 applid Program DFHRCEX cannot be found.
X'8516' The data set has RECOVERY=NONE specified. The Explanation: This is a disastrous error. The DC link has failed
file is attempting to open with to link to DFHRCEX during FC initialization.
RECOVERY=BACKOUTONLY. System action: CICS setup is abnormally terminated with a
X'851C' The file specified RECOVERY=NONE. The VSAM dump.
data set had BACKOUTONLY specified. User response: Find out why DFHRCEX could not be
located.
Module: DFHFCBP


DFHFC4602 date time applid DTB failed - Batch backout
needed after base data set closed.
Trans=tranid File=filename Task=taskid.
DFHFC4600 applid DTB failed - Batch backout needed Explanation: This is the same as message DFHFC4600, except
after base data set closed. Trans=tranid that this message is sent to transient data queue CSFL,
File=filename Task=taskid. whereas message DFHFC4600 is sent to the console.
Explanation: DTB (dynamic transaction backout) was unable
Dynamic transaction backout (DTB) was unable to back out
to back-out uncommitted changes made to a VSAM data set
uncommitted changes made to a VSAM data set via file
via file filename by task taskid servicing transaction code tranid.
filename by task taskid servicing transaction code tranid. This
This message is followed by message DFHFC4601 which message is followed by message DFHFC4603 which includes
includes the base cluster/path data set names involved. The the base cluster/path data set names involved. The base
base cluster control block has been flagged 'Backout Failing'. cluster control block has been flagged 'Backout Failing'. You
You cannot open a file against this base cluster data set until cannot open a file against this base cluster data set until the
the flag has been reset via a CEMT or EXEC CICS SET flag has been reset via a CEMT or EXEC CICS SET
DSNAME(base) NORMAL command. A corresponding DSNAME(base) NORMAL.
message, DFHFC4602, is sent to CSFL. System action: Processing continues.
User response: Wait for message DFHFC4603 which tells you
Note: This message can also be issued when a record is the base/path data set names involved, and also for message
encountered on the data set with a length that does not match DFHFC0922A which tells you when all files open against this
the fixed length of the file as defined to CICS. data set have been closed. Then use the CEMT INQUIRE
System action: The system continues as normal. DSNAME FAILED command to check if any other data sets
User response: You should wait for message DFHFC4601 are in a 'Backout Failed' or a 'Backout Failing' state. If any are
which tells you the base/path data set names involved, and in a 'Backout Failing' state, wait until they change to a
also for message DFHFC0922A which tells you when all files 'Backout Failed' state (that is, when all files open against them
open against this data set have been closed. You should then are closed). You should then switch the system log and archive
issue a CEMT INQUIRE DSNAME FAILED command to check it, so that it can be used in an offline backout utility run.
if any other data sets are in a 'Backout Failed' or a 'Backout Module: DFHDBP
Failing' state. If any are in a 'Backout Failing' state, wait until XMEOUT Parameters: date, time,applid, tranid, filename, taskid
they change to a 'Backout Failed' state (that is, when all files Destination: CSFL
open against them are closed). You should then switch the
system log and archive it so that it can be used in an offline
backout utility run. DFHFC4603 date time applid Base=base dsname Path=path
dsname
If the backout failure is due to a record on the data set with a Explanation: This message tells you the base cluster and path
length that does not match the fixed length of the file as data set names for which dynamic transaction backout (DTB)
defined to CICS, scan the data set for all records with a length could not perform back-out.
different from the fixed length of the file and adjust them
accordingly. This message follows message DFHFC4602 which tells you the
Module: DFHDBP transaction code, file name, and task number involved.
Message DFHFC4601 is sent to the console.
XMEOUT Parameters: applid, tranid,filename, taskid System action: The system continues as normal.
Destination: Console User response: See message DFHFC4602 for details of the
transaction code, file name, and task number involved.
DFHFC4601 applid Base=base dsname Path=path dsname You should wait for message DFHFC0922A which tells you
Explanation: This message tells you the base cluster and path when all files open against this data set have been closed. You
data set names for which dynamic transaction backout (DTB) should then use the CEMT INQUIRE DSNAME FAILED
could not perform back-out. This message follows message command to check if any other data sets are in a 'Backout
DFHFC4600 which tells you the transaction code, file name, Failed' or a 'Backout Failing' state. If any are in a 'Backout
and task number involved. Failing' state, wait until they change to a 'Backout Failed' state
System action: The system continues as normal. (that is, when all files open against them are closed). You
User response: See message DFHFC4600 for details of should then:
transaction code, file name and task number. 1. Switch the system log using CEMT SET JOURNAL (01)
You should wait for message DFHFC0922A which tells you ADVANCE,
when all files open against this data set have been closed. 2. Archive the log.
Then use the CEMT INQUIRE DSNAME FAILED command to 3. Run the batch backout utility.
check if any other data sets are in a 'Backout Failed' or a Module: DFHDBP
'Backout Failing' state. If any are in a 'Backout Failing' state, XMEOUT Parameters: date, time,applid, base dsname, path
wait until they change to a 'Backout Failed' state (that is, when dsname
all files open against them are closed). Then switch the system Destination: CSFL
log and archive it, so that it can be used in an offline backout
utility run.
Module: DFHDBP
XMEOUT Parameters: applid, base dsname, path dsname


DFHFC4604 applid DTB failed for DAM data set. DFHFC5712 applid Backout failed. Batch backout needed
Trans=tranid File=filename Task=taskid. after base d/s closed. Trans=tranid
Explanation: DTB (dynamic transaction backout) was unable File=filename Task=taskid.
to back-out uncommitted changes made to a DAM data set via Explanation: During an emergency restart, file back out was
file filename by transaction tranid. unable to back out uncommitted changes made to a VSAM
System action: The system continues as normal. data set via file filename by task taskid servicing transaction
User response: Close all the files open against the DAM data code tranid.
set using CEMT SET FILE CLOSED, and backout any
uncommitted changes offline. This message is followed by message DFHFC5713 which
includes the base cluster/path data set names involved. The
Module: DFHDBP
base cluster control block has been flagged 'Backout Failing'.
XMEOUT Parameters: applid, tranid,filename, taskid You cannot open a file against this base cluster data set until
Destination: Console the flag has been reset via a CEMT or EXEC CICS SET
DSNAME(base) NORMAL.
System action: Processing continues
DFHFC4605 date time applid DTB failed for DAM data set. User response: Wait for message DFHFC5713 which tells you
Trans=tranid File=filename Task=taskid. the base/path data set names involved, and also for message
Explanation: DTB (dynamic transaction backout) was unable DFHFC0922A which tells you when all files open against this
to back-out uncommitted changes made to a DAM data set via data set have been closed.
file filename by transaction tranid.
System action: The system continues as normal. Then use the CEMT INQUIRE DSNAME FAILED command to
User response: You should close all files open against the check whether any other data sets are in a 'Backout Failed' or
DAM data set using CEMT SET FILE CLOSED, and backout a 'Backout Failing' state. If any are in a 'Backout Failing' state,
any uncommitted changes offline. wait until they change to a 'Backout Failed' state (that is, when
Module: DFHDBP all files open against them are closed). Then switch the system
log and archive it, so that it can be used in an offline backout
XMEOUT Parameters: date, time,applid, tranid, filename, taskid utility run.
Destination: CSFL Module: DFHFCBP
XMEOUT Parameters: applid, tranid,filename, taskid
DFHFC5707 applid Backout data present for file filename Destination: Console
but no FCT entry exists.
Explanation: During emergency restart, the file filename could
not be found by the table manager in the FCT that has been DFHFC5713 applid Base=base dsname Path=path dsname
restored from the CICS global catalog. Explanation: This message tells you the base cluster and path
System action: CICS checks if any other files that need data set names for which file backout was not performed
backout are missing from the FCT and issues this message for during an emergency restart.
them. This is a severe error which could impact data integrity
This message follows message DFHFC5712 which tells you the
and so CICS issues message DFHFC0002 and terminates
transaction code, file name, and task number involved.
abnormally with a dump.
User response: Either the global catalog that was used to
User response: Wait for message DFHFC0922A which tells
restore the FCT on emergency restart, or the log that provides
you when all files open against this data set have been closed.
the backout records, has been corrupted.
Then use the CEMT INQUIRE DSNAME FAILED command to
Use the dump to investigate and correct the cause of this
check whether any other data sets are in a 'Backout Failed' or
failure before rerunning the emergency restart.
a 'Backout Failing' state. If any are in a 'Backout Failing' state,
Module: DFHFCBP
wait until they change to a 'Backout Failed' state (that is, when
XMEOUT Parameters: applid, filename all files open against them are closed). You should then switch
Destination: Console the system log and archive it, so that it can be used in an
offline backout utility run.
Module: DFHFCBP
DFHFC5708D applid Error while opening file filename. Reply
'GO' or 'CANCEL'. XMEOUT Parameters: applid, base dsname, path dsname
Explanation: CICS detected an error while opening file Destination: Console
filename.
System action: The system waits for the operator to reply. If
DFHFC5714 date time applid Backout failed. Batch backout
the reply is 'GO', the initialization exit is given control. Upon
needed after base d/s closed. Trans=tranid
return, processing continues. If the reply is 'CANCEL', CICS
File=filename Task=taskid.
terminates abnormally with a dump and VSE user abend 0143.
Explanation: This message is the same as DFHFC5712, except
User response: Reply 'GO' or 'CANCEL'.
that this message is sent to transient data queue CSFL,
Module: DFHFCBP
whereas message DFHFC5712 is sent to the console.
During emergency restart, file backout was unable to back out
uncommitted changes made to a VSAM data set via file
filename by task taskid servicing transaction code tranid.
This message is followed by message DFHFC5715 which tell

you the base cluster/path data set names involved. The base

DFHFC5715 • DFHFC5740I
cluster control block has been flagged 'Backout Failing'. You

DFHFC5717 date time applid Backout failed for DAM data
cannot open a file against this base cluster data set until the
set. Trans=tranid File=filename Task=taskid.
flag has been reset via a CEMT or EXEC CICS SET
Explanation: This message is the same as DFHFC5716, except
DSNAME(base) NORMAL.
that this message is sent to transient data queue CSFL,
System action: The system continues as normal.
whereas message DFHFC5716 is sent to the console. During an
User response: Wait for message DFHFC5715 which tells you
emergency restart file backout was unable to back out
the base/path data set names involved, and also for message
uncommitted changes made to a DAM data set via file
DFHFC0922A which tells you when all files open against this
filename by transaction transaction.
data set have been closed.
Then use the CEMT INQUIRE DSNAME FAILED command to User response: Close all files open against the DAM data set.
check if any other data sets are in a 'Backout Failed' or a Back out any uncommitted changes offline.
'Backout Failing' state. If any are in a 'Backout Failing' state, Module: DFHFCBP
wait until they change to a 'Backout Failed' state (that is, when
XMEOUT Parameters: date, time,applid, tranid, filename, taskid
all files open against them are closed). You should then switch
Destination: CSFL
the system log and archive it, so that it can be used in an
offline backout utility run.
Module: DFHFCBP DFHFC5718 applid A failure has occurred while processing
the restart data set during file backout
XMEOUT Parameters: date, time,applid, tranid, filename, taskid
processing.
Destination: CSFL
Explanation: A serious problem has occurred with the restart
data set (DFHRSD). This is usually because a CONNECT, a
DFHFC5715 date time applid Base=base dsname Path=path START BROWSE, a GETNEXT or a DELETE command has
dsname failed.
Explanation: This message is the same as DFHFC5713, except System action: The system puts out a trace entry and a
that this message is sent to transient data queue CSFL, dump. CICS restart is abnormally terminated.
whereas message DFHFC5713 is sent to the console.
This message tells you the base cluster and path data set symptom string for this problem.
names for which file backout could not perform back out User response: Use the dump and the trace entry to
during an emergency restart. investigate the problem in the restart data set.
Module: DFHFCBP
This message follows message DFHFC5714 which tells you the
transaction code, file name, and task number involved. XMEOUT Parameter: applid
System action: The system continues as normal. Destination: Console
User response: Wait for message DFHFC0922A which tells
you when all files open against this data set have been closed.
DFHFC5719 date time applid A failure has occurred while
Then use the CEMT INQUIRE DSNAME FAILED command to processing the restart data set during file
check if any other data sets are in a 'Backout Failed' or a backout processing.
'Backout Failing' state. If any are in a 'Backout Failing' state, Explanation: A serious problem has occurred with the restart
wait until they change to a 'Backout Failed' state (that is, when data set(DFHRSD). This is usually because a CONNECT, a
all files open against them are closed). You should then switch START BROWSE, a GETNEXT or a DELETE command fails.
the system log and archive it, so that it can be used in an System action: The system puts out a trace entry and a
offline backout utility run. dump. CICS restart is abnormally terminated.
Module: DFHFCBP User response: Use the dump and the trace entry to
determine the problem in the restart data set.
XMEOUT Parameters: date, time,applid, base dsname, path Module: DFHFCBP
dsname
Destination: CSFL XMEOUT Parameters: date, time,applid
Destination: CSFL
DFHFC5716 applid Backout failed for DAM data set.

Trans=tranid File=fileid Task=taskid. DFHFC5740I applid File backout beginning.
Explanation: During an emergency restart, file backout was Explanation: During emergency restart, CICS issues this
unable to back out uncommitted changes made to a DAM message when the CICS module, DFHFCBP, starts processing.
data set via file filename by transaction tranid. DFHFCBP backs out changes to recoverable files that were
System action: The system continues as normal. made by in-flight tasks (that is, tasks that were incomplete
User response: You should close all files open against the when the preceding abnormal termination occurred).
DAM data set, and back out any uncommitted changes offline. System action: Processing continues.
Module: DFHFCBP User response: None.
Module: DFHFCBP
XMEOUT Parameters: applid, tranid,fileid, taskid
Destination: Console XMEOUT Parameter: applid

DFHFC5741I • DFHFE3307
System action: CICS termination continues.

DFHFC5741I applid No file backout required.
User response: In order to avoid repetition of this failure, try
to determine why the file was not closed from any other
message when the CICS module, DFHFCBP, finds no changes
DFHFCxxxx messages produced during termination.
to recoverable files that need to be backed out. DFHFCBP
Module: DFHFCSD
backs out changes to recoverable files that were made by
in-flight tasks (that is, tasks that were incomplete when the XMEOUT Parameters: applid, filename
preceding abnormal termination occurred). Destination: Console
Module: DFHFCBP DFHFC5820 applid Any files that are still open against the
base data set may need to be closed. File
XMEOUT Parameter: applid filename, data set dsname.
Destination: Console Explanation: File filename was the first file to open a
dynamically allocated data set dsname. This file is being closed
leaving one or more files still open against the same base data
DFHFC5742I applid File backout complete.
set. However, if one of these files requires secondary extents,
the request will fail with a CICS ILLOGIC error (EIBRCODE
message when the CICS module DFHFCBP finishes
X'08BA0000').
processing. DFHFCBP backs out changes to recoverable files
System action: Close processing completes normally.
that were made by in-flight tasks (that is, tasks that were
User response: To avoid this potential problem, you are
incomplete when the preceding abnormal termination
advised to close and reopen the files that remain open against
occurred).
the base data set. If you are unsure of the data set
associations, run a LISTCAT against the above base dataset to
produce a list of all associated data sets. Use CEMT INQ
Module: DFHFCBP
FILE(*) to identify which files are affected. All of these should
XMEOUT Parameter: applid be closed and reopened, for example, using the CEMT SET
Destination: Console FILE(file name) CLOSE and CEMT SET FILE(file name)
OPEN.
Module: DFHFCFS
DFHFC5804 applid File CLOSE failed during CICS
termination. File ' filename'. XMEOUT Parameters: applid, filename, dsname
Explanation: An attempt to close file filename during orderly Destination: Console
CICS termination has failed. This message is produced only as
a warning that this file could not be closed. Data integrity has
been maintained.
DFHFExxxx messages
Module: DFHFEP
DFHFE3301 Transaction complete
Explanation: The field engineering program, DFHFEP, which
was called by the field engineering transaction, CSFE, has
completed. DFHFE3304 Enter PRINT for character set, END to
System action: Other processing continues. terminate. All other data will be echoed.
User response: None. Explanation: This message is sent to the terminal when the
Module: DFHFEP CSFE transaction is started. It asks the engineer what action is
Destination: Terminal End User required from the field engineering program, DFHFEP.
System action: The task waits for a response.
User response: Enter PRINT to display the character set.
DFHFE3302 Invalid debug request
Explanation: The field engineering program, DFHFEP, which Enter END to terminate module DFHFEP.
was called by the field engineering transaction, CSFE, either
found a syntax error in the debug request, or found that the All other data typed in is echoed to the screen.
installed transaction definition option was invalid. Module: DFHFEP
System action: The task ends. Destination: Terminal End User
User response: Check for syntax errors or for an invalid
installed transaction definition option. Correct the errors and
DFHFE3307 Invalid option specified in request
reenter the request.
Explanation: The field engineering program, DFHFEP, which
Module: DFHFEP
was called by the field engineering transaction, CSFE, found
an error in one of the options specified in the request. Either
the specified option could not be found (for example, an
DFHFE3303 Invalid trace option invalid transaction definition) or it was an invalid type. CSFE
Explanation: The field engineering program, DFHFEP, which ends without completing the request.
was called by the field engineering transaction, CSFE, found a System action: The task ends.
syntax error in the trace request (ZCQTRACE). User response: Correct the error and reenter the request.
System action: The task ends. Module: DFHFEP
User response: Check for syntax errors. Correct the errors Destination: Terminal End User
and reenter the request.

DFHFE3308 • DFHIC0310
CSFE DEBUG,TRAP=OFF (to deactivate the current

DFHFE3308 Program DFHTRAP is not available - global
trap);
trap not activated
Explanation: CICS could not find the global trap exit CEMT SET PROGRAM(DFHTRAP) NEWCOPY (to update
program, DFHTRAP, during execution of the CICS field the disk trap known to CICS);
engineering transaction request, CSFE DEBUG,TRAP=ON. CSFE DEBUG,TRAP=ON (to activate the new version
System action: CICS continues with the global trap not of the trap).
activated.
User response: Ensure that DFHTRAP is defined in the You should use the global trap exit only in consultation with
processing program table and made available in the program an IBM support representative.
library. You should use the global trap exit only in Module: DFHFEP
consultation with an IBM support representative. Destination: Terminal End User
Module: DFHFEP
DFHFE3310 applid Program DFHTRAP is not available -
global trap not activated.
DFHFE3309 Global trap DFHTRAP is unusable following Explanation: CICS could not find the global trap exit
program check in exit program, DFHTRAP, during execution of the CICS field
Explanation: While executing a field engineering (FE) engineering transaction request, CSFE DEBUG,TRAP=ON.
transaction request to activate the global trap exit (CSFE
System action: CICS continues with the global trap not
DEBUG,TRAP=ON), the FE program, DFHFEP, has found that
activated.
the global trap exit program, DFHTRAP, is already active but
User response: Ensure that DFHTRAP is defined in the
marked unusable. This is because, when the trap was last
processing program table and made available in the program
used, a program check occurred in DFHTRAP. This error is
fully documented in message DFHTR1001. library. You should use the global trap exit only in
System action: CICS continues with the global trap still consultation with an IBM support representative.
marked unusable. Module: DFHFEP
User response: Refer to DFHTR1001 for more information. To XMEOUT Parameter: applid
replace the currently active but unusable version of DFHTRAP Destination: Console
by a new version from the CICS program library, issue the
following commands in the sequence:
DFHICxxxx messages
DFHIC0002 applid A severe error (code X'code') has DFHIC0200 date time applid Automatic transaction restart
occurred in module modname. for transaction tranid has failed.
Explanation: An error has been detected in module modname. Explanation: A STARTed nonterminal transaction is ending
The code X'code' is the exception trace point ID which abnormally and automatic transaction restart was requested
uniquely identifies what the error is and where it was via the user replaceable module DFHREST. A severe error
detected. occurred when CICS attempted to restart the transaction.
System action: An exception entry (code X'code' in the System action: Message DFHAP0002 with a dump is issued
message) is made in the trace table. A system dump is taken, for the severe error that caused the restart to fail. Abnormal
unless you have specifically suppressed dumps in the dump termination of the transaction for which restart was requested
table. continues. The transaction is not automatically restarted.
User response: Investigate the reason for the earlier severe
CICS continues unless you have specified in the dump table error. See message DFHAP0002 for further guidance. Restart
that CICS should terminate. the transaction manually if necessary.
Message DFHME0116 is normally produced containing the Module: DFHICXM
symptom string for this problem. XMEOUT Parameters: date, time,applid, tranid
User response: This indicates a possible error in CICS code. Destination: Console and Transient Data Queue CSMT
The severity of its impact depends on the importance of the
function being executed at the time of the error.
DFHIC0310 date time applid Unable to attach transaction -
tranid to terminal - termid
If the message occurs once and module modname is not crucial Explanation: An attempt was made to start transaction tranid
to the running of your CICS system, you may decide to on terminal termid as a result of a:
continue to run and bring CICS down at a convenient time to v START command, or
resolve the problem. v DFHIC TYPE=PUT macro, or
v DFHIC TYPE=INITIATE macro.
of module modname, you will need assistance. Bring CICS The attempt was rejected. The most likely cause is that, at the
down in a controlled shutdown and collect the dumps and time the attempt was made, the terminal was unknown in the
any relevant messages sent by the module identified in the system.
message. See Part 4 of the CICS Problem Determination Guide
for guidance on how to proceed. This message is also issued when:
Module: DFHEIIC v A START command is issued in an application owning
XMEOUT Parameters: applid, X'code',modname region (AOR) for a terminal that exists as a remote terminal
Destination: Console entry in the AOR, but the destination system ID associated
with the remote terminal has not been defined.

DFHIC0360 • DFHIC0802
v A START command is issued against a pipeline device, or

DFHIC0802 applid System clock inoperative. External
other device which is not eligible for ATI requests.
action required
System action: The request is deleted from the system.
Explanation: CICS execution is dependent on the continued
User response: Ensure that a valid terminal name is being
operation of the processor time-of-day clock. This warning
specified. If the name is valid, examine the trace (if one is
message is sent to the console operator during the execution
available) to determine why the attempt was rejected.
of the time adjustment program if the system detects a
Module: DFHICP
processor clock failure at that time. Immediate corrective
XMEOUT Parameters: date, time,applid, tranid, termid action (if possible) must be taken by the console operator, if
Destination: Console the clock has been disabled for any reason.
System action: CICS abnormally terminates after the
condition is detected.
DFHIC0360 date time applid An attempt to establish User response: The ability to enable or disable the
security for userid userid has failed. time-of-day clock is under the control of the console operator.
Transaction tranid cannot be started without a If the clock is disabled, it must be enabled immediately.
terminal. SAF codes are (X'safresp',X'safreas'). Module: DFHTAJP
ESM codes are (X'esmresp',X'esmreas').
Explanation: An attempt was made to establish security for XMEOUT Parameter: applid
userid userid but it was rejected by the external security Destination: Console
manager (ESM).
A time ordered request, such as an EXEC CICS START
command, required security to be established for the userid in
order to start the transaction tranid without a terminal.
System action: Security has not been established for the
userid. The attempt to start the transaction has failed.
User response: The response and reason codes (safresp and
safreas) returned by the system authorization facility (SAF),
and the response and reason codes (esmresp and esmreas)
returned by the external security manager (ESM) are those
issued by the RACROUTE REQUEST=VERIFY or RACROUTE
REQUEST=EXTRACT macros. For the meaning of the
response and reason codes see "BSM Return Codes" in section
Messages and Codes - Volume 1.
There may be further messages produced by CICS or the
external security manager (ESM) which provide more
information.
Module: DFHICXM
XMEOUT Parameters: date, time,applid, userid, tranid, X'safresp',
X'safreas', X'esmresp', X'esmreas'
Destination: CSCS
DFHIC0801 applid CICS time altered from hh.mm.sss to

hh.mm.sss - date dddddddd - relative day rrr
Explanation: This console message is printed when the
operating system-maintained time of day has been rolled back
(for example, when the operating system clock is reset to zero
at midnight). Where:
v hh.mm.sss is the time in hours minutes and tenths of a
second
v dddddddd is the current date in the format specified by the
DATFORM parameter in the system initialization table
v rrr is the day number relative to the day CICS was started.
System action: CICS has recognized the condition and
adjusted its own time of day to agree with that of the
operating system.
User response: None
Module: DFHTAJP
XMEOUT Parameters: applid, hh.mm.sss, hh.mm.sss, dddddddd,

rrr

DFHIR2122 • DFHIR3751
DFHIRxxxx messages
netname of each session that is still active, and additionally for
DFHIR2122 date time applid Intersystem session recovery.
EXCI sessions, the jobname, stepname, procname and the ID
Database changes found to be synchronized.
of the batch program communicating on that session.
Original failure details: Time=time. Remote
system=sysid. Intersystem terminal=termid. For EXCI sessions, a netname of GENERIC indicates a generic
Transaction=tranid. Task number=taskno. pipe. For the batch job information to appear in the message,
Operator terminal=termid. Operator=operid. at least one DPL request must have been issued on that
Unit of work ID=uowid session.
Explanation: An error occurred on an intersystem session System action: CICS continues to wait for the remaining
recovery which has now been successfully recovered and session(s) to close. This message is reissued at 30 second
resynchronized. This message is normally issued as a intervals, or until the last session is closed.
follow-up to message DFHZN2101, (which may have been User response: None, unless the delay in closedown appears
issued at the time of the failure if the session failed at a critical abnormally long. If this is the case, investigate why the
time during syncpoint processing). session(s) are still active. Take appropriate action to allow the
System action: Processing continues. session(s) to close.
User response: None. Module: DFHZDSP
Module: DFHCRR
XMEOUT Parameters: date, time,applid, time, sysid, termid, Destination: Console
tranid, taskno, termid,operid, uowid
Destination: CSMT
DFHIR3747 applid CONNECTION connid with
protocol(EXCI) has been connected to by a
DFHIR2123 date time applid Intersystem session recovery. NON-BATCH system. Connection set out of
Data base changes found to be out of sync. service.
Original failure details: Time=time. Remote Explanation: A CICS connection has been defined with the
system=sysid. Intersystem terminal=termid. protocol EXCI and an attempt has been made to connect to it
Transaction=tranid. Task number=taskno. by a non-batch system.
Operator terminal=termid. Operator=operid.
Unit of work ID=uowid There are two possible explanations for this message:
Explanation: This message is issued as a follow-up to v The non-batch system is attempting to communicate with
message DFHZN2101. The original failure information the wrong target connection definition.
provides a cross-reference. v The target connection definition has incorrectly been
System action: Processing continues. defined as an EXCI connection.
User response: Take user-defined action to resynchronize the System action: CICS sets the connection out of service.
local and remote databases. User response: Investigate and correct the relevant
Module: DFHCRR connection definitions and set back in service.
Module: DFHCRNP
XMEOUT Parameters: date, time,applid, time, sysid, termid,
tranid, taskno, termid,operid, uowid XMEOUT Parameters: applid, connid
Destination: CSMT Destination: Console
DFHIR2124 date time applid Intersystem session recovery. DFHIR3750 applid Unable to stop interregion
Error when data base changes may be out of communication session during startup
sync. Original failure details: Time=time. recovery.
Remote system=sysid. Intersystem Explanation: A request has been received as the result of an
terminal=termid. Transaction=tranid. Task abnormal termination to stop the interregion communication
number=taskno. Operator terminal=termid.
session during the startup recovery process. This request has
Operator=operid. Unit of work ID=uowid
failed.
Explanation: This message is issued as a follow-up to
System action: The session remains active.
message DFHZN2101. During session recovery, the system
User response: If the session must be stopped, you may have
was unable to determine whether database changes were out
of synchronization. to re-IPL. You need further assistance from IBM to resolve this
System action: Processing continues. problem. See Part 4 of the CICS Problem Determination Guide
User response: Make the necessary database enquiries to for guidance on how to proceed.
detect whether changes are synchronized. If they are not, take Module: DFHCRNP
user-defined action to resynchronize the databases. XMEOUT Parameter: applid
Module: DFHCRR
tranid, taskno, termid,operid, uowid
Destination: CSMT DFHIR3751 applid Unable to stop interregion
communication session during shutdown.
Explanation: A request has been received (by means of
DFHIR2321 applid MRO/IRC Communication being system termination, abnormal termination, or master terminal)
Terminated. Session(s) with the following to stop the interregion communication session during the
Netname(s) are still Active: shutdown process. This request has failed.
Explanation: CICS is attempting to close MRO/IRC System action: The session remains active.
communication. This message is normally followed by the User response: If the session must be stopped, you may have

to re-IPL. You need further assistance from IBM to resolve this and/or supply module DFHCRSP
problem. See Part 4 of the CICS Problem Determination Guide Module: DFHSIJ1
Module: DFHSTP
DFHIR3771 applid Unable to start interregion
communication because ESTAEX macro
DFHIR3760 applid Unable to break lines with interregion failed.
communication. (Modname: modname) Explanation: CICS issued an OS/390 ESTAEX macro that did
Explanation: A request has been made to shut down the not execute successfully, probably because storage for an
interregion session. This has caused module DFHZCX to issue ESTAEX control block (SCB) was not available.
a request to the interregion communication program to System action: The IRC session is not started.
terminate the association between CICS and the interregion User response: Correct the cause of ESTAEX failure.
communication program, but the request failed because of a Module: DFHSIJ1
system error. XMEOUT Parameter: applid
System action: Any running batch (EXCI client) programs are Destination: Console
left in the wait state, and should be canceled. Any CICS tasks
(in other CICS systems) that are in communication with this
system are also left in the wait state. These other CICS DFHIR3772 applid Error while attempting to start
systems should issue CEMT SET CONNECTION(sysid) interregion communication.
OUTSERVICE PURGE, where sysid is the CONNECTION Explanation: CICS has evidence that the IRC session has
name of the system for which DFHIR3760 was issued. Also, already started. This is probably because the previous session
any attempt to restart the interregion session (in the current or could not be stopped (see messages DFHIR3760 and
any subsequent CICS session) fails. DFHIR3765).
User response: To run further batch CICS interregion
communication, you must re-IPL. You will need further Note: The session, although apparently started, is not in a
assistance to resolve the underlying problem. See Part 4 of the usable state.
System action: The IRC session is not started.
proceed.
User response: Perform another IPL.
Module: DFHZIS2, DFHSTP
Module: DFHSIJ1
DFHIR3762 date time applid Inter-region activity now

complete DFHIR3773 applid Unable to start interregion
Explanation: A CEMT SET INTERREGION communication because the APPLID option
COMMUNICATION (IRC) CLOSED request was issued at the has a blank value.
master terminal. The IRC session is now complete. Explanation: Either the default value of applid (on DFHTCT
System action: Processing continues. TYPE=INITIAL, DFHSIT, override) must be used, or a value
User response: None. which is not a null value must be used.
Module: DFHCRNP System action: The IRC session is not started.
User response: Correct the applid value.
XMEOUT Parameters: date, time,applid Module: DFHSIJ1
Destination: CSMT
DFHIR3765 UNABLE TO STOP INTERREGION
COMMUNICATION SESSION AFTER
SYSTEM ABEND. DFHIR3775 applid Unable to start interregion
Explanation: A request has been received (by means of communication because short on storage.
system termination, abnormal termination, or master terminal) Explanation: Main storage is required to start the IRC
to stop the interregion session. This request has failed. session, but the storage is not available.
System action: The session remains active. System action: The IRC session is not started.
User response: If the session must be stopped, you may have User response: Wait until the storage condition has eased,
to re-IPL. You will need further assistance to resolve the
then issue a CEMT SET IRC OPEN command at the master
underlying problem. See Part 4 of the CICS Problem
terminal.
Module: DFHSIJ1
Module: DFHCRC
DFHIR3767 applid The interregion startup program
DFHCRSP is not present.
Explanation: Module DFHCRSP is required to start an IRC
session, but is missing from the CICS program library or has
no installed program definition.
User response: Install DFHCRSP definition (group DFHISC)

DFHIR3776 applid Unable to start interregion DFHIR3780 applid Unable to start interregion
communication because another CICS system communication. Return code=X'retcode',
of the same name is active. Reason code=X'rsncode'.
Explanation: A CICS system is named by its applid value. If Explanation: CICS attempted to establish itself as a user of
two CICS systems have the same applid value, the interregion the interregion communication (IRC) services, but the attempt
communication SVC cannot distinguish between the systems. failed.
Note: This situation may arise if a previous interregion
communication (IRC) session could not be stopped; see symptom string for this problem.
message DFHIR3760. In this case, the IRC SVC would
User response: The return code (which might include an
consider that the new session conflicted with the old error qualifier) and reason code (if any) correspond to a
(unstoppable) session.
number of possible errors. See Interregion Control Blocks (IRC)
in the CICS Data Areas manual for a complete list of return
User response: Use a different generic applid for each CICS codes, error qualifiers and reason codes. (The names of all the
system.
return codes, error qualifiers and reason codes start with
Module: DFHSIJ1 IRERR, IRERQ and IRRSN respectively.) Check that the
XMEOUT Parameter: applid following requirements are satisfied:
Destination: Console v A copy of DFHIRP providing an adequate level of function
is present in the shared virtual area (SVA).
v CICS has been defined as an operating system subsystem.
DFHIR3777 applid The interregion communication table is v There has been no SURROGAT security violation preventing
full. the region logging on to the CICS interregion program
Explanation: The interregion communication SVC's user table (IRP).
is full.
System action: The IRC session is not started. If the message is issued when all of these conditions have
User response: When there are fewer batch-sharing programs been met, you will need further assistance from IBM. See Part
running, issue CEMT SET IRC OPEN at the master terminal. 4 of the CICS Problem Determination Guide for guidance on how
Module: DFHSIJ1 to proceed.
Module: DFHSIJ1
Destination: Console XMEOUT Parameters: applid, X'retcode', X'rsncode'
DFHIR3778 applid Insufficient storage is available for

interregion communication blocks. DFHIR3781 applid Unable to start interregion
Explanation: There is insufficient system GETVIS storage communication because task CSNC cannot be
available for the IRC control blocks. attached.
System action: The IRC session is not started. Explanation: Definitions for CSNC or DFHCRNP have not
User response: Ensure that sufficient storage is available. Use been installed, or DFHCRNP was not found in a sublibrary of
the VSE SVA command to increase the size of the system the LIBDEF search chain for the CICS job.
GETVIS area. See the z/VSE System Control Statements manual System action: The IRC session is not started.
for further information on the SVA command. User response: Make CSNC or DFHCRNP available.
Module: DFHSIJ1 Module: DFHSIJ1

DFHIR3779 applid Insufficient storage is available for DFHIR3783 date time applid Transaction transid termid
interregion communication subsystem blocks. termid - Connected transaction abended with
Explanation: There is insufficient storage for the control message xxxx
blocks required by IRC. Storage is required from the CICS Explanation: Transaction transid was connected to a
region but from outside the CICS DSA. transaction in another CICS system, through an MRO link.
System action: The IRC session is not started. This other transaction has abnormally terminated with the
User response: Ensure that sufficient storage is available. given message, causing the local transaction to abnormally
Either increase the size of the CICS partition or reduce the size terminate.
of the CICS DSA's to allocate more program GETVIS. System action: The transaction abnormally terminates.
Module: DFHSIJ1 User response: Correct the cause of the abend in the
connected transaction.
XMEOUT Parameter: applid Module: DFHZCX
XMEOUT Parameters: date, time,applid, transid, termid, xxxx
Destination: CSMT

See Interregion Control Blocks (IRC) in the CICS Data Areas

DFHIR3785 applid Interregion control task CSNC abend.
manual for a complete list of return codes (which might
Interregion activity will be abnormally
include an error qualifier) and reason codes. (The names of all
terminated.
the return codes, error qualifiers and reason codes start with
Explanation: CSNC is abnormally terminated.
IRERR, IRERQ and IRRSN respectively.)
System action: CSNC is abnormally terminated with a
system dump. All tasks using MRO links to other systems are
abnormally terminated. CICS also abends all tasks in other A possible reason for this message is that the applid of the
CICS regions (including non-CICS jobs using the external system on which the message appears does not match the
CICS interface (EXCI)) that are currently communicating with NETNAME on any of the system entries defined in system
this system. sysid.
User response: You need further assistance from IBM to System action: The connection is not established. Any
resolve this problem. See Part 4 of the CICS Problem existing connections are not affected.
Determination Guide for guidance on how to proceed. Message DFHME0116 is normally produced containing the
Following this abend it is not possible to use IRC within this symptom string for this problem.
CICS system. CICS must be restarted before IRC can be used. User response: If an applid or a NETNAME mismatch has
Module: DFHCRNP occurred, correct the error and retry.
XMEOUT Parameter: applid If a mismatch is not the cause of the error, you may need
Destination: Console further assistance from IBM. See Part 4 of the CICS Problem
Module: DFHCRNP
DFHIR3786 applid Unable to start interregion
XMEOUT Parameters: date, time,applid, X'retcode',
communication because module DFHSCTE
X'rsncode',sysid
could not be found.
Destination: CSMT
Explanation: The IRC module DFHIRP attempted to load
DFHSCTE, but the module was not in the SVA.
System action: The interregion communication session is not DFHIR3789 date time applid SEND/RECEIVE mismatch
started. between TCT system entries for this system
User response: Ensure that DFHSCTE is available. and system sysid
Module: DFHSIJ1 Explanation:
XMEOUT Parameter: applid v The number of send sessions defined in this system's TCT
Destination: Console entry for system sysid does not equal the number of receive
sessions defined in system sysid's TCT entry for this system,
or
DFHIR3787 applid Unable to start inter-region v The number of receive sessions defined in this system's TCT
communication because there are no IRC entry for system sysid does not equal the number of send
entries in the system. sessions defined in system sysid's TCT entry for this system.
Explanation: No valid MRO connections have been installed. System action: As many sessions as possible are established.
System action: Interregion communication is not started. User response: Alter one or both DFHTCT entries.
User response: If IRC is required, install appropriate MRO Module: DFHCRNP
connection and session definitions. See the CICS Resource
Definition Guide for guidance on defining MRO connections XMEOUT Parameters: date, time,applid, sysid
and sessions. If IRC is not required, run with system Destination: CSMT
initialization option IRCSTRT=NO.
Module: DFHSIJ1 DFHIR3790 date time applid Unable to connect to system
XMEOUT Parameter: applid sysid for security reasons
Destination: Console Explanation: The TYPE=SYSTEM entry in system sysid's
DFHTCT entry for this system contained a SECURITYNAME
operand that did not match the real external security ID of
DFHIR3788 date time applid Unexpected failure (return this system, or the ID was unknown to IRC.
code=X'retcode', reason code=X'rsncode') trying System action: The connection is not established.
to establish connection to system sysid
Explanation: CICS could not establish a link to system sysid, Message DFHME0116 is normally produced containing the
even though system sysid is available for communication. symptom string for this problem.
User response: Discuss with the system programmer
The return code X'code' returned by the interregion responsible for system sysid.
communication SVC is one of the following: Module: DFHCRNP
12 The secondary to primary converter has failed.
68 The secondary system is not in the primary LCB XMEOUT Parameters: date, time,applid, sysid
92 The system being connected to is not logged on. Destination: CSMT
100 A GETVIS failed for CSB storage.
104 The secondary system is not in the primary LCB.
The system is not defined.
108 No primary CCB. Check the definitions for the
connection.
112 The secondary system is in quiesce mode.

DFHIR3791 applid Unable to start interregion DFHIR3799 applid Unable to start interregion
communication because ISC=NO has been communication because DFHIRP services are
specified. down level.
Explanation: IRC facilities are not available because ISC=NO Explanation: The version of DFHIRP being used is at a lower
has been specified. level than that of the caller wishing to make use of interregion
System action: The interregion communication session is not communication.
started. System action: The interregion communication session is not
User response: Run with a value other than NO for the ISC started.
system initialization parameter. User response: If IRC is required, update the level of the
Module: DFHSIJ1 DFHIRP module in the SVA such that it matches the level of
the latest CICS version in use. If IRC is not required, run with
system initialization parameter IRCSTRT=NO.
Destination: Console Module: DFHSIJ1
DFHIR3794 date time applid Interregion usage of VSE Destination: Console
system GETVIS storage has reached nnnn
bytes for this IPL
Explanation: The maximum number of bytes of VSE System
GETVIS used so far in this IPL by the CICS interregion
communication facility (for interregion buffers), is nnnn.
Module: DFHZCX
XMEOUT Parameters: date, time,applid, nnnn

Destination: CSMT
DFHIR3796 date time applid Transaction tranid termid

termid - A connected transaction sent issue
abend with following message: xxxxxx
Explanation: Transaction tranid was connected to a
transaction in another CICS system via an MRO link. The
other transaction sent an ISSUE-ABEND flow with a message.
User response: Examine the information in the included
message to determine the circumstances and what action to
take.
Module: DFHZIS1
XMEOUT Parameters: date, time,applid, tranid, termid, xxxxxx
Destination: CSMT
DFHIR3798 applid IRC Not Started. Unable to load

Interregion Communication Work Exit
DFHIRW10.
Explanation: As part of interregion communication
initialization, an attempt is made to establish an internal work
exit mechanism. This attempt has failed.
The most likely reason for the failure is that the interregion
communication work exit module, DFHIRW10, cannot be
located in the SVA. This module must be loaded in the SVA.
System action: The attempt to initiate the interregion
communication facility (via the IRCSTRT operand of the
DFHSIT, IRCSTRT system initialization override or via the
CEMT SET IRC OPEN command) fails. CICS continues.
User response: Ensure that the interregion communication
work exit module, DFHIRW10, is loaded into the SVA.
Module: DFHSIJ1

DFHJC0001 • DFHJC2900I
DFHJCxxxx messages
DFHJC0001 applid An abend (code aaa/bbbb) has occurred
continue to run and bring CICS down at a convenient time to
Alternatively, unexpected data has been input, or storage has
been overwritten. The code aaa/bbbb is a three digit
controlled shutdown. You need further assistance from IBM to
hexadecimal VSE code (if applicable), followed by a four digit
alphanumeric CICS code. The VSE code is a system
completion code, for example 0C1. If a VSE code is not
Module: DFHJCRM
applicable, this field is filled with three hyphens. The CICS
code is an abend code or a number referring to a CICS XMEOUT Parameters: applid, X'code',modname
message (for example, AKEA is a CICS abend code; 1310 Destination: Console
refers to message DFHTS1310).
A system dump is taken, unless you have specifically DFHJC0004 applid A possible loop has been detected at
suppressed dumps in the dump table. offset X'offset' in module modname.
CICS continues unless you have specified in the dump table than CICS expects. A possible loop has been detected in
that CICS should terminate. module modname at offset X'offset'. This is the offset of the
Message DFHME0116 is normally produced containing the instruction which was executing at the time the error was
symptom string for this problem. detected.
User response: Notify the system programmer. If CICS is still System action: An exception entry is made in the trace table.
running, it is necessary to decide whether to terminate CICS. A system dump is taken, unless you have specifically
Look up the VSE code, if there is one, in "OS/390 API Abend
Codes" in section "VSE/Advanced Functions Codes & SVC CICS continues unless you have specified in the dump table
Errors" of z/VSE Messages and Codes - Volume 1. that CICS should terminate.
Then look up the CICS alphanumeric code in “Transaction Message DFHME0116 is normally produced containing the
Abend Codes (CICS Transaction Server for VSE/ESA)” on symptom string for this problem.
page 453. This tells you, for example, whether the error was a User response: If CICS has not been terminated, it is
program check, an abend, or a runaway, and may give you necessary to decide whether the problem is serious enough to
some guidance concerning user response. bring CICS down.
If module modname is not crucial to the running of your CICS Since some CICS functions can use a lot of processor time, this
system, you may decide to continue to run and bring CICS message may have been caused by a long-running function in
down at a convenient time to resolve the problem. which case there may not be an error here. Usually, CICS
purges a CICS function which exceeds the runaway task time
If you cannot run without the full use of module modname, interval which you have specified on the ICVR system
you should bring CICS down in a controlled shutdown. initialization parameter (ICVR is measured in milliseconds).
This means that module modname is terminated and CICS
You need further assistance from IBM to resolve this problem. continues.
guidance on how to proceed. However, if you have declared ICVR=0 and you consider that
Module: DFHJCRM module modname has gone into a loop, you have to terminate
CICS in order to terminate the runaway function.
Destination: Console If CICS has terminated module modname and you consider
interval. You will have to bring CICS down at a suitable time
DFHJC0002 applid A severe error (code X'code') has to do this permanently. However, you can change the ICVR
occurred in module modname. time interval temporarily online using the CEMT transaction.
The code code is the exception trace point ID which uniquely If raising the ICVR time does not solve the problem, you will
identifies what the error is and where the error was detected. need further assistance from IBM. See Part 4 of the CICS
System action: An exception entry (code code in the message) Problem Determination Guide for guidance on how to proceed.
is made in the trace table. A system dump is taken, unless you Module: DFHJCRM
XMEOUT Parameters: applid, X'offset', modname
CICS continues unless you have specified in the dump table Destination: Console
Message DFHME0116 is normally produced containing the DFHJC2900I DFHTEOF UTILITY.
symptom string for this problem. Explanation: This message is for information only. The
User response: This indicates a possible error in CICS code. DFHTEOF utility has begun execution.
The severity of its impact depends on the importance of the System action: The program continues.
function being executed at the time of the error. User response: None.
Module: DFHTEOF
CICS may not have been terminated. Destination: Console

DFHJC2901I • DFHJC2909D
DFHJC2901I DFHTEOF COMPLETED, ON SIGNAL
THAT TAPE WAS ALREADY INTACT.
Explanation: The DFHTEOF utility was invoked by CICS DFHJC2906I VOLUME LABEL VERIFICATION.
initialization. It has completed successfully. It indicates that Explanation: This message indicates that volume labels are
the "Fast Restart" path was taken because the tape was known
being verified and that the operator's decision is needed for
to be closed during the previous shutdown. The tape is not
messages DFHJC2907 and DFHJC2909 which follow.
overwritten, but is positioned ready for input backward.
System action: The program continues.
System action: The program terminates.
Module: DFHTEOF Module: DFHTEOF
DFHJC2902I UNABLE TO ALLOCATE STORAGE. DFHJC2907I LABEL INFORMATION - VOLUME

DFHTEOF TERMINATES ABNORMALLY. NUMBER yyddd/nnn/nnn RUN time1 BLOCK
Explanation: Storage was not available for this program time2.
when the storage request was issued. Explanation: This message displays fields from the label
System action: Program execution is abnormally terminated record that the operator is requested to examine. The context
with abend code 2902. in which the operator is required to examine these fields is
User response: Increase the region size and rerun. given in the preceding message. This must be done in order to
Module: DFHTEOF verify that:
Destination: Console v The correct volume is open,
v Logical continuity is not lost and that
v Logical continuity ends at the expected point.
DFHJC2903I UNABLE TO OPEN LOG VOLUME.
Explanation: An OPEN macro has been issued but it has yyddd is the date this volume was created, nnn is the volume
failed to open the journal. sequence number within the day and the run, time1 is the time
System action: Program execution is abnormally terminated that the run started and time2 is the time that the block was
with abend code 2903. written to the tape. Both "time" fields have the form hh:mm:ss.
User response: Check for a missing DLBL statement for the
data definition name DFHTAPE.
If the journal is in the DMF format, no details of the start of
Module: DFHTEOF
the run are available, so the date and the time1 fields are made
to show when the first block of this reel was written.
DFHJC2904D DO YOU WANT TO SWAP JOURNAL Note: The volume-creation date, the run-start time and
VOLUMES? REPLY 'Y' OR 'N'. block-output time do NOT all necessarily refer to the same
Explanation: A negative response was received during label day.
verification of a journal volume. System action: Message DFHJC2908 is issued if volume
System action: If the response is 'Y', the program will close verification is in progress. Message DFHJC2912 is issued if
the current volume and request another journal volume. record label verification is in progress.
If the response is 'N', program execution will abnormally User response: Check the label information displayed and
terminate with message DFHJC2915. reply accordingly to message DFHJC2908 or message
User response: Reply 'Y' if the incorrect volume is mounted DFHJC2912.
and another volume should be mounted. Otherwise, reply 'N'. Module: DFHTEOF
Module: DFHTEOF Destination: Console
DFHJC2908D IS MOUNTED VOLUME VALID - 'Y' OR 'N'.

DFHJC2905I eeee ERROR ON PREVIOUS RECORD - Explanation: This message refers to the verification of a
NEXT RECORD LABEL VALID. mounted journal volume.
Explanation: While the labels of the journal were being System action: The system waits for a reply. If the reply is
validated, an error eeee occurred. However, the next sequential 'Y', processing continues for the location of the end of valid
label record was found to be valid. eeee is one of the following: journal records.
v DATA CONVERSION
v WORD COUNT ZERO If the reply is 'N', volume swapping takes place.
v OVERRUN User response: Reply 'Y' if label information is valid. Reply
v DATA CHECK 'N' if label information is invalid.
v EQUIPMENT CHECK Module: DFHTEOF
v BUS-OUT CHECK Destination: Console
v INTERVENTION RQ
v COMMAND REJECT
DFHJC2909D CONTINUE PROCESSING? REPLY 'Y' or 'N'.
System action: The task writes the label information and
Explanation: This message follows message DFHJC2905
enquires if further processing should continue by issuing
when an I/O error occurs and the next label record is valid.
message DFHJC2909.
System action: The system waits for a reply. If the reply is
User response: Decide whether you want to continue
'Y', processing continues until end-of-data is detected.
processing or not. Respond appropriately to message
DFHJC2909. If the reply is 'N', execution of program DFHTEOF is
Module: DFHTEOF terminated.

DFHJC2910I • DFHJC2918I
User response: Reply 'Y' if processing is to continue. Reply

DFHJC2914I END-OF-DATA OCCURRED. LAST
'N' if processing is to terminate.
RECORD LABEL VERIFICATION
FOLLOWS.
Note: If this is the system log, the error may recur during Explanation: An end-of-data condition occurred but there
recovery processing. was no detection of an error (unless stated by DFHJC2926).
Module: DFHTEOF System action: If DFHTEOF is being invoked by CICS
Destination: Console initialization, this message is followed by DFHJC2901. If
DFHTEOF is being run as a batch utility, this message is
DFHJC2910I AN I/O ERROR HAS OCCURRED. followed by DFHJC2907.
DFHTEOF TERMINATES ABNORMALLY. User response: None as far as this message is concerned, but
Explanation: A negative response was received for message user action may have to be performed for the messages that
DFHJC2909. follow this one.
System action: Program execution is abnormally terminated. Module: DFHTEOF
Module: DFHTEOF
Destination: Console DFHJC2915D IS THE CORRECT VOLUME MOUNTED?
REPLY 'Y' OR 'N'.
DFHJC2911I RECORD LABEL VERIFICATION. Explanation: When end-of-data occurs, the label information
Explanation: This message indicates that record labels are of the last record is written to the console for verification.
being verified. This message is issued in one of the following System action: The system waits for a reply. If the reply is
situations: 'Y', the program is terminated. If the reply is 'N', the option to
1. A record label does not match the first label record on the swap volumes is given.
volume, or User response: Reply 'Y' if the correct volume is mounted.
2. Unit-check errors occurred in succession, or Reply 'N' if the wrong volume is mounted.
3. A "hard" error occurred (implying that, (on a 3480) the
read head ran past the end of good data. Note: The option to swap volumes is be given in those cases
System action: Message DFHJC2907 is issued, bearing data where the wrong volume was originally mounted.
from the record preceding the fault. Module: DFHTEOF
User response: Refer to message DFHJC2907 for further Destination: Console
information.
Module: DFHTEOF
DFHJC2916I AN UNRECOVERABLE I/O ERROR HAS
OCCURRED. DFHTEOF TERMINATES
ABNORMALLY.
DFHJC2912D IS THE JOURNAL RECORD LABEL VALID? Explanation: An error, other than unit check or unit
REPLY 'Y' OR 'N'. exception, was detected on the journal volume.
Explanation: This message follows message DFHJC2907. It System action: Further processing is discontinued and
requests verification of the last valid record label that was execution of the program is abnormally terminated.
found by the program DFHTEOF. User response: There is a possible hardware malfunction.
System action: The system waits for a reply. If the reply is Have the problem corrected and then resubmit the program.
'Y', an end-of-file (EOF) mark is written on the tape volume Module: DFHTEOF
and the program is terminated. Destination: Console
If the reply is 'N', program execution is abnormally

terminated. DFHJC2917I INCORRECT REPLY x.
User response: Reply 'Y' if the label information is correct. Explanation: An incorrect reply character, x, was received in
Otherwise reply 'N'. response to action messages.
System action: The program reissues the message that
Note: The label information can be verified by comparing the received this incorrect reply.
data with the volume previously displayed, and with the User response: Reenter the correct reply.
known time when the run that produced this data set ended. Module: DFHTEOF
DFHJC2918I NEGATIVE RESPONSE TO VOLUME
DFHJC2913I NEGATIVE RESPONSE TO RECORD VERIFICATION. DFHTEOF TERMINATES
LABEL VERIFICATION. DFHTEOF ABNORMALLY.
TERMINATES ABNORMALLY. Explanation: A negative response was received for
Explanation: This message is issued when the response to volume-label verification. No swapping of volumes was
message DFHJC2912 is negative. required.
System action: Program execution is abnormally terminated. System action: Program execution is abnormally terminated.
Module: DFHTEOF Module: DFHTEOF

DFHJC2919I • DFHJC2927I
DFHJC2919I END-OF-DATA. EITHER NO VOLUME DFHJC2924I FIRST RECORD ON THIS TAPE IS NOT
LABEL, OR INVALID VOLUME MOUNTED. FORMATTED AS A JOURNAL LABEL
Explanation: During volume label verification, an end-of-data Explanation: Verification of the mounted volume failed
condition occurred before verification could be performed. because some expected constant and packed-decimal fields
This normally indicates that a wrong volume was mounted. were not found in the first block read.
System action: After message DFHJC2919 is issued, System action: DFHJC2904 is issued to try for another
DFHJC2904 is issued to swap volumes. volume.
User response: Reply 'Y' and mount the correct volume, or User response: A non-journal tape was probably mounted in
reply 'N' to terminate the program. error. Mount the correct journal.
Module: DFHTEOF
Destination: Console Alternatively, the correct volume has been mounted, but it
may have been damaged or overwritten. Investigate for a
possible loss of data and try to recover the situation.
DFHJC2920I NEGATIVE RESPONSE AFTER Module: DFHTEOF
END-OF-DATA OCCURRED. DFHTEOF Destination: Console
TERMINATES ABNORMALLY.
Explanation: After end-of-data (EOD) occurred, a negative
DFHJC2925I I/O ERRORS OCCURRED - NO RECORDS
response was received for label verification of the volume and
READ.
for swapping of the volume.
Explanation: During volume verification, I/O errors occurred
System action: Program execution is abnormally terminated.
which prevented the first two blocks from being read. This
normally indicates that a wrong or a damaged volume was
Module: DFHTEOF
mounted.
System action: After the above message is issued, message
DFHJC2904 is issued to swap volumes.
DFHJC2921I I/O ERROR DURING WRITE. DFHTEOF User response: Reply 'Y' and mount the correct volume, or
TERMINATES ABNORMALLY. reply 'N' to terminate the program.
Explanation: An I/O error occurred while writing a dummy Module: DFHTEOF
record to enable output processing. This causes an end-of-file Destination: Console
mark to be written during execution of the CLOSE macro
instruction (as it would be for an OUTPUT data set).
DFHJC2926I ERROR FOUND ADJACENT TO FINAL
System action: DFHJC2921 is written to the operator console
TAPEMARK. ONE RECORD WILL BE
and execution of the program is abnormally terminated.
ELIMINATED.
User response: Rerun DFHTEOF and use another tape drive.
Explanation: An error occurred while DFHTEOF was
Module: DFHTEOF
scanning the labels of the journal. The next sequential read
returned "unit exception". The most probable cause is that the
unit exception indicates a correctly-placed tapemark at the end
DFHJC2922I UNABLE TO OPEN 3480 JOURNAL of the data set, but that the last data block is unreadable.
VOLUME FOR REPOSITIONING. System action: The task treats the data set as logically ending
Explanation: After the broken end of a data set on a 3480 with the block before the faulty one. The task attempts to
tape was identified, DFHTEOF attempted to reopen the device position and close the journal at the point preceding the faulty
in order to position and close the data set properly. However, block.
the OPEN failed. User response: No user action is required but you should be
System action: The task abnormally ends. aware that some data may be permanently lost.
User response: None. Module: DFHTEOF
DFHJC2927I ERROR FOUND AT BEGINNING OF
DFHJC2923I ERROR READING 3480 JOURNAL DATASET. INPUT IS RE-TRIED.
VOLUME FOR REPOSITIONING. Explanation: An error was detected during the first attempt
Explanation: After the position at which the last previously to read the data set. DFHTEOF makes a second attempt to
written record had been identified on the 3480 tape, read the data set.
DFHTEOF opened the device in order to reposition and close
In the case of the system log, there is a significant chance that
the data set properly. However, DFHTEOF encountered either
restart may still succeed. This is because reading backward
a serious error, or a tapemark that had not been seen during a
does not necessarily reach the beginning of the tape.
previous analytical scan.
System action: DFHTEOF continues analysis, depending on
System action: The task abnormally ends.
what it finds during the second read.
User response: There has been a possible hardware
User response: No user action is required, but you should be
malfunction. Resubmit the program. If it fails again, check for
aware that some data may be lost.
a hardware malfunction and have it corrected.
Module: DFHTEOF
Module: DFHTEOF

DFHJC2928I • DFHJC4506
'YES' in response to this message to indicate that the scratch

DFHJC2928I DFHTEOF COMPLETED, LEAVING nnnnnnn
volume is available.
BLOCKS IN PLACE.
Explanation: Although the DFHTEOF utility has completed An operating system OPEN request is issued with this
successfully, the previous shutdown was unable to close the message (or after the positive response if a reply is required).
tape. DFHTEOF scans the tape looking for the last record and When the OPEN succeeds, or after a positive response if a
places an end-of-file marker after the last record. DFHTEOF reply is required, message DFHJC4503 is issued.
counts the number of blocks read. This number is indicated by User response: Mount a tape and ready on the addressed
nnnnnnn. device. The volume will receive output records for journal nn.
System action: DFHTEOF terminates.
User response: None. Do not delay taking action, or other journal OPEN and/or
Module: DFHTEOF CLOSE processing may be held up.
Destination: Console Module: DFHJCOCP
Destination: Console Routecodes 2, 3 and 11
DFHJC4500 applid nn of mm journals successfully opened

Explanation: This is an informational message, issued at DFHJC4504 CICS {SYSTEM LOG | JOURNAL nn}
system initialization time. Both the inserts are two-digit MOUNT ON cuu FOR INPUT: {LATEST
numbers. OUTPUT VOLUME | NEXT VOLUME (IF
ANY) | PREVIOUS VOLUME (IF ANY)}
Explanation: CICS requires journal volume nn to be mounted
Note: You can suppress this message with MSGLVL=0. This
on device cuu. LATEST, NEXT and PREVIOUS refer to the
message also does not occur when the run has
sequence implied by the external label allocated by CICS (see
START=LOGTERM coded, either in the SIT or by operator
message DFHJC4503). External labels are sequential by date
override.
and volume sequence number for a particular CICS execution.
System action: This message is always followed by message
DFHJC4505, which requires a reply of YES or NO.
Module: DFHJCKOJ
User response: Locate the appropriately labeled tape reel if it
XMEOUT Parameters: applid, nn,mm is not already mounted. If the volume is already mounted and
Destination: Console the drive is ready, do not touch it. Otherwise, merely mount
the volume but do not ready the drive. Then reply to message
DFHJC4505, which always follows message DFHJC4504.
DFHJC4501 applid CICS {System Log | Journal nn} not Module: DFHJCOCP
available - initial open failure Destination: Console Routecodes 2, 3 and 11
Explanation: The journal nn could not be opened for output
at system initialization time.
System action: If the journal is specified with the CRUCIAL DFHJC4505 CICS {SYSTEM LOG | JOURNAL nn} REPLY
option in its journal control table (JCT) entry, CICS is 'YES' IF VOLUME AVAILABLE, OR 'NO' IF
terminated with a dump and a VSE user abend code of 0113. NOT
Explanation: This message accompanies message DFHJC4504,
Otherwise, CICS execution continues and the journal is requesting a journal tape volume to be mounted for input.
unavailable for the duration of the run. System action: If the reply is 'YES', CICS issues an operating
User response: Ensure that the correct JCL is supplied. For a system OPEN request. If the reply is 'NO', a volume error
disk journal, check that the data set had been preformatted status is returned to the requesting transaction by CICS.
correctly. For further information, see the CICS System User response: Reply 'YES' if the volume has been located, or
Definition and Operations Guide. 'NO' if it cannot be found or if the request was for a
If the error persists, check for prior messages indicating a nonexistent volume label. After a YES reply, prepare to mount
possible data corruption. If the error still persists, allocate a the volume onto the tape drive, unless the volume was
different device. already mounted and left ready on the drive (see message
Module: DFHJCKOJ DFHJC4506). Do not delay replying, or other journal
open/close processing may be held up.
XMEOUT Parameters: applid, {1=System Log, 2=Journalnn} Module: DFHJCOCP
Destination: Console Destination: Console Routecodes 2, 3 and 11
DFHJC4502 CICS {SYSTEM LOG | JOURNAL nn} DFHJC4506 CICS {SYSTEM LOG | JOURNAL nn} {label}
MOUNT SCRATCH VOLUME ON cuu FOR {LATEST OUTPUT VOLUME NOW CLOSING
OUTPUT. {REPLY YES WHEN AVAILABLE} BUT REMAINING ON | UNLOADING FROM
Explanation: The named volume or a scratch volume is to be | VOLUME FOR INPUT (BUT NEVER USED),
mounted and opened to receive the output of the specified UNLOADING CUU=cuu}
journal. Explanation: The specified journal tape volume has been
closed. External label information (see message DFHJC4503)
nn indicates the journal; cuu is the address of the tape unit.
previously allocated by CICS is provided if the tape is being
The sentence "REPLY 'YES' WHEN AVAILABLE" is issued as unloaded from the drive.
part of this message only if the PAUSE option has been System action: This is the action indicated by the message
specified in the JCT. text. Namely that the tape is either unloading from or
System action: If the PAUSE option is specified in the journal remaining on the drive whose address is given.
control table (JCT), the system waits for the operator to reply User response: If the tape is unloaded attach a physical label
to it, as indicated in the message text. This label is the external

DFHJC4507 • DFHJC4513
label to which CICS may later refer when asking for it to be

DFHJC4511 applid Link to a journal control transient
mounted (see message DFHJC4504).
failed
If the tape is not unloaded, you should leave it and the drive Explanation: CICS could not find one of the following
alone (unless the tape is due to be removed anyway; for journal control transient programs in the program library:
example, to be read on another system). DFHJCO, DFHJCC, DFHJCEOV, DFHJCIOE, or DFHJCI.
Module: DFHJCOCP System action: CICS execution is terminated with a dump.
Destination: Console Routecodes 2, 3 and 11 The VSE user abend code is 0111.
User response: Either restart CICS with the journal control
option disabled, or ensure that all the above programs are in
DFHJC4507 applid CICS {SYSTEM LOG | JOURNAL nn} the program library.
{PRIMARY |SECONDARY} DATA SET Module: DFHJCP
ABOUT TO RECEIVE OUTPUT ON cuu.
REPLY 'Ynn{A | B}' WHEN AVAILABLE XMEOUT Parameter: applid
Explanation: The specified journal disk data set is about to Destination: Console
be overwritten by output. The journal was specified with the
PAUSE option in its journal control table (JCT) entry.
DFHJC4512 date time applid CICS {System Log |Journal nn}
no longer available - output volume-switch
User response: For a detailed description of the pause
failure
mechanism, see the CICS Operations and Utilities Guide. Ensure
Explanation: An invalid response code was obtained by a
that any installation operational procedures to copy (archive)
CICS journal task while trying to perform the close/open
data from the data set have been completed, then reply
sequence to switch automatically to a new journal output
'{YnnA|B}' as prompted by the message. Do not delay
volume. applid in the message is the VTAM APPLID of the
replying in case other journal open or close processing is held
CICS system issuing the message.
up.
System action: If the journal is specified with
Module: DFHJCOCP
JOUROPT=CRUCIAL in its journal control table (JCT) entry,
CICS execution is abnormally terminated with a dump. The
VSE user abend code is 0112.
DFHJC4508 applid CICS {SYSTEM LOG | JOURNAL nn}
If the journal is not CRUCIAL, execution continues and the
{PRIMARY |SECONDARY} DATA SET NOW
journal is unavailable for the duration of the run; the journal
RECEIVING OUTPUT ON cuu
task of the journal is abnormally terminated with CICS abend
Explanation: The specified journal disk data set is being used
code AJCB.
(overwritten).
User response: Restart CICS, if it has terminated. Inform the
applid is the VTAM APPLID of the CICS system issuing the person(s) responsible for debugging system errors of the
message. condition, which should not occur, and may be due to an
System action: The specified data set of journal nn becomes operating system or device open/close failure, or to a CICS
the current volume for output. error.
For further information, refer to abend code AJCB.
Module: DFHJCOCP
Module: DFHJCEOV
XMEOUT Parameters: date, time,applid, {1=System Log,
2=Journal nn}
DFHJC4509 applid The Global Catalog control record Destination: CSMT
cannot be updated
Explanation: An error occurred when reading or writing the
control record on the global CICS catalog. The record is being DFHJC4513 date time applid CICS {System Log |Journal nn}
updated with the latest volume serial number and a no longer available - output I/O error
timestamp. A previous message may indicate the reason why Explanation: An unrecoverable output I/O error has
there is a problem with the global catalog. occurred for the specified journal data set. applid in the
System action: CICS is terminated with a dump. message is the VTAM APPLID of the CICS system issuing the
User response: Refer to any preceding messages for further message.
information and guidance. Correct the problem with the System action: The journal task for the specified journal
catalog. terminates abnormally with abend AJCA. CICS continues, but
Module: DFHJCO the journal remains unavailable for the rest of the run.
XMEOUT Parameter: applid Message DFHJC4513 is always followed by message

Destination: Console DFHJC4517. If JOUROPT=CRUCIAL is specified, message
DFHJC4518 is also issued to prompt the terminal operator, and
transactions attempting to use the journal terminate
DFHJC4510I applid All open journals now closed abnormally with abend AJCR.
Explanation: Informatory message issued when CICS is in User response: Inform the person(s) responsible for the
the process of terminating execution. integrity of journal data sets. If the error persists, allocate a
System action: System termination continues. different device or data set to the journal.
Module: DFHJCSDJ For further information, refer to abend code AJCA.
Module: DFHJCIOE

XMEOUT Parameters: date, time,applid, {1=System Log, reason for the global catalog write error.
2=Journal nn} System action: CICS takes a dump and terminates
Destination: Console and Transient Data Queue CSMT abnormally with VSE user abend code 0183.
User response: Look for any preceding console message
issued by DFHCCCC which indicates the reason for the global
DFHJC4514 applid Journal Control subtask has catalog write error. The response code to the DFHCCCC call
abnormally terminated can also be found in the trace table, or in the DFHCCCC
Explanation: The operating system subtask DFHJCOCP, used parameter list within the dump.
by journal control for open/close requests and console Module: DFHJCO, DFHJCC, DFHJCP
communication, has abnormally terminated. The subtask only
XMEOUT Parameters: applid, {1=Open, 2=Close, 3=Status}
performs simple open or close processing. The abend may be
due either to an operating system failure, to a device failure,
or to a CICS error.
System action: If the abnormal termination of the subtask DFHJC4517 date time applid A non-immediate shutdown of
occurs during the final termination phase of normal CICS should be initiated
shutdown, CICS attempts to shut down journaling and the Explanation: CICS issues this message after DFHJC4513.
normal shutdown continues. System action: Processing continues.
User response: If the journal is critical to the security of your
If the abnormal termination of the subtask occurs outside the data, close down CICS normally.
final termination phase, CICS attempts to shut down Module: DFHJCIOE
journaling and then terminates abnormally with a VSE dump.
The VSE user abend code is 0114. XMEOUT Parameters: date, time,applid
User response: Restart CICS. If the error recurs immediately, Destination: Console and Transient Data Queue CSMT
inform the system programmer.
Module: DFHJCBSP
DFHJC4518D date time applid Reply 'YES' to acknowledge
XMEOUT Parameter: applid message DFHJC4517
Destination: Console Explanation: CICS issues this message after DFHJC4517 if the
unavailable journal is specified with JOUROPT=CRUCIAL in
the journal control table (JCT).
DFHJC4515 applid Unable to note open of System Log by System action: Processing continues.
DFHTEOF on DFHGCD data set User response: Reply 'YES' to acknowledge receipt of
Explanation: Before attaching DFHTEOF to open the system messages DFHJC4513 and DFHJC4517.
log for tape end-of-file processing, DFHSIC1 tries to Module: DFHJCIOE
update/write the system log control record in the CICS global XMEOUT Parameters: date, time,applid
catalog (DFHGCD). This update/write operation has failed. Destination: Console and Transient Data Queue CSMT
This message may have been preceded by another console
message, issued by module DFHCCCC, which indicates the DFHJC4519 applid Program DFHJCBSP is not available
reason for the global catalog write error. Explanation: During system initialization, CICS cannot find
System action: CICS terminates abnormally with a dump. the journal control module, DFHJCBSP, and therefore cannot
User response: Look for any preceding console message initialize journaling.
issued by DFHCCCC which indicates the reason for the global System action: CICS terminates abnormally with VSE user
catalog write error. The response code to the DFHCCCC call abend code 0119.
will also be found in the trace table, or in the DFHCCCC User response: Ensure that DFHJCBSP is a member of a
parameter list within the dump. sublibrary of the specified LIBDEF search chain for the CICS
Module: DFHSIC1 startup job stream.
Module: DFHJCKOJ
DFHJC4516 applid Unable to note {Open | Close | Status}

of a journal on CICS Global Catalog DFHJC4520 applid Required module modname could not be
Explanation: The system log or a user journal has been loaded.
opened or closed, but the following attempt to update or write Explanation: Module modname is required by journal control.
the journal's status to the CICS global catalog (DFHGCD) has It could not be loaded because it is missing from the LIBDEF
failed. search chain.
System action: The system terminates with a system dump.
The record in question may be either the system log control Message DFHME0116 is normally produced containing the
record (which affects any later emergency restart from tape), symptom string for this problem.
or an "extent status" record, essential to the integrity of a disk User response: Ensure that module modname is in the LIBDEF
journal. search chain.
If OPEN is inserted, the message is issued by DFHJCO. If this is not the cause of the problem, you will need further
If CLOSE is inserted, the message is issued by DFHJCC. assistance from IBM. See Part 4 of the CICS Problem
If STATUS is inserted, the message is issued by DFHJCP. Module: DFHJCRP
This message may have been preceded by another console XMEOUT Parameters: applid, modname
message, issued by module DFHCCCC, which indicates the Destination: Console

Destination: SYSLST
DFHJC4522 FILENAME filename HAD A PERMANENT
I/O ERROR.
Explanation: An unrecoverable I/O error occurred while the DFHJC4526 INVALID OPTION CARD OR PRIOR
CICS journal print utility was processing the data set defined ERROR.
in the DLBL statement filename.
Explanation: The CICS journal print utility detected an error
System action: The journal print utility terminates.
in an OPTION card or ignored it because of a previous error.
User response: If the error occurred on an output data set,
The card is displayed in the line before this message.
and you wish to rerun, change the DLBL statement to refer to
System action: The journal print utility ignores the card and
a different volume, and resubmit the job. Take the original
volume offline for recovery, if possible. continues processing.
User response: If the job fails or the output is not what you
If the error occurred on the input data set, it is probably due want, correct the error and resubmit the job.
to reading a file with an incorrect format e.g. fixed. DFHJUP Module: DFHJUP
validates the Record Descriptor Word in the first two bytes of Destination: SYSLST
each logical record, and if it is negative or greater than 31,757
it terminates with this message. Otherwise, it is likely to be a
real I/O error; to be able to recover you must have a backup DFHJC4527 END OF JOB.
copy of the defective volume. You can change the DLBL Explanation: This is an end-of-job information message
statement to refer to the backup volume, and rerun the job. If issued by the CICS journal print utility when it terminates
you have a backup copy of a defective disk, you can use IBM normally. Errors may have been detected but none were
utilities to recover the disk by flagging the defective track and serious enough to cause abnormal termination.
pointing to an alternate track. System action: The journal print utility terminates normally.
Module: DFHJUP User response: Check that all options completed normally. If
Destination: SYSLST not, submit another job for the options that you still need.
Module: DFHJUP
DFHJC4523 PROCESSING IS BEING TERMINATED Destination: SYSLST
FOR THIS OPTION.
Explanation: This is an informatory message issued by the DFHJC4528 NO OPTION CARDS SUPPLIED.
CICS journal print utility, when it completes processing for an
Explanation: The CICS journal print utility detected that, for
OPTION card. The card referred to is the last OPTION card
one CONTROL card:
before this message on SYSLST.
1. No OPTION cards were supplied OR
System action: The journal print utility continues processing
2. All the OPTION cards contained errors (notified in
with the next option.
User response: If no other messages appear between the previous messages).
OPTION card and this message, the termination is normal. If System action: The journal print utility does no processing
other messages have been issued, check them to see if the for the CONTROL card with no OPTION cards.
termination is normal or abnormal. If abnormal termination User response: Supply correct OPTION cards for the options
has occurred, correct the errors notified in other message(s), you want and resubmit the job.
and resubmit the job. Module: DFHJUP
Module: DFHJUP Destination: SYSLST
Destination: SYSLST
DFHJC4529 UNABLE TO OPEN INPUT FILE.

DFHJC4524 INVALID CONTROL CARD FORMAT. Explanation: The CICS journal print utility was unable to
Explanation: The CICS journal print utility detected an error open the input data set associated with the CONTROL card
in an input CONTROL card. The card is displayed on SYSLST displayed before this message.
on the line before this message. System action: The journal print utility continues processing
System action: The journal print utility ignores the invalid with the next input card.
card, and assumes standard defaults. User response: Check the JCL. For a data set without a
User response: If the output of the run is not what you want, standard label, check that the data set control block (DCB)
correct the invalid card and resubmit the job. parameters are supplied. If you find a JCL error, correct it and
Module: DFHJUP resubmit the job.
Destination: SYSLST Module: DFHJUP
Destination: SYSLST
DFHJC4525 INVALID CARD TYPE.
Explanation: The CICS journal print utility read an input
DFHJC4530 ELEMENT LIST ERROR.
card that did not contain one of the following strings starting
Explanation: The CICS journal print utility detected an error
in column 1:
while processing an input file.
System action: The journal print utility terminates processing
'CONTROL', 'OPTION', '*', or 'END'. with the VSE user abend code 0185.
User response: This is usually caused by a previous error, for
The invalid card is displayed on SYSLST in the line before this which a message has been issued. If any previous error
message. messages were displayed, make the necessary corrections and
System action: The journal print utility ignores the invalid resubmit the job.
card and continues processing. Module: DFHJUP
User response: If the job fails or the output is not what you Destination: SYSLST
want, correct the invalid card and resubmit the job.
Module: DFHJUP

Further information on PAUSE can be found in the CICS

DFHJC4531 END OF FILE ON INPUT.
Recovery and Restart Guide.
Explanation: The CICS journal print utility has reached EOF
on the current input file. The most likely causes of the problem are:
System action: The journal print utility completes processing v JCL for the JACD is missing or incorrect. In this case, VSE
for the CONTROL card preceding this message on SYSLST. issues an error message.
User response: None. v The control interval (CI) size is not equal to 512 bytes. In
Module: DFHJUP this case, message DFHJC4564 is issued.
Destination: SYSLST v An I/O error has occurred accessing the JACD. This is
probably a hardware error.
DFHJC4532 OPTION COMPLETE. If you cannot find the problem, rerun with trace on to identify
Explanation: The CICS journal print utility has completed the source of the error. After correcting the problem, before
processing for the OPTION card preceding this message on CICS is restarted, ensure all journal data sets are archived as
SYSLST. required, and redefine the JACD.
System action: The journal print utility continues processing Module: DFHJCRP
with the next OPTION card or, if there are no further options
XMEOUT Parameters: date, time,applid, journalno
before the END card, completes processing for the current
control card.
Module: DFHJUP DFHJC4536 date time applid I/O error while modname was
Destination: SYSLST accessing JACD. Journal journalno using
'PAUSE' instead of 'AUTOARCH'.
Explanation: An I/O error occurred trying to access the
DFHJC4533 UNABLE TO OPEN OUTPUT FILE. journal archive control data set. Module modname caused this
Explanation: The CICS journal print utility was unable to message to be issued.
open the output data set associated with the last CONTROL
card displayed on SYSLST before this message. The journal journalno uses PAUSE to control the journal data
System action: The journal print utility terminates processing sets.
for this CONTROL card, and continues processing with the System action: As the status of the journal data sets cannot
next CONTROL card. be determined, CICS assumes that all journal data sets are in
User response: Correct the JCL and resubmit the job. need of archiving, and issues message DFHJC4583 or
Module: DFHJUP DFHJC4586.
Destination: SYSLST User response: Respond to DFHJC4583 or DFHJC4586,
whichever has been issued. Until the reason for the failure has
been investigated and corrected, the PAUSE option requests a
DFHJC4534 NO ELEMENT LIST ADDRESS. response from the CPU console operator before a data set is
Explanation: During CICS journal print utility processing, an reused. This gives the operator the chance to copy the data set
error occurred in building the element list. (using a batch job) before it is reused. Further information on
System action: The journal print utility terminates processing PAUSE can be found in the CICS Recovery and Restart Guide.
for this element list, and terminates abnormally with the VSE This problem is probably caused by a hardware error. Look
user abend code, 0184. out for an associated VSAM error message. If trace is on, you
User response: This is an internal error in the journal print might be able to follow the course of the previous request and
utility, DFHJUP. You need further assistance from IBM to identify where the error occurred. If trace is not on and you
resolve this problem. See Part 4 of the CICS Problem cannot find the error, you should set trace on and rerun. This
Determination Guide for guidance on how to proceed. gives you the VSAM return code which you can check in
Module: DFHJUP section "VSE/VSAM Codes" in z/VSE Messages and Codes -
Destination: SYSLST Volume 2. After correcting the error, ensure all journal data sets
are archived as required, and redefine the JACD before CICS
is restarted.
DFHJC4535 date time applid The JACD cannot be Module: DFHJCO, DFHJCC, DFHJCKOJ
initialized. Journal journalno will use 'PAUSE'
instead of 'AUTOARCH'. XMEOUT Parameters: date, time,applid, modname, journalno
Explanation: Archiving could not be initialized due to a Destination: Console and Transient Data Queue CSMT
problem opening the journal archive control data set (JACD).
The specified journal uses PAUSE to control the journal data DFHJC4538 date time applid Error acquiring storage.
sets. Cannot submit archive for journal journalno
System action: The status of the journal data sets is datasetid.
contained in the JACD, so it cannot be determined what the Explanation: A severe error has been detected by the storage
status of the journal data sets is. CICS assumes that all journal manager domain. There should have been a previous message
data sets are in need of archiving, and issues message on the console indicating what this error was. The archive job
DFHJC4583 or DFHJC4586. for this journal is not submitted.
User response: First, respond to DFHJC4583 or DFHJC4586 System action: Processing continues.
(whichever has been issued). Then, until the reason for the User response: Take whatever action has been indicated in
failure has been investigated and corrected, the PAUSE option the previous message indicating the source of the error. Then
requests a response from the CPU console operator before a manually submit an archive job for the journal data set
data set is reused. This gives the operator the chance to copy journalno.
the data set (using a batch job) before it is reused.
Set the status of the journal data set to READY, using the

DFHJC4539 • DFHJC4544D
UPDATE function of the DFHJACDU utility. For further User response: This message indicates the information on the
information about how to do this, refer to the CICS Operations JACD does not agree with the information on the journal data
and Utilities Guide. sets. This is possible if the journal is reformatted as part of
Module: DFHJAP archiving. Ensure the status of both data sets is correct and
that all archiving is complete. You may need to update
XMEOUT Parameters: date, time,applid, journalno, datasetid DFHJACDU if the status is incorrect.
Destination: Console and Transient Data Queue CSMT Module: DFHJAP
XMEOUT Parameters: date, time,applid, journalno,
DFHJC4539 date time applid insert disagrees with the datasetid1,datasetid2
information on the JACD for journal data set Destination: Console and Transient Data Queue CSMT
journalno datasetid.
Explanation: This is a warning message which occurs at
CICS initialization. insert may be either DSNAME or DFHJC4542D date time applid Journal data set journalno
ARCHJCL. During the load of the journal control archive data datasetid is not ready. Reply 'GO' or
set (JACD), either the CICS JCL for the journal data set 'SUBMIT'.
(DSNAME), or the ARCHJCL parameter in the JCT, was Explanation: CICS wants to use the journal data set journalno
different to the data held for this journal data set on the datasetid but it has not been archived yet.
JACD. The journal data set name (DSNAME) or the ARCHJCL System action: Wait for the operator to reply.
parameter, whichever is applicable, is given in the message. User response: There are three possible courses of action:
The JACD has been updated to reflect this new information v If there is an archive job running or about to run, wait for it
and the status has been set to READY. to complete successfully and then reply GO.
System action: Processing continues. v If there is no archive job running or about to run, enter
User response: None, unless this was not the expected result. SUBMIT, to archive the journal data set. After this has
The message implies that someone has changed the DLBL happened, message DFHJC4544 is issued.
statement for the journal data set or the ARCHJCL parameter
Note that this implies that the previous archiving job failed.
in the JCT since the last use of CICS. If this is unexpected, you
You may want to investigate the cause of this. If this
may wish to change it back again by stopping CICS, making
the required changes, and restarting. submitted job has failed or fails now, there are several
possible explanations. For example:
You should note that, if you do this, message DFHJC4539 will – If there are user-supplied programs in the job stream,
be repeated because you have changed the attributes again. they may be impacting the output of the job.
Also, an archive will have been submitted when CICS – There may be a job control error.
terminated if this data set had been opened. – The job may not contain a job step to set the journal data
Module: DFHJAP set to READY.
XMEOUT Parameters: date, time,applid, insert, journalno, – The POWER® queues may be very long and the job may
datasetid not yet have started.
Destination: Console and Transient Data Queue CSMT v If for some reason you cannot run or do not wish to run the
archive job, the status of the journal data set can be set to
READY by running the UPDATE function of the
DFHJC4540 date time applid There was an error opening DFHJACDU utility. For further information on this, see the
JACD. Journal archiving is not active. CICS Operations and Utilities Guide.
Explanation: An error occurred opening the journal archive Module: DFHJAP
control data set (JACD). If it was a VSAM open error, more
information will be available in the VSAM open error XMEOUT Parameters: date, time,applid, journalno, datasetid
message. Destination: Console and Transient Data Queue CSMT
System action: CICS initialization continues. As each journal
that is using journal archiving attempts to initialize, message
DFHJC4535 is issued, and the journal uses PAUSE mode. DFHJC4543D date time applid Journal data set journalno
User response: The decision must be made whether to stop datasetid is still not ready. Reply 'GO' or
CICS prematurely. Investigate the reason for the open failure 'SUBMIT'.
and correct before CICS is restarted. Ensure all journal data Explanation: 'GO' was entered to message DFHJC4542,
sets are archived as required. Then delete and redefine the DFHJC4543 or DFHJC4544, but the journal data set journalno
JACD. datasetid has still not been archived.
Module: DFHJAP System action: The system waits for the operator to reply.
User response: The user response is the same as for message
DFHJC4542.
Module: DFHJAP
XMEOUT Parameters: date, time,applid, journalno, datasetid
DFHJC4541 date time applid Journal journalno JACD records
disagree with the journal data sets. datasetid1
is now READY. The status of datasetid2 is
unaltered. DFHJC4544D date time applid Reply 'GO' when the archive
Explanation: During initialization, it was found that the completes or 'SUBMIT' if it has to be
information on the journal archive control data set (JACD) was resubmitted.
out of step with the actual journal data sets. Explanation: This message is issued after a reply of 'SUBMIT'
System action: CICS starts logging according to the
to either DFHJC4542 or DFHJC4543 or DFHJC4544. An archive
information on the journal data sets, not the information on
job will be submitted. At this stage, CICS does not know
the JACD. The data set that is to be used first is set to READY.
whether the archive job submitted has completed successfully.
The status of the other data set will remain unaltered.

This message (DFHJC4544) is issued so that CICS can be XMEOUT Parameters: date, time,applid, journalno, datasetid
informed of this. Destination: Console and Transient Data Queue CSMT
System action: The system waits for the operator to reply.
User response: Reply 'GO' if the archive job completes
successfully. If it does not, reply 'SUBMIT'. If the job continues DFHJC4549 date time applid Error acquiring storage during
to fail and this message is repeated, follow the user response initialization. Journal archiving not active.
for message DFHJC4542. Explanation: Journal archiving could not be started as a
Module: DFHJAP severe error has been detected by the storage manager
domain. There should have been a previous message on the
XMEOUT Parameters: date, time,applid console indicating what this error was.
Destination: Console and Transient Data Queue CSMT System action: CICS initialization continues.
User response: Take whatever action has been indicated in
the previous message which indicated the source of the error.
DFHJC4545 date time applid Journal data set journalno
You will be unable to use journal archiving for this session of
datasetid is READY. Archive not submitted.
CICS. CICS may be short on storage because you have not
Explanation: This message is be issued after a reply of
allocated enough storage for this run of CICS.
'SUBMIT' to DFHJC4542, DFHJC4543, or DFHJC4544. A
Module: DFHJAP
SUBMIT was requested, but the journal data set journalno
dataseid is READY. An archive job for this data set has XMEOUT Parameters: date, time,applid
probably just completed. Destination: Console and Transient Data Queue CSMT
System action: CICS continues, and opens the journal data
set.
User response: Check that the SUBMIT was for the correct DFHJC4550 date time applid Error while opening VSE
message or journal. source library. Archive for journalno datasetid
Module: DFHJAP not submitted.
Explanation: The VSE source library containing the archive
XMEOUT Parameters: date, time,applid, journalno, datasetid JCL could not be opened. This message is issued for every
Destination: Console and Transient Data Queue CSMT archive submitted.
User response: Investigate and correct the reason for the
DFHJC4547 date time applid DFHJASP could not be
open error. Manually submit an archive job for the journal
loaded. No journal archiving can be
data set journalno datasetid. The most likely cause of this is an
performed.
incorrect or missing LIBDEF for the source library.
Explanation: DFHJASP has failed to load during CICS
initialization. CICS could not find DFHJASP. This is probably Because the data set is reopened for each archiving operation,
because DFHJASP was not in a sublibrary of the LIBDEF it may be possible to correct this error while CICS is running
search chain for the CICS job. (for example, if there is a hardware error). Otherwise, when
System action: CICS initialization continues. Journal the problem is resolved, CICS has to be terminated and then
archiving controls the reuse of journal data sets, but no restarted.
archive submission is performed. When CICS attempts to Module: DFHJASP
submit an archive job, message DFHJC4548 is issued.
User response: Add DFHJASP to a sublibrary of the LIBDEF XMEOUT Parameters: date, time,applid, journalno, datasetid
search chain for the CICS job. DFHJASP cannot be used in this Destination: Console and Transient Data Queue CSMT
run of CICS. To use DFHJASP, stop CICS and restart.
Module: DFHJAP DFHJC4551 date time applid Connection to VSE/POWER
XMEOUT Parameters: date, time,applid RDR queue failed. Archive for journalno
Destination: Console and Transient Data Queue CSMT datasetid not submitted.
Explanation: The required connection to the VSE/POWER
RDR queue could not be opened. This message is issued for
DFHJC4548 date time applid DFHJASP is not active. every archive job submitted.
Archive for journal journalno datasetid will not System action: Processing continues.
be submitted. User response: Investigate the reason for the open error and
Explanation: The archive job could not be submitted because correct. Manually submit an archive job for the journal data
DFHJASP is not active. This message is normally followed by set journalo dataseid.
DFHJC4543.
System action: The archive job is not submitted. CICS As this connection is reopened for each archiving operation, it
processing continues. may be possible to correct this error while CICS is running
User response: Investigate the reason for DFHJASP not being (for example, if there is a hardware error). Otherwise, when
active. A possible reason is that DFHJASP was not loaded at the problem is resolved, CICS will have to be terminated and
CICS initialization, and message DFHJC4547 is issued to then restarted.
indicate this. See the explanation of message DFHJC4547 for Module: DFHJASP
guidance in resolving this problem. XMEOUT Parameters: date, time,applid, journalno, datasetid
Submit the archive job manually and set the status of the Destination: Console and Transient Data Queue CSMT
journal data set to READY, using the UPDATE function of the
DFHJACDU utility. This is documented in the CICS Operations
and Utilities Guide.
Module: DFHJAP

Manually submit an archive job for the journal data set

DFHJC4552 date time applid Member y could not be found
in the source library search chain. Archive for
journalno datasetid not submitted. If the problem persists, rerun with trace on to locate the
Explanation: An error occurred while trying to find member source of the error.
y in the VSE source library search chain for the partition. Module: DFHJASP
User response: Investigate and correct the reason for the XMEOUT Parameters: date, time,applid, y, journalno, datasetid
FIND error. Manually submit an archive job for the journal Destination: Console and Transient Data Queue CSMT
data set journalno datasetid.
The most likely reasons for this error are that member y does DFHJC4556 date time applid Error acquiring storage.
not exist in the source library which contains the skeletal JCL Archive for journalno datasetid not submitted.
for the archive jobs, or the 'LIBDEF SOURCE,SEARCH=' Explanation: The archive for journal data set journalno
statement does not contain the correct library. It may be that datasetid cannot be submitted because a severe error has been
the JCT parameter ARCHJCL was coded incorrectly, or it may detected by the storage manager domain. An associated
be because the member was incorrectly catalogued into the console message should have been issued indicating what this
source library. error is.
Module: DFHJASP System action: Processing continues.
User response: Take whatever action has been indicated in
XMEOUT Parameters: date, time,applid, y, journalno, datasetid the previous message then manually submit an archive job for
Destination: Console and Transient Data Queue CSMT the journal data set journalno datasetid. Set the status of the
journal data set to READY using the UPDATE function of the
DFHJACDU utility. For guidance on using the UPDATE
DFHJC4553 date time applid Archive job submitted for
function, see the CICS Operations and Utilities Guide.
Module: DFHJASP
Explanation: An archive job has been submitted for journal
data set journalno datasetid. XMEOUT Parameters: date, time,applid, journalno, datasetid
System action: The job is sent to the POWER queue. CICS Destination: Console and Transient Data Queue CSMT
continues.
Module: DFHJASP DFHJC4557 date time applid Error writing to VSE/POWER
RDR queue. Archive for journalno datasetid not
XMEOUT Parameters: date, time,applid, journalno, datasetid submitted.
Destination: Console and Transient Data Queue CSMT Explanation: During archive submission, an I/O error was
encountered writing to the VSE/POWER RDR queue.
DFHJC4554 date time applid JCL error building archive
User response: Investigate the reason for the I/O error. This
submission job. Archive for journalno datasetid
is probably due to a hardware error.
not submitted.
Explanation: During symbolic substitution, a JCL statement Manually submit an archive job for the journal data set
was built that went beyond position 72, but the statement journalno datasetid.
could not be continued. The JCL statement is invalid. CICS
has partially built the JCL up to the error condition. If the problem persists, rerun with trace on to locate the
System action: DFHJASP outputs everything in the JCL source of the error.
which has been done so far to the VSE/POWER RDR queue. Module: DFHJASP
User response: Investigate the reason for the overflow XMEOUT Parameters: date, time,applid, journalno, datasetid
condition by looking at the output from the JCL which was Destination: Console and Transient Data Queue CSMT
sent by CICS. The last statement in this JCL will be the one
which caused the invalid overflow. Perhaps a punctuation
mark has been omitted in the statement. DFHJC4558 date time applid XPCC FUNC=IDENT failed,
R15=return_code, IJBXRETC=ijbxretc
Correct the error online. The next time DFHJASP reads the Explanation: The XPCC FUNC=IDENT failed. This message
archive JCL from the VSE source library it picks up the is issued during DFHJASP initialisation.
updated JCL. But you need to manually submit the archive job System action: Job submission support is disabled for the
for journal data set journalno datasetid. rest of the CICS session.
Module: DFHJASP User response: Investigate the reason for the error based on
XMEOUT Parameters: date, time,applid, journalno, datasetid the XPCC R15 return code and XPCCB IJBXRETC as shown in
Destination: Console and Transient Data Queue CSMT the message. See the MAPXPCCB macro in the z/VSE System
Macros Reference for a list of the possible R15 and IJBXRETC
return codes. Manually submit an archive job for each journal
DFHJC4555 date time applid I/O error reading VSE source data set.
library member y. Archive for journalno
datasetid not submitted. When the problem is resolved, CICS will have to be
Explanation: During archive submission, an I/O error was terminated and and then restarted to allow automatic archive
encountered reading from the VSE source library containing job submission to occur again.
skeletal JCL for the archive jobs. Module: DFHJASP
System action: Processing continues. XMEOUT Parameters: date, time,applid, return_code, ijbxretc
User response: Investigate the reason for the I/O error. This Destination: Console and Transient Data Queue CSMT
is probably due to a hardware error.

This message could also arise if JACD is used in unauthorized

DFHJC4559 THERE WAS AN ERROR WHILE OPENING
ways.
DFHJACD.
System action: There are three possible system actions,
Explanation: The journal archive control data set (JACD)
depending on the circumstances:
could not be opened.
v CICS may not have this error (for example, if there is a fault
System action: The job ends with a condition code of 16.
in a channel in another CPC). In this case, CICS continues
User response: A condition code of 16 indicates that this is a
as before.
serious error. Do not proceed any further without correcting
v CICS may not have this error yet (for example, it may have
the error. Investigate the reason for the open error. A VSAM
switched journal data sets before encountering the problem).
message is issued with a VSAM return code. See the section
In this case, CICS continues as before until it meets the
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2
error.
for the meaning of the return code.
v CICS may have this error. In this case, automatic archiving
Module: DFHJACDU
may not continue. CICS goes to its fallback position of
Destination: SYSLST
PAUSE. Various messages from this area of CICS may then
be generated.
DFHJC4560 THERE HAS BEEN A PARAMETER ERROR User response: Investigate the reason for the missing data
xxxx and correct. Check that the correct journal data set has been
Explanation: An invalid parameter was passed to named. Then, either manually run any job step which was
DFHJACDU. The insert xxxx indicates the type of error. dependent on the CHECK. Or, if this was an UPDATE job,
System action: The job ends with a condition code of 16. since there is probably no further job step dependent on it,
User response: A condition code of 16 indicates that this is a there is no need for further action.
serious error. Do not proceed any further without correcting Module: DFHJACDU
the error. Correct the invalid parameter and resubmit the job. Destination: SYSLST
Module: DFHJACDU
Destination: SYSLST
DFHJC4563 THERE WAS AN ERROR WHILE OPENING
DFHJAPRT FILE.
DFHJC4561 I/O ERROR ACCESSING JOURNAL DATA Explanation: An error occurred trying to open DFHJAPRT.
SET journalno datasetid. THE VSAM RETURN This message is normally accompanied by a VSE message.
CODE IS rc System action: The job ends with a condition code of 16.
Explanation: An I/O error occurred while accessing the User response: The condition code of 16 indicates that this is
journal data set journalno datasetid on the journal archive data a serious error. Do not proceed any further without correcting
set (JACD) with VSAM return code rc. the problem. Refer to the accompanying VSE message for
System action: The job continues. further information about the error. Check whether the DLBL
User response: Investigate and correct the reason for the I/O statement is missing.
error. Look up the meaning of the VSAM return code in Module: DFHJACDU
section "VSE/VSAM Codes" in z/VSE Messages and Codes - Destination: Console
Volume 2.
Module: DFHJACDU
DFHJC4564 date time applid The JACD control interval size
Destination: SYSLST
is not 512 bytes.
Explanation: This is an OPEN error caused by having a
DFHJC4562 NO DATA HAS BEEN FOUND FOR journal archive data set (JACD) which does not have a control
interval size of 512 bytes.
JOURNAL DATA SET journalno datasetid
System action: The JACD closes and journal archiving is
Explanation: There was no data for the journal data set
inactive for this session of CICS. Message DFHJC4535 is
journalno datasetid on the journal archive control data set
issued for any journals with AUTOARCH specified.
(JACD). There are three functions for this program: LIST,
CHECK and UPDATE. CICS initialization continues.
User response: Redefine the JACD with the correct interval
If the function was LIST, data was found for journal data set size.
A, but the expected data for journal data set B was not found. Module: DFHJAP, DFHJACDU
There is an error in the JACD.
This could happen if CICS canceled during initialization. If the Destination: Console and Transient Data Queue CSMT
journal data sets were coded in the JCT with the AUTOARCH
option, the problem is automatically solved at the next CICS
initialization. If AUTOARCH is not coded and it is needed, the DFHJC4565 NO DATA HAS BEEN FOUND FOR
situation is not a problem and there is no need to investigate JOURNAL(S) journalno
further. Explanation: A journal was requested by the user to be listed
which was not found in the journal active data set (JACD).
If the function was CHECK or UPDATE, there are likely to be There was no data for the journal journalno on the JACD. This
two likely sources of the problem. If the user was specifying message is issued when an error is found in the LIST function.
the journal data set, the problem may simply be user error.
If the complete JACD was requested for listing, this message is
If the job has been submitted by CICS journal archiving, an issued for all journals not found. If specific journals from the
error has occurred, probably between job submission and job JACD were requested, this message is issued for any specified
execution. The journal data set information existed when CICS journals not found.
requested the job to be submitted, but this information has System action: The job continues.
since been destroyed. User response: The reason for the missing data is likely to be

a user error. Check the entries that have been created for all Module: DFHJCO
journals which use automatic archiving. Destination: Console
Module: DFHJACDU
DFHJC4584 applid AWAITING 'Ynnx' REPLY BEFORE
SWITCHING TO CICS {SYSTEM LOG |
DFHJC4566 applid Journal Archive failure whilst waiting JOURNAL nn} {PRIMARY | SECONDARY}
for I/O operation on DFHJACD to complete. DATA SET.
Explanation: A DISASTER type error occurred whilst the Explanation: Message DFHJC4583 was previously issued for
transaction was waiting for the completion of an I/O this disk data set. No reply was received. applid is the VTAM
operation on the VSAM file DFHJACD. This could be due to APPLID of the CICS system issuing this message.
an invalid IORB address or an internal error within CICS.
System action: All tasks using the journal are held up until a
System action: An exception trace entry containing the
'Ynnx' reply is received to message DFHJC4583.
response code, the reason code, the first 12 bytes of the
User response: See user response for DFHJC4583.
EXCPAD parameter list and the first 16 bytes of the IORB is
Module: DFHJCO
produced, and a system dump is taken. The caller is passed
back a return code indicating an I/O error. Destination: Console
User response: This problem was caused by an earlier error.
Look for earlier messages and return codes (for example, from DFHJC4586 applid CICS {SYSTEM LOG | JOURNAL nn}
the dispatcher domain) and associated trace entries and {PRIMARY | SECONDARY} DATA SET IS
dumps. NOT READY. PLEASE REPLY Ynnx WHEN
If the problem cannot be traced to an application error, you READY.
will require further assistance from IBM. See Part 4 of the Explanation: You have entered an incorrect reply to message
CICS Problem Determination Guide for guidance on how to DFHJC4583. See message DFHJC4583 for an explanation of its
proceed. meaning. Possibly the journal named has just switched from
Module: DFHJAP AUTOARCH to PAUSE due to an error on the journal archive
control data set (JACD), and this is indicated by message
XMEOUT Parameter: applid DFHJC4536.
Destination: Console System action: CICS does not reuse the specified data set
until the requested reply is received.
User response: Reply 'Ynnx' as soon as possible (or
DFHJC4571 AN ERROR (CODE X'code') HAS immediately, if no copy is to be performed).
OCCURRED IN THE USER EXIT Module: DFHJCO, DFHJCP
PROGRAM. Destination: Console
Explanation: An error has been detected in the user exit
program. The code code is the value returned in register 15
from the exit program to DFHJUP. The journal print utility DFHJC4587 date time applid Unable to invoke Journal exit
terminates without processing any remaining OPTION cards. DFHXJCO
User response: Correct the error in the user exit program and Explanation: The DFHPC link for the journal exit DFHXJCO
resubmit the job. has failed.
Module: DFHJUP System action: The task that issued the request abends with
Destination: SYSLST abend code AJCH and a transaction dump is produced. If this
error occurs while the system log is being opened during
initialization, initialization cannot be completed and CICS
DFHJC4583 applid CICS {SYSTEM LOG | JOURNAL nn} abends.
{PRIMARY | SECONDARY} DATA SET User response: This is probably a setup error. Make sure that
(FILENAME=DFHJnnx) READY TO BE DFHXJCO is in the program library.
COPIED. REPLY 'Ynnx' WHEN COPIED. Module: DFHJCO
Explanation: JOUROPT=PAUSE is specified in the JCT entry
for disk journal nn. CICS has closed the specified data set of XMEOUT Parameters: date, time,applid
the journal, and you should now copy it (if required, for Destination: Console and Transient Data Queue CSMT
example, for forward recovery). applid is the VTAM APPLID of
the CICS system issuing this message. In the requested reply:
v nn is the journal number from the message DFHJC4588 applid Journal Exit {DFHXJCC | DFHXJCO}
v x is A for a primary data set and B for a secondary data set. has abnormally terminated with abend code
System action: CICS does not reuse the specified data set for abcode.
output until the requested reply is received. If you enter an Explanation: An abend has occurred in the user replaceable
module (URM), and there is no HANDLE ABEND command
incorrect reply, CICS issues message DFHJC4586.
active. If the message text contains DFHXJCO, it has been
If you do not enter a correct reply before CICS attempts to issued by DFHJCO. If it contains DFHXJCC, it has been issued
reuse the specified data set for output, CICS issues message by DFHJCC. The abend code relates to the abend within the
DFHJC4584. Tasks using journal nn are be delayed until you URM.
reply correctly to the original DFHJC4583 message. System action: The task that issued the request abends and a
transaction dump is produced. If this error occurs while the
For a single data set journal, CICS closes the journal data set system log is being opened during initialization, initialization
when it is full, and issues messages DFHJC4583 and cannot be completed and CICS abends.
DFHJC4584. User response: This is probably caused by a programming
User response: Copy the disk data set if necessary. Reply error within the URM. Use the abend code produced to
'Ynnx' when copy complete (or immediately, if no copy is determine the reason for the error. This could be the result of
wanted). For each journal, reply to messages in the order in a condition being raised for which there was no handle
which they were issued. command; in which case the default action is taken, to abend

the transaction. It is also possible that an invalid EXEC more information about determining the necessary size of the
command has been used within the URM. For a list of EXEC journal data set, refer to the CICS System Definition and
commands permissable within the journalling URMs see the Operations Guide.
CICS Customization Guide. Module: DFHJCJFP
Module: DFHJCC, DFHJCO Destination: Console
XMEOUT Parameters: applid, {1=DFHXJCC, 2=DFHXJCO},
abcode DFHJC4599 JOURNAL DATA SET INITIALIZED - nnnnn
Destination: Console {TRACKS | BLOCKS} FORMATTED.
Explanation: The CICS journal formatting utility program
issues this informatory message, indicating that the specified
DFHJC4589 date time applid Unable to invoke Journal exit number of tracks/blocks are correctly preformatted for use as
DFHXJCC a CICS disk journal output data set.
Explanation: The DFHPC link for the journal exit has failed. System action: The utility continues processing.
System action: The task that issued the request abends with User response: None.
abend code AJCH and a transaction dump is produced. If this Module: DFHJCJFP
error occurs while the system log is being opened during Destination: Console
initialization, then initialization cannot be completed and CICS
will abend.
User response: This is probably a setup error. Make sure that DFHJC5610 date time applid DFHJCP DMF problem n
DFHXJCC is in a sublibrary of the LIBDEF search chain for Explanation: JCP has called DFHASV to issue the
the CICS job. DFHSMFEW macro. The return code is n, with the following
Module: DFHJCC meanings:
XMEOUT Parameters: date, time,applid Code Meaning
Destination: Console and Transient Data Queue CSMT 1 DMF record larger than 32KB.
2 Record is not a CICS record.
3 A page fix or page free cannot be performed
DFHJC4596 JOURNAL DATA SET NOT INITIALIZED -
probably because the CICS SVC is disabled.
I/O ERROR OCCURRED.
Explanation: The journal data set is not initialized. An I/O 5 Insufficient storage. There was insufficient storage to
error has occurred. fulfil a write to DMF.
System action: Execution of utility program DFHJCJFP is System action: The request is ignored. CICS continues.
abnormally terminated with a dump. The VSE user abend User response: Notify the system programmer. The user has
code is 0117. indicated with JCT that the journal is to go to the Data
User response: If the error recurs immediately, inform the Management Facility (JCT JTYPE=SMF). This is only
person(s) responsible for debugging system errors of the supported in DFHASV, and the JCT must be assembled on
condition, and give the dump(s) to that person. VSE.
Module: DFHJCJFP Module: DFHJCP
XMEOUT Parameters: date, time,applid, n
Destination: CSMT
DFHJC4597 JOURNAL DATA SET NOT INITIALIZED -
UNABLE TO OPEN FILE. CHECK DLBL
SUPPLIED. DFHJC6100 FORMAT TAPE.
Explanation: The journal data set is not initialized. Unable to Explanation: Execution of the tape-formatting program
open the file. (DFHFTAP) has started.
System action: Execution of the utility program DFHJCJFP System action: The program continues.
terminates abnormally. User response: None.
User response: Ensure that DLBL,EXTENT and ASSGN Module: DFHFTAP
statements are supplied and are correct, then rerun the job. Destination: SYSLST
Module: DFHJCJFP
DFHJC6101 UNABLE TO OPEN MESSAGE DATASET.
Explanation: The SYSOUT message data set could not be
DFHJC4598 JOURNAL DATA SET NOT INITIALIZED - opened, possibly because no DLBL statement was supplied.
INSUFFICIENT SPACE HAS BEEN System action: Execution of the program DFHFTAP is
ALLOCATED. abnormally terminated.
Explanation: The journal data set has not initialized. The User response: Supply the proper DLBL statement and rerun
formatting utility program DFHJCJFP has found that the the program.
allocated space on the EXTENT statement for journal data set Module: DFHFTAP
is inadequate for CICS journaling requirements. Destination: Console
System action: Execution of the utility program DFHJCJFP
terminates abnormally with a completion code of 16.
User response: The condition code of 16 indicates that this is DFHJC6102 UNABLE TO ALLOCATE WORKING
a serious error. Do not proceed any further without correcting STORAGE. DFHFTAP TERMINATES
it. ABNORMALLY.
Increase the number of tracks or blocks specified on the Explanation: Storage was not available for this program.
EXTENT statement for the journal data set. The minimum size System action: Program execution is abnormally terminated.
required is 3 tracks if using CKD devices, or 200 blocks is User response: Increase the partition size and rerun.
using FBA devies. The allocated space must be contiguous. For Module: DFHFTAP

Destination: SYSLST
DFHJC6111 INVALID REPLY x
Explanation: The response to message DFHJC6110 was
DFHJC6103 UNABLE TO OPEN LOG VOLUME. neither Y or N. The response was x.
DFHFTAP TERMINATES ABNORMALLY. System action: Message DFHJC6110 is reissued.
Explanation: The operator log data set could not be opened, User response: None.
possibly because no DLBL statement was supplied. Module: DFHFTAP
System action: Program execution is abnormally terminated. Destination: Console
User response: Supply the proper DLBL statement and rerun
the program.
DFHJC6199 nnnn VOLUME(S) FORMATTED - FORMAT
Module: DFHFTAP
TAPE ENDED.
Destination: SYSLST
Explanation: This message is issued at the end of the job.
nnnn is the number of volumes that were formatted.
DFHJC6104I DISCONTINUED PROCESSING ON LOG System action: The program is terminated.
VOLUME DUE TO xxxxxxxx ERROR, User response: None.
PROGRAM PROCEEDING TO NEXT Module: DFHFTAP
VOLUME. Destination: SYSLST
Explanation: An error occurred on initialization of a log
volume, which caused the volume to be rejected. This message
is followed by message DFHJC6110.
System action: Message DFHJC6110 is issued asking if more
log volumes are to be formatted.
User response: Look for any accompanying access method
messages to determine the cause of the error.
Module: DFHFTAP
DFHJC6105 UNRECOVERABLE I/O ERROR

OCCURRED. DFHFTAP TERMINATES
ABNORMALLY.
Explanation: A hardware error occurred on an I/O device
but recovery was not possible.
System action: Program execution is abnormally terminated.
Module: DFHFTAP
Destination: SYSLST
DFHJC6107I LOG VOLUME FORMATTED.

Explanation: The log volume has been formatted successfully.
System action: The volume is closed and message
DFHJC6110 is issued.
Module: DFHFTAP
DFHJC6110D MORE VOLUMES TO BE FORMATTED.

REPLY 'Y', 'N' or 'VOLUME SERIAL
NUMBER'.
Explanation: This message is issued after message
DFHJC6107I, and asks if more log volumes are to be
formatted.
System action: If the reply is Y, the next log volume is
opened. If the reply is N, the program is terminated.
User response: Reply 'Y' if more log volumes are to be
formatted, otherwise reply 'N'. For labeled tapes, the reply
may be the next volume serial number.
Module: DFHFTAP

DFHKC0102 • DFHKC0302
DFHKCxxxx messages
in the LIBDEF search chain for the CICS startup job stream.
DFHKC0102 date time applid terminal userid tranid PFT entry
System action: CICS terminates abnormally with a dump.
for profname has been added.
User response: To correct this error, place DFHKCRP in a
Explanation: This is an audit log message indicating that
sublibrary in the LIBDEF search chain for the CICS startup job
profile entry profname has been added to the CICS profile table
stream.
(PFT) using the INSTALL command.
Module: DFHKCQ
terminal is the netname or termid of the terminal at which the
INSTALL command was entered.
userid is the user identifier of the operator performing the
INSTALL command.
DFHKC0302 applid Transaction Manager restart failed.
tranid is the transaction used to perform the INSTALL Reason - rc.
command. Explanation: During transaction manager initialization, CICS
System action: The system continues normally. executes the following steps in the order in which they are
User response: None. listed:-
Module: DFHKCQ 1 Building the program control table directory
3 Purging transaction definitions from the RSD
catalog, using DFHCCP. (COLD start after a
profname
previous run.)
Destination: CSKL
4 Purging transaction definitions from the recovery
file, using DFHRCP. (COLD start after a run that
DFHKC0104 date time applid terminal userid tranid PFT entry used the system log.)
for profname has been deleted. 5 Restoring transaction definitions from the RSD
Explanation: This is an audit log message indicating that catalog, using DFHCCP. (WARM or EMERGENCY
profile entry profname has been deleted from the CICS profile restart.)
table (PFT) using the DISCARD command. 6 Recovering transaction definitions from the recovery
file, using DFHRCP. (EMERGENCY restart.)
terminal is the netname or termid of the terminal at which the
8 Purging profile definitions from the RSD catalog,
DISCARD command was entered.
using DFHCCP. (COLD start after a previous run.)
userid is the user identifier of the operator performing the 9 Purges profile definitions from the recovery file,
DISCARD command. using DFHRCP. (COLD start after a run that used
the system log.)
tranid is the transaction used to perform the DISCARD
10 Restoring profile definitions from the catalog, using
command.
DFHCCP. (WARM or EMERGENCY restart.)
11 Recovering profile definitions from the recovery file,
Module: DFHKCQ using DFHRCP. (EMERGENCY restart.)
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, The transaction manager restart has failed for reason rc, where
profname rc indicates the job step that did not complete successfully.
Destination: CSKL Subsequent steps have not been attempted.
System action: CICS terminates the task under which
DFHKC0106 date time applid terminal userid tranid PFT entry DFHKCRP is running with an AKCB abend code, and issues
for profname has been replaced. message DFHSI1521.
Explanation: This is an audit log message indicating that User response: Examine the trace in the CICS AKCB
profile entry profname has been replaced in the CICS profile transaction dump to see the history of the task that DFHKCRP
table PFT using the INSTALL command. is running under for further information regarding the precise
cause of the failure.
terminal is the netname or termid of the terminal at which the Module: DFHKCRP
INSTALL command was entered.
XMEOUT Parameters: applid, rc
userid is the user identifier of the operator performing the
INSTALL command.
tranid is the transaction used to perform the INSTALL
command.
Module: DFHKCQ
profname
Destination: CSKL
DFHKC0301 applid Program DFHKCRP cannot be found.

Explanation: The transaction manager recovery program is
not available. CICS cannot find DFHKCRP in any sublibrary

DFHKE0001 • DFHKE0004
DFHKExxxx messages
DFHKE0001 applid An abend (code aaa/bbbb) has occurred
code is sent to the caller of this domain. In this case, CICS
manager, DFHDMDM). A message will be issued to this effect.
input, or storage has been overwritten. Message DFHME0116 is normally produced containing the
User response: This indicates a possible error in CICS code.
hyphens. The CICS code is an abend code or a number CICS may not have been terminated.
abend code; 1310 refers to message DFHTS1310). If the message occurs once and module modname is not crucial
During initialization, CICS may not have access to the user's continue to run and bring CICS down at a convenient time to
applid coded in the SIT. If CICS produces this message in these resolve the problem.
System action: An exception entry is made in the trace table. If the message recurs or if you cannot run without the full use
A system dump is taken, unless you have specifically of module modname you should bring CICS down in a
suppressed dumps in the dump table. controlled shutdown.
CICS continues unless you have specified in the dump table You need further assistance from IBM to resolve this problem.
that CICS should terminate. See Part 4 of the CICS Problem Determination Guide for
Message DFHME0116 is normally produced containing the Module: DFHKEDD, DFHKEGD, DFHKEIN
User response: If CICS is still running, it is necessary to XMEOUT Parameters: applid, X'code',modname
decide whether to terminate CICS. Destination: Console

Codes" in section "VSE/Advanced Functions Codes & SVC DFHKE0004 applid A possible loop has been detected at
Errors" of z/VSE Messages and Codes - Volume 1. offset X'offset' in module modname.
Next, look up the CICS alphanumeric code in “Transaction than CICS expects. A possible loop has been detected in
Abend Codes (CICS Transaction Server for VSE/ESA)” on module modname at offset X'offset'. This is the offset of the
page 453. This tells you, for example, whether the error was a instruction which was executing at the time the error was
program check, an abend, or a runaway, and may give you detected.
some guidance concerning user response.
If module modname is not crucial to the running of your CICS applid coded in the SIT. If CICS produces this message in these
system, you may decide to continue to run and bring CICS circumstances, it uses the default applid value DBDCCICS.
down at a convenient time to resolve the problem. System action: An exception entry is made in the trace table.
If you cannot run without the full use of module modname you A system dump is taken, unless you have specifically
should bring CICS down in a controlled shutdown. suppressed dumps in the dump table.
You need further assistance from IBM to resolve this problem. CICS continues unless you have specified in the dump table
See Part 4 of the CICS Problem Determination Guide for that CICS should terminate.
guidance on how to proceed. Message DFHME0116 is normally produced containing the
Module: DFHKEDD, DFHKEDS, DFHKEGD, DFHKETI symptom string for this problem.
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname User response: Notify the system programmer. If CICS has
Destination: Console not been terminated, it is necessary to decide whether the
DFHKE0002 applid A severe error (code X'code') has
function which exceeds the runaway task time interval which
For further information about CICS exception trace entries, see that module modname is terminated and CICS continues.
the CICS Problem Determination Guide.
But if you have declared ICVR=0 and you consider that
During initialization, CICS may not have access to the user's module modname has gone into a loop, you have to terminate
applid coded in the SIT. If CICS produces this message in these CICS in order to terminate the runaway function.
If CICS has terminated module modname and you consider
System action: An exception entry (code X'code' in the
message) is made in the trace table. A system dump is taken,
unless you have specifically suppressed dumps in the dump
this permanently. However, you can change the ICVR time
table.

interval temporarily online, using the CEMT transaction. you will need to bring CICS down to do this. See the CICS
System Definition and Operations Guide or the CICS Performance
If raising the ICVR time does not solve the problem, you will Guide for further information on CICS storage.
need further assistance from IBM. See Part 4 of the CICS Module: DFHKEIN
Module: DFHKEDD, DFHKEDS, DFHKEGD, DFHKETI XMEOUT Parameters: applid, X'code',modname, vsecode
DFHKE0101 applid UNABLE TO OBTAIN SUBSYSTEM
STATUS. CICS WILL TERMINATE.
DFHKE0005 applid A hardware error has occurred (module Explanation: Part of CICS initialization must be done in an
modname, code X'code'). The Time-of-Day clock VSE-authorized state. The kernel has been unable to obtain
is invalid. this state.
running of module modname. The store clock facility is the This indicates a internal error in the interface between CICS
timing mechanism for the operating system. and VSE.
System action: CICS terminates. The CICS job step
The code code is the exception trace point ID which uniquely terminates with return code 12.
identifies the place where the error was detected. User response: Contact the IBM support center.
During initialization, CICS may not have access to the user's Module: DFHKESIP
applid coded in the SIT. If CICS produces this message in these Destination: Console
DFHKE0102 applid UNSUCCESSFUL PRE-
INITIALIZATION OF domain DOMAIN.
CICS WILL TERMINATE.
CICS continues unless you have specified in the dump table Explanation: A domain has failed to pre-initialize and as a
that CICS should terminate. result the system will terminate.
User response: If CICS is still running, it is necessary to
decide whether to terminate CICS. This is probably a
hardware error and you should first investigate the store clock
and find out whether it is working properly. If this is the
cause, you should take the appropriate action to have it Since this problem has occurred so early in CICS initialization,
repaired or replaced. possible causes include a severe lack of storage or corruption
of the local catalog.
will need further assistance from IBM. See Part 4 of the CICS
User response: Inform the system programmer. If a dump is
taken investigate this problem using the exception trace which
Module: DFHKETI
is issued by the failing domain. If no dump is taken, check for
preceding messages issued by the failing domain to explain
the reason for the error.
DFHKE0006 applid Insufficient storage to satisfy Getmain You may need further assistance to resolve this problem. See
(code X'code') in module modname. VSE code Part 4 of the CICS Problem Determination Guide for guidance on
vsecode. how to proceed.
Explanation: A OS/390 GETMAIN was issued by module Module: DFHKETCB.
modname but there was insufficient storage available to satisfy Destination: Console
the request.
DFHKE0103 applid LOAD FOR DFHEIVD1 IN MODULE
DFHKETCB FAILED WITH RETURN CODE
The code vsecode is the OS/390 GETMAIN return code. code. CICS WILL TERMINATE.
Explanation: The kernel has issued a OS/390 LOAD for
During initialization, CICS may not have access to the user's DFHEIVD1 which has failed.
circumstances, it uses the default applid value DBDCCICS. The code code is the OS/390 LOAD return code.
System action: CICS will terminate with a system dump. An
exception entry is made in the trace table (code code in the
message).
Message DFHME0116 is normally produced containing the System action: CICS terminates. The CICS job step
symptom string for this problem. terminates with return code 12.
User response: Inform the system programmer. User response: Inform the system programmer.
See "OS/390 API Return Codes" in section "VSE/Advanced To resolve the problem, use the LOAD return code vsecode to
Functions Codes & SVC Errors" of z/VSE Messages and Codes - determine why the LOAD failed. See "OS/390 API Return
Volume 1 for diagnostic information about the VSE return Codes" in section "VSE/Advanced Functions Codes & SVC
code. Errors" of z/VSE Messages and Codes - Volume 1 for diagnostic
information about the OS/390 LOAD return code.
Try decreasing the overall size limit of the DSAs or EDSAs. Module: DFHKETCB.
Or, try increasing the size of the CICS partition, if it is not Destination: Console
already at maximum size. If CICS is not already terminated,

DFHKE0105 applid DFHEVAS LOAD FAILED WITH DFHKE0202 applid SDUMP COMPLETE. (MODULE
RETURN CODE code. CICS WILL modname).
TERMINATE. Explanation: This message is issued on successful completion
Explanation: The load of DFHEVAS has failed. DFHEVAS of an SDUMPX.
must be loaded before CICS can initialize.
During initialization, CICS may not have access to the user's applid coded in the SIT. If CICS produces this message in these
applid coded in the SIT. If CICS issues this message in these circumstances, it uses the default applid value DBDCCICS.
circumstances, it uses the default applid value DBDCCICS. System action: CICS will terminate.
System action: CICS terminates. The CICS job step User response: Print off the system dump if required. A
terminates with return code 12. previous VSE message identifies the SYSDUMP library name
User response: The return code comes from the VSE and which member of the SYSDUMP library contains the
CDLOAD macro. A list of these codes can be found with the dump.
description of CDLOAD macro in the z/VSE System Macros Module: DFHKEDD, DFHKEDS, DFHKEGD, DFHKEIN,
Reference manual. Correct the reason for the failure and restart DFHKESTX
CICS. Destination: Console
Module: DFHKESIP
DFHKE0210 applid SDUMP REQUEST FAILED.
(MODULE modname) - reason.
DFHKE0106 applid DFHEVAS INITIALIZATION FAILED Explanation: A VSE SDUMPX request from CICS signalled
WITH RETURN CODE code. CICS WILL by message DFHKE0201 has failed to complete successfully.
TERMINATE. The possible reasons reason for the failure are detailed below.
Explanation: The initialization of DFHEVAS has failed. SDUMPX RETURN CODE X'nn' ONLY PARTIAL DUMP
DFHEVAS must be initialized before CICS can initialize. The number of storage areas to be dumped exceeds
the maximum allowed for one SDUMPX request.
SDUMPX RETURN CODE X'nn' REASON X'mm' NO
applid coded in the SIT. If CICS issues this message in these
SYSDUMP LIBRARY
System action: CICS terminates. The CICS job step No SYSDUMP library is defined for the CICS job. If
terminates with return code 12. the VSE SYSDUMPC job control option is in effect
User response: Notify the system programmer. for the CICS job the dump is suppressed, otherwise
the dump is redirected to SYSLST.
The most likely cause of this message is a lack of partition SDUMPX RETURN CODE X'nn' REASON X'mm'
GETVIS. Return codes 40, 42, 43, 80, 81, and 200 signify SYSDUMP LIBRARY IS FULL
problems acquiring GETVIS from above the 16MB line The SYSDUMP library defined for the CICS job is
whereas return codes 41 and 201 signify problems acquiring full. If the SYSDUMPC job control option is in effect
GETVIS from below the 16 MB line. for the CICS job the dump is suppressed, otherwise
If the unlikely event is not due to a lack of GETVIS you will the dump is redirected to SYSLST.
need further assistance from IBM to resolve the problem. See SDUMPX RETURN CODE X'nn' REASON X'mm'
Part 4 of the CICS Problem Determination Guide for guidance on VSE rejected the SDUMPX request for some other
how to proceed. reason than those listed above. X'nn' gives the
Module: DFHKESIP hexadecimal SDUMPX return code and X'mm' gives
Destination: Console the hexadecimal SDUMPX reason code.
SDUMPX is not authorized for this CICS run.
DFHKE0201 applid ABOUT TO TAKE SDUMP. INSUFFICIENT STORAGE
DUMPCODE: dumpcode, DUMPID: dumpid. CICS issued a OS/390 GETMAIN for storage during
(MODULE modname). the processing of the SDUMPX request. The
Explanation: An error during pre-initialization or
GETMAIN was rejected by VSE.
termination, possibly signalled by a previous message, has
DFHDUSVC FESTAE FAILED. FESTAE RETURN CODE
caused the kernel domain to take a dump, which will issue
X'nn' CICS issued a OS/390 FESTAE request from
this message immediately before calling the VSE SDUMP
DFHDUSVC during the processing of the SDUMPX
facility.
request. The FESTAE has been rejected by VSE.
The dump code dumpcode is the 8-character dump code DFHDUSVC FUNCTION INVALID
'KERNDUMP'. CICS called DFHDUSVC during the processing of
the SDUMPX request. The function passed to
The dumpid dumpid is the string '0/0000'.
DFHDUSVC was invalid.
applid coded in the SIT. If CICS produces this message in these During initialization, CICS does not have access to the user's
circumstances, it uses the default applid value DBDCCICS. applid coded in the SIT. If CICS produces this message in these
System action: When the dump is complete, message number circumstances, it uses the default applid value DBDCCICS.
DFHKE0202 is issued. System action: CICS proceeds as if the dump had been
User response: Inform the system programmer. See the successful.
associated dump and error messages for further guidance. User response: The user response depends on the reason for
Module: DFHKEDD, DFHKEDS, DFHKEGD, DFHKEIN,
the failure. For:
DFHKESTX
SDUMP RETURN CODE X'nn' ONLY PARTIAL DUMP
Use VSE problem determination methods to
determine why a partial dump was taken. See the

z/VSE System Macros Reference manual for a

DFHKE0301 applid Insufficient storage to satisfy Getmain
description of this return code.
in module modname. VSE code vsecode.
SDUMPX RETURN CODE X'nn' REASON X'mm' NO Explanation: The kernel (KE) domain has issued a OS/390
SYSDUMP LIBRARY AVAILABLE GETMAIN for kernel stack storage, but there was insufficient
Define a SYSDUMP library for the CICS job and storage available to satisfy the request.
then cause the SDUMP request to be reissued. See
the z/VSE Diagnosis Tools manual for a description of The code vsecode is the OS/390 GETMAIN return code.
SDUMPX RETURN CODE X'nn' REASON X'mm' applid coded in the SIT. If CICS produces this message in these
SYSDUMP LIBRARY IS FULL circumstances, it uses the default applid value DBDCCICS.
Clear some dumps from the dump library and cause System action: CICS terminates abnormally with a system
the SDUMP request to be reissued. See the z/VSE dump. No exception entry is made in the trace table since a
Diagnosis Tools manual for a description of how to call to the trace (TR) domain would itself require kernel stack
delete or offload a dump from the SYSDUMP storage.
library. User response: Inform the system programmer.
No action is required if the dump was suppressed See "OS/390 API Return Codes" in section "VSE/Advanced
deliberately. If the dump failed because of an error Functions Codes & SVC Errors" of z/VSE Messages and Codes -
in the VSE SDUMPX routine, use VSE problem Volume 1 for diagnostic information about the GETMAIN
return code. Also look at the kernel domain section of the
system dump to see how the kernel stack storage has been
cause the SDUMP request to be reissued.
used up.
This reason should not appear, because an SDUMP Try decreasing the size limits of the DSAs or EDSAs. Or, try
is unconditionally authorized during CICS increasing the size of the whole region, if it is not already at
initialization, and should be authorized throughout maximum size. See the CICS System Definition and Operations
the CICS run. If you do get this reason, the CICS Guide or the CICS Performance Guide for further information on
AFCB (authorized function control block) has CICS storage.
probably been accidentally overwritten. Module: DFHKESGM
INSUFFICIENT STORAGE Destination: Console
Ensure sufficient partition storage is available to
OS/390 GETMAIN requests.
DFHKE0302 applid Freemain of stack storage failed in
DFHDUSVC FESTAE FAILED. FESTAE RETURN CODE module modname. VSE code vsecode.
X'nn' Use VSE problem determination methods to fix the Explanation: The kernel (KE) domain has issued a OS/390
OS/390 FESTAE failure and then cause the SDUMP FREEMAIN for kernel stack storage, but a bad return code
to be reissued. See "OS/390 API Return Codes" in was returned.
section "VSE/Advanced Functions Codes & SVC
Errors" of z/VSE Messages and Codes - Volume 1 for an The code vsecode is the OS/390 FREEMAIN return code.
explanation of the FESTAE return code. During initialization, CICS may not have access to the user's
DFHDUSVC FUNCTION INVALID applid coded in the SIT. If CICS produces this message in these
The CICS DAFPB (dump authorized function circumstances, it uses the default applid value DBDCCICS.
parameter block) has probably been accidentally System action: CICS terminates abnormally with a system
overwritten. dump. No exception entry is made in the trace table since a
call to the trace (TR) domain would itself require kernel
Notify the system programmer. If CICS is still
linkage.
running, it will be necessary to decide whether to
User response: Inform the system programmer.
terminate CICS.
See "OS/390 API Return Codes" in section "VSE/Advanced
You may decide to continue to run and bring CICS
down at a convenient time to resolve the problem. Volume 1 for diagnostic information about the FREEMAIN
To resolve the problem, collect any dumps and any return code.
relevant messages and contact your IBM Support Module: DFHKEDS
Center. Destination: Console
Further guidance on how to prepare information for

IBM support is given in the CICS Problem DFHKE0303 applid A RECURSIVE ABEND HAS BEEN
Determination Guide. If you are not familiar with this DETECTED BY THE KERNEL DOMAIN.
process, refer to the guide before contacting IBM Explanation: The kernel (KE) domain has detected that the
current task is recursively abending while attempting to
support.
recover from an abend.
Module: DFHKEDD, DFHKEDS, DFHKEGD, DFHKEIN,
System action: CICS terminates abnormally with a system
DFHKESTX
dump. No exception entry is written to the trace table because
the trace (TR) domain may be the cause of the loop.
User response: Use the dump provided to investigate the
kernel error table to diagnose the earlier abends for the failing
task.
Module: DFHKERRI

DFHKE0999 • DFHLD0002
Explanation: This message is issued when CICS has

DFHKE0999 applid VSE HAS CALLED DFHKESTX WITH
terminated.
NO SDWA. ABEND CODE X'code'.
Explanation: VSE has made a call to the CICS ESTAE-type During initialization, CICS may not have access to the user's
recovery routine DFHKESTX, but it supplied no system applid coded in the SIT. If CICS produces this message in these
diagnostic work area (SDWA). DFHKESTX is unable to circumstances, it uses the default applid value DBDCCICS.
continue with the recovery. System action: Control is given back to the operating system.
Module: DFHKESIP
System action: Module DFHKESTX produces a system dump
and percolates the error to the next ESTAE routine. This is DFHKE1800 applid ABNORMAL TERMINATION OF
potentially a serious error. CICS continues processing pending CICS IS COMPLETE.
the result of the error percolation. Explanation: CICS issues this message when it terminates
User response: The abend code X'code' is the reason the CICS abnormally.
ESTAE was called. You need to find out which product has
produced the abend. Typically it is a VSE system completion During initialization, CICS may not have access to the user's
code, for example 0C1. However the abend may have been applid coded in the SIT. If CICS produces this message in these
issued by CICS, for example abend 1596, or another product. circumstances, it uses the default applid value DBDCCICS.
System action: The abnormal termination of CICS continues.
Since there is little further diagnostic information in this case, The kernel returns control to the operating system by issuing a
look for any messages that may indicate the reason for the user 1800 abend.
abend. The entry in the appropriate manual for the abend
code gives user guidance regarding the error, and may also The original error which caused the abnormal termination
give some guidance concerning the appropriate user response. may also have produced a dump. No specific dump is
produced to accompany this message.
The reason why no SDWA was passed and subsequently no User response: If a dump is produced, check the dump to
recovery was attempted is probably a shortage of storage. This determine the cause of the error. Use the CICS Problem
storage shortage may also be an influencing factor in the Determination Guide to assist you to determine the problem.
abend itself.
Module: DFHKESTX If no dump is produced, check for other CICS and VSE
Destination: Console messages and abend codes to help you to determine the cause
of the problem.
Module: DFHKESIP
DFHKE1799 applid TERMINATION OF CICS IS Destination: Console
COMPLETE.
DFHLDxxxx messages
abend using the system dump and any previously output
DFHLD0001 applid An abend (code aaa/bbbb) has occurred
diagnostic information provided by CICS, the access methods,
or the operating system.
occurred in module modname. This implies that there may be Look up the VSE code, if there is one, in "OS/390 API Abend
an error in CICS code. Alternatively, unexpected data has been Codes" in section "VSE/Advanced Functions Codes & SVC
input, or storage has been overwritten. Errors" of z/VSE Messages and Codes - Volume 1
The code aaa/bbbb is a three digit hexadecimal VSE code (if Next, look up the CICS alphanumeric code in “Transaction
applicable), followed by a four digit alphanumeric CICS code. Abend Codes (CICS Transaction Server for VSE/ESA)” on
The VSE code is a system completion code, for example 0C1. page 453. This tells you, for example, whether the error was a
If an VSE code is not applicable, this field is filled with three program check, an abend, or a runaway, and may give you
hyphens. The CICS code is an abend code or a number some guidance concerning user response.
abend code; 1310 refers to message DFHTS1310). You may need further assistance from IBM to resolve this
During initialization, CICS may not have access to the user's for guidance on how to proceed.
applid coded in the SIT. If CICS produces this message in these Module: DFHLDDM, DFHLDDMI, DFHLDLD, DFHLDLD1,
circumstances, it uses the default applid value DBDCCICS. DFHLDLD2, DFHLDLD3, DFHLDNT, DFHLDST
The program status word (PSW) at the time of the program XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
check or abend indicated that CICS was executing at offset Destination: Console
X'offset' in module modname. This may have been caused by
corruption of CICS code or control blocks.
System action: An exception entry is made in the trace table. DFHLD0002 applid A severe error (code X'code') has
A system dump is taken, unless you have specifically occurred in module modname.
suppressed dumps in the dump table. Explanation: The loader has received an unexpected error
response from some other part of CICS or an operating system
CICS continues unless you have specified in the dump table service. The operation requested by the loader is described by
that CICS should terminate. code X'code'.
Message DFHME0116 is normally produced containing the For further information about CICS exception trace entries,
symptom string for this problem. refer to the CICS Problem Determination Guide.
User response: Investigate the cause of the program check or System action: A system dump is taken and the system

DFHLD0004 • DFHLD0105
attempts to continue operation unless specifically inhibited by symptom string for this problem.
dump table entries. User response: This message diagnoses an internal error
within CICS. Investigate whether previous errors have left
Message DFHME0116 is normally produced containing the CICS in a damaged state. If there is no evidence of previous
symptom string for this problem. serious errors, you will need further assistance from IBM to
User response: Investigate the cause of the problem as resolve the problem. See Part 4 of the CICS Problem
follows: Determination Guide for guidance on how to proceed.
1. Determine if the problem can be explained by any Module: DFHLDDMI
previous messages output from some other part of CICS.
2. Examine the symptom string. XMEOUT Parameters: applid, ff,modname
3. Examine the dump. Destination: Console
Module: DFHLDDM, DFHLDDMI, DFHLDLD, DFHLDLD1,
DFHLDLD2, DFHLDLD3, DFHLDNT, DFHLDST
DFHLD0103I applid Module Storage Compression OFF. All
XMEOUT Parameters: applid, X'code',modname modules are USAGE=TRANSIENT.
Destination: Console Explanation: This message is normally preceded by either
message DFHLD0101 or DFHLD0102 and indicates that the
loader (LD) domain was unable to initialize its dynamic
DFHLD0004 applid A possible loop has been detected at program storage compression facility.
offset X'offset' in module modname. System action: CICS execution continues but all nonresident
Explanation: CICS has detected what it believes to be a code application programs are treated as if they had been defined
execution loop. At the time execution was interrupted, the with the USAGE=TRANSIENT option. Therefore they are
program status word (PSW) indicated the next instruction removed from storage the moment their use count reaches
address would have been at offset X'offset' in module modname. zero.
System action: CICS is terminated with a system dump For some functions, this can lead to a performance
unless dump table options specifically prevent this. degradation as programs may be loaded many times during
Message DFHME0116 is normally produced containing the the life of a transaction instead of only once.
symptom string for this problem. User response: Investigate the reasons for the previous
problem concerning module DFHLDNT as diagnosed by
User response: Investigate the existence of a previous error
either message DFHLD0101 or DFHLD0102.
situation which may have led to corruption of CICS control
Module: DFHLDDMI
blocks or to the non-completion of an expected event. If there
is no evidence of a previous error, you will need further XMEOUT Parameter: applid
assistance from IBM to resolve the problem. See Part 4 of the Destination: Console
proceed.
Module: DFHLDDM, DFHLDDMI, DFHLDLD, DFHLDLD1, DFHLD0104I applid Module Statistics are not being
DFHLDLD2, DFHLDLD3, DFHLDNT, DFHLDST collected.
Explanation: This message is normally preceded by either
XMEOUT Parameters: applid, X'offset', modname message DFHLD0101 or DFHLD0102 and indicates that the
Destination: Console loader (LD) domain was unable to initialize it's statistics
collection module.
System action: CICS execution continues but no module
DFHLD0101I applid CICS nucleus module modname not statistics are collected.
found. User response: Investigate the reasons for the previous
Explanation: The CICS loader (LD) was unable to locate a problem concerning module DFHLDST as diagnosed by either
copy of module modname in either the SVA or the LIBDEF message DFHLD0101 or DFHLD0102.
search chain specified in the CICS startup job stream. Module: DFHLDDMI
System action: A system dump is taken and CICS execution
continues unless specifically inhibited by a dump table entry. XMEOUT Parameter: applid
User response: This message is followed by one or more Destination: Console
messages informing the user of reduced function availability
due to the missing module modname.
DFHLD0105 applid Restart of Loader Option Block (LOB)
Ensure that there is a copy of module modname in the SVA failed. System defaults in use.
and/or in a sublibrary within the LIBDEF search chain for the Explanation: The initialization of the CICS loader has
CICS job. detected one or more invalid parameters in the loader option
Module: DFHLDDMI block (LOB) recovered from the local catalog.
XMEOUT Parameters: applid, modname This may indicate that corruption of the CICS local catalog
Destination: Console (DFHLCD) has occurred.
System action: A system dump is taken and CICS execution
continues unless specifically inhibited by a dump table option.
DFHLD0102 applid Unable to declare gate ff for module
modname. Message DFHME0116 is normally produced containing the
Explanation: As part of its initialization, the CICS loader has symptom string for this problem.
attempted to define domain gate ff for module modname, but User response: Investigate the possibility of corruption of the
has received a bad response. DFHLCD. If you suspect that the local catalog is corrupt,
System action: A system dump is taken and CICS execution reinitialize it and resubmit the CICS job.
continues unless specifically inhibited by a dump table entry. Module: DFHLDDM
Message DFHME0116 is normally produced containing the XMEOUT Parameter: applid

DFHLD0107I • DFHLD0204
DFHLD0201 applid Corrupt Loader load structure detected
at X'address'. Module marked as unavailable.
DFHLD0107I applid modname1 is unable to locate module Explanation: During the execution of a CICS loader request,
modname2 in the SVA. LIBDEF search chain the loader detected an invalid field in the control block type
version of module will be used. tttt at storage address address.
Explanation: The user has specified the system initialization System action: A system dump is taken and execution
parameter SVA=YES. Module modname2 is either defined as continues unless specifically inhibited by a dump table option.
USESVACOPY(YES) via RDO, or is a CICS PCLASS=SYSTEM Message DFHME0116 is normally produced containing the
module. CICS has been unable to find module2 in the SVA. symptom string for this problem.
System action: CICS execution continues with an attempt to User response: Investigate the possibility of corruption of
locate module modname2 in the LIBDEF search chain for the CICS modules or control blocks or the local or global catalogs.
CICS job. Module: DFHLDLD1
User response: carry out one of the following:
v Load module modname2 into the SVA, if this is required and XMEOUT Parameters: applid, load,X'address'
the module is SVA eligible (refer to the CICS System Destination: Console
Definition Guide for SVA eligibility of CICS modules).
v Code PRVMOD=modname2 as a system initialization
DFHLD0202 applid Loader SVC svc request failed due to
parameter which ensures that CICS does not search the SVA
shortage of free storage in the region.
for that module.
Explanation: The loader domain has issued a request to its
v Code SVA=NO as a system initialization parameter. This
CICS SVC service routine, DFHLDSVC, but the execution of
ensures that CICS does not search the SVA for any module.
this request failed due to a lack of free storage. The type of
Module: DFHLDDMI, DFHLDLD1 request is indicated by svc.
XMEOUT Parameters: applid, modname1, modname2 System action: A system dump will be taken unless
Destination: Console Routecode 11 specifically suppressed through a dump table entry and the
system continues execution. The task requesting loader
services is abnormally terminated with abend code APCT, or a
DFHLD0108I applid The maximum of 32767 entries that PGMIDERR condition is raised.
CICS allows on a BLDL has been exceeded. User response: Ensure there is adequate free storage by
Explanation: During a warm or emergency restart, the loader balancing the overall size limits of the DSAs or EDSAs with
domain has detected more than 32767 modules eligible for the size of the CICS partition.
OS/390 BLDL. Module: DFHLDLD1
System action: A BLDL macro call is issued to locate the first
XMEOUT Parameters: applid, svc
32767 modules and the rest are ignored. CICS initialization
continues normally.
This is not a problem because CICS attempts to locate those
modules not located during initialization when the module is DFHLD0203 applid Loader SVC svc request failed due to
first used. I/O errors processing the LIBDEF search
User response: None. chain.
Module: DFHLDDMI Explanation: The loader domain has issued a request to its
CICS SVC service routine, DFHLDSVC, but the execution of
XMEOUT Parameter: applid this request failed due to I/O errors processing the LIBDEF
Destination: Console search chain. The type of request is indicated by svc.
System action: A system dump is taken unless specifically
suppressed through a dump table entry and the system
DFHLD0109 applid Insufficient storage to satisfy continues execution. The task requesting loader services is
GETMAIN request by DFHLDSVC. abnormally terminated with abend code APCT, or a
Explanation: The CICS loader has issued a OS/390 PGMIDERR condition is raised.
GETMAIN request during CICS initialization in order to User response: Investigate the possible causes of the I/O
acquire VSE partition storage below the 16MB line for the errors encountered. The VSE system console log may contain
loader supervisor services control block. However insufficient more information about the problem in the form of access
storage was available to satisfy the request. method or I/O subsystem messages. The loader domain
System action: CICS execution continues although only SVA exception trace entries, from the full trace, in the system dump
resident modules are accessible. normally identify the module or modules for which the I/O
User response: Ensure sufficient partition storage is available error occurred.
below the 16MB line to satisfy OS/390 GETMAIN requests. Module: DFHLDLD1
This may mean reducing the size of the system initialization
parameter DSALIM to free more storage below the 16MB line XMEOUT Parameters: applid, svc
to satisfy these requests. Destination: Console
Module: DFHLDDM
XMEOUT Parameter: applid DFHLD0204 applid Bad Loader PDB for module modname
Destination: Console recovered from the {Local | Global} catalog.
Corruption suspected.
Explanation: The loader definition record, PDB, for module
modname has been read from either the local (DFHLCD) or the
global (DFHGCD) catalog during startup and has been found
to contain invalid data.
System action: System initialization terminates with a system
dump, unless the dump is specifically suppressed. If the

DFHLM0001 • DFHLM0004
system dump is suppressed, the module definition is ignored. been corrupted and is available to the CICS job.
Module: DFHLDDMI, DFHLDLD
symptom string for this problem. XMEOUT Parameters: applid, modname,{1=Local, 2=Global}
User response: Ensure the specified catalog data set has not Destination: Console
DFHLMxxxx messages
If appropriate, an error return code is sent to the caller of this
DFHLM0001 applid An abend (code abcode) has occurred at
domain. In this case, CICS could be terminated by the caller
(for example, the domain manager, DFHDMDM). A message is
issued to this effect.
an error in CICS code. Alternatively, unexpected data has been Message DFHME0116 is normally produced containing the
input, or storage has been overwritten. symptom string for this problem.
User response: Inform the system programmer. This indicates
The code abcode is a 3-digit hexadecimal VSE code (if
a possible error in CICS code. The severity of its impact
applicable), followed by a 4-digit alphanumeric CICS code.
hyphens. The CICS code is an abend code or a number CICS may not have been terminated.
abend code; 1310 refers to message DFHTS1310). If the message occurs once and module modname is not crucial
System action: An exception entry is made in the trace table. to the running of your CICS system, you may decide to
A system dump is taken, unless you have specifically continue to run and bring CICS down at a convenient time to
suppressed dumps in the dump table. resolve the problem.
CICS continues unless you have specified in the dump table If the message recurs or if you cannot run without the full use
that CICS should terminate. of module modname, you should bring CICS down in a
symptom string for this problem. You need further assistance from IBM to resolve this problem.
User response: Notify the system programmer. If CICS is still See Part 4 of the CICS Problem Determination Guide for
running, it is necessary to decide whether to terminate CICS. guidance on how to proceed.
Module: DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM
If there is a VSE code, look it up in "OS/390 API Abend
Codes" in section "VSE/Advanced Functions Codes & SVC XMEOUT Parameters: applid, X'code',modname
Errors" of z/VSE Messages and Codes - Volume 1. Destination: Console
Next, look up the CICS alphanumeric code in “Transaction

Abend Codes (CICS Transaction Server for VSE/ESA)” on DFHLM0004 applid A possible loop has been detected at
page 453. This tells you, for example, whether the error was a offset X'offset' in module modname.
program check, an abend, or a runaway, and may give you Explanation: A CICS function is taking more time to process
some guidance concerning user response. than CICS expects. A possible loop has been detected in
If module modname is not crucial to the running of your CICS instruction which was executing at the time the error was
system, you may decide to continue to run and bring CICS detected.
down at a convenient time to resolve the problem. System action: An exception entry is made in the trace table.
If you cannot run without the full use of module modname, A system dump is taken, unless you have specifically
you should bring CICS down in a controlled shutdown. suppressed dumps in the dump table.
You need further assistance from IBM to resolve this problem. CICS continues unless you have specified in the dump table
See Part 4 of the CICS Problem Determination Guide for that CICS should terminate.
guidance on how to proceed. Message DFHME0116 is normally produced containing the
Module: DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM symptom string for this problem.
XMEOUT Parameters: applid, abcode,X'offset', modname User response: Notify the system programmer. If CICS has
Destination: Console not been terminated, it will be necessary to decide whether the
DFHLM0002 applid A severe error (code X'code') has
uniquely identifies what the error is and where the error was
detected. For further information about CICS exception trace
that module modname in the message will be terminated and
entries, refer to the CICS Problem Determination Guide.
CICS will continue.
is made in the trace table. A system dump is taken, unless you But if you have declared ICVR=0 and you consider that
have specifically suppressed dumps in the dump table. module modname has gone into a loop, you will have to
terminate CICS in order to terminate the runaway function.
that CICS should terminate. If CICS has terminated module modname and you consider

DFHLM0006 • DFHME0001
that it was not a runaway, you should increase the ICVR time domain. In this case, CICS could be terminated by the caller
interval. You will have to bring CICS down at a suitable time (for example, the domain manager, DFHDMDM). A message is
to do this permanently. But you can change the ICVR time issued to this effect.
interval temporarily online, using the CEMT transaction.
If raising the ICVR time does not solve the problem, you will symptom string for this problem.
need further assistance from IBM. See Part 4 of the CICS User response: Inform the system programmer.
Module: DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM See "OS/390 API Return Codes" in section "VSE/Advanced
XMEOUT Parameters: applid, X'offset', modname Volume 1 for diagnostic information about the VSE return
Destination: Console code. If CICS has been terminated by another module, look
out for the relevant termination messages (from, for example,
the domain manager), and look up the user response
DFHLM0006 applid Insufficient storage to satisfy Getmain suggested for these messages.
(code X'code') in module modname. VSE code
vsecode. If CICS is still running, the problem may be a temporary one
Explanation: A OS/390 GETMAIN was issued by module which will right itself if more storage becomes available. If
modname, but there was insufficient storage available to satisfy you can manage without module modname, you may decide to
the request. continue and bring CICS down at a convenient time to resolve
The code X'code' is the exception trace point id which uniquely without the full use of all CICS modules, you should bring
identifies the place where the error was detected. CICS down in a controlled shutdown.
This error has occurred above the 16MB line. Try decreasing the overall size limits of the DSAs or EDSAs.
The code vsecode is the OS/390 GETMAIN return code. Or, try increasing the size of the CICS partition, if it is not
System action: An exception entry is made in the trace table already at maximum size. If CICS is not already terminated,
(code code in the message). A system dump is taken, unless you will need to bring CICS down to do this. See the CICS
you have specifically suppressed dumps in the dump table. System Definition Guide or the CICS Performance Guide for
further information on CICS storage.
CICS will continue unless you have specified in the dump Module: DFHLMDM, DFHLMDS, DFHLMIQ, DFHLMLM
table that CICS should terminate.
If appropriate, an error return code is sent to the caller of this Destination: Console
DFHMCxxxx messages
v A TRANSID error
DFHMC4000 CICS SYNAD EXIT TAKEN FOR dscname,
v An INVALD REQ error
INPUT MSG TRUNCATED.
Explanation: This message is issued when the SYNAD exit is v An UNEXPECTED error.
taken for an input queue. dscname represents the DSCNAME. System action: Purge delay does not operate for this
System action: The data control block (DCB) is closed and execution of CICS. A dump is taken.
then opened again. The data is truncated to the specified block User response:
size and passed to the user. v For a TRANSID error, define transaction CSPQ.
User response: Increase the block size or reduce the length of v For an INVALD REQ, the ICP returned an INVALID
input. REQUEST return code in response to the INITIATE request.
Module: VSE data management determines the problem. This Determine why this has occurred and correct the problem.
message is issued from the CICS-provided SYNAD routine v For an UNEXPECTED error, the ICP returned an
generated in the terminal control table (TCT). unrecognized error code in response to the INITIATE
Destination: Console request. The error code can be found in the dump at label
MCPINERR in program DFHMCP. Determine why this has
occurred and correct the problem.
DFHMC4001I date time applid Error purge delay inoperative,
Module: DFHMCP
{transid | invalid req | unexpected} error
Explanation: An error return code has been received from the XMEOUT Parameters: date, time,applid, {1=transid, 2=invalid
interval control program (ICP) during initiation of the purge req, 3=unexpected}
delay transaction, CSPQ. Destination: CSMT
The return code is caused by one of the following.
DFHMExxxx messages
hyphens. The CICS code is an abend code (for example
DFHME0001 applid An abend (code xxx/yyyy) has occurred
AKEA) or a number referring to a CICS message (for example
1310 refers to CICS message DFHTS1310).
Explanation: An abnormal end or program check has
A dump is taken, unless you have specifically suppressed
The code xxx/yyyy is a 3-digit hexadecimal VSE code (if dumps in the dump table. Since this error may not be critical,
applicable), followed by a 4-digit alphanumeric CICS code. CICS is not terminated, even if you have specified terminate
The VSE code is a system completion code, for example 0C1. in the dump table.

DFHME0002 • DFHME0006
symptom string for this problem. dumps in the dump table. This situation may not be an error,
User response: Since the abend affects the national language or if it is an error it may not be critical, so CICS is not
modules in the message (ME) domain, CICS is not terminated immediately, even if you have specified terminate
automatically terminated. However, you may decide that your in the dump table. CICS will purge the runaway task if you
system should not be allowed to run without these modules, have specified a non-zero value for the ICVR system
in which case you need to bring CICS down. initialization parameter.
Look up the VSE code, if there is one, in "OS/390 API Abend Message DFHME0116 is normally produced containing the
Codes" in section "VSE/Advanced Functions Codes & SVC symptom string for this problem.
Errors" of z/VSE Messages and Codes - Volume 1. User response: This error affects message generation, and the
message (ME) domain does not automatically terminate CICS.
Next, look up the CICS alphanumeric code in “Transaction You should decide whether the problem is serious enough to
Abend Codes (CICS Transaction Server for VSE/ESA)” on bring CICS down.
page 453. This code tells you, for example, whether the error
was a program check, an abend, a runaway, or a recovery Since some transactions can use a lot of CPU time, this
percolation. message may have been caused by a long-running transaction.
Usually, CICS terminates a task which it considers to be a
You need further assistance from IBM to resolve this problem. runaway task. It does this termination when the task exceeds
See Part 4 of the CICS Problem Determination Guide for the runaway task time interval which you have specified on
guidance on how to proceed. the ICVR system initialization parameter (ICVR is measured in
Module: DFHMEDM, DFHMEME, DFHMESR milliseconds).
If you have declared ICVR=0, you have to terminate the task
yourself if you consider that it has gone into a loop. Purge the
DFHME0002 applid An error (code X'code') has occurred in task using the CEMT transaction.
module modname.
Explanation: An error has been detected in module modname. If CICS has purged the task and you consider that it was not a
The code X'code' is the exception trace point id which uniquely runaway, you should increase the ICVR time interval. You will
identifies the place where the error was detected. have to bring CICS down at a suitable time in order to do
System action: A bad return code is sent to the caller of the this.
message (ME) domain. If the call is made by the domain
manager, DFHDMDM, CICS is terminated by the domain
manager, and a message is issued to this effect. However, if
the message is issued by a message domain module, CICS is
Module: DFHMEDM, DFHMESR, DFHMEME
allowed to continue.
An exception entry is made in the trace table. For further
information about CICS exception trace entries, refer to the
CICS Problem Determination Guide. DFHME0006 applid Insufficient storage to satisfy
A dump is taken, unless you have specifically suppressed VSE code vsecode.
dumps in the dump table. Since this error may not be critical, Explanation: A OS/390 GETMAIN was issued by module
CICS is not terminated immediately, even if you have modname, but there was insufficient storage available to satisfy
specified terminate in the dump table. the request. The code X'code' is the exception trace point ID
which uniquely identifies the place in the code where the error
Message DFHME0116 is normally produced containing the occurred. The code vsecode is the OS/390 GETMAIN return
symptom string for this problem. code.
User response: Inform the system programmer as this System action: An exception entry is made in the trace table
message indicates a severe error in CICS code. Its impact may with code X'code'. A dump is taken, unless you have
or may not be severe, depending on the circumstances. For specifically suppressed dumps in the dump table. Since this
example, if it only occurs once and CICS has not been may not be a critical error, CICS is not terminated
terminated by the domain manager, you may decide to immediately, even if you have specified terminate in the
continue to run and bring CICS down at a convenient time. dump table. However, if this error indicates a general problem
But if the message recurs or if you cannot run without the full with storage, CICS could be abnormally terminated by the
use of all CICS messages, you should bring CICS down in a CICS storage manager. A message will be issued to this effect.
If the GETMAIN fails for DFHMEDM, a return code is sent to
You need further assistance from IBM to resolve this problem. the domain manager, DFHDMDM, and CICS is terminated by
See Part 4 of the CICS Problem Determination Guide for the domain manager. A message is issued to this effect.
Module: DFHMEDM, DFHMEME, DFHMESR, DFHMEWT If the GETMAIN fails for the message domain DFHMEME, it
Destination: Console could occur in one of four places. The code X'code' indicates
which GETMAIN has failed as follows:
DFHME0004 applid A possible loop has been detected at Code Meaning

offset X'offset' in module modname. X'0340' - During formatting of TD message
than CICS expects. A possible loop has been detected in The message is not issued.
module modname at offset X'offset'. This is the offset of the X'0341' - During build of message
instruction which was executing at the time the error was The message is not issued.
detected. X'0342' - While building user exit parameters
A dump is taken, unless you have specifically suppressed The message is issued to original destination.

X'0343' - During rebuild of message in English

DFHME0105 applid Insufficient storage to load module
The rebuilt English message is not issued. modname.
Explanation: A OS/390 LOAD has failed. The message
language module modname could not be loaded as there was
insufficient storage available. The language module is defined
by the NATLANG system initialization parameter for
User response: If CICS is terminated, look out for the
messages in a particular language, or is the default language
relevant termination messages from the storage manager or module.
the domain manager and the user response suggested.
The default language is always used for messages sent to
Try decreasing the size limits of the DSAs or EDSAs. Or, try transient data queues and to consoles (providing that it is not
increasing the size of the CICS partition, if it is not already at a double-byte language in which case the message is sent to
maximum size. You will need to bring CICS down to do this, the console in English). If the default language module cannot
if it has not already been terminated. be loaded, no messages can be delivered. Terminals can have
messages in the default language or in another chosen
The problem may be a temporary one which rights itself if
language. If the chosen language module cannot be loaded,
more storage becomes available. If CICS is still running, and
terminal messages use the default language instead.
you can manage without the full set of CICS messages, you
may decide to continue and bring CICS down at a convenient and a dump is taken, unless you have specifically suppressed
time. dumps in the dump table. As this may not be a critical
You can get diagnostic information about the VSE return code problem, CICS is not terminated unless the default language
vsecode in "OS/390 API Return Codes" in section module cannot be loaded, (even if you have specified
"VSE/Advanced Functions Codes & SVC Errors" of z/VSE terminate in the dump table).
Messages and Codes - Volume 1. If the missing module is not the default language module,
Module: DFHMEDM, DFHMEME CICS uses the default language for messages to terminals. If
Destination: Console the default language module cannot be loaded, a return code
is sent to the domain manager and CICS is terminated by the
domain manager.
DFHME0102 applid An error (code X'code') has occurred in User response: If the default language is in operation and
module modname while producing message this is acceptable, you need not bring CICS down. (Or you
msgno. may bring CICS down at a more convenient time.)
Explanation: A severe error has been detected and the
message (ME) domain has been unable to produce message If the default language is in operation and this is not
msgno. The code X'code' is the exception trace point ID which acceptable, or if the default language module itself is missing,
uniquely identifies the place where the error was detected. try decreasing the size limits of the DSAs or EDSAs. Or you
System action: A return code is sent to the caller of the could try increasing the size of the CICS partition, if it is not
already at maximum size.
message (ME) domain, but since the call was made by a
message domain module, CICS is allowed to continue. Alternatively, you may be able to get more storage space by
removing unwanted language modules from storage. To do
An exception entry is made in the trace table. A dump is
this, bring CICS down, remove the language codes you do not
taken, unless you have specifically suppressed dumps in the
need from the NATLANG system initialization parameter, and
dump table. Since this may not be a critical error, CICS is not restart CICS.
terminated immediately, even if you have specified terminate
in the dump table.
Note: You should not remove the default language module
Message DFHME0116 is normally produced containing the from the SIT.
symptom string for this problem. Module: DFHMEDM
User response: Inform the system programmer as this Destination: Console
indicates a severe error in CICS code. However, its impact
may not be serious. For example, if the error only occurs once
and you can run without message msgno, you may continue to DFHME0106 applid Module modname could not be loaded.
run and bring CICS down at a convenient time. REGISTER 1 = X'nnnnnnnn' and REGISTER
15 = X'nnnnnnnn'.
However, if the message recurs (and on each recurrence there Explanation: The message language module modname could
is a different message number msgno), or if you cannot run not be loaded. The reason that it could not be loaded is given
without the full use of all CICS messages, you should bring by the contents of registers 1 and 15, which are returned by
CICS down in a controlled shutdown. VSE. Registers 1 and 15 contain the OS/390 LOAD abend and
reason codes respectively.
System action: If the missing module is not the default
language module, CICS uses the default language for
messages.
Module: DFHMEBU, DFHMEIN, DFHMEWT, DFHMEME
Destination: Console If the default language module is missing, a return code is
sent to the domain manager and CICS is terminated.
An exception entry is made in the trace table and a dump is
dump table. As this may not be a critical problem, CICS is not
terminated unless the default language module cannot be

loaded (even if you have specified terminate in the dump remove it from NATLANG system initialization parameter at
table). the next convenient opportunity.
Message DFHME0116 is normally produced containing the If the default language module is missing, CICS is terminated
symptom string for this problem. by the domain manager. You need to discover whether the
User response: If the default language is in operation and fault is in the library or the SIT and follow the appropriate
this is acceptable, you need not bring CICS down, or you may procedure.
do so at some convenient time. Module: DFHMEDM
If the default language is in operation and this is not
acceptable, or if the default language module itself is missing,
consult "OS/390 API Abend Codes" in section "VSE/Advanced DFHME0108 applid Message msgno cannot be found in
Functions Codes & SVC Errors" of z/VSE Messages and Codes - module modname.
Volume 1 to interpret the OS/390 abend and reason codes Explanation: Message msgno should have been delivered, but
displayed in the message. The return codes indicate why the was not found in message language module modname.
module could not be loaded.
Module: DFHMEDM This module is the national language module specified in the
Destination: Console SIT by the user which gives messages in a chosen language.
DFHME0107 applid Module modname cannot be found in dumps in the dump table. Since this may not be a critical
the library. error, CICS is not terminated, even if you have specified
Explanation: The message load module modname was not terminate in the dump table.
found in a sublibrary of the LIBDEF search chain for the CICS
startup job stream. This load module is a language module for Message DFHME0116 is normally produced containing the
messages. It is either a module which has been defined by the symptom string for this problem.
NATLANG system initialization parameter for messages in a User response: This indicates an error in CICS code.
particular language, or it is the default language module. However, its impact may not be severe. For example, the error
may only occur once, or you may decide to continue to run
The default language is always used for messages sent to without message number msgno. Note that this message will
transient data queues and to consoles (providing that it is not appear after maintenance has been applied to the CICS
a double-byte language, in which case the message is sent to message domain if there are older, pre-maintenance, versions
the console in English). If the default language module is of the DFHMET1x message modules elsewhere in the LIBDEF
missing no messages can be delivered. search chain for the CICS job.
Terminals can have messages in the default language or in If you have just applied maintenance and are encountering
another chosen language. If the chosen language module is this message, check for, and remove, older versions of the
missing, terminal messages use the default language instead. message modules from other sublibraries in the LIBDEF search
System action: An exception entry is made in the trace table. chain for the CICS job.
dumps in the dump table. But since this may not be a critical If the problem persists, you will need further assistance from
error, CICS is not terminated immediately, even if you have IBM. See Part 4 of the CICS Problem Determination Guide for
specified this in the dump table, unless the default language guidance on how to proceed.
module is missing, (even if you have specified terminate in Module: DFHMEIN
the dump table). Destination: Console
If the missing module is not the default language module,

CICS uses the default language for messages. If the default DFHME0109 applid Message set setname could not be found
language module is missing, a return code is sent to the in module modname while producing message
domain manager and CICS is terminated. msgno.
User response: This error could have occurred because of a Explanation: Message set setname was not found in the
problem in a library or in the SIT. If the default language is in message language module modname.
operation and this is acceptable, you need not bring CICS The setname is the first two characters after the DFH in CICS
down, or you may do so at some convenient time. messages (for example, LD or 21), which is followed by the
The missing module may have been placed in the wrong message number.
library, or the wrong or misspelled module name may have System action: An exception entry is made in the trace table.
been used in the right library. A dump is taken, unless you have specifically suppressed
dumps in the dump table. Since this may not be a critical
If the default language is in operation and this is NOT error, CICS is not terminated, even if you have specified
acceptable, link the missing module into a sublibrary of the terminate in the dump table.
LIBDEF search chain for the CICS job. You have to bring CICS
down to do this. Message DFHME0116 is normally produced containing the
It is also possible that an incorrect or misspelled language User response: This indicates an error in CICS code.
code has been used on the NATLANG system initialization However, its impact may not be severe. For example, the error
parameter. In this case, you have to bring CICS down, reinstall may only occur once, or you may decide to continue without
your chosen language code as a system initialization message number msgno.
parameter, and restart CICS.
If the problem persists, you will need further assistance from
If you no longer need this language module, you should

IBM. See Part 4 of the CICS Problem Determination Guide for

DFHME0112 applid Insert number ii is invalid for message
msgno (code X'code').
Module: DFHMEIN
Explanation: Insert ii, supplied on the call to the message
(ME) domain, was invalid. For example, it may have been a
decimal insert with a length greater than 4 bytes.
DFHME0110 applid Optional insert ii is missing for
The code X'code' uniquely identifies the occurrence of the
message msgno.
invalid insert.
Explanation: Optional insert ii was requested on a call to the
System action: CICS delivers the message with ??? in place
message domain but could not be found in the message
of the invalid insert ii.
definition template.
System action: CICS delivers the message with ??? in place An exception entry with code X'code' is made in the trace
of the missing insert ii. table. A dump is taken, unless you have specifically
suppressed dumps in the dump table. Since this may not be a
An exception entry is made in the trace table. A dump is
critical error, CICS is not terminated, even if you have
specified terminate in the dump table.
dump table. Since this may not be a critical error, CICS is not
terminated, even if you have specified terminate in the dump Message DFHME0116 is normally produced containing the
table. symptom string for this problem.
User response: Ensure that you have loaded the correct
message language module. That is, ensure that you have the
correct language specified in the NATLANG system
User response: This message indicates an error in CICS code.
initialization parameter and that a sublibrary of the LIBDEF
However, its impact may not be severe. For example, the error
search chain for the CICS job contains the correct message
may only occur once, or you may decide to continue without
language module.
message msgno.
This message indicates an error in CICS code. However, its
impact may not be serious. For example, the error may only
occur once, or you may decide to continue without message
msgno being produced.
Module: DFHMEBU
Destination: Console If the problem persists, you will need further assistance from
DFHME0111 applid Insert ii is missing for message msgno. Module: DFHMEBU
Explanation: Insert ii is required for message msgno. The Destination: Console
insert was not found.
System action: CICS delivers the message with ??? in place
of the missing insert ii. DFHME0113 applid Incorrect parameters used in call to
DFHMEME for message msgno.
An exception entry is made in the trace table. A dump is Explanation: A call to the message (ME) domain for message
taken, unless you have specifically suppressed dumps in the msgno was made with an invalid combination of parameters.
dump table. But since this may not be a critical error, CICS is System action: An exception entry is made in the trace table.
not terminated, even if you have specified terminate in the A dump is taken, unless you have specifically suppressed
dump table. dumps in the dump table.
Message DFHME0116 is normally produced containing the CICS is not terminated, even if you have specified terminate
symptom string for this problem. in the dump table.
message language module. That is, ensure that you have the Message DFHME0116 is normally produced containing the
correct language specified in the NATLANG system symptom string for this problem.
initialization parameter and that a sublibrary of the LIBDEF User response: Ensure that you have loaded the correct
search chain for the CICS job contains the correct message message language module. That is, ensure that you have the
language module. correct language specified in the NATLANG system
This message indicates a severe error in CICS code. However, search chain for the CICS job contains the correct message
its impact may not be serious. For example, the error may language module.
only occur once, or you may decide to continue without
message msgno. This message indicates a severe error in CICS code. However,
its impact may not be serious. For example, the error may
If the problem persists, you will need further assistance from only occur once, or you may decide to continue without
IBM. See Part 4 of the CICS Problem Determination Guide for message msgno.
Module: DFHMEBU If the problem persists, you will need further assistance from
Destination: Console IBM. See Part 4 of the CICS Problem Determination Guide for
Module: DFHMEME

module modname failed to load at initialization, take the action

DFHME0114 applid There are no destinations specified for
described for the appropriate message about a failed LOAD
message msgno.
issued during start-up.
Explanation: There was no destination destid specified in the
message language module for message msgno. This error could Otherwise, bring CICS down and specify language language on
occur if the message language module has been corrupted or the NATLANG system initialization parameter, and restart
is not at the correct release level. CICS.
System action: An exception entry is made in the trace table. Module: DFHMEIN
A dump is taken, unless you have specifically suppressed Destination: Console
dumps in the dump table. Since this error may not be critical,
CICS is not terminated even if you have specified terminate in
the dump table. DFHME0116 applid (Module:modname) CICS symptom
string for message msgno is symstring.
Message DFHME0116 is normally produced containing the Explanation: Message msgno has been issued as the result of
symptom string for this problem. a possible CICS error.
message language module. That is, ensure that you have the Symptom string symstring has been produced to provide
correct language specified in the NATLANG system additional diagnostic information for IBM support.
initialization parameter and that a sublibrary of the LIBDEF System action: This message accompanies message msgno
search chain for the CICS job contains the correct message and has no effect on the system action. The system action is
language module. that stated in message msgno.
User response: Refer to the user response of message msgno
This message indicates a severe error in CICS code. However, which provides the necessary information to determine if the
its impact may not be serious. For example, the error may error is serious enough to be reported to IBM Support.
only occur once, or you may decide to continue without Module: DFHMEME
message msgno being produced. If you feel it is not critical,
you can continue to run your system without message msgno XMEOUT Parameters: applid, modname,msgno, symstring
until a convenient time comes to resolve the problem. Destination: Console

IBM. See Part 4 of the CICS Problem Determination Guide for DFHME0117 applid The Message User Exit point XMEOUT
guidance on how to proceed. is unavailable for message msgno.
Module: DFHMEIN Explanation: The message (ME) domain was unable to use
Destination: Console the message user exit point 'XMEOUT' when it was processing
message msgno. This is probably because it was invoked too
early in CICS initialization. A response of KERNERROR has
DFHME0115 applid modname Message module for language been returned to the message (ME) domain from the program
language not found. The default module which invokes the user exit, DFHAPEX.
modnameb is used. System action: The message (ME) domain continues
Explanation: The message language module modname for the processing as this error is not severe. The message msgno
national language language could not be found in the list of which the message (ME) domain was trying to produce is not
available modules. It is not found if a CICS program calls for suppressed or rerouted by the message user exit. Instead, it is
a message in a particular language from the message domain, issued to the original destination defined for message msgno.
but the message domain cannot locate the message in that User response: None. You cannot suppress message msgno
language. because the error has occurred too early in initialization.
The message language module may be unavailable because Module: DFHMEME
the LOAD for the appropriate message language module Destination: Console
failed at initialization. In this case, there will have been an
earlier message about the failed LOAD. Alternatively, the DFHME0118 applid An error has occurred when calling the
module may not be available because the language specified Message User Exit for message msgno.
on the terminal definition, or userid definition, was not Explanation: The message (ME) domain has received an
specified on the NATLANG system initialization parameter or incorrect response from DFHAPEX, the program which
was specified incorrectly. invoked the message user exit.
System action: An exception entry is made in the trace table. System action: The message (ME) domain continues
A dump is taken, unless you have specifically suppressed processing as this error is not severe. The message msgno
dumps in the dump table. Since this may not be a critical which the message domain was trying to produce is not
error, CICS is not terminated, even if you have specified suppressed or rerouted but is issued to its original destination.
terminate in the dump table. User response: This message indicates a probable error in the
All messages which should appear in language language in message user exit. Ensure that your message user exit
module modname appear in the system default language program is working properly.
modnameb instead. However, it is possible that the user exit invoking program
User response: Your action depends on whether the use of DFHAPEX interface has been corrupted. DFHAPEX issues an
the default language for messages is acceptable or not. If it is exception trace entry to indicate that there is an error, but is
acceptable, you can delay taking any action until a convenient not able to issue its own error message via the message
time. This may entail changing a terminal or userid definition domain as doing so would cause CICS to loop. In this case,
if that is the cause of the problem. you will need further assistance from IBM to resolve the
If the use of the default language is not acceptable, and if problem. See Part 4 of the CICS Problem Determination Guide

Module: DFHMEME the reason for first or second attempts at formatting the
Destination: Console message.)
System action: A dump is taken. The message domain does
not issue the message being formatted. An exception trace
DFHME0119 applid Message msgno has an invalid entry is made by the formatting routine DFHMEFO.
{Destination | User Exit | Message Identification} User response: This message indicates an error in CICS code.
component. However, its impact may not be severe. For example, the error
Explanation: The message (ME) domain has encountered an may only occur once, or you may decide to continue without
invalid component in the definition of message msgno in the the message msgno. If you feel it is not critical, you can
message language module. The message language module continue to run your system without message msgno until a
may have been corrupted or be at the wrong release level. convenient time comes to resolve the problem. If the problem
System action: The ME domain produces an exception trace persists, you will need further assistance from IBM. See Part 4
entry and continues processing. No dump is taken. of the CICS Problem Determination Guide for guidance on how
User response: Ensure that you are using the correct level of to proceed.
the message language module. That is, ensure that you have Module: DFHMEME
the correct language specified in the NATLANG system Destination: Console
search chain for your CICS job contains the correct message
language module. DFHME0122 applid The Message User Exit has returned
invalid route code information for message
This message indicates a severe error in CICS code. However, number msgno.
its impact may not be severe. For example, the error may only Explanation: The message user exit program has set an
occur once, or you may decide to continue without message invalid route code as the destination of message msgno. Valid
number msgno. If you feel it is not critical, you can continue to route codes are numbers 1 to 28 inclusive.
run your system without this message until a convenient time System action: The message (ME) domain ignores the invalid
comes to resolve the problem. route code and defaults to the original destination defined for
If the problem persists, you will need further assistance from message msgno in the message language module.
IBM. See Part 4 of the CICS Problem Determination Guide for User response: Check that your message user exit program
guidance on how to proceed. sets valid route code information for message msgno.
Module: DFHMEIN Module: DFHMEME
DFHME0120I applid Message msgno has been rerouted to its DFHME0123 applid The Message User Exit has returned
original destination. invalid TD queue information for message
Explanation: The message domain user exit point XMEOUT number msgno.
has attempted to route message msgno to a transient data (TD) Explanation: The message user exit program has set an
queue while CICS is quiescing or terminating. After CICS invalid queue name as the destination of the message msgno.
shutdown has started, a message can only be rerouted to a TD Valid queue names consist of 4 alphanumeric characters.
queue if its original destination has a TD queue. System action: The message (ME) domain ignores the invalid
System action: The message is rerouted to its original queue name and defaults to the original destination defined
destination. for message msgno in the message language module.
User response: None. For programming information about User response: Check that your message user exit program
the XMEOUT user exit, see the CICS Customization Guide. sets valid queue name information for message msgno.
Module: DFHMEME Module: DFHMEME
XMEOUT Parameters: applid, msgno
DFHME0124 applid TD is unavailable for writing message
msgno to TD queue queuename.
DFHME0121 applid The {first | second} attempt at Explanation: The message (ME) domain has tried to output
formatting message msgno, TD queue message msgno to transient data queue queuename. However,
queuename has failed - {Invalid DBCS format transient data (TD) is not yet available. This situation may
|Unknown error}. occur early in CICS initialization.
Explanation: The message (ME) domain was trying to System action: The message is lost.
produce message msgno (destined for transient data queue User response: The impact of this error may not be severe.
queuename). However, an invalid response has been returned For example, the error may only occur once, or you may
from the message formatting routine, DFHMEFO. This error is decide to continue without message msgno. If you feel it is not
probably due to invalid DBCS characters being found in either critical, you can continue to run your system without message
the message inserts or the message text. The message text is msgno until a convenient time comes to resolve the problem.
checked at definition time for mismatched shift-out and
shift-in characters. However, adjacent shift-in and shift-out You need further assistance from IBM to resolve this problem.
characters could appear in a message, for instance, if a double See Part 4 of the CICS Problem Determination Guide for
byte message insert has not been supplied correctly. guidance on how to proceed.
Module: DFHMEME
The message (ME) domain first tries to format the message Destination: Console
into 120-byte segments. However, if the transient data queue
has been defined with a different queue length, formatting is
performed a second time using the new queue length. (Hence

System action: The message (ME) domain issues an

DFHME0125 applid The Message User Exit has returned an
exception trace entry. Message msgno is not issued.
invalid return code rc for message msgno.
Explanation: The message user exit has returned a return
code rc. which is neither 0 or 4 when it was processing
message msgno. (A return code of 4 indicates that the message
Module: DFHMEME
is to be suppressed.)
System action: The message (ME) domain continues
processing as normal and does not suppress or reroute the
message. Instead, it issues the message as it was originally DFHME0131 applid Unable to calculate length of message
defined in the message language module. msgno due to message table corruption,
User response: Check that your message user exit program is code(code).
working properly, and that it is passing the correct return code Explanation: The message (ME) domain could not calculate
back to the message (ME) domain. the length of the message msgno due to possible corruption of
Module: DFHMEME the message language module.
Destination: Console System action: A return code is sent to the caller of the
message (ME) domain. The message msgno is not issued.
User response: Ensure that you are using the correct level of
DFHME0128 applid Message msgno has an invalid route
the message data module. That is, ensure that you have the
code.
correct language specified in the NATLANG system
Explanation: The routine which issues the console message
was unable to do so as it encountered an invalid route code
search chain for your CICS job contains the correct message
associated with message msgno. Valid route codes are numbers
language module.
from 1 through 28.
This message indicates an error in CICS code. However, its
This error could only happen if the route codes have become
impact may not be severe. For example, the error may only
corrupted as they are being passed to the routine which issues
occur once, or you may decide to continue without message
the console message, DFHSUWT.
number msgno. If you feel it is not critical, you can continue to
System action: The message (ME) domain issues an
run your system without message msgno until a convenient
exception trace entry. Message msgno is not issued.
time comes to resolve the problem.
resolve this problem. See Part 4 of the CICS Problem You may need further assistance from IBM to resolve this
Determination Guide for guidance on how to proceed. problem. See Part 4 of the CICS Problem Determination Guide
Module: DFHMEME for guidance on how to proceed.
Destination: Console Module: DFHMEME
DFHME0129 applid Unable to format console message
msgno as it contains invalid DBCS characters. DFHME0132 applid The User's Message Exit program has
Explanation: The routine which attempted to format console failed while processing message msgno
message msgno was unable to do so as it was found to contain Explanation: The user's message exit program is either
invalid double byte (DBCS) characters. For example, adjacent looping or has failed with a program check.
or unmatched pairs of shift-in and shift-out characters are System action: The message (ME) domain continues
invalid in a string of DBCS text. processing and issues message msgno to its original
destination. The user exit invoking program DFHAPEX issues
This situation could occur if there are inserts in the message
an exception trace entry to indicate that the user's message
which contain, for example, a shift-out and a shift-in character
exit program has failed, but it cannot issue its own error
with no double byte characters entered in between.
message via the message (ME) domain as doing so would
System action: The message (ME) domain continues
cause CICS to loop.
processing but message msgno is not issued as it cannot be
User response: Disable your message exit program and
formatted. The message formatting routine, DFHMEFO, issues
ensure it is working properly.
an exception trace entry. The routine which issues console
Module: DFHMEME
messages, DFHSUWT, also issues an exception trace entry.
User response: Ensure that any double-byte information
entered from a terminal which may be used as a message
insert is entered correctly. DFHME0133 applid Message msgno could not be found in
Module: DFHMEME module DFHMEMGT.
Destination: Console Explanation: The message domain was trying to issue one of
its own error messages to indicate that an error had occurred
in the message domain. However, the message domain was
DFHME0130 applid Message msgno has an invalid
unable to find the message it was attempting to issue in its
descriptor code.
own internal message table DFHMEMGT.
Explanation: The routine which issues the console message
was unable to do so as it encountered an invalid descriptor
by the message domain. A dump is taken, unless you have
code associated with message msgno. Valid descriptor codes
specifically suppressed dumps in the dump table. Since this
are numbers 1 through 16.
may not be a critical error, CICS is not terminated, even if you
This error could only happen if the descriptor codes have have specified terminate in the dump table.
become corrupted as they are being passed to the routine User response: This message indicates an error in CICS code.
which issues the console message, DFHSUWT. However, its impact may not be severe.

DFHME0134 • DFHME9997I
If the problem persists, you will need further assistance from Determination Guide for guidance on how to proceed.
IBM. See Part 4 of the CICS Problem Determination Guide for Module: DFHMEIN
guidance on how to proceed. Destination: Console
Module: DFHSUME
DFHME0137 applid Message msgno cannot be rerouted to a
transient data destination by the message
DFHME0134 applid Message msgno has been truncated user exit XMEOUT.
because it was too long. Explanation: The message msgno cannot be rerouted to a
Explanation: The message (ME) domain was trying to output transient data destination via XMEOUT because by doing so,
message msgno, but truncated the message because it was too CICS could get into a loop.
long. Message msgno is a conversational message to an System action: An exception entry is made in the trace table.
operator which has exceeded the maximum size of 119 The message (ME) domain ignores the queue destination
characters. returned by the message exit and defaults to the original
System action: The ME domain truncates the message to 119 destination defined for message msgno in the message
bytes before issuing it. An exception trace entry is made and a language module.
dump taken, but processing continues. User response: Alter your message user exit program to
User response: This message indicates that msgno has been avoid rerouting the message msgno to a transient data
incorrectly defined in the message table, or that the inserts destination. The noreroute indicator is passed by the message
supplied to the message have caused it to exceed the size limit domain to the exit so that the exit program can check whether
imposed on conversational messages. If enough information or not it is valid to reroute a particular message.
can be obtained from the truncated message, the impact of this Module: DFHMEME
error may not be severe. If necessary, you can continue to run Destination: Console
your system without this message until a convenient time
comes to resolve the problem. See Part 4 of the CICS Problem
Determination Guide for guidance on how to proceed. DFHME9993I UNABLE TO DETERMINE LENGTH OF
Module: DFHMEME MESSAGE msgno - response reason
Destination: Console Explanation: The message DFHmsgno could not be found by
the message (ME) domain in the message tables.
DFHME0135 applid The default language language specified User response: If the problem persists, you will need further
in the SIT NATLANG parameter is invalid. It assistance from IBM. See Part 4 of the CICS Problem
has been defaulted to E. Determination Guide for guidance on how to proceed.
Explanation: The default language is the first character in the Module: DFHMGPME
NATLANG system initialization parameter. The default Destination: Terminal End User
language language is not in the list of valid CICS language
suffixes.
System action: CICS continues with a default language of E DFHME9994I UNABLE TO RETRIEVE MESSAGE msgno -
(US English). response reason
User response: If you do not want a default language of E, Explanation: The message DFHmsgno could not be retrieved
change the first character in the NATLANG system by the message (ME) domain from the message tables.
initialization parameter to another valid CICS language suffix. System action: CICS continues.
See the CICS System Definition Guide for a list of valid CICS User response: If the problem persists, you will need further
language suffixes. assistance from IBM. See Part 4 of the CICS Problem
Module: DFHMESR Determination Guide for guidance on how to proceed.
Destination: Console Module: DFHMGPME
DFHME0136 applid Message msgno is missing from

national language module modname. DFHME9996I MESSAGE PARAMETER LIST ERROR -
Searching the English message table for the CHECK PLIST
message text. Explanation: The parameter list for the message generation
Explanation: Message msgno cannot be issued in the specified process is not valid.
language because the message was not found in the national System action: CICS continues but the message in error
language module modname. cannot be issued.
User response: Ensure that the DFHMGT entry for the
This could be the result of a PTF containing message msgno message has been built correctly.
not being applied to the module modname. In this case, the text Module: DFHMGP00
of the missing message could be present in the English Destination: Terminal End User
language message table DFHMET1E.
The message domain tries to find the message in the English DFHME9997I MESSAGE FIND ERROR - CHECK THE
language message table. If the message is not found in the MESSAGE MODULE
English table either, message DFHME0108 is issued followed Explanation: The message being issued could not be found
by a system dump. by the message generation process in the DFHMGT table entry
User response: If message DFHME0108 follows this message, for this message set.
there is an error in CICS code and you will need further System action: CICS continues but the message in error
assistance from IBM. See Part 4 of the CICS Problem cannot be issued.
User response: Ensure that an entry exists for the message

DFHME9998I • DFHMN0003
number in the appropriate DFHMGT tables.

DFHME9999I THE MESSAGE INDEX MODULE
Module: DFHMGP00
'DFHMGT' IS MISSING
Explanation: The message generation process cannot find an
index module in the DFHMGT table for the message it is
DFHME9998I MESSAGE NUMBERS GREATER THAN trying to issue. This can occur where a message defined as
9999 ARE INVALID being destined for either a console or a transient data queue is
Explanation: The message being issued has a message being issued as a terminal end user message.
number greater than 9999. Message numbers should be in the System action: CICS continues but the message in error
range 1 through 9999. cannot be issued.
System action: CICS continues but the message in error User response: Ensure that the destination is correct for the
cannot be issued. message being issued.
User response: Redefine the message number. Module: DFHMGP00
Module: DFHMGP00 Destination: Terminal End User
DFHMNxxxx messages
DFHMN0001 applid An abend (code aaa/bbbb) has occurred
at offset X'offset' in module modname. The code X'code' is the exception trace point id which uniquely
Explanation: An abend or program check has occurred in identifies what the error is and where the error was detected.
module modname. This implies an error in CICS code. For further information about CICS exception trace entries,
Alternatively, it is possible that unexpected data has been refer to the CICS Problem Determination Guide.
input, or storage has been overwritten. System action: An exception entry (code code in the message)
The code aaa/bbbb is a 3-digit hexadecimal VSE code (if
have specifically suppressed dumps in the dump table. CICS
will continue unless you have specified in the dump table that
CICS should terminate.
hyphens. The CICS code is an abend code or a number If appropriate, an error return code is sent to the caller of this
referring to a CICS message (for example, AKEA is a CICS domain. In this case, CICS could be terminated by the caller
abend code; 1310 refers to message DFHTS1310). (for example, the domain manager, DFHDMDM). A message is
System action: An exception entry is made in the trace table. issued to this effect.
suppressed dumps in the dump table. CICS continues unless Message DFHME0116 is normally produced containing the
you have specified in the dump table that CICS should symptom string for this problem.
terminate. User response: Inform the system programmer. This indicates
a possible error in CICS code. The severity of its impact
Message DFHME0116 is normally produced containing the depends on the importance of the function being executed at
symptom string for this problem. the time of the error.
decide whether to terminate CICS. CICS may not have been terminated.
Look up the VSE code, if there is one, in "OS/390 API Abend If the message occurs once and module modname is not crucial
Codes" in section "VSE/Advanced Functions Codes & SVC to the running of your CICS system, you may decide to
Errors" of z/VSE Messages and Codes - Volume 1. continue to run and bring CICS down at a convenient time to
Abend Codes (CICS Transaction Server for VSE/ESA)” on If the message recurs or if you cannot run without the full use
page 453. This tells you, for example, whether the error was a of module module you should bring CICS down in a controlled
program check, an abend, or a runaway, and may give you shutdown.
some guidance concerning a user response. You need further assistance from IBM to resolve this problem.
If module modname is not crucial to the running of your CICS See Part 4 of the CICS Problem Determination Guide for
system, you have the option to continue to run and to bring guidance on how to proceed.
CICS down at a convenient time to resolve the problem. Module: DFHMNDM, DFHMNMN, DFHMNNT,
DFHMNSR, DFHMNST, DFHMNSU, DFHMNTI, DFHMNUE
If you cannot run without the full use of module modname you
should bring CICS down in a controlled shutdown. XMEOUT Parameters: applid, X'code',modname
guidance on how to proceed. DFHMN0003 applid Insufficient storage to satisfy Getmain
Module: DFHMNDM, DFHMNMN, DFHMNSR, DFHMNST, (code X'code') in module modname.
DFHMNSU, DFHMNTI, DFHMNUE Explanation: Insufficient storage is available to satisfy a
request by module modname.
Destination: Console The code X'code' is the exception trace point ID which
DFHMN0002 applid A severe error (code X'code') has (code code in the message). A system dump is taken, unless

DFHMN0004 • DFHMN0103I
you have specifically suppressed dumps in the dump table. need further assistance from IBM. See Part 4 of the CICS
This is a critical error. Problem Determination Guide for guidance on how to proceed.
Module: DFHMNDM, DFHMNMN, DFHMNSR, DFHMNST,
If DFHMNDM issues this message, CICS terminates, even if DFHMNSU, DFHMNTI, DFHMNUE
you have specified in the dump table that CICS should not
terminate. XMEOUT Parameters: applid, X'offset', modname
If either DFHMNMN or DFHMNST issues this message, an
exception trace and a system dump is taken and CICS
continues. DFHMN0005 applid A hardware error has occurred (module
is invalid.
User response: If CICS has been terminated by another
running of module modname. The store clock facility is the
module, look out for the relevant termination messages (from,
timing mechanism for the operating system.
for example, the domain manager), and look up the user
response for these messages. The code X'code' is the exception trace point ID which
you can manage without module modname, you may decide to
table. CICS will continue unless you have specified in the
dump table that CICS should terminate. If appropriate, an
without the full use of all CICS modules, you should bring
error return code is sent to the caller of this domain. In this
case, CICS could be terminated by the caller (for example, the
Try increasing the size limits of the DSAs or EDSAs. See the domain manager, DFHDMDM). A message will be issued to
CICS System Definition Guide or the CICS Performance Guide for this effect.
further information on CICS storage.
Module: DFHMNDM, DFHMNMN, DFHMNST
XMEOUT Parameters: applid, X'code',modname User response: Notify the system programmer. This is in all
Destination: Console probability a hardware error and you should in the first
instance investigate the store clock and find out whether it is
working properly. If this is the cause, you should take the
DFHMN0004 applid A possible loop has been detected at appropriate action to have it repaired or replaced.
Explanation: A CICS function is taking more time to process In the unlikely event that this is not a hardware problem, you
than CICS expects. A possible loop has been detected in will need further assistance from IBM. See Part 4 of the CICS
module modname at offset X'offset'. This is the offset of the Problem Determination Guide for guidance on how to proceed.
instruction which was executing at the time the error was Module: DFHMNDM, DFHMNMN, DFHMNST, DFHMNUE
detected. XMEOUT Parameters: applid, modname,X'code'
System action: An exception entry is made in the trace table. Destination: Console
suppressed dumps in the dump table. This is a critical error
and CICS is terminated, even if you have specified in the DFHMN0101 applid DMF error - DMF return code X'rc'.
dump table that CICS should not terminate. Explanation: The monitoring domain authorized services
routine issued a DFHSMFEW macro to write a record to the
CICS data management facilities (DMF) data handler and
encountered a non-zero return code.
User response: Notify the system programmer. If CICS has
System action: The request is ignored and the DMF record is
lost. An exception entry is made in the trace table. CICS
operation continues.
If the same error condition occurs continuously, the error
messages are suppressed but tracing continues. The message is
there may not be an error here. Usually, CICS will purge a
reissued if a different error condition occurs or if a zero return
CICS function which exceeds the runaway task time interval
code has been received since the message was last issued.
which you have specified on the ICVR system initialization
User response: Consult the description of the DFHEWTM
macro in the CICS Operations and Utilities Guide manual for a
that module modname will be terminated and CICS will
detailed explanation of the return code X'rc'.
continue.
Module: DFHMNSU
XMEOUT Parameters: applid, X'rc'
If CICS has terminated module modname, and you consider
that it was not a runaway, you should increase the ICVR time DFHMN0103I applid Monitoring control table for suffix 'xx'
interval. You will have to bring CICS down at a suitable time not found.
to do this permanently. But you can change the ICVR time Explanation: The monitoring control table for suffix xx could
interval temporarily online, using the CEMT transaction. not be found in a sublibrary described by the LIBDEF search
chain. This suffix is specified on the MCT system initialization
If raising the ICVR time does not solve the problem, you will parameter.

DFHMN0104 • DFHMN0107
System action: Control is returned to the parameter manager User response: None.
for interaction with the operator. Further action depends upon Module: DFHMNDM
which option is specified for the PARMERR system
initialization parameter. The operator may enter another suffix XMEOUT Parameter: applid
or continue with system initialization. Destination: Console
If initialization continues without an override, monitoring

domain uses the default monitoring control table. DFHMN0106 applid Unable to read the catalog record for
User response: There are three likely causes of this error: the Monitoring Domain.
v The monitoring control table is not in a sublibrary described Explanation: The monitoring domain has attempted to
by the LIBDEF search chain. reestablish the status of the monitoring classes and the
v The monitoring control table name has been misspelled. monitoring control table suffix under which it was running
v An incorrect suffix has been used at startup. during the last execution of CICS. But it was unable to
successfully read the record from the CICS global catalog
Ensure that the suffix specified is correct and that a sublibrary
(DFHGCD).
described in the LIBDEF search chain contains a copy of the
named monitoring control table.
System initialization continues with the supplied system
If the suffix is incorrect and PARMERR=INTERACT is initialization parameters.
specified, the operator is prompted to enter an alternative
suffix.
User response: Investigate the cause of the error using any
If the suffix is incorrect and PARMERR=IGNORE is specified, dump or other diagnostic messages which have been issued
the monitoring domain uses the default monitoring control (for example, from VSAM or VSE).
table.
If the problem has been caused by an I/O error, there will be
If the monitoring control table is missing or misspelled and an earlier CICS message. Follow the user response for this
you want to reinstall it, CICS has to be terminated. message.
Reassemble the monitoring control table into the relevant If the problem has been caused by an invalid data length,
sublibrary. there will be an exception trace entry in the trace table.
Module: DFHMNSR Module: DFHMNDM
XMEOUT Parameters: applid, xx XMEOUT Parameter: applid
DFHMN0104 applid Monitoring Control Table with suffix DFHMN0107 applid Unable to update the catalog record for
'xx' required for restart not found. the Monitoring Domain.
Explanation: The monitoring domain has determined the Explanation: The monitoring domain has attempted to
monitoring control table suffix xx from the last CICS update either the status of the monitoring classes or the
execution, but was unable to locate the monitoring control monitoring control table suffix in the CICS global catalog, but
table in a sublibrary described by the LIBDEF search chain was unable to successfully complete the request.
and no override suffix has been specified. System action: An exception entry is made in the trace table,
Subsequent executions of CICS will continue to use the suffix and CICS operation continues with the updated values. Since
specified in the message until it is changed in the SIT. the updates are not saved across a restart, the subsequent
System action: Initialization continues with the monitoring execution of CICS will restart with values recorded before the
domain using the default monitoring control table. updates were applied.
User response: Ensure that a sublibrary described in the Message DFHME0116 is normally produced containing the
LIBDEF search chain contains a copy of the named monitoring symptom string for this problem.
control table. If the monitoring control table is missing, it must User response: Investigate the cause of the error using any
have been deleted. If you want to reinstall the table, CICS dump or other diagnostic messages which have been issued
must be terminated. Reassemble the monitoring control table (for example, from VSAM or VSE).
into the relevant library.
Module: DFHMNDM If the problem has been caused by an I/O error, there will be
an earlier CICS message from the catalog. Follow the user
XMEOUT Parameters: applid, xx response for this message.
If the problem has been caused by an invalid data length,
there is an exception trace entry in the trace table.
DFHMN0105I applid Using default Monitoring Control Module: DFHMNSU
Table.
Explanation: The monitoring domain is initializing with XMEOUT Parameter: applid
default monitoring control table settings. This occurs: Destination: Console
1. If the user has specified MCT=NO, or
2. Following message DFHMN0104, or
3. After message DFHMN0103 or DFHMN0106 has been
issued, but no corrective action has been taken.

DFHMN0108I • DFHMN0206S
Destination: SYSLST
DFHMN0108I applid Using Monitoring Control Table suffix
'xx'.
Explanation: The monitoring control table with the suffix xx DFHMN0203S Invalid parameter. SYSID must be four
is used for this CICS run. characters or less.
System action: Processing continues. Explanation: A SYSID of greater than 4 characters, or a
User response: None. You can suppress this message with SYSID keyword without an operand has been specified.
the system initialization parameter, MSGLVL=0. System action: The job step is terminated with a return code
Module: DFHMNDM of 12.
User response: Specify a valid SYSID of up to 4 characters.
XMEOUT Parameters: applid, xx
For further guidance, see the CICS Operations and Utilities
Guide.
Module: DFHMNDUP
DFHMN0109I applid CICS Monitoring is active. Destination: SYSLST
Explanation: The CICS monitoring facility is currently active
for this run of CICS.
DFHMN0204S Invalid parameter. GAPPLID must be eight
characters or less.
Explanation: A generic APPLID (GAPPLID) of greater than 8
the system initialization parameter, MSGLVL=0.
characters, or a GAPPLID keyword without an operand has
Module: DFHMNDM
been specified.
XMEOUT Parameter: applid System action: The job step is terminated with a return code
Destination: Console of 12.
User response: Specify a valid GAPPLID of up to 8
characters. For further guidance, see the CICS Operations and
DFHMN0110I applid CICS Monitoring is inactive. Utilities Guide.
Explanation: The CICS monitoring facility is currently Module: DFHMNDUP
inactive for this run of CICS. Destination: SYSLST
the system initialization parameter, MSGLVL=0. DFHMN0205S Invalid parameter. SAPPLID must be eight
Module: DFHMNDM characters or less.
Explanation: A specific APPLID (SAPPLID) of greater than 8
XMEOUT Parameter: applid characters has been specified.
Destination: Console System action: The job step is terminated with a return code
of 12.
DFHMN0201S Invalid parameter. The equals sign is User response: Specify a valid SAPPLID of up to 8 characters
missing. or allow the SAPPLID to default to the GAPPLID by not
Explanation: A SYSIPT parameter has been encountered that specifying SAPPLID. For further guidance, see the CICS
does not contain an equals sign. Equals signs are mandatory Operations and Utilities Guide.
for every keyword supported by the monitoring dictionary Module: DFHMNDUP
utility. Destination: SYSLST
System action: The job step is terminated with a return code
of 12. DFHMN0206S Invalid parameter. DATE must be of format
User response: Correct the SYSIPT keyword that does not yyddd or yyyyddd.
have an equals sign and resubmit the job. For further Explanation: The date has been specified incorrectly. There
guidance on the syntax of DFHMNDUP keywords, see the are three possible reasons for this:
CICS Operations and Utilities Guide. v The date specified is not in the correct format of yyddd or
Module: DFHMNDUP yyyyddd
Destination: SYSLST v The date contains non-numeric characters
v 'ddd' is not in the range 1 through 366.
DFHMN0202S Invalid parameter. MCT incorrectly specified System action: The job step is terminated with a return code
Explanation: Following the equals sign of the MCT= of 12.
keyword there must be a 2-character operand or a delimiter. User response: Ensure that the date is in the format 'yyddd'
Neither has been found. The 2-character operand is treated as or 'yyyyddd' and that the values are valid.
the suffix for an MCT to load. If you want DATE to default to the current date, do not
System action: The job step is terminated with a return code specify this parameter. For further guidance, see the CICS
of 12. Operations and Utilities Guide.
User response: Correct the MCT= keyword with a valid Module: DFHMNDUP
operand or delimiter. Destination: SYSLST
If you do not wish to have a dictionary record constructed
from a particular MCT, you can use a default MCT image by
specifying a blank or a comma after the equals sign, or by
specifying MCT=NO. For further guidance, see the CICS
Module: DFHMNDUP

DFHMN0207S • DFHMN0216S
Module: DFHMNDUP
DFHMN0207S Invalid parameter. TIME must be of format
Destination: SYSLST
hhmmss.
Explanation: The time has been specified incorrectly. There
are three possible reasons for this: DFHMN0212S Storage obtain for output record has failed.
v More than 6 characters have been specified Explanation: A request for storage for the 32KB record buffer
v The value specified contains nonnumeric characters storage has failed. There is not enough storage below the 16M
v The hours (hh), minutes (mm), or seconds (ss) are outside of line available in the partition.
the valid range. System action: The job step is terminated with a return code
System action: The job step is terminated with a return code of 12.
of 12. User response: Increase the storage available in the VSE
User response: Ensure that the time specified is in the format partition and try again.
'hhmmss' and that the values are valid. Module: DFHMNDUP
Destination: SYSLST
If you want TIME to default to the current time, do not
specify this parameter. For further guidance, see the CICS
Operations and Utilities Guide. DFHMN0214S Invalid parameter. Missing delimiter
Module: DFHMNDUP detected.
Destination: SYSLST Explanation: DFHMNDUP parameter syntax requires
keyword/operand pairs to be separated by a delimiter in the
DFHMN0208S Invalid parameter. Keyword is unknown. form of a comma or a blank space. A delimiter has been found
Explanation: A SYSIPT parameter has been processed and missing from a keyword/operand.
found to contain an unrecognized keyword. System action: The job step is terminated with a return code
System action: The job step is terminated with a return code of 12.
of 12. User response: If the SYSIPT data set has been coded such
User response: Rename the unrecognized keyword. See the that there are multiple parameters on one line, then ensure
CICS Operations and Utilities Guide. for a complete list of that there is one blank or one comma between each parameter.
supported keywords. Also, ensure that there are no blanks If the SYSIPT data set has been coded such that there is only
preceding any of the keywords in the SYSIPT data set. one parameter on a line, ensure that it is terminated with a
Module: DFHMNDUP blank or a comma. For further guidance on the syntax of
Destination: SYSLST DFHMNDUP parameters, see the CICS Operations and Utilities
Guide.
Module: DFHMNDUP
DFHMN0209S No SYSIPT parameters have been specified. Destination: SYSLST
Explanation: There are no SYSIPT parameters specified in the
JCL.
DFHMN0215S Mandatory SYSIPT parameter(s) missing.
Explanation: The two mandatory parameters are for the
of 12.
generic APPLID (GAPPLID) and the VSE system identifier
User response: Check the JCL for the existence of SYSIPT
(SYSID). These two parameters have not been specified and
parameters. If SYSIPT does not exist or has no parameters, see
there are no defaults.
the CICS Operations and Utilities Guide for guidance on coding
DFHMNDUP parameters.
of 12.
Module: DFHMNDUP
User response: Specify the following:
Destination: SYSLST
v The generic APPLID of the CICS system for which
DFHMNDUP is going to produce a dictionary record.
DFHMN0210S applid Load for MCT has failed. MCT cannot v The system identifier for the VSE system that produced the
be found. A dump will be provided. monitoring performance class records you are going to
Explanation: DFHMNDUP attempted to load 'DFHMCTxx' process.
from the LIBDEF search chain, where 'xx' is the suffix
For further guidance on the syntax of DFHMNDUP
provided via the MCT= keyword. This MCT was not found in
parameters, see the CICS Operations and Utilities Guide.
the LIBDEF search chain.
Module: DFHMNDUP
System action: The job step is abended with a dump.
Destination: SYSLST
User response: Ensure that the MCT suffix is correct and that
the sublibrary that contains it is in the LIBDEF search chain
for the job step. DFHMN0216S Invalid parameter. JOBNAME must be eight
Module: DFHMNDUP characters or less.
Destination: Console Explanation: A JOBNAME has been specified with more than
eight characters.
DFHMN0211S Storage obtain for control blocks has failed.
of 12.
Explanation: A request for the utilities global storage has
User response: Specify a valid JOBNAME of up to eight
failed. There is not enough storage below the 16MB line
available in the partition.
Utilities Guide.
Module: DFHMNDUP
of 12.
Destination: SYSLST
User response: Increase the storage available in the VSE
partition and try again.

DFHMN0217S • DFHMN0221
DFHMN0217S Invalid parameter. JOBDATE must be of DFHMN0221 DFHMNDUP CANNOT OPEN THE SYSIPT
format yyddd or yyyyddd. FILE.
Explanation: The JOBDATE parameter has been specified Explanation: The SYSIPT file cannot be opened because the
incorrectly. There are three possible reasons for this: SYSIPT DLBL statement is missing or incorrectly defined.
v The date specified is not in the correct format of yyddd or System action: The job step is terminated with a return code
yyyyddd of 12.
v Nonnumeric characters have been specified User response: Ensure that the SYSIPT DLBL statement has
v The number of days 'ddd' is not in the range 1 through 366. been correctly defined. For further guidance, see the CICS
System action: The job step is terminated with a return code Operations and Utilities Guide.
of 12. Module: DFHMNDUP
User response: Ensure that JOBDATE consists of valid Destination: Console
characters in the format 'yyddd' or 'yyyyddd'.
If you want JOBDATE to default to the current date, do not
Module: DFHMNDUP
Destination: SYSLST
DFHMN0218S Invalid parameter. JOBTIME must be of

format hhmmss.
Explanation: The JOBTIME parameter has been specified
incorrectly. There are three possible reasons for this:
v More than six characters have been specified
v Nonnumeric characters have been specified
v The hours (hh), minutes (mm), or seconds (ss) are outside of
the valid range.
of 12.
User response: Ensure that JOBTIME consists of valid
characters in the format 'hhmmss'.
If you want JOBTIME to default to the current time, do not

Module: DFHMNDUP
Destination: SYSLST
DFHMN0219S Invalid parameter. USERID must be eight

characters or less.
Explanation: A USERID has been specified with more than
eight characters.
of 12.
User response: Specify a valid USERID of up to eight
Utilities Guide.
Module: DFHMNDUP
Destination: SYSLST
DFHMN0220 DFHMNDUP CANNOT OPEN THE SYSLST

FILE.
Explanation: The SYSLST file cannot be opened because the
SYSLST DLBL statement is missing or incorrectly defined.
of 12.
User response: Ensure that the SYSLST DLBL statement has
been correctly defined. For further guidance, see the CICS
Module: DFHMNDUP

DFHPA0001 • DFHPA0004
DFHPAxxxx messages
DFHPA0001 applid An abend (code aaa/bbbb) has occurred
Explanation: An unexpected program check or operating If appropriate, an error return code is sent to the caller of this
system abend with abend code aaa/bbbb occurred at offset domain. In this case, CICS could be terminated by the caller
X'offset' in module modname. This can be caused by corruption (for example, the domain manager, DFHDMDM). A message is
of CICS code or control blocks. issued to this effect.
The code aaa/bbbb is a three digit hexadecimal VSE code (if Message DFHME0116 is normally produced containing the
applicable), followed by a four digit alphanumeric CICS code. symptom string for this problem.
The VSE code is a system completion code, for example 0C1. User response: This indicates a possible error in CICS code.
If an VSE code is not applicable, this field is filled with three The severity of its impact depends on the importance of the
hyphens. The CICS code is an abend code or a number function being executed at the time of the error.
abend code; 1310 refers to message DFHTS1310). CICS may not have been terminated.
During initialization, CICS might not have access to the user's If the message occurs once and module modname is not crucial
applid coded in the SIT. If CICS produces this message in these to the running of your CICS system, you may decide to
circumstances, it uses the default applid value DBDCCICS. continue to run and bring CICS down at a convenient time to
System action: A system dump is taken unless specifically resolve the problem.
suppressed for this system abend code, and the system If the message recurs or if you cannot run without the full use
attempts to continue operation unless termination has been of module modname, you should bring CICS down in a
requested via the dump table. controlled shutdown.
Message DFHME0116 is normally produced containing the For further information about CICS exception trace entries,
symptom string for this problem. refer to the CICS Problem Determination Guide.
User response: Notify your system programmer. If CICS is
still running, it is necessary to decide whether to terminate You need further assistance from IBM to resolve this problem.
CICS. See Part 4 of the CICS Problem Determination Guide for
Look up the VSE code, if there is one, in "OS/390 API Abend Module: DFHPADM
Errors" of z/VSE Messages and Codes - Volume 1. XMEOUT Parameters: applid, X'code',modname
page 453. This tells you, for example, whether the error was a DFHPA0004 applid A possible loop has been detected at
program check, an abend, or a runaway, and may give you offset X'offset' in module modname.
some guidance concerning user response. Explanation: A CICS function is taking more time to process
instruction which was executing when the error was detected.
You need further assistance from IBM to resolve this problem. System action: An exception entry is made in the trace table.
See Part 4 of the CICS Problem Determination Guide for A system dump is taken, unless you have specifically
guidance on how to proceed. suppressed dumps in the dump table.
Module: DFHPAGP, DFHPADM, DFHPAIO
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname that CICS should terminate.
DFHPA0002 applid A severe error (code X'code') has User response: If CICS has not been terminated, it is
occurred in module modname. necessary to decide whether the problem is serious enough to
Explanation: An error has been detected in module modname bring CICS down.
The code X'code' is the exception trace point ID which Since some CICS functions can use a lot of processor time, this
uniquely identifies what the error is and where the error was message may have been caused by a long-running function. So
detected. there may not be an error here. Usually, CICS purges a CICS
During initialization, CICS may not have access to the user's you have specified on the ICVR system initialization
applid coded in the SIT. If CICS produces this message in these parameter (ICVR is measured in milliseconds). This means
circumstances, it uses the default applid value DBDCCICS. that the CICS module identified in the message is terminated
System action: An exception entry (code X'code' in the and CICS continues..
unless you have specifically suppressed dumps in the dump However, if you have declared ICVR=0 and you consider that
table. module modname has gone into a loop, you have to terminate

If CICS has terminated module modname, and you consider User response: None.
that it was not a runaway, you should increase the ICVR time Module: DFHPAIO
interval. You have to bring CICS down at a suitable time to do Destination: Console
this permanently. However, you can change the ICVR time
interval temporarily online, using the CEMT transaction.
DFHPA1104 applid SPECIFY ALTERNATIVE SIT
If raising the ICVR time does not solve the problem, you will PARAMETERS, IF ANY, AND THEN TYPE
need further assistance from IBM. See Part 4 of the CICS '.END'.
Problem Determination Guide for guidance on how to proceed. Explanation: If the word "CONSOLE" or "CN" was detected
Module: DFHPADM in either the parameter input stream on the EXEC statement of
the CICS JCL, or in the SYSIPT data set, this prompt message
is displayed when the parameter (PA) manager is ready to
accept console overrides.
System action: The system initialization program waits for a
DFHPA1100 applid OVERRIDE PARAMETERS FROM JCL response from the operator.
EXEC STATEMENT: parm User response: Enter the required parameter changes,
Explanation: This message is displayed during CICS separated by commas. Terminate your reply by entering
initialization to show the SIT overrides obtained from the '.END'.
PARM parameter of the JCL EXEC statement for the CICS job. Module: DFHPAIO
If the parameter string parm contains 40 characters or less, it is Destination: Console
shown on this message. Otherwise it is shown on a
DFHPA1927 message following this message.
DFHPA1105 applid CONTINUE SPECIFYING SIT
During initialization, CICS may not have access to the user's PARAMETERS AND THEN TYPE '.END'.
applid coded in the SIT. If CICS produces this message in these Explanation: While SIT overrides are being entered on the
circumstances, it uses the default applid value DBDCCICS. console, this prompt message is displayed to request more
System action: System initialization continues. overrides if the previous line did not end with '.END'.
User response: None. System action: The system initialization program waits for
Module: DFHPAIO more override parameters to be entered by the operator.
Destination: Console User response: Continue entering the required parameter
changes, separated by commas. Terminate your reply by
entering '.END'.
DFHPA1101 applid DFHSITxx IS BEING LOADED. Module: DFHPAIO
Explanation: This is an informational message displayed Destination: Console
during CICS initialization.
xx, if present, represents the 1- or 2-character suffix for the SIT DFHPA1106 applid MODULE DFHSITxx COULD NOT BE
being used. LOADED. SPECIFY NEW SUFFIX,
During initialization, CICS may not have access to the user's 'NONE'(UNSUFFIXED) OR 'CANCEL'.
applid coded in the SIT. If CICS produces this message in these Explanation: During PA domain initialization, a SIT with a
circumstances, it uses the default applid value DBDCCICS. suffix of xx could not be loaded.
System action: System initialization continues. During initialization, CICS may not have access to the user's
User response: None. applid coded in the SIT. If CICS produces this message in these
Module: DFHPADM circumstances, it uses the default applid value DBDCCICS.
Destination: Console System action: The PA domain initialization routines wait for
the operator to enter an alternative 1- or 2-character suffix, or
YES to request the unsuffixed SIT, or CANCEL. If CANCEL is
DFHPA1102 applid OVERRIDE PARAMETERS FROM
entered, CICS is abnormally terminated.
SYSIPT:
User response: Determine whether the suffix is correct. If it is
Explanation: This message is displayed during CICS
not, enter the correct suffix or enter 'YES' for the unsuffixed
initialization before displaying the SIT overrides obtained from
version. Otherwise enter 'CANCEL', correct the error (by
the SYSIPT data set. The message is followed by a series of
adding the module to the appropriate library) and restart
DFHPA1927 messages that show the actual contents of the
CICS.
SYSIPT records.
Module: DFHPADM
During initialization, CICS may not have access to the user's Destination: Console
System action: System initialization continues. DFHPA1107 applid A level VERSION OF MODULE
User response: None. DFHSITxx WAS LOADED. CICS CAN ONLY
Module: DFHPAIO INITIALIZE WITH THE CURRENT LEVEL
Destination: Console SIT.
Explanation: During PA domain initialization, a SIT with a
suffix of xx and a release level of level was loaded. Since this
DFHPA1103 applid END OF FILE ON SYSIPT. version is not compatible with current CICS code, CICS is
Explanation: This is an informational message displayed abnormally terminated.
when CICS has reached the end of the SYSIPT data set.
During initialization, CICS may not have access to the user's applid coded in the SIT. If CICS produces this message in these
applid coded in the SIT. If CICS produces this message in these circumstances, it uses the default applid value DBDCCICS.
circumstances, it uses the default applid value DBDCCICS. System action: CICS terminates abnormally.
System action: System initialization continues. User response: To correct the error, reassemble the SIT at the

current CICS level. Refer to the CICS Transaction Server for

DFHPA1903 applid ERROR WHILE READING FROM
OS/390: Migration Guide for guidance on changes to the SIT
SYSIPT DATA SET. CICS IS TERMINATED.
that may be required for the new release. CICS should then be
restarted. Explanation: An error has occurred while attempting to read
a record from the SYSIPT data set. This can occur if the
Alternatively, the system may have been pointing to the SYSIPT data set has been corrupted, or has been incorrectly
wrong SIT. To correct this second case, check the bring up JCL defined (for example, has not been defined with a logical
to make sure that the 'SIT=' override is correct. Refer to the record length, LRECL, of 80).
CICS System Definition Guide for guidance on coding system
initialization parameters. Furthermore, check the library search During initialization, CICS may not have access to the user's
order to make sure that stray SITs, which may be applid coded in the SIT. If CICS produces this message in these
unknowingly present, are removed or renamed. circumstances, it uses the default applid value DBDCCICS.
Module: DFHPADM System action: CICS terminates abnormally.
Destination: Console User response: Correct the problem in the SYSIPT data set.
Module: DFHPAIO
DFHPA1108 applid DFHSITxx HAS BEEN LOADED.
(GENERATED AT MM/DD= mm/dd
HH/MM= hh/mm). DFHPA1907 applid SIT DATA data IS INVALID FOR
Explanation: This is an informational message displayed KEYWORD keyword. KEYWORD IS
during CICS initialization. It displays the date and time that IGNORED.
the loaded system initialization table was generated. Explanation: This message is displayed if the data specified,
v xx is the suffix of the SIT being used. either for a keyword in the SIT or for a SIT override, is
v mm/dd is the date (month and day) that the SIT was invalid, AND the PARMERR=IGNORE option is specified in
generated. the SIT or as an override, where:
v hh/mm is the time (hours and minutes of the 24 hour clock) v keyword is the keyword for which the value is in error.
that the SIT was generated. v data is the invalid data.
System action: CICS Initialization continues. System action: The keyword is ignored. CICS attempts to
User response: None. initialize without the keyword in error.
Module: DFHPADM User response: Correct the error by specifying a valid value
Destination: Console for the keyword wherever it has been specified, either in the
SIT or in the CICS input JCL, prior to restarting CICS. Refer to
DFHPA1901 applid modname COULD NOT BE FOUND. the CICS System Definition Guide for information on how to do
CICS IS TERMINATED. this.
Explanation: An error has occurred while attempting to load Module: DFHPAGP
either DFHPASYL or DFHPAIO. Destination: Console

applid coded in the SIT. If CICS produces this message in these DFHPA1908 applid SIT DATA data IS INVALID FOR
circumstances, it uses the default applid value DBDCCICS. KEYWORD keyword. CICS IS TERMINATED.
System action: CICS terminates abnormally. Explanation: This message is displayed if the data specified,
User response: Correct the problem with the module that either for a keyword in the SIT or for a SIT override, is
failed to load. invalid, and the PARMERR=ABEND option is specified in the
SIT or as an override.
For example, check that a module modname actually exists in v keyword is the keyword for which the value is in error.
the program libraries used by CICS. Check the JCL and that v data is the invalid data.
the correct name, the correct library and the correct member in
the library are used. This message is issued only if the data for keyword MCT is in
Module: DFHPADM error.
Destination: Console System action: CICS terminates abnormally.
User response: Correct the error by specifying a valid value
for the keyword wherever it has been specified, either in the
DFHPA1902 applid UNABLE TO OPEN SYSIPT DATA SIT or in the CICS input JCL, prior to restarting CICS. Refer to
SET. CICS IS TERMINATED. the CICS System Definition Guide for information on how to do
Explanation: An error has occurred while attempting to open this.
the SYSIPT data set. This occurs if the SYSIPT data set does Module: DFHPAGP
not exist. Destination: Console
applid coded in the SIT. If CICS produces this message in these DFHPA1909 applid SIT DATA data IS INVALID FOR
circumstances, it uses the default applid value DBDCCICS. KEYWORD keyword. RESPECIFY KEYWORD
System action: CICS terminates abnormally. AND DATA.
User response: Ensure that the SYSIPT data set exists and is Explanation: This message is issued if the data specified,
correct. either for a keyword in the SIT or for a SIT override, is
Module: DFHPAIO invalid, and the PARMERR=INTERACT option is specified in
Destination: Console the SIT or as an override. The message inserts are as follows:
v keyword is the keyword for which the value is in error.
v data is the invalid data.

Note: PARMERR=INTERACT is the default action for invalid Module: DFHPADM

keyword data. Destination: Console
System action: CICS waits for the corrected keyword and
data to be entered as an override on the console by the
DFHPA1913 applid INVALID DATA HAS BEEN
operator, and analyzes this override.
DETECTED FOR SIT OVERRIDE keyword BY
User response: Enter the corrected SIT keyword and data on
MODULE modname. OVERRIDE IS
the console, or bypass by typing '.END', or just supply a blank
IGNORED.
line. Refer to the CICS System Definition Guide for information
Explanation: This message can be issued in the following
on how to do this. situations:
Module: DFHPAGP v If the data supplied for a SIT override is syntactically
Destination: Console invalid, and the PARMERR=IGNORE system initialization
parameter is specified. The insert keyword is the keyword for
DFHPA1910 applid SIT OVERRIDE keyword IS NOT which the value is in error.
RECOGNIZED. OVERRIDE IS IGNORED. v In response to invalid data when PARMERR=INTERACT is
(MODULE modname). specified but the user has been attempting to correct a
Explanation: This message is issued if a keyword specified in previous invalid SIT keyword or value. In this case,
the input override parameter stream is invalid, and the message DFHPA1912 or DFHPA1915 follows this message
PARMERR=IGNORE option is specified in the SIT, or as an to prompt for the correction to the original error.
override. The insert keyword is the invalid keyword. v When PARMERR=INTERACT is specified if invalid data
has been passed in PARM or SYSIPT for a keyword that
During initialization, CICS may not have access to the user's cannot be entered from the console (and therefore cannot be
corrected by interaction with the console). This typically
applies to security keywords.
System action: The keyword is ignored, and CICS attempts
to initialize without the keyword in error.
User response: Ensure the keyword specified is correct and During initialization, CICS may not have access to the user's
update CICS input JCL with the corrected keyword prior to applid coded in the SIT. If CICS produces this message in these
the next initialization of CICS. circumstances, it uses the default applid value DBDCCICS.
Module: DFHPADM, DFHPAGP System action: The keyword is ignored, and CICS attempts
Destination: Console to initialize without the keyword in error.
User response: Ensure the value specified is correct and
update CICS input JCL with the corrected keyword prior to
DFHPA1911 applid SIT OVERRIDE keyword IS NOT the next initialization of CICS.
RECOGNIZED. CICS IS TERMINATED. Module: DFHPADM, DFHPAGP
Explanation: This message is displayed if a keyword Destination: Console
specified in the input override parameter stream is invalid,
and the PARMERR=ABEND option is specified in the SIT, or
as an override. the insert keyword is the invalid keyword. DFHPA1914 applid INVALID DATA HAS BEEN
DETECTED FOR SIT OVERRIDE keyword.
CICS IS TERMINATED.
Explanation: This message is displayed if the data specified
for a SIT override is syntactically invalid, and the
System action: CICS terminates abnormally.
PARMERR=ABEND option is specified in the SIT, or as an
User response: Correct the error by specifying a valid
override.
keyword in the SIT overrides, then restart CICS. Refer to the
CICS System Definition Guide for information on how to do The insert keyword is the keyword for which the value is in
this. error.
Module: DFHPADM
Destination: Console During initialization, CICS may not have access to the user's
DFHPA1912 applid SIT OVERRIDE keyword IS NOT System action: CICS terminates abnormally.
RECOGNIZED. SPECIFY CORRECT SIT User response: Correct the error by specifying a valid value
OVERRIDE. for the keyword in the SIT overrides, then restart CICS. Refer
Explanation: This message is issued if a keyword specified in to the CICS System Definition Guide for information on how to
the input override parameter stream is invalid, and the do this.
PARMERR=INTERACT option is specified in the SIT, or as an Module: DFHPADM
override. The insert keyword is the invalid keyword. Note that Destination: Console
PARMERR=INTERACT is the default action for invalid SIT
overrides.
DFHPA1915 applid INVALID DATA HAS BEEN
During initialization, CICS may not have access to the user's DETECTED FOR SIT OVERRIDE keyword.
applid coded in the SIT. If CICS produces this message in these RESPECIFY THE OVERRIDE.
circumstances, it uses the default applid value DBDCCICS. Explanation: This message is displayed if the data specified
System action: CICS waits for the corrected override to be for a SIT override is syntactically invalid or is a numeric value
entered on the console by the operator, and analyzes this of 2 gigabytes or greater. It is only displayed if the
override. PARMERR=INTERACT option is specified in the SIT, or as an
User response: Enter the corrected SIT override on the override.
console, or bypass by typing '.END', or just supply a blank
line. The insert keyword is the keyword for which the value is in
error.

Note: PARMERR=INTERACT is the default action for invalid

DFHPA1919I applid SPECIFIED DATA IS INCORRECT.
SIT overrides.
ALL SUBSEQUENT OVERRIDES ON THIS
System action: CICS waits for the corrected override to be
LINE IGNORED.
entered on the console by the operator, and then analyzes this
Explanation: An invalid value for a keyword has been
override.
entered after message DFHPA1912 or DFHPA1915 has been
User response: Enter the corrected SIT override on the
issued. CICS has been unable to analyze the overrides
console, or bypass by typing '.END', or just supply a blank
following the invalid one.
line.
Module: DFHPADM During initialization, CICS may not have access to the user's
Destination: Console applid coded in the SIT. If CICS produces this message in these
System action: CICS continues to prompt for the corrected
DFHPA1916 applid SIT OVERRIDE DATA data IS OUT OF
override using either message DFHPA1912 or message
RANGE FOR KEYWORD keyword.
DFHPA1915.
OVERRIDE IS IGNORED.
User response: Enter the corrected SIT override, ensuring
Explanation: This message is displayed if the data supplied
that the data is in the valid range for that keyword.
for a SIT override is out of range, and the
PARMERR=IGNORE option is specified in the SIT, or as an You cannot suppress this message with the system
override. initialization parameter MSGLVL=0.
v keyword is the keyword for which the value is in error. Module: DFHPADM
v data is the invalid data. Destination: Console
System action: The keyword is ignored. CICS attempts to
initialize without the keyword in error.
User response: Ensure the value specified is correct and DFHPA1920I applid SIT KEYWORD keyword AND ALL
update CICS input JCL with the corrected keyword prior to SUBSEQUENT OVERRIDES ON THIS LINE
the next initialization of CICS. IGNORED.
Module: DFHPAGP Explanation: An invalid keyword has been entered in
Destination: Console response to message DFHPA1912 or DFHPA1915. CICS has
been unable to analyze the overrides following the invalid
one.
RANGE FOR KEYWORD keyword. CICS IS The insert keyword is the invalid keyword.
TERMINATED. During initialization, CICS may not have access to the user's
Explanation: This message is displayed if the data specified applid coded in the SIT. If CICS produces this message in these
for a SIT override is out of range, and the PARMERR=ABEND circumstances, it uses the default applid value DBDCCICS.
option is specified in the SIT, or as an override. System action: CICS continues to prompt for the corrected
v keyword is the keyword for which the value is in error. keyword using message DFHPA1912 or message DFHPA1915.
v data is the invalid data. User response: Enter the corrected SIT override, ensuring
System action: CICS terminates abnormally. that the keyword is valid.
User response: Correct the error by specifying a valid value
for the keyword in the SIT overrides, and restart CICS. Refer Refer to the CICS System Definition Guide for information on
to the CICS System Definition Guide for information on how to how to do this.
do this.
You cannot suppress this message with the SIT parameter,
Module: DFHPAGP
MSGLVL=0.
Module: DFHPADM
RANGE FOR KEYWORD keyword. DFHPA1921 applid PLEASE SPECIFY THE REQUIRED
RESPECIFY THE OVERRIDE. SIT SUFFIX, OR SPECIFY
Explanation: This message is displayed if the data specified 'NONE'(UNSUFFIXED).
for a SIT override is out of range, and the Explanation: The system initialization table (SIT) holds
PARMERR=INTERACT option is specified in the SIT, or as an information needed for CICS to initialize. This is loaded
override. during preinitialization. The user specifies a 1- or 2-character
v keyword is the keyword for which the data is in error. suffix to identify which SIT to load. To use the unsuffixed
v data is the invalid data. default SIT, reply with 'SIT=NO'.
Note: PARMERR=INTERACT is the default action for invalid During initialization, CICS may not have access to the user's
SIT overrides. applid coded in the SIT. If CICS produces this message in these
System action: CICS waits for the corrected override to be circumstances, it uses the default applid value DBDCCICS.
entered on the console by the operator, and analyzes this System action: The system loads and uses the specified SIT if
override. it can be found. Otherwise the user is prompted to enter a
User response: Enter the corrected SIT override on the valid suffix.
console, or bypass by typing '.END', or just supply a blank User response: Type 'SIT=xx' in response to the message,
line. where xx represents the SIT suffix to be used. (A suffix of 'NO'
Module: DFHPAGP causes the system to load an unsuffixed SIT).
Destination: Console Module: DFHPADM.

DFHPA1922I • DFHPA1928
User response: Alter the system initialization parameters so

DFHPA1922I applid SPECIAL KEYWORD keyword HAS
that parm2 is greater than parm1 for the next bring up of CICS.
BEEN REPEATED AND IS IGNORED.
(Refer to the CICS System Definition Guide for more
Explanation: There are 2 special keywords, each with an
information on coding system initialization parameters.)
abbreviation. The first is SYSIPT, which has the abbreviation
SI. The second is CONSOLE, which has the abbreviation CN. CICS initialization continues with the default values. The user
These keywords direct CICS to read SIT overrides from the can then change the defaulted values using the CICS supplied
SYSIPT data stream and from the console respectively. transaction.
The system has found a duplication of one of these keywords. You cannot suppress this message with the system
The JCL should be amended. initialization parameter, MSGLVL=0.
Module: DFHPADM, DFHPAGP
System action: System initialization continues. DFHPA1926 applid A MISSING DELIMITER HAS BEEN
User response: Correct the JCL by removing the second DETECTED FOR OVERRIDE keyword
occurrence of the special keyword specified. (Refer to the CICS (MODULE modname).
System Definition Guide for more information on coding CICS Explanation: The data supplied for a SIT override keyword
system initialization parameters). has not been delimited correctly.
You cannot suppress this message with the system User response: Correct the specified override in the SYSIPT
initialization parameter MSGLVL=0. data set by entering the opening or the closing delimiter on its
Module: DFHPADM data.
Restart CICS.
DFHPA1923I applid SPECIAL KEYWORD keyword HAS Refer to the CICS System Definition Guide for the required
BEEN DEFINED OUT OF CONTEXT. delimiter for keyword keyword.
Module: DFHPADM
Explanation: There are 2 special keywords, each with an
abbreviation. The first is SYSIPT, which has the abbreviation
SI. The second is CONSOLE, which has the abbreviation CN.
These keywords direct CICS to read SIT overrides from the DFHPA1927 applid text
SYSIPT data stream and from the console respectively. Explanation: This message is displayed during CICS
initialization to show parameters that will override the system
SYSIPT cannot be specified from either the SYSIPT data
initialization parameters coded on the DFHSIT macro. If it is
stream, or from the console. CONSOLE cannot be specified preceded by message DFHPA1100, text shows the contents of
from the console. the PARM parameter from the JCL EXEC statement. If it is
The system has found the specified keyword keyword in one of preceded by message DFHPA1102, text shows the contents of a
the situations described above, and so the JCL should be record read from the SYSIPT data set.
amended. During initialization, CICS may not have access to the user's
Module: DFHPAIO
User response: Correct the JCL by removing the special Destination: Console
keyword specified (Refer to the CICS System Definition Guide
for more information on coding CICS system initialization
parameters). DFHPA1928 applid IF XRF=YES, THE GENERIC AND
SPECIFIC APPLIDS MUST BE DIFFERENT.
You cannot suppress this message with the system CICS IS TERMINATED.
initialization parameter MSGLVL=0. Explanation: In an XRF CICS system, a generic and a specific
Module: DFHPADM applid must be defined. They must also be unique.
This message is displayed and CICS is terminated if both
these applids, which are defined as SIT overrides, are found to
DFHPA1924I applid INITIALIZATION PARAMETER parm1 be identical in an XRF environment.
EXCEEDS parm2. BOTH ARE DEFAULTED.
(MODULE modname). This message is also displayed if only the generic applid is
Explanation: One of two situations has occurred. defined.
v Parameter parm1 has been set as greater than parameter System action: CICS terminates abnormally.
parm2 by override. User response: Correct the error by defining both the generic
v Parameter parm1 has been set to a certain level in the SIT and the specific applids as SIT overrides. Ensure that they are
unique. Refer to the CICS System Definition Guide for further
macro, but parameter parm2 has been changed by override
information on how to do this.
so that it is now less than parameter parm1.
Module: DFHPADM
In either case, the condition is invalid, and so default values Destination: Console
are applied to both parameters.
System action: Both parameters are set to their default values
and system initialization continues.

DFHPA1930 • DFHPC0402
Module: DFHPADM
DFHPA1930 applid CSDFRLOG=nn HAS BEEN IGNORED
AS CSDRECOV=ALL HAS NOT BEEN
SPECIFIED.
Explanation: When a forward recovery log value is specified DFHPA1935 applid keyword IS A SECURITY KEYWORD.
for the CSDFRLOG keyword, the CSDRECOV keyword must THIS KEYWORD AND ALL SUBSEQUENT
have the value ALL. However, the override parameter stream KEYWORDS ON THIS LINE ARE
has overridden the SIT values and this requirement has not IGNORED.
been fulfilled. Explanation: A SIT override has been entered at the console
System action: To enable initialization to continue, the which is deemed to be a member of the set of security system
CSDFRLOG value has been ignored. Because CSDFRLOG is initialization parameters. Security system initialization
ignored, the CICS CSD as defined in the input JCL is not parameters cannot be entered at the console. CICS has been
eligible for forward recovery logging. unable to analyze the overrides following the security
User response: Update CICS input JCL with the correct keyword.
values for the CSDFRLOG and CSDRECOV keywords prior to
the next initialization of CICS. During initialization, CICS might not have access to the user's
Module: DFHPADM applid coded in the SIT. If CICS produces this message in these
Destination: Console circumstances, it uses the default applid value DBDCCICS.
System action: CICS ignores the security SIT override and all
subsequent overrides entered on this line. Initialization
DFHPA1931 applid keyword IS A SECURITY KEYWORD continues.
AND CANNOT BE ENTERED AT THE User response: Update CICS input JCL so that security
CONSOLE. THE KEYWORD IS IGNORED. keywords are included in the SIT, SYSIPT or PARM prior to
Explanation: A SIT override has been entered at the console the next initialization of CICS.
which is deemed to be a member of the set of security system Module: DFHPADM
initialization parameters. Security system initialization Destination: Console
parameters cannot be entered at the console.
During initialization, CICS might not have access to the user's DFHPA1940 applid WRONG VERSION OF CICS SVC
applid coded in the SIT. If CICS produces this message in these MODULE DFHCSVC IN SVA.
circumstances, it uses the default applid value DBDCCICS. Explanation: CICS has validated the CICS SVC module
System action: CICS ignores the security SIT override, and DFHCSVC, but it is not the correct version for this release of
initialization continues. CICS. CICS cannot function without the correct version of
User response: Update CICS input JCL so that security DFHCSVC.
keywords are included in the SIT, SYSIPT or PARM prior to System action: CICS terminates abnormally.
the next initialization of CICS. User response: Correct the error by installing the correct
Module: DFHPADM version of DFHCSVC in the SVA, and restart CICS. Refer to
Destination: Console the CICS System Definition Guide, for information on how to do
this.
Module: DFHPAGP
DFHPA1932 applid A PSDINT VALUE GREATER THAN
ZERO WAS SPECIFIED WITH XRF=YES.
PSDINT HAS BEEN RESET TO 0.
Explanation: A conflict of options has been detected. You DFHPA1945 applid sitname MUST BE LINK-EDITED
have requested persistent session support by specifying a WITHOUT THE SVA OPTION. CICS IS
nonzero value for the PSDINT system initialization parameter. TERMINATED.
This parameter is used to set the persistent sessions delay Explanation: The system initialization table sitname has been
interval. However, you have also requested XRF support by link-edited with the SVA option, which means CICS will load
specifying XRF=YES. Persistent sessions support and XRF are it into read-only storage.
mutually exclusive. System action: CICS initialization is terminated.
System action: The PSDINT value defaults to 0. CICS User response: You should re-link the system initialization
attempts to continue with XRF support. table without the SVA option.
User response: Before you next initialize CICS, alter the Module: DFHPADM
system initialization parameters so that either PSDINT=0 or Destination: Console
XRF=NO. See the CICS System Definition Guide for further
information.
DFHPCxxxx messages
XMEOUT Parameters: applid, abcode,yyy
DFHPC0401 applid Abend abcode issued by yyy task.
Explanation: A CICS task has abnormally terminated with
CICS transaction abend code abcode. yyy identifies the task, for
example TCP (terminal control). DFHPC0402 applid Error with kernel error code errorcode
A task abend has been requested for a system task. CICS is has occurred while processing transaction
abnormally terminated with a system dump. abend abcode in transaction tranid
System action: CICS terminates abnormally with a dump. Explanation: A program check, abend, loop, or a second
User response: See the description of abend abcode for further transaction abend has occurred while processing a transaction
guidance. abend and CICS is unable to complete the original transaction
Module: DFHABAB abend.
System action: CICS processing is terminated.

DFHPC0405 • DFHPD0105
User response: This is a severe error in CICS internal manager cannot syncpoint correctly, and thus that data
processing. You need further assistance from IBM to resolve integrity is at risk.
this problem. See Part 4 of the CICS System Definition Guide for System action: CICS terminates abnormally with a system
guidance on how to proceed. dump.
Module: DFHABAB User response: See the description of abend abcode for further
guidance.
XMEOUT Parameters: applid, errorcode, abcode, tranid Module: DFHABAB
XMEOUT Parameters: applid, abcode,tranid
DFHPC0405 applid Abend abcode2 has been issued while
processing abend abcode1 for the same task,
transaction tranid. DFHPC0409 applid Abends abcode2 and abcode3 have been
Explanation: Transaction tranid has abnormally terminated issued while processing abend abcode1 for the
with abend code abcode1. While CICS was backing out same task, transaction tranid.
transaction tranid, another abend (namely abcode2) occurred. Explanation: A task has abnormally terminated with abend
CICS was unable to process the original abcode abend correctly. code abcode1. While processing this abend, the task abnormally
System action: CICS is terminated with a dump. terminated twice more (in CICS code) with abends abcode2 and
User response: Investigate why abend abcode1 occurred. It abcode3 in that sequence. This may be a permanent abend
may be due to an error in CICS abend handling. loop.
Module: DFHABAB System action: CICS terminates abnormally with a system
dump.
XMEOUT Parameters: applid, abcode2,abcode1, tranid User response: See the description of abend abcode1 for
Destination: Console further guidance. You may need further assistance from IBM
to resolve this problem. See Part 4 of the CICS System
DFHPC0408 applid Abend abcode has been issued during Definition Guide for guidance on how to proceed.
post commit processing, transaction tranid. Module: DFHABAB
Explanation: During post commit processing for transaction XMEOUT Parameters: applid, abcode2,abcode3, abcode1, tranid
tranid, the transaction issued abend abcode. An abend during Destination: Console
transaction post commit processing implies that a resource
DFHPDxxxx messages
Explanation: The address address of a block of type xxxxxxxx
DFHPD0101 Pointer to xxxxxxxx at offset X'offset' is
is invalid.
invalid.
System action: Dump formatting continues after skipping
Explanation: A pointer to a block of type xxxxxxxx, whose
any sections affected by the error.
address is at offset offset in the block just formatted, is invalid.
User response: Either the pointer to the required area was
corrupted, the pointer has not been initialized, or the address
was valid but the area was not present in the dump. In the
User response: Either the pointer to the required area was
latter case, if the area is essential for diagnosing the problem,
corrupted, the pointer has not been initialized, or the address
a fresh dump which includes the missing area has to be
was valid but the area was not present in the dump. In the
obtained.
latter case, if the area is essential for diagnosing the problem,
Module: DFHPD410
a fresh dump which includes the missing area has to be
Destination: SYSLST
obtained.
It is possible that the storage is present in the dump, and the
pointer has been initialized with its address, but the storage DFHPD0104 Address of xxxxxxxx is zero.
has not been referred to by CICS code. You can check this by Explanation: The address of a block of type xxxxxxxx is zero.
browsing the storage in the dump at this address. System action: Dump formatting continues after skipping
Module: DFHPD410 any sections affected by the error.
Destination: SYSLST User response: The area may have been corrupted or not set
up correctly. It is also possible that the zero value is valid.
This depends on the circumstances or timing of the dumps
DFHPD0102 Pointer to xxxxxxxx at offset X'offset' is zero. collection; for example, a zero value is valid before the block is
Explanation: A pointer to a block of type xxxxxxxx, whose initialized.
address is at offset offset in the block just formatted, is zero. Module: DFHPD410
System action: Dump formatting continues after skipping Destination: SYSLST
User response: The area may have been corrupted or not set
up correctly. It is also possible that the zero value is valid. DFHPD0105 A loop has been detected. xxxxxxxx at address
This depends on the circumstances or timing of the dumps X'address' already encountered.
collection; for example, a zero value is valid before the block is Explanation: The formatting program avoids loops resulting
initialized. from corrupted control block chains by checking for duplicate
Module: DFHPD410 addresses. The block xxxxxxxx at address address has already
Destination: SYSLST been encountered and may already have been formatted.
DFHPD0103 xxxxxxxx address X'address' is invalid. User response: Check the chain fields in control blocks of the
same type which have already been processed. Otherwise the

DFHPD0106 • DFHPD0117
problem may be caused by the timing of the dumps collection, problem obtain a fresh dump which includes the missing area.
if for example this occurs before the block is initialized. Module: DFHPD410
Module: DFHPD410 Destination: SYSLST
Destination: SYSLST
DFHPD0111I Pointer to xxxxxxxx at offset X'offset' is zero.

DFHPD0106 An error has occurred while formatting Explanation: A pointer to a block of type xxxxxxxx, whose
xxxxxxxx. address is at offset offset in the block just formatted, is zero.
Explanation: An error has occurred during the formatting of System action: Dump formatting continues after skipping
a block of type xxxxxxxx. any sections affected by the zero pointer.
System action: Dump formatting continues after skipping User response: The message is informatory, indicating that
any sections affected by the error. the area was zero at the time the dump was taken.
User response: If no data has been formatted for the block Module: DFHPD410
then the block address was probably invalid. In this case see Destination: SYSLST
message DFHPD0101.
If part of the block has been successfully formatted, it is DFHPD0112I Address of xxxxxxxx is zero.
possible that the length of the control block is incorrect. The Explanation: The address of a block of type xxxxxxxx is zero.
length may have been overwritten which may provide a clue System action: Dump formatting continues after skipping
to the problem. any sections affected by the block.
Module: DFHPD410 User response: The message is informatory, indicating that
Destination: SYSLST the area did not contain an address at the time the dump was
taken.
Module: DFHPD410
DFHPD0107 Eyecatcher for xxxxxxxx at X'address' is Destination: SYSLST
invalid.
Explanation: The eyecatcher field of a control block of type
xxxxxxxx at address address has an incorrect value. DFHPD0113 This block has already been processed.
System action: Dump formatting continues after skipping Explanation: The block whose heading line has just been
any sections affected by the error. printed has already been formatted in this section of the
User response: Investigate why the eyecatcher has been dump.
overwritten or why the control block has not been set up System action: The block is formatted again then any
correctly. For more information on how to solve storage sections which may be impacted by the probable control block
overwrite problems, see the CICS Problem Determination Guide. chain loop are skipped.
Module: DFHPD410 User response: Check the chain fields in the control blocks
Destination: SYSLST processed so far. This may provide a clue to the problem.
Module: DFHPD410
Destination: SYSLST
DFHPD0108 Unable to start browse of xxxxxxxx.
Explanation: An error has occurred when attempting to start
browsing a table of type xxxxxxxx. DFHPD0114 Invalid keyword keyword
System action: Dump formatting continues after skipping Explanation: The keyword keyword is not valid for the
any sections affected by the error. CICS410 verb.
User response: This error may be due to the table manager System action: The keyword is ignored.
program (TMP) control blocks being invalid. Check the TMP User response: Correct the keyword and retry.
control blocks for the table in question. Module: DFHPD410
Module: DFHPD410 Destination: SYSLST
Destination: SYSLST
DFHPD0115 CICS job not found.

DFHPD0109 Unable to get next entry in xxxxxxxx table. Explanation: The dump formatting program searched the
Explanation: An error has occurred when attempting to dump for a CICS job but found none.
access the next entry in a table of type xxxxxxxx. System action: Formatting is terminated. This message is
System action: Dump formatting continues after skipping followed by message DFHPD0120.
any sections affected by the error. User response: Ensure that the dump is the correct one, and
User response: This error may be due to the table manager that the dump contains the necessary data areas. If the dump
program (TMP) control blocks being invalid. Check the TMP was taken very early during CICS initialization there may be
control blocks for the table in question. insufficient control blocks initialized for the dump formatter to
Module: DFHPD410 format the dump.
Destination: SYSLST Module: DFHPD410
Destination: SYSLST
DFHPD0110 Unable to access data for xxxxxxxx
Explanation: The interactive problem control system (IPCS) DFHPD0117 An error has occurred while formatting
service routine ADPLMEMA was unable to find the requested xxxxxxxx.
data for control block xxxxxxxx in the dump. Explanation: An error has occurred during the formatting of
System action: Dump formatting continues after skipping a block of type xxxxxxxx.
any sections impacted by the lack of data.
User response: Either the pointer to the required area was Either the user has attempted to acquire storage, but the
corrupted, which may in itself be a clue to the problem, or the storage has not been referenced. Unreferenced storage may not
address was valid but the area was not present in the dump. be present in the dump.
In the latter case, if the area is essential for diagnosing the

DFHPD0119 • DFHPD0127
Or the block address is invalid, You need further assistance from IBM to resolve this problem.
Or the length of the control block is incorrect. guidance on how to proceed.
System action: Dump formatting continues after skipping Module: DFHPD410
any sections affected by the error. Destination: SYSLST
User response: If no data has been formatted for the block
then either the storage has not been referenced, or the block
address was invalid. If the block address was invalid, refer to DFHPD0124 Storage violation detected at X'address'.
message DFHPD0101. Leading SAA is invalid.
Explanation: The storage accounting area (SAA) in the first
If part of the block has been successfully formatted then it is
eight bytes of the user storage element at address X'address'
possible that the length of the control block is incorrect. The
has been found to be invalid. However, the trailing SAA is
length may have been overwritten which may provide a clue
valid.
to the problem.
Module: DFHPD410
Destination: SYSLST
User response: Investigate why the storage has been
overwritten or has not been set up correctly. For more
DFHPD0119 Duplicate keyword keyword found. Value information on how to solve storage overwrite problems, refer
value accepted to the CICS Problem Determination Guide.
Explanation: The DFHPD410 keyword keyword has already Module: DFHPD410.
been encountered. Destination: SYSLST
System action: The value value specified in the message
overrides any value previously specified for keyword keyword.
DFHPD0125 Storage violation detected at X'address'.
Processing continues with the new value value.
Trailing SAA is invalid.
User response: Remove the duplicate keyword specified on
Explanation: The storage accounting area (SAA) in the first
the VSE Info/Analysis (INFOANA) DATA statement.
eight bytes of the user storage element at address X'address'
Module: DFHPD410
has been found to be invalid. However, the leading SAA is
Destination: SYSLST
valid.
DFHPD0120 CICS dump analyzer exit is terminating. any sections affected by the error.
Explanation: The CICS exit is terminating. User response: Investigate why the storage has been
System action: The exit is returning to the VSE Info/Analysis overwritten or has not been set up correctly. For more
(INFOANA) without performing the requested function. A information on how to solve storage overwrite problems, refer
previous message gives the reason for this. to the CICS Problem Determination Guide.
User response: To determine what action is necessary, refer to Module: DFHPD410.
the message immediately preceding this one on the dump. Destination: SYSLST
Module: DFHPD410
Destination: SYSLST
DFHPD0126 Storage violation detected at X'address'.
Leading and trailing SAAs are invalid.
DFHPD0121I Formatting control blocks for job jobname Explanation: The storage accounting areas (SAAs) in the first
Explanation: This shows the job name for the CICS system and last eight bytes of the user storage element at address
from which the dump was taken. X'address' are invalid.
System action: Processing continues. System action: Dump formatting continues after skipping
User response: None. any sections affected by the error.
Module: DFHPD410 User response: Investigate why the storage has been
Destination: SYSLST overwritten or has not been set up correctly. For more
information on how to solve storage overwrite problems, refer
to the CICS Problem Determination Guide.
DFHPD0122I End of dump for job jobname Module: DFHPD410.
Explanation: This marks the end of the output from the CICS Destination: SYSLST
print dump exit.
System action: None. The formatting job has just completed.
User response: None. DFHPD0127 Storage violation detected at X'address'.
Module: DFHPD410 Leading and trailing SAAs differ.
Destination: SYSLST Explanation: Although the storage accounting areas (SAAs)
in the first and last eight bytes of the user storage element at
address X'address' are valid, they do not match.
DFHPD0123 A program check has occurred while System action: Dump formatting continues after skipping
processing keyword keyword any sections affected by the error.
Explanation: A program check has occurred during User response: Investigate why the storage has been
processing of the keyword identified in the message. overwritten or has not been set up correctly. For more
System action: Dump formatting continues after skipping information on how to solve storage overwrite problems, refer
any sections affected by the error. to the CICS Problem Determination Guide.
Module: DFHPD410.
Note that the maximum possible number of occurrences of Destination: SYSLST
this message is five. If a sixth program check occurs, the
dump formatting program terminates abnormally with user
abend code 212.
User response: A dump accompanies this message.

DFHPD0128 • DFHPG0002
System action: There is only a severe problem when this

DFHPD0128 Invalid data length X'length' specified for
message is followed by message DFHPD0120.
address X'address'.
Explanation: The offline utility DFHPD410 has detected a User response: If this is a severe error. Try to recreate the
request for a block of data of invalid length X'length' while original error and produce a valid system dump against which
formatting a system dump. the dump formatter can be rerun.
System action: Dump formatting usually continues after If the problem recurs, you will need further assistance from
skipping any sections affected by this error. IBM. Collect the sysprint output from the dump formatter and
User response: This message indicates a probable error in
note any relevant messages. See Part 4 of the CICS Problem
CICS code. You need further assistance from IBM to resolve
this problem. See Part 4 of the CICS Problem Determination
Module: DFHPD410
Destination: SYSLST
Module: DFHPD410
Destination: SYSLST
DFHPD0131 CICS job jobname is for CICS version version1.
DFHPD0129 CICS Domain Anchor Blocks not found for CICS INFOANA exit is for CICS version
AFCB. Scan will continue. version2.
Explanation: The dump formatter has attempted to find a Explanation: The CICS job jobname being processed by the
CICS dump in a TCB chain but has failed. The scan continues. dump formatting program was executing under CICS version
This is because DFHPD410 could not find the addresses of the version1, but the INFOANA exit program was the one
CICS domain anchor blocks in the kernel global storage. distributed with CICS version version2.
Possible causes for this are: System action: The dump formatting program terminates.
v Scanning the wrong TCB on the TCB chain. The scan will User response: Retry dump formatting for the CICS job using
continue. the dump formatting program for CICS version version1.
v The kernel global storage being overwritten or freed. Module: DFHPD410
v The dump being taken so early on in CICS initialization that Destination: SYSLST
the kernel global storage has not yet been set up.
DFHPGxxxx messages
DFHPG0001 applid An abend (code aaa/bbbb) has occurred
at offset X'offset' in module modname. If you cannot run without the full use of module modname,
Explanation: An abnormal end (abend) or program check has you should bring CICS down in a controlled shutdown.
an error in the CICS code. Alternatively, unexpected data has You need further assistance from IBM to resolve this problem.
been input, or storage has been overwritten. See Part 4 of the CICS Problem Determination Guide for
The code aaa/bbbb is a 3-digit hexadecimal VSE code (if Module: DFHPGAI, DFHPGAQ, DFHPGDD, DFHPGDM,
applicable), followed by a 4-digit alphanumeric CICS code. DFHPGEX, DFHPGHM, DFHPGIS, DFHPGLD, DFHPGLK,
The VSE code is a system completion code, for example 0C1. DFHPGLU, DFHPGPG, DFHPGRP, DFHPGST, DFHPGXM.
hyphens. The CICS code is an abend code or a number XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
referring to a CICS message (for example, AKEA is a CICS Destination: Console
DFHPG0002 applid A severe error (code X'code') has
CICS continues unless you have specified in the dump table The code X'code' is the exception trace point ID which
that CICS should terminate. If appropriate, an error return uniquely identifies what the error is and where the error was
code is sent to the caller of this domain. In this case CICS detected.
could be terminated by the caller ( for example, the domain System action: An exception entry (code X'code' in the
manager, DFHDMDM). A message is issued to this effect. message) is made in the trace table. A system dump is taken,
Message DFHME0116 is normally produced containing the table.
User response: Notify the system programmer. If CICS is still CICS continues unless you have specified in the dump table
running, it is necessary to decide whether to terminate CICS. that CICS should terminate. If appropriate, an error return
Look up the VSE code, if there is one, in "OS/390 API Abend could be terminated by the caller (for example, the domain
Codes" in section "VSE/Advanced Functions Codes & SVC manager, DFHDMDM). A message is issued to this effect.
Errors" of z/VSE Messages and Codes - Volume 1.
Next, look up the CICS alphanumeric code in “Transaction symptom string for this problem.
Abend Codes (CICS Transaction Server for VSE/ESA)” on User response: This indicates a possible error in CICS code.
page 453. This tells you, for example, whether the error was a The severity of its impact depends on the importance of the
program check, an abend, or a runaway, and may give you function being executed at the time of the error.
CICS may not have been terminated. If the message occurs
If module modname is not crucial to the running of your CICS once and module modname is not crucial to the running of
system, you may decide to continue to run and bring CICS your CICS system, you may decide to continue to run and

DFHPG0004 • DFHPG0103
bring CICS down at a convenient time to resolve the problem.

DFHPG0101 date time applid terminal userid tranid PPT entry
If the message recurs or if you cannot run without the full use for progname has been added.
of module modname, you should bring CICS down in a Explanation: This is an audit log message indicating that
controlled shutdown. program entry progname has been added to the PPT using the
CEDA INSTALL or EXEC CICS CREATE command. Where:
You need further assistance from IBM to resolve this problem. v terminal is the netname or termid of the terminal associated
See Part 4 of the CICS Problem Determination Guide for with the transaction issuing the message. If there is no
guidance on how to proceed. terminal associated with the transaction, the terminal name
Module: DFHPGAI, DFHPGAQ, DFHPGDD, DFHPGDM, is suppressed.
DFHPGEX, DFHPGHM, DFHPGIS, DFHPGLD, DFHPGLK, v userid is the identifier of the user associated with the
DFHPGLU, DFHPGPG, DFHPGRP, DFHPGST, DFHPGXM.
transaction issuing the message.
XMEOUT Parameters: applid, X'code',modname v tranid is the transaction issuing the message.
Destination: Console System action: The system continues normally.
Module: DFHPGDD
DFHPG0004 applid A possible loop has been detected at
offset X'offset' in module modname. XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
Explanation: A CICS function is taking more time to process progname
than CICS expects. A possible loop has been detected in Destination: CSPL
detected. DFHPG0102 date time applid terminal userid tranid PPT entry
System action: An exception entry is made in the trace table. for progname has been deleted.
A system dump is taken, unless you have specifically Explanation: This is an audit log message indicating that
suppressed dumps in the dump table. program entry progname has been deleted from the PPT using
the CEMT or EXEC CICS DISCARD command. command.
CICS continues unless you have specified in the dump table Where:
v terminal is the netname or termid of the terminal associated
code is sent to the caller of this domain. In this case CICS
with the transaction issuing the message. If there is no
could be terminated by the caller ( for example, the domain
terminal associated with the transaction, the terminal name
manager, DFHDMDM). A message is issued to this effect.
is suppressed.
Message DFHME0116 is normally produced containing the v userid is the user identifier of the user associated with the
symptom string for this problem. transaction issuing the message.
User response: Notify the system programmer. If CICS has v tranid is the transaction issuing the message.
not been terminated, it is necessary to decide whether the System action: The system continues normally.
problem is serious enough to bring CICS down. User response: None.
Module: DFHPGDD
message may have been caused by a long-running function. So XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
there may not be an error here. Usually, CICS purges a CICS progname
function which exceeds the runaway task time interval which Destination: CSPL
that module modname in the message is terminated and CICS DFHPG0103 date time applid terminal userid tranid PPT entry
continues. for progname has been replaced.
If you have declared ICVR=0 and you consider that module Explanation: This is an audit log message indicating that
modname has gone into a loop, you need to terminate CICS in program entry progname has been replaced in the PPT using
order to terminate the runaway function. the CEDA INSTALL or EXEC CICS CREATE command.
Where:
If CICS has terminated module modname, and you consider v terminal is the netname or termid of the terminal associated
that it was not a runaway, you should increase the ICVR time with the transaction issuing the message. If there is no
interval. You have to bring CICS down at a suitable time to do terminal associated with the transaction, the terminal name
this permanently. But you can change the ICVR time interval is suppressed.
temporarily online, using the CEMT transaction. v userid is the identifier of the user associated with the
If raising the ICVR time does not solve the problem, you will transaction issuing the message.
need further assistance from IBM. See Part 4 of the CICS v tranid is the transaction issuing the message.
Problem Determination Guide for guidance on how to proceed. System action: The system continues normally.
Module: DFHPGAI, DFHPGAQ, DFHPGDD, DFHPGDM, User response: None.
DFHPGEX, DFHPGHM, DFHPGIS, DFHPGLD, DFHPGLK, Module: DFHPGDD
DFHPGLU, DFHPGPG, DFHPGRP, DFHPGST, DFHPGXM.
XMEOUT Parameters: applid, X'offset', modname progname
Destination: Console Destination: CSPL

and EIBRESP2 is set to indicate the cause of the error. The

DFHPG0104 date time applid Program progname is defined
autoinstall function is disabled.
with DATALOCATION(ANY) but is
linkedited with AMODE(24). User response: Continue processing without program
Explanation: Program entry progname has been loaded. It is autoinstall or correct the error in the autoinstall exit program
defined (using RDO or by program autoinstall) with and reenable the autoinstall function using CEMT SET
DATALOCATION(ANY), but was linkedited with AUTOINSTALL command.
AMODE(24). Addresses returned to the program by EXEC Module: DFHPGAI
CICS commands using the SET option may be above the
16MB line and not accessible by the AMODE(24) program.
urmname, abcode
The definition is accepted as the program can pass the storage Destination: CSPL
on to another program which is linkedited with AMODE(31).
See the description of DATALOCATION in the CICS Resource
Definition Guide. DFHPG0203 date time applid terminal userid tranid Program
autoinstall exit urmname failed, reason: reason.
This message is issued the first time the program is loaded, The program autoinstall function has been
linked to or XCTLed to, after being defined. disabled.
System action: The system continues normally. Explanation: An attempt has been made to autoinstall a
User response: None. program during link, XCTL, load, or exit processing but the
Module: DFHPGLD, DFHPGLE, DFHPGLK, DFHPGLU, program autoinstall exit program is incorrectly defined or
DFHPGPG, DFHPGXE, DFHPGEX cannot be found on the load libraries. Where:
XMEOUT Parameters: date, time,applid, progname v terminal is the netname or termid of the terminal associated
Destination: CSPL with the transaction issuing the message. If there is no
is suppressed.
DFHPG0201 date time applid terminal userid tranid Program v userid is the identifier of the user associated with the
autoinstall exit urmname indicated that transaction issuing the message.
program progname should not be added to the v tranid is the transaction issuing the message.
PPT. v reason is one of the following:
Explanation: An attempt has been made to autoinstall a – Program not defined
program during link, XCTL, load or exit processing but the
– Program not enabled
autoinstall exit set a return code indicating that the program
– Program not loadable
should not be installed. Where:
– Remote program
– AMODE error
– Invalid COMMAREA
– Recursion in autoinstall exit.
is suppressed.
System action: Control is returned to the caller with an error
v userid is the identifier of the user associated with the
response. For EXEC CICS commands, EIBRESP is set to
PGMIDERR and EIBRESP2 is set to indicate the cause of the
v tranid is the transaction issuing the message.
error. The autoinstall function is disabled.
User response: Continue processing without program
response. For EXEC commands, EIBRESP is set to PGMIDERR
autoinstall or correct the problem and reenable the autoinstall
and EIBRESP2 is set to indicate the cause of the error.
function using the CEMT transaction or the SPI command.
User response: None
Take the appropriate action to correct the problem:
Module: DFHPGAI
Program not defined
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, Install the autoinstall exit program.
urmname, progname Program not enabled
Destination: CSPL Reset the status of the autoinstall exit program.
Program not loadable
Ensure that the autoinstall exit program is in the
DFHPG0202 date time applid terminal userid tranid Program load libraries.
autoinstall exit urmname has abended with Remote program
code abcode. The program autoinstall function Ensure that the autoinstall exit program is defined
has been disabled. as a local program.
Explanation: An attempt has been made to autoinstall a AMODE error
program during link, XCTL, load or exit processing but the Ensure that the autoinstall exit program is AMODE
program autoinstall exit program abended with code abcode. 31.
Where: Invalid COMMAREA
v terminal is the netname or termid of the terminal associated Ensure that if the program autoinstall exit program
with the transaction issuing the message. If there is no passes the COMMAREA to another program, the
terminal associated with the transaction, the terminal name COMMAREA is correctly passed.
is suppressed. Recursion in autoinstall exit
v userid is the user identifier of the user associated with the The autoinstall user-replaceable module has
transaction issuing the message. attempted to link to XCTL or to load another
v tranid is the transaction issuing the message. program which is not defined. Autoinstall cannot be
System action: Control is returned to the caller with an error attempted with the autoinstall exit. Ensure that the
response. For EXEC commands, EIBRESP is set to PGMIDERR program being referred to is defined using RDO.
Module: DFHPGAI


DFHPG0206 date time applid terminal userid tranid
urmname, reason
Autoinstall for program progname failed.
Destination: CSPL
Programs starting with 'DFH' cannot be
defined as remote programs.
DFHPG0204 date time applid terminal userid tranid Explanation: An attempt has been made to autoinstall a
Autoinstall for program progname failed. program during link, XCTL, load, or exit processing with
Program autoinstall model modelname is not remote attributes but the program starts with the characters
defined. 'DFH'. Where:
Explanation: An attempt has been made to autoinstall a v terminal is the netname or termid of the terminal associated
program during link, XCTL, load or exit processing but the with the transaction issuing the message. If there is no
model selected for the autoinstall is not defined. Where: terminal associated with the transaction, the terminal name
v terminal is the netname or termid of the terminal associated is suppressed.
with the transaction issuing the message. If there is no v userid is the identifier of the user associated with the
terminal associated with the transaction, the terminal name transaction issuing the message.
is suppressed. v tranid is the transaction issuing the message.
v userid is the user identifier of the user associated with the System action: Control is returned to the caller with an error
transaction issuing the message. response. For EXEC CICS commands, EIBRESP is set to
v tranid is the transaction issuing the message. PGMIDERR and EIBRESP2 is set to indicate the cause of the
System action: Control is returned to the caller with an error error.
response. For EXEC CICS commands, EIBRESP is set to User response: Ensure that the autoinstall model program
PGMIDERR and EIBRESP2 is set to indicate the cause of the selected for programs starting 'DFH' is defined as a local
error. program and that no remote attributes are specified by the
User response: Ensure that all programs to be used as program autoinstall exit program.
models for the autoinstall function have been defined. Module: DFHPGAI
Module: DFHPGAI
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, progname
progname, modelname Destination: CSPL
Destination: CSPL
DFHPG0207 date time applid terminal userid tranid
DFHPG0205 date time applid terminal userid tranid Invalid Autoinstall for program progname failed. The
value: value returned by program autoinstall program name is not valid.
exit urmname for field fieldname. Explanation: An attempt has been made to autoinstall a
Explanation: An attempt has been made to autoinstall a program during link, XCTL, load or exit processing but the
program during link, XCTL, load, or exit processing but the program name includes invalid characters. Where:
program autoinstall exit returned an invalid value for a v terminal is the netname or termid of the terminal associated
program definition field or the return code via the commarea. with the transaction issuing the message. If there is no
Where: terminal associated with the transaction, the terminal name
v terminal is the netname or termid of the terminal associated is suppressed.
with the transaction issuing the message. If there is no v userid is the identifier of the user associated with the
terminal associated with the transaction, the terminal name transaction issuing the message.
is suppressed. v tranid is the transaction issuing the message.
v userid is the identifier of the user associated with the System action: Control is returned to the caller with an error
transaction issuing the message. response. For EXEC CICS commands, EIBRESP is set to
v tranid is the transaction issuing the message. PGMIDERR and EIBRESP2 is set to indicate the cause of the
v value is the returned value. This may be invalid or there error.
may be a conflict between the load attribute specified and User response: Ensure that the program name is valid.
the load type of the model program. If the program type is Module: DFHPGAI
shared, the load attribute must be resident. XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
System action: Control is returned to the caller with an error progname
response. For EXEC CICS commands, EIBRESP is set to Destination: CSPL
PGMIDERR and EIBRESP2 is set to indicate the cause of the
error.
User response: Ensure that the data returned by the DFHPG0208 date time applid terminal userid tranid
autoinstall exit program is correct. Autoinstall for program progname failed.
Module: DFHPGAI Explanation: An attempt has been made to autoinstall a
program during link, XCTL, load, or exit processing but the
install of the definition failed. Either the AMODE/RMODE
value, urmname, fieldname
combination is invalid or the load attribute and type
Destination: CSPL
combination is invalid. Where:
is suppressed.
v userid is the user identifier of the user associated with the

DFHPG0209 • DFHPR0104I
v tranid is the transaction issuing the message. Where:

System action: Control is returned to the caller with an error v terminal is the netname or termid of the terminal associated
response. For EXEC CICS commands, EIBRESP is set to with the transaction issuing the message. If there is no
PGMIDERR and EIBRESP2 is set to indicate the cause of the terminal associated with the transaction, the terminal name
error. is suppressed.
User response: Ensure the AMODE and RMODE are v userid is the identifier of the user associated with the
compatible and the program attribute is specified as resident if transaction issuing the message.
the program type is shared. v tranid is the transaction issuing the message.
Module: DFHPGAI System action: The system continues normally.
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, Module: DFHPGAI
progname
Destination: CSPL XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
progname
Destination: CSPL
for progname has been autoinstalled using
model modelname. DFHPG0211 date time applid terminal userid tranid
Explanation: This is an audit log message indicating that Autoinstall for program progname failed.
program entry progname has been added to the PPT by the Program autoinstall model modelname is
AUTOINSTALL function using the model modelname. disabled.
Explanation: An attempt has been made to autoinstall a
Where:
program during link, XCTL, load or exit processing but the
v terminal is the netname or termid of the terminal associated model selected for the autoinstall is disabled. Where:
terminal associated with the transaction, the terminal name with the transaction issuing the message. If there is no
is suppressed.
v userid is the identifier of the user associated with the is suppressed.
transaction issuing the message. v userid is the identifier of the user associated with the
v tranid is the transaction issuing the message. transaction issuing the message.
System action: The system continues normally. v tranid is the transaction issuing the message.
Module: DFHPGAI response. For EXEC CICS commands, EIBRESP is set to
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, PGMIDERR and EIBRESP2 is set to indicate the cause of the
progname, modelname error.
Destination: CSPL User response: Ensure that all programs to be used as
models for the autoinstall function are enabled.
Module: DFHPGAI
for progname has been system autoinstalled. XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
Explanation: This is an audit log message indicating that progname, modelname
program entry progname has been added to the PPT by the Destination: CSPL
system AUTOINSTALL function.
DFHPRxxxx messages
DFHPR0101I date time applid The table entry for partner DFHPR0103I date time applid The table entry for partner
ptnrname has been replaced. ptnrname has been deleted.
Explanation: This is an informational message indicating that Explanation: This is an informational message indicating that
the partner resource manager has replaced the existing table the partner resource manager has deleted the table entry for
entry for the partner ptnrname, with a new table entry. the ptnrname partner.
System action: The system continues normally. System action: The system continues normally.
Module: DFHPRPT Module: DFHPRPT
XMEOUT Parameters: date, time,applid, ptnrname XMEOUT Parameters: date, time,applid, ptnrname
Destination: CSRL Destination: CSRL
DFHPR0102I date time applid The table entry for partner DFHPR0104I applid Partner resource manager initialization
ptnrname has been added. has started.
Explanation: The partner resource manager has added a new Explanation: Partner resource manager initialization has
table entry for the partner ptnrname. started.
System action: The system continues normally. System action: Initialization continues.
Module: DFHPRPT Module: DFHPRIN1
XMEOUT Parameters: date, time,applid, ptnrname XMEOUT Parameter: applid
Destination: CSRL Destination: Console

DFHPR0105I • DFHRC5366
System action: Message DFHSI1522 is issued following this

DFHPR0105I applid Partner resource manager initialization
message. CICS terminates or continues initialization
has ended.
depending upon the operator's response to message
Explanation: Partner resource manager initialization has
DFHSI1522. An exception trace entry is written at the time the
completed successfully.
failure is detected. Other CICS components called by the
partner resource manager initialization process may also issue
messages or write trace entries.
SIT parameter, MSGLVL=0.
User response: Decide whether CICS can continue execution
Module: DFHPRIN1
without the partner resource manager, and respond
XMEOUT Parameter: applid accordingly to message DFHSI1522. You should also
Destination: Console investigate why the partner resource manager failed to
initialize, starting from the data contained in the exception
trace entry.
DFHPR0106I applid Partner resource manager initialization Module: DFHPRIN1
has failed.
Explanation: The partner resource manager has failed to XMEOUT Parameter: applid
initialize successfully. Destination: Console
DFHRCxxxx messages
VSE/POWER by executing an EXEC CICS START
DFHRC5301 applid FAILED TO INITIALIZE POWER
TRANSID(CXPB) command.
INTERFACE.
Explanation: An attempt to open a NOTIFY path to POWER If these attempts to re-establish the connection fail, you have
was unsuccessful. to restart CICS to re-establish the VSE/POWER connection.
System action: System spooling initialization cannot Module: DFHCXPB
continue.
User response: Ensure that the POWER program is available XMEOUT Parameters: applid, X'return_code'
and working. If there is more than one CICS system running, Destination: Console
investigate the names used by POWER to identify these
systems. These names have the form SYSCICx, where x is
DFHRC5312I applid CXPB is terminating because abend
specified on the SPOOL system initialization parameter. x
code abend_code has been detected
defaults to "A". Ensure that the value of x is different for each
Explanation: Transaction CXPB has detected an abend code
CICS system that is running with POWER.
of abend_code
Module: DFHCXPA
System action: A transaction dump with abend code APTQ
XMEOUT Parameter: applid will be issued. CICS continues but Report Controller printers
Destination: Console will no longer be able to be started. This is because the CXPB
transaction is the CICS interface to which VSE/POWER passes
start requests.
DFHRC5302 applid AUDIT LOG CSMT IS FULL, User response: Use the resulting dump to analyze why the
LOGGING DISCONTINUED. abend code has been issued. After taking any necessary action,
Explanation: An attempt has been made by CEMS or CEOS you should then re-establish the connection between CICS and
to write to the audit file CSMT. This has caused the NOSPACE POWER by entering option 5 of the CICS Supplied
condition to be raised. Transaction CEMS. For guidance on using CEMS refer to the
System action: Logging to CSMT is discontinued. CICS Report Controller User's Guide.
User response: Auditing to CSMT continues after this file has
been processed and emptied. Depending on the nature of the problem, it may also be
Module: DFHCXPA possible to restart the connection between CICS and
VSE/POWER by executing an EXEC CICS START
XMEOUT Parameter: applid TRANSID(CXPB) command.
If these attempts to re-establish the connection fail, you will
have to restart CICS to re-establish the VSE/POWER
DFHRC5311I applid CXPB is terminating because a return connection.
code of X'return_code' has been received from Module: DFHCXPB
an OPEN,ANY request
Explanation: Transaction CXPB has received a return code of XMEOUT Parameters: applid, abend_code
return_code from the OPEN,ANY request. Destination: Console
System action: A transaction dump with abend code APTP
will be issued. CICS continues but Report Controller printers DFHRC5366 applid System spooling interface initialization
will no longer be able to be started. This is because the CXPB program DFHPSIP not present.
transaction is the CICS interface to which VSE/POWER passes Explanation: CICS attempted to link to DFHPSIP but the
start requests. attempt failed because DFHPSIP was not in a sublibrary of the
User response: Use the resulting dump to analyze why the LIBDEF search chain for the CICS startup job stream.
return code has been passed back to CXPB. After taking any System action: CICS terminates the system spooler
necessary action, you should then re-establish the connection initialization.
between CICS Supplied Transaction CEMS. For guidance on User response: Place DFHPSIP in a sublibrary of the LIBDEF
using CEMS refer to the CICS Report Controller User's Guide. search chain for the CICS job.
Depending on the nature of the problem, it may also be Module: DFHPSBP
possible to restart the connection between CICS and

DFHRC5440 • DFHRC5461
DFHRC5440 operid tranid yy.ddd hh.mm.ss REPORT reportid DFHRC5458 date time applid TASK taskno TERMINAL
CHANGED xxxxxxxxxxxxxxxxxxxx. termid - REPORT reportid at DESTINATION
Explanation: A report characteristic has been changed using destid is not printable. Report is now held.
CEOS or CEMS. time date
System action: Create an audit record describing the change. Explanation: An attempt has been made to print a report
User response: None. whose format is not manageable by the CICS report controller
Module: DFHEMSRE writer task (CEPW).
Destination: CSPA System action: The report is rejected by the report controller
writer task and held with a POWER Disposition of "Y"
(ERRPRT).
DFHRC5441 AUDIT LOG CSPA IS FULL, NOW User response: Check with the operating system controller to
LOGGING TO CSMT. get the report rescheduled for printing at a suitable printer not
Explanation: An attempt has been made by CEOS/CEMS to controlled by the report controller writer task.
write to the audit file CSPA causing the NOSPACE condition Module: DFHPSOP
to be raised. Destination: CSPW
System action: An attempt is made to write the record to
CSMT and this warning message is sent to the operator
console. Auditing to CSPA continues after the file has been DFHRC5459 date time applid TASK taskno TERMINAL
processed and emptied. termid - REPORT reportid is not format
User response: None. compatible with device at DESTINATION
Module: DFHEMSRE destid. Report is now held.
Destination: Console Explanation: An attempt has been made to print a report
whose format is not manageable by the CICS report controller
writer task (CEPW). For example, an attempt has been made
DFHRC5443 operid tranid yy.ddd hh.mm.ss PRINTER reportid to print a T3270 NOCONV report on an SCS printer, or an
CHANGED xxxxxxxxxxxxxxxxxxxx. SCS NOCONV report on a 3270 printer.
Explanation: A printer characteristic has been changed using System action: The report is rejected by the report controller
CEOS or CEMS. writer task and held with a POWER Disposition of "Y"
System action: Create an audit record describing the change. (ERRPRT).
User response: None. User response: Reschedule the report to print on a device
Module: DFHEMSPR whose format is compatible with report.
Destination: CSPA Module: DFHPSOP
Destination: CSPW
DFHRC5444 AUDIT LOG CSPA IS FULL, NOW
LOGGING TO CSMT. DFHRC5460 date time applid TASK taskno TERMINAL
Explanation: An attempt has been made by CEOS/CEMS to termid - REPORT reportid AT DESTINATION
write to the audit file CSPA causing the NOSPACE condition destid requires FORMS formid to be loaded.
to be raised. Ensure that the line counter is correctly set
System action: An attempt is made to write the record to for the new stationary.
CSMT and this warning message is sent to the operator Explanation: The report controller writer task has detected
console. Auditing to CSPA continues after the file has been that a Forms Change is required to print the next report on
processed and emptied. the printer.
User response: None. System action: The writer task awaits confirmation that the
Module: DFHEMSPR forms change is complete.
Destination: Console User response: Mount the requested stationary on the
printer, and change the line counter to the appropriate value.
Then resume the printer using the CEMS/CEOS Printer
DFHRC5446 operid tranid yy.ddd hh.mm.ss REPORT reportid
Operator commands.
CHANGED xxxxxxxxxxxxxxxxxxxx.
Module: DFHPSOP
Explanation: A report characteristic has been changed using
Destination: CSPW
CEOS or CEMS.
System action: Create an audit record describing the change.
User response: None. DFHRC5461 date time applid TASK taskno TERMINAL
Module: DFHEMSJB termid LINEUP REQUEST FOR REPORT
Destination: CSPA reportid at DESTINATION destid is not format
compatible. Request rejected.
Explanation: A lineup request was made for a report of
DFHRC5447 AUDIT LOG CSPA IS FULL, NOW
format not supported for lineups.
LOGGING TO CSMT.
System action: Lineups will not be produced for this report.
Explanation: An attempt has been made by CEOS/CEMS to
User response: Resume the printer using the CEMS/CEOS
write to the audit file CSPA causing the NOSPACE condition
Printer Operator commands.
to be raised.
Module: DFHPSOP
System action: An attempt is made to write the record to
Destination: CSPW
CSMT and this warning message is sent to the operator
console. Auditing to CSPA continues after the file has been
processed and emptied.
Module: DFHEMSJB

DFHRC5462 date time applid TASK taskno TERMINAL DFHRC5467 date time applid TASK taskno TERMINAL
termid - forms load request for report reportid termid - ESCAPE PROGRAM progid
at DESTINATION destid has been fulfilled. RESPONSE: RETURN CODE = X'nn' TEXT =
Explanation: The report controller writer task is confirming xxxxxxxxxxxxxxxxxxxx. REPORT reportid AT
that it has received a Resume Printing command, after a DESTINATION destid IS NOW HELD.
previous Form Load request. Explanation: The named escape program returned a non-zero
System action: The Writer Task will now start printing the return code.
named report. System action: The report is rejected by the report controller
User response: None. writer task (CEPW) and held with a POWER Disposition of
Module: DFHPSOP "Y" (ERRPRT).
Destination: CSPW User response: The return code and text are supplied by the
escape program. Use them to diagnose and rectify the problem
before rescheduling the report for printing.
DFHRC5463 date time applid TASK taskno TERMINAL Module: DFHPSOP
termid - REPORT reportid at DESTINATION
destid has started printing. XMEOUT Parameters: date, time,applid, taskno, termid, progid,
Explanation: The report controller writer is notifying the date X'nn', xxxxxxxxxxxxxxxxxxxx, reportid, destid
and time that it started printing the named report. Destination: CSPW
System action: The Writer Task will continue printing the
named report.
User response: None. DFHRC5468 date time applid TASK taskno TERMINAL
Module: DFHPSOP termid - A severe interrupt on the device at
Destination: CSPA DESTINATION destid has caused the printer
task to terminate. (REPORT reportid was
being printed).
DFHRC5464 date time applid TASK taskno TERMINAL Explanation: A severe interruption has occurred while
termid - REPORT reportid AT DESTINATION printing on the named device.
destid has finished printing. System action: Communications with POWER are broken.
Explanation: The report controller writer is notifying the date The writer task is terminated with an abend code of APSM or
and time that it finished printing the named report. APSN. In the case of abend code APSM, the printer will also
System action: The Writer Task will process the next be set out of service. The status of the report depends on the
available report. PRINTFAIL option and the original POWER disposition.
User response: None. User response: Rectify the reason for the interrupt and restart
Module: DFHPSOP the printer.
Destination: CSPA Module: DFHPSOP
Destination: CSPW
DFHRC5465 date time applid TASK taskno TERMINAL

termid - REPORT reportid at DESTINATION DFHRC5469 date time applid TASK taskno TERMINAL
destid had a mapping failure, for MAP mapid termid - An interrupt on the device at
within MAPSET mapsetname. Report is now DESTINATION destid has caused the printer
held. task to pause.
Explanation: While printing a MAP format report, CICS Explanation: A printing interruption on the named device
returned an error response from a SEND MAP command, or has caused the CICS writer task to pause until the interruption
attempted to abend the report controller writer task (CEPW). is cleared.
System action: The report is rejected by the report controller System action: The writer task will wait in a paused state.
writer task (CEPW) and held with a POWER Disposition of User response: Rectify the reason for the interrupt and
"Y" (ERRPRT). resume the printer using CEMS/CEOS.
User response: Reschedule the report to be reprinted while Module: DFHPSOP
CICS auxiliary trace is running. After attempting to print the Destination: CSPW
report, close and print the auxiliary trace file. Then find the
last SEND MAP entry for the failed task within the trace to
deduce the reason for the failure. DFHRC5470 date time applid TASK taskno TERMINAL
Module: DFHPSOP termid - Request to facilitate the device at
Destination: CSPW DESTINATION destid for system spooling
has been rejected. The CICS Report
Controller is not activated or is quiescing.
DFHRC5466 date time applid TASK taskno TERMINAL Explanation: A request has been made to the operating
termid - ESCAPE PROGRAM progid could not system spooler to use a CICS terminal as a surrogate printer,
be located for the ESC report reportid at but either the report controller has not been activated, or it is
DESTINATION destid. Report is now held. quiescing as part of CICS shutdown.
Explanation: The link to the named escape program has System action: The writer task will detect the system status
failed. and close itself down.
System action: The report is rejected by the report controller User response: Retry the request to start the printer after
writer task and held with a POWER Disposition of "Y" CICS has been reinitialized.
(ERRPRT). Module: DFHPSOP
User response: Obtain a CICS auxiliary trace to determine Destination: CSPW
the reason for the link failure. The report may be rescheduled
for printing after the problem has been rectified.
Module: DFHPSOP
Destination: CSPW

DFHRC5471 date time applid TASK taskno TERMINAL DFHRC5482 applid Report Controller waiting for POWER
termid - ESCAPE REPORT reportid at connection.
DESTINATION destid has had an error while Explanation: During systems initialization the report
building the report for data transmission. controller received no response from POWER to the NOTIFY
The report is now held. PATH CONNECTION.
Explanation: While building an escape format report, CICS System action: The system waits for 30 seconds before
returned an error response from a WRITEQ TS command. reissuing the message.
System action: The report is rejected by the report controller User response: Check that POWER is available.
writer task (CEPW) and held with a POWER Disposition of Module: DFHPSPIO
"Y" (ERRPRT).
User response: Reschedule the report to be reprinted while XMEOUT Parameter: applid
CICS auxiliary trace is running. After attempting to print the Destination: Console
report, close and print the auxiliary trace file. Then find the
last WRITEQ TS entry for the failed task within the trace to DFHRC5483 date time applid TASK taskno TERMINAL
deduce the reason for the failure. termid - this terminal is not authorized to
Module: DFHPSOP print REPORT reportid. The report is now
Destination: CSPW held.
Explanation: An attempt has been made to print a report
DFHRC5478 SETUP COMPLETE. with an RSL which the selected printer is not authorized to
Explanation: The operator requested forms setup on a access.
printer, and the setup process is now complete. System action: The report is rejected by the report controller
System action: The writer task waits for operator action. writer task (CEPW) and held with a POWER Disposition of
User response: The operator should issue a PGO command "Y" (ERRPRT).
to resume printing, or a PSETUP command to redo the setup. User response: Change the DESTINATION and CLASS of the
Module: DFHPSPIO report to match those of an authorized printer and then
Destination: Console request it to be printed again.
Module: DFHPSOP
Destination: CSPW
DFHRC5479 SETUP PRINTER printerid WITH FORMS
formid.
Explanation: The report controller writer task (CEPW) has DFHRC5484 date time applid TASK taskno TERMINAL
detected that a change of forms formid is required on printer termid - this terminal has received an
printerid. immediate stop request while printing
System action: The writer task waits for a PGO or PSETUP REPORT reportid. The report is now held.
command. Explanation: Printing of the report has been prematurely
User response: The operator should issue a PGO or PSETUP terminated due to an operator stop request.
command after changing the forms in the printer. System action: The report is rejected by the report controller
Module: DFHPSPIO writer task (CEPW) and held with a POWER Disposition of
Destination: Console "Y" (ERRPRT).
User response: The report may be rescheduled for printing
on an available printer.
DFHRC5480 applid Report Controller recovery failed for Module: DFHPSOP
REPORT - reportid. Destination: CSPW
Explanation: During emergency restart, the report controller
was unable to open the named report.
System action: The report is skipped. DFHRC5485 date time applid TASK taskno TERMINAL
User response: None. termid - this terminal, serving DESTINATION
Module: DFHPSBP destid has been stopped.
Explanation: The printer has been stopped due to an
XMEOUT Parameters: applid, reportid operator request.
Destination: Console System action: The printer is stopped.
User response: No further reports will be printed by this
printer until the operator requests the printer be started.
DFHRC5481 applid Report Controller backout program - Module: DFHPSOP
DFHPSBP - missing. Destination: CSPW
Explanation: During emergency restart, the report controller
was unable to load the backout program.
System action: The report recovery is skipped. DFHRC5486 applid AUDIT LOG CPSA/CSPW IS FULL,
User response: Ensure a sublibrary of the LIBDEF search NOW LOGGING TO CSMT.
chain for the CICS startup job stream contains DFHPSBP. Explanation: An attempt has been made by CEPW to write
Module: DFHPSP to the audit log CSPA or CSPW, causing the NOSPACE
condition to be raised.
XMEOUT Parameter: applid System action: An attempt is made to write the record to
Destination: Console CSMT and this warning message is sent to the operator
console. Auditing to CSPA or CSPW continues after the file
has been processed and emptied.
Module: DFHPSOP

DFHRC5487 • DFHRD0102
System action: Transaction CEMS or CEOS returns to CICS.

User response: Check whether module is in the PPT and in
termid - ERROR CODE X'nn' occurred whilst
the group DFHRCF. If it is not, the RCF is probably incorrectly
attempting to send data to this device.
installed for the specified national language. See the CICS
Explanation: Whilst attempting to print to the named
System Definition Guide for more information.
terminal an error occurred which caused the Report Controller
Module: DFHEMS00
NEP to be driven.
System action: If the error is not severe, then the printer is
placed into a PAUSED status. If the error is severe, then the
writer task will be abended and the terminal may be forced DFHRC5491 date time applid TASK taskno TERMINAL
out of service. termid - this terminal, serving DESTINATION
User response: The error code is that at offset '8' in the destid has been started.
Terminal Abnormal Condition Line Entry (TACLE). For an Explanation: The printer at destination destid has been
explanation of the possible values of this code, see the TACLE successfully started by the operator request at terminal termid
description in the CICS Data Areas. For non-severe errors, the for task taskno.
CEMS/CEOS operator may request that printing be resumed. System action: The printer is ready to process reports for
Module: DFHPSOP task taskno.
Destination: CSPW User response: None.
Module: DFHPSOP
Destination: CSPW
termid - load of FCB phasename for REPORT
reportid at DESTINATION destid failed. The DFHRC5492 date time applid TASK taskno TERMINAL
report will be printed using the default FCB. termid - this terminal, serving DESTINATION
Explanation: The report to be printed was to be formatted destid has been released due to time-out.
according to the channel specification in the named FCB Explanation: The printer at destination destid has been
phase. This phase could not be loaded. released by task taskno because the SPOOLPRTTO time-out
System action: The report is printed using the default FCB. period has expired.
User response: Determine why the FCB phase could not be System action: The printer is released by task taskno and is
loaded and correct the fault. now available for other tasks. If more work becomes available
Module: DFHPSOP for the printer, it is restarted automatically as soon as it
Destination: CSPW becomes free.
User response: If the printer is being timed-out too often
consider increasing the value specified for SPOOLPRTTO on
the associated RDO TERMINAL definition. See the CICS
termid - an error occurred switching EPC on/off
Resource Definition Guide for more information about setting
the architected capability is now disabled.
the printer time-out period.
Explanation: The printer has the early print complete (EPC)
Module: DFHPSOP
feature installed but when attempting to turn the capability
Destination: CSPW
ON or OFF, CICS detected an error condition.
System action: The RCF print task continues using the
printer without EPC. DFHRC5493 date time applid TASK taskno TERMINAL
User response: Determine the cause of the error and remedy. termid - truncation of records for REPORT
Module: DFHPSOP reportid at DESTINATION destid has occurred.
Destination: CSPW Explanation: Records have been truncated for report reportid
at destination destid because the printer buffer capacity was
exceeded.
DFHRC5490 applid UNABLE TO LOAD RCF MESSAGE
System action: The report is printed but during formatting it
MODULE module
may have been corrupted.
Explanation: CEMS or CEOS failed to load the report
User response: Ensure the spool records never exceed the
controller (RCF) message module module. module takes the
buffer capacity of the printer, or its carriage width if the report
form DFHPSEx, where x specifies the national language in use
is formatted.
when RCF was invoked. For example "E" specifies English, "K"
Module: DFHPSOP
specifies Kanji, "G" specifies German and "C" specifies
Destination: CSPW
Chinese.
DFHRDxxxx messages
DFHRD0101 date time applid terminal userid tranid INSTALL DFHRD0102 date time applid terminal userid tranid INSTALL
PROGRAM(progname) MAPSET(mapsetid)
Explanation: Program progname has been installed into CICS Explanation: Mapset mapsetid has been installed into CICS by
by user userid at terminal terminal using transaction tranid. user userid at terminal terminal using transaction tranid.
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
progname mapsetid
Destination: CRDI Destination: CRDI

DFHRD0103 • DFHRM0101

DFHRD0103 date time applid terminal userid tranid INSTALL
lsrpoolid
PARTITIONSET(partitionsetid)
Destination: CRDI
Explanation: Partitionset partitionsetid has been installed into
CICS by user userid at terminal terminal using transaction
tranid. DFHRD0108 date time applid terminal userid tranid INSTALL
System action: Processing continues. PARTNER(partner_name)
User response: None. Explanation: Partner partner_name has been installed into
Module: DFHAMP CICS by user userid at terminal terminal using transaction
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, tranid.
partitionsetid System action: Processing continues.
Destination: CRDI User response: None.
Module: DFHAMP
partner_name
TRANSACTION(transid)
Destination: CRDI
Explanation: Transaction transid has been installed into CICS
by user userid at terminal terminal using transaction tranid.
System action: Processing continues. DFHRD0109 date time applid terminal userid tranid INSTALL
User response: None. TRANCLASS(tranclassid)
Module: DFHAMP Explanation: Transaction class tranclassid has been installed
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, into CICS by user userid at terminal terminal using transaction
transid tranid.
Destination: CRDI System action: Processing continues.
Module: DFHAMP
PROFILE(profid)
tranclassid
Explanation: Profile profid has been installed into CICS by
Destination: CRDI
userid userid at terminal terminal using transaction tranid.
User response: None. DFHRD0119 I date time applid terminal userid tranid INSTALL
Module: DFHAMP DOCTEMPLATE(doctemplate-name)
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, Explanation: DOCTEMPLATE doctemplate-name has been
profid installed into CICS by userid userid at terminal terminal using
Destination: CRDI transaction tranid.
DFHRD0106 date time applid terminal userid tranid INSTALL Destination: CRDI
FILE(fileid) Module: DFHAMP
Explanation: File fileid has been installed into CICS by user
userid at terminal terminal using transaction tranid.
doctemplate-name
Module: DFHAMP DFHRD0120 I date time applid terminal userid tranid INSTALL
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, TCPIPSERVICE(tcpipservice-name)
fileid Explanation: TCPIPSERVICE tcpipservice-name has been
Destination: CRDI installed into CICS by userid userid at terminal terminal using
transaction tranid.
DFHRD0107 date time applid terminal userid tranid INSTALL User response: None.
LSRPOOL(lsrpoolid) Destination: CRDI
Explanation: Lsrpool lsrpoolid has been installed into CICS by Module: DFHAMP
userid userid at terminal terminal using transaction tranid.
tcpipservice-name
Module: DFHAMP
DFHRMxxxx messages
dumps in the dump table. If the error is not critical, the
DFHRM0101 applid A severe error (code X'code') has
transaction is terminated with abend code ASPM and CICS
occurred in module DFHSPP.
continues.
Explanation: CICS has detected a severe error in module
DFHSPP. Message DFHME0116 is normally produced containing the
System action: If this is a critical error, CICS is terminated symptom string for this problem.
(even if you have specified in the dump table that CICS User response: You need further assistance from IBM to
should not terminate) and a system dump with dumpcode resolve this problem. See Part 4 of the CICS Problem
RM0101 is taken unless you have specifically suppressed Determination Guide for guidance on how to proceed.

DFHRM0102 • DFHRT4408
Module: DFHSPP XMEOUT Parameters: applid, X'code'

DFHRM0103 date time applid Transaction tranid has been
backed out during task detach.
DFHRM0102 applid A severe error (code X'code') has Explanation: An implicit syncpoint at the end of a task has
occurred in module DFHDBP. resulted in a backout. This occurs if any of the resource
Explanation: CICS has detected a severe error in module managers respond to the syncpoint request with a backout.
DFHDBP.
System action: This is a critical error. CICS is terminated This message is sent to the CSMT log and not to the terminal
(even if you have specified in the dump table that CICS because at this stage, the terminal has already been detached
should not terminate). A system dump with dumpcode from the task.
RM0102 is taken unless you have specifically suppressed System action: Other processing continues.
dumps in the dump table. User response: Take user-defined action to ensure all local
and remote resources are synchronized.
Message DFHME0116 is normally produced containing the Module: DFHSPP
User response: You need further assistance from IBM to XMEOUT Parameters: date, time,applid, tranid
resolve this problem. See Part 4 of the CICS Problem Destination: CSMT
Module: DFHDBP
DFHRTxxxx messages
DFHRT4401 time applid No transaction identification DFHRT4405 time applid System sysid cannot be found.
specified. Please try again. Please check that you have used the correct
Explanation: The terminal operator has not entered an system name.
identifier for this transaction. Explanation: System sysid is not defined to CICS.
System action: CICS processing continues. System action: CICS processing continues.
User response: Enter a valid transaction identifier. User response: Check that you have used the correct system
Module: DFHRTE name. Either reenter the request specifying the correct system
Destination: Terminal End User name, or define system sysid to CICS.
Module: DFHRTE
DFHRT4402 time applid You cannot use a Program
Function key to start transactions on other
systems. DFHRT4406 time applid System sysid is not in service or is
Explanation: Program function keys cannot be used to released.
initiate a transaction on another system using the routing Explanation: The system sysid is not currently in service, or is
transaction (CRTE). released.
System action: CICS processing continues. System action: CICS processing continues. If a routing
User response: Enter a valid transaction identifier. session had been established before the connection became
Module: DFHRTE unavailable, it remains in force until the user enters CANCEL.
Destination: Terminal End User If the connection becomes usable before this, transactions are
again routed. If this message is in response to the initial CRTE
command, no routing session is in force and no routing is
DFHRT4403 time applid The routing session to system sysid attempted for subsequent terminal input.
has been terminated. Further transactions User response: Wait until system sysid becomes available.
will not be routed to the connected system. Enter CANCEL to terminate an existing routing session.
Explanation: The routing session has been terminated. Module: DFHRTE
Subsequent transaction identifiers will not be shipped to the Destination: Terminal End User
connected system.
System action: CICS processing continues without the
connection to system sysid. DFHRT4407 time applid This system does not include
User response: If you need to use system sysid, investigate support of Intersystem Communication.
why the routing session has terminated. Explanation: The system has not been generated with
Module: DFHRTE support for intersystem communication.
Destination: Terminal End User System action: CICS processing continues without support
for intersystem communication.
User response: Generate the system with support for
DFHRT4404 time applid Please change format of request to intersystem communication.
CRTE SYSID=XXXX,TRPROF=YYYYYYYY. Module: DFHRTE
Explanation: The request to the routing transaction CRTE Destination: Terminal End User
contained incorrect syntax.
User response: Reenter the request to the routing transaction DFHRT4408 time applid Terminal termid is not of the type
CRTE using the correct syntax. supported by routing transaction tranid.
Module: DFHRTE Explanation: The routing transaction does not support the
Destination: Terminal End User type of terminal being used.

DFHRT4409 • DFHRT4418
System action: CICS processing continues without support

DFHRT4414 time applid Transaction tranid cannot run.
for terminal termid.
CICS shutdown is in progress in the remote
User response: Use a terminal of the type supported by the
system.
routing transaction, that is, a 3270 display terminal or a
Explanation: A transaction tranid was routed to a remote
console.
CICS system that was being quiesced. CICS directs this
Module: DFHRTE
message to the terminal at which the transaction identification
was entered.
This message is similar to DFHAC2007 in a local system.
DFHRT4409 time applid The routing session to system sysid System action: The remote CICS system continues quiescing.
has been started. User response: Reenter the transaction when the remote
Explanation: The routing session has been started. CICS system is in normal execution mode.
System action: CICS processing continues. Module: DFHZTSP
User response: None. Destination: Terminal End User
Module: DFHRTE
DFHRT4415 time applid Transaction CXRT was invoked
directly by terminal input. This is not
DFHRT4410 time applid System sysid is unavailable. The allowed.
routing session to it is terminated. Explanation: The transaction code CXRT, which is reserved
Explanation: The routing transaction has been terminated for an internal CICS transaction, was entered from a terminal.
because the system became unavailable. Subsequent System action: The transaction is run with no effect.
transaction identifiers will not be shipped to the connected User response: Do not enter transaction code CXRT at a
system. terminal.
System action: CICS processing continues. Module: DFHCRT
User response: If appropriate, reenter the transaction when Destination: Terminal End User
the routing session to system sysid becomes available.
Module: DFHRTE
Destination: Terminal End User DFHRT4416 date time applid Abend abcode has occurred in
the Dynamic Routing Program
Explanation: The dynamic routing program has abnormally
DFHRT4411 time applid The Communication Profile cannot terminated with abend code abcode.
be found. System action: Normal transaction abend processing
Explanation: The profile, specified for a transaction invoked continues.
from the terminal to which the message is directed, is not User response: The abend code is either a transaction abend
defined to CICS. code or a user abend code. First, look up the abend code in
System action: CICS stops initialization of the transaction. “Transaction Abend Codes (CICS Transaction Server for
User response: Define the communication profile to CICS VSE/ESA)” on page 453.
and reinvoke the transaction. For further information on how
to define the profile, refer to the CICS Distributed Transaction If the code is not a CICS transaction abend code, it is a user
Programming Guide. abend code. Request an explanation from the programmer
Module: DFHRTE responsible for this area.
Destination: Terminal End User Module: DFHAPRT
XMEOUT Parameters: date, time,applid, abcode
DFHRT4412 time applid The transaction code is not Destination: CSMT
defined on the remote system.
Explanation: A transaction identification, routed to a remote
CICS system, is not an installed transaction definition in the DFHRT4417 date time applid Abend abcode in DFHAPRT -
remote system. CICS directs this message to the terminal at Dynamic routing program must be
which the transaction identification was entered. AMODE=31.
Explanation: CICS has failed to link to the dynamic routing
This message is similar to DFHAC2001 in a local system. program because it is not AMODE(31).
System action: CICS stops initialization of the transaction. System action: Normal transaction abend processing
User response: Enter a valid transaction ID, or install the continues.
transaction on the remote system. User response: Recompile, reassemble, and link edit the
Module: DFHZTSP dynamic routing program to AMODE(31).
Destination: Terminal End User Module: DFHAPRT
DFHRT4413 time applid The transaction has been disabled Destination: CSMT
on the remote system.
Explanation: A transaction, routed to a remote CICS system,
is disabled in the installed transaction definition of the remote DFHRT4418 date time applid Abend abcode in DFHAPRT -
system. CICS directs this message to the terminal at which the Dynamic routing program PPT entry not
transaction identification was entered. found.
Explanation: CICS was unable to find a PPT entry for the
This message is similar to DFHAC2008 in a local system. dynamic routing program.
System action: CICS stops initialization of the transaction. System action: Normal transaction abend processing
User response: Enable the transaction on the remote system. continues.
Module: DFHZTSP User response: Ensure that the dynamic routing program
Destination: Terminal End User specified by the DTRPGM system initialization parameter or

DFHRT4419 • DFHRU2803
via the EXEC CICS SET SYSTEM DTRPROGRAM(program Module: DFHAPRT

name) command has been correctly defined to CICS.
Module: DFHAPRT XMEOUT Parameters: date, time,applid, abcode
Destination: CSMT
Destination: CSMT
DFHRT4421 date time applid Unable to Delete remote
Terminal termid that is connected to system
DFHRT4419 date time applid Abend abcode in DFHAPRT - sysid.
Fetch for dynamic routing program failed. Explanation: A transaction could not be started because the
Explanation: CICS was unable to load the dynamic routing remote terminal definition for termid, system sysid was flagged
program. for deletion but the DELETE failed. This might indicate a
System action: Normal transaction abend processing transaction looping on the terminal.
continues. System action: The user transaction abends with abend code
User response: Ensure that the dynamic routing program AZTI.
specified on the DTRPGM system initialization parameter or User response: See the associated DFHZCxxxx messages for
via the EXEC CICS SET SYSTEM DTRPROGRAM(program further guidance. Once corrected, you can attempt to run the
name) command has been correctly defined. Ensure that it is transaction again.
also in a load library accessible to CICS. Module: DFHZTSP
Module: DFHAPRT
XMEOUT Parameters: date, time,applid, termid, sysid
XMEOUT Parameters: date, time,applid, abcode Destination: Console and Transient Data Queue CSMT
Destination: CSMT
DFHRT4480 time applid The CSSF transaction is no longer

DFHRT4420 date time applid Abend abcode in DFHAPRT - supported. Please use CESF.
Link to the dynamic routing program failed. Explanation: A user has attempted to run the CSSF
Explanation: An unexpected return code was returned from transaction. The CSSF transaction is only invoked internally by
the link to the dynamic routing program. CICS for CRTE cancel processing.
System action: Normal transaction abend processing System action: The transaction terminates.
continues. User response: Use the CESF transaction to sign off.
User response: You need further assistance from IBM to Module: DFHRTC
resolve this problem. See Part 4 of the CICS Problem Destination: Terminal End User
DFHRUxxxx messages
the journal record that was read was not part of the sequence
DFHRU2800I applid DFHRUP completed
of records associated with the last CICS execution that is
Explanation: The recovery utility program has completed
undergoing an emergency restart. If this is a disk volume, a
processing.
wraparound condition might have occurred, and insufficient
data was collected to restart the system. (This normally occurs
when insufficient space has been allocated on disk for the
Module: DFHRUP
system log).
XMEOUT Parameter: applid System action: CICS is abnormally terminated with a dump.
Destination: Console User response: Check that the correct journal volume has
been mounted.
DFHRU2801 applid I/O error reading the system log. If this is a tape volume and DFHTEOF was not executed,
DFHRUP terminates abnormally. execute DFHTEOF to locate end-of-file for the tape volume.
Explanation: An unidentified error has occurred during If this is a disk volume, check for tasks that have been in the
emergency restart while DFHRUP was attempting to read the system for longer than the time that records have been logged,
system log. but without issuing a syncpoint. Check that the value
System action: CICS terminates abnormally with a system specified for the AKPFREQ system initialization parameter is
dump. greater than zero. If it is impossible to perform an emergency
User response: Examine the system log to check whether restart, specify START=COLD instead of START=AUTO.
DFHRUP has encountered an EOF (end of file) marker before Module: DFHRUP
completing its backward read. This may be due to DFHRUP
wrapping back round through the journal extents, possibly XMEOUT Parameter: applid
missing a syncpoint or an activity keypoint. Destination: Console
If DFHRUP has not encountered an EOF marker, investigate
whether you have a physical tape or disk error. DFHRU2803 applid Failure detected on open of the system
Module: DFHRUP log. DFHRUP terminates abnormally.
Explanation: This message can arise from errors resulting
from one of three macro calls to journal control issued by
DFHRUP.
1. GETJCA,OPEN,VOL=FIRST.
DFHRU2802 applid Log record invalid. DFHRUP v The GETMAIN for JCA storage may have failed.
Explanation: The journal data set might contain no entries, or

DFHRU2804 • DFHRU2809
v The initial open processing, which examines the log data Destination: Console
sets to ascertain which is to be the current one, and then
searches for the last written record, may have failed for
some reason. DFHRU2806 applid No storage available for TBO record.
2. OPEN,INPUT,VOL=CURRENT. DFHRUP terminates abnormally.
v The main open-for-input processing, which positions the Explanation: An attempt to allocate storage for the
log in preparation for reading by DFHRUP, has failed. transaction backout (TBO) data area was unsuccessful.
3. OPEN,INPUT,VOL=PREVIOUS. System action: CICS is abnormally terminated with a dump.
v The opening of the previously used data set has failed. User response: Increase the region size and rerun.
Module: DFHRUP
Possible reasons for the message are:
1. The system log has been reformatted since the last CICS XMEOUT Parameter: applid
run. Destination: Console
2. The last CICS run did not write an activity keypoint to the
log because system initialization parameter AKPFREQ was DFHRU2807 applid Error occurred writing stats to transient
specified as zero. data.
3. During emergency restart, DFHRUP, reading the system Explanation: The CICS recovery utility program (DFHRUP)
log backward, reached the beginning of the data set, and did not get a normal response (NORESP) from a DFHTD
tried to open another log data set, but none existed. TYPE=PUT macro issued to write statistics to the transient
(During the previous run, CICS logging wrapped round data destination, CSSL.
from the end of the log data set to its beginning.) System action: CICS terminates writing of statistical data, but
4. The CICS startup job stream does not include all the emergency restart continues.
necessary DLBL statements. User response: Inspect your destination control table (DCT)
System action: CICS is abnormally terminated with a dump. to find out which device CSSL is held on. Correct any problem
User response: Try to determine which of the macro calls that exists on that device. If statistical data is required, cancel
was responsible for the message. You will probably need to emergency restart, and restart CICS when you have corrected
refer to a dump and trace table in order to do this. the error.
Locate the JCA, which will obtain request information and Module: DFHRUP
possibly a response code, and also the JCT entry for the log, XMEOUT Parameter: applid
for its status information. You may also need to print off the Destination: Console
log data sets using DFHJUP to examine their contents.
If any of the reasons listed in the explanation apply, respond

DFHRU2808 applid I/O error writing backout data to the
as shown below:
restart data set. DFHRUP terminates
1. Cold start CICS.
abnormally.
2. If you wish emergency restart to be possible in future,
Explanation: The program encountered an I/O error while
change AKPFREQ to a nonzero value, and cold start CICS.
writing the backout data records to the restart data set. This
3. To prevent a recurrence of this problem and the failure of a
message is issued because the restart data set is full.
future emergency restart, increase the size of your log data
System action: CICS is abnormally terminated with a dump.
set, or create a second one. Then cold start CICS.
User response: Reallocate the restart data set to different
4. Add the missing DLBL statement(s) to the startup job
extents or, if necessary, increase the size of the restart data set.
stream, and retry emergency restart.
The data set should be formatted as in a cold start.
Module: DFHRUP
If this message is issued during emergency restart, in order to
allocate more space to the restart data set and still allow
emergency restart, do the following:
1. Carry out a VSAM REPRO on DFHRSD.
DFHRU2804 applid Unable to allocate storage. DFHRUP 2. Make the original restart data set larger using the
terminates abnormally. DELETE/DEFINE procedure.
Explanation: Storage was not allocated in response to the 3. Use REPRO to reload the data into DFHRSD.
storage macro.
After this, START=AUTO should invoke emergency restart.
Module: DFHRUP
User response: Increase the region size and rerun.
Module: DFHRUP XMEOUT Parameter: applid
DFHRU2809 applid I/O error writing control tables to the
restart data set. DFHRUP terminates
DFHRU2805 applid Unrecoverable I/O error on the system
abnormally.
log. DFHRUP terminates abnormally.
Explanation: The program encountered an I/O error while
Explanation: An error occurred other than an end-of-file
writing the control tables to the restart data set.
(EOF) or a read error on the system log volume.
User response: Reallocate the restart data set to different
User response: Rerun emergency restart.
extents, or, if necessary, increase the size of the restart data set.
Module: DFHRUP
Format the data set as in a cold start.
XMEOUT Parameter: applid Module: DFHRUP

DFHRU2811 • DFHRU2830
XMEOUT Parameter: applid Module: DFHRCRP

DFHRU2811 applid Recovery control restart failed
Explanation: The CICS recovery control restart task could not
DFHRU2816 applid Exit program progname is not available
complete because a necessary step failed. The task has done
Explanation: The user-defined global exit program, progname,
some essential recovery operations and has abnormally
is not defined, disabled, or missing from the program library.
terminated with abend code ARCA.
System action: CICS abnormally terminates the recovery
System action: CICS writes a transaction dump for the
control restart task with transaction abend ARCB. CICS then
recovery control restart task. CICS then terminates abnormally
with a system dump.
User response: Make program progname available.
CICS sends two messages to the console, one to identify the Module: DFHRCEX
error detected by the recovery control restart task, and one,
XMEOUT Parameters: applid, progname
DFHRU2811, to say that the task has failed. 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 DFHRU2818A applid Unable to browse DL/I entries on the
cause of the failure. CICS Global Catalog
Module: DFHRCRP Explanation: An invalid return code was encountered from
XMEOUT Parameter: applid the Global catalog browse for DL/I status records. The Global
Destination: Console catalog is corrupt.
System action: Execution is abnormally terminated
User response: Reformat both the Global and Local catalogs
DFHRU2812 applid Program DFHRCRP cannot be found and cold start the system.
Explanation: The CICS recovery recontrol restart program Module: DFHRUP
(DFHRCRP) cannot be found.
CICS cannot find DFHRCRP in any sublibrary in the LIBDEF Destination: Console
User response: To correct this error, place DFHRCRP in a DFHRU2820I applid DFHRUP in progress
sublibrary in the LIBDEF search chain for the CICS startup job Explanation: The CICS recovery utility program has begun
stream. execution.
Module: DFHRCP System action: CICS recovery processing continues.
XMEOUT Parameter: applid Module: DFHRUP
DFHRU2814 applid I/O error on restart data set, VSAM
return codes are RF=nn, FDBK=mm
Explanation: A VSAM error occurred while reading or DFHRU2821 applid Storage Allocation error. DFHRUP
writing to the restart data set. nn is the return code in register abnormally terminates.
15, and mm is the value of the feedback field in the request Explanation: An error occurred on a request to the storage
parameter list (RPL). manager (SM) domain. The domain that detected the error
System action: If this message occurs during shutdown, and will have provided an exception trace, a console message and,
CICS is restarted with START=AUTO, an emergency start will possibly, a system dump.
result. System action: CICS is abnormally terminated with a system
User response: For the meaning of the codes in the message, dump.
see the section "VSE/VSAM Codes" in z/VSE Messages and User response: Refer to the related message from the domain
Codes - Volume 2. that detected the original error. It will provide further
Module: DFHRCP information and guidance.
Module: DFHRUP
XMEOUT Parameters: applid, nn,mm
DFHRU2815 applid Program DFHUSBP cannot be found.

User backout processing cannot be performed DFHRU2830 applid Unable to find the start of unit of work
Explanation: CICS is unable to do user backout processing record on the system log for task taskid,
because program DFHUSBP cannot be found. transaction tranid on terminal termid.
Explanation: The task taskid cannot be recovered completely
CICS cannot find DFHUSBP in any sublibrary in the LIBDEF because CICS cannot find the start of the unit of work record
search chain for the CICS startup job stream. on the system log. This is normally caused by a system log
System action: CICS terminates abnormally with a dump. wrap-around condition in which insufficient data is collected
User response: To correct this error, place DFHUSBP in a to restart the system. This occurs when:
sublibrary of the LIBDEF search chain for the CICS startup job v Insufficient space has been allocated on disk for the system
stream. log.

DFHRU2831 • DFHSI0102
v A premature switch of the system log data sets has If you choose 'Yes', all units of work that can be recovered
occurred. completely are recovered, and all units of work that fail to
v A task is waiting for an external event that is late. recover completely, as reported by message DFHRU2830,
System action: Processing continues. This message is issued are partially recovered if some data is available.
for each task that cannot be fully recovered. Message If an active DL/I record is found without a corresponding
DFHRU2839 is then issued. schedule record, the unit of work is not recovered and
User response: Make a note of the message details as they reported through the message DFHRU2830. If an active
may be needed for a manual recovery of the task. See message DL/I record is found including its corresponding schedule
DFHRU2839 for further guidance. record, the unit of work is fully recovered. The net effect is
Module: DFHRUP that active DL/I units of work are either fully recovered or
XMEOUT Parameters: applid, taskid,tranid, termid not recovered at all.
Destination: Console Consider completing the recovery of these manually by
retrieving the records related to the reported messages from
the archived system log tapes.
DFHRU2831 applid Unable to find the committed output v Reply 'No' if you are not sure that the correct system log
message record on the system log for has been recovered, if there are a large number of
terminal termid. individual recovery problems (reported in messages
Explanation: The positive acknowledgement of a DFHRU2830 and DFHRU2831), or if you are unsure of the
committed-output message to terminal termid was never status of the system.
received by CICS, and the message cannot be found on the
If you reply 'No', no transactions are recovered and message
system log. This is normally caused by a wrap-around
DFHRU2802 is issued after this one.
condition in which insufficient data is collected to restart the
system. This can occur when:
v Insufficient space has been allocated on disk for the system To reduce the chances of a recurrence of this problem consider
log. the following:
v A premature switch of the system log data sets occurred. v Syncpointing
System action: Processing continues. Message DFHRU2839 is A transaction can be partitioned into a sequence of units of
issued when recovery ends. work, where each unit of work delimits the resources to be
User response: Make a note of the message details as they recovered after a failure. This should be kept to a minimum
may be needed for a manual recovery of the message and by issuing more SYNCPOINT calls at appropriate points
terminal. See message DFHRU2839 for further guidance. throughout the application program.
Module: DFHRUP v The system initialization parameter AKPFREQ
XMEOUT Parameters: applid, termid Specifying AKPFREQ=0 switches keypointing off and causes
Destination: Console an attempted recovery to fail every time.
v System log size
The system log should be large enough to hold all logged
DFHRU2839D applid Emergency restart failed to complete. data that has been logged during the life of the oldest unit
Do you wish to continue? Reply 'Yes' or 'No'. of work, extended if appropriate, by the time to receive all
Explanation: Emergency restart has not been successful for committed-output messages.
the reasons reported in one or more messages DFHRU2830
and DFHRU2831. The system log should contain a complete activity keypoint.
System action: CICS waits for a reply to the message. Module: DFHRUP
User response: Reply either 'Yes' or 'No'. XMEOUT Parameter: applid
v Reply 'Yes' if you are satisfied that the correct system log Destination: Console
has been loaded and the number of reported recovery
problems, through the DFHRU2830 and DFHRU2831
messages, is low. Replying 'Yes' can significantly reduce the
amount of manual recovery that is needed.
DFHSIxxxx messages
DFHSI0101 applid Storage error while restoring DWE DFHSI0102 applid Error reading DWE warm start data.
warm start data. Explanation: CICS was trying to create a deferred work
Explanation: CICS was trying to create a deferred work element (DWE) that had been saved in the catalog during a
element (DWE) that had been saved in the catalog during a previous warm keypoint. A call to retrieve the next DWE
previous warm keypoint. A call to the storage (SM) manager saved in the catalog failed. An implication of this message is
domain failed. DWE recovery is prevented. that the catalog is corrupt.
System action: CICS abends with a system dump. System action: CICS abends with a system dump.
User response: Refer to the preceding SM domain message to User response: Refer to the preceding catalog (CC) manager
determine the cause of the GETMAIN failure. message to determine the cause of the error in catalog
processing.
CICS should be either AUTO or COLD restarted.
Module: DFHSII1 CICS should be COLD restarted because the catalog is
unreliable.
XMEOUT Parameter: applid Module: DFHSII1

DFHSI0103 • DFHSI1500
DFHSI0914I applid Unable to initiate transaction CSFU.
Files will not be opened at initialization.
DFHSI0103 applid Error chaining a DWE onto a {LU6.1 | Explanation: Module DFHSIJ1 could not start transaction
LU6.2} owner. CSFU. Either CSFU is not an installed transaction definition,
Explanation: CICS created a copy of a deferred work element or DFHFCU is not an installed program definition.
(DWE) which was saved in the catalog during a previous System action: CICS does not open any files at initialization
warm keypoint. CICS then tried to chain it to the appropriate time. If a file is defined in the file control table (FCT) to be
control block but failed because the control block could not be opened at initialization time, CICS will open it on first
found. The restart did not produce all the necessary reference.
information for chaining to be successful. User response: Make transaction CSFU and program
DFHFCU available for execution. Group DFHOPCLS in
If the DWE is an LU6.1 type, the owning control block is the DFHLIST contains all of the definitions needed for file
TCTTE mentioned in the DWE. opening and closing (dynamically as well as at initialization
time).
If the DWE is an LU6.2 type, the owning control block is the
Module: DFHSIJ1
unit of recovery descriptor (URD) number mentioned in the
DWE. XMEOUT Parameter: applid
System action: CICS abends with a system dump. Destination: Console
User response: CICS should be COLD restarted because
WARM restart is unreliable.
Module: DFHSII1 DFHSI1250 applid VSAM error processing SHOWCAT for
intrapartition data set dsetname R15=xxxx.
XMEOUT Parameters: applid, {1=LU6.1, 2=LU6.2} Explanation: During SHOWCAT processing for the
Destination: Console intrapartition data set, dsetname, VSAM detected an error and
issued return code xxxx.
System action: CICS writes a dump and terminates
DFHSI0104 applid Catalog error while restoring URDP
abnormally.
warm start data.
Explanation: CICS was trying to read a URDP (unit of Message DFHME0116 is normally produced containing the
recovery descriptor pointer) that had been saved in the catalog symptom string for this problem.
at a previous warm keypoint. User response: Check the return code in the VSE/VSAM
User's Guide and Application Programming manual and restart
A call to retrieve the next URDP saved in the catalog failed.
CICS.
An implication of this message is that the catalog is corrupt.
Module: DFHSID1
System action: CICS abends with a system dump.
User response: Refer to the preceding catalog (CC) manager XMEOUT Parameters: applid, dsetname, xxxx
message to determine the cause of the error in catalog Destination: Console
processing.
CICS should be COLD restarted because the catalog is DFHSI1499 applid Unable to acquire special storage.
unreliable. Explanation: As part of CICS initialization, an attempt is
Module: DFHSII1 made to acquire an area of storage from the fetch-protected
XMEOUT Parameter: applid subpool. The attempt has been unsuccessful.
Destination: Console System action: CICS terminates abnormally with a dump.
User response: This error indicates a severe problem with
your operating system. You need further assistance from IBM
DFHSI0105 applid Error locating terminal tttt for URDP to resolve this problem. See Part 4 of the CICS Problem
processing. Determination Guide for guidance on how to proceed.
Explanation: CICS was trying to rechain an URDP (unit of Module: DFHSIB1
recovery descriptor pointer) element for terminal tttt. Terminal
tttt could not be found.
User response: CICS should be COLD restarted because the
catalog is unreliable. DFHSI1500 applid element startup is in progress for CICS
Module: DFHSII1 Transaction Server Version version
XMEOUT Parameters: applid, tttt Explanation: This is an informatory message indicating that
Destination: Console element startup is in progress.
Element is part of CICS Transaction Server Version version.
DFHSI0106 applid Error terminal tttt has no LUC
User response: None. This message cannot be suppressed.
extension.
Module: DFHAPSIP
Explanation: CICS was trying to rechain an URDP (unit of
recovery descriptor pointer) element for terminal tttt. Terminal XMEOUT Parameters: applid, element,version
tttt did not have a LUC extension. Destination: Console
User response: CICS should be COLD restarted because the
catalog is unreliable.
Module: DFHSII1
XMEOUT Parameters: applid, tttt

DFHSI1501I • DFHSI1516I
you cannot correct the problem, you must perform a cold start
DFHSI1501I applid Loading CICS nucleus.
or an emergency restart.
Module: DFHSII1
the CICS nucleus is being loaded.
System action: System initialization continues. XMEOUT Parameter: applid
Module: DFHSIB1
XMEOUT Parameter: applid DFHSI1509 applid Error reading ICE warm start control
Destination: Console data.
Explanation: CICS was unable to read the ICE (interval
control elements) warm start control information in the restart
DFHSI1502I applid CICS startup is {Cold | Warm |
data set (DFHRSD). A message giving VSAM return codes
Emergency | Logterm}.
usually precedes this message.
Explanation: During CICS initialization, the type of restart is
determined and the operator notified by this message.
User response: Correct the problem in the restart data set. If
you cannot correct the problem, you must perform a cold start
or an emergency restart.
Module: DFHSIC1
Module: DFHSII1
XMEOUT Parameters: applid, {1=Cold, 2=Warm, 3=Emergency,
4=Logterm}
DFHSI1510I applid Journal control subtask is being

DFHSI1503I applid Terminal data sets are being opened.
attached/entered.
the terminal data sets are being opened.
the journal control OPEN/CLOSE operating system subtask is
being attached.
Module: DFHSIF1
XMEOUT Parameter: applid Module: DFHSIH1
DFHSI1504 applid Error reading URD warm start control
data.
DFHSI1511I applid Installing group list grplist.
Explanation: CICS was unable to read the URD (unit of
Explanation: Group list grplist is being installed.
recovery descriptors) warm start control information in the
restart data set (DFHRSD). A message giving VSAM return
codes usually precedes this message.
Module: DFHSII1
User response: Correct the problem in the restart data set. If XMEOUT Parameters: applid, grplist
you cannot correct the problem, you must do a cold start or Destination: Console
an emergency restart.
Module: DFHSII1
DFHSI1514I applid DL/I initialization started.
XMEOUT Parameter: applid Explanation: This is an informatory message indicating that
Destination: Console Data Language/I (DL/I) initialization has started.
DFHSI1506 applid Unable to OPEN the global catalog.
Module: DFHSIH1
Explanation: During initialization, CICS issued an OPEN for
the global catalog data set (DFHGCD), but the OPEN failed. XMEOUT Parameter: applid
System action: CICS terminates abnormally with a dump. Destination: Console
User response: Examine the preceding VSAM message for
the reason for the OPEN failure. Note that if you specify
START=AUTO, or if you define your system with journal DFHSI1516I applid Opening journal data sets.
support, you must supply a global catalog data set in the JCL. Explanation: This is an informatory message indicating that
Module: DFHSIC1 the journal data sets are being opened.
XMEOUT Parameter: applid User response: You can suppress this message with the SIT
Destination: Console parameter, MSGLVL=0.
Module: DFHRCRP
DFHSI1508 applid Error reading AID warm start control XMEOUT Parameter: applid
data. Destination: Console
Explanation: CICS was unable to read the AID (auto initiate
descriptors) warm start control information in the restart data
set (DFHRSD). A message giving VSAM return codes usually
precedes this message.
User response: Correct the problem in the restart data set. If

DFHSI1517 applid Control is being given to CICS.
control is being given to CICS. DFHSI1525 applid Control record on DFHGCD data set
applid is the VTAM APPLID of the CICS system issuing the invalid.
message. Explanation: CICS is unable to read the control record from
System action: System initialization continues. the global catalog.
User response: None. This message is also issued if the system log data set is
Module: DFHSIJ1 missing from the job control table (JCT).
XMEOUT Parameter: applid System action: CICS terminates with a dump.
Destination: Console User response: If the system log data set is missing, generate
the system log data set, and attempt an emergency restart.
If the system log data set is not missing, or if emergency
DFHSI1518 applid No control record on global catalog
restart fails, perform a cold start.
data set. Cold start forced.
Module: DFHSIC1
Explanation: There was no control record on the global
catalog data set. This should only happen when the global XMEOUT Parameter: applid
catalog data set is used for the very first time. Destination: Console
User response: If the global catalog data set is being used for
the very first time this message is to be expected. However if DFHSI1527 applid Cannot open DFHGCD data set. Cold
the global catalog data set should contain information from a start will be forced when CICS restarted.
previous CICS execution then CICS should be canceled and Explanation: During a cold start, CICS could not open the
the reason for the discrepancy investigated. global catalog. This may be because no global catalog is
Module: DFHSIC1 defined in the startup job stream, or because of a VSAM error
(see preceding VSAM error message). Since CICS cannot write
XMEOUT Parameter: applid to the global catalog, only a cold start will be possible when
Destination: Console you next bring up CICS.
User response: If this CICS run terminates abnormally, you
DFHSI1519I applid The interregion communication session
will not be able to do an emergency restart. If this is an
was successfully started.
acceptable risk, allow CICS to continue, otherwise cancel CICS
and restart with a usable global catalog defined in the job
the interregion communication (IRC) session has been
stream.
successfully started.
Module: DFHSIC1
User response: None. XMEOUT Parameter: applid
Module: DFHSIJ1 Destination: Console
Destination: Console DFHSI1528 applid CSA record on DFHGCD data set
invalid.
Explanation: CICS attempted to read the common system
DFHSI1521 applid CICS unable to continue for reasons
area (CSA) warm start control record from the global catalog
given above.
but found it to be invalid.
Explanation: CICS initialization cannot continue because of
System action: CICS is abnormally terminated and a dump is
one or more serious errors. One or more preceding messages
provided.
describe these errors.
User response: Perform an emergency restart.
System action: CICS terminates with a dump.
Module: DFHSIC1
User response: Refer to any preceding messages for further
guidance on what the problems may be and how to solve XMEOUT Parameter: applid
them. Correct the errors and restart CICS. Destination: Console
Module: DFHSII1
XMEOUT Parameter: applid DFHSI1530 applid Purge of non-executable ATI request
Destination: Console inoperative.
Explanation: CICS is unable to initiate the CRSQ task to
delete automatic transaction initiation (ATI) requests from the
DFHSI1522D applid Restart errors reported above. Reply
system when those requests are not honored for longer than
'GO' or 'CANCEL'.
the ATI purge delay interval.
Explanation: One or more error messages precede this
message. CICS can continue initialization but only in degraded
User response: If ATI purge is required, ensure that the
mode.
CRSQ task is available next time CICS is initialized.
System action: Depending on your response to this message,
Module: DFHSIJ1
CICS terminates or continues initialization in degraded mode.
User response: Consider the reported errors and their effects, XMEOUT Parameter: applid
and decide if you want CICS to continue in degraded mode. If Destination: Console
you do, reply 'GO'. If you do not, then reply 'CANCEL'.
Correct the errors and restart CICS.
Module: DFHSII1

DFHSI1531 applid Terminal control incompatibility. macro
VTAM return code: retcode error code: errcode
(modname: DFHZRPL). DFHSI1536D applid GRPLIST grplist does not exist. Enter
Explanation: CICS found an inconsistency during the alternative name, 'GO' or 'CANCEL'.
initialization of terminal control.
Explanation: Group list grplist cannot be found on the CSD
macro is the name of the failing VTAM macro.
file.
retcode is the VTAM hexadecimal return code in register 15.
System action: CICS waits for a reply. If you reply CANCEL,
errcode contains the contents of register 0, which is the
CICS terminates. If you reply GO, CICS ignores the specified
associated error code in hexadecimal.
GRPLIST and tries to install the next one. If you specify a
Refer to section "VTAM codes" in z/VSE Messages and Codes - valid list name, CICS initialization continues and the list is
Volume 2 for a complete description of the VTAM return code installed.
retcode and the VTAM error code errcode. User response: Enter 'GO', 'CANCEL' or a valid GRPLIST.
Module: DFHSII1
The probable cause of this inconsistency is that VTAM=YES XMEOUT Parameters: applid, grplist
was specified (perhaps by default) in the SIT, but the VTAM Destination: Console
macros GENCB and SHOWCB are not available.
System action: After issuing this message, CICS system
initialization abnormally terminates with a system dump. DFHSI1537D applid GRPLIST grplist does not exist. Enter
alternative name or 'CANCEL'.
Message DFHME0116 is normally produced containing the Explanation: Group list grplist cannot be found on the CSD
symptom string for this problem. file.
User response: Use the VTAM return code and error code to System action: CICS waits for a reply. If you reply CANCEL,
determine the cause of failure in the VTAM macro macro. See CICS terminates. If you specify a valid list name, CICS
section "VTAM codes" in z/VSE Messages and Codes - Volume 2 initialization continues and the list is installed.
for diagnostic information about the VTAM return code. User response: Enter 'CANCEL' or a valid GRPLIST.
Correct the error and restart CICS. Module: DFHSII1
Module: DFHZRPL
XMEOUT Parameters: applid, grplist
XMEOUT Parameters: applid, macro,retcode, errcode Destination: Console
DFHSI1538D applid Install GRPLIST Errors. Is startup to be

DFHSI1533 applid modname loaded at X'address'. continued - Enter 'GO' or 'CANCEL'.
Explanation: This is an informatory message indicating that Explanation: Errors have been detected in DFHAMP while
CICS has loaded module modname at address address. installing GRPLIST during CICS initialization. Accompanying
System action: System initialization continues. messages describe the nature of the errors.
User response: None. System action: CICS waits for a reply. If you reply CANCEL,
Module: DFHAPSIP CICS terminates. If you reply GO, CICS initialization
XMEOUT Parameters: applid, modname,address continues.
Destination: Console User response: See the associated messages for further
information about these errors. Reply with GO or CANCEL.
Module: DFHSII1
DFHSI1534 applid Unable to link to program DFHAMP -
GRPLIST parameter ignored. XMEOUT Parameter: applid
Explanation: The DFHAMP program cannot be found in any Destination: Console
sublibrary of the LIBDEF search chain for the CICS job. The
GRPLIST parameter cannot be processed and so is ignored. DFHSI1539 applid Error attaching the CESC (Terminal
System action: System initialization continues. Timeout) transaction.
User response: Ensure that the DFHAMP program is in a Explanation: The CESC transaction failed to start during
sublibrary of the LIBDEF search chain for the CICS job. initialization of an alternate XRF region. Although CICS
Module: DFHSII1 continues to initialize, terminals left signed on after the
XMEOUT Parameter: applid takeover are not timed out.
Destination: Console System action: A dump is produced and CICS continues
initialization.
User response: Use the dump to investigate why the
DFHSI1535 applid Severe error detected in DFHAMP - transaction could not be started. It may be that the system was
CICS is terminating. short on storage or that the transaction has been disabled.
Explanation: A severe error was detected while the GRPLIST Module: DFHSIJ1
parameter was being processed.
System action: A dump is provided and CICS is terminated. XMEOUT Parameter: applid
User response: This is most probably a logic error in Destination: Console
DFHAMP. You need further assistance from IBM to resolve
Module: DFHSII1

DFHSI1543 applid Time-Of-Day clock inoperative. DFHSI1550 applid A severe error has occurred while
Explanation: System initialization was unable to establish the making a domain domain call with response
time-of-day clock values for CICS. (X'response') and reason (X'reason').
System action: CICS is abnormally terminated and a dump is Explanation: An unexpected error was returned from the
provided. specified domain. The response and reason codes are given.
User response: The time-of-day clock is external to CICS System action: A system dump is taken, unless the failing
execution and may have been disabled. Enable the time-of-day domain has previously taken diagnostics.
clock and restart CICS.
Module: DFHSII1 This is a critical error and CICS is terminated, even if you
XMEOUT Parameter: applid terminate. Message DFHME0116 is normally produced
Destination: Console containing the symptom string for this problem.
User response: Notify the system administrator. This failure
indicates a serious error in CICS.
DFHSI1545 applid Unable to OPEN ACB for restart data
set. You need further assistance from IBM to resolve this problem.
Explanation: CICS issued an OPEN for the restart data set See Part 4 of the CICS Problem Determination Guide for
(DFHRSD) but the OPEN failed. guidance on how to proceed.
System action: CICS is abnormally terminated and a dump is Module: DFHSII1
provided.
XMEOUT Parameters: applid, domain,X'response', X'reason'
the reason for the OPEN failure.
Module: DFHSII1
DFHSI1551 applid The CICS region userid userid is not
authorized to use the PLTPIUSR parameter
userid userid. Initialization cannot continue,
so CICS is terminated.
DFHSI1546 applid Control record on DFHGCD data set Explanation: The userid specified in the job control
invalid. statements for the CICS region is not authorized to use the
Explanation: CICS attempted to read the control record from userid specified in the PLTPIUSR system initialization
the global catalog (DFHGCD) but found it to be invalid. parameter.
System action: CICS is terminated abnormally and a dump is System action: CICS initialization terminates.
provided. User response: Ensure that the correct userid is specified for
User response: Perform a cold start. PLT processing.
Module: DFHSII1
Ensure that the userid for the CICS region has the necessary
XMEOUT Parameter: applid authorization. This may require the assistance of a security
Destination: Console administrator.
When the necessary corrections have been made rerun the
DFHSI1549 applid Logic error when building TCT module CICS job.
list. Module: DFHSII1
Explanation: Either the format of the modules DFHZCA,
XMEOUT Parameters: applid, userid,userid
ZCB, ZCP, ZCW, ZCX, ZCY, ZCZ and ZCXR was not as
expected, or the TCT was generated incorrectly.
System action: CICS is abnormally terminated and a dump is
provided. DFHSI1552 applid Userid userid specified for the
PLTPIUSR parameter has not been defined
correctly to the external security manager
(ESM). SAF codes are (X'safresp',X'safreas').
User response: Possible reasons for this message are:
1. The modules listed were generated without VTAM
Explanation: The userid specified for the PLTPIUSR
facilities, but the system initialization table (SIT) specifies
initialization parameter has been defined incorrectly.
VTAM=YES.
2. The TCT does not include ACCESSMETHOD=VTAM, but
User response: Ensure that the desired userid is specified for
the system initialization table (SIT) specifies VTAM=YES.
PLT processing and that external security manager (ESM)
3. The entry points of the listed modules are incorrect.
definitions have been specified correctly.
4. The module list in each of the listed modules is incorrect.
The response and reason codes (safresp and safreas) returned by
If reason 1 or 2 applies, correct the error. Otherwise, you will
the system authorization facility (SAF), and the response and
reason codes (esmresp and esmreas) returned by the external
security manager (ESM) are those issued by the RACROUTE
Module: DFHSIF1
REQUEST=VERIFY or RACROUTE REQUEST=EXTRACT
XMEOUT Parameter: applid macros. For the meaning of the response and reason codes in
Destination: Console the message see "BSM Return Codes" in section

There may be further messages produced by CICS or the

DFHSI1561D applid Startup time earlier than shutdown
external security manager (ESM) which provide more
time. Reply 'WAIT' or 'CANCEL'.
information. Explanation: CICS is being warm started. The time-of-day
Correct the errors and restart CICS. clock value for startup is compared with the time-of-day clock
Module: DFHSII1 value recorded for the previous warm shutdown. The two
values differ by more than 15 seconds. Note that:
XMEOUT Parameters: applid, userid,X'safresp', X'safreas', 1. Various resources managers rely on the time-of-day clock
X'esmresp',X'esmreas' value being non-decreasing.
Destination: Console 2. The problem can only occur if CICS had been running on
one CPC and is being restarted on a different CPC.
System action: If the response is 'CANCEL', CICS is
DFHSI1556 applid SKRP {A | F}x disabled due to abnormally terminated and a dump is provided. If the
extension of PGRET value. response is 'WAIT', CICS startup will be delayed for up to 15
Explanation: The PGRET value supplied as an initialization seconds after which the time-of-day clock values will be
option has caused all the single-key retrieval values to be compared once again.
rebuilt. The value shown in the message exceeds 16 bytes. x User response: The time-of-day clocks must be synchronized
can be a value 1 through 3 for A and 1 through 12 for F. across all CPCs that may be used for CICS. If this is not done
System action: The key given in the message (PA1-PA3 and then the effect on CICS is that:
PF1-PF12 respectively) is disabled. 1. Takeover may be delayed if START=STANDBY is specified
User response: If it has been specified (by PARM) that on the SIT.
initialization overrides can be entered by means of the console, 2. Unpredictable errors may occur if CICS is emergency
the opportunity will be given to reenter the PGRET and/or started.
the SKRxxxxx initialization option. Module: DFHSIC1
Module: DFHPASY
XMEOUT Parameters: applid, {1=A, 2=F}, x Destination: Console
DFHSI1562 applid Unable to initialize application domain

DFHSI1558 applid Program progname cannot be found. statistics.
Explanation: Program progname is essential for CICS to Explanation: During CICS initialization, an error was
initialize correctly, but was not defined in a group referenced detected while the application domain (AP) statistics control
by the group list specified in the startup job stream. module, DFHSII1, was being initialized. This could indicate a
System action: A dump is provided and CICS is terminated. problem with the AP component of CICS.
User response: Ensure that the program is defined in a group System action: An exception trace entry is made in the trace
referenced by the group list specified in the startup job stream. table and CICS terminates abnormally with a system dump.
Module: DFHSIJ1
XMEOUT Parameters: applid, progname symptom string for this problem.
Destination: Console User response: This error may have occurred because of an
earlier error detected by the kernel (KE) domain of CICS. Look
DFHSI1559 applid Profile DFHCICSE cannot be found. for earlier messages from the KE domain beginning
Explanation: The DFHCICSE profile is essential for CICS to DFHKExxxx, CICS trace table entries with the prefix KE and a
initialize correctly. However it was not defined in the group dump. These indicate the type of error and the action that
list specified in the startup job stream. should be taken.
System action: A dump is provided and CICS is terminated.
If no earlier error is detected by the KE component, DFHSII1
User response: Ensure that the DFHCICSE profile is defined
makes an exception entry in the trace table (id=X'0700') and
in the group list specified in the startup job stream. A
terminates CICS abnormally with code=1562 and with a
definition of DFHCICSE is provided in the DFHSTAND group
system dump. In this case you will need further assistance
on the CICS system definition (CSD) file.
Module: DFHXCPA, DFHSIJ1 from IBM. See Part 4 of the CICS Problem Determination Guide
XMEOUT Parameter: applid Module: DFHSII1
DFHSI1560 applid Time-Of-Day clock inoperative.
Explanation: System initialization was unable to establish the
time-of-day clock values for CICS. DFHSI1563 applid System log entry not present in JCT.
System action: CICS is abnormally terminated and a dump is Explanation: No entry was found in the JCT for the system
provided. log. One is required because either:
User response: The time-of-day clock is external to CICS 1. DLI was requested (DLI=YES).
execution and may have been disabled. Enable the time-of-day 2. An emergency restart is required.
clock and restart CICS. System action: A dump is provided, and CICS is terminated.
Module: DFHSIC1 User response: The user response depends on the reason the
message was issued (refer to the numbers in Explanation):
1. Supply a system log entry.

2. Supply a system log entry and the correct log to perform Use the values and the return code to determine the cause of
the emergency restart, or Specify START=COLD as the problem.
databases may now be out of synchronization.
Decide whether to cancel or to continue. (This message
Module: DFHSIB1
appears if you bring up CICS before you bring up VTAM.)
If you want to use VTAM terminals in this CICS run, you
Destination: Console must activate VTAM. You can open the VTAM ACB with the
CEMT SET VTAM OPEN command.
DFHSI1564 applid Program DFHSTP failed. Module: DFHSIF1
Explanation: During emergency restart, a CANCEL reply was XMEOUT Parameters: applid, xxxxxxxx, yy
entered to message DFHSI1588. The CICS system initialization Destination: Console
program linked to the system termination program, which
should have terminated CICS, but, instead, it returned control
to the system initialization program. DFHSI1573 date time applid Terminal Control is
System action: CICS terminates abnormally with a dump. unavailable due to an unsupported access
method.
Message DFHME0116 is normally produced containing the Explanation: Releases of VTAM prior to version 3, are not
symptom string for this problem. supported by this release of CICS.
User response: This is an internal CICS error. You need System action: CICS terminates with a system dump.
further assistance from IBM to resolve this problem. See Part 4 User response: Update your access method.
of the CICS Problem Determination Guide for guidance on how Module: DFHZSLS
to proceed.
Module: DFHSII1 Destination: Console
DFHSI1574 applid TCTUA Subpool not added in
DFHZRPL. CICS initialization cannot
DFHSI1565 applid Program DFHSTP cannot be found. continue.
Explanation: An attempt to add a subpool by the storage
Explanation: During CICS initialization, a user CANCEL
manager has failed. Module DFHZRPL has failed in an
request was issued, but the CICS system termination program
attempt to add a subpool for use by the TCTUAs associated
could not be found. CICS cannot find DFHSTP in any
with non-VTAM terminals. Because it is necessary to have the
sublibrary in the LIBDEF search chain for the CICS startup job
subpool present for use when needed, this is a serious error.
stream. System action: The initialization of the CICS system which
System action: CICS terminates abnormally with a dump. tried to perform the addition of the subpool abends. If it was
User response: To correct this error, place DFHSTP in a not able to add the subpool, then CICS is not able to execute
sublibrary of the LIBDEF search chain for the CICS startup job properly.
stream.
Module: DFHSII1 Message DFHME0116 is normally produced containing the
XMEOUT Parameter: applid User response: You need further assistance from IBM to
Destination: Console resolve this problem. See Part 4 of the CICS Problem
Module: DFHZRPL
DFHSI1566 applid Unable to establish JCT entries.
Explanation: During system initialization, CICS has detected XMEOUT Parameter: applid
errors when trying to establish the JCT entries from the CICS Destination: Console
global catalog (DFHGCD).
DFHSI1575 applid Getmain failed for TCTUA subpool in
Message DFHME0116 is normally produced containing the module DFHZRPL. CICS initialization cannot
symptom string for this problem. continue.
User response: Check the CICS catalog and the journal Explanation: The module DFHZRPL has failed in an attempt
control table (JCT). to GETMAIN an area of storage for use by the TCTUA
Module: DFHSIC1, DFHJCRP subpool. This subpool has already been added but no storage
yet exists for it. This is a serious error.
System action: As a result of the GETMAIN failure so early
in the initialization sequence, it is not possible to continue the
CICS initialization. The CICS system which tried and failed to
DFHSI1572 applid Unable to OPEN VTAM ACB - perform the GETMAIN terminates.
RC=xxxxxxxx ACB Code=yy. Message DFHME0116 is normally produced containing the
Explanation: An error was encountered during system symptom string for this problem.
initialization while attempting to open the VTAM ACB. User response: You need further assistance from IBM to
RC=xxxxxxxx is the VTAM error code found in Register 15. yy resolve this problem. See Part 4 of the CICS Problem
is the hexadecimal contents of the ACB. Determination Guide for guidance on how to proceed.
System action: CICS initialization continues. Module: DFHZRPL
User response: Refer to the VTAM Programming manual for a
complete description of the values of the ACB error field and XMEOUT Parameter: applid
the return code. Destination: Console

DFHSI1576 applid Unable to find VTAM ACB. DFHSI1581 applid Journaling specified, but initialization
Explanation: An error was encountered during system programs not present
initialization while attempting to find the VTAM ACB. Explanation: The system initialization table (SIT) specifies
System action: CICS continues to initialize, but VTAM is not journaling, but the journal initialization programs do not exist
available. as installed program definitions.
User response: If you do not require VTAM support, this System action: CICS terminates abnormally with a dump.
message can be ignored. User response: Correct the error and restart CICS. You can
generate all the required transaction and program entries for
If you have VTAM installed on your system, check that journaling by installing the CICS-supplied group, DFHJRNL
VTAM=NO has not been specified as a system initialization (using resource definition online (RDO)).
parameter. If VTAM=YES is specified, investigate why VTAM Module: DFHRCRP
is not currently available on your system.
Module: DFHSIF1 XMEOUT Parameter: applid
DFHSI1584 applid System log positioning subtask attach
failure.
DFHSI1578D applid PLTPI specified cannot be found. Explanation: System initialization attempted to attach the
Reply 'GO' or 'CANCEL'. CICS subtask that positions the system log (DFHTEOF), but
Explanation: The post-initialization program list table (PLTPI) the ATTACH was unsuccessful. The most probable reason for
cannot be found because the PLT does not exist in the CICS the ATTACH failure is that the maximum number of subtasks
program library. allowed has been exceeded. The maximum number of
System action: If the response is 'CANCEL', CICS is subtasks allowed is 15.
terminated. If the response is 'GO', processing continues System action: A dump is provided, and CICS is abnormally
without PLT processing. terminated.
User response: Respond 'GO' or 'CANCEL'. User response: Check that the maximum number of subtasks
Module: DFHSIPLT has not been exceeded. Correct the error, and restart CICS.
XMEOUT Parameter: applid Module: DFHSIC1
DFHSI1579D applid Module modname - PLT program
progname not found. Reply 'GO' or 'CANCEL'. DFHSI1585 applid System log positioning subtask abend
Explanation: This message indicates that a program defined Explanation: During emergency restart, the CICS subtask that
in the post-initialization program list table (PLTPI) cannot be repositions the system log tape (DFHTEOF) has abnormally
found. terminated.
If the message is produced during the first PLT phase in System action: A dump is provided, and CICS is abnormally
initialization (DFHSII1), then the program does not exist in terminated.
any sublibrary of the LIBDEF search chain for the CICS job. User response: If possible, correct the error and restart CICS,
otherwise cold start CICS.
If the message is produced during the post-initialization PLT Module: DFHRCRP
phase (DFHSIJ1), then the program was either not an installed
program entry or was not found in any sublibrary of the XMEOUT Parameter: applid
LIBDEF search chain for the CICS job. Destination: Console
modname indicates which of the modules issued the message.

progname is the name of the program which cannot be found. DFHSI1586 applid Recovery utility program not present
System action: If the response is 'CANCEL', CICS is Explanation: During emergency restart, the system
terminated. If the response is 'GO', the program is bypassed. initialization program (SIP) could not find the recovery utility
User response: Reply 'CANCEL' or 'GO'. program (DFHRUP).
Module: DFHSIPLT System action: A dump is provided, and CICS is abnormally
terminated.
XMEOUT Parameters: applid, modname,progname User response: Ensure that DFHRUP is in the CICS program
Destination: Console library, otherwise cold start CICS.
Module: DFHRCRP
DFHSI1580D applid PLTPI program program-name has XMEOUT Parameter: applid
abended, code abcode. Reply 'GO' or Destination: Console
'CANCEL'.
Explanation: CICS was processing the initialization program
list table (PLT) when the PLT program program-name abended DFHSI1587 applid Unable to link to program DFHAKP.
with abend code abcode. Explanation: CICS was unable to link to the activity keypoint
System action: If the response is 'CANCEL', CICS is program (DFHAKP) when attempting to take the initial
terminated. If the response is 'GO', the program is bypassed. keypoint for a CICS execution. In general DFHAKP will be
User response: Reply 'CANCEL' or 'GO'. missing from a sublibrary of the LIBDEF search chain for the
Module: DFHSIPLT CICS startup job stream.
XMEOUT Parameters: applid, program-name, abcode Other possible reasons for this error are:
Destination: Console v The dynamic storage area (DSA) is not large enough.

DFHSI1588D • DFHSI1596
v Group DFHAKP is not included in any group list specified

DFHSI1592 applid CICS applid not (yet) active to VTAM.
on the GRPLIST system initialization parameter.
Explanation: CICS initialization cannot OPEN the VTAM
access method control block (ACB) because VTAM does not
User response: Ensure that DFHAKP is in a sublibrary of the
recognize the APPLID (VTAM error X'5A'). There may be a
LIBDEF search chain for the CICS startup job stream.
user error in the value of APPLID (for example, on a SIT
If it is already present, then check that the DSA is large override) or the application subarea containing APPLID may
enough. Increase the size specified on the DSALIM system not be active in VTAM. Alternatively, it may be possible that
initialization parameter if it is too small. VTAM is still coming up. If so, the problem may correct itself
Module: DFHSII1 when VTAM completes its initialization.
System action: If this is an alternate CICS, wait for 15
XMEOUT Parameter: applid seconds and retry the OPEN indefinitely. If this is not an
Destination: Console alternate, CICS proceeds with the rest of initialization.
User response: In the case of an alternate, check that VTAM
DFHSI1588D applid Is startup to be continued? Reply 'GO' is on its way up. If it is, check that the required application
or 'CANCEL'. sub-area is active in VTAM. If it is, you may cancel this
Explanation: This message can appear after completion of alternate. If this is not an alternate, you can use CEMT to retry
emergency restart, or when an error occurs during CICS the OPEN when CICS has initialized.
startup. Module: DFHSIF1
System action: If you reply 'GO', CICS continues XMEOUT Parameter: applid
initialization. If you reply 'CANCEL', CICS either shuts down Destination: Console
normally if emergency restart has completed, or terminates
abnormally with a dump if an error has occurred during
initialization. DFHSI1594 applid A xxxx level of module progname is
User response: Reply 'GO' or 'CANCEL'. being loaded.
Module: DFHSII1 Explanation: The system is loading a level of module
progname that was not assembled against the current level of
XMEOUT Parameter: applid CICS in the CICS Transaction Server product. The level xxxx
Destination: Console shows the level of the module being used.
DFHSI1589D applid VTAM is not currently active. User response: Ensure that it is valid to use an old level of
Explanation: CICS initialization cannot OPEN the VTAM module progname. Usually, it will be necessary to reassemble
access method control block (ACB) because VTAM is not the module for the current level of CICS being used.
active. Module: DFHAPSIP
System action: If this is an alternate system, CICS waits for XMEOUT Parameters: applid, xxxx,progname
15 seconds and retries the OPEN indefinitely. Destination: Console
If this is not an alternate system, CICS proceeds with the rest
of initialization. The Open VTAM Retry transaction COVR is DFHSI1595S applid Failure to create a special purpose
attached, and retries the OPEN every 5 seconds for ten storage subpool - CICS will be terminated.
minutes. Explanation: An attempt to allocate a special purpose storage
User response: In the case of an alternate, check that VTAM subpool during CICS initialization has been unsuccessful.
is on its way up. If it is not, you can cancel this alternate System action: CICS initialization is terminated
system. User response: See Part 4 of the CICS Problem Determination
Module: DFHSIF1 Guide for guidance on how to proceed.
XMEOUT Parameter: applid Module: DFHSIDZ
DFHSI1590 applid XRF alternate cannot proceed without
VTAM. DFHSI1596 applid Nucleus module progname cannot be
Explanation: CICS initialization cannot OPEN the VTAM located.
access method control block (ACB). The ACB error code may Explanation: Nucleus module progname was not found in the
be found in the preceding message DFHSI1572. CICS library while loading the nucleus.
System action: CICS is terminated with a dump. System action: The AP domain initialization routines
User response: Refer to DFHSI1572 and use the information continue to attempt to load the remaining nucleus modules.
to try and resolve the causes of the errors. After trying to load all the nucleus modules, CICS is
Module: DFHSIF1 terminated.
User response: Add the missing module progname to the
XMEOUT Parameter: applid appropriate library and restart CICS.
Destination: Console Module: DFHAPSIP, DFHSID1

DFHSI1597 • DFHSI9000I
DFHSI1597 applid VTAM=YES invalid with a non VTAM DFHSI8420I applid About to link to PLT programs during
TCT - VTAM=NO forced. the second stage of initialization.
Explanation: The TCT loaded has not been assembled with Explanation: CICS is about to link to the user PLT programs
ACCESSMETHOD=VTAM but VTAM=YES was specified on defined in the PLTPI system initialization parameter during
the SIT. the second stage of initialization.
System action: CICS continues but without VTAM support. System action: Control is passed to the user PLT programs.
User response: To use VTAM, assemble the TCT with User response: None.
ACCESSMETHOD=VTAM or use the CICS supplied TCT Module: DFHSIPLT
which has a suffix of DY.
Module: DFHZINT XMEOUT Parameter: applid
DFHSI8424I applid Control returned from PLT programs
during the second stage of initialization.
DFHSI1599 applid CICS Partition size insufficient to Explanation: Control is returned to CICS to continue system
initialize transient data. initialization.
Explanation: Transient data initialization failed, either System action: Control is returned to CICS.
because an attempt to create a storage manager subpool failed User response: None.
or because an attempt to get storage failed. Module: DFHSIPLT
System action: A system dump is produced, and CICS is
abnormally terminated. XMEOUT Parameter: applid
User response: Use the system dump to determine which Destination: Console
DSA is too small. Increase the size specified on the DSALIM
or EDSALIM system initialization parameter as appropriate. DFHSI8430I applid About to link to PLT programs during
Module: DFHSID1 the third stage of initialization.
XMEOUT Parameter: applid Explanation: CICS is about to link to the user PLT programs
Destination: Console defined in the PLTPI SIT parameter during the third stage of
initialization.
System action: Control is passed to the user PLT programs.
DFHSI1600S UNABLE TO LOAD CICS SYSTEM User response: None.
INITIALIZATION MODULE DFHSIP31. Module: DFHSIPLT
CDLOAD FAILED. R15=X'xxxx'
Explanation: CICS has been unable to load the system XMEOUT Parameter: applid
initialization module DFHSIP31. Destination: Console
The code in register 15 (X'xxxx') is the return code from the

CDLOAD macro. DFHSI8434I applid Control returned from PLT programs
System action: CICS terminates. during the third stage of initialization.
User response: See the z/VSE System Macros Reference manual Explanation: Control is returned to CICS to continue system
for the meaning of the CDLOAD return code. Use this code to initialization.
determine why the load failed. System action: Control is returned to CICS.
Module: DFHSIP User response: None.
Destination: Console Module: DFHSIPLT
DFHSI2810 applid CANCEL reply received. CICS is Destination: Console
terminating.
Explanation: A CANCEL reply has been received. DFHSI9000I applid CICS system initialization is complete.
System action: CICS terminates. Explanation: CICS has successfully completed its
User response: Refer to previous messages to determine what initialization and is ready for use by applications.
action to take. System action: Processing continues.
Module: DFHSII1, DFHSIPLT User response: None. This message is for information only.
XMEOUT Parameter: applid This message cannot be suppressed.
Destination: Console Module: DFHSIJ1
DFHSI2813 applid Program DFHRCEX cannot be found. Destination: Console
Explanation: CICS cannot find DFHRCEX in any sublibrary
of the LIBDEF search chain for the CICS startup job stream.
System action: CICS initialization terminates with a dump.
User response: To correct this error, place DFHRCEX in a
sublibrary of the LIBDEF search chain for the CICS startup job
stream.
Module: DFHSIJ1

DFHSK1101I • DFHSM0001
DFHSKxxxx messages
because error threshold has been reached
DFHSK1101I applid General purpose subtask terminated
Explanation: A general purpose subtask has failed several
abnormally - system completion code=
times while executing its own code. CICS has terminated the
X'xxxx'
task.
Explanation: A subtask attached by DFHSKP has completed
System action: CICS continues in degraded mode.
abnormally.
User response: Find out why the subtask failed.
System action: CICS continues in degraded mode.
Module: DFHSKP
User response: Find out why the subtask failed. xxxx is the
operating system completion code. XMEOUT Parameter: applid
Module: DFHSKP Destination: Console
XMEOUT Parameters: applid, X'xxxx'
Destination: Console DFHSK1106I applid Unable to authorize a general purpose
subtask - RC=nn
Explanation: The CICS subtask program issued the CICS
DFHSK1102I applid Unable to attach general purpose
SVC to CICS authorize the TCB of an VSE subtask. The SVC
subtask - system return code= X'xxxx'
returned the error response code nn. The possible values of nn
Explanation: DFHSKP has attempted to attach an operating
and their meanings are:
system subtask. The ATTACH has failed.
System action: CICS continues in degraded mode. nn Meaning
User response: Find out why the attach failed. xxxx is the 01 SVC service is not authorized.
operating system completion code. 02 Load of DFHASV failed.
Module: DFHSKP 03 Internal error in CICS SVC.
XMEOUT Parameters: applid, X'xxxx' 04 Internal error in CICS SVC. RB check failed.
Destination: Console 10 DFHAUTH TYPE=CHECK macro failed.
14 Invalid TCB address passed to DFHASV.
18 DFHAUTH TYPE=subtask AFCB storage failed.
DFHSK1103I applid ESTAEX macro failed in general 1C GETMAIN for subtask AFCB storage failed.
purpose subtask - system return code= 20 Main task AFCB version is pre-CICS 1.7.
X'xxxx' 24 Main task AFCB version is too large for the SVC
Explanation: A general purpose subtask issued an OS/390 version in use.
ESTAEX macro. xxxx is the nonzero response from VSE. Other The SVC has not been defined and installed as
System action: CICS continues in degraded mode. described in the CICS System Definition Guide.
User response: Inform the system programmer. System action: CICS continues. The CICS SVC may fail again
See "OS/390 API Return Codes" in section "VSE/Advanced if reinvoked by a general purpose subtask.
Functions Codes & SVC Errors" of z/VSE Messages and Codes - User response: Use the response code in the message to
Volume 1 for diagnostic information about the ESTAEX return determine the cause of the failure.
code. Module: DFHSKP
Module: DFHSKP
XMEOUT Parameters: applid, nn
XMEOUT Parameters: applid, X'xxxx' Destination: Console
DFHSK1104I applid General purpose subtask terminated
DFHSMxxxx messages
DFHSM0001 applid An abend (code aaa/bbbb) has occurred
occurred in module modname. This implies that there may be Message DFHME0116 is normally produced containing the
an error in the CICS code. Alternatively, unexpected data has symptom string for this problem.
been input, or storage has been overwritten. User response: Notify the system programmer. If CICS is still
applicable), followed by a 4-digit alphanumeric CICS code. Look up the VSE code, if there is one, in "OS/390 API Abend
The VSE code is a system completion code, for example 0C1. Codes" in section "VSE/Advanced Functions Codes & SVC
If an VSE code is not applicable, this field is filled with three Errors" of z/VSE Messages and Codes - Volume 1.
referring to a CICS message (for example, AKEA is a CICS Next, look up the CICS alphanumeric code in “Transaction
abend code; 1310 refers to message DFHTS1310). Abend Codes (CICS Transaction Server for VSE/ESA)” on
System action: An exception entry is made in the trace table. page 453. This tells you, for example, whether the error was a
A system dump is taken, unless you have specifically program check, an abend, or a runaway, and may give you
suppressed dumps in the dump table. some guidance concerning user response.
CICS continues unless you have specified in the dump table If module modname is not crucial to the running of your CICS
that CICS should terminate. If appropriate, an error return system, you may decide to continue to run and bring CICS

DFHSM0002 • DFHSM0006
down at a convenient time to resolve the problem. that CICS should terminate. If appropriate, an error return
If you cannot run without the full use of module modname you could be terminated by the caller ( for example, the domain
should bring CICS down in a controlled shutdown. manager, DFHDMDM). A message is issued to this effect.
You need further assistance from IBM to resolve this problem. Message DFHME0116 is normally produced containing the
See Part 4 of the CICS Problem Determination Guide for symptom string for this problem.
guidance on how to proceed. User response: Notify the system programmer. If CICS has
Module: DFHSMAD, DFHSMAR, DFHSMCK, DFHSMDM, not been terminated, it is necessary to decide whether the
DFHSMGF, DFHSMMCI, DFHSMMC2, DFHSMMF, problem is serious enough to bring CICS down.
DFHSMMG, DFHSMPQ, DFHSMPP, DFHSMSR, DFHSMST,
DFHSMSU, DFHSMSY, Since some CICS functions can use a lot of processor time, this
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname there may not be an error here. Usually, CICS purges a CICS
Destination: Console function which exceeds the runaway task time interval which
DFHSM0002 applid A severe error (code X'code') has parameter (ICVR is measured in milliseconds). This means
occurred in module modname. that module modname in the message is terminated and CICS
Explanation: An error has been detected in module modname. continues.
The code X'code' is the exception trace point ID which But if you have declared ICVR=0 and you consider that
uniquely identifies what the error is and where the error was module modname has gone into a loop, you have to terminate
detected. CICS in order to terminate the runaway function.
message) is made in the trace table. A system dump is taken, If CICS has terminated module modname, and you consider
unless you have specifically suppressed dumps in the dump that it was not a runaway, you should increase the ICVR time
table. interval. You have to bring CICS down at a suitable time to do
CICS continues unless you have specified in the dump table temporarily online, using the CEMT transaction.
code is sent to the caller of this domain. In this case, CICS If raising the ICVR time does not solve the problem, you need
could be terminated by the caller (for example, the domain further assistance from IBM. See Part 4 of the CICS Problem
manager, DFHDMDM). A message is issued to this effect. Determination Guide for guidance on how to proceed.
Module: DFHSMMCI, DFHSMST
symptom string for this problem. XMEOUT Parameters: applid, X'offset', modname
User response: This indicates a possible error in CICS code. Destination: Console
DFHSM0006 applid Insufficient storage to satisfy Getmain
CICS may not have been terminated. If the message occurs (code X'code') in module modname. VSE code
once and module modname is not crucial to the running of vsecode.
your CICS system, you may decide to continue to run and Explanation: Module modname attempted to acquire storage
bring CICS down at a convenient time to resolve the problem. but there was insufficient storage available to satisfy the
request.
of module modname, you should bring CICS down in a The code X'code' is the exception trace point ID which
controlled shutdown. uniquely identifies the place where the error was detected.
A description of the exception trace point ID, X'code', and the The code vsecode is the OS/390 GETMAIN return code.
data it contains, is in the CICS Trace Entries Handbook. System action: An exception entry is made in the trace table
(code X'code'). A system dump is taken, unless you have
You need further assistance from IBM to resolve this problem. specifically suppressed dumps in the dump table.
guidance on how to proceed. CICS continues unless you have specified in the dump table
Module: DFHSMAD, DFHSMAR, DFHSMCK, DFHSMGF, that CICS should terminate.
DFHSMMC2, DFHSMMF, DFHSMMG, DFHSMPQ, DFHSMPP
DFHSMSCP, DFHSMSR, DFHSMST, DFHSMSU, DFHSMSY If appropriate, an error return code is sent to the caller of this
XMEOUT Parameters: applid, X'code',modname (for example, the domain manager, DFHDMDM). A message is
Destination: Console issued to this effect.
DFHSM0004 applid A possible loop has been detected at symptom string for this problem.
offset X'offset' in module modname. User response: If CICS has been terminated by another
Explanation: A CICS function is taking more time to process module, look out for the relevant termination messages (from,
than CICS expects. A possible loop has been detected in for example, the domain manager), and look up the user
module modname at offset X'offset'. This is the offset of the response suggested for these messages.
detected.
which rights itself if more storage becomes available. If you
can manage without module modname, you may decide to
CICS continues unless you have specified in the dump table without the full use of all CICS modules, you should bring

DFHSM0102 • DFHSM0120I
CICS down in a controlled shutdown. symptom string for this problem.

A description of the exception trace point ID, X'code', and the
data it contains, is in the CICS Trace Entries Handbook. Note: Even if CICS is able to repair the storage, the storage
violation trap still remains inactive.
You can get diagnostic information about the GETMAIN User response: Use the exception trace point ID, X'code', to
return code by consulting "OS/390 API Abend Codes" in investigate the cause of the storage violation. A description of
section "VSE/Advanced Functions Codes & SVC Errors" of the exception trace point ID, and the data it contains, is in the
z/VSE Messages and Codes - Volume 1. CICS Trace Entries Handbook.
Try decreasing the limits of the CICS dynamic storage areas Module: DFHSMCK.
(DSAs), or increasing the VSE partition size. You can vary the XMEOUT Parameters: applid, X'code'
CICS DSAs dynamically using the DSALIM and EDSALIM Destination: Console
parameters on the CEMT master terminal command. To
increase the partition size you must bring CICS down.
Module: DFHSMDM. DFHSM0113I applid Storage protection is not active.
Explanation: This is an informatory message stating that
Destination: Console storage protection has not been requested and is not in effect
for this execution of CICS.
DFHSM0102 applid A storage violation (code X'code') has User response: None. You can suppress this message with
been detected by module modname. the system initialization parameter, MSGLVL=0. Storage
Explanation: A storage violation has been detected by protection can be enabled by specifying the system
module modname. The code X'code' is the exception trace point initialization parameter STGPROT=YES.
ID which uniquely identifies the type of storage violation. Module: DFHSMDM.
message) is made in the trace table. A system dump is taken, XMEOUT Parameter: applid
unless you have specifically suppressed dumps in the dump Destination: Console
table.
CICS continues unless you have specified in the dump table DFHSM0114 applid Storage protection was requested but
that CICS should terminate. the support is not available. Storage
protection is not active.
If you have enabled storage recovery (by specifying the
Explanation: This is an informatory message stating that
system initialization parameter STGRCVY=YES), CICS
attempts to repair the storage violation. Otherwise, the storage although storage protection was requested, it is not in effect
is left unchanged. for this execution of CICS because the necessary hardware
and/or operating system support is not available.
Message DFHME0116 is normally produced containing the System action: CICS continues.
symptom string for this problem. User response: None.
User response: Use the exception trace point ID, X'code', to Module: DFHSMDM.
investigate the cause of the storage violation. A description of
the exception trace point ID, and the data it contains, is in the XMEOUT Parameter: applid
CICS Trace Entries Handbook. Destination: Console
Module: DFHSMAR, DFHSMCK, DFHSMGF, DFHSMMC2,
DFHSMMF
DFHSM0115I applid Storage protection is active.
XMEOUT Parameters: applid, X'code',modname Explanation: This is an informatory message stating that
Destination: Console storage protection is requested and is in effect for this
execution of CICS.
DFHSM0103 applid A storage violation (code X'code') has
been detected by the storage violation trap.
Trap is now inactive. the system initialization parameter, MSGLVL=0.
Explanation: A storage violation has been detected by the Module: DFHSMDM.
storage violation trap, which may be enabled via the XMEOUT Parameter: applid
CHKSTSK or the CHKSTRM system initialization parameters Destination: Console
or via the CSFE transaction. The code X'code' is the exception
trace point ID which uniquely identifies the type of storage
violation detected. DFHSM0120I applid Reentrant programs will not be loaded
System action: CICS disables the storage violation trap. An into read-only storage.
exception entry (code X'code' in the message) is made in the Explanation: This is an informatory message stating that
trace table. A system dump is taken, unless you have read-only programs will not be loaded into read-only storage
specifically suppressed dumps in the dump table. for this execution of CICS. This is because
CICS continues unless you have specified in the dump table RENTPGM=NOPROTECT was specified as a system
that CICS should terminate. initialization parameter.
If you have enabled storage recovery (by specifying the User response: None.
system initialization parameter STGRCVY=YES), CICS
attempts to repair the storage violation. Otherwise, the storage You should not specify RENTPGM=NOPROTECT unless you
is left unchanged. wish to deliberately overwrite programs (to set breakpoints
while testing, for example).

DFHSM0122I • DFHSM0131
Module: DFHSMDM. then terminate CICS, in which case a message to this effect is
issued.
XMEOUT Parameter: applid User response: Ensure that the EDSALIM parameter is
Destination: Console specified correctly.
Ensure that the CICS partition size is large enough.
DFHSM0122I applid Limit of DSA storage below 16MB is Module: DFHSMDM.
dsalimitK.
Explanation: This message gives the limit dsalimit of the XMEOUT Parameters: applid, dsalimit
dynamic storage area (DSA) below the 16MB line. Destination: Console
DFHSM0129 applid Insufficient storage to allocate default
the message level system initialization parameter, MSGLVL=0.
size for DSA limit storage below 16MB
Module: DFHSMDM.
(dsalimitK).
XMEOUT Parameters: applid, dsalimit Explanation: Following message DFHSM0127, CICS has
Destination: Console reduced the requested storage to the default size for the
DSALIM system initialization parameter but the request has
still failed.
DFHSM0123I applid Limit of DSA storage above 16MB is System action: The storage manager makes an exception
edsalimitM. entry in the trace table.
Explanation: This message gives the limit edsalimit of the
dynamic storage area (DSA) above the 16MB line. An error return code is sent to the domain manager,
System action: CICS continues. DFHDMDM, (the caller of storage manager). The domain
User response: None. You can suppress this message with manager might then terminate CICS, in which case a message
the message level system initialization parameter, MSGLVL=0. to this effect is issued.
Module: DFHSMDM. User response: See DFHSM0127 for further information.
XMEOUT Parameters: applid, edsalimit Ensure that the CICS partition size is large enough.
Destination: Console Module: DFHSMDM
XMEOUT Parameters: applid, dsalimit

DFHSM0127 applid Insufficient storage to allocate Destination: Console
requested size for DSA limit storage below
16MB (dsalimitK).
DFHSM0130 applid Insufficient storage to allocate default
Explanation: CICS has issued a requested for the maximum
size for DSA limit storage above 16MB
dsalimit of DSA storage below 16MB, but the request has
(dsalimitM).
failed.
Explanation: Following message DFHSM0128, CICS has
System action: If the requested size is greater than the
reduced the requested storage to the default size for the
default, CICS reissues the request using the default size for the
EDSALIM system initialization parameter but the request has
DSALIM parameter.
still failed.
If the requested size is not greater than the default, the storage System action: The storage manager makes an exception
manager makes an exception entry in the trace table. An error entry in the trace table.
return code is sent to the domain manager DFHDMDM (the
An error return code is sent to the domain manager,
caller of the storage manager). The domain manager might
DFHDMDM, (the caller of storage manager). The domain
then terminate CICS, in which case a message to this effect is
manager might then terminate CICS, in which case a message
issued.
to this effect is issued.
User response: Ensure that the DSALIM system initialization
User response: See DFHSM0128 for further information.
parameter is specified correctly.
Module: DFHSMDM
Module: DFHSMDM.
DFHSM0131 applid CICS is under stress (short on storage

DFHSM0128 applid Insufficient storage to allocate
below 16MB).
requested size for DSA limit storage above
Explanation: This message is produced when there is a
16MB (dsalimitM).
shortage of storage in any of the dynamic storage areas
Explanation: CICS has issued a request for the maximum
(DSAs) below 16MB. Either the largest free area in one of the
dsalimit of DSA storage above 16MB, but the request failed.
DSAs is less than the size of the internally defined cushion for
System action: If the requested size is greater than the
that DSA, or there is at least one transaction suspended due to
default, CICS reissues the request using the default size for the
insufficient contiguous free storage.
EDSALIM parameter.
If the requested size is not greater than the default, the storage to record the event.
manager makes an exception entry in the trace table. An error
CICS continues to operate but takes steps to alleviate the
return code is sent to the domain manager DFHDMDM (the
situation by, for example, slowing down the rate at which new
caller of the storage manager). The domain manager might
tasks are started and by releasing storage occupied by

DFHSM0132 • DFHSM0300
programs which are not currently in use. have been rounded up to a multiple of 256K (or 1M for the
User response: No immediate action is required. However, if UDSA if transaction isolation is in effect) and an above the
the problem persists you could increase the value of the line DSA size specified via the SIT override will have been
DSALIM system initialization parameter, if possible, or reduce rounded up to a multiple of 1M.
the storage requirements below 16MB of your CICS system. System action: An error return code is sent to the domain
For more information about how to do this, see the CICS manager, DFHDMDM, (the caller of storage manager). The
Performance Guide. domain manager might then terminate CICS, in which case a
Module: DFHSMSY message to this effect is issued.
User response: Either reduce the value specified in the
XMEOUT Parameter: applid xDSASZE parameter, or increase the value specified in the
Destination: Console xDSALIM parameter.
Module: DFHSMDM
DFHSM0132 applid CICS is no longer short on storage XMEOUT Parameters: applid, dsasize,dsaname
below 16MB. Destination: Console
Explanation: The short on storage condition reported by
message DFHSM0131 has ceased.
System action: CICS continues. DFHSM0136I applid The size of the dsaname was specified
User response: None. as dsasizeK.
Module: DFHSMSY. Explanation: This is an informatory message giving the size
dsasize of the dynamic storage area (DSA) dsaname.
XMEOUT Parameter: applid System action: CICS continues.
Destination: Console User response: None. You can suppress this message with
DFHSM0133 applid CICS is under stress (short on storage Module: DFHSMDM
above 16MB). XMEOUT Parameters: applid, dsaname,dsasize
Explanation: There is a shortage of storage in one of the Destination: Console
dynamic storage areas (DSAs) above the 16MB line. Either the
largest free area in one of the DSAs is less than the size of the
internally defined cushion for that DSA, or there is at least one DFHSM0300 DFHSMUTL ERROR REPORT
transaction suspended due to insufficient contiguous free Explanation: This is the report from the local catalog storage
storage. manager domain subpool record manipulation program,
System action: An exception entry is made in the trace table DFHSMUTL. A number of lines may be written to the report:
to record the event. DFHSM0300 DFHSMUTL REPORT
Report header.
CICS continues to operate but takes steps to alleviate the ADD SUBPOOL=xxxxxxxx PROCESSED SUCCESSFULLY
situation by, for example, slowing down the rate at which new ADD SUBPOOL=xxxxxxxx has been processed
tasks are started and by releasing storage occupied by successfully.
programs which are not currently in use. DEL SUBPOOL=xxxxxxxx PROCESSED SUCCESSFULLY
User response: No immediate action is required. However, if DEL SUBPOOL=xxxxxxxx has been processed
the problem persists you could, if possible, increase the value successfully.
of the EDSALIM system initialization parameter, or reduce the FOUND DFHLCD RECORD SMSUBPOL=xxxxxxxx
storage requirements of your CICS system above the 16MB Subpool record found by the LST command.
line. For guidance on how to do this, see the CICS Performance ERROR OPENING DFHLCD
Guide. An error has occurred opening the local catalog data
Module: DFHSMSY set. The program is terminated.
XMEOUT Parameter: applid UNRECOGNISED VERB xxx IN INPUT
Destination: Console Only ADD, DEL and LST are allowed. The statement
is ignored.
UNRECOGNISED OPERAND xxxxxxxx IN INPUT
DFHSM0134 applid CICS is no longer short on storage Only ADD SUBPOOL=xxxxxxxx or DEL
above 16MB. SUBPOOL=xxxxxxxx are allowed. The statement is
Explanation: The short on storage condition reported by ignored.
message DFHSM0133 has ceased. ERROR PROCESSING 'ADD SUBPOOL=xxxxxxxx'. R15 =
System action: CICS continues. X'yy'. RPL FEEDBACK CODE = X'zz'.
User response: None. A VSAM error has occurred whilst processing an
Module: DFHSMSY. ADD SUBPOOL=xxxxxxxx command. For the
meaning of the VSAM codes, refer to section
"VSE/VSAM Codes" in z/VSE Messages and Codes -
Volume 2. The program is terminated.
ERROR PROCESSING 'DEL SUBPOOL=xxxxxxxx'. R15 =
DFHSM0135 applid Insufficient storage to allocate the X'yy'. RPL FEEDBACK CODE = X'zz'.
requested size of dsasizeK for the dsaname. A VSAM error has occurred whilst processing a DEL
Explanation: CICS has attempted to allocate the requested SUBPOOL=xxxxxxxx command. For the meaning of
size of dsasize for the dsaname but there is insufficient storage the VSAM codes, refer to section "VSE/VSAM
to satisfy the request. Note that a below the line dynamic Codes" in z/VSE Messages and Codes - Volume 2. The
storage area (DSA) size specified via the SIT override will program is terminated.

END OF DFHSMUTL REPORT Module: DFHSMUTL

Report trailer. Destination: SYSLST
System action: See Explanation.
User response: If an error is reported, correct the cause and
retry.
DFHSNxxxx messages
DFHSN0001 applid An abend (code aaa/bbbb) has occurred
Module: DFHSNUS, DFHSNAS, DFHSNPU, DFHSNSU,
DFHSNTU, DFHSNXR
been input, or storage has been overwritten.
XMEOUT Parameters: applid, X'code',progname
If an VSE code is not applicable, this field is filled with three DFHSN0004 applid A possible loop has been detected at
hyphens. The CICS code is an abend code or a number offset X'offset' in module modname.
referring to a CICS message (for example, AKEA is a CICS Explanation: A CICS function is taking more time to process
abend code; 1310 refers to message DFHTS1310). than CICS expects. A possible loop has been detected in
System action: An exception entry is made in the trace table. module modname at offset X'offset'. This is the offset of the
A system dump is taken, unless you have specifically instruction which was executing at the time the error was
suppressed dumps in the dump table. detected.
CICS continues unless you have specified in the dump table System action: An exception entry is made in the trace table.
that CICS should terminate. If appropriate, an error return A system dump is taken, unless you have specifically
code is sent to the caller of this domain. In this case CICS suppressed dumps in the dump table.
could be terminated by the caller ( for example, the domain CICS continues unless you have specified in the dump table
manager, DFHDMDM). A message is issued to this effect. that CICS should terminate. If appropriate, an error return
Message DFHME0116 is normally produced containing the code is sent to the caller of this domain. In this case CICS
symptom string for this problem. could be terminated by the caller ( for example, the domain
User response: Notify the system programmer. If CICS is still manager, DFHDMDM). A message is issued to this effect.
running, it is necessary to decide whether to terminate CICS. Message DFHME0116 is normally produced containing the
Look up the VSE code, if there is one, in "OS/390 API Abend symptom string for this problem.
Codes" in section "VSE/Advanced Functions Codes & SVC User response: Notify the system programmer. If CICS has
Errors" of z/VSE Messages and Codes - Volume 1. not been terminated, it is necessary to decide whether the
Next, look up the description of the CICS alphanumeric code
in “Transaction Abend Codes (CICS Transaction Server for Since some CICS functions can use a lot of processor time, this
VSE/ESA)” on page 453. This tells you, for example, whether message may have been caused by a long-running function. So
the error was a program check, an abend, or a runaway, and there may not be an error here. Usually, CICS purges a CICS
may give you some guidance concerning user response. function which exceeds the runaway task time interval which
If module modname is not crucial to the running of your CICS parameter (ICVR is measured in milliseconds). This means
system, you may decide to continue to run and bring CICS that module modname in the message is terminated and CICS
down at a convenient time to resolve the problem. continues.
If you cannot run without the full use of module modname you But if you have declared ICVR=0 and you consider that
should bring CICS down in a controlled shutdown. module modname has gone into a loop, you have to terminate
See Part 4 of the CICS Problem Determination Guide for If CICS has terminated module modname, and you consider
guidance on how to proceed. that it was not a runaway, you should increase the ICVR time
Module: DFHSNUS, DFHSNAS, DFHSNPU, DFHSNSU, interval. You have to bring CICS down at a suitable time to do
DFHSNTU, DFHSNXR 0 this permanently. But you can change the ICVR time interval
temporarily online, using the CEMT transaction.
Destination: Console If raising the ICVR time does not solve the problem, you will
need further assistance from IBM to resolve this problem. See
DFHSN0002 applid A severe error (code X'code') has how to proceed.
occurred in program progname. Module: DFHSNUS, DFHSNAS, DFHSNPU, DFHSNSU,
Explanation: CICS has detected a severe error while running DFHSNTU, DFHSNXR
module progname. This error is associated with exception trace
point ID code. For further information about CICS exception XMEOUT Parameters: applid, X'offset', modname
trace entries, refer to the CICS Problem Determination Guide. Destination: Console
System action: The task issuing the signon abends.

DFHSN1100 • DFHSN1107
DFHSN1100 date time applid Signon at {netname |console | DFHSN1104 date time applid Signon at {netname |console |
terminal }portname by user userid in group terminal }portname by user userid has failed.
groupid is complete. New password not allowed.
Explanation: Terminal portname has been signed on. It now Explanation: A signon has been issued from terminal
has the security attributes for userid userid in group groupid. portname which attempted to change the password to a value
System action: Processing continues. that the external security manager (ESM) does not allow.
User response: The user at terminal portname can now use System action: The signon request is rejected.
those CICS transactions permitted for this userid in group User response: None, unless this implies a breach of security
groupid. that needs investigating.
Module: DFHSNTU Module: DFHSNTU
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
3=terminal }, portname, userid,groupid 3=terminal }, portname, userid
Destination: CSCS Destination: CSCS
terminal }portname has failed. User userid not terminal }portname by user userid requires a
recognized. password.
Explanation: A signon has been issued from terminal Explanation: A signon has been issued from terminal
portname which specified a userid userid that is not known to portname which did not specify a password. The signon has
the ESM. been rejected because user userid requires a password.
System action: The signon request is rejected. System action: The signon request is rejected.
User response: Unless this implies a breach of security that User response: None, unless this implies a breach of security
needs investigating, contact your security administrator so that that needs investigating.
the userid can be made known to the ESM. Module: DFHSNTU
Module: DFHSNTU
XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, 3=terminal }, portname, userid
3=terminal }, portname, userid Destination: CSCS
Destination: CSCS
DFHSN1106 date time applid Signon at {netname |console |

DFHSN1102 date time applid Signon at {netname |console | terminal }portname by user userid requires a
terminal }portname by user userid has failed. new password.
Password not recognized. Explanation: A signon has been issued from terminal
Explanation: A signon has been issued from terminal portname for which the external security manager (ESM)
portname which specified an incorrect password. indicates the password has expired.
This was probably caused by a misspelling of the password or This does not imply a security breach. It is a normal response
because the password is not valid for this userid. indicating that the ESM password has expired.
User response: None, unless this implies a breach of security User response: None.
that needs investigating. Module: DFHSNTU
Module: DFHSNTU
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, 3=terminal }, portname, userid
3=terminal }, portname, userid Destination: CSCS
Destination: CSCS

DFHSN1103 date time applid Signon at {netname |console | terminal }portname by user userid requires an
terminal }portname by user userid has failed. OID card.
OID card damaged or not authorized. Explanation: A signon has been issued from terminal
Explanation: A signon has been issued from terminal portname which did not use an operator identification (OID)
portname which used an unauthorized or damaged operator card when the external security manager (ESM) indicates that
identification (OID) card. one should have been used.
User response: None, unless this implies a breach of security User response: None, unless this implies a breach of security
that needs investigating. which needs investigating.
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
3=terminal }, portname, userid 3=terminal }, portname, userid

terminal }portname by user userid has failed. terminal }portname by user userid has failed.
SAF codes are (X'safresp',X'safreas'). ESM codes Signon is not allowed at a surrogate terminal
are (X'esmresp',X'esmreas'). except by use of the CRTE transaction.
Explanation: A signon has been issued from terminal Explanation: CICS does not support the signing on of
portname and has been rejected by the external security surrogate terminals, except when done during a CRTE routing
manager (ESM). session.
System action: The signon request is rejected. System action: Processing continues.
User response: The response and reason codes (safresp and User response: Investigate how and why users are
safreas) returned by the system authorization facility (SAF), attempting to use signon via transaction routing.
and the response and reason codes (esmresp and esmreas) Module: DFHSNTU
issued by the RACROUTE REQUEST=VERIFY or RACROUTE XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
REQUEST=EXTRACT macros. For the meaning of the 3=terminal }, portname, userid
response and reason codes in the message see "BSM Return Destination: CSCS
Errors" of z/VSE Messages and Codes - Volume 1. DFHSN1116 date time applid Signon at {netname |console |
Module: DFHSNTU terminal }portname by user userid has failed
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, because the national language to be used is
3=terminal }, portname, userid,X'safresp', X'safreas', not supported in this run of CICS.
X'esmresp',X'esmreas' Explanation: The national language specified has been
Destination: CSCS recognized as a valid IBM national language. However, either
this language cannot be specified as a valid national language
for CICS initialization, or CICS has not been initialized with
DFHSN1112 date time applid Signon at {netname |console | this language in the current run of CICS.
terminal }portname by user userid has failed
because the terminal has preset security. See the CICS Problem Determination Guide for a list of national
Explanation: A signon has been issued from terminal languages that CICS can be initialized to use.
portname. This terminal has been defined to CICS with fixed System action: Signon fails.
security attributes. It does NOT support signon. User response: Retry signon with a national language that
System action: The signon request is rejected. CICS has been initialized to use.
User response: None, unless this implies a breach of security Module: DFHSNTU
that needs investigating. XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
Module: DFHSNTU 3=terminal }, portname, userid
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, Destination: CSCS
3=terminal }, portname, userid
Destination: CSCS DFHSN1117 date time applid Signon at {netname |console |
DFHSN1113 date time applid Signon at {netname |console | because an invalid national language was
terminal }portname by user userid has failed selected.
because the terminal was already signed on. Explanation: Signon failed because the language specified
Explanation: A signon has been issued from terminal was not recognized as an IBM national language.
portname while a previous signon was still in effect for this System action: Signon fails.
terminal. User response: Retry signon with a correct language value.
System action: The signon request is rejected. Module: DFHSNTU
User response: None, unless this implies a breach of security XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
which needs investigating. 3=terminal }, portname, userid
Module: DFHSNTU Destination: CSCS
3=terminal }, portname, userid DFHSN1118 date time applid Signon at {netname |console |
Destination: CSCS terminal }portname by user userid has failed
because the user is not authorized to use the
DFHSN1114 date time applid Signon by user userid has terminal.
failed because there is no terminal associated Explanation: A signon has been issued from terminal
with the requesting task. portname which has failed. The user is not authorized to use
Explanation: A signon has been issued by user userid from a the terminal.
task that had been started without a terminal. System action: The signon request is rejected.
System action: The signon request is rejected. User response: Contact your security administrator, who
User response: Investigate why a signon has been issued should check if the user should be authorized to use terminal
from a task that is not associated with a terminal. portname.
Module: DFHSNTU In particular, check if the user should be able to access the
XMEOUT Parameters: date, time,applid, userid system on this particular day and time and whether the
Destination: CSCS terminal may be used on this day and time.
Module: DFHSNTU
3=terminal }, portname, userid

Destination: CSCS
terminal }portname by user userid failed
DFHSN1119 date time applid Signon at {netname |console | because the userid was not found in the
terminal }portname by user userid has failed specified group.
because the user is not authorized to use Explanation: A signon has been issued from terminal
application applname. portname which has failed. Either the userid is not in the
Explanation: A signon has been issued from terminal specified group, or the group specified for this user to be
portname which has failed. The user is not authorized to use associated with after signon is not known to the ESM.
the application applname. System action: The signon request is rejected.
v If you are using XRF, applname is the generic applid User response: Check that the groupid specified is correct. If
specified as the first operand of the APPLID system it is, contact your security administrator to ensure that this
initialization parameter. group is defined properly, and that the user is connected to
v Otherwise, applname is the application identifier specified as this group.
the single operand of the APPLID system initialization Module: DFHSNTU
parameter.
System action: The signon request is rejected. XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
User response: Contact your security administrator, who 3=terminal }, portname, userid
should check whether the user should have authorization to Destination: CSCS
use application applid.
Module: DFHSNTU
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, terminal }portname by user userid has failed
3=terminal }, portname, userid,applname because security is not active in this CICS
Destination: CSCS region.
Explanation: A signon has been issued from terminal
portname which has failed. This is because this CICS region is
DFHSN1120 date time applid Signon at {netname |console | running without security active.
terminal }portname by user userid has failed System action: The signon request is rejected.
because the {userid | group access} has been User response: None.
revoked. Module: DFHSNTU
Explanation: Either the userid, or the user's access to the
ESM group containing it, has been revoked by the ESM. This XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
is usually the result of repeated attempts to signon with an 3=terminal }, portname, userid
invalid password. Destination: CSCS
System action: The signon request is rejected.
User response: Contact your security administrator who can
DFHSN1132 date time applid Signon at terminal termid by
reauthorize the revoked userid or restore the user's access to
user userid has failed because the terminal is
the group.
a session.
Module: DFHSNTU
Explanation: A signon has been issued from terminal termid
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, which is a session. The security attributes of a session can only
3=terminal }, portname, userid,{1=userid, 2=group access} be changed on receipt of a valid FMH-5 attach header.
Destination: CSCS System action: The signon request is rejected.
User response: Investigate how and why users are
attempting to use signon for a session.
DFHSN1129 date time applid Signon at {netname |console | Module: DFHSNTU
because the user is already signed on XMEOUT Parameters: date, time,applid, termid, userid
elsewhere. Destination: CSCS
portname while the user is already signed on under the
restrictions imposed by the current setting of the SNSCOPE
because of an error during SNSCOPE
System action: The signon request is rejected.
checking.
User response: Investigate why users are attempting to
signon twice within the current signon scope.
portname. The SNSCOPE initialization parameter disallows
See the CICS System Definition Guide for more information signon to more than one terminal at a time. An internal failure
about the SNSCOPE parameter. during SNSCOPE checking means that CICS is unable to
Module: DFHSNTU confirm if the user is already signed on elsewhere. The failure
has occurred because the limit of concurrent OS/390 ENQ
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, requests has been reached.
3=terminal }, portname, userid System action: The signon request is rejected. Message
Destination: CSCS DFHUS0120 will have been written to the console. See the
explanation of this message for further information.
User response: Please report this problem to your CICS
systems programmer.

See the CICS System Definition Guide for more information

DFHSN1214 date time applid An attempted signoff has
about the SNSCOPE parameter.
failed because there was no terminal
Module: DFHSNTU
associated with the requesting task.
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, Explanation: A signoff has been issued from a task that had
3=terminal }, portname, userid been started without a terminal.
Destination: CSCS System action: The signoff request is rejected.
User response: Investigate why a signoff has been issued
from a task that is not associated with a terminal.
DFHSN1200 date time applid Signoff at {netname |console | Module: DFHSNTU
terminal }portname by user userid is complete.
tt transactions entered with nn errors. XMEOUT Parameters: date, time,applid
Explanation: Terminal portname has been signed off. It now Destination: CSCS
has the default security attributes.
nn indicates the number of errors which have occurred. DFHSN1215 date time applid Signoff at {netname |console |
System action: Processing continues. terminal }portname has failed. Signoff is not
User response: None. allowed at a surrogate terminal except by use
Module: DFHSNTU of the CRTE transaction.
Explanation: CICS does not support the signing off of
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, surrogate terminals, except when done during a CRTE routing
3=terminal }, portname, userid,tt, nn session.
Destination: CSCS System action: Processing continues.
DFHSN1211 date time applid Signoff at terminal termid has attempting to use signoff via transaction routing.
failed because the terminal is a session. Module: DFHSNTU
Explanation: A signoff has been issued from terminal termid XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
which is a session. The security attributes of a session can only 3=terminal }, portname
be changed on receipt of a valid FMH-5 attach header. Destination: CSCS
System action: The signoff request is rejected.
attempting to use signoff for a session. DFHSN1300 date time applid An attempt to reschedule BMS
Module: DFHSNTU pages for operator opid at {netname | console |
terminal }portname has failed following a
XMEOUT Parameters: date, time,applid, termid timeout. Pages on temporary storage queue
Destination: CSCS X'hexqueueid' may require cleanup.
Explanation: Operator opid has been timed out on terminal
DFHSN1212 date time applid Signoff at {netname |console | netname while viewing BMS pages. CICS has attempted to
terminal }portname has failed because the reschedule the pages so that they are available when the
terminal has preset security. operator signs on again, but the reschedule has failed.
Explanation: A signoff has been issued from terminal The pages are available on temporary storage queue
portname which has been defined to CICS with fixed security hexqueueid. This queue continues to exist until it is explicitly
attributes and so does not support signoff. disposed of.
System action: The signoff request is rejected. System action: Processing continues.
User response: None, unless this implies a breach of security User response: If you still need to view this data, repeat the
which needs investigating. processing which created the BMS pages.
XMEOUT Parameters: date, time,applid, {1=netname, 2=console, XMEOUT Parameters: date, time,applid, opid,
3=terminal }, portname {1=netname,2=console, 3=terminal }, portname, X'hexqueueid'
DFHSN1213 date time applid Signoff at {netname |console | DFHSN1400 date time applid Session signon for session
terminal }portname has failed because the session by user userid is complete.
terminal was not signed on. Explanation: The two CICS systems are connected and the
Explanation: A signoff has been issued from terminal MRO/ISC session is given the security authority of user userid.
portname while no previous signon was in effect. System action: The MRO/ISC sessions are signed on.
System action: The signoff request is rejected. User response: None.
User response: None, unless this implies a breach of security Module: DFHSNSU
which needs investigating.
Module: DFHSNTU XMEOUT Parameters: date, time,applid, session, userid
Destination: CSCS
3=terminal }, portname
Destination: CSCS

XMEOUT Parameters: date, time,applid, session, X'safresp',

DFHSN1401 date time applid Session signon for session
session by user userid has failed. SAF codes
Destination: CSCS
are (X'safresp',X'safreas'). ESM codes are
(X'esmresp',X'esmreas').
Explanation: An MRO/ISC signon is attempted by user DFHSN1604 date time applid Attach header signon at
userid but the signon has failed for the reason given. terminal termid by user userid has failed. SAF
System action: The session is not signed on. codes are (X'safresp',X'safreas'). ESM codes are
User response: The response and reason codes (safresp and (X'esmresp',X'esmreas').
safreas) returned by the system authorization facility (SAF), Explanation: User userid has failed the implicit signon for
and the response and reason codes (esmresp and esmreas) attach security.
returned by the external security manager (ESM) are those System action: The attach fails.
issued by the RACROUTE REQUEST=VERIFY or RACROUTE User response: The response and reason codes (safresp and
REQUEST=EXTRACT macros. For the meaning of the safreas) returned by the system authorization facility (SAF),
response and reason codes in the message see "BSM Return and the response and reason codes (esmresp and esmreas)
Codes" in section "VSE/Advanced Functions Codes & SVC returned by the external security manager (ESM) are those
Errors" of z/VSE Messages and Codes - Volume 1. issued by the RACROUTE REQUEST=VERIFY or RACROUTE
Module: DFHSNSU REQUEST=EXTRACT macros. For the meaning of the
response and reason codes in the message see "BSM Return
XMEOUT Parameters: date, time,applid, session, userid, X'safresp',
Destination: CSCS
Module: DFHSNUS
XMEOUT Parameters: date, time,applid, termid, userid, X'safresp',
DFHSN1410 date time applid Session signon for session
session with default security attributes is
Destination: CSCS
complete.
Explanation: The two CICS systems are connected and the
MRO/ISC session is given the security authority of the default DFHSN1605 date time applid Attach header signon at
user. terminal termid has failed. SAF codes are
System action: The MRO/ISC sessions are signed on. (X'safresp',X'safreas'). ESM codes are
User response: None. (X'esmresp',X'esmreas').
Module: DFHSNSU Explanation: The implicit signon for local user security has
failed.
XMEOUT Parameters: date, time,applid, session
System action: The attach fails.
Destination: CSCS
DFHSN1500 date time applid Session signoff for session and the response and reason codes (esmresp and esmreas)
session is complete. tt transactions entered returned by the external security manager (ESM) are those
with nn errors. issued by the RACROUTE REQUEST=VERIFY or RACROUTE
Explanation: An MRO/ISC session is signed-off. REQUEST=EXTRACT macros. For the meaning of the
nn indicates the number of abends which have occurred. Codes" in section "VSE/Advanced Functions Codes & SVC
System action: The security authority is removed from the Errors" of z/VSE Messages and Codes - Volume 1.
session. Module: DFHSNUS
Module: DFHSNSU XMEOUT Parameters: date, time,applid, termid, X'safresp',
XMEOUT Parameters: date, time,applid, session, tt, nn Destination: CSCS
Destination: CSCS
DFHSN1606 date time applid Attach header signoff at

DFHSN1501 date time applid Session signoff for session terminal termid has failed. SAF codes are
session has failed. SAF codes are (X'safresp',X'safreas'). ESM codes are
(X'safresp',X'safreas'). ESM codes are (X'esmresp',X'esmreas').
(X'esmresp',X'esmreas'). Explanation: The user has failed the implicit signoff for
Explanation: An MRO/ISC signoff is attempted but the attach security.
signoff has failed for the reason given. System action: Processing continues.
System action: Processing continues. User response: The response and reason codes (safresp and
User response: The response and reason codes (safresp and safreas) returned by the system authorization facility (SAF),
safreas) returned by the system authorization facility (SAF), and the response and reason codes (esmresp and esmreas)
and the response and reason codes (esmresp and esmreas) returned by the external security manager (ESM) are those
returned by the external security manager (ESM) are those issued by the RACROUTE REQUEST=VERIFY or RACROUTE
issued by the RACROUTE REQUEST=VERIFY or RACROUTE REQUEST=EXTRACT macros. For the meaning of the
REQUEST=EXTRACT macros. For the meaning of the response and reason codes in the message see "BSM Return
response and reason codes in the message see "BSM Return Codes" in section "VSE/Advanced Functions Codes & SVC
Codes" in section "VSE/Advanced Functions Codes & SVC Errors" of z/VSE Messages and Codes - Volume 1.
Errors" of z/VSE Messages and Codes - Volume 1. Module: DFHSNUS
Module: DFHSNSU

DFHSN1800 • DFHSO0001
XMEOUT Parameters: date, time,applid, termid, X'safresp', XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
X'safreas', X'esmresp', X'esmreas' 3=terminal }, portname, userid,X'safresp', X'safreas',
Destination: CSCS X'esmresp',X'esmreas'
Destination: CSCS

terminal }portname by preset user userid in DFHSN1850 date time applid Signoff at preset {netname |
group groupid is complete. console | terminal }portname is complete.
Explanation: The user userid, specified for preset security Explanation: The preset security terminal portname has been
terminal portname has been signed on to the external security signed off while the terminal was being deleted. Its security
manager (ESM). has been removed.
System action: The security attributes for this userid are used System action: Processing continues.
in all security requests issued against this terminal. User response: None.
Module: DFHSNPU
The terminal is now PRESET with this userid for its entire
duration. XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
User response: None. 3=terminal }, portname
Module: DFHSNPU Destination: CSCS
3=terminal }, portname, userid,groupid DFHSN1851 date time applid Signoff at preset {netname |
Destination: CSCS console | terminal } portname has failed. SAF
codes are (X'safresp',X'safreas'). ESM codes are
Explanation: The preset security terminal portname, could not
terminal }portname by preset user userid has
be signed off while the terminal was being deleted.
failed. SAF codes are (X'safresp',X'safreas').
Explanation: The user userid, specified for a preset security
terminal portname, could not be signed on to the external
security manager (ESM).
System action: The signon request is rejected and the
terminal cannot be put in service.
REQUEST=EXTRACT macros. For the meaning of the
Module: DFHSNPU
REQUEST=EXTRACT macros. For the meaning of the XMEOUT Parameters: date, time,applid, {1=netname, 2=console,
response and reason codes in the message see "BSM Return 3=terminal }, portname, X'safresp',X'safreas', X'esmresp', X'esmreas'
Codes" in section "VSE/Advanced Functions Codes & SVC Destination: CSCS
Module: DFHSNPU
DFHSOxxxx messages
DFHSO0001 applid An abend (code aaa/bbbb) has occurred
an error in the CICS code. Alternatively, unexpected data has Look up the VSE code, if there is one, in "OS/390 API Abend
been input, or storage has been overwritten. Codes" in section "VSE/Advanced Functions Codes & SVC
applicable), followed by a 4-digit alphanumeric CICS code. Next, look up the CICS alphanumeric code. This tells you, for
The VSE code is a system completion code, for example 0C1. example, whether the error was a program check, an abend, or
If an VSE code is not applicable, this field is filled with three a runaway, and may give you some guidance concerning user
hyphens. The CICS code is an abend code or a number response.
abend code; 1310 refers to message DFHTS1310). If module modname is not crucial to the running of your CICS
System action: An exception entry is made in the trace table. system, you may decide to continue to run and bring CICS
A system dump is taken, unless you have specifically down at a convenient time to resolve the problem. If you
suppressed dumps in the dump table. cannot run without the full use of module modname you
that CICS should terminate. If appropriate, an error return You need further assistance from IBM to resolve this problem.
code is sent to the caller of this domain. In this case CICS See Part 4 of the CICS Problem Determination Guide for
could be terminated by the caller ( for example, the domain guidance on how to proceed.
manager, DFHDMDM). A message is issued to this effect. Destination: Console
Module: DFHSOCK

DFHSO0002 • DFHSO0102
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname If you have specified system initialization parameter ICVR=0
and you consider that module modname is looping, you must
DFHSO0002 applid A severe error (code X'code') has
occurred in module modname. If CICS has terminated module modname, and you consider
Explanation: An error has been detected in module modname. that it was not a runaway, you should increase the value of
The code X'code' is the exception trace point ID which the ICVR system initialization parameter. You have to close
uniquely identifies what the error is and where the error was down CICS at a suitable time to do this permanently. You can
detected. change the ICVR time interval temporarily online using the
System action: An exception entry (code X'code' in the CEMT transaction.
If raising the ICVR time does not solve the problem, you may
need further assistance from IBM to resolve the problem. See
table.
CICS continues unless you have specified in the dump table how to proceed.
that CICS should terminate. If appropriate, an error return Destination: Console
code is sent to the caller of this domain. In this case, CICS Modules: DFHSOCK, DFHSOSE
XMEOUT Parameters: applid, X'offset',modname
symptom string for this problem. DFHSO0100I applid Sockets domain initialization has
User response: This indicates a possible error in CICS code. started.
The severity of its impact depends on the importance of the Explanation: This is an informational message indicating that
function being executed at the time of the error. sockets domain initialization has started.
CICS may not have been terminated. If the message occurs User response: None. The message can be suppressed with
once and module modname is not crucial to the running of the system initialization parameter MSGLVL=0.
your CICS system, you may decide to continue to run and Destination: Console
bring CICS down at a convenient time to resolve the problem. Module: DFHSODM
If the message recurs or if you cannot run without the full use XMEOUT Parameter: applid
DFHSO0101I applid Sockets domain initialization has
You need further assistance from IBM to resolve this problem. ended.
See Part 4 of the CICS Problem Determination Guide for Explanation: This is an informational message indicating that
guidance on how to proceed. sockets domain initialization has completed successfully.
Destination: Console System action: System initialization continues.
Modules: DFHSODM, DFHSOL, DFHSOCK, DFHSORD, User response: None. The message can be suppressed with
DFHSOIS. the system initialization parameter MSGLVL=0.
Module: DFHSODM
DFHSO0004 applid A possible loop has been detected at
Explanation: A CICS function is taking more time to process DFHSO0102 applid date time A Language Environment
than CICS expects. A possible loop has been detected in Callable Service error (code X'code') has
module modname at offset X'offset'. This is the offset of the occurred on receipt of a severe TCP/IP return
instruction which happened to be executing at the time when code; theTCPIPSERVICE tcpipservice on port
the error was detected. portnumber at IP address ipaddress will be
System action: An exception entry is made in the trace table. closed.
Explanation: An error has been detected in DFHSOCK. The
A system dump is taken unless you have specifically
error has been caused by a severe return code received from
suppressed the dump (by a user exit program at the XDUREQ
TCP/IP.
exit, in the dump table or by global system dump
System action: An exception entry X'code' is made in the
suppression). CICS processing continues unless you have
trace table. No system dump is taken, unless you have
specified in the dump table that CICS should terminate.
specifically requested a dump in the dump table. CICS
Message DFHME0116 is normally produced containing the continues unless you have specified in the dump table that
symptom string for this problem. CICS should terminate.
The TCPIPSERVICE tcpipservice on port portnumber at the
necessary to decide whether the problem is serious enough to
specified IP address will be shutdown. When this is complete
bring CICS down.
then message DFHSO0108 will be issued.
Since some CICS functions can use a lot of CPU time, this User response: This error could have been returned if
message may have been caused by a long-running function, TCP/IP had been shutdown, for example. The exception trace
and there may not be an error. Usually, CICS purges a CICS entry will tell you which service routine was called and the
function which exceeds the runaway task time interval that return values that were returned. Refer to the TCP/IP for
you have specified in the ICVR system initialization VSE/ESA Messages and Codes book to determine the cause of
parameter. This means that execution of module modname is the error.
terminated and CICS continues.
The TCPIPSERVICE tcpipservice will be closed, and after the

TCP/IP region has been restarted the closed TCPIPSERVICE CICS continues unless you have specified in the dump table
should be reopened. At this point normal work can resume on that CICS should terminate. If appropriate, an error return
the TCPIPSERVICE. code is sent to the caller of this domain. In this case, CICS
Destination: Console could be terminated by the caller (for example, the domain
Module: DFHSODM manager, DFHDMDM). A message is issued to this effect.
User response: This indicates a possible error in CICS code
XMEOUT Parameters: applid, date, time, X'code', tcpipservice, or the called Language Environment® Callable Service routine.
portnumber, ipaddress The exception trace entry will tell you which service routine
was called and the return values that were returned. The
DFHSO0103 applid ENCRYPTION=level is not available on severity of its impact depends on the importance of the
this system. function being executed at the time of the error.
Explanation: The ENCRYPTION=level system initialization CICS may not have been terminated. If the message occurs
parameter was specified, where level may be STRONG or once and module modname is not crucial to the running of
NORMAL, but the necessary support to implement it was not your CICS system, you may decide to continue to run and
installed with your SSL. bring CICS down at a convenient time to resolve the problem.
System action: Sockets Domain initialization fails, and CICS
terminates. If the message recurs or if you cannot run without the full use
User response: Ensure that your TCP/IP SSL version of module modname, you should bring CICS down in a
supports the requested level. controlled shutdown.
Destination: Console and Transient Data Queue CSOO
If the feature is unavailable, you must specify Module: DFHSOCK
ENCRYPTION=NORMAL, which is the default.
Destination: Console Routecodes 2, 9, 10 and 11 XMEOUT Parameters: date, time,applid, X'code', modname
Module: DFHSODM
XMEOUT Parameters: applid, level DFHSO0107 date time applid TCPIPSERVICE tcpipservice has
been opened on port portnumber at IP address
ipaddress.
DFHSO0104 applid Secure sockets program pgmname could Explanation: The TCPIPSERVICE tcpipservice has been
not be loaded. Secure Sockets Layer is not opened on port portnumber at the IP address specified.
available. System action: CICS continues.
Explanation: The program module pgmname, which is User response: None.
required to implement the secure sockets layer, could not be Destination: CSOO
loaded. Module: DFHSOCK
System action: System initialization continues, but support
for the secure sockets layer is not enabled. XMEOUT Parameters: date, time,applid, tcpipservice,
User response: If this message is preceded by message portnumber,ipaddress
DFHSO0103, try restarting CICS with
ENCRYPTION=NORMAL.
Destination: Console Routecodes 2, 9, 10 and 11 DFHSO0108 date time applid TCPIPSERVICE tcpipservice on
Module: DFHSODM port portnumber at IP address ipaddress has
been closed.
XMEOUT Parameters: applid, pgmname Explanation: The TCPIPSERVICE tcpipservice on port
portnumber on the specified IP address has been closed.
DFHSO0105 applid ENCRYPTION=level is not available on User response: None.
this system. ENCRYPTION=WEAK is used Destination: CSOO
instead. Module: DFHSOCK
Explanation: The ENCRYPTION=NORMAL system
initialization parameter was specified, but the necessary XMEOUT Parameters: date, time,applid, tcpipservice,
support to implement it was not installed on your system via portnumber,ipaddress
TCP/IP.
System action: The lower level of encryption corresponding
to ENCRYPTION=WEAK is used instead. DFHSO0109 date time applid The TCPIPSERVICE
User response: None. tcpipservice could not be opened because the
Destination: Console Routecodes 2, 9, 10 and 11 port portnumber is already in use on the IP
Module: DFHSODM address ipaddress.
Explanation: This message is issued when the open of a
XMEOUT Parameters: applid, level TCPIPSERVICE cannot be completed. The port number
specified is already in use in combination with the IP address.
By default, TCP/IP only allows one server to be listening on a
DFHSO0106 date time applid A Language Environment port at any one time.
Callable Service error (code X'code') has
occurred in module modname. Specifically, this message is issued when the TCP/IP bind call
Explanation: An error has been detected in module modname. fails with a return code of EADDRINUSE.
The code X'code' is the exception trace point ID which System action: The TCPIPSERVICE does not open, but
uniquely identifies what the error is and where the error was remains closed. An exception trace entry is written detailing
detected. the return values from the TCP/IP bind call. An application
System action: An exception entry (code X'code' in the using the EXEC API to set the TCPIPSERVICE open receives
message) is made in the trace table. A system dump is taken, an RESP(INVREQ) RESP2(9).
unless you have specifically suppressed dumps in the dump User response: Check that there are no other
table. TCPIPSERVICES open using the same port number and IP

address as the failing one. If there is another TCPIPSERVICE System action: The TCPIPSERVICE is not opened. If an
open using the port, it must be closed before the new one can application has used the EXEC API to open the
be opened. TCPIPSERVICE, it receives RESP(INVREQ) RESP2(4) values.
User response: Open TCPIP and re-open the TCPIPSERVICE.
If no TCPIPSERVICES are using the requested port, there may Destination: CSOO
be another z/VSE application acting as a TCP/IP server Module: DFHSORD
already listening on the port. Attempting to open a
TCPIPSERVICE on an already used port will fail. Choose an XMEOUT Parameters: date, time,applid, tcpipservice
unused port for the TCPIPSERVICE.
If your z/VSE system has more than one TCP/IP stack you DFHSO0113 applid The IP address ip_address cannot be
may specify another stack's IP address on the TCPIPSERVICE resolved to a host name by the gethostbyaddr
definition. This will allow you to install multiple function.
TCPIPSERVICES each using the same port number. Explanation: CICS has issued the TCP/IP function
Destination: CSOO gethostbyaddr to resolve the IP address ip_address to a host
Module: DFHSOCK name, but the call failed.
System action: An exception trace entry is made. CICS will
XMEOUT Parameters: date, time,applid, tcpipservice,
continue to attempt to access the name server for subsequent
portnumber,ipaddress
requests.
User response: The gethostbyaddr function will usually
DFHSO0110 date time applid The TCPIPSERVICE perform a name server reverse lookup to resolve the IP
tcpipservice cannot be opened on the IP address into a host name. This can fail if CICS is unable to
address ipaddress because the address is contact a name server, or the name server does not know the
unknown to TCP/IP. correct host name to IP address mapping.
Explanation: Opening the TCPIPSERVICE has failed because Check that the name server defined to TCP/IP via the SET
the IP address specified on the definition is not known to DNS1 command is valid and responding correctly. If the name
TCP/IP. server is defined correctly to TCP/IP then contact the
This message is issued when the TCP/IP bind call fails with administrator to determine why the IP address lookup has
the return value of EADDRNOTAVAIL. failed.
System action: The IP address must be a valid address Destination: Console
known to TCP/IP. If the system only has one IP address then Module: DFHSOIS
the IP address field of the TCPIPSERVICE definition can be Destination: Console
left blank, or filled with the string INADDR_ANY. This causes Module: XMEOUT Parameters: applid, ip_address
the bind to use the default IP address for the system. To use
an alternative, a valid address must be specified.
DFHSO0114 date time applid The socket listener cannot
User response: Check that the address specified on the
attach the transaction transaction, the
TCPIPSERVICE definition is known to TCPIP on the system.
TCPIPSERVICE tcpipservice will be closed.
Destination: CSOO
Explanation: The TCP/IP listener task has received a
Module: DFHSOCK
connection from a client but the attach for the transaction
XMEOUT Parameters: date, time,applid, tcpipservice, ipaddress associated with the TCPIPSERVICE definition has failed. The
associated transaction may not have been installed or the
TCPIPSERVICE definition could have specified the wrong
DFHSO0111 date time applid Opening the TCPIPSERVICE transaction.
tcpipservice has failed because the region System action: The TCPIPSERVICE that is defined on the
userid is not authorized to bind to port port that the connection arrived on is closed. The socket
portnumber. accepted for the client is closed.
Explanation: Opening the TCPIPSERVICE has failed because User response: Determine why the attach for the transaction
the userid of the region is not authorized to use the port has failed. Correct the error and re-open the TCPIPSERVICE.
number specified. Destination: CSOO
Module: DFHSOCK
This message is issued when the TCP/IP bind call fails with a
return value of EPERM. XMEOUT Parameters: date, time,applid, transaction, tcpipservice
System action: The TCPIPSERVICE is not opened. If an
application has used the EXEC API to open the
TCPIPSERVICE, it receives RESP(INVREQ) RESP2(3) values. DFHSO0115 date time applid CICS has registered the group
User response: The CICS region's userid must be authorized name groupname with Work Load Manager.
to open the specified port. The TCP/IP host name genericname will
Destination: CSOO become available for DNS connection
Module: DFHSOCK optimization.
Explanation: The group name has been registered with Work
XMEOUT Parameters: date, time,applid, tcpipservice, portnumber Load Manager for Domain Name Service (DNS) connection
optimization. This occurs when a TCPIPSERVICE is opened
where its name begins with the character 'D'. The new generic
DFHSO0112 date time applid TCPIPSERVICE tcpipservice
TCP/IP host name becomes available for clients to use to
cannot be opened because TCPIP status is
access the CICS system, and any others that have registered
not OPEN.
with the named group name.
Explanation: Opening the TCPIPSERVICE has failed because
System action: CICS has issued the Work Load Manager
TCPIP is currently not open. Either TCPIP=NO has been
macro IWMSRSRG to register the specified group name for
specified in the SIT or TCPIP has been dynamically closed
DNS connection optimization. This only occurs when the
using CEMT or an SPI command.
name of the TCPIPSERVICE begins with a 'D'. Work Load

manager registration only occurs once for a given group name.

DFHSO0117 applid Unable to determine the TCP/IP host
If multiple TCPIPSERVICES define the same group name, then
name. Language Environment return code
registration will only occur once.
X'retcode', reason code X'rc'. TCP/IP services
The group name registered is taken from a combination of are unavailable.
part of the name of the TCPIPSERVICE and the transaction Explanation: Language Environment has returned a non-zero
defined for the TCPIPSERVICE. Any characters of the name return code/reason code to a gethostname call during Listener
following a dot '.' are concatenated onto the transaction initialization.
identifier to form the group name. For example, a System action: Listener initialization terminates. The CICS
TCPIPSERVICE has the name D1.CICS and is defined with the region does not open its TCP/IP interface.
transaction IIOP (The IIOP transaction being an alias of the User response: Determine the reason for the gethostname
CICS supplied CIOR transaction). The group name generated failure. The return code and reason code included in the
is 'CICSIIOP'. If the TCPIPSERVICE name does not contain a message text are described in the TCP/IP for VSE/ESA
dot, then only the transaction identifier is used. For example, a Messages and Codes manual.
TCPIPSERVICE with a name of 'DYNWEB' and a transaction Destination: Console
of WWW will generate a registration for the group 'WWW'. Module: DFHSOCK
The group name registered effectively becomes a new name in XMEOUT Parameters: applid, X'retcode',X'rc'
the sysplex TCP/IP domain. When multiple CICS systems in a
sysplex each register with the same group name, the DNS
server uses Work Load Manager to resolve the group name DFHSO0119 applid Unable to register service servicename
into one of the IP addresses of the associated systems. The IP for WLM DDNS on host hostname.
address returned is that of the system that is most eligible Explanation: During activation of a TCPIPSERVICE, the
according to Work Load Manager's load balancing rules. For Sockets Domain was unable to locate a TCP/IP name server.
example, two OS/390® systems in a sysplex are Without a name server, CICS cannot obtain the information
necessary for registration with WLM DDNS.
mvs1.plex.hursley.ibm.com and mvs2.plex.hursley.ibm.com;
System action: TCPIPSERVICE activation continues, but this
and on each system, CICS registers with the group name
service is not registered with WLM DDNS.
cicsiiop. The new name cicsiiop.plex.hursley.ibm.com is
User response: Determine why no name server was found.
dynamically added to the DNS name servers tables. Client
Message DFHSO0113 may have preceded this message. Once
TCP/IP applications can use this name instead of the name of
the name server has been activated, re-install the
one of the specific OS/390 images. When a client resolves the
TCPIPSERVICE.
name to an IP address using the DNS, it will get the IP
address of the most eligible system. Since the DNS
Module: DFHSOCK
dynamically knows when systems register and de-register,
additional CICS systems can be registered as required to XMEOUT Parameters: applid, servicename,hostname
expand the list of available IP addresses returned for a group
name. If a system fails, its IP address will be removed from
the DNS server's list of associated addresses for any groups DFHSO0120 applid numtcbs TCBs are initialized for SSL
with which it was registered. processing.
User response: No user action is necessary. Explanation: The specified number (numtcbs) of TCBs have
Destination: CSOO been attached and initialized to perform Secure Sockets Layer
Module: DFHSOCK processing for CICS.
System action: CICS can handle numtcbs simultaneous SSL
XMEOUT Parameters: date, time,applid, groupname, genericname sessions.
Destination: Console Routecodes 2 and 10
DFHSO0116 date time applid CICS has de-registered the
Module: DFHSOSE
group name groupname with Work Load
Manager. XMEOUT Parameters: applid, numtcbs
Explanation: The group name has been de-registered from
Work Load Manager. This CICS system will no longer
participate in connection optimization in the group specified. DFHSO0121 applid No TCBs have been initialized for SSL
This occurs when a TCPIPSERVICE is closed where its name processing. Secure Sockets Layer has been
begins with a 'D'. deactivated.
System action: The Work Load Manager IWMSRDRS call is Explanation: CICS requires at least one TCB to be
made to de-register the group name. This will remove the IP successfully initialized to handle the TCP/IP Secure Sockets
address of the system from the DNS servers table associated Layer, but it has been unable to initialize any.
with the group name. System action: CICS cannot handle any SSL sessions, so
attempts to open TCPIPSERVICEs which specify SSL(YES) or
If more than one open TCPIPSERVICE share the same group SSL(CLIENTAUTH) will fail.
name, then the WLM de-registration only occurs when the last User response: The partition size of the CICS address-space
one is closed. is probably too small to allow CICS Secure Sockets Layer to be
User response: Check the availability of the name server. initialized. Restart CICS with a larger partition size.
Destination: CSOO Destination: Console Routecodes 2 and 10
Module: DFHSOCK Module: DFHSOSE
XMEOUT Parameters: date, time,applid, groupname XMEOUT Parameter: applid

DFHSO0122 • DFHSR0603
response to be encrypted by SSL, but SSL services cannot be

DFHSO0122 date time applid SSL request from ipaddr on
provided.
TCPIPSERVICE(service) rejected because of
User response: If this message occurs frequently, consider
insufficient TCBs.
starting another CICS for this application.
Explanation: A Secure Sockets Layer connection from a client
Destination: CSOO
with address ipaddr was received on TCPIPSERVICE(service),
Module: DFHSOSE
but there were no available TCBs to process the request.
System action: The socket for the connection is closed. No XMEOUT Parameters: date, time,applid, ipaddr, service
message is sent to the client because the client expects the
DFHSRxxxx messages
system task taskid in control
DFHSR0001 applid An abend (code aaa/bbbb) has occurred
Explanation: A program check has been detected in a system
at offset X'offset' in program progname.
task. taskid is the system task identifier (for example, TCP, III)
as set in field TCAKCTTA.
occurred in program progname. Storage protection is active,
System action: CICS abnormally terminates with system
and CICS was executing in USER key at the time of the abend
dump SR0601 and an exception trace entry which gives the
or program check.
kernel error data for the program check.
The code aaa is a three digit hexadecimal VSE system User response: Use the dump to determine the cause of the
completion code, for example 0C1. If a VSE code is not program check. The most likely causes are either an error in a
applicable, this field is filled with three hyphens. The four CICS module, or an error in a user-written PLT program.
digit code bbbb, which follows aaa, is a user abend code,
For advice on problem determination, refer to the CICS
produced either by CICS or by another product on the user's
system. Message DFHME0116 is normally produced
Module: DFHSRP
containing the symptom string for this problem.
System action: An exception trace entry is made giving XMEOUT Parameters: applid, taskid
details of the error. System dump SR0001 is taken unless you Destination: Console
have specifically suppressed dumps for that dumpcode in the
dump table.
DFHSR0602 applid Program interrupt routine has been
CICS continues and abends the transaction, unless you have entered while processing program interrupt
specified in the dump table that CICS should terminate. The for same task
transaction abend code is ASRA, ASRB or ASRD. Explanation: A program check occurred. CICS started to
User response: As the execution key was USER key, modname abend the task with an abend code of ASRA when another
is probably a customer application program. Review this program check occurred. As this is a potentially recursive
program and correct the error. situation, DFHSRP terminates CICS.
First look up the VSE code, if there is one, in "OS/390 API System action: CICS abnormally terminates with system
Abend Codes" in section "VSE/Advanced Functions Codes & dump SR0602 and exception trace entries giving the kernel
SVC Errors" of z/VSE Messages and Codes - Volume 1. error data for each program check.
User response: Try to discover where and why the first
Next, look up the CICS alphanumeric code in “Transaction program check occurred. The most likely cause is an error in
Abend Codes (CICS Transaction Server for VSE/ESA)” on the application program. The second program check may be
page 453. This tells you, for example, whether the error was a due to a CICS error while terminating the task.
program check, an abend, or a runaway, and may give you
some guidance concerning user response. For advice on problem determination, refer to the CICS
Note that if the error was an 0C4 program check caused by an Module: DFHSRP
attempt to overwrite a CICS DSA, the exception trace entry
indicates which DSA the program attempted to overwrite. If XMEOUT Parameter: applid
this is the case, also refer to the explanation for message Destination: Console
DFHSR0622.
For advice on problem determination, refer to the CICS DFHSR0603 applid Program interrupt has occurred
Problem Determination Guide. Explanation: A program check occurred, and CICS did not
attempt to recover, because SRT=NO was specified in the
Report the details of the symptom string given in message system initialization table or by the operator at start-up time.
DFHME0116. System action: CICS abnormally terminates with system
dump SR0603 and an exception trace entry giving the kernel
If you want to suppress system dumps that precede ASRA,
error data for the program check.
ASRB and ASRD abends when the execution key is USER, you
User response: Initially, check that the specification of
must specify this on an entry in the dump table for system
SRT=NO is correct. If it is incorrect, change it as described in
dumpcode SR0001. Use either CEMT or an EXEC CICS
the CICS System Definition Guide.
command. Further guidance on this can be found in the CICS
System Definition Guide. For advice on problem determination, refer to the CICS
Module: DFHSRP Problem Determination Guide.
Module: DFHSRP
XMEOUT Parameters: applid, aaa/bbbb, X'offset', progname
DFHSR0601 applid Program interrupt occurred with

DFHSR0605 • DFHSR0618
program running at the XSRAB exit gets into a loop

DFHSR0605 applid Error from KE Domain - DFHSRP
(runaway), or issues an unknown XPI call (kernerror). The
initialization
second exception trace entry should help to diagnose this.
Explanation: Module DFHSRP has detected a severe error
during the initialization phase of CICS. It is unlikely that any For advice on problem determination, see the CICS Problem
recovery functions can run until the error is found and Determination Guide.
corrected. Module: DFHSRP
System action: CICS abnormally terminates with system
dump SR0605. XMEOUT Parameter: applid
User response: Use the dump to determine, if possible, the Destination: Console
cause of the problem and what must be done to correct it.
For advice on problem determination, refer to the CICS DFHSR0613 applid Abend has occurred with system task
Problem Determination Guide taskid in control
Module: DFHSRP Explanation: An operating system abnormal termination has
been detected in a system task. taskid is the system task
XMEOUT Parameter: applid identifier (for example, TCP, III) as set in field TCAKCTTA.
Destination: Console System action: CICS abnormally terminates with system
dump SR0613 and an exception trace entry giving the kernel
error data for the operating system abend.
DFHSR0606 applid Abend (code aaa/bbbb) has been
User response: Use the dump to determine the cause of the
detected.
abend, and take action to correct it.
Explanation: DFHSRP has detected an abnormal termination
which CICS is not able to handle fully (for example, the abend For advice on problem determination, see the CICS Problem
code cannot be found in the SRT). In this instance it is the Determination Guide.
CICS system and not merely a transaction, that has Module: DFHSRP
XMEOUT Parameters: applid, taskid
The code aaa is a three digit hexadecimal VSE system Destination: Console
completion code, for example 0C1. If an VSE code is not
applicable, this field is filled with three hyphens. The four
digit code bbbb, which follows aaa, is a user abend code DFHSR0615 applid Program interrupt has occurred in
produced either by CICS or by another product on the user's recovery task
system. Explanation: An operating system abnormal termination
System action: CICS abnormally terminates. A system dump occurred. CICS started to abend the task with an abend code
(dumpcode SR0606) can be taken with this message depending of ASRB when a program check occurred. DFHSRP terminates
on the abend code. An exception trace entry is produced CICS.
giving the kernel error data for the abend. System action: CICS abnormally terminates with system
User response: Use the dump to determine the abnormal dump SR0615 and exception trace entries giving the kernel
termination, and to investigate its cause. error data for the operating system abend and the program
check.
Look up the VSE code, if there is one, in "OS/390 API Abend User response: The most likely cause of the program check is
Codes" in section "VSE/Advanced Functions Codes & SVC an error in a global user exit program running at the XSRAB
Errors" of z/VSE Messages and Codes - Volume 1. exit. This is the global user exit that can be invoked when an
Next, look up the CICS alphanumeric code in “Transaction abend code is found in the SRT. If such a program was
Abend Codes (CICS Transaction Server for VSE/ESA)” on running, determine the cause of the program check and
page 453. This tells you, for example, whether the error was a correct it.
program check, an abend, or a runaway, and may give you For advice on problem determination, refer to the CICS
some guidance concerning user response. Problem Determination Guide.
Module: DFHSRP Module: DFHSRP
XMEOUT Parameters: applid, aaa/bbbb XMEOUT Parameter: applid
DFHSR0612 applid Abend recovery has been entered by DFHSR0618 applid An illegal macro call or reference to the
same task CSA or TCA has caused the abend which
Explanation: An operating system abnormal termination follows
occurred. CICS started to abend the task with abend code Explanation: A user program was executing which either
ASRB when another operating system abnormal termination contains an assembler macro which is no longer supported, or
occurred. As this is a potentially recursive situation, DFHSRP refers incorrectly to the CICS TCA or CSA. This error appears
terminates CICS. as an 0C4 program check.
System action: CICS abnormally terminates with system System action: Either The transaction abends with abend
dump SR0612 and exception trace entries giving the kernel code ASRD. This message is followed by message DFHAP0001
error data for each operating system abend. or DFHSR0001 which gives the name of the program in error
User response: The most likely cause of the second operating and the offset into that program at which the error occurred.
system abend is an error in a global user exit program
running at the XSRAB exit. This is the global user exit that can Or This is a critical error and CICS is terminated. This
be invoked when an abend code is found in the SRT. If such a message is followed by a DFHSR06xx message giving the
program was running, determine the cause of the second reason for the termination.
abend and take steps to prevent a recurrence. User response: Review the program and correct the error.
Note that this message will also be issued if a global user exit If the error is in the module DFHUEHC, ensure that UEPCSA

DFHSR0622 • DFHST0001
and UEPTCA are not being used because these reference protection active. The ERDSA or RDSA contains only
fetch-protected storage. reentrant CICS and user programs. If
RENTPGM=PROTECT was specified as a system
For advice on problem determination, refer to the CICS
initialization parameter, the ERDSA or RDSA is
write protected from programs executing in both
Module: DFHSRP
CICS key and User key. If
XMEOUT Parameter: applid RENTPGM=NOPROTECT, the ERDSA or RDSA is
Destination: Console only protected from user programs executing in
User key. The most likely causes of the 0C4 are:
v A user program residing in the ERDSA or RDSA
DFHSR0622 applid An attempt to overwrite the dsaname
has attempted to modify its own storage, (that is,
has caused the abend which follows
the program is not reentrant).
Explanation: An 0C4 program interrupt (protection
v A user program contains an error and accidentally
exception) has occurred. CICS has diagnosed the cause of the
attempted to overwrite program storage in the
0C4 as an attempt to overwrite storage in DSA dsaname.
dsaname is one of CDSA, RDSA, UDSA, ECDSA, ERDSA or ERDSA or RDSA.
EUDSA. System action: Either, the transaction abends with abend
If dsaname is CDSA or ECDSA: code ASRA. This message is followed by message DFHAP0001
CICS is running with storage protection active. Both or DFHSR0001 which gives the name of the program in error
the CDSA and the ECDSA therefore contain CICS and the offset into that program at which the error occurred.
key storage. They are write protected from user Additionally, an exception trace entry is taken which gives
programs executing in USER key. The most likely program, offset, execution key and the DSA in question.
causes of the 0C4 are: Or, this is a critical error and CICS is terminated. This
v A program executing in CICS key passed the message is followed by a DFHSR06xx message giving the
address of CICS key storage in the CDSA or reason for the termination.
ECDSA to a user program executing in user key User response: Depending on the cause and dsaname, do one
and this user program attempted to write to this of the following:
storage. v Correct any error in the program.
v A user program executing in user key contains an v Change the program resource definition so that it executes
error and accidentally attempted to write to CICS in CICS key.
key storage in the CDSA or ECDSA. v Ensure that the program is not loaded into the ERDSA by
v A user program executing in user key deliberately not link-editing it with the SVA option.
attempted to write to CICS key storage in the Module: DFHSRP
CDSA or ECDSA.
If dsaname is ERDSA or RDSA: XMEOUT Parameters: applid, dsaname
CICS may be running with or without storage Destination: Console
DFHSTxxxx messages
For modules DFHSTWR, DFHSTRD, and DFHSTUx (modules
DFHST0001 applid An abend (code aaa/bbbb) has occurred
within DFHSTUP), the job step is terminated with a dump.
Explanation: An abnormal end (abend) or program check has For ALL modules, a system dump is taken, unless you have
occurred in module modname. This implies that there may be specifically suppressed dumps in the dump table.
Alternatively, unexpected data has been input, or storage has symptom string for this problem.
been overwritten. User response: If CICS is still running, it is necessary to
decide whether to terminate CICS.
Note: There is NO applid for DFHSTUP modules.
The code aaa/bbbb is a 3-digit hexadecimal VSE code (if Look up the VSE code, if there is one, in "OS/390 API Abend
applicable), followed by a 4-digit alphanumeric CICS code. Codes" in section "VSE/Advanced Functions Codes & SVC
The VSE code is a system completion code, for example 0C1. Errors" of z/VSE Messages and Codes - Volume 1.
Then look up the CICS alphanumeric code in “Transaction
page 453. This tells you, for example, whether the error was a
program check, an abend, a runaway or a recovery
percolation, and may give you some guidance concerning user
For modules DFHSTST and DFHSTTI, a dump is taken and response.
the collection interval is set to 24 hours. Message DFHST0101
is also issued.
For module DFHSTDM, the action depends on the down at a convenient time to resolve the problem.
initialization error action value which is used by the domain
If you cannot run without the full use of module modname,
(DM) manager. The usual action is to terminate CICS with a
dump.
For module DFHSTUE, processing continues.

DFHST0002 • DFHST0004
Module: DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, (for example, the domain manager, DFHDMDM). A message is
DFHSTUx (Modules within DFHSTUP), DFHSTWR, issued to this effect.
DFHSTRD
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname symptom string for this problem.
Destination: Console User response: Inform the system programmer. If CICS has
termination messages (from, for example, the domain
DFHST0002 applid A severe error (code X'code') has manager), and look up the user response suggested for these
occurred in module modname. messages.
message) is made in the trace table. A system dump is taken, the problem. If the message recurs or if you cannot run
unless you have specifically suppressed dumps in the dump without the full use of all CICS modules, you should bring
table. CICS down in a controlled shutdown.
CICS will continue unless you have specified in the dump Try increasing the size limits of the DSAs or EDSAs. If CICS is
table that CICS should terminate. not already terminated, you need to bring CICS down to do
this. See the CICS System Definition Guide or the CICS
Performance Guide for further information on CICS storage.
Module: DFHSTDM
issued to this effect. XMEOUT Parameters: applid, X'code',modname
User response: Inform the system programmer. This indicates DFHST0004 applid A possible loop has been detected at
a possible error in CICS code. The severity of its impact will offset X'offset' in module modname.
depend on the importance of the function being executed at Explanation: A CICS function is taking more time to process
the time of the error. than CICS expects. A possible loop has been detected in
For further information about CICS exception trace entries, instruction which was executing at the time the error was
refer to the CICS Problem Determination Guide. detected.
CICS may not have been terminated. If the message occurs Note that no applid is included for DFHSTUP modules.
once and module modname is not crucial to the running of System action: An exception entry is made in the trace table.
your CICS system, you may decide to continue to run and
bring CICS down at a convenient time to resolve the problem. For modules DFHSTST and DFHSTTI, a system dump is taken
and the collection interval is set to 24 hours. Message
If the message recurs or if you cannot run without the full use DFHST0101 will also be issued.
For module DFHSTDM, the action depends on the
initialization error action value which is used by the domain
You need further assistance from IBM to resolve this problem. (DM) manager. The usual action will be to terminate CICS
See Part 4 of the CICS Problem Determination Guide for with a dump.
guidance on how to proceed. For module DFHSTUE, processing continues.
Module: DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE
For modules DFHSTWR, DFHSTRD, and DFHSTUx (modules
XMEOUT Parameters: applid, X'code',modname within DFHSTUP), the job step is terminated with a dump.
For ALL modules, a system dump is taken, unless you have
specifically suppressed dumps in the dump table.
DFHST0003 applid Insufficient storage to satisfy
GETMAIN (code X'code') in module modname. Message DFHME0116 is normally produced containing the
Explanation: A CICS GETMAIN was issued by module symptom string for this problem.
modname, but there was insufficient storage available to satisfy User response: Notify the system programmer. If CICS has
the request. not been terminated, it is necessary to decide whether the
identifies the place where the error was detected. Because some CICS functions can use a lot of CPU time, this
This error has occurred above the 16MB line. there may not be an error here. Usually, CICS purges a CICS
System action: An exception entry is made in the trace table function which exceeds the runaway task time interval which
(code X'code' in the message). A system dump is taken, unless you have specified on the ICVR system initialization
you have specifically suppressed dumps in the dump table. parameter (ICVR is measured in milliseconds). This means
that CICS should terminate. But if you have declared ICVR=0 and you consider that

DFHST0005 • DFHST0203W
If CICS has terminated module modname, and you consider User response: Refer to any associated message for guidance
that it was not a runaway, you should increase the ICVR time on resolving the original problem.
this permanently. But you can change the ICVR time interval If no associated message has been issued, you will need
temporarily online, using the CEMT transaction. further assistance from IBM. See Part 4 of the CICS Problem
If raising the ICVR time does not solve the problem, you will Module: DFHSTST, DFHSTDM, DFHSTTI
Problem Determination Guide for guidance on how to proceed. XMEOUT Parameter: applid
Module: DFHSTST, DFHSTDM, DFHSTTI, DFHSTUE, Destination: Console
DFHSTUx (Modules within DFHSTUP), DFHSTWR,
DFHSTRD DFHST0103 applid A DMF error has occurred with return
XMEOUT Parameters: applid, X'offset', modname code X'rc'.
Destination: Console Explanation: DMF has returned to the statistics (ST) domain
with an error return code X'rc' from the DFHSMFEW macro.
System action: Other CICS processing continues.
DFHST0005 applid A hardware error has occurred (module User response: Refer to the CICS Operations and Utilities
modname, code X'code'). The Time-of-Day clock Guide for a detailed explanation of the meaning of the return
is invalid. code.
Explanation: Execution of the STCK machine instruction Module: DFHSTST
resulted in a non-zero condition code.
System action: A system dump is taken and interval XMEOUT Parameters: applid, X'rc'
collections are canceled. Message DFHST0102 is also issued. Destination: Console

symptom string for this problem. DFHST0201S An attempt to open the statistics data set has
User response: Notify the system programmer. This is in all failed.
probability a hardware error and you should first investigate Explanation: DFHSTUP has tried to open the unloaded DMF
the store clock and find out whether it is working properly. If data set but has failed.
this is the cause, take the appropriate action to have it System action: A dump is taken and the job step is
repaired or replaced. terminated.
User response: Ensure that the JCL for the job is correct. A
In the unlikely event that this is not a hardware problem, you sample set of JCL to execute the DFHSTUP utility is contained
will need further assistance from IBM. See Part 4 of the CICS in the CICS Operations and Utilities Guide.
Module: DFHSTST, DFHSTDM If incorrect JCL is not the cause of the problem, you will need
further assistance from IBM. See Part 4 of the CICS Problem
XMEOUT Parameters: applid, modname,X'code' Determination Guide for guidance on how to proceed.
Destination: Console Module: DFHSTRD
Destination: SYSLST
DFHST0101I applid The Statistics Domain has set the
collection interval to 24 hours. DFHST0202S A read error on the statistics data set has
Explanation: A problem has been detected by, or has been occurred
passed back to, the statistics (ST) domain. As a result, the Explanation: A read error was encountered on the unloaded
collection interval has been set to the maximum value. The DMF data set.
end-of-day collection time is unchanged. System action: A dump is taken and the job step is
terminated.
A message explaining the problem has already been issued by
User response: Inform the system programmer. First check
the module in error.
that the JCL for the job is correct. A sample set of JCL to
execute the DFHSTUP utility is contained in the CICS
User response: Refer to the associated message for guidance
Operations and Utilities Guide. Resubmit the job.
on resolving the original problem.
Module: DFHSTRD
Issue a CEMT SET STATISTICS command to reset the interval Destination: SYSLST
when the problem has been resolved.
Module: DFHSTST, DFHSTDM, DFHSTTI
DFHST0203W The statistics data set is empty.
XMEOUT Parameter: applid Explanation: An end-of-file condition was detected during
Destination: Console the first attempt to read the unloaded DMF data set, or the
unloaded DMF data set contained no CICS statistics from any
CICS system.
DFHST0102I applid The Statistics Domain has cancelled System action: The job step is terminated.
interval collections. User response: The most likely cause is an error in the JCL
Explanation: A problem has been detected by, or has been which unloads the DMF data set. First check that the JCL is
passed back to, the statistics (ST) domain. A message correct. A sample set of JCL to unload the DMF data set is
explaining the problem may have already been issued by the contained in the CICS Operations and Utilities Guide. Also check
module in error. that you have unloaded the correct DMF data set. Resubmit
To reduce the occurrence of this problem, the interval the job.
collections have been cancelled. The end-of-day collection time Module: DFHSTIN
is unchanged. Destination: SYSLST

DFHST0204S • DFHST0213S
DFHST0204S Invalid record id recid encountered on the DFHST0209S A read error on the SYSIPT data set has
statistics data set. occurred.
Explanation: An invalid record identifier recid has been Explanation: A read error was encountered on the SYSIPT
encountered in the unloaded DMF data set. data set.
System action: A dump is taken and the job step is System action: A dump is taken and the job step is
terminated. terminated.
User response: Check that the unloaded DMF data set User response: Inform the system programmer.
contains statistics records. CICS statistics records are of SMF
record type 110, sub-type 2. For further information, see the To resolve the problem, collect the dumps and any relevant
CICS Data Areas. messages and determine why the read failed. Resubmit the
job.
If the DMF data set does contain statistics records, the most Module: DFHSTRD
likely cause of the problem is a corrupted DMF data set. Destination: SYSLST
Unload the DMF data set again and rerun the DFHSTUP
utility. If the problem persists, you will need further assistance
from IBM. See Part 4 of the CICS Problem Determination Guide DFHST0210I No statistics are available for applid applid.
for guidance on how to proceed. Explanation: No statistics data records exist for applid applid
Module: DFHSTUx (modules within DFHSTUP) in the unloaded DMF data set. This is because
Destination: SYSLST v Applid applid is unknown, or
v You have unloaded the wrong DMF data set, or
v You have specified a COLLECTION TYPE= parameter for
DFHST0206S An invalid parameter (parameter) has been which applid applid has no statistics, or
specified for the DFHSTUP utility. v No CICS statistics records were written for applid applid.
Explanation: One or more of the parameters specified in the System action: The job step continues.
SYSIN data set were incorrect. User response: Check that you have specified the correct
System action: The job step is terminated. applid. If necessary, respecify the correct applid.
User response: Correct the erroneous parameter as identified
in the message and resubmit the job. Check that you have unloaded the correct DMF data set. If
Module: DFHSTUP1 necessary, unload the correct DMF data set.
Destination: SYSLST
If you have specified the correct applid and unloaded the
correct DMF data set, then there are no statistics data records
DFHST0207W An incomplete data record has been for applid applid.
encountered on the statistics data set. Module: DFHSTUP1
Explanation: A record input from the unloaded DMF data set Destination: SYSLST
specifies that the data it contains is incomplete.
User response: For an incomplete data record to have been DFHST0211S Processing terminated. Getmain failed with a
encountered, there must have been an error in the running of short on storage condition.
CICS. This should result in an exception trace and perhaps a Explanation: The DFHSTUP utility detected an error from a
dump being issued. OS/390 GETMAIN macro while obtaining working storage.
This was because DFHSTUP had exhausted the available
storage.
System action: A dump is taken and the job step terminates.
Module: DFHSTUx (modules within DFHSTUP) User response: Check that you have specified the correct
Destination: SYSLST SIZE on the EXEC JCL command used to execute the
DFHSTUP utility. A sample set of JCL to execute the
DFHSTUP utility is contained in the CICS Operations and
DFHST0208S An attempt to open the SYSIPT data set has Utilities Guide.
failed.
Explanation: DFHSTUP has tried to open the SYSIPT data set Alternatively increase the size of the partition in which the
but has failed. DFHSTUP job is run.
System action: A dump is taken and the job step is Module: All DFHSTUP modules
User response: Ensure that the JCL for the job is correct. A
sample set of JCL to execute the DFHSTUP utility is contained
in the CICS Operations and Utilities Guide. DFHST0213S Processing terminated. Error detected by
DFSORT. Check DFSORT messages.
If incorrect JCL is not the cause of the problem, you will need Explanation: An error was detected by the DFSORT utility
further assistance from IBM. See Part 4 of the CICS Problem and the DFHSTUP utility terminated.
Determination Guide for guidance on how to proceed. System action: A dump is taken and the job step is
Module: DFHSTRD terminated.
Destination: SYSLST User response: Inspect the DFSORT message data set and
search for messages indicating the reason for the failure of the
DFSORT utility. A detailed explanation of the messages
produced by DFSORT can be found in the DFSORT Application
Programming Guide.
After analyzing the DFSORT error message, take the
appropriate corrective actions and resubmit the job.

DFHST0214S • DFHST0223I
Module: DFHSTUP1
DFHST0219S A read error has occurred on the DFHSTWK
Destination: SYSLST
data set.
Explanation: The statistics utility program has detected an
DFHST0214S Processing terminated. Failure to obtain error while attempting to read from the DFHSTWK data set
system time and date. during non-summary statistics processing.
Explanation: The DFHSTUP utility was unable to obtain the System action: The statistics utility program ends
system time and date from the CICS kernel. abnormally.
System action: A dump is taken and the job step is User response: Check that the DFHSTWK data set has been
terminated. specified on the job, that the attributes of the data set are
User response: You need further assistance from IBM to correct, and that the data set is large enough.
resolve this problem. See Part 4 of the CICS Problem Module: DFHSTU17, DFHSTSOX, DFHSTUSO
Determination Guide for guidance on how to proceed. Destination: SYSLST
Module: DFHSTUP1
Destination: SYSLST
DFHST0220S An attempt to open the DFHSTWK data set
has failed.
DFHST0216W An incompatible statistics record version Explanation: The statistics utility program has detected an
number version, was detected by module error while attempting to open the DFHSTWK data set while
module. processing summary statistics.
Explanation: The statistics utility program has detected that a System action: The statistics utility program ends
statistics record has a version number which is incompatible abnormally.
with the version number expected by the DFHSTUP utility. User response: Check that the DFHSTWK data set has been
System action: The statistics record containing the invalid specified on the job, and that the attributes of the data set are
version number is ignored. Statistics records immediately correct.
following which are of the same type and which also contain Module: DFHST17X
an invalid version number are also ignored. Processing Destination: SYSLST
continues.
User response: Obtain a dump of the DMF data set. You
DFHST0221S A write error has occurred on the DFHSTWK
data set.
how to proceed.
error while attempting to write to the DFHSTWK data set
Module: All DFHSTUP modules.
during summary statistics processing.
Destination: SYSLST
System action: The statistics utility program ends
abnormally.
DFHST0217S An attempt to open the DFHSTWK data set User response: Check that the DFHSTWK data set has been
has failed. specified on the job, that the attributes of the data set are
Explanation: The statistics utility program has detected an correct, and that the data set is large enough.
error while attempting to open the DFHSTWK data set during Module: DFHST17X
non-summary statistics processing. Destination: SYSLST
abnormally.
DFHST0222S A read error has occurred on the DFHSTWK
User response: Ensure that the DFHSTWK data set has been
data set.
specified on the job, and that the attributes of the data set are
correct.
error while attempting to read from the DFHSTWK data set
Module: DFHSTU17, DFHSTSOX, DFHSTUSO
during summary statistics processing.
Destination: SYSLST
abnormally.
DFHST0218S A write error has occurred on the DFHSTWK User response: Check that the DFHSTWK data set has been
data set. specified on the job, that the attributes of the data set are
Explanation: The statistics utility program has detected an correct, and that the data set is large enough.
error while attempting to write to the DFHSTWK data set Module: DFHST17X
during non-summary statistics processing. Destination: SYSLST
abnormally.
DFHST0223I There are no data table statistics to report.
User response: Ensure that the DFHSTWK data set has been
Explanation: The file subsection of the DFHSTUP report
specified on the job, that the attributes of the data set are entitled 'Data Table Requests Information' only contains
correct, and that the data set is large enough. formatted information if the data currently being processed
Module: DFHSTU17, DFHSTSOX, DFHSTUSO contains statistics records for files accessed as data tables. This
Destination: SYSLST message is written to the DFHSTUP report, when the utility
program detects that there are no data table statistics in this
section of the statistics report.
System action: Processing continues normally.
User response: Take no action unless you expect data table
statistics in the DFHSTUP report. In this case, ensure that the

DFHST0224S • DFHSZ4005E
data tables feature is in use during the time period covered by

DFHST0225S Processing terminated. Unable to load phase
the statistics being processed.
SORT. Return code from LOAD was X'rc'.
Module: DFHSTU17, DFHST17X
Explanation: An attempt was made to load phase SORT, but
Destination: SYSLST
this failed. The DFHSTUP utility is terminated.
System action: A dump is taken and the job step is
DFHST0224S UNABLE TO LOAD STATISTICS terminated.
INITIALIZATION MODULE DFHSTU31. User response: rc is the return code from the VSE LOAD
LOAD FAILED. R15=X'xxxx'. request.
Explanation: DFHSTUP has been unable to load the statistics The most usual value in rc will be 4, which means that the
initialization module DFHSTU31. DFSORT/VSE phase SORT (or equivalent) could not be found
The code in register 15 (X'xxxx') is the return code from the in the LIBDEF PHASE search chain specified for the job.
VSE LOAD macro. A detailed explanation of the reason for the return code can be
System action: DFHSTUP terminates. found in the z/VSE System Macros Reference.
User response: See the z/VSE System Macros Reference for the
meaning of the LOAD return code. Use this code to determine After analyzing the reasons for the LOAD error, take the
why the load failed. appropriate corrective actions and resubmit the job.
Module: DFHSTUP Module: DFHSTUP1
Destination: Console Destination: SYSLST
DFHSZxxxx (FEPI) messages

DFHSZ4001I date time applid FEPI initialization has started.
Destination: Console and Transient Data Queue CSZL
Explanation: The Front End Programming Interface (FEPI) is
being initialized.
This means the CSZI transaction – FEPI – has started its DFHSZ4004E date time applid FEPI cannot be started:
processing. CSZI is started as part of CICS system FEPI=YES not specified in the SIT.
initialization, if the system initialization parameter FEPI is set Explanation: The Front End Programming Interface (FEPI)
to YES. cannot be started because the FEPI system initialization
parameter was set to NO indicating that FEPI is not required.
If you specified FEPI=YES and this message does not appear
during CICS initialization, CSZI failed to start; the most This message usually means that you attempted to start the
common reason for this is that group DFHFEPI is not included FEPI transaction (CSZI) manually, but did not set up the
in the list specified by the GRPLIST system initialization correct environment for it to run.
parameter. System action: The FEPI transaction is not run.
User response: If you require FEPI in the CICS system,
If message DFHSZ4001 is not followed by message restart CICS specifying the system initialization parameter
DFHSZ4002, FEPI failed to start. In this case, a DFHSZnnnn FEPI=YES. You do not need to start the FEPI transaction
message is issued to indicate the error. manually.
System action: FEPI initialization proceeds. Module: DFHSZRMP(DFHSZSIP)
Module: DFHSZRMP(DFHSZSIP) XMEOUT Parameters: date, time,applid
DFHSZ4005E date time applid FEPI cannot be started: FEPI is
already active, in state X'ssssssss'.
DFHSZ4002I date time applid FEPI initialization has ended. Explanation: The Front End Programming Interface (FEPI)
Explanation: The Front End Programming Interface (FEPI) cannot be started because FEPI is already active in the system.
has finished initialization.
System action: EXEC CICS FEPI commands are made This message usually means that you attempted to start a new
available. instance of FEPI manually by running the FEPI transaction
User response: None. (CSZI), but the previous instance of FEPI failed in some way
Module: DFHSZRMP(DFHSZSIP) that caused an 'active' indication to be left in error.
XMEOUT Parameters: date, time,applid The possible FEPI states (X'ssssssss') are:
Destination: Console and Transient Data Queue CSZL State Meaning
X'00000002'
DFHSZ4003I date time applid FEPI termination complete. FEPI is being initialized
Explanation: The Front End Programming Interface (FEPI) X'00000003'
has ended. FEPI is active
X'00000004'
A DFHSZnnnn message may precede message DFHSZ4003 to FEPI is terminating as CICS is undergoing a normal
indicate what caused FEPI to terminate. shutdown
System action: EXEC CICS FEPI commands are made X'00000005'
unavailable. FEPI is terminating as CICS is undergoing an
User response: Resolve the problem indicated by the immediate shutdown
messages, then restart CICS.
Module: DFHSZRMP(DFHSZSIP)

DFHSZ4006E • DFHSZ4009E
X'00000006' System action: FEPI initialization ends, and EXEC CICS FEPI
FEPI is terminating as CICS is undergoing an commands are unavailable. An exception trace entry is
abnormal shutdown generated.
System action: The request to start a new instance of FEPI is User response: The only action you can take is when there is
rejected. insufficient storage, in which case you can increase the storage
User response: If the state suggests that a previous instance available to CICS on restart.
of FEPI failed, you must restart CICS to resolve the problem.
All other errors are system failures, and you should consult
You do not need to start the FEPI transaction manually.
the system programmer. You need further assistance from IBM
to resolve this problem. See Part 4 of the CICS Problem
XMEOUT Parameters: date, time,applid, X'ssssssss' Determination Guide for guidance on how to proceed.
Destination: Console and Transient Data Queue CSZL Module: DFHSZRMP(DFHSZSIP)
XMEOUT Parameters: date, time,applid, pppppppp, X'rr', X'ee'
DFHSZ4006E date time applid FEPI initialization failed: Destination: Console and Transient Data Queue CSZL
enqueue failure, code X'rr'.
Explanation: The Front End Programming Interface (FEPI)
DFHSZ4008E date time applid FEPI initialization failed:
cannot be initialized because an attempt to enqueue on the
Non-runaway task setting failure, reason X'rr'
FEPI enqueue name SZENQRMI failed, indicating that FEPI is
response X'ee'.
already active in the system. FEPI initialization issues this
enqueue to prevent a second instance of FEPI being present in
cannot be initialized. Because FEPI is a long-running
the system.
transaction (CSZI), it must not be subject to a runaway task
This message usually means that you attempted to start the time out. The request to prevent this failed.
FEPI transaction (CSZI) manually, but there is a previous
The value of X'rr', the reason for failure, is always X'00'.
instance of CSZI still running.
The values of X'ee', the response to the failed request, are:
The possible values of X'rr', the reason for failure, are:
Response
Code Meaning
Meaning
X'31' Duplicate enqueue on SZENQRMI attempted.
X'01' Request completed successfully
X'32' Failure during enqueue processing.
X'02' Exception response generated
System action: The request to start a second instance of FEPI
X'03' Disaster response generated
is rejected.
X'04' Invalid response generated
System action: FEPI initialization ends, and EXEC CICS FEPI
commands are made unavailable. An exception trace entry is
XMEOUT Parameters: date, time,applid, X'rr' generated.
Destination: Console and Transient Data Queue CSZL User response: You need further assistance from IBM to
DFHSZ4007E date time applid FEPI initialization failed: Module: DFHSZRMP(DFHSZSIP)
storage ADD_SUBPOOL failure for subpool
pppppppp, reason X'rr' response X'ee'. XMEOUT Parameters: date, time,applid, X'rr', X'ee'
Explanation: The Front End Programming Interface (FEPI) Destination: Console and Transient Data Queue CSZL
cannot be initialized because creating the named storage
subpool for FEPI use failed.
DFHSZ4009E date time applid FEPI initialization failed:
The values of X'rr', the reason for failure, are: change-priority failure, response X'ee'.
Reason Meaning cannot be initialized because changing the dispatching priority
X'01' Insufficient storage available for the subpool of the FEPI transaction (CSZI) failed.
X'03' Subpool requested with an invalid fixed length
X'04' Subpool requested with an invalid boundary Because FEPI runs as a transaction, a high priority is required.
alignment The request to set this dispatching priority failed.
X'05' Subpool requested with an invalid initial number of
elements
X'06' Subpool requested with an invalid name Response
X'08' Subpool requested already exists Meaning
X'11' Access to the Storage Manager was denied X'01' Request completed successfully
X'03' Disaster response generated
The values of X'ee', the response to the failed request, are: X'04' Invalid response generated
X'05' A kernel error was detected
Response System action: FEPI initialization ends, and EXEC CICS FEPI
Meaning commands are made unavailable. An exception trace entry is
X'01' Request completed successfully generated.
X'02' Exception response generated User response: You need further assistance from IBM to
X'03' Disaster response generated resolve this problem. See Part 4 of the CICS Problem
X'04' Invalid response generated Determination Guide for guidance on how to proceed.
X'05' A kernel error was detected Module: DFHSZRMP(DFHSZSIP)
X'06' The request was purged

DFHSZ4010E • DFHSZ4013E
XMEOUT Parameters: date, time,applid, X'ee' User response: If this message occurs frequently, you should
Destination: Console and Transient Data Queue CSZL take a dump of the CICS system before restarting it. You need
DFHSZ4010E date time applid FEPI initialization failed: SZ to proceed.
TCB swap failure, response X'ee'. Module: DFHSZRMP(DFHSZZNG)
usually runs under the CICS SZ TCB. Transferring the FEPI XMEOUT Parameters: date, time,applid, X'rr', X'ee'
transaction (CSZI) from running under the QR TCB to the SZ Destination: Console and Transient Data Queue CSZL
TCB failed.
The values of X'ee', the response to the failed request, are: DFHSZ4012E date time applid FEPI storage GETMAIN failed
in subpool DA, reason X'rr' response X'ee'.
Response Explanation: The Front End Programming Interface (FEPI)
Meaning attempted to acquire storage in the SZSPVCDA storage
X'01' Request completed successfully subpool for general usage but the request failed.
X'02' Exception response generated
X'03' Disaster response generated The values of X'rr', the reason for failure, are:
X'04' Invalid response generated
Reason Meaning
X'05' A kernel error was detected
X'01' Insufficient storage for the request.
System action: FEPI initialization ends, and EXEC CICS FEPI
X'02' Invalid subpool token given.
commands are made unavailable. An exception trace entry is
X'04' Invalid length of element requested.
generated.
X'05' Length of element not specified.
User response: The SZ TCB is created as part of the early
X'08' Access was denied to the storage subpool.
CICS initialization and you should examine the console log to
X'11' Invalid initial image supplied.
see if any messages were generated indicating a TCB creation
X'12' An abnormal end occurred in the storage manager.
failure.
X'13' A loop was detected in the storage manager.
See Part 4 of the CICS Problem Determination Guide for The values of X'ee', the response to the failed request, are:
Module: DFHSZRMP(DFHSZSIP) Response
Meaning
XMEOUT Parameters: date, time,applid, X'ee' X'01' Request completed successfully.
Destination: Console and Transient Data Queue CSZL X'02' Exception response generated.
X'03' Disaster response generated.
X'04' Invalid response generated.
DFHSZ4011E date time applid FEPI storage GETMAIN failed
X'05' A kernel error was detected.
in subpool NB, reason X'rr' response X'ee'.
X'06' The request was purged.
attempted to acquire storage in the SZSPFCNB storage
subpool for NIB usage which failed. All of these responses indicate that a system error occurred.
System action: An exception trace entry is generated.
The values of X'rr', the reason for failure, are:
FEPI tries to recover from this error by retrying the request.
Reason Meaning However, no action is taken to prevent multiple occurrences.
X'01' Insufficient storage for the request User response: If this message occurs frequently, you should
X'02' Invalid subpool token given take a dump of the CICS system before restarting it.
X'04' Invalid length of element requested
X'05' Length of element not specified You need further assistance from IBM to resolve this problem.
X'08' Access was denied to the storage subpool See Part 4 of the CICS Problem Determination Guide for
X'11' Invalid initial image supplied guidance on how to proceed.
X'12' An abnormal end occurred in the storage manager Module: DFHSZRMP(DFHSZZAG)
X'13' A loop was detected in the storage manager XMEOUT Parameters: date, time,applid, X'rr', X'ee'
Response DFHSZ4013E date time applid FEPI storage GETMAIN failed
Meaning in subpool RP, reason X'rr' response X'ee'.
X'01' Request completed successfully. Explanation: The Front End Programming Interface (FEPI)
X'02' Exception response generated. has attempted to acquire storage in the SZSPPCRP storage
X'03' Disaster response generated. subpool for RPL usage. The request failed.
X'04' Invalid response generated.
X'05' A kernel error was detected. The values of X'rr', the reason for failure, are:
X'06' The request was purged. Reason Meaning
X'01' Insufficient storage for the request.
All these responses indicate that a system error has occurred. X'02' Invalid subpool token given.
System action: An exception trace entry is generated. X'04' Invalid length of element requested.
X'05' Length of element not specified.
FEPI tries to recover from this error by retrying the request.
X'08' Access was denied to the storage subpool.
However, no action is taken to prevent multiple occurrences.

DFHSZ4014E • DFHSZ4101I
X'11' Invalid initial image supplied. Module: DFHSZRMP(DFHSZZFR)

X'12' An abnormal end occurred in the storage manager.
XMEOUT Parameters: date, time,applid, X'rr', X'ee'
X'13' A loop was detected in the storage manager.

DFHSZ4015I date time applid FEPI {normal | immediate |
Response
forced} termination has started.
Meaning
X'01' Request completed successfully.
has acknowledged a shutdown request and is starting to
X'02' Exception response generated.
terminate.
X'03' Disaster response generated.
X'04' Invalid response generated. Message DFHSZ4003 is issued when FEPI completes
X'05' A kernel error was detected. termination.
X'06' The request was purged.
FEPI terminates only in response to a CICS shutdown request
(such as CEMT PERFORM SHUTDOWN). Some types of CICS
All of these responses indicate that a system error occurred.
shutdown can result in more than one DFHSZ4015 message
System action: An exception trace entry is generated.
being issued.
FEPI tries to recover from this error by retrying the request. System action: Certain EXEC CICS FEPI commands are made
However, no action is taken to prevent multiple occurrences. unavailable during FEPI termination.
User response: If this message occurs frequently, you should
Normal termination allows all transactions using FEPI
take a dump of the CICS system before restarting it.
resources to end before FEPI itself ends. However, no new
You need further assistance from IBM to resolve this problem. usage of FEPI resources is permitted.
Immediate termination stops usage of FEPI facilities
immediately but does a controlled shutdown of
Module: DFHSZRMP(DFHSZZRG)
communication functions.
XMEOUT Parameters: date, time,applid, X'rr', X'ee'
Forced termination stops usage of FEPI facilities immediately,
and does the quickest possible shutdown of communication
functions (which may lead to many VTAM messages being
DFHSZ4014E date time applid FEPI storage FREEMAIN issued).
failed in subpool DA|NB|RP, reason X'rr' User response: None.
response X'ee'. Module: DFHSZRMP(DFHSZRDP)
XMEOUT Parameters: date, time,applid, {1=normal, 2=immediate,
attempted to free storage in an SZSPxxxx storage subpool. The
3=forced}
request failed.
The values of X'rr', the reason for failure, are:
Reason Meaning DFHSZ4099E date time applid FEPI ended abnormally.
X'02' Invalid subpool token given. Explanation: The Front End Programming Interface (FEPI)
X'03' The address of the element to be freed is invalid. has ended abnormally.
X'06' Invalid length of element specified. System action: A system dump is taken. All EXEC CICS FEPI
X'07' Length of element not specified. commands are made unavailable.
X'08' Access was denied to the storage subpool. User response: You need further assistance from IBM to
X'10' The specified storage subpool was empty. resolve this problem. See Part 4 of the CICS Problem
X'12' An abnormal end occurred in the storage manager. Determination Guide for guidance on how to proceed.
X'13' A loop was detected in the storage manager. Module: DFHSZRMP(DFHSZSIP)
The values of X'ee', the response to the failed request, are: Destination: Console and Transient Data Queue CSZL
Response
Meaning DFHSZ4101I date time applid FEPI node nnnnnnnn installed,
X'01' Request completed successfully. for transaction xxxx.
X'02' Exception response generated. Explanation: The Front End Programming Interface (FEPI)
X'03' Disaster response generated. has successfully installed the named node.
X'04' Invalid response generated. System action: Processing continues.
X'05' A kernel error was detected. User response: None.
X'06' The request was purged. Module: DFHSZRMP(DFHSZRII)
All of these responses indicate that a system error occurred. XMEOUT Parameters: date, time,applid, nnnnnnnn, xxxx
System action: The request is rejected, and a retry is not Destination: CSZL
attempted (perhaps leaving storage that is never subsequently
accessible). An exception trace entry is generated.

DFHSZ4102W • DFHSZ4111I
DFHSZ4102W date time applid FEPI node nnnnnnnn DFHSZ4107W date time applid FEPI pool pppppppp (with
installation failed, code rrr, for transaction property set yyyyyyyy) installation failed,
xxxx. code rrr, for transaction xxxx.
Explanation: The Front End Programming Interface (FEPI) Explanation: The Front End Programming Interface (FEPI)
cannot install the named node. The code rrr indicates the cannot install the named pool, which has the characteristics of
reason, and is the RESP2 value returned by the EXEC CICS the named property set. The code rrr indicates the reason and
FEPI INSTALL NODE command. is the RESP2 value returned by the EXEC CICS FEPI INSTALL
System action: Processing continues. POOL command.
User response: Investigate the failure, and correct it. System action: Processing continues.
Module: DFHSZRMP(DFHSZRII) User response: Investigate the failure, and correct it.
Module: DFHSZRMP(DFHSZRII)
XMEOUT Parameters: date, time,applid, nnnnnnnn, rrr, xxxx
Destination: CSZL XMEOUT Parameters: date, time,applid, pppppppp, yyyyyyyy, rrr,
xxxx
Destination: CSZL
DFHSZ4103I date time applid FEPI node nnnnnnnn
discarded, for transaction xxxx.
Explanation: The Front End Programming Interface (FEPI) DFHSZ4108I date time applid FEPI pool pppppppp discarded,
has successfully discarded the named node. for transaction xxxx.
System action: Processing continues. Explanation: The Front End Programming Interface (FEPI)
User response: None. has successfully discarded the named pool.
Module: DFHSZRMP(DFHSZRDN) System action: Processing continues.
XMEOUT Parameters: date, time,applid, nnnnnnnn, xxxx Module: DFHSZRMP(DFHSZRDG)
Destination: CSZL
XMEOUT Parameters: date, time,applid, pppppppp, xxxx
Destination: CSZL
DFHSZ4104I date time applid FEPI node nnnnnnnn discard
scheduled, for transaction xxxx.
Explanation: The Front End Programming Interface (FEPI) DFHSZ4109I date time applid FEPI pool pppppppp discard
has scheduled the discard operation for the named node. scheduled, for transaction xxxx.
System action: Processing continues. The node is discarded Explanation: The Front End Programming Interface (FEPI)
when it becomes inactive. has scheduled the discard operation for the named pool.
User response: None. System action: Processing continues. The pool is discarded
Module: DFHSZRMP(DFHSZRID) when it becomes inactive.
XMEOUT Parameters: date, time,applid, nnnnnnnn, xxxx Module: DFHSZRMP(DFHSZRID)
Destination: CSZL
XMEOUT Parameters: date, time,applid, pppppppp, xxxx
Destination: CSZL
DFHSZ4105W date time applid FEPI node nnnnnnnn discard
failed, code rrr, for transaction xxxx.
Explanation: The Front End Programming Interface (FEPI) DFHSZ4110W date time applid FEPI pool pppppppp discard
cannot discard the named node. The code rrr indicates the failed, code rrr, for transaction xxxx.
reason, and is the RESP2 value returned by the EXEC CICS Explanation: The Front End Programming Interface (FEPI)
FEPI DISCARD NODE command. cannot discard the named pool. The code rrr indicates the
System action: Processing continues. reason and is the RESP2 value returned by the EXEC CICS
User response: Investigate the failure, and correct it. FEPI DISCARD POOL command.
Module: DFHSZRMP(DFHSZRID) System action: Processing continues.
User response: Investigate the failure, and correct it.
XMEOUT Parameters: date, time,applid, nnnnnnnn, rrr, xxxx Module: DFHSZRMP(DFHSZRID)
Destination: CSZL
XMEOUT Parameters: date, time,applid, pppppppp, rrr, xxxx
Destination: CSZL
DFHSZ4106I date time applid FEPI pool pppppppp (with
property set yyyyyyyy) installed, for
transaction xxxx. DFHSZ4111I date time applid FEPI target tttttttt installed, for
Explanation: The Front End Programming Interface (FEPI) transaction xxxx.
has successfully installed the named pool which has the Explanation: The Front End Programming Interface (FEPI)
characteristics of the named property set. has successfully installed the named target.
Module: DFHSZRMP(DFHSZRII) Module: DFHSZRMP(DFHSZRII)
XMEOUT Parameters: date, time,applid, pppppppp, yyyyyyyy, XMEOUT Parameters: date, time,applid, tttttttt, xxxx
xxxx Destination: CSZL
Destination: CSZL

DFHSZ4112W • DFHSZ4121W
DFHSZ4112W date time applid FEPI target tttttttt installation DFHSZ4117W date time applid FEPI property set yyyyyyyy
failed, code rrr, for transaction xxxx. installation failed, code rrr, for transaction
Explanation: The Front End Programming Interface (FEPI) xxxx.
cannot install the named target. The code rrr indicates the Explanation: The Front End Programming Interface (FEPI)
reason and is the RESP2 value returned by the EXEC CICS cannot install the named property set. The code rrr indicates
FEPI INSTALL TARGET command. the reason and is the RESP2 value returned by the EXEC CICS
System action: Processing continues. FEPI INSTALL PROPERTYSET command.
Module: DFHSZRMP(DFHSZRII) User response: Investigate the failure, and correct it.
XMEOUT Parameters: date, time,applid, tttttttt, rrr, xxxx
Destination: CSZL XMEOUT Parameters: date, time,applid, yyyyyyyy, rrr, xxxx
Destination: CSZL
DFHSZ4113I date time applid FEPI target tttttttt discarded,

for transaction xxxx. DFHSZ4118I date time applid FEPI property set yyyyyyyy
Explanation: The Front End Programming Interface (FEPI) discarded, for transaction xxxx.
has successfully discarded the named target. Explanation: The Front End Programming Interface (FEPI)
System action: Processing continues. has successfully discarded the named property set.
User response: None. System action: Processing continues.
Module: DFHSZRMP(DFHSZRDT) User response: None.
Module: DFHSZRMP(DFHSZRID)
XMEOUT Parameters: date, time,applid, tttttttt, xxxx
Destination: CSZL XMEOUT Parameters: date, time,applid, yyyyyyyy, xxxx
Destination: CSZL
DFHSZ4114I date time applid FEPI target tttttttt discard

scheduled, for transaction xxxx. DFHSZ4119W date time applid FEPI property set yyyyyyyy
Explanation: The Front End Programming Interface (FEPI) discard failed, code rrr, for transaction xxxx.
has scheduled the discard operation for the named target. Explanation: The Front End Programming Interface (FEPI)
System action: Processing continues. The target is discarded cannot discard the named property set. The code rrr indicates
when it becomes inactive. the reason and is the RESP2 value returned by the EXEC CICS
User response: None. FEPI DISCARD PROPERTYSET command.
XMEOUT Parameters: date, time,applid, tttttttt, xxxx Module: DFHSZRMP(DFHSZRID)
Destination: CSZL
XMEOUT Parameters: date, time,applid, yyyyyyyy, rrr, xxxx
Destination: CSZL
DFHSZ4115W date time applid FEPI target tttttttt discard
failed, code rrr, for transaction xxxx.
Explanation: The Front End Programming Interface (FEPI) DFHSZ4120I date time applid FEPI node nnnnnnnn added to
cannot discard the named target. The code rrr indicates the pool pppppppp, for transaction xxxx.
reason and is the RESP2 value returned by the EXEC CICS Explanation: The Front End Programming Interface (FEPI)
FEPI DISCARD TARGET command. has successfully added the named node to the named pool.
User response: Investigate the failure, and correct it. User response: None.
Module: DFHSZRMP(DFHSZRID) Module: DFHSZRMP(DFHSZRII)
XMEOUT Parameters: date, time,applid, tttttttt, rrr, xxxx XMEOUT Parameters: date, time,applid, nnnnnnnn, pppppppp,
Destination: CSZL xxxx
Destination: CSZL
DFHSZ4116I date time applid FEPI property set yyyyyyyy

installed, for transaction xxxx. DFHSZ4121W date time applid FEPI node nnnnnnnn not
Explanation: The Front End Programming Interface (FEPI) added to pool pppppppp, code rrr, for
has successfully installed the named property set. transaction xxxx.
System action: Processing continues. Explanation: The Front End Programming Interface (FEPI)
User response: None. cannot add the named node to the named pool. The code rrr
Module: DFHSZRMP(DFHSZRII) indicates the reason and is the RESP2 value returned by the
EXEC CICS FEPI ADD POOL command.
XMEOUT Parameters: date, time,applid, yyyyyyyy, xxxx System action: Processing continues.
Destination: CSZL
XMEOUT Parameters: date, time,applid, nnnnnnnn, pppppppp,

rrr, xxxx
Destination: CSZL

DFHSZ4122I • DFHSZ4153I
DFHSZ4122I date time applid FEPI node nnnnnnnn deleted DFHSZ4127W date time applid FEPI target tttttttt not deleted
from pool pppppppp, for transaction xxxx. from pool pppppppp, code rrr, for transaction
Explanation: The Front End Programming Interface (FEPI) xxxx.
has successfully deleted the named node from the named Explanation: The Front End Programming Interface (FEPI)
pool. cannot delete the named target from the named pool. The
System action: Processing continues. code rrr indicates the reason and is the RESP2 value returned
User response: None. by the EXEC CICS FEPI DELETE POOL command.
xxxx
Destination: CSZL XMEOUT Parameters: date, time,applid, tttttttt, pppppppp, rrr,
xxxx
Destination: CSZL
DFHSZ4123W date time applid FEPI node nnnnnnnn not
deleted from pool pppppppp, code rrr, for
transaction xxxx. DFHSZ4128W date time applid FEPI delete from pool
Explanation: The Front End Programming Interface (FEPI) pppppppp failed, code rrr, for transaction xxxx.
cannot delete the named node from the named pool. The code Explanation: The Front End Programming Interface (FEPI)
rrr indicates the reason and is the RESP2 value returned by cannot do a delete operation on the named pool. The code rrr
the EXEC CICS FEPI DELETE POOL command. indicates the reason and is the RESP2 value returned by the
System action: Processing continues. EXEC CICS FEPI DELETE POOL command.
Module: DFHSZRMP(DFHSZRID) User response: Investigate the failure, and correct it.
rrr, xxxx XMEOUT Parameters: date, time,applid, pppppppp, rrr, xxxx
Destination: CSZL Destination: CSZL
DFHSZ4124I date time applid FEPI target tttttttt added to DFHSZ4151I date time applid Unsolicited data received for
pool pppppppp, for transaction xxxx. FEPI pool pppppppp target tttttttt node
Explanation: The Front End Programming Interface (FEPI) nnnnnnnn. Transaction xxxx started.
has successfully added the named target to the named pool. Explanation: The Front End Programming Interface (FEPI)
System action: Processing continues. received some unsolicited data for the named pool-target-node
User response: None. connection, and started the named transaction to process this
Module: DFHSZRMP(DFHSZRII) data.
XMEOUT Parameters: date, time,applid, tttttttt, pppppppp, xxxx User response: None.
Destination: CSZL Module: DFHSZRMP(DFHSZBUN)
XMEOUT Parameters: date, time,applid, pppppppp, tttttttt,

DFHSZ4125W date time applid FEPI target tttttttt not added to nnnnnnnn, xxxx
pool pppppppp, code rrr, for transaction xxxx. Destination: CSZL
cannot add the named target to the named pool. The code rrr
indicates the reason and is the RESP2 value returned by the DFHSZ4152I date time applid Begin-session processing
EXEC CICS FEPI ADD POOL command. required for FEPI pool pppppppp target tttttttt
System action: Processing continues. node nnnnnnnn. Transaction xxxx started.
User response: Investigate the failure, and correct it. Explanation: The Front End Programming Interface (FEPI)
Module: DFHSZRMP(DFHSZRII) invoked begin-session processing for the named
pool-target-node connection, by starting the named
XMEOUT Parameters: date, time,applid, tttttttt, pppppppp, rrr, transaction.
xxxx System action: Processing continues.
Destination: CSZL User response: None.
Module: DFHSZRMP(DFHSZBSI)
DFHSZ4126I date time applid FEPI target tttttttt deleted from XMEOUT Parameters: date, time,applid, pppppppp, tttttttt,
pool pppppppp, for transaction xxxx. nnnnnnnn, xxxx
Explanation: The Front End Programming Interface (FEPI) Destination: CSZL
has successfully deleted the named target from the named
pool.
System action: Processing continues. DFHSZ4153I date time applid STSN processing required for
User response: None. FEPI pool pppppppp target tttttttt node
Module: DFHSZRMP(DFHSZRID) nnnnnnnn. Transaction xxxx started.
XMEOUT Parameters: date, time,applid, tttttttt, pppppppp, xxxx invoked STSN processing for the named pool-target-node
Destination: CSZL connection, by starting the named transaction.

DFHSZ4154W • DFHSZ4159W
User response: None. pool-target-node connection. Refer to section "VTAM codes" in

Module: DFHSZRMP(DFHSZBST) z/VSE Messages and Codes - Volume 2 for a description of the
reason code (error code or sense code) that describes this error.
XMEOUT Parameters: date, time,applid, pppppppp, tttttttt, Setting up a session for this connection has failed several
nnnnnnnn, xxxx times.
Destination: CSZL System action: Processing continues; the session setup for
this connection is not tried again.
DFHSZ4154W date time applid FEPI session setup in pool User response: None; operator intervention may be needed
pppppppp to target tttttttt and node nnnnnnnn to make the connection available.
failed with a reason code of X'rrrrrrrr'. Setup Module: DFHSZRMP(DFHSZBLO)
will be retried later. XMEOUT Parameters: date, time,applid, pppppppp, tttttttt,
Explanation: The Front End Programming Interface (FEPI) nnnnnnnn, X'rrrrrrrr'
has detected an error during session setup for the named Destination: CSZL
pool-target-node connection. Refer to section "VTAM codes" in
z/VSE Messages and Codes - Volume 2 for a description of the
reason code (error code or sense code) that describes this error. DFHSZ4158W date time applid The VTAM OPEN request for
System action: Processing continues; the session setup is FEPI node nnnnnnnn failed with a reason
tried again after a short interval, using a different node if one code of X'rrrrrrrr'. This operation will be
is available. retried.
User response: None. Explanation: The Front End Programming Interface (FEPI)
Module: DFHSZRMP(DFHSZBLO) has detected an error during VTAM OPEN processing for the
named node.
nnnnnnnn, X'rrrrrrrr' The possible values of X'rrrrrrrr', the reason for failure, are:
Destination: CSZL
Code Meaning
X'00000000'
DFHSZ4155W date time applid FEPI session in pool pppppppp VTAM TPEND occurred with error code 0.
to target tttttttt and node nnnnnnnn ended X'00000004'
with a reason code of X'rrrrrrrr'. VTAM TPEND occurred with error code 4.
Explanation: The Front End Programming Interface (FEPI) X'00000008'
has detected this VTAM event for the named pool-target-node VTAM TPEND occurred with error code 8.
connection. Refer to section "VTAM codes" in z/VSE Messages X'0000000C'
and Codes - Volume 2 for a description of the reason code (error VTAM SETLOGON failed.
code or sense code) that describes this event. other values
System action: Processing continues. VTAM OPEN failed with error code given.
User response: None; This message can have a reason code
of zero. If the message is not wanted with a reason code of Refer to VTAM Programming for a description of these error
zero then we recommend the use of the XMEOUT global user codes.
exit to suppress it. System action: Processing continues; the VTAM OPEN for
Module: DFHSZRMP(DFHSZBLO) the node is repeated after a short interval.
Module: DFHSZRMP(DFHSZRIO)
nnnnnnnn, X'rrrrrrrr'
Destination: CSZL XMEOUT Parameters: date, time,applid, nnnnnnnn, X'rrrrrrrr'
Destination: CSZL
DFHSZ4156I date time applid End-session processing
required for FEPI pool pppppppp target tttttttt DFHSZ4159W date time applid The VTAM OPEN request for
node nnnnnnnn. Transaction xxxx started. FEPI node nnnnnnnn failed with a reason
Explanation: The Front End Programming Interface (FEPI) code of X'rrrrrrrr'. This operation will not be
invoked end-session processing for the named retried.
pool-target-node connection, by starting the named Explanation: The Front End Programming Interface (FEPI)
transaction. has detected an error during VTAM OPEN processing for the
System action: Processing continues. named node. The reason code is the error code returned by
User response: None. the VTAM OPEN operation. Refer to section "VTAM codes" in
Module: DFHSZRMP(DFHSZBFT) z/VSE Messages and Codes - Volume 2 for a description of these
error codes.
System action: Processing continues; the VTAM OPEN for
nnnnnnnn, xxxx
the node is not repeated.
Destination: CSZL
User response: None; operator intervention may be needed
to make the node available.
DFHSZ4157W date time applid FEPI session setup in pool Module: DFHSZRMP(DFHSZRIO)
pppppppp to target tttttttt and node nnnnnnnn
XMEOUT Parameters: date, time,applid, nnnnnnnn, X'rrrrrrrr'
failed with a reason code of X'rrrrrrrr'. Setup
Destination: CSZL
will not be retried.
has detected an error during session setup for the named

DFHSZ4201I • DFHTC1012

DFHSZ4201I date time applid FEPI node nnnnnnnn now has
User response: None
status {INSERVICE | OUTSERVICE |
Module: DFHSZRMP(DFHSZRIW)
GOINGOUT}, {ACQUIRED | RELEASED
|ACQUIRING | RELEASING}. XMEOUT Parameters: date, time,applid, pppppppp,
Explanation: The status of a Front End Programming {1=INSERVICE, 2=OUTSERVICE, 3=GOINGOUT}
Interface (FEPI) node has been changed by an EXEC CICS Destination: CSZL
FEPI SET NODE or a CEMT SET FENODE command, and is
now as described.
System action: Processing continues. DFHSZ4203I date time applid FEPI target tttttttt now has
User response: None status {INSERVICE | OUTSERVICE |
Module: DFHSZRMP(DFHSZRIW) GOINGOUT}.
Explanation: The status of a Front End Programming
XMEOUT Parameters: date, time,applid, nnnnnnnn, Interface (FEPI) target has been changed by an EXEC CICS
{1=INSERVICE, 2=OUTSERVICE, 3=GOINGOUT}, FEPI SET TARGET or a CEMT SET FETARGET command, and
{4=ACQUIRED, 5=RELEASED, 6=ACQUIRING, is now as described.
7=RELEASING} System action: Processing continues.
Destination: CSZL User response: None
Module: DFHSZRMP(DFHSZRIW)
DFHSZ4202I date time applid FEPI pool pppppppp now has XMEOUT Parameters: date, time,applid, tttttttt, {1=INSERVICE,
status {INSERVICE | OUTSERVICE | 2=OUTSERVICE, 3=GOINGOUT}
GOINGOUT}. Destination: CSZL
Explanation: The status of a Front End Programming
Interface (FEPI) pool has been changed by an EXEC CICS FEPI
SET POOL or a CEMT SET FEPOOL command, and is now as
described.
DFHTCxxxx messages
DFHTC1001 applid Terminal control initialization failed
stream.
(modname).
Module: DFHSII1
Explanation: The CICS terminal control restart task could not
complete because a necessary step failed. The task has done XMEOUT Parameter: applid
some essential recovery operations and has abnormally Destination: Console
terminated itself with code ATC1.
System action: CICS writes a transaction dump for the
terminal control restart task. CICS sends two messages to the DFHTC1003 applid Program DFHTCBP cannot be found -
console, one to identify the error detected by the terminal message recovery cannot be performed
control restart task, and one, DFHTC1001, to say that the task Explanation: The CICS terminal control backout program,
has failed. A third message follows, either to say that CICS has DFHTCBP, is not available. CICS cannot find DFHTCBP in any
terminated abnormally with a dump or to ask you to reply sublibrary of the LIBDEF search chain for the CICS startup job
GO or CANCEL. Depending on the nature of the original stream.
error, you may see messages from some other system System action: CICS terminates abnormally with a dump.
component (for example, an access method). User response: To correct this error, place DFHTCBP in a
Message DFHME0116 is normally produced containing the stream.
symptom string for this problem. Module: DFHTCRP
User response: First, if CICS has requested a response, you
must reply. If you reply 'GO', CICS continues processing, but XMEOUT Parameter: applid
without terminal control. If you reply 'CANCEL', CICS Destination: Console
terminates abnormally with a dump. Use the messages and
dumps to find out the cause of the failure. You need further
assistance from IBM to resolve this problem. See Part 4 of the DFHTC1011 applid Unable to load modname
CICS Problem Determination Guide for guidance on how to Explanation: During a CICS cold start, CICS could not PC
proceed. LOAD the CICS module, modname, probably because it is
Module: DFHSII1, DFHTCRP missing from the library.
System action: CICS initialization continues, but, even if it
XMEOUT Parameters: applid, modname completes, VTAM resource initialization will be incorrect in
Destination: Console some respect, depending on the function of module modname.
User response: If CICS completes initialization, processing of
VTAM resources will be invalid. You should cancel CICS,
DFHTC1002 applid Unable to link to program DFHTCRP. make module modname available and then restart CICS.
Explanation: The CICS terminal control recovery program, Module: DFHTCRP
DFHTCRP, is unavailable. CICS cannot find DFHTCRP in any
sublibrary of the LIBDEF search chain for the CICS startup job XMEOUT Parameters: applid, modname
stream. Destination: Console
User response: To correct this error, place DFHTCRP in a
DFHTC1012 applid Failure in installing VTAM resources
Explanation: During a cold start, CICS could not install all

DFHTC1013 • DFHTC1034I
the VTAM resources defined by TCT macros. CICS has issued and see if you can resolve the problem.
other message(s) identifying which resources could not be Module: DFHTCRP
installed.
System action: CICS initialization continues. XMEOUT Parameters: applid, type,key
User response: If any of the uninstalled resources is essential, Destination: Console
use RDO to make it available, or cancel CICS. The most likely
reasons for this message are:
DFHTC1023 applid Logic error in tracking condition
v The output of the DFHTCT assembly was corrupted, or
Explanation: During XRF tracking, a condition was detected
v A previous CICS message such as DFHTC1011, or
which is not possible within the intended design. The insert
v CICS code contains a logic error.
indicates which of the checked conditions has been detected:
If you suspect an error in CICS, you will need further 1. No broadcast message accepted outside tracking. The
assistance from IBM. See Part 4 of the CICS Problem GETMSG routine in DFHTCRP should only accept
Determination Guide for guidance on how to proceed. broadcast messages and those whose id matches that in
Module: DFHTCRP field GETMSPEC. This field should only be set during
tracking.
XMEOUT Parameter: applid 2. Broadcast message with null key. A null-key record
Destination: Console indicates that the catch-up stream that it arrives in is
complete. This can only happen to the broadcast tracking
DFHTC1013 applid Restore failed for xxxxxx stream if the active has just done a normal (warm)
Explanation: During a warm or emergency restart, CICS shut-down.
could not restore the resource xxxxxx. System action: The message in question is ignored
System action: CICS continues initialization. If the resource is User response: You need further assistance from IBM to
defined in a DFHTCT macro, CICS will try to cold start it resolve this problem. See Part 4 of the CICS Problem
when processing DFHRDTxx. Determination Guide for guidance on how to proceed.
User response: If resource xxxxxx is not cold started, and is Module: DFHTCRP
essential to your system, cancel CICS. This problem is XMEOUT Parameters: applid, condition
probably caused by a CICS logic error. You need further Destination: Console
proceed. DFHTC1024I applid XRF takeover while catching up.
Module: DFHTCRP Explanation: The alternate CICS that issued this message has
only just started. The active CICS failed before the alternate
XMEOUT Parameters: applid, xxxxxx could obtain all the information about TCT resources in the
Destination: Console active. Please refer to messages DFHTC1034-DFHTC1036 for
details of the types of information which may be missing or
DFHTC1015 applid TCT load module contains obsolete may be incomplete.
entries System action: Takeover continues.
Explanation: During CICS initialization, the TCT load User response: Watch for further messages.
module DFHTCTxx (xx being the suffix) was found to contain Module: DFHTCRP
entries not generated by the assembly macros for this release XMEOUT Parameter: applid
of CICS. This table cannot be used. Destination: Console
System action: The bring-up is abandoned.
User response: Either the incorrect TCT suffix was specified
or implied, or the TCT has been assembled against the wrong DFHTC1034I applid TCT contents incomplete. Will read
level of CICS macros. Retry the bring-up, specifying a different catalog.
suffix, or using a TCT assembled against the correct macros, as Explanation: DFHTC1024 provides background information
appropriate. for this message. The active CICS failed before the alternate
Module: DFHAPSIP CICS could obtain the definitions for all the trackable
resources in the active system's TCT. Definitions may be
XMEOUT Parameter: applid missing at this point. However, the CICS catalog in the active
Destination: Console system may contain a more complete set of definitions in the
restart data set. These will now be read as for a warm or
DFHTC1022 applid Error for XRF tracking record - Type: emergency restart.
type - Key: key System action: Takeover continues.
Explanation: An error during XRF tracking prevented a User response: Look for any errors while reading the CICS
change to a resource from being tracked. The resource is of catalog.
type type and is associated with key key. Module: DFHTCRP
type is the tracking record type. This is one of the following: XMEOUT Parameter: applid
TCT CONTENTS Destination: Console
ZCP SESSIONS
key is the location of an object in the TCTTE hierarchy.

System action: The associated resource is in an incorrect
state, missing, or not deleted at the end of takeover.
User response: Decide whether the named resource is critical

DFHTC1035E • DFHTC1046I
and then flushes the outstanding tracking activity as described

DFHTC1035E applid Session states may be incorrect
in message DFHTC1046.
Explanation: DFHTC1024 provides background information
User response: Look for message DFHTC1046.
for this message. The active CICS failed before the alternate
Module: DFHZXQO
CICS could obtain the session-state for all the trackable
resources in the active system's TCT. States may be incorrect at XMEOUT Parameter: applid
this point. Destination: Console
System action: Takeover continues.
User response: Be prepared for some logical units (LUs) that
were ACQUIRED in the old active system not to be after the DFHTC1043I applid Terminal control tracking ended - nnn
takeover. records received.
Module: DFHTCRP Explanation: An XRF alternate system is taking over. The last
of the terminal control tracking records from the failing active
XMEOUT Parameter: applid system has been received and is being processed.
Destination: Console System action: Takeover continues.
Module: DFHTCRP
DFHTC1036I applid Unimplemented tracking-type
incomplete: xxxx XMEOUT Parameters: applid, nnn
Explanation: DFHTC1024 provides background information Destination: Console
for this message. The active CICS failed before the alternate
CICS had been sent all the information regarding a type of
resource which has not been implemented. This does not have DFHTC1044I applid Terminal control catch-up started.
any serious consequences because the information would have Explanation: An XRF alternate system is preparing to
been thrown away. However, it indicates a level of standby and has received the first message from the active
incompatibility between the old active system and this system. containing information about terminal control resources
System action: Takeover continues. installed and/or bound before this alternate system was
User response: Decide whether the implied level started.
incompatibility exists and is expected. System action: Initialization continues.
Module: DFHTCRP User response: None.
Module: DFHTCRP
XMEOUT Parameters: applid, xxxx
DFHTC1040I applid nnnn Terminal control tracking records

received. DFHTC1045I applid Terminal control catch-up complete.
Explanation: An alternate CICS is standing by and has Explanation: An XRF alternate system is standing by, and has
received nnnn terminal control tracking messages from the now received all the terminal control information it needs
active. about terminal control resources installed and/or bound in the
System action: Tracking continues. active before this alternate system was started.
User response: None. System action: Normal tracking continues.
Module: DFHTCRP User response: None.
Module: DFHTCRP
XMEOUT Parameters: applid, nnnn
DFHTC1041I applid Terminal control tracking started.

Explanation: An alternate CICS is initializing, and is now DFHTC1046I applid Flushing terminal control tracking.
about to start accepting messages from the active system. Explanation: An alternate is taking over and is processing
Message DFHTC1044 should appear shortly. the remaining few tracking records from the active. Message
System action: Initialization continues. DFHTC1042 has been issued twice. DFHZXQO is now doing a
User response: None. controlled flush of the outstanding activity.
Module: DFHTCRP System action: CICS posts one outstanding action every 2
seconds in an attempt to free the hold-up A system dump is
XMEOUT Parameter: applid taken for the first action only.
Destination: Console User response: This processing only occurs when an error or
unforeseen circumstance arises. If the problem can be
reproduced, you will need further assistance from IBM. See
DFHTC1042I applid Waiting for terminal control tracking to
drain.
how to proceed.
Explanation: An alternate is taking over and is processing
Module: DFHZXQO
the remaining few tracking records from the active. This
message is issued every 15 seconds while the takeover is held XMEOUT Parameter: applid
up for processing to complete. This is potentially an error, Destination: Console
especially if it is repeated an unusual number of times. The
likely causes include a delay in UNBIND processing in VTAM,
or a CICS logic error. The system issues this message twice

DFHTC1047I • DFHTC2513
DFHTC1047I applid Higher node missing. Record dropped DFHTC2506 date time applid Output event rejected return
for key code zz {on line w/term | at term }termid{, trans
Explanation: An XRF alternate has received a tracking }tranid{, rel line=}rrtime
message from the active CICS, but either the associated system Explanation: An output operation was attempted but was
entry for this terminal is not present, or the ordering of halted by the I/O routines and resulted in the SAM return
terminal catalog records on the restart data set is incorrect. (In code zz. If an abnormal condition is detected after a READ or
that the terminal in error comes before the associated system WRITE macro, the operation is not started, and control is
entry.) returned to the user program at the instruction following the
READ or WRITE macro.
key is the location of an object in the TCTTE hierarchy. This
System action: The line is placed out of service.
situation occurs if the active system was unable to send all of User response: Ensure that the system is dumped at
its tracking messages. This sometimes results in the system
shutdown time in order to document the failure.
entry not being sent. Module: DFHTACP
System action: The tracking message is discarded and so the
associated action (an INSTALL or LOGON) is not performed. XMEOUT Parameters: date, time,applid, zz, {1=on line w/term,
User response: Ensure the CAVM message data set is large 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time
enough and restart the alternate. Check that the active CICS Destination: CSMT
job is referring to the correct restart data set.
Module: DFHTCRP
DFHTC2507 date time applid Input event rejected return
XMEOUT Parameters: applid, key code zz {on line w/term | at term }termid{, trans
Destination: Console }tranid{, rel line=}rr,time
Explanation: An input operation was attempted but was
halted by the I/O routines, and resulted in the SAM return
DFHTC1060 applid Insufficient storage (code FCF7) in
code zz. If an abnormal condition is detected after a READ or
module DFHTCRP.
WRITE macro instruction, the operation is not started, and
Explanation: A request for storage could not be satisfied in
control is returned to your program at the instruction
module DFHTCRP. The specific error is identified by the code
following the READ or WRITE macro.
FCF7. This implies that the dynamic storage area (DSA) size is
System action: The line is placed out of service.
too small.
User response: Ensure the system is dumped at shutdown
System action: Terminal control initialization is terminated
time in order to document the failure.
with a system dump and message DFHTC1001 is issued.
Module: DFHTACP
User response: Since sufficient storage should be obtainable
from within the minimum size DSA, this may imply a logic XMEOUT Parameters: date, time,applid, zz, {1=on line w/term,
error within CICS. Try to increase the DSA size limits. You 2=at term }, termid, {1=, trans },tranid, {1=, rel line=}, rr, time
need further assistance from IBM to resolve this problem. See Destination: CSMT
how to proceed.
Module: DFHTCRP DFHTC2511 date time applid Invalid write request {on line
w/term | at term }termid{, trans }tranid{, rel
XMEOUT Parameter: applid line=}rr,time
Destination: Console Explanation: This message is issued when one of the
following has occurred.
1. A transaction has issued a write to its terminal facility that
DFHTC1575 applid No TCT entry for termid
currently has a terminal status of input.
Explanation: This message is issued when system
2. A transaction has issued a write to a 3735 during batch
initialization reads a warm start record for which there is no
transmission prior to receipt of the end-of-file (EOF)
matching terminal control table (TCT) entry. termid is the TCT
condition.
name that is missing.
System action: The write request is not executed, and the
System action: The record is ignored.
transaction terminates abnormally. CICS processing continues.
User response: If TCT termid is required, system initialization
User response: The user response depends on the condition
should be canceled. Ensure that a matching TCT entry for
that has occurred. For condition
terminal termid exists and retry.
1. ensure that transactions do not issue write requests to
Module: DFHTCRP
terminals in input status.
XMEOUT Parameters: applid, termid 2. ensure that the 3735 batch transaction does not issue its
Destination: Console first write request before it has received the EOF condition.
Module: DFHTACP
DFHTC2501 Msg too long, please resubmit XMEOUT Parameters: date, time,applid, {1=on line w/term, 2=at
Explanation: The terminal operator has keyed in more data term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
than was expected for this READ. Destination: CSTL
System action: The transaction in progress is terminated.
User response: Reset the terminal and restart the transaction DFHTC2513 date time applid Output length zero {on line
after the message TRANSACTION HAS BEEN ABENDED has w/term | at term }termid{, trans }tranid{, rel
been received. line=}rr,time
Module: DFHTACP Explanation: The data length in TIOATDL was not positive
Destination: Terminal End User for a write operation.
System action: The transaction is abnormally terminated.

DFHTC2514 • DFHTC2538
User response: Correct the zero or negative data length System action: The default action(s) set by DFHTACP are
specification in the application program. taken.
Module: DFHTACP User response: Refer to message DFHTC2538 for an
explanation of the default action(s) that have been taken.
XMEOUT Parameters: date, time,applid, {1=on line w/term, 2=at
term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time Possible solutions are:
Destination: CSMT v Ensure that DFHTEP is linked with AMODE 31.
v Ensure that DFHTEP is contained in one of the sublibraries
of the LIBDEF search chain and has the correct name.
DFHTC2514 date time applid No output area provided {on v Ensure that the PPT entry for module DFHTEP exists and is
line w/term | at term }termid{, trans }tranid{, rel valid.
line=}rr,time Module: DFHTACP
Explanation: A write was requested on terminal termid by
transaction tranid. However, the TCTTEDA field was not XMEOUT Parameters: date, time,applid, {1=module DFHTEP is
initialized. not AMODE 31, 2=module DFHTEP could not be loaded, 3=there
System action: The write request is not executed, and the is no PPT entry for program DFHTEP}
transaction terminates abnormally. CICS processing continues. Destination: CSMT
User response: Ensure that transaction tranid obtains the
required storage and initializes the TCTTEDA field.
DFHTC2537 date time applid Abend abcode has occurred in
Module: DFHTACP
module DFHTEP.
XMEOUT Parameters: date, time,applid, {1=on line w/term, 2=at Explanation: While processing an error for a non-VTAM
term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time terminal, user replaceable module DFHTEP was linked to and
Destination: CSTL the program has abended with abend code abcode. One or
more of the default actions described in message DFHTC2538
have been taken.
DFHTC2515 date time applid Output area exceeded {on line System action: Control is passed back to the calling module
w/term | at term }termid{, trans }tranid{, rel DFHTACP. DFHTACP reinstates the default action(s) set
line=}rr,time before DFHTEP was called. The action(s) are then taken.
Explanation: The terminal I/O area (TIOA) is not large User response: Refer to message DFHTC2538 for an
enough to contain both the data and carrier control characters. explanation of the default action(s) that have been taken.
System action: The write request is not executed, the
terminal write storage is freed (if possible), and the transaction Refer to abend code abcode for details of the original error.
terminates abnormally. CICS processing continues. Follow the user response given in abend code abcode to solve
User response: Ensure that application programs do not set the problem.
the value TIOATDL greater than the TIOA GETMAIN size. Module: DFHTACP
Module: DFHTACP
XMEOUT Parameters: date, time,applid, {1=on line w/term, 2=at Destination: CSMT
term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time
Destination: CSTL
DFHTC2538 date time applid I Default actions actions have
been taken for message number related
DFHTC2521 date time applid Undetermined unit error {on message.
line w/term | at term }termid{, trans }tranid{, rel Explanation: A problem has arisen during the processing of
line=}rr,time an error for a non-VTAM terminal and message msgno has
Explanation: An I/O error (that was not a unit check, a unit been issued. The explanations for all possible default actions
exception, or a negative response) occurred on the line defined are as follows:
by terminal termid.
Action Meaning
System action: The line associated with terminal termid is
LINEOS
placed out of service.
Place line out of service
User response: Examine the system console log message
NONPRGT
generated by SAM for this error. Have the unit error corrected.
Non purgeable task
Module: DFHTACP
TERMOS
XMEOUT Parameters: date, time,applid, {1=on line w/term, 2=at Place terminal out of service
term }, termid, {1=, trans }, tranid, {1=, rel line=}, rr,time ABENDT
Destination: CSMT Abend task on terminal
ABORTWR
Abort write and free terminal storage
DFHTC2536 date time applid Link to DFHTEP from SIGNOFF
DFHTACP failed because {module DFHTEP is Call the signoff program for terminal in error
not AMODE 31 | module DFHTEP could not be System action: The system action is stated in message related
loaded | there is no PPT entry for program message.
DFHTEP}. User response: Follow the guidance given in the user
Explanation: While processing an error for a non-VTAM response section of message related message.
terminal, CICS attempted to link to user replaceable module Module: DFHTACP
DFHTEP. The link failed. One or more of the default actions
described in message DFHTC2538 have been taken. XMEOUT Parameters: date, time,applid, actions, related message
Destination: CSMT

DFHTC8510 • DFHTD0003
Module: DFHQRY
DFHTC8510 date time applid SNA protocol violation
detected in query response at termid termid XMEOUT Parameters: date, time,applid, termid
Explanation: CICS has detected a violation of SNA protocols Destination: CSMT
in a query response from device termid.
System action: DFHQRY runs without effect.
User response: Find out why an invalid query response is
being sent to CICS.
DFHTDxxxx messages
DFHTD0001 applid An abend (code aaa/bbbb) has occurred
Explanation: An abnormal end (abend) or program check has message) is made in the trace table. A system dump is taken,
occurred in module modname. This implies that there may be unless you have specifically suppressed dumps in the dump
an error in CICS code. Alternatively, unexpected data has been table.
input, or storage has been overwritten. CICS continues unless you have specified in the dump table
The code aaa/bbbb is a three 3-digit hexadecimal VSE code (if that CICS should terminate. If appropriate, an error return
applicable), followed by a 4-digit alphanumeric CICS code. code is sent to the caller of this domain. In this case, CICS
The VSE code is a system completion code, for example 0C1. could be terminated by the caller (for example, the domain
If a VSE code is not applicable, this field is filled with three manager, DFHDMDM). A message is issued to this effect.
abend code; TS1310 refers to message DFHTS1310). symptom string for this problem.
System action: An exception entry is made in the trace table. User response: The severity of this error depends on the
A system dump is taken, unless you have specifically importance of the function being executed at the time of the
suppressed dumps in the dump table. error.
CICS continues unless you have specified in the dump table CICS may not have been terminated.
Message DFHME0116 is normally produced containing the to the running of your CICS system, you may decide to
symptom string for this problem. continue to run and bring CICS down at a convenient time to
User response: If CICS is still running, it is necessary to resolve the problem.
Look up the VSE code, if there is one, in "OS/390 API Abend of module modname, you should bring CICS down in a
Codes" in section "VSE/Advanced Functions Codes & SVC controlled shutdown.
Then look up the CICS alphanumeric code in “Transaction See Part 4 of the CICS Problem Determination Guide for
Abend Codes (CICS Transaction Server for VSE/ESA)” on guidance on how to proceed.
page 453. This tells you, for example, whether the error is a
data queue.
If module modname is not crucial to the running of your CICS Module: DFHAPTD
down at a convenient time to resolve the problem. XMEOUT Parameters: applid, X'code',modname
If you cannot run without the full use of module modname,
DFHTD0003 applid Insufficient storage (code X'code') in
You need further assistance from IBM to resolve this problem. module modname.
See Part 4 of the CICS Problem Determination Guide for Explanation: A CICS GETMAIN was issued by module
guidance on how to proceed. modname, but there was insufficient storage available to satisfy
the request.
data queue. The code X'code' is the exception trace point id which uniquely
Module: DFHAPTD identifies the place where the error was detected.
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname (code X'code'). A system dump is taken, unless you have
Destination: Console specifically suppressed dumps in the dump table.

DFHTD0002 applid A severe error (code X'code') has have specified in the dump table that CICS should not
occurred in module modname. terminate.
The code X'code' is the exception trace point id which uniquely Message DFHME0116 is normally produced containing the
identifies what the error is and where the error was detected. symptom string for this problem.
For further information about CICS exception trace entries, User response: Inform the system programmer. If CICS has

DFHTD0004 • DFHTD0006
termination messages (from, for example, the domain

DFHTD0005 applid A hardware error has occurred (module
manager), and look up the user response for these messages.
Try increasing the size limits of the DSAs or EDSAs. See the is invalid.
CICS System Definition Guide or the CICS Performance Guide for Explanation: An error has occurred during the running of
more information on CICS storage. module modname.
The store clock facility is the timing mechanism for the
Note: Do not attempt to reroute this message to a transient operating system.
data queue.
Module: DFHAPTD The code X'code' is the exception trace point id which uniquely
XMEOUT Parameters: applid, X'code',modname System action: An exception entry (code X'code') is made in
Destination: Console the trace table. A system dump is taken, unless you have
DFHTD0004 applid A possible loop has been detected at This is a critical error and CICS is terminated, even if you
offset X'offset' in module modname. have specified in the dump table that CICS should not
Explanation: A CICS function is taking more time to process terminate.
module modname at offset X'offset'. This is the offset of the Message DFHME0116 is normally produced containing the
instruction which was executing at the time the error was symptom string for this problem.
detected. User response: Notify the system programmer. This is in all
System action: An exception entry is made in the trace table. probability a hardware error and you should in the first
A system dump is taken, unless you have specifically instance investigate the store clock and find out whether it is
suppressed dumps in the dump table. working properly. If this is the cause, you should take the
appropriate action to have it repaired or replaced.
that CICS should terminate. In the unlikely event that this is not a hardware problem, you
will need further assistance from IBM. See Part 4 of the CICS
Message DFHME0116 is normally produced containing the Problem Determination Guide for guidance on how to proceed.
data queue.
Module: DFHAPTD
XMEOUT Parameters: applid, modname,X'code'
there may not be an error here. Usually, CICS will purge a
CICS function which exceeds the runaway task time interval
which you have specified on the ICVR system initialization DFHTD0006 applid Insufficient storage to satisfy Getmain
parameter (ICVR is measured in milliseconds). This means (code X'code') in module modname. VSE code
that the module modname will be terminated and CICS will vsecode.
continue. Explanation: Module modname attempted to acquire storage
but there was insufficient storage available to satisfy the
request.
terminate CICS in order to terminate the runaway function. The code X'code' is the exception trace point ID which
that it was not a runaway, you should increase the ICVR time The code vsecode is the OS/390 GETMAIN return code.
interval. You have to bring CICS down at a suitable time to do System action: An exception entry is made in the trace table
this permanently. But you can change the ICVR time interval (code X'code'). A system dump is taken, unless you have
temporarily online, using the CEMT transaction. specifically suppressed dumps in the dump table.
If raising the ICVR time does not solve the problem, you will CICS continues unless you have specified in the dump table
need further assistance from IBM. See Part 4 of the CICS that CICS should terminate.
data queue.
issued to this effect.
Module: DFHAPTD
response for these messages.


DFHTD0100I • DFHTD0180
continue and bring CICS down at a convenient time to resolve which should explain why transient data initialization has
the problem. If the message recurs or if you cannot run failed.
CICS down in a controlled shutdown. Note: Do not attempt to reroute this message to a transient
data queue.
You can get diagnostic information about the GETMAIN
Module: DFHTDRP
return code vsecode by consulting "OS/390 API Return Codes"
in section "VSE/Advanced Functions Codes & SVC Errors" of XMEOUT Parameter: applid
z/VSE Messages and Codes - Volume 1. Destination: Console
Try decreasing the size limits of the DSAs or EDSAs. Or, try
increasing the size of the whole region, if it is not already at DFHTD0103I applid Transient Data initialization has been
maximum size. See the CICS System Definition Guide or the suspended pending takeover.
CICS Performance Guide for further information on CICS Explanation: This is an informational message indicating that
storage. transient data initialization has been suspended pending
takeover.
data queue. Some transient data initialization can be performed while
Module: DFHAPTD CICS is operating in standby mode. However the remaining
initialization can not be performed until takeover is complete
XMEOUT Parameters: applid, X'code',modname, vsecode because transient data sets, with the exception of the
Destination: Console DFHCXRF data set, are assumed to be passively shared.
DFHTD0100I applid Transient Data initialization has
started.
Explanation: This is an informational message indicating that Note: Do not attempt to reroute this message to a transient
transient data initialization has started. data queue.
System action: System initialization continues. Module: DFHTDRP
User response: None. The message can be suppressed with XMEOUT Parameter: applid
the system initialization parameter MSGLVL=0. Destination: Console

data queue. DFHTD0104I applid Transient Data initialization has been
Module: DFHTDRP resumed following takeover.
XMEOUT Parameter: applid transient data initialization has been resumed following
Destination: Console takeover.
DFHTD0101I applid Transient Data initialization has ended.
transient data initialization has completed successfully. Note: Do not attempt to reroute this message to a transient
System action: System initialization continues. data queue.
User response: None. The message can be suppressed with Module: DFHTDRP
the system initialization parameter MSGLVL=0. XMEOUT Parameter: applid
data queue.
Module: DFHTDRP DFHTD0180 applid Unexpected response (code X'response')
and reason (code X'reason') from a dfhxxyym
XMEOUT Parameter: applid call.
Destination: Console Explanation: Module DFHTDA cannot continue processing
following the failure of a dfhxxyym call to domain xx.
DFHTD0102A applid Transient Data initialization has failed. The response (code X'response') and reason (code X'reason') are
Explanation: Transient data initialization has failed. those returned from the domain call (that is, xxyy_response and
xxyy_reason).
The SETXIT routine in DFHTDRP has been entered following
System action: This is a critical error and CICS is terminated,
abnormal termination of the transient data initialization task.
System action: Provided there are no subsequent serious
not terminate.
errors which prevent further initialization of CICS, CICS issues
one of two messages depending on what other errors, if any, A system dump with dumpcode TD0180 is taken unless you
have occurred during initialization. have specifically suppressed dumps in the dump table.
If DFHSI1521 is issued, CICS initialization is terminated. If Message DFHME0116 is normally produced containing the
DFHSI1522 is issued, decide if CICS initialization is to be symptom string for this problem.
continued in degraded mode or to be terminated. User response: You need further assistance from IBM to
User response: Check previous console messages, one of resolve this problem. See Part 4 of the CICS Problem

Note: Do not attempt to reroute this message to a transient Module DFHTDB could not initiate the associated transaction
data queue. following the response of a dfhxxyym call to domain xx.
Module: DFHTDA
The response (code X'response') and reason (code X'reason') are
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym those returned from the domain call (that is, xxyy_response and
Destination: Console xxyy_reason).
Initiation of the associated transaction has failed.
DFHTD0181 applid Unexpected response (code X'response') System action: This is probably a CICS logic error.
Each subsequent write to the transient data queue causes
call.
another attempt to initiate the transaction, which will fail.
Explanation: Module DFHTDB cannot continue processing
However, this message is only issued the first time the error is
following the failure of a dfhxxyym call to domain xx.
detected.
CICS writes a dump and continues processing. Message
those returned from the domain call (that is, xxyy_response and
DFHME0116 is normally produced containing the symptom
xxyy_reason).
string for this problem.
not terminate.
A system dump with dumpcode TD0181 is taken unless you
have specifically suppressed dumps in the dump table. Note: Do not attempt to reroute this message to a transient
data queue.
Module: DFHTDB
User response: You need further assistance from IBM to XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym,
resolve this problem. See Part 4 of the CICS Problem queue
Determination Guide for guidance on how to proceed. Destination: Console

DFHTD0240 applid Queue queue (DLBL name dlblname) is
data queue.
full.
Module: DFHTDB
Explanation: No more data can be written to extrapartition
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym queue queue with DLBL name dlblname.
Destination: Console System action: If the system abend occurs during processing
of an EXEC CICS WRITEQ TD command, the NOSPACE
condition is returned.
DFHTD0182 applid Unexpected response (code X'response')
If the system abend occurs during processing of an EXEC
CICS SET TDQUEUE CLOSED command, the data set is not
call.
closed and the IOERR condition is returned.
Explanation: Module DFHTDRP cannot continue processing
following the failure of a dfhxxyym call to domain xx. Note that a second attempt to close the data set succeeds.
User response: Consider allocating more space to the data set
The response (code X'response') and reason (code X'reason') are before you bring CICS up again.
those returned from the domain call (that is, xxyy_response and
xxyy_reason). This message can be suppressed with the system initialization
System action: This is a critical error. parameter MSGLVL=0.
CICS writes a dump and terminates abnormally.

Message DFHME0116 is normally produced containing the data queue.
symptom string for this problem. Module: DFHTDA from code contained in copybook
User response: You need further assistance from IBM to DFHTDEXP
XMEOUT Parameters: applid, queue,dlblname

data queue. DFHTD0242 applid An abend has been detected during
Module: DFHTDRP processing for queue queue (DLBL name
dlblname).
XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym Explanation: A system abend has occurred during processing
Destination: Console on the extrapartition queue queue (that is, the data set with
DLBL name filename).
DFHTD0183 applid Unexpected response (code X'response') System action: A system dump with dumpcode TD0242 is
and reason (code X'reason') from a dfhxxyym taken unless you have specifically suppressed dumps in the
call during processing of intrapartition queue dump table.
queue. Since this may not be a critical error, CICS is not terminated,
Explanation: The trigger level has been reached for and the IOERROR condition is returned.
intrapartition transient data queue queue. User response: You need further assistance from IBM to

resolve this problem. See Part 4 of the CICS Problem errors persist after a subsequent open, you probably need to
Determination Guide for guidance on how to proceed. reallocate this data set on a different volume.
This message can be suppressed with the system initialization

parameter MSGLVL=0.
data queue.
Module: DFHTDA
data queue. XMEOUT Parameters: applid, queue,dlblname
Module: DFHTDA from code contained in copybook Destination: Console
DFHTDEXP
XMEOUT Parameters: applid, queue,dlblname DFHTD0340 applid Transaction tranid initiated when the
Destination: Console trigger level is reached for Transient Data
queue queue is defined as REMOTE. The
transaction initiation has failed.
DFHTD0244 applid An I/O error has occurred during an Explanation: The trigger level has been reached for the
output operation to an extrapartition dataset transient data queue queue. The transaction associated with the
for queue queue. (DLBL name = dlblname). queue is remote, which is invalid for trigger transactions. The
Explanation: An I/O error has occurred during the initiation of the transaction has, therefore, failed.
processing of an output operation to the extrapartition data set System action: Until the error is corrected, each subsequent
dlblname on queue queue. write to the transient data queue causes another attempt to
This message is issued by module DFHTDA from code initiate the transaction, which fails. However, in order to avoid
contained in copybook DFHTDEXP. filling the log with messages, this message is only issued the
System action: An IOERR condition is returned. Subsequent first time the error is detected.
put requests are returned IOERR. User response: Perform one of the following, as appropriate:
User response: Close data set dlblname via CEMT. If the I/O v If the transid in the DCT is incorrect:
errors persist after a subsequent open, you probably need to – Amend the DCT, replacing the transid for the queue with
reallocate this data set on a different volume. a transid that is local, and reassemble, or
– Use EXEC CICS SET TDQUEUE(queue)
ATITRANID(tranid) to replace the transid for the queue
with a local transid. See the CICS System Programming
data queue.
Reference for more information.
Module: DFHTDA
v If the transaction definition is incorrect, amend the
XMEOUT Parameters: applid, queue,dlblname transaction definition using CEDA to make the transaction
Destination: Console local.

DFHTD0245 applid NOSPACE condition on a PUT to the
data queue.
intrapartition data set (DLBL name dlblname).
Module: DFHTDB from code contained in copybook
The RBA of the next CI would have exceeded
DFHTDSUB
2 gigabytes.
Explanation: An attempt to write to intrapartition transient XMEOUT Parameters: applid, tranid,queue
data set with DLBL name dlblname has failed due to a Destination: Console
NOSPACE condition. CICS did attempt to extend the data set
but the relative byte address (RBA) of the next control interval
(CI), if it were added, would have exceeded 2 gigabytes DFHTD0341 applid Transaction tranid associated with the
(x'7FFFFFFF'). trigger level for Transient Data queue queue
System action: The system continues normally. has not been initiated.
User response: Delete unwanted transient data queues from Explanation: The trigger level has been reached for transient
the intrapartition data set. data queue queue. Initiation of the associated transaction has
failed due to an error in system set up.
System action: Until the error is corrected, each subsequent
write to the transient data queue causes another attempt to
data queue.
initiate the transaction, which will fail. However, in order to
Module: DFHTDB
avoid filling the log with messages, this message will only be
XMEOUT Parameters: applid, dlblname issued the first time the error is detected.
Destination: Console User response: Check the definition for the queue in the
DCT. The queue must have a transaction associated with it
that exists, is defined as local, and is installed.
DFHTD0246 applid An I/O error has occurred during an
input operation to an extrapartition dataset
for queue queue. (DLBL name = dlblname).
data queue.
Explanation: An I/O error has occurred during the
processing of an input operation to the extrapartition data set
DFHTDSUB
dlblname on queue queue. This message is issued by module
DFHTDA from code contained in copybook DFHTDEXP. XMEOUT Parameters: applid, tranid,queue
System action: An IOERR condition is returned. Subsequent Destination: Console
put requests are returned IOERR.
User response: Close data set dlblname via CEMT. If the I/O


DFHTD0342 applid Transaction tranid associated with the
trigger level for Transient Data queue queue
User response: Message DFHME0116 is normally produced
has not been scheduled. containing the symptom string for this problem. For the
Explanation: The trigger level has been reached for the meaning of the codes in the message, refer to section
transient data queue queue. The schedule of the associated "VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2.
transaction has failed due to an error in system set up.
System action: Until the error is corrected, each subsequent You need further assistance from IBM to resolve this problem.
write to the transient data queue causes another attempt to See Part 4 of the CICS Problem Determination Guide for
schedule the transaction, which fails. However, in order to guidance on how to proceed.
avoid filling the log with messages, this message is only
issued the first time the error is detected. Note: Do not attempt to reroute this message to a transient
User response: Check the following and amend if necessary: data queue.
v The queue must have a transaction associated with it that Module: DFHTDB from code contained in copybook
exists, is defined as local, and is installed. The transaction DFHTDSUB.
was local since the Remote attributes were not set in the
XMEOUT Parameters: applid, dlblname, X'retcode', X'fdbkcode'
transaction definition, yet the dynamic parm indicated that
it could be remote.
v For DESTFAC (destination facility) of SYSTEM or
TERMINAL, the named facility must exist, and any required DFHTD0361 applid Logical I/O error occurred during a
system links must be installed and in service. PUT request to the intrapartition data set
(DLBL name dlblname); VSAM return codes
Note: Do not attempt to reroute this message to a transient are R15=X'retcode', FDBK=X'fdbkcode'.
data queue. Explanation: An attempt to (re)write a control interval to the
Module: DFHTDB from code contained in copybook intrapartition data set with DLBL name dlblname has failed
DFHTDSUB due to a logical I/O error. retcode is the return code in register
15 and fdbkcode is the value of the feedback field in the request
XMEOUT Parameters: applid, tranid,queue
parameter list (RPL).
DFHTD0343 date time applid Automatic transaction restart not terminate.
for transaction tranid processing TD queue
queue-name has failed.
Explanation: A transaction that was attached when a TD
trigger level was reached is ending abnormally and automatic Message DFHME0116 is normally produced containing the
transaction restart was requested for this transaction via the symptom string for this problem.
user replaceable module DFHREST. A severe error occurred User response: For the meaning of the codes in the message,
when CICS attempted to restart the transaction. refer to section "VSE/VSAM Codes" in z/VSE Messages and
System action: Message DFHAP0002 is issued with a dump Codes - Volume 2.
for the severe error that caused the restart to fail. Abnormal
termination of the transaction for which restart was requested You need further assistance from IBM to resolve this problem.
continues. The transaction is not automatically restarted. See Part 4 of the CICS Problem Determination Guide for
The system attempts to reattach the trigger level transaction
when the next TD request is received for this TD queue and
the trigger level has been reached or exceeded. Note: Do not attempt to reroute this message to a transient
User response: Investigate the reason for the earlier severe data queue.
error. See message DFHAP0002 for further guidance. Module: DFHTDB from code contained in copybook
DFHTDSUB.
Note: Do not attempt to reroute this message to a transient XMEOUT Parameters: applid, dlblname, X'retcode', X'fdbkcode'
data queue. Destination: Console
Module: DFHTDXM
XMEOUT Parameters: date, time,applid, tranid, queue-name DFHTD0362 applid Physical I/O error occurred during a
Destination: Console GET request to the intrapartition data set
(DLBL name dlblname); VSAM return codes
DFHTD0360 applid Logical I/O error occurred during a are R15=X'retcode', FDBK=X'fdbkcode'.
GET request to the intrapartition data set Explanation: An attempt to read a control interval from the
(DLBL name dlblname); VSAM return codes intrapartition data set with DLBL name dlblname has failed
are R15=X'retcode', FDBK=X'fdbkcode'. due to a physical I/O error. retcode is the return code in
Explanation: An attempt to read a control interval from the register 15 and fdbkcode is the value of the feedback field in the
intrapartition data set with DLBL name dlblname has failed request parameter list (RPL).
due to a logical I/O error. retcode is the return code in register System action: A system dump with dumpcode TD0362 is
15 and fdbkcode is the value of the feedback field in the request taken unless you have specifically suppressed dumps in the
parameter list (RPL). dump table.
even if you have specified in the dump table that CICS should This is a critical error and CICS is terminated, even if you
not terminate. have specified in the dump table that CICS should not
terminate.

User response: For the meaning of the codes in the message, which, if the queue is not empty, are relative byte addresses
refer to section "VSE/VSAM Codes" in z/VSE Messages and (RBAs) associated with the intrapartition data set with
Codes - Volume 2. dlblname.
A copy of the physical error message produced by VSAM Furthermore each allocated control interval, apart from the
appears in (one of) the transient data VSAM error message first, contains one or more user records as well as a queue
area(s) in the system dump. control record. This latter record, the first in the control
interval, contains the forward chain pointer or RBA for the
Note: Do not attempt to reroute this message to a transient next control interval containing data for the queue.
data queue. In each case, transient data assumes that RBAs address record
Module: DFHTDB from code contained in copybook boundaries within the intrapartition data set.
DFHTDSUB.
The assumption can be violated in several ways. The type of
XMEOUT Parameters: applid, dlblname, X'retcode', X'fdbkcode' violation may be determined from:
Destination: Console v A control interval print of the intrapartition data set, or
v Using access method services, or
DFHTD0363 applid Physical I/O error occurred during a v Using the system dump.
PUT request to the intrapartition data set
(DLBL name dlblname); VSAM return codes Violations include:
are R15=X'retcode', FDBK=X'fdbkcode'. v THE WRONG INTRAPARTITION DATA SET WAS USED If
Explanation: An attempt to (re)write a control interval to the the wrong data set has been used, that is, the data set used
intrapartition data set with DLBL name dlblname has failed for this CICS start up was not used for the previous CICS
due to a physical I/O error. retcode is the return code in start up, it is probable that most of the RBAs in the DCTEs
register 15 and fdbkcode is the value of the feedback field in the will not address record boundaries in the intrapartition data
request parameter list (RPL). set. CICS may be restarted but transient data must be
System action: A system dump with dumpcode TD0363 is COLD STARTED.
taken unless you have specifically suppressed dumps in the v THE INTRAPARTITION DATA SET WAS ALTERED If the
dump table. records have been moved, possibly through data set
compression, it is probable that control interval 0 will
This is a critical error and CICS is terminated, even if you contain more than one record and that most of the RBAs in
have specified in the dump table that CICS should not the DCTEs will not address record boundaries in the
terminate. intrapartition data set. CICS may be restarted but transient
User response: For the meaning of the codes in the message, data must be COLD STARTED.
refer to section "VSE/VSAM Codes" in z/VSE Messages and v A DCTE WAS CORRUPTED If a DCTE has been corrupted
Codes - Volume 2. then it is highly probable that just one or two RBAs will not
A copy of the physical error message produced by VSAM will address record boundaries in the intrapartition data set. A
appear in (one of) the transient data VSAM error message specialized trap may be required to identify the offending
area(s) in the system dump. program.
CICS may be restarted. An emergency restart for transient
Note: Do not attempt to reroute this message to a transient data will result in the RBAs being reconstructed from the
data queue. system log and the intrapartition data set.
DFHTDSUB. Note: If an activity keypoint was taken between the
occurrence of the error and its detection then it may prove
XMEOUT Parameters: applid, dlblname, X'retcode', X'fdbkcode' necessary for transient data to be COLD STARTED.
Destination: Console v AN I/O BUFFER WAS CORRUPTED If an I/O buffer has
been corrupted then it is highly probable one of the RBAs
DFHTD0380 applid Illegal attempt to read control interval in the DCTE will not address record boundaries in the I/O
0 for the intrapartition data set (DLBL name buffer. A specialized trap may be required to identify the
dlblname). offending program.
Explanation: Control interval 0 in the intrapartition data set CICS may be restarted. An emergency restart for transient
is reserved for transient data control information. The data results in the RBAs being reconstructed from the
remaining control intervals are allocated to hold data for system log and the intrapartition data set.
queues as determined by transient data processing on behalf Note: If the contents of the I/O buffer were written to the
of application program requests. intrapartition data set between the occurrence of the error
An invalid attempt has been made to read control interval 0 and its detection then it may prove necessary for transient
for the intrapartition data set with DLBL name dlblname. data to be COLD STARTED.
System action: This is a critical error and CICS is terminated, v A CICS LOGIC ERROR OCCURRED You need further
even if you have specified in the dump table that CICS should assistance from IBM to resolve this problem. See Part 4 of
not terminate. the CICS Problem Determination Guide for guidance on how
to proceed.
have specifically suppressed dumps in the dump table. Note: Do not attempt to reroute this message to a transient
Message DFHME0116 is normally produced containing the data queue.
symptom string for this problem. Module: DFHTDB from code contained in copybook
User response: Each intrapartition DCTE contains pointers DFHTDSUB.

XMEOUT Parameters: applid, dlblname A system dump with dumpcode TD0383 is taken unless you
Destination: Console have specifically suppressed dumps in the dump table.
DFHTD0381 applid Invalid attempt to (re)write control symptom string for this problem.
interval 0 for the intrapartition data set User response: refer to message DFHTD0380.
(DLBL name dlblname).
Explanation: Control interval 0 in the intrapartition data set Note: Do not attempt to reroute this message to a transient
is reserved for transient data control information; the data queue.
remaining control intervals are allocated to hold data for Module: DFHTDB from code contained in copybook
queues as determined by Transient Data processing on behalf DFHTDSUB.
of application program requests.
XMEOUT Parameters: applid, qqqq,dlblname
An invalid attempt has been made to (re)write control interval Destination: Console
0 for the intrapartition data set with DLBL name dlblname.
even if you have specified in the dump table that CICS should DFHTD0384 applid A forward chain pointer for queue qqqq
not terminate. does not match the contents of the
intrapartition data set (DLBL name dlblname).
A system dump with dumpcode TD0381 is taken unless you Explanation: A forward chain pointer for queue qqqq is
have specifically suppressed dumps in the dump table. invalid with respect to the intrapartition data set with DLBL
name dlblname.
User response: refer to message DFHTD0380.
not terminate.
Note: Do not attempt to reroute this message to a transient A system dump with dumpcode TD0384 is taken unless you
data queue. have specifically suppressed dumps in the dump table.
DFHTDSUB.
XMEOUT Parameters: applid, dlblname User response: Refer to message DFHTD0380.
data queue.
DFHTD0382 applid The output pointer for queue qqqq does
not match the contents of the intrapartition
DFHTDSUB.
data set (DLBL name dlblname).
Explanation: The output pointer for queue qqqq does not XMEOUT Parameters: applid, qqqq,dlblname
address a record boundary within the intrapartition data set Destination: Console
with DLBL name dlblname.
even if you have specified in the dump table that CICS should DFHTD0385 applid Invalid attempt to allocate/deallocate
not terminate. CI 0 for the intrapartition data set (DLBL
name dlblname).
A system dump with dumpcode TD0382 is taken unless you Explanation: Control interval (CI) 0 in the intrapartition data
have specifically suppressed dumps in the dump table. set, dlblname, is reserved for transient data control information.
The remaining control intervals are allocated to hold data for
queues as determined by transient data processing on behalf
of application program requests.
User response: Refer to message DFHTD0380.
System action: System dump TD0385 is taken unless you
data queue. This is a critical error. CICS is terminated even if you have
Module: DFHTDB from code contained in copybook specified in the dump table that CICS should not terminate.
DFHTDSUB. User response: Refer to the User Response of message
DFHTD0380.
XMEOUT Parameters: applid, qqqq,dlblname
data queue.
DFHTD0383 applid The input pointer for queue qqqq does Module: DFHTDB from code contained in copybook
not match the contents of the intrapartition DFHTDSUB
data set (DLBL name dlblname).
XMEOUT Parameters: applid, dlblname
Explanation: The input pointer for queue qqqq does not
address a record boundary within the intrapartition data set
with DLBL name dlblname.
not terminate.


DFHTD1210 applid DCT index in error, xxxx failed
data queue.
Explanation: While carrying out operation xxxx
(CREATEINDEX, ADD, LOCATE, or GETNEXT), CICS found Module: DFHTDRP
an error in the destination control table (DCT) index. The most XMEOUT Parameter: applid
likely reasons for this error are: Destination: Console
v A storage violation. An application program has overwritten
the index,
v A CICS logic error. The CICS table mapping program, DFHTD1212 applid Unrecognizable entry found in the
DFHTMP, created the index incorrectly. DCT
System action: CICS writes a dump. The transaction Explanation: During initialization, CICS found an
abnormally terminates with abend code ATDY and message unrecognizable entry in the destination control table (DCT).
DFHSI1522 is issued. This means that the loaded DCT is in error – either a
DFHDCT macro was coded incorrectly, or the output of the
macro assembly was corrupted.
System action: CICS ignores the unrecognizable DCT entry
User response: Respond GO or CANCEL to message
and all subsequent DCT entries, and continues initialization.
DFHSI1522.
User response: Depending on how many DCT entries CICS
The CICS Data Areas manual gives the format of the DCT has ignored, you may have almost all or very few transient
index entries, under TMDEL and TMSKT. Find these entries in data destinations available in the initialized run. You must
the dump and find the invalid data, which may help you to decide whether or not to terminate CICS. To solve the problem
decide if the problem is caused by a storage violation or a permanently, remove or replace the invalid DCT entry.
CICS error.
Assuming that the error is a storage violation, and that you
data queue.
have activated the trace facility, find in the trace the
Module: DFHTDRP
unsuccessful attempt to access the DCT by DFHTDP. Then
find the last preceding successful access. You have now XMEOUT Parameter: applid
narrowed the search to programs that were running between Destination: Console
these two accesses. Examine these programs for an error that
could cause a storage violation.
DFHTD1213 applid Duplicate entry for xxxx found in the
If you have not activated trace, but you can recreate the error, DCT
activate trace, recreate the error, and proceed as in the Explanation: During initialization, CICS found a duplicate
previous paragraph. entry in the destination control table (DCT) for destination
xxxx. Either the entries are true duplicates, or one entry
Note: Do not attempt to reroute this message to a transient contains an incorrect destination name.
data queue. System action: CICS ignores the duplicate DCT entry, and
Module: DFHTDRP continues initialization.
User response: First, decide whether you want CICS to
XMEOUT Parameters: applid, xxxx continue without the ignored entry. If the entry is not a true
Destination: Console duplicate, you may be running without an important
destination. To solve the problem permanently, either remove
DFHTD1211 applid DCT in error the duplicate entry from the DCT, or correct its destination
Explanation: CICS found corrupted data in the DCT. name.
At CICS initialization, the table management program Note: Do not attempt to reroute this message to a transient
(DFHTMP) set up index links to the destination control table data queue.
(DCT) which were then validly formatted. Module: DFHTDRP
Since initialization, the DCT has been overwritten, almost XMEOUT Parameters: applid, xxxx
certainly by an application program (storage violation). Destination: Console
System action: CICS writes a dump. The transaction
abnormally terminates with abend code ATDY and message
DFHSI1522 is issued. DFHTD1214 applid No entry for xxxx found in the DCT
Explanation: During warm or emergency restart, the
Message DFHME0116 is normally produced containing the transient data recovery program (DFHTDRP) read a catalog or
symptom string for this problem. recovery record for destination xxxx. However, the DCT
User response: Respond GO or CANCEL to message contains no entry for destination xxxx. Almost certainly you
DFHSI1522. are using a different DCT from the one that was in use when
Assuming that you have activated the trace facility, find in the CICS abnormally terminated.
trace the unsuccessful attempt to access the DCT by System action: CICS ignores the record and continues
DFHTDRP. Then find the last preceding successful access. You initialization.
have now narrowed the search to programs that were running User response: First, decide whether you want CICS to
between these two accesses. continue without the missing transient data destination which
will not be recovered and cannot be accessed in this run. The
If you have not activated trace, but you can recreate the error, safest action is to cancel CICS and perform another emergency
activate trace, recreate the error, and proceed as in the restart with the correct DCT.
previous paragraph.

Note: Do not attempt to reroute this message to a transient XMEOUT Parameter: applid
Module: DFHTDRP
XMEOUT Parameters: applid, xxxx DFHTD1221 applid DCT not restored, xxxx failed
Destination: Console Explanation: During a warm start, while carrying out
operation xxxx (CONNECT, STARTBROWSE, GETNEXT,
ENDBROWSE, or DISCONNECT), the transient data recovery
DFHTD1215 applid Conflicting entry for xxxx found in the
program (DFHTDRP) found an error in the destination control
DCT
table (DCT) catalog.
Explanation: During a warm start, the transient data
recovery program (DFHTDRP) has read a catalog or recovery The most likely reasons for this error are I/O errors in the
record for destination xxxx. However, the destination control catalog data set, or a logic error in the CICS module,
table (DCT) entry for destination xxxx conflicts with the DFHCCCC.
destination definition in the record. Almost certainly you are System action: CICS writes a dump. The transaction
using a different DCT from the one in use when CICS abnormally terminates with abend code ATDY and message
terminated. DFHSI1522 is issued.
System action: CICS ignores the record and continues
initialization. Message DFHME0116 is normally produced containing the
User response: First, decide whether you want CICS to symptom string for this problem.
continue without the ignored record. If not, cancel CICS, and User response: Respond GO or CANCEL to message
restart with the correct DCT. DFHSI1522.
Determine and correct the I/O errors on the catalog data set.
Note: Do not attempt to reroute this message to a transient If you cannot restore the catalog data set, or suspect that there
data queue. might be a CICS logic error in DFHCCCC, you will need
Module: DFHTDRP further assistance from IBM. See Part 4 of the CICS Problem
data queue.
DFHTD1216 applid Loop starting with indirect entry xxxx Module: DFHTDRP
found in the DCT
Explanation: During initialization, the transient data recovery
program (DFHTDRP) followed a chain of indirection pointers
beginning with destination control table (DCT) entry xxxx and
found the chain to be endless. DFHTD1222 applid Unrecognizable entry found in a CSM
System action: CICS sets the indirection pointer in entry xxxx catalog record
to zero and continues initialization. Explanation: CICS has found an unrecognizable entry in an
User response: Check all DCT entries defined as DFHRSD catalog record for the CSM (control interval state
TYPE=INDIRECT. Correct the entry (or entries) in error. map or transient data bit map). An error may have occurred
during the last CICS shutdown, resulting in the overwriting of
Note: Do not attempt to reroute this message to a transient the CSM.
data queue. System action: CICS writes a dump and terminates
Module: DFHTDRP abnormally.
XMEOUT Parameters: applid, xxxx Message DFHME0116 is normally produced containing the
Destination: Console symptom string for this problem.
DFHTD1220 applid Unrecognizable entry found in a DCT Determination Guide for guidance on how to proceed.
catalog record
Explanation: During a warm start, the transient data
recovery program (DFHTDRP) read a transient data catalog
data queue.
record containing an unrecognizable entry. You may have
Module: DFHTDRP
specified an incorrect data set in the startup job stream.
System action: CICS writes a dump and terminates XMEOUT Parameter: applid
abnormally. Destination: Console
symptom string for this problem. DFHTD1223 applid CSM not restored, xxxx failed
User response: If you cannot find an explanation (such as Explanation: While carrying out operation xxxx (CONNECT,
incorrect JCL), you will need further assistance from IBM. See STARTBROWSE, GETNEXT, ENDBROWSE, or
Part 4 of the CICS Problem Determination Guide for guidance on DISCONNECT), the transient data recovery program
how to proceed. (DFHTDRP) found an error in a catalog record for the control
interval state map (transient data bit map).
The most likely reasons for this error are I/O errors in the
data queue.
Module: DFHTDRP

catalog data set, or a logic error in the CICS module, Module: DFHTDRP
DFHCCCC.
DFHSI1522 is issued.
Message DFHME0116 is normally produced containing the DFHTD1232 applid CSM not recovered, {Forward Chain |
symptom string for this problem. Record Offset} in error for qname
User response: Respond GO or CANCEL to message Explanation: A forward chain or record offset error occurred
DFHSI1522. while attempting to recover the CI storage map for the
intrapartition transient data set (DFHNTRA). The field qname
Determine and correct the I/O errors on the catalog data set. gives the name of the transient data queue which could not be
If you cannot restore the catalog data set, or suspect that there recovered.
might be a CICS logic error in DFHCCCC, you will need
further assistance from IBM. See Part 4 of the CICS Problem The most likely reasons for this error are corrupted data on
Determination Guide for guidance on how to proceed. the intrapartition data set or I/O errors on the intrapartition
data set.
data queue.
Module: DFHTDRP
DFHSI1522.
DFHTD1230 applid Unrecognizable entry found in a DCT
If you cannot restore the intrapartition data set, you will need
recovery record
Explanation: CICS has found an unrecognizable entry in a
recovery record for the destination control table (DCT).
System action: CICS writes a dump and terminates
abnormally. Note: Do not attempt to reroute this message to a transient
data queue.
Message DFHME0116 is normally produced containing the Module: DFHTDRP
User response: You need further assistance from IBM to XMEOUT Parameters: applid, {1=Forward Chain, 2=Record
resolve this problem. See Part 4 of the CICS Problem Offset}, qname
Note: Do not attempt to reroute this message to a transient DFHTD1260 applid No DLBL statement for intrapartition
data queue. data set dlblname
Module: DFHTDRP Explanation: CICS is unable to open the intrapartition data
set dlblname because no DLBL statement has been provided.
DFHTD1231 applid DCT not recovered, xxxx failed User response: Respond GO or CANCEL to message
Explanation: While carrying out operation xxxx (CONNECT, DFHSI1522.
STARTBROWSE, GETNEXT, ENDBROWSE, or
Modify the CICS JCL to add a DLBL statement defining the
DISCONNECT), the transient data recovery program
intrapartition data set (DFHNTRA).
(DFHTDRP) found an error in a recovery record for the DCT.
The most likely reasons for this error are I/O errors in the Note: Do not attempt to reroute this message to a transient
recovery data set, or a logic error in the CICS module, data queue.
DFHRCP. Module: DFHTDRP
abnormally terminates with abend code ATDY and message XMEOUT Parameters: applid, dlblname
DFHSI1522 is issued. Destination: Console

symptom string for this problem. DFHTD1261 applid Intrapartition data set filename not
User response: Respond GO or CANCEL to message defined as VSAM ESDS
DFHSI1522. Explanation: CICS is unable to open the intrapartition data
set filename because it is not defined as VSAM ESDS.
If you cannot restore the recovery data set, you will need System action: CICS writes a dump. The transaction
further assistance from IBM. See Part 4 of the CICS Problem abnormally terminates with abend code ATDY and message
Determination Guide for guidance on how to proceed. DFHSI1522 is issued.
Note: Do not attempt to reroute this message to a transient DFHSI1522.
data queue.

Recreate the intrapartition data set as a VSAM ESDS and Note: Do not attempt to reroute this message to a transient
restart CICS. data queue.
Module: DFHTDRP
Note: Do not attempt to reroute this message to a transient XMEOUT Parameters: applid, filename, retcode
Module: DFHTDRP

DFHTD1272 applid VSAM error processing OPEN for
Intrapartition data set filename, R15=retcode,
RC=errorcode
DFHTD1262 applid Intrapartition data set filename not Explanation: VSAM has detected an error during OPEN
formatted processing for the intrapartition data set filename. retcode is the
Explanation: The intrapartition data set filename is not VSAM return code and errorcode is the VSAM error code.
formatted (it is empty). Initial formatting is done (if necessary) System action: CICS writes a dump. The transaction
when transient data is cold started. abnormally terminates with abend code ATDY and message
System action: CICS writes a dump. The transaction DFHSI1522 is issued.
DFHSI1522.
DFHSI1522.
Cold start CICS at the next bringup.
Check the VSAM return code and error code in section
data queue.
Module: DFHTDRP
data queue.
XMEOUT Parameters: applid, filename Module: DFHTDRP
XMEOUT Parameters: applid, filename, retcode, errorcode
DFHTD1263 applid Invalid control record for Intrapartition
data set filename DFHTD1273 applid VSAM error processing CLOSE for
Explanation: The intrapartition data set filename was not intrapartition data set filename, R15=retcode
initialized for intrapartition transient data. The most likely Explanation: VSAM has detected an error during CLOSE
reason for this is data corruption by VSAM export and import. processing for the intrapartition data set filename. retcode is the
System action: CICS writes a dump. The transaction VSAM return code.
abnormally terminates with abend code ATDY and message System action: CICS writes a dump. The transaction
DFHSI1522 is issued. abnormally terminates with abend code ATDY and message
User response: Respond GO or CANCEL to message DFHSI1522 is issued.
DFHSI1522.
Reinitialize the intrapartition data set. symptom string for this problem.
Note: Do not attempt to reroute this message to a transient DFHSI1522.
data queue.
Module: DFHTDRP Check the VSAM return code in section "VSE/VSAM Codes"
in z/VSE Messages and Codes - Volume 2.
Destination: Console Note: Do not attempt to reroute this message to a transient
data queue.
DFHTD1271 applid VSAM error processing SHOWCB for Module: DFHTDRP
intrapartition data set filename, R15=retcode XMEOUT Parameters: applid, filename, retcode
Explanation: VSAM has detected an error during SHOWCB Destination: Console
processing for the intrapartition data set filename with VSAM
return code retcode.
System action: CICS writes a dump. The transaction DFHTD1274 applid VSAM error processing PUT for
abnormally terminates with abend code ATDY and message intrapartition data set filename, R15=retcode,
DFHSI1522 is issued. RC=errorcode
Explanation: VSAM has detected an error during PUT
Message DFHME0116 is normally produced containing the processing for the intrapartition data set filename. retcode is the
symptom string for this problem. VSAM return code and errorcode is the VSAM error code.
User response: Respond GO or CANCEL to message System action: CICS writes a dump. The transaction
DFHSI1522. abnormally terminates with abend code ATDY and message
Check the VSAM return code retcode in section "VSE/VSAM DFHSI1522 is issued.
Codes" in z/VSE Messages and Codes - Volume 2. Message DFHME0116 is normally produced containing the

User response: Respond GO or CANCEL to message Destination: Console

DFHSI1522.
Check the VSAM return code and error code in section DFHTD1279 applid Unexpected response (code X'response')
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2. and reason (code X'reason') from a dfhxxyym
call.
Note: Do not attempt to reroute this message to a transient Explanation: Module DFHTDRP detected the failure of a
data queue. dfhxxyym call to domain xx.
Module: DFHTDRP
XMEOUT Parameters: applid, filename, retcode, errorcode those returned from the domain call (that is, xxyy_response and
Destination: Console xxyy_reason).
This can be due to a CICS logic error.
DFHTD1275 applid VSAM error processing GET for System action: Transient data initialization continues.
intrapartition data set filename, R15=retcode, User response: Refer to earlier messages and the dump
RC=errorcode produced by domain xx.
Explanation: VSAM has detected an error during GET
processing for the intrapartition data set filename. retcode is the
VSAM return code and errorcode is the VSAM error code.
DFHSI1522 is issued. Note: Do not attempt to reroute this message to a transient
data queue.
Message DFHME0116 is normally produced containing the Module: DFHTDRP
User response: Respond GO or CANCEL to message XMEOUT Parameters: applid, X'response', X'reason', dfhxxyym
DFHSI1522. Destination: Console
Check the return code and error code in section "VSE/VSAM

Codes" in z/VSE Messages and Codes - Volume 2. DFHTD1280 applid An attempt to establish security has
failed for userid userid. SAF codes are
(X'safresp',X'safreas'). ESM codes are
data queue.
Explanation: An attempt was made to establish security for
Module: DFHTDRP
userid userid. The attempt was rejected by the external security
XMEOUT Parameters: applid, filename, retcode, errorcode manager (ESM).
Destination: Console System action: Security has not been established for the
userid.
DFHTD1278 applid An error occurred during initialization safreas) returned by the system authorization facility (SAF),
of intrapartition queue queuename for userid and the response and reason codes (esmresp and esmreas)
userid. ATI for non-terminal transactions has returned by the external security manager (ESM) are those
been deactivated for this queue. issued by the RACROUTE REQUEST=VERIFY or RACROUTE
Explanation: Transient data initialization detected an error REQUEST=EXTRACT macros. For the meaning of the
with userid userid during initialization of the intrapartition response and reason codes in the message see "BSM Return
queue for automatic transaction initiation. Codes" in section "VSE/Advanced Functions Codes & SVC
The specified userid is not valid for use by this CICS job for Errors" of z/VSE Messages and Codes - Volume 1.
nonterminal transactions initiated by the transient data trigger. There may be further messages produced by CICS or the
There may be a previous message which gives the cause of external security manager (ESM) which provide more
this error. information.
System action: Transient data initialization continues.
If the intrapartition queue has been defined without a data queue.
terminal, automatic transaction initiation for the queue is Module: DFHTDRP
deactivated.
User response: Notify the systems programmer. XMEOUT Parameters: applid, userid,X'safresp', X'safreas',
X'esmresp',X'esmreas'
If the userid is invalid, correct the userid specified in the Destination: Console
resource definition for the intrapartition
If the userid is valid, ensure that it can be used by DFHTD1290 applid Program DFHTDRP cannot be found.
nonterminal transactions that are initiated by trigger for the Explanation: CICS cannot link to the transient data recovery
intrapartition queue. program (DFHTDRP).
Note: Do not attempt to reroute this message to a transient CICS cannot find DFHTDRP in any sublibrary of the LIBDEF
data queue. search chain for the CICS startup job stream.
Module: DFHTDRP System action: Transient data initialization terminates
abnormally. CICS continues initialization, and unless canceled,
XMEOUT Parameters: applid, queuename, userid

DFHTF0001 • DFHTF0101
runs without support for transient data. Module: DFHTDX

User response: To correct this error, place DFHTDRP in a
stream. Destination: Console

data queue.
DFHTFxxxx messages
DFHTF0001 applid An abend (code aaa/bbbb) has occurred
that CICS should terminate. In some circumstances CICS is
terminated directly if the error is critical.
occurred in module modname. This implies that there may be Message DFHME0116 is normally produced containing the
an error in the CICS code. Alternatively, unexpected data has symptom string for this problem.
been input, or storage has been overwritten. User response: This indicates a possible error in CICS code.
The VSE code is a system completion code, for example 0C1. CICS may not have been terminated. If the message occurs
If a VSE code is not applicable, this field is filled with three once and module modname is not crucial to the running of
hyphens. The CICS code is an abend code or a number your CICS system, you may decide to continue to run and
referring to a CICS message (for example, AKEA is a CICS bring CICS down at a convenient time to resolve the problem.
System action: An exception entry is made in the trace table. If the message recurs or if you cannot run without the full use
A system dump is taken, unless you have specifically of module modname, you should bring CICS down in a
suppressed dumps in the dump table. controlled shutdown.
CICS continues unless you have specified in the dump table You need further assistance from IBM to resolve this problem.
that CICS should terminate. In some circumstances CICS is See Part 4 of the CICS Problem Determination Guide for
terminated directly if the error occurred in a crucial XM guidance on how to proceed.
domain module. Module: DFHTFIQ, DFHZSUP, DFHTFRF, DFHTFAL
Message DFHME0116 is normally produced containing the XMEOUT Parameters: applid, X'code',modname
DFHTF0100 date time applid nnnn AIDs canceled for
Look up the VSE code, if there is one, in "OS/390 API Abend terminal termid. nnnn AIDs remain.
Codes" in section "VSE/Advanced Functions Codes & SVC Explanation: AIDs queuing for terminal termid have been
Errors" of z/VSE Messages and Codes - Volume 1. canceled. This could be due to the terminal being deleted, or
as a result of an SPI or CEMT SET TERMINAL(termid)
Next, look up the CICS alphanumeric code in “Transaction CANCEL command. Any AIDs remaining after this operation
Abend Codes (CICS Transaction Server for VSE/ESA)” on are also enumerated in this message. For programming
page 453. information about CICS SET TERMINAL, see the CICS System
If module modname is not crucial to the running of your CICS Programming Reference. For information about the equivalent
system, you may decide to continue to run and bring CICS CEMT command, see the CICS Supplied Transactions.
down at a convenient time to resolve the problem. System action: Requests represented as AIDs queuing for the
terminal have been purged from the system.
If you cannot run without the full use of module modname you User response: None.
should bring CICS down in a controlled shutdown. Module: DFHALP
You need further assistance from IBM to resolve this problem. XMEOUT Parameters: date, time,applid, nnnn, termid, nnnn
See Part 4 of the CICS Problem Determination Guide for Destination: CSMT
Module: DFHTFIQ, DFHZSUP, DFHTFRF, DFHTFAL
DFHTF0101 date time applid nnnn AIDs {canceled |
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname force-canceled} for connection conname. nnnn
Destination: Console AIDs remain.
Explanation: AIDs queuing for connection conname have been
canceled or force-canceled. This could be due to connection
DFHTF0002 applid A severe error (code X'code') has reinstall, or as a result of a SPI or CEMT SET
occurred in module modname. CONNECTION(conname) CANCEL or FORCECANCEL
Explanation: An error has been detected in module modname. command. Any AIDs remaining after this operation are also
The code X'code' is the exception trace point ID which enumerated in this message.
uniquely identifies what the error is and where the error was System action: Requests represented as AIDs queuing for the
detected. connection will have been purged from the system.
System action: An exception entry (code X'code' in the User response: None.
message) is made in the trace table. A system dump is taken, Module: DFHALP
table. XMEOUT Parameters: date, time,applid, nnnn,

DFHTI0001 • DFHTI0005
{1=canceled,2=force-canceled}, conname, nnnn Destination: CSMT
DFHTIxxxx messages
DFHTI0001 applid An abend (code aaa/bbbb) has occurred
could be terminated by the caller (for example the domain
occurred in module module. This implies that there may be an
error in CICS code. Alternatively, unexpected data has been
input, or storage has been overwritten.
bring CICS down.
module modname has gone into a loop, you have to terminate
suppressed dumps in the dump table. If CICS has terminated module modname and you consider
temporarily online, using the CEMT transaction.
could be terminated by the caller (for example the domain
manager, DFHDMDM). A message is issued to this effect. If raising the ICVR time does not solve the problem, you will
User response: Notify the system programmer. If CICS is still need further assistance from IBM. See Part 4 of the CICS
running, it is necessary to decide whether to terminate CICS. Problem Determination Guide for guidance on how to proceed.
Module: DFHTISR, DFHTIDM
Codes" in section "VSE/Advanced Functions Codes & SVC XMEOUT Parameters: applid, X'offset', modname
Errors" of z/VSE Messages and Codes - Volume 1. Destination: Console
Abend Codes (CICS Transaction Server for VSE/ESA)” on DFHTI0005 applid A hardware error has occurred (module
page 453. This tells you, for example, whether the error was a modname, code X'code'). The Time-of-Day clock
program check, an abend, or a runaway, and may give you is invalid.
some guidance concerning user response. Explanation: An error has occurred during the running of
If module modname is not crucial to the running of your CICS module modname. The store clock facility is the timing
system, you may decide to continue to run and bring CICS mechanism for the operating system.
down at a convenient time to resolve the problem. The code X'code' is the exception trace point id which uniquely
If you cannot run without the full use of module modname you identifies the place where the error was detected.
should bring CICS down in a controlled shutdown. Message DFHME0116 is normally produced containing the
You need further assistance from IBM to resolve this problem. symptom string for this problem.
See Part 4 of the CICS Problem Determination Guide for System action: An exception entry (code X'code' in the
guidance on how to proceed. message) is made in the trace table. A system dump is taken,
Module: DFHTISR, DFHTIDM unless you have specifically suppressed dumps in the dump
table.
Destination: Console CICS continues if possible, unless you have specified in the
dump table that CICS should terminate. If appropriate, an
error return code is sent to the caller of this domain. In this
DFHTI0004 applid A possible loop has been detected at case, CICS could be terminated by the caller (for example the
offset X'offset' in module modname. domain manager, DFHDMDM). A message is issued to this
Explanation: A CICS function is taking more time to process effect.
than CICS expects. A possible loop has been detected in User response: If CICS is still running, it is necessary to
module modname at offset X'offset'. This is the offset of the decide whether to terminate CICS. First, investigate the store
instruction which was executing at the time when the error clock and find out whether it is working properly. If this is the
was detected. cause, you should take the appropriate action to have it
repaired or replaced.
symptom string for this problem. In the unlikely event that this is not a hardware problem, you
System action: An exception entry is made in the trace table. will need further assistance from IBM. See Part 4 of the CICS
A system dump is taken, unless you have specifically Problem Determination Guide for guidance on how to proceed.
suppressed dumps in the dump table. Module: DFHTISR, DFHTIDM
CICS continues unless you have specified in the dump table XMEOUT Parameters: applid, modname,X'code'

DFHTM1703 • DFHTM1781
DFHTMxxxx messages
DFHTM1703 applid product is being terminated by userid
Module: DFHSTP
userid in transaction tranid{at netname | at
terminal }terminal. XMEOUT Parameter: applid
Explanation: This message is issued after a PERFORM SHUT Destination: Console
IMMEDIATE request.
System action: The termination process continues.
User response: None. DFHTM1715 applid product is being quiesced by userid
Module: DFHSTP userid in transaction tranid{at netname | at
terminal }terminal.
XMEOUT Parameters: applid, product,userid, tranid, {1= at Explanation: This message is issued after a PERFORM SHUT
netname, 2= at terminal }, terminal request.
Destination: Console and Terminal End User System action: Quiesce of CICS continues.
Module: DFHSTP
DFHTM1707I applid Program DFHWKP cannot be found.
No warm keypoint taken. XMEOUT Parameters: applid, product,userid, tranid, {1= at
Explanation: CICS cannot take a warm keypoint because the netname, 2= at terminal }, terminal
CICS module, DFHWKP, cannot be found in any sublibrary of Destination: Console and Terminal End User
the LIBDEF search chain for the CICS startup job stream.
System action: CICS passes control to the user phase 1 PLT
program. DFHTM1752 applid PLT - program progname not available.
User response: None. Explanation: The program list table (PLT) specified for
Module: DFHSTP shutdown contains program progname, but CICS is unable to
link to the program because one of the following has occurred:
XMEOUT Parameter: applid v An executable copy of the program could not be brought
Destination: Console into storage.
v The installed definition for the program is disabled.
DFHTM1709I applid About to link to PLT programs. v There is no installed definition for the program.
Explanation: DFHSTP is about to link to the user PLT System action: CICS termination continues without executing
program PLTSD parameter in the system initialization table. program progname.
System action: Control is passed to the user PLT programs. User response: In the next execution, check that each
User response: None. program specified in the PLT is contained in a sublibrary of
Module: DFHSTP the LIBDEF search chain for the CICS startup job stream, and
ensure that the program is defined and enabled.
XMEOUT Parameter: applid Module: DFHSTP
DFHTM1710I applid Control returned from PLT programs.
Explanation: Control is returned to DFHSTP to continue
system initialization. DFHTM1780 applid Abend has occurred while processing
System action: Control is returned to DFHSTP. program progname during termination,
User response: None. code=abcode.
Module: DFHSTP Explanation: Program progname specified in the program list
XMEOUT Parameter: applid table (PLT) for shutdown has abnormally terminated. abcode is
Destination: Console the CICS transaction abend code.
System action: Control is passed to the next program
specified in the PLT and a CICS dump is supplied for review.
DFHTM1711I applid About to link to phase 2 PLT programs. User response: Look up the CICS transaction abend code in
Explanation: DFHSTP is about to link to the phase 2 PLT “Transaction Abend Codes (CICS Transaction Server for
programs as defined by the PLTSD system initialization VSE/ESA)” on page 453 for further information about the
parameter. error. Try and correct program progname.
System action: CICS passes control to the phase 2 user PLT Module: DFHSTP
programs.
User response: None. XMEOUT Parameters: applid, progname, abcode
Module: DFHSTP Destination: Console
Destination: Console DFHTM1781 applid CICS shutdown cannot complete
because some non-system user tasks have not
terminated.
DFHTM1712I applid Control returned from phase 2 PLT
Explanation: This message is issued during shutdown of the
programs.
Explanation: CICS returns control to DFHSTP so that system CICS session and indicates that one or more CICS tasks are
shutdown may continue. still active, thereby preventing the successful termination of
System action: CICS returns control to DFHSTP. CICS.
System action: CICS shutdown waits until the active task or

DFHTM1782I • DFHTO6003E
tasks are successfully terminated. hung), and take whatever steps are necessary to resolve the
User response: Determine, which CICS tasks are still situation.
running, using the CEMT INQUIRE TASK command, for Module: DFHSTP
example, and take whatever steps are necessary to terminate
them.
Module: DFHSTP
Destination: Console DFHTM1797 applid System termination program has
abended.
Explanation: While terminating CICS, the CICS system
DFHTM1782I applid All non-system tasks have been termination program DFHSTP has abnormally terminated.
successfully terminated. System action: CICS terminates abnormally with a system
Explanation: This message is issued during shutdown of the dump.
CICS session after successful termination by the user of any User response: Try to find out why DFHSTP terminated. If
active tasks which had previously prevented termination. you cannot resolve the problem, you will need assistance from
System action: CICS shutdown continues normally. IBM. See Part 4 of the CICS Problem Determination Guide for
User response: None guidance on how to proceed.
Module: DFHSTP Module: DFHSTP
DFHTM1783 applid CICS shutdown cannot complete DFHTM1798 applid Requested dump in progress.
because a system task which prevents normal Explanation: This message is issued when CICS is terminated
shutdown has not terminated. before the requested dump has started.
Explanation: This message is issued during shutdown of the System action: CICS produces a system dump and shutdown
CICS session and indicates that CICS system transaction CLS1 continues.
is still active, thereby preventing the successful termination of User response: None.
CICS. Module: DFHSTP
System action: CICS shutdown waits until the active task is
successfully terminated. XMEOUT Parameter: applid
User response: Determine, what is delaying the CLS1 Destination: Console
transaction (for example the other CICS job or system being
DFHTOxxxx messages
DFHTO6000E date time applid The definition for TERMINAL DFHTO6002E date time applid The definition for SESSIONs
termdef refers to an undefined TYPETERM sesdef refers to an undefined CONNECTION
termtype. condef.
Explanation: While installing a GRPLIST during Explanation: While installing a GRPLIST during
initialization, or while executing a CEDA CHECK, a CEDA initialization, or while executing a CEDA CHECK, a CEDA
INSTALL, or an EXEC CICS CREATE command, CICS INSTALL, or an EXEC CICS CREATE command. CICS
detected a TERMINAL definition (termdef) that referenced an detected a SESSIONS definition (sesdef) that referenced a
nonexistent TYPETERM definition (termtype). nonexistent CONNECTION definition (condef).
System action: The TERMINAL is not installed. System action: The SESSIONS definition is not installed.
User response: Correct the TERMINAL definition or define User response: Correct the SESSIONS definition or define the
the named TYPETERM. named CONNECTION.
Module: DFHTOR Module: DFHTOR
XMEOUT Parameters: date, time,applid, termdef, termtype XMEOUT Parameters: date, time,applid, sesdef, condef
Destination: CSMT Destination: CSMT
DFHTO6001E date time applid The definition for pooled DFHTO6003E date time applid TERMINAL termdef specifies
TERMINAL termdef refers to an undefined CONSNAME but refers to TYPETERM
TYPETERM termtype. termtype which does not specify
Explanation: While installing a GRPLIST during DEVICE=CONSOLE.
initialization, or while executing a CEDA CHECK, a CEDA Explanation: While installing a GRPLIST during
INSTALL, or an EXEC CICS CREATE command, CICS initialization, or while executing a CEDA CHECK, a CEDA
detected a TERMINAL definition (termdef) that referenced a INSTALL, or an EXEC CICS CREATE command, CICS
nonexistent TYPETERM definition (termtype). detected a TERMINAL definition termdef, specified with
System action: The TERMINAL is not installed. CONSNAME=name, which referred to a TYPETERM definition
User response: Correct the TERMINAL definition or define termtype specified without DEVICE=CONSOLE.
the named TYPETERM. System action: The TERMINAL definition is not installed.
Module: DFHTOR (The TYPETERM definition is installed and may be referred to
by other compatible TERMINAL definitions).
XMEOUT Parameters: date, time,applid, termdef, termtype User response: Correct the TERMINAL or TYPETERM
Destination: CSMT definition.

DFHTO6004E • DFHTO6011E
Module: DFHTOR
DFHTO6007E date time applid AUTINSTMODEL YES|ONLY
XMEOUT Parameters: date, time,applid, termdef, termtype for TERMINAL termdef is invalid for the
Destination: CSMT DEVICE specified in TYPETERM termtype.
Explanation: While installing a GRPLIST during
initialization, or while executing a CEDA CHECK, a CEDA
DFHTO6004E date time applid TERMINAL termdef does not INSTALL, or an EXEC CICS CREATE command, CICS
specify CONSNAME but refers to detected a TERMINAL definition (termdef) specified with
TYPETERM termtype which specifies AUTINSTMODEL=[YES|ONLY], which referred to a
DEVICE=CONSOLE. TYPETERM definition (termtype) that specified
Explanation: While installing a GRPLIST during DEVICE=3614|TLX|TWX, or was a PIPELINE terminal.
initialization, or while executing a CEDA CHECK, a CEDA System action: The TERMINAL definition is not installed.
INSTALL, or an EXEC CICS CREATE command, CICS (The TYPETERM definition is installed and may be referenced
detected a TERMINAL definition (termdef), specified without a by other compatible TERMINAL definitions).
CONSNAME, which referred to a TYPETERM definition User response: Correct the TERMINAL or TYPETERM
(termtype) specified with DEVICE=CONSOLE. definition.
System action: The TERMINAL definition is not installed. Module: DFHTOR
(The TYPETERM definition is installed and may be referred to
by other compatible TERMINAL definitions). XMEOUT Parameters: date, time,applid, termdef, termtype
User response: Correct the TERMINAL or TYPETERM Destination: CSMT
definition.
Module: DFHTOR
DFHTO6009E date time applid The definition for SESSIONs
XMEOUT Parameters: date, time,applid, termdef, termtype sesdef refers to CONNECTION condef which
Destination: CSMT specifies a different PROTOCOL.
DFHTO6005E date time applid PRINTER or ALTPRINTER for INSTALL, or an EXEC CICS CREATE command, CICS
TERMINAL termdef is invalid for the detected a SESSIONS definition (sesdef) that referred to a
DEVICE specified in TYPETERM termtype. CONNECTION definition (condef) that specified a different
Explanation: While installing a GRPLIST during PROTOCOL.
initialization, or while executing a CEDA CHECK, a CEDA System action: The SESSIONS definition is not installed.
INSTALL, or an EXEC CICS CREATE command, CICS User response: Correct the SESSIONS or CONNECTION
detected a TERMINAL definition (termdef) specified with definition.
PRINTER or ALTPRINTER or both, which referred to a Module: DFHTOR
TYPETERM definition (termtype) that did not specify one of
these DEVICEs: 3270, 3275, 3270P, LUTYPE2, or LUTYPE3. XMEOUT Parameters: date, time,applid, sesdef, condef
System action: The TERMINAL definition is not installed. Destination: CSMT
(The TYPETERM definition is installed and may be referenced
DFHTO6010E date time applid The definition for SESSIONs
User response: Correct the TERMINAL or TYPETERM
sesdef must specify PROTOCOL LU61 as it
definition.
refers to an MRO CONNECTION condef.
Module: DFHTOR
XMEOUT Parameters: date, time,applid, termdef, termtype initialization, or while executing a CEDA CHECK, a CEDA
Destination: CSMT INSTALL, or an EXEC CICS CREATE command, CICS
detected a SESSIONS definition (sesdef), specified without
LU61, which referred to a CONNECTION definition (condef)
DFHTO6006E date time applid PRINTERCOPY or that specified ACCESSMETHOD=IRC (MRO).
ALTPRINTCOPY for TERMINAL termdef is System action: The SESSIONS definition is not installed.
invalid for the DEVICE specified in User response: Correct the SESSIONS or CONNECTION
TYPETERM termtype. definition.
Explanation: While installing a GRPLIST during Module: DFHTOR
INSTALL, or an EXEC CICS CREATE command, CICS XMEOUT Parameters: date, time,applid, sesdef, condef
detected incompatible TERMINAL and TYPETERM Destination: CSMT
definitions. The TERMINAL definition termdef specified
PRINTERCOPY or ALTPRINTCOPY or both, but referred to a
DFHTO6011E date time applid SESSIONs sesdef must specify
TYPETERM definition termtype which specified an LUTYPE2
both SENDCOUNT and RECEIVECOUNT as
or LUTYPE3 device.
it refers to an MRO CONNECTION condef.
System action: The TERMINAL definition is not installed.
(The TYPETERM definition is installed and may be referenced
INSTALL, or an EXEC CICS CREATE command, CICS
User response: Correct the TERMINAL or TYPETERM
detected a SESSIONS definition (sesdef), specified with either
definition.
SENDCOUNT=0 or RECEIVECOUNT=0, which referred to a
Module: DFHTOR
CONNECTION definition (condef) that specified
XMEOUT Parameters: date, time,applid, termdef, termtype ACCESSMETHOD=IRC (MRO).
Destination: CSMT System action: The SESSIONS definition is not installed.
User response: Correct the SESSIONS or CONNECTION
definition.
Module: DFHTOR

DFHTO6012 • DFHTO6018E
XMEOUT Parameters: date, time,applid, sesdef, condef

DFHTO6015E date time applid TRANSACTION for
Destination: CSMT
TERMINAL termdef is invalid for the
DEVICE specified in TYPETERM typedef.
DFHTO6012 date time applid The CICS global catalog Explanation: An attempt has been made to install a
dataset is not available. RDO function is TERMINAL definition which specified TRANSACTION, but
restricted. referred to a TYPETERM specifying device APPC.
Explanation: During initialization for a COLD start, CICS System action: CICS initialization continues, but TERMINAL
could not find the global catalog data set (DFHGCD). termdef is not installed.
System action: CICS continues, but with the following User response: Correct the TERMINAL definition, or the
restrictions to RDO function: TYPETERM definition.
v A TYPETERM definition must be in the same group as the Module: DFHTOR
TERMINAL definitions that refer to it.
v AUTOINSTALL is not available, because the MODEL XMEOUT Parameters: date, time,applid, termdef, typedef
definitions cannot be stored. Destination: CSMT
User response: If you wish to avoid the above restrictions to
RDO function in future CICS runs, create a global catalog data
DFHTO6016E date time applid The MRO CONNECTION
set and make it available to CICS in the DFHGCD DLBL
condef is referenced by more than one
statement of the CICS startup job stream.
SESSIONs definition, including sesdef.
Module: DFHTORP
Explanation: When installing a GRPLIST during
XMEOUT Parameters: date, time,applid initialization, or while executing a CEDA CHECK, a CEDA
Destination: CSMT INSTALL, or an EXEC CICS CREATE command, CICS has
detected a CONNECTION definition condef that specified
ACCESSMETHOD=IRC, which implies that it is an MRO
DFHTO6013E date time applid No SESSIONs definition connection. This CONNECTION was then referenced by more
refers to CONNECTION condef. than one SESSIONS definition, one of which was sesdef. An
Explanation: During installation of a GRPLIST at MRO connection must only have one SESSIONS definition
initialization time, during CEDA INSTALL of a GROUP, or referencing it. Other SESSION definition names that reference
during the CEDA CHECK command, or an EXEC CICS this CONNECTION are listed in further occurrences of this
CREATE command, a CONNECTION definition was detected message.
that had no valid SESSIONS definitions. This is valid only for System action: The CONNECTION definition is not installed.
INDIRECT or REMOTE connections. User response: Correct the CONNECTION definition or the
System action: The CONNECTION is not installed. SESSIONS definitions.
If the reason for the failure is one or more invalid SESSIONS Module: DFHTOR
definitions, CICS issues another message which identifies the XMEOUT Parameters: date, time,applid, condef, sesdef
incorrect definition(s). If the reason was a missing SESSIONS Destination: CSMT
definition, this is the only message.
User response: Correct the CONNECTION definition, create
a SESSIONS definition, or correct existing SESSIONS DFHTO6017E date time applid REMOTESYSTEM for
definition(s), as appropriate. TERMINAL 'termid' is invalid for the
Module: DFHTOR DEVICE specified in TYPETERM 'typeterm'.
Explanation: When installing a GRPLIST during
XMEOUT Parameters: date, time,applid, condef initialization, or while executing a CEDA CHECK, a CEDA
Destination: CSMT INSTALL, or an EXEC CICS CREATE command, CICS
detected a CONSOLE that was defined as remote. This is an
DFHTO6014E date time applid POOL is required for invalid option.
TERMINAL termdef as it refers to TYPETERM System action: The CONSOLE is not installed.
typedef which specifies User response: Correct the CONSOLE that is defined as
SESSIONTYPE=PIPELINE. remote.
Explanation: An attempt has been made to install a terminal Module: DFHTOR
whose TYPETERM specified SESSIONTYPE=PIPELINE, but XMEOUT Parameters: date, time,applid, termid, typeterm
whose terminal definition did not specify POOL. Destination: CSMT
System action: CICS initialization continues, but TERMINAL
termdef is not installed.
User response: Correct the TERMINAL definition, or the DFHTO6018E date time applid TERMINAL 'termid' refers to
TYPETERM definition. TYPETERM 'typeterm' which has an invalid
Module: DFHTOR ALTSCREEN.
Explanation: A TYPETERM definition includes an invalid
XMEOUT Parameters: date, time,applid, termdef, typedef ALTSCREEN. ALTSCREEN has two components; width and
Destination: CSMT height. One of these components is zero while the other is
nonzero. This is an invalid combination. CICS has detected
this problem in a TERMINAL definition while installing a
GRPLIST during initialization, or while executing a CEDA
CHECK, a CEDA INSTALL, or an EXEC CICS CREATE
command.
System action: The TERMINAL definition is not installed.
User response: Correct the TYPETERM that is referenced or

DFHTO6019E • DFHTP4105
reference a different TYPETERM in the TERMINAL definition. CONNECTION definition condef because condef is defined as
See the CICS Resource Definition Guide for details of valid single-session. This was detected when sesdef referred to condef
ALTSCREEN values. during installation of a GRPLIST at initialization, during
Module: DFHTOR CEDA INSTALL of a GROUP, or following a CHECK
command, or during an EXEC CICS CREATE.
XMEOUT Parameters: date, time,applid, termid, typeterm
Destination: CSMT When a SESSION definition refers to a single-session
CONNECTION definition, the value of the MAXIMUM option
should be (1,0).
DFHTO6019E date time applid User userid is not authorized to System action: The SESSIONS definition is not installed.
install TERMINAL tttt with preset security. User response: There are two ways to solve this problem:
Explanation: User userid was attempting to install v Correct the SESSIONS definition by specifying
TERMINAL tttt but the userid does not have sufficient MAXIMUM(1,0) using either CEDA or the CSD batch
authority. This is because the TERMINAL has preset security update utility DFHCSDUP.
(the definition for TERMINAL tttt specifies a USERID value). v Redefine the CONNECTION definition so that it is no
Installing a resource with preset security requires special longer single-session by specifying SINGLESESS=NO.
authorization. Module: DFHTOR
System action: Resource security violation messages are
logged to the CSCS transient data queue and to the system XMEOUT Parameters: date, time,applid, sesdef, condef
console. The resource is not installed. CICS continues. Destination: CSMT
User response: In order to install this resource, do one of the
following:
DFHTO6025E date time applid The definition for LU6.1
v Use the CESN transaction to sign on with a userid that is
SESSIONs sesdef specifies a send or receive
permitted to install TERMINALs with preset security.
count with no prefix.
v Ask your security administrator to authorize user userid to
install terminals with preset security.
v Remove the USERID specification from the resource
INSTALL, or an EXEC CICS CREATE command, CICS
definition and install the resource without preset security.
detected an LU6.1 SESSIONS definition (sesdef) that specified a
Module: DFHTOATM
send count with no send prefix or a receive count with no
XMEOUT Parameters: date, time,applid, userid, tttt receive prefix. Prefixes must be specified for LU6.1.
Destination: CSMT System action: The SESSIONS definition is not installed.
User response: Correct the definition referred to in the
message.
DFHTO6020E date time applid SESSIONS sesdef refers to Module: DFHTOR
single-session CONNECTION condef but has
an invalid MAXIMUM option specified. XMEOUT Parameters: date, time,applid, sesdef
Explanation: The value specified for the MAXIMUM option Destination: CSMT
in the SESSIONS definition sesdef is incompatible with the
DFHTPxxxx messages
DFHTP4101 Cannot reset from temporary paging to DFHTP4103 Attempting to PURGE, COPY or CHAIN, but
autopaging. no pages are currently connected to this
Explanation: A terminal requested that it be reset from terminal.
temporary paging status to autopaging status. However, the Explanation: There are currently no tasks attached to this
terminal is defined as a paging terminal, or the message is terminal.
marked to state that the operator must purge it. System action: Other processing continues.
System action: Other processing continues. User response: None.
User response: If the terminal is defined as a purging Module: DFHTPR
terminal, use the master terminal program to change the status Destination: Terminal End User
of the terminal.
If the message is so marked, the operator must purge the DFHTP4104 A paging request was received but there are
message. The system then automatically resets the status to no pages for display.
autopaging. Explanation: The CICS paging command (CSPG) or a request
Module: DFHTPR for paging was entered from a terminal in transaction status,
Destination: Terminal End User but there are no pages to be displayed at the terminal.
DFHTP4102 nnnn messages are queued for immediate Module: DFHTPR
delivery. Destination: Terminal End User
Explanation: The operator requested the nnnn messages to be
delivered via the page retrieve command queue.
System action: The count of messages queued for this DFHTP4105 The specified message is not recognized.
operator or terminal is displayed. Explanation: The terminal operator tried to retrieve or purge
User response: None. a specific message using a message identifier (rather than the
Module: DFHTPR current or next available message). However, the specified
Destination: Terminal End User message does not exist, or is not destined for this terminal.

DFHTP4106 • DFHTP4113
User response: None. N The next page.

Module: DFHTPR P The previous page.
Destination: Terminal End User Q (Query) display the identifier of all logical messages
destined for this terminal. If the message is security
protected, its identifier is displayed only if the
DFHTP4106 You are not allowed to RETRIEVE or PURGE
operator identifier and class for the signed-on
this message.
operator match those in the message. The identifier
Explanation: The terminal operator tried to retrieve or purge
consists of 1-to-6-digit hexadecimal number, and
a specific message using a message identifier (rather than the
current or next available message). However, the specified optionally, a message title.
message is not destined for this operator identifier. System action: Other processing continues.
System action: Other processing continues. User response: Use a valid page retrieve function.
User response: None. Module: DFHTPR
Module: DFHTPR Destination: Terminal End User
DFHTP4111 function is not valid. Page PURGE function
DFHTP4107 Chain value chain is less than 1 or greater must be A, B, C, H, or R.
than the level of chaining allowed. Explanation: The page purge function represented by function
Explanation: The chain value, chain, as indicated by the page is not A, B, C, H, or R. The functions have the following
retrieval command, is either less than one or is greater than meanings.
the level of chaining at that terminal.
System action: Other processing continues. Function Meaning
User response: None. A All logical messages destined for and being
Module: DFHTPR displayed on that terminal.
Destination: Terminal End User B The logical message being displayed on that
terminal and all logical messages chained to it.
C The current (level) logical message.
DFHTP4108 Requested page pageno does not exist (it is H All logical messages chained to the base logical
less than 1 or more than the number of pages message being displayed on that terminal.
in the message). R All logical messages queued for immediate delivery
Explanation: The page pageno, as indicated by the page (routed) to the terminal.
retrieval command, is either less than one or is greater than System action: Other processing continues.
the number of pages in the message. This can be caused, for
User response: Use a valid page purge function.
example, by requesting the previous page after the first page,
Module: DFHTPR
or the next page after the last page.
User response: The paging session can be continued with a
valid page value. The last valid page displayed is still the DFHTP4112 The terminal identifier termid is unknown or
current page. For example, to recall the last valid page is not supported.
displayed, execute the page retrieval command used to get a Explanation: The terminal identifier represented by termid
current page.
does not exist or is not supported under basic mapping
Module: DFHTPR
support (BMS).
User response: Use a valid terminal identifier.
DFHTP4109 The requested command command was not Module: DFHTPR
recognized. Check that you have the correct Destination: Terminal End User
value.
Explanation: Transaction CSPG was entered at the terminal,
but what follows cannot be identified as a paging command. DFHTP4113 date time applid msgno termtype pageno I/O error
command represents the first four nonblank characters after on MCR or Page (MODULE NAME:
CSPG. modname).
System action: Other processing continues. Explanation: While attempting to retrieve a message control
User response: None. record (MCR) or page of a message, a temporary storage I/O
Module: DFHTPR error occurred. msgno represents the message number in
Destination: Terminal End User hexadecimal; termtype is the terminal type; pageno is zero if the
error occurred for the MCR, or is the page number. The
message or page noted may be lost for this and/or other
DFHTP4110 function is not valid. Page RETRIEVE terminals.
function must be A, C, L, N, P, Q, or a
System action: If pages are being displayed at an autopaging
number.
terminal, the next page if any is displayed. Otherwise no
Explanation: The page retrieve function represented by
action takes place.
function is not one of the following: A, C, L, N, P, Q, or a
number that may be preceded by a + (plus) or a – (minus)
sign, where: Module: DFHTPQ
Function Meaning XMEOUT Parameters: date, time,applid, msgno, termtype, pageno,

A All logical messages destined for and being modname
displayed on that terminal. Destination: CSMT
C The current (level) logical message.
L The last page.

The insert bmsid is the BMS logical message identifier, which is

DFHTP4114 You must purge messages from the terminal
a unique hexadecimal identifier used in the generation of a TS
before issuing a new transaction.
key for saving this page or message. The insert termtype
Explanation: While messages were being displayed at the
identifies the terminal type.
terminal, the operator entered data that was not a paging
System action: The message or page may be lost. Other
command, either in error or to initiate a new transaction.
processing continues.
However, at least one of the messages on the terminal is
marked that the operator must specifically purge it before
Module: DFHTPR
initiating a new transaction.
User response: Purge all messages being displayed at this
terminal (T/A), or chain the desired transaction using the DFHTP4119 An invalid request on Message Control
chaining command. Record (MCR) or Page Retrieval has occurred.
Module: DFHTPR Message bmsid, terminal type termtype, page
Destination: Terminal End User pageno.
Explanation: CICS was trying to store or retrieve page pageno
of a message when a temporary storage invalid request
DFHTP4115 You must purge the message from your
occurred. Alternatively, CICS could have been trying to store
terminal to continue.
or retrieve a message control record (MCR) if the page pageno
Explanation: A transaction is displaying pages at the
equaled zero when the temporary storage invalid error was
terminal. Before the operator can continue with the
received.
transaction, the message must be purged.
System action: Other processing continues. The message or page may be lost. The probable cause is that
User response: Purge the current message (T/C). temporary storage was not loaded. bmsid is the BMS logical
Module: DFHTPR message identifier, which is a unique hexadecimal identifier
Destination: Terminal End User used in the generation of a TS key for saving this page or
message. termtype is the terminal type.
DFHTP4116 Your message request cannot be done while
User response: Ensure that the temporary storage program is
another message is being displayed.
loaded.
Explanation: While viewing a message, the operator entered
Module: DFHTPR
a request for a specific message (for example, P/1,xxx) or
requested the message identifiers of messages waiting to be
displayed (P/Q). CICS cannot service this request while
another message is being displayed. xxx is the message DFHTP4120 Unable to interpret input. Please try again.
identifier of one of the messages waiting to be displayed. Explanation: The operator entered data that could not be
System action: Other processing continues. interpreted.
User response: If desired, reenter the request when there are System action: Input is discarded.
no messages being displayed at the terminal. User response: Verify that input is valid under existing
Module: DFHTPR conditions.
Destination: Terminal End User Module: DFHTPR
DFHTP4117 Purge display % after viewing.
Explanation: The operator at a 3270 has requested a display DFHTP4121 An I/O error occurred while retrieving a
of message identifiers waiting to be displayed. The reply is message control record or message page.
constructed as one or more pages stored in temporary storage Message bmsid, terminal type termtype, page
and can be viewed like any page message. % is the page pageno.
number indicator. Explanation: CICS was trying to retrieve page pageno of a
System action: Other processing continues. message when a temporary storage I/O error occurred.
User response: Purge the message when viewing is complete. Alternatively, CICS could have been trying to store or retrieve
Module: DFHTPR a message control record (MCR) if the page pageno equaled
Destination: Terminal End User zero when the temporary storage I/O error occurred.
The message or page may be lost. bmsid is the BMS logical
DFHTP4118 An ID error occurred while retrieving a message identifier, which is a unique hexadecimal identifier
Message Control Record (MCR) or Message used in the generation of a TS key for saving this page or
Page. Message bmsid, terminal type termtype, message. termtype is the terminal type.
page pageno. System action: If pages are being displayed at an autopaging
Explanation: CICS was trying to retrieve page pageno of a terminal, the next page, if any, is displayed. Otherwise no
message from temporary storage when an identifier error was action takes place.
received. User response: None.
Module: DFHTPR
Alternatively, if page pageno is equal to zero, CICS could have
been trying to retrieve a message control record (MCR) when
the identifier error was received. The probable cause of the
error is that temporary storage was cold started after the
message was scheduled or after the message was saved.
Otherwise the message had already been purged.

DFHTP4122 Requested purge completed successfully. DFHTP4130 You have used an unrecognized logical
Explanation: CICS has completed a page purge function device. The valid names are xxx,yyy.
requested from the terminal. Explanation: A paging command containing an invalid
System action: Processing continues. logical device mnemonic was entered. xxx,yyy,... indicates the
User response: None. valid logical device mnemonics for the requested logical
Module: DFHTPR message.
Destination: Terminal End User System action: Input is discarded and other processing
continues.
User response: Reenter the paging command with a logical
DFHTP4123 Terminal is now Autopaging. device mnemonic chosen from those listed in the message.
Explanation: The terminal operator has requested that CICS Module: DFHTPR
reset a terminal that is temporarily in paging status, to Destination: Terminal End User
autopaging status.
System action: The rest of the pages in the message are
displayed. If there are none left and the message can be DFHTP4131 Requested page cannot be copied to that
purged automatically, it is purged. terminal.
User response: None. Explanation: The operator has tried to copy a page that
Module: DFHTPR refers to an outboard format:
Destination: Terminal End User v To a terminal that does not support outboard formats, or
v To a terminal that does support outboard formats, but
which has a different page width or a smaller page depth
DFHTP4124 Page copied from terminal termid (Message than the source terminal.
number msgno). System action: The paging request is ignored.
Explanation: This message appears in the display of User response: Carry out whichever one of the following is
messages waiting to be displayed (P/Q) and identifies a appropriate:
copied page. msgno is the message number of the copied page v Copy the offending page to a terminal that supports
and termid is the terminal for which it is queued. outboard formatting
System action: Processing continues. v Make the referenced format nonoutboard
User response: None. v Copy the offending page to a terminal that does support
Module: DFHTPR outboard formatting and which has a page size the same as
Destination: Terminal End User that of the source terminal.
Module: DFHTPR
DFHTP4126 msgno has been copied. Destination: Terminal End User
Explanation: This message is issued in response to a request
to copy to another terminal. msgno is the message number of DFHTP4132 No pages have been built for this partition.
the message being displayed. Explanation: This an information message issued during a
System action: Processing continues. page retrieval session. It appears in a screen partition for
User response: None. which no pages have been built.
Module: DFHTPR System action: Processing continues.
Destination: Terminal End User User response: None, unless a display was expected in the
affected partition. In this case, check for an operator or
DFHTP4127 nnnn must be a number. Please try again. application error.
Explanation: The characters nnnn are not valid. The system Module: DFHTPR
expected a decimal value for a page or chain number, or a Destination: Terminal End User
hexadecimal value for a message number.
System action: Other processing continues. DFHTP4133 date time applid bmsid termtype pageno ID error
User response: Reenter the paging command. Use a valid on MCR or page.
number. Explanation: CICS was trying to retrieve page pageno of a
Module: DFHTPR message when an identifier error was received. Alternatively,
Destination: Terminal End User CICS could have been trying retrieve a message control record
(MCR) if the page pageno equaled zero when the identifier
DFHTP4128 command is undefined for page retrieval. error was received. The message or page may be lost.
Explanation: After a page retrieval (PR) session had been The probable cause is that temporary storage was cold started
started, the operator pressed a PA or PF key for which no PR after the message was scheduled or saved, or the message has
command had been defined in the SIT. already been purged.
System action: The command is ignored. The display status
bit is not altered. bmsid is the BMS logical message identifier, which is a unique
User response: Ensure that the PR command in question is hexadecimal identifier used in the generation of a TS key for
defined in the SIT. saving this page/message. termtype is the terminal type.
Module: DFHTPR System action: Other processing continues.
Destination: Terminal End User User response: None.
Module: DFHTPQ
XMEOUT Parameters: date, time,applid, bmsid, termtype, pageno
Destination: CSMT

messages waiting longer than a time specified by the

DFHTP4134 date time applid bmsid termtype pageno Invalid
installation are purged.
request on MCR or page.
Explanation: CICS was trying to store or retrieve page pageno
Module: DFHTPQ
of a message when a temporary storage invalid request error
occurred. Alternatively, CICS could have been trying to store XMEOUT Parameters: date, time,applid, msgno, nnnn
or retrieve a message control record (MCR) if the page pageno Destination: CSMT
equaled zero when the temporary storage invalid request error
occurred. The message or page may be lost.
DFHTP4161 Message msgno was not delivered. It was
The probable cause is that temporary storage was not loaded. purged from terminal(s) termid. Message title
was title.
bmsid is the BMS logical message identifier, which is a unique
Explanation: The message numbered msgno has been purged
hexadecimal identifier used in the generation of a TS key for
because it was not delivered within the system-defined time
saving this page/message. termtype is the terminal type.
limit.
User response: Ensure that the temporary storage program is title is the title of message msgno and appears in this message
loaded. only if one exists. termid is the terminal from which the
Module: DFHTPQ message was purged.
System action: The message is purged from the system. No
XMEOUT Parameters: date, time,applid, bmsid, termtype, pageno
further attempt is made to deliver the message.
Destination: CSMT
Module: DFHTPQ
DFHTP4150 date time applid ID error on MCR. Destination: Terminal End User
Explanation: During processing of a delayed delivery
message a temporary storage identification error occurred. The
DFHTP4162 date time applid nnnn BMS system messages
message is lost for all destination terminals. Temporary
purged as undeliverable from error
storage was probably cold started after the message was
notification terminal.
originally scheduled.
Explanation: Basic mapping support (BMS) system messages
(for example, DFHTP4161) have been waiting to be displayed
at the error notification terminal, but the terminal is unable to
Module: DFHTPS
display them because its status is not consistent with their
XMEOUT Parameters: date, time,applid status, or because traffic is too heavy.
Destination: CSMT
nnnn is the number of BMS system messages purged and
termid is the error notification terminal's identifier.
DFHTP4151 date time applid I/O error on MCR. System action: To avoid affecting system performance,
Explanation: During processing of a delayed delivery messages waiting longer than a time specified by the
message a temporary storage I/O error occurred. The message installation, are purged.
is lost for all destination terminals. User response: Either alter the status of the terminal to allow
System action: Other processing continues. messages to be displayed or increase purge delay time at CICS
User response: None. system initialization.
Module: DFHTPS Module: DFHTPQ
XMEOUT Parameters: date, time,applid XMEOUT Parameters: date, time,applid, nnnn

DFHTP4152 date time applid Invalid request on MCR. DFHTP4164 date time applid termid cannot accept message
Explanation: During processing of a delayed delivery DFHTP4161. It is undefined or does not
message, a temporary storage invalid request error occurred. support paging.
The message is lost for all destination terminals. The system Explanation: termid is the identifier of a terminal specified to
was probably initialized without temporary storage. receive notification if a message could not be delivered.
System action: Other processing continues. However, termid is not now in the TCT or is not defined as a
User response: Ensure that the system is initialized with terminal supported by BMS. This message is followed by
temporary storage. DFHTP4161, which contains the error notification.
Module: DFHTPS System action: Other processing continues.
User response: Notify terminal termid of the contents of
XMEOUT Parameters: date, time,applid message DFHTP4161, which is issued following this message.
Destination: CSMT Module: DFHTPQ
XMEOUT Parameters: date, time,applid, termid
DFHTP4160 date time applid Message msgno purged as Destination: CSMT
undeliverable from nnnn terminal(s).
Explanation: The message numbered msgno has been waiting
for display at a terminal, but nnnn of these terminals are
unable to display the message because they are out of service.
This message is sent to the master terminal operator.
System action: To avoid affecting system performance,

DFHTP4165 Undeliverable messages are being purged. DFHTP4172 date time applid Request from system sysid to
The terminal is available for use. route message number msgno to terminal
Explanation: This message is sent to destination CSMT. It is termid was not executed. Terminal not
also sent to the originating terminal if transaction CSPQ is supported by BMS.
entered from the terminal. Program DFHTPQ has been Explanation: BMS received a request from system sysid to
time-initiated to purge any messages that are considered route message msgno to terminal termid. The request could not
undeliverable. be executed because terminal termid is of a type not supported
System action: A non-terminal task is initiated to purge by BMS.
undeliverable messages. System action: Processing continues.
User response: None. The message is displayed at the User response: Ensure that the TCTs for the two systems are
terminal to indicate that the terminal is available for use. consistent.
Module: DFHTPQ Module: DFHTPS
XMEOUT Parameters: date, time,applid, sysid, msgno, termid
Destination: CSMT
DFHTP4166 date time applid BMS has received an error
return code retcode from CICS macro {TS
DFHTP4173 date time applid Request from system sysid to
PURGE | BMS TEXTBLD | BMS PAGEOUT |
route message number msgno to terminal
TS PUT}.
termid was not executed. Invalid LDC
Explanation: BMS received an error return code after issuing
specified.
a CICS system macro request. retcode is the return code and
Explanation: BMS has received a request from system sysid to
macro is the macro request.
route message msgno to terminal termid. The request could not
System action: Message DFHME0116 is normally produced
be executed because the LDC specification was invalid.
User response: Ensure that the TCTs for the two systems are
consistent.
Module: DFHTPS
Module: DFHTPQ
XMEOUT Parameters: date, time,applid, sysid, msgno, termid
XMEOUT Parameters: date, time,applid, retcode, {1=TS
Destination: CSMT
PURGE,2=BMS TEXTBLD, 3=BMS PAGEOUT, 4=TS PUT}
Destination: CSMT
DFHTP4174 date time applid Message routing has failed for
DFHTP4170 date time applid Request from system sysid to terminal termid. The termid was invalid or
route message number msgno to terminal could not be located.
termid was not executed. Explanation: BMS has received a request from system sysid to
Explanation: BMS received a request from system sysid to route message msgno to terminal termid. The request could not
route message msgno to terminal termid. The request could not be executed because termid is invalid or could not be located.
be executed. System action: Processing continues.
System action: Processing continues. User response: Ensure that the TCTs for the two systems are
User response: Ensure that the TCTs for the two systems are consistent.
consistent. Module: DFHTPS
Module: DFHTPS XMEOUT Parameters: date, time,applid, termid
XMEOUT Parameters: date, time,applid, sysid, msgno, termid Destination: CSMT
Destination: CSMT
DFHTP4180 date time applid Terminal termid specified as
DFHTP4171 date time applid Request from system sysid to error terminal for message msgno from system
route message number msgno to terminal sysid invalid and ignored.
termid was not executed. Terminal not valid. Explanation: BMS has received a request from system sysid to
Explanation: BMS received a request from system sysid to route message msgno, specifying terminal termid to be notified
route message msgno to terminal termid. The request could not in the event of the message not being delivered. Terminal
be executed because terminal termid is not defined on this termid is not defined in the terminal control table.
system. System action: Processing continues.
System action: Processing continues. User response: Ensure that the TCTs for the two systems are
User response: Ensure that the TCTs for the two systems are consistent.
consistent. Module: DFHTPS
Module: DFHTPS XMEOUT Parameters: date, time,applid, termid, msgno, sysid
XMEOUT Parameters: date, time,applid, sysid, msgno, termid Destination: CSMT
Destination: CSMT
DFHTP4190 Please enter your data again in the partition
containing the cursor.
Explanation: The terminal operator entered data from a
partition other than the expected input partition. The expected
input partition is activated (that is, the cursor is moved into

DFHTR0001 • DFHTR0004
it), and the terminal operator should reenter data in this Module: DFHPHP
partition. Destination: Terminal End User
User response: Ensure that the terminal operator enters data
in the correct partition.
DFHTRxxxx messages
DFHTR0001 applid An abend (code abcode) has occurred at
Alternatively, unexpected data has been input, or storage has
been overwritten.
User response: There may be an error in CICS code. The
The code abcode is a 3-digit hexadecimal VSE code (if severity of its impact depends on the importance of the
applicable), followed by a 4-digit alphanumeric CICS code. function being executed at the time of the error.
hyphens. The CICS code is an abend code or a number If the message occurs once and module modname is not crucial
referring to a CICS message (for example, AKEA is a CICS to the running of your CICS system, you may decide to
abend code; 1310 refers to message DFHTS1310). continue to run and bring CICS down at a convenient time to
System action: An exception entry is made in the trace table. resolve the problem.
suppressed dumps in the dump table. If the message recurs or if you cannot run without the full use
CICS continues unless you have specified in the dump table controlled shutdown.
Message DFHME0116 is normally produced containing the See Part 4 of the CICS Problem Determination Guide for
symptom string for this problem. guidance on how to proceed.
User response: If CICS is still running, it is necessary to Module: DFHTRSR
Look up the VSE code, if there is one, in section Destination: Console
DFHTR0004 applid A possible loop has been detected at
Next, look up the CICS alphanumeric code in “Transaction offset X'offset' in module modname.
Abend Codes (CICS Transaction Server for VSE/ESA)” on Explanation: A CICS function is taking more time to process
page 453. This tells you, for example, whether the error was a than CICS expects. A possible loop has been detected in
program check, an abend, or a runaway, and may give you module modname at offset X'offset'. This is the offset of the
some guidance concerning user response. instruction which was executing at the time the error was
If module modname is not crucial to the running of your CICS detected.
system, you may decide to continue to run and bring CICS System action: An exception entry is made in the trace table.
down at a convenient time to resolve the problem. A system dump is taken, unless you have specifically
should bring CICS down in a controlled shutdown. CICS continues unless you have specified in the dump table
See Part 4 of the CICS Problem Determination Guide for Message DFHME0116 is normally produced containing the
guidance on how to proceed. symptom string for this problem.
Module: DFHTRSR, DFHTRPT, DFHTRDM, DFHTRFT User response: If CICS has not been terminated, it is
XMEOUT Parameters: applid, abcode,X'offset', modname bring CICS down.
DFHTR0002 applid A severe error (code X'code') has there may not be an error here. Usually, CICS purges a CICS
occurred in module modname. function which exceeds the runaway task time interval which
Explanation: An error has been detected in module modname. you have specified on the ICVR system initialization
The code X'code' is the exception trace point id which uniquely parameter (ICVR is measured in milliseconds). This means
identifies what the error is and where the error was detected. that module modname is terminated and CICS continues.
For further information about CICS exception trace entries,
System action: An exception entry (code X'code') is made in
the trace table. A system dump is taken, unless you have
specifically suppressed dumps in the dump table. If CICS has terminated module modname and you consider

interval. You have to bring CICS down at a suitable time to do TR0104 is taken. CICS then continues with auxiliary trace
this permanently. But you can change the ICVR time interval inactive.
temporarily online, using the CEMT transaction. User response: Determine why so little storage is available
and retry if possible.
Module: DFHTRDM
Problem Determination Guide for guidance on how to proceed. XMEOUT Parameter: applid
Module: DFHTRSR, DFHTRPT, DFHTRDM, DFHTRFT Destination: Console
Destination: Console DFHTR0105 AUXILIARY TRACE DATA SET dataset
COULD NOT BE OPENED - AUXILIARY
DFHTR0101 STORAGE FOR INTERNAL TRACE TABLE TRACE INOPERATIVE.
NOT AVAILABLE -TRACE INOPERATIVE. Explanation: An attempt to start auxiliary trace or to switch
Explanation: During CICS initialization, there was auxiliary trace extents has failed because the request to SAM
insufficient storage for even the minimum allowable internal to open data set dataset failed.
trace table size (16KB). System action: There are two cases:
System action: CICS terminates with a system dump. v If the error occurs after an explicit request to start auxiliary
User response: The failure to get even 16KB from VSE at this trace (as opposed to switching extents), a CICS system
early stage of initialization almost certainly means that other dump with dump code TR0105 is taken. CICS then
areas of CICS and other system functions will not be able to continues with auxiliary trace inactive.
acquire the storage they require to operate, so the system is v If the error occurs when auxiliary trace is already active,
unlikely to initialize completely. A possible solution is to that is, an explicit switch request when auxiliary trace starts
increase the size of the CICS partition. or an end-of-extent with autoswitching active, an SDUMP
Module: DFHTRDM with dump code KERNDUMP is taken. This type of dump
Destination: Console is not subject to suppression or modification by use of the
dump table.
User response: Check that the DLBL statement for data set
DFHTR0102 REQUESTED TRACE TABLE SIZE NOT dataset is present.
AVAILABLE.
Explanation: CICS issues a variable-type VSE GETMAIN for If it is, format the system dump and examine the TR domain
the internal trace table storage. This message indicates that the information. The DCB for the auxiliary trace data set should
upper limit specified (on the TRTABSZ keyword) was not be present. Use this to determine the reason for the open
available, but that at least the lower limit of 16K was obtained. failure.
Message DFHTR0103 which follows this message gives the Module: DFHTRSR, DFHTRSU
actual size acquired. Destination: Console
System action: CICS continues with an internal trace table of
the size given by message DFHTR0103.
DFHTR0106 applid DFHTRAO could not be loaded.
User response: There are three possible courses of action:
Auxiliary trace is inoperative.
v Allow CICS to run with the decreased table size if this is
Explanation: An attempt to start auxiliary trace failed
thought to be adequate. because the CICS module, DFHTRAO, which is used to write
v Terminate the system and reinitialize after increasing the to the auxiliary trace data set, could not be loaded.
region size available to CICS. System action: The loader domain (LD) will have issued
v Once the system is initialized, use CETR to increase the messages and dumps as necessary. CICS continues with
table size to the required value. auxiliary trace inactive.
Module: DFHTRDM User response: Refer to the associated loader domain
Destination: Console messages for further information and guidance.
Module: DFHTRSR
DFHTR0103 TRACE TABLE SIZE IS nnK. XMEOUT Parameter: applid

Explanation: The internal trace table acquired during CICS Destination: Console
initialization has a table size nnKB.
This is either the same as that specified on the TRTABSZ DFHTR0107 ABEND X'abcode' ON AUXILIARY TRACE
keyword of the SIT or message DFHTR0101 or DFHTR0102 DATA SET dataset - AUXILIARY TRACE
has preceded this on the console. STOPPED.
System action: CICS continues. Explanation: An error has been detected whilst performing a
User response: None. sequential i/o operation on the auxiliary trace data set dataset.
Module: DFHTRDM The 3-digit abend code is indicated as X'abcode'
Destination: Console System action: CICS continues with auxiliary trace inactive.
User response: Refer to the "OS/390 API Abend Codes" in
section "VSE/Advanced Functions Codes & SVC Errors" of
DFHTR0104 applid No buffer storage available for
z/VSE Messages and Codes - Volume 1 manual for an
auxiliary trace data set. Auxiliary trace is
explanation of the abend code, X'abcode'.
inoperative. Module: DFHTRAO
Explanation: An attempt to start auxiliary trace failed Destination: Console
because there was insufficient storage available for the 4KB
output buffer.
System action: A CICS system dump with dump code

DFHTR0108 I/O ERROR ON AUXILIARY TRACE DATA DFHTR0113 applid Auxiliary trace is being started on data
SET dataset - AUXILIARY TRACE STOPPED. set dataset.
Explanation: An error has been detected whilst performing Explanation: A request to start auxiliary trace has been
an sequential I/O operation to the auxiliary trace data set successfully processed. The trace records are being written to
dataset. data set dataset.
System action: CICS will continue with auxiliary trace System action: CICS continues with auxiliary trace active.
inactive. User response: None.
User response: Use any accompanying VSE messages to Module: DFHTRSR
determine the cause of the error.
Module: DFHTRAO XMEOUT Parameters: applid, dataset
DFHTR0109 AUXILIARY TRACE DATA SET dataset FULL DFHTR0114 AN ABEND HAS OCCURRED DURING
-AUXILIARY TRACE HAS BEEN STOPPED. INITIALIZATION OF TRACE IN MODULE
Explanation: The auxiliary trace data set dataset is full. modname.
Auxiliary trace has been stopped because autoswitch is not Explanation: Module modname's recovery routine received
active. control during pre-initialization of the trace (TR) domain. This
System action: CICS continues with auxiliary trace inactive. indicates that a program check has occurred in module
User response: The auxiliary trace data set dataset can now modname.
be processed by the print routine DFHTU410. There are three possible causes of this condition.
Module: DFHTRSU v The module has been overwritten in main storage.
Destination: Console v The module is at an incompatible level with the rest of the
CICS modules.
DFHTR0110 AUXILIARY TRACE DATA SET dataset1 v There is an error in the module.
FULL - SWITCHING TO dataset2. System action: A system dump with dump code
Explanation: The auxiliary trace data set dataset1 is full. KERNDUMP is taken.
Auxiliary trace is continuing on data set dataset2 because User response: Inform the system programmer.
autoswitching was requested.
There may be an error in CICS code. The severity of its impact
System action: CICS continues with auxiliary trace active on
the data set dataset2.
User response: Process the full data set if required.
Module: DFHTRSU CICS may not have been terminated.
DFHTR0112 applid Bad data passed for tracing to module continue to run and bring CICS down at a convenient time to
modname. resolve the problem.
Explanation: Some data passed to the trace (TR) domain for
addition to the internal trace table or auxiliary trace data set If the message recurs or if you cannot run without the full use
caused a program check when an attempt was made to access of module modname you should bring CICS down in a
it. controlled shutdown.
This could either be as a result of a request made by CICS Use the dump to determine the cause of the condition.
system code or a request made by a user program through the Module: DFHTRDM , DFHTRSR
API or XPI. Destination: Console
System action: A system dump with dump code TR0112 is
taken.
DFHTR0115 AN ABEND HAS OCCURRED IN THE
If the message was issued by DFHTRPT the dump contains an AUXILIARY TRACE MODULE DFHTRAO.
exception trace entry (point ID TR0102) that includes the Explanation: Module DFHTRAO's recovery routine has
erroneous parameter list passed to DFHTRPT. received control.
If the message was issued by DFHTRFT the dump contains an This indicates a program check or VSW abend has occurred in
exception trace entry (point ID TR0402) that includes the DFHTRAO.
erroneous parameter list passed to DFHTRFT.
There are three possible causes of this condition:
Message DFHME0116 is normally produced containing the v DFHTRAO has been overwritten in main storage
symptom string for this problem. v DFHTRAO is at an incompatible level with the rest of the
User response: Examine the interpreted exception trace entry CICS modules
to determine the domain that issued the call and the ID of the v There is an error in DFHTRAO.
entry. Then look at the specified addresses and lengths in the
System action: A system dump with dump code
datan fields to see if they contain reasonable values. The fault
KERNDUMP is taken.
is in the module that set up these fields for the trace call.
User response: There may be an error in CICS code. The
Module: DFHTRPT, DFHTRFT
severity of its impact depends on the importance of the
XMEOUT Parameters: applid, modname function being executed at the time of the error.
If the message occurs once and module DFHTRAO is not

crucial to the running of your CICS system, you may decide to

continue to run and bring CICS down at a convenient time to Module: DFHTRSR
XMEOUT Parameters: applid, dataset1, dataset2
If the message recurs or if you cannot run without the full use Destination: Console
of module DFHTRAO, you should bring CICS down in a
DFHTR1000 applid CICS abend requested by global trap
Use the dump to determine the cause of the condition. exit DFHTRAP in module modname.
Module: DFHTRAO Explanation: The field engineering global trap exit program
Destination: Console (DFHTRAP) requested termination of CICS.
System action: CICS disables the trap exit so that it will not
be reentered, and terminates CICS.
DFHTR0116 AN ABEND HAS OCCURRED IN THE User response: Determine why DFHTRAP has requested
TRACE SUBROUTINES MODULE system termination and act accordingly. You should use the
DFHTRSU. global trap exit only in consultation with an IBM support
Explanation: The recovery routine belonging to the trace representative.
domain module DFHTRSU has received control. Module: DFHTRPT, DFHTRFT
This indicates a program check or abend has occurred in that XMEOUT Parameters: applid, modname
module. Destination: Console
There are three possible causes of this condition:

v DFHTRSU has been overwritten in main storage. DFHTR1001 applid Program check occurred within global
v DFHTRSU is at an incompatible level with the rest of the trap exit - DFHTRAP now marked unusable
CICS modules. by module modname.
v There is an error in DFHTRSU. Explanation: After making a trace entry, the CICS trace
System action: A system dump with dump code domain (TR) called the field engineering global trap exit
KERNDUMP is taken. program (DFHTRAP). A program check occurred during
User response: There may be an error in CICS code. The execution of DFHTRAP.
severity of its impact depends on the importance of the System action: CICS marks the currently active version of
DFHTRAP unusable, and will ignore it on future calls to TR
domain. CICS then takes a dump with system dump code
CICS may not have been terminated. TR1001, and continues execution.
User response: Use the dump to find the cause of the
If the message occurs once and module DFHTRSU is not program check. To replace the currently active but unusable
crucial to the running of your CICS system, you may decide to DFHTRAP by a new version in the CICS program library,
continue to run and bring CICS down at a convenient time to issue the following commands in the sequence shown:
resolve the problem. CSFE DEBUG,TRAP=OFF (to deactivate the current trap)
CEMT SET PROGRAM(DFHTRAP) NEWCOPY (to update
the trap disk address known to CICS)
of module DFHTRSU, bring CICS down in a controlled
CSFE DEBUG,TRAP=ON (to activate the new version of
shutdown.
the trap)
Use the dump to determine the cause of the condition.
Module: DFHTRSU
Module: DFHTRPT, DFHTRFT

DFHTR0117 applid Auxiliary trace on data set dataset has Destination: Console
been stopped.
Explanation: An operator or application program request, to
stop CICS tracing to the auxiliary trace data set dataset, has DFHTR1002 applid Program DFHTRAP is not available -
been successfully processed. global trap not activated
System action: CICS continues with auxiliary trace inactive. Explanation: CICS could not activate the field engineering
User response: The auxiliary trace data set dataset can now global trap exit program, DFHTRAP, during processing of the
be processed by the print routine DFHTU410. TRAP=ON SIT keyword or override in CICS initialization.
Module: DFHTRSR This is almost certainly because DFHTRAP is not present in
the program library.
XMEOUT Parameters: applid, dataset System action: CICS takes a system dump with dump code
Destination: Console TR1002 and continues with the global trap not activated.
User response: Ensure that DFHTRAP is defined to RDO and
made available in the program library.
DFHTR0118 applid Auxiliary trace is being switched from
dataset1 to dataset2. You should use the global trap exit only in consultation with
Explanation: An operator or application program request to an IBM support representative.
switch extents on the auxiliary trace data set while auxiliary Module: DFHTRDM
trace is active is being processed. XMEOUT Parameter: applid
System action: CICS stops tracing on the first named data set Destination: Console
dataset1, and resumes tracing on the second named data set
dataset2.
User response: The first named auxiliary trace data set
dataset1 can now be processed by the print routine DFHTU410.

DFHTR1003 • DFHTS1301
User response: Ensure that the DLBL statement for

DFHTR1003 applid CICS system dump requested by
DFHAUXT is present and correct in the DFHTU410 job.
global trap exit DFHTRAP in module
Module: DFHTRPRA
modname.
Explanation: The user-coded global trap exit program
(DFHTRAP) has requested a system dump in its return action
settings. DFHTR3003 ERROR IN OPENING DFHAXPM FILE.
System action: CICS takes a system dump with dump code Explanation: The auxiliary trace print program DFHTU410
TR1003 and continues with the global trap still active. could not open the parameter input data set DFHAXPM.
User response: Analyse the requested dump. System action: The print job terminates with a return code of
You should use the global trap exit only in consultation with 8.
an IBM support representative. User response: Ensure that the DLBL statement for
Module: DFHTRPT, DFHTRFT DFHAXPM is correct in the DFHTU410 job, or remove the
DLBL and specify your input parameters via SYSIPT or on the
XMEOUT Parameters: applid, modname PARM keyword of the EXEC statement.
Destination: Console Module: DFHTRPRA
DFHTR3001 ERROR IN OPENING DFHAXPR FILE.

Explanation: The auxiliary trace print program DFHTU410 DFHTR3010 ERROR IN TRACE DATA - ENTRIES MAY
could not open the data set defined to receive the print HAVE BEEN LOST.
output. Explanation: The trace block being formatted contains invalid
System action: The print job terminates with a return code of length and/or pointer fields. This can happen if the trace table
8. is accidentally overwritten.
User response: Ensure that the DLBL statement for System action: The trace formatting code scans the block to
DFHAXPR is correct in the DFHTU410 job or remove DLBL try and find valid entries. Any that are found are printed. The
statement and allow DFHTU410 to write the output to rest of the data is ignored.
SYSLST. User response: Try and determine what caused the
Module: DFHTRPRA overwriting of the internal trace table.
The trace entries immediately before and after this message in
the print out should be viewed with suspicion. They may
DFHTR3002 ERROR IN OPENING DFHAUXT FILE. contain incorrect data, or there may be one or more entries
Explanation: The auxiliary trace print program DFHTU410 missing altogether at this point.
could not open the auxiliary trace data set to be processed. Module: DFHTRFPB
System action: The print job terminates with a return code of Destination: SYSLST
8.
DFHTSxxxx messages
control intervals which will be formatted.
DFHTS0100I applid Temporary Storage initialization has
System action: CICS continues. Message DFHTS0101 is
started.
issued when temporary storage initialization has been
Explanation: This is an informational message indicating the
completed. Note that formatting can take a significant time if
start of temporary storage initialization.
the data set is large.
Module: DFHTSRP.
Module: DFHTSRP
XMEOUT Parameters: applid, numcis
DFHTS1300 applid Clock is not in set state, reply 'RETRY',

DFHTS0101I applid Temporary Storage initialization has
'GO' or 'CANCEL'.
ended.
Explanation: The STCK value of the processor store clock is
Explanation: Temporary storage initialization has completed
either currently less than the value keypointed during the
successfully
previous execution, or the store clock itself is disabled or not
set.
System action: The system waits for operator response.
User response: Set the clock and continue or cancel. A 'GO'
Module: DFHTSRP
response, as a result of this message, initializes CICS with a
XMEOUT Parameter: applid cold start of temporary storage.
Destination: Console Module: DFHTSRP
DFHTS0102I applid About to format the temporary storage Destination: Console
data set (numcis control intervals).
Explanation: Temporary storage has been cold-started with a
DFHTS1301 applid {READ | WRITE} Error detected by
new data set. This message is issued when formatting of the
temporary storage. RPL feedback area is
data set commences, and indicates the number numcis of
X'yyyyy'.

DFHTS1302 • DFHTS1308
Explanation: An I/O error has been detected by temporary

DFHTS1305 CURRENT STCK VALUE LESS THAN
storage. Either:
TEMPORARY STORAGE RECORD STCK
v A hardware error occurred while a task was accessing the
VALUE. REPLY 'GO' OR 'CANCEL'.
temporary storage data set, or
Explanation: The processor store clock (STCK) value is
v VSAM detected a logic error in the request. The most likely
currently less than the value recorded during the previous
cause of this is that the data set was defined incorrectly.
execution.
System action: An I/O ERROR return code is returned to the
System action: CICS either cold starts temporary storage
application program.
(response of 'GO'), or the emergency restart process is
Message DFHME0116 is normally produced containing the terminated (response of 'CANCEL') with a dump.
symptom string for this problem. User response: Set the clock and continue or cancel. A 'GO'
User response: Ensure that the definition of the temporary response initializes CICS with a cold start of temporary
storage data set is correct. storage.
Module: DFHTSRP
See the CICS Problem Determination Guide for more guidance in Destination: Console
dealing with temporary storage problems.
Module: DFHTSP
DFHTS1306 applid Restart has been terminated by request
XMEOUT Parameters: applid, {1=READ, 2=WRITE}, X'yyyyy'
from operator.
Explanation: This message is issued in response to a
CANCEL reply from one of the messages, DFHTS1304,
DFHTS1302 applid I/O error on temporary storage data set DFHTS1305, and DFHTS1308.
attempting to emergency restart System action: CICS is abnormally terminated with a dump.
Explanation: An unrecoverable I/O error has occurred on the User response: None.
temporary storage data set. Module: DFHTSRP
System action: The emergency restart process is abnormally XMEOUT Parameter: applid
terminated with a system dump. Destination: Console
User response: Correct the problem and either try an
emergency restart, or try to initialize CICS with a cold start of
temporary storage. DFHTS1307 applid Interval control element not
Module: DFHTSRP recoverable.
Explanation: An attempt to schedule an interval control
element (ICE) during emergency restart of temporary storage
has failed.
The most likely reason is that following restart the terminal

DFHTS1303 applid No storage available for temporary associated with the ICE is not known to the system.
storage control blocks
Explanation: An attempt to allocate storage during Another possible reason is that the ICE is for an autoinstalled
emergency restart failed because insufficient storage was TCTTE that has been deleted at emergency restart. The
available. deletion occurred because the AIRDELAY system initialization
System action: The emergency restart process is abnormally parameter of zero was specified which means autoinstalled
terminated with a dump. TCTTEs are deleted immediately.
User response: Use the dump to investigate the Storage System action: Processing continues.
Manager domain statistics. It may be necessary to increase the User response: None.
size of a dynamic storage area (DSA). Module: DFHTSRP
Module: DFHTSRP
DFHTS1308 TEMPORARY STORAGE DATA ADDRESS

DFHTS1304 applid Clock is not in set state, reply 'RETRY', NOT RECOVERABLE. REPLY 'GO' OR
'GO' or 'CANCEL'. 'CANCEL'.
Explanation: The STCK value of the processor store clock is Explanation: During emergency restart of temporary storage,
either currently less than the value keypointed during the the data associated with a recoverable data identification
previous execution, or the store clock itself is disabled or not (DATAID) could not be found on the data set.
set.
If TSAGE is specified as nonzero in the TST generation, it is
System action: The system waits for operator response.
possible that this message is issued validly. In this case, for a
User response: Set the clock and continue or cancel. A 'GO'
given TS queue, emergency restart may not have recovered
response, as a result of message DFHTS1304, initializes CICS
some or all of the TS records created before the value specified
with a cold start of temporary storage.
by TSAGE. If the operator allows emergency restart to
Module: DFHTSRP
continue, and only some of the records have been recovered,
XMEOUT Parameter: applid IOERR is returned to any transaction which attempts to access
Destination: Console the records which have not been recovered. However, the TS
records can be purged successfully by a transaction.
If the operator allows emergency restart to continue and none
of the records in the queue have been recovered, QIDERR is

returned to any transaction that attempts to access that queue. Whatever the cause of the error, temporary storage must now
System action: The system waits for a reply of GO or be cold-started.
CANCEL.
If overwriting has occurred, contact your IBM Support Center
If you reply 'GO', data that cannot be located is not restored.
for assistance in writing a trap to detect the cause.
All other data is restored.
The DATAID(s) for data not restored are written to transient Note that CICS also abends with a DFHTS1310 message if a
data destination CSSL. For each DATAID, a message line is record length is such that the record seems to extend beyond
written quoting the actual identification in the form: the end of the buffer. If this is the case, then the length of the
DFHTSR dataid - UNRECOVERABLE TEMP STRG DATAID buffer is the same as the VSAM CI size (TSACSZ). When this
occurs determine why the length is incorrect (an overlay
If you reply 'CANCEL', the system abnormally terminates before the CI was written to disk is the most probable cause of
with message DFHTS1306. this problem)
User response:
1. Cancel to determine the cause of the error. If an overlay has occurred, you will need further assistance
2. Allow CICS to initialize without the data. from IBM. See Part 4 of the CICS Problem Determination Guide
3. Initialize CICS with a cold start of temporary storage. for guidance on how to proceed.
Module: DFHTSRP Module: DFHTSP
DFHTS1309 applid Temporary storage is being cold started
Explanation: This message is issued in response to a 'GO'
DFHTS1311 applid Temporary storage data set is full and
reply from message DFHTS1304 or message DFHTS1305.
cannot be extended
System action: CICS cold starts temporary storage.
Explanation: The temporary storage data set is full. CICS has
failed in an attempt to extend it.
Module: DFHTSRP
XMEOUT Parameter: applid User response: Consider whether you need to increase the
Destination: Console space allocation for the temporary storage data set.
Module: DFHTSP
DFHTS1310 applid Temporary storage data set does not XMEOUT Parameter: applid
match bit map Destination: Console
Explanation: During compression to reacquire unused space
in a temporary storage data set control interval (CI), CICS
DFHTS1312I PROGRAM DFHTSRP CANNOT BE
discovered an incompatibility between the records in the CI,
FOUND.
the unit tables, and the bit map.
Explanation: CICS cannot find the temporary storage restart
The temporary storage program, DFHTSP, tries to move all the program, DFHTSRP, in any sublibrary of the LIBDEF search
valid records in a CI to the left in order to leave a contiguous chain for the CICS startup job stream.
space for new temporary storage records. It first checks, using System action: CICS abnormally terminates the temporary
the temporary storage common area (TSCOM), whether the CI storage restart task. CICS issues another message asking you
would have enough room for the record it is trying to write. If to reply GO or CANCEL.
there is room, but there is insufficient contiguous space at the User response: If you reply 'GO' to the second message, CICS
end of the CI, it scans the CI from left to right to determine continues processing, but without support for temporary
whether each record is still valid. storage. If you reply 'CANCEL', CICS terminates abnormally
with a dump.
During its first pass of the buffer, if it finds a record to be
valid, DFHTSP sets the flag TSCIREQD to one in the record. If To correct this error, place DFHTSRP in a sublibrary of the
the record is no longer required, DFHTSP sets TSCIREQD to LIBDEF search chain for the CICS startup job stream.
zero. Also during its first pass, DFHTSP updates the disk Module: DFHTSP
addresses of the records still required to reflect where they Destination: Console
will be after compression has been performed.
During the second pass of the buffer, DFHTSP moves records DFHTS1313 applid Temporary storage restart failed.
to the left, leaving contiguous free space to the right. Explanation: The CICS temporary storage restart task could
System action: CICS is abnormally terminated with a dump. not complete because a necessary step failed. The task has
done some essential recovery operations and abnormally
Message DFHME0116 is normally produced containing the terminated itself with code ATSA.
symptom string for this problem. System action: CICS writes a transaction dump for the
User response: To determine the cause of the error, check temporary storage restart task.
that:
v The correct data set was used. CICS sends two messages to the console, this one, and one to
v The CISIZE of DFHTEMP was not altered between CICS identify the error detected by the temporary storage restart
runs (if CISIZE was altered, temporary storage should have task. A third message follows either to say that CICS has
been cold started). 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

DFHTS1324 applid Temporary storage byte map cannot be
component.
restored.
User response: First, if CICS has requested a response, you
Explanation: An error occurred while the temporary storage
must reply.
byte map was being restored from the CICS global catalog
If you reply 'GO', CICS continues processing, but without (DFHGCD).
support for temporary storage. System action: The temporary storage initialization task is
abnormally terminated. This causes message DFHTS1313 to be
If you reply CANCEL, CICS terminates abnormally with a sent to the console.
dump.
A system dump with dumpcode TS1324 is taken unless you
Use the messages and dumps to find out the cause of the have specifically suppressed dumps in the dump table.
failure.
Module: DFHTSRP Message DFHME0116 is normally produced containing the
XMEOUT Parameter: applid User response: See message DFHTS1313 for further guidance.
Use the dump to determine the cause of the catalog problem.
DFHTS1314 applid Program DFHTSUT cannot be loaded. See the CICS Problem Determination Guide for more guidance in
Explanation: The temporary storage unit table program, dealing with temporary storage problems.
DFHTSUT, cannot be loaded, probably because it is not Module: DFHTSRP
available. It is not available if CICS cannot find DFHTSUT in
any sublibrary of the LIBDEF search chain for the CICS
startup job stream.
User response: To correct this error, place DFHTSUT in a DFHTS1325 applid Temporary storage unit tables cannot
sublibrary of the LIBDEF search chain for the CICS startup job be restored.
stream. Explanation: An error has occurred while the temporary
Module: DFHTSIP storage unit tables are being restored from the CICS global
catalog (DFHGCD).
System action: The temporary storage initialization task is
sent to the console.
DFHTS1315 applid The temporary storage data set has
A system dump with dumpcode TS1325 is taken unless you
exceeded the maximum number of control
intervals supported.
Explanation: During a temporary storage write request, an Message DFHME0116 is normally produced containing the
attempt has been made to add a new control interval to the symptom string for this problem.
temporary storage data set. The temporary storage data set User response: See message DFHTS1313 for further guidance.
already contains the maximum number of supported control
intervals and cannot be extended. Use the dump to determine the cause of the catalog problem.
System action: Processing continues. See the CICS Problem Determination Guide for more guidance in
User response: Consider whether you need to increase the dealing with temporary storage problems.
control interval size for the temporary storage data set. See the Module: DFHTSRP
CICS System Definition Guide for guidance on defining the
temporary storage data set. XMEOUT Parameter: applid
Module: DFHTSP Destination: Console

Destination: Console DFHTS1340 applid No DLBL statement provided for
temporary storage data set.
Explanation: CICS is unable to open the auxiliary temporary
DFHTS1317 applid No DSA storage available below the storage data set (DFHTEMP) because no DLBL statement has
line for temporary storage control blocks. been provided.
Explanation: An attempt to allocate storage during System action: A dump is provided and CICS is terminated.
emergency restart failed because insufficient below the line User response: Correct the error and restart CICS.
storage was available. Module: DFHSIG1
System action: The emergency restart process is abnormally
terminated with a dump. XMEOUT Parameter: applid
User response: Use the dump to investigate the Storage Destination: Console
Manager domain statistics. It may be necessary to increase the
size of a dynamic storage area (DSA).
DFHTS1341 applid VSAM error processing SHOWCAT for
Module: DFHTSRP
temporary storage data set.
XMEOUT Parameter: applid Explanation: VSAM has detected an error during SHOWCAT
Destination: Console processing for the auxiliary temporary storage data set
(DFHTEMP).
User response: Correct the error and restart CICS.

Module: DFHSIG1
DFHTS1372 applid VSAM error processing OPEN for
XMEOUT Parameter: applid temporary storage data set, R15=retcode,
Destination: Console RC=errorcode
Explanation: VSAM has detected an error during OPEN
processing for the auxiliary temporary storage data set. The
DFHTS1342 applid Invalid VSAM definition for temporary inserts identify the return code and the error code.
storage data set. System action: The temporary storage initialization task is
Explanation: CICS is unable to open the auxiliary temporary abnormally terminated; this causes message DFHTS1313 to be
storage data set (DFHTEMP) because it is not defined as sent to the console.
VSAM ESDS.
System action: A dump is provided and CICS is terminated. Message DFHME0116 is normally produced containing the
User response: Correct the error and restart CICS. symptom string for this problem.
Module: DFHSIG1 User response: See message DFHTS1313 for more guidance.
XMEOUT Parameter: applid Check the VSAM OPEN return code retcode and error code
Destination: Console errorcode in section "VSE/VSAM Codes" in z/VSE Messages and
Codes - Volume 2.
Module: DFHTSRP
DFHTS1362 applid Temporary storage data set not
formatted XMEOUT Parameters: applid, retcode,errorcode
Explanation: The auxiliary temporary storage data set Destination: Console
(DFHTEMP) is not formatted. It is empty. If initial formatting
is necessary, it is performed when temporary storage is cold DFHTS1373 applid VSAM error processing CLOSE for
started. temporary storage data set, R15=retcode,
System action: The temporary storage initialization task is RC=errorcode
abnormally terminated. This causes message DFHTS1313 to be Explanation: VSAM has detected an error during CLOSE
sent to the console. processing for the auxiliary temporary storage data set
User response: Refer to DFHTS1313. Correct the error and (DFHTEMP). The inserts identify the return code and the error
restart CICS. code.
Module: DFHTSRP System action: The temporary storage initialization task is
XMEOUT Parameter: applid abnormally terminated; this causes message DFHTS1313 to be
Destination: Console sent to the console.
DFHTS1363 applid Invalid control record for temporary symptom string for this problem.
storage data set User response: See message DFHTS1313 for more guidance.
Explanation: The auxiliary temporary storage data set Check the VSAM CLOSE return code retcode and error code
(DFHTEMP) was not initialized for temporary storage. errorcode in section "VSE/VSAM Codes" in z/VSE Messages and
System action: The temporary storage initialization task is Codes - Volume 2.
abnormally terminated. This causes message DFHTS1313 to be Module: DFHTSRP
User response: Refer to DFHTS1313. Correct the error and XMEOUT Parameters: applid, retcode,errorcode
restart CICS. Destination: Console
Module: DFHTSRP
XMEOUT Parameter: applid DFHTS1374 applid VSAM error processing PUT for
Destination: Console temporary storage data set, R15=retcode,
RC=errorcode
Explanation: VSAM has detected an error during PUT
DFHTS1371 applid VSAM error processing SHOWCB for processing for the auxiliary temporary storage data set
temporary storage data set, RC=retcode (DFHTEMP). The inserts identify the return code and the error
Explanation: VSAM has detected an error during SHOWCB code.
processing for the auxiliary temporary storage data set System action: The temporary storage initialization task is
(DFHTEMP). abnormally terminated. This causes message DFHTS1313 to be
System action: The temporary storage initialization task is sent to the console.
sent to the console. Message DFHME0116 is normally produced containing the
Message DFHME0116 is normally produced containing the User response: See message DFHTS1313 for more guidance.
User response: Refer to DFHTS1313. Check the VSAM PUT return code retcode and error code
errorcode in section "VSE/VSAM Codes" in z/VSE Messages and
Check the VSAM SHOWCB return code retcode in section Codes - Volume 2.
"VSE/VSAM Codes" in z/VSE Messages and Codes - Volume 2. Module: DFHTSRP
Module: DFHTSRP
XMEOUT Parameters: applid, retcode,errorcode
XMEOUT Parameters: applid, retcode Destination: Console

DFHTS1375 applid VSAM error processing GET for DFHTS1378 applid Logic error during temporary storage
temporary storage data set, R15=retcode, backout
RC=errorcode Explanation: During an emergency restart, the temporary
Explanation: VSAM has detected an error during GET storage backout program has detected a logic error.
processing for the auxiliary temporary storage data set System action: CICS terminates the task with an abnormal
(DFHTEMP). The inserts identify the return code and the error termination code ABP3 and issues message DFHTS1313 to
code. indicate that temporary storage restart has failed.
abnormally terminated. This causes message DFHTS1313 to be Message DFHME0116 is normally produced containing the
User response: See message DFHTS1313 for more guidance.
User response: See message DFHTS1313 for more guidance.
Check the VSAM GET return code retcode and error code Module: DFHTSBP
errorcode in section "VSE/VSAM Codes" in z/VSE Messages and
Codes - Volume 2. XMEOUT Parameter: applid
Module: DFHTSRP
XMEOUT Parameters: applid, retcode,errorcode
Destination: Console DFHTS1379 applid Temporary storage MVCL failed with
destructive overlap
Explanation: A move of data to or from temporary storage
DFHTS1376 applid VSAM error processing MODCB for failed. The probable reason for this is that the size of the area
temporary storage data set, R15=retcode being passed to CICS was inconsistent with the data length
Explanation: VSAM has detected an error during MODCB being used.
processing for the auxiliary temporary storage data set System action: The transaction is abnormally terminated with
(DFHTEMP). The insert identifies the return code. a CICS system dump.
abnormally terminated. This causes message DFHTS1313 to be Message DFHME0116 is normally produced containing the
sent to the console. symptom string for this problem.
User response: This is most likely an internal logic error in
Message DFHME0116 is normally produced containing the temporary storage processing. You need further assistance
symptom string for this problem. from IBM to resolve this problem. See Part 4 of the CICS
User response: See message DFHTS1313 for more guidance. Problem Determination Guide for guidance on how to proceed.
Module: DFHTSP
Check the VSAM MODCB return code retcode and error code
errorcode in section "VSE/VSAM Codes" in z/VSE Messages and XMEOUT Parameter: applid
Codes - Volume 2. Destination: Console
Module: DFHTSRP
XMEOUT Parameters: applid, retcode DFHTS1380 applid Severe error occurred while waiting for
Destination: Console I/O to the temporary storage data set to
complete.
Explanation: A CICS task was waiting for I/O to the
DFHTS1377 applid Error during temporary storage
temporary storage data set to complete and the wait failed for
backout, operation failed
an unexpected reason. This message indicates a possible error
Explanation: During an emergency restart, while performing
in CICS code.
a CONNECT, STARTBROWSE, or GETNEXT operation
(indicated by operation), the temporary storage backout
program, DFHTSBP, has received a bad response from a
recovery control request. This is possibly due to an I/O error.
System action: CICS terminates the task with an abnormal
Module: DFHTSP
termination code ABP2 and issues message DFHTS1313 to
indicate that temporary storage restart has failed. XMEOUT Parameter: applid
User response: See message DFHTS1313 for more guidance. DFHTS1576 applid Temporary storage format error
Explanation: A nonzero return code was received from the
Use the dump to determine the cause of the failure.
VSAM macro GENCB when CICS was attempting to build a
See the CICS Problem Determination Guide for more guidance in VSAM request parameter list (RPL).
dealing with temporary storage problems. System action: CICS terminates abnormally with a system
Module: DFHTSBP dump. Message DFHME0116 is normally produced containing
the symptom string for this problem.
XMEOUT Parameters: applid, operation User response: You need further assistance from IBM to
Destination: Console resolve this problem. See Part 4 of the CICS Problem
Module: DFHTSIP

DFHTS1599 • DFHUS0004
XMEOUT Parameter: applid system initialization parameter as appropriate to allocate more

Destination: Console storage for CICS's use. You can get information about the
location, size and number of occurrences of relevant control
blocks by using the CICS Data Areas manual in conjunction
DFHTS1599 applid Partition size insufficient to initialize with the system dump.
CICS. Module: DFHTSIP
Explanation: CICS has been unable to get sufficient storage
for its own control blocks during initialization. XMEOUT Parameter: applid
System action: CICS terminates with a system dump. Destination: Console
User response: Increase the value of DSALIM or EDSALIM
DFHUSxxxx messages
uniquely identifies what the error is and where it was
DFHUS0001 applid An abend (code aaa/bbbb) has occurred
detected.
table.
referring to a CICS message (for example, AKEA is a CICS Message DFHME0116 is normally produced containing the
abend code; 1310 refers to message DFHTS1310). symptom string for this problem.
System action: An exception entry is made in the trace table. User response: This indicates a possible error in CICS code.
A system dump is taken, unless you have specifically The severity of its impact depends on the importance of the
suppressed dumps in the dump table. function being executed at the time of the error.
CICS continues unless you have specified in the dump table CICS may not have been terminated. If the message occurs
that CICS should terminate. If appropriate, an error return once and module modname is not crucial to the running of
code is sent to the caller of this domain. In this case CICS your CICS system, you may decide to continue to run and
could be terminated by the caller ( for example, the domain bring CICS down at a convenient time to resolve the problem.
Message DFHME0116 is normally produced containing the of module modname, you should bring CICS down in a
symptom string for this problem. controlled shutdown.
running, it is necessary to decide whether to terminate CICS. You need further assistance from IBM to resolve this problem.
Look up the VSE code, if there is one, in "OS/390 API Abend guidance on how to proceed.
Errors" of z/VSE Messages and Codes - Volume 1. Note: Do not attempt to reroute this message to a transient
Next, look up the CICS alphanumeric code in “Transaction data queue.
Abend Codes (CICS Transaction Server for VSE/ESA)” on Module: DFHUSAD, DFHUSDM, DFHUSFL, DFHUSIS,
page 453. This tells you, for example, whether the error was a DFHUSST, DFHUSXM
down at a convenient time to resolve the problem. DFHUS0004 applid A possible loop has been detected at
If you cannot run without the full use of module modname you Explanation: A CICS function is taking more time to process
should bring CICS down in a controlled shutdown. than CICS expects. A possible loop has been detected in
You need further assistance from IBM to resolve this problem. module modname at offset X'offset'. This is the offset of the
See Part 4 of the CICS Problem Determination Guide for instruction which was executing at the time the error was
guidance on how to proceed. detected.
Module: DFHUSAD, DFHUSDM, DFHUSFL, DFHUSIS, System action: An exception entry is made in the trace table.
DFHUSST, DFHUSXM A system dump is taken, unless you have specifically
Destination: Console CICS continues unless you have specified in the dump table
DFHUS0002 applid A severe error (code X'code') has could be terminated by the caller ( for example, the domain
occurred in module modname. manager, DFHDMDM). A message is issued to this effect.
The code X'code' is the exception trace point ID which Message DFHME0116 is normally produced containing the

DFHUS0006 • DFHUS0120
symptom string for this problem. CICS down in a controlled shutdown.

not been terminated, it is necessary to decide whether the
return code in "OS/390 API Return Codes" in section
Since some CICS functions can use a lot of processor time, this Messages and Codes - Volume 1.
Try decreasing the size limits of the DSAs or EDSAs. Or, try
increasing the size of the whole partition, if it is not already at
maximum size. See the CICS System Definition Guide or the
CICS Performance Guide for more information on CICS storage.
that module modname in the message is terminated and CICS
continues. Note: Do not attempt to reroute this message to a transient
data queue.
But if you have declared ICVR=0 and you consider that Module: DFHUSDM, DFHUSAD
CICS in order to terminate the runaway function. XMEOUT Parameters: applid, X'code',modname, vsecode
interval. You have to bring CICS down at a suitable time to do DFHUS0050 applid The default userid userid1 cannot be
this permanently. However you can change the ICVR time used by this CICS job with region userid
interval temporarily online, using the CEMT transaction. userid2.
Explanation: The default userid specified in the system
If raising the ICVR time does not solve the problem, you will initialization parameter DFLTUSER cannot be used by this
need further assistance from IBM. See Part 4 of the CICS CICS job.
The region userid for this CICS job is not authorized to use
the userid specified in the DFLTUSER system initialization
Note: Do not attempt to reroute this message to a transient parameter.
data queue. System action: CICS initialization terminates.
Module: DFHUSAD, DFHUSDM, DFHUSFL, DFHUSIS, User response: Ensure the default userid and the userid for
DFHUSST, DFHUSXM the CICS region are correct.
XMEOUT Parameters: applid, X'offset', modname If the two userids are correct, obtain the necessary
Destination: Console authorization for the default userid to be used by the CICS
region userid. This may require the assistance of a security
administrator.
DFHUS0006 applid Insufficient storage to satisfy Getmain
(code X'code') in module modname. VSE code Previous messages may have been produced by the job giving
vsecode. additional information.
Explanation: Insufficient storage is available to satisfy a Module: DFHUSDM
storage request issued by module modname. XMEOUT Parameters: applid, userid1,userid2
The code X'code' is the exception trace point ID which Destination: Console
The code vsecode is the OS/390 GETMAIN return code. DFHUS0120 applid An error occurred when performing
System action: An exception entry is made in the trace table SNSCOPE checking for a sign on request.
(code X'code'). A system dump is taken, unless you have Explanation: The OS/390 ENQ issued as part of SNSCOPE
specifically suppressed dumps in the dump table. checking has failed. The return code indicates that 31-bit
system GETVIS has been exhausted.
CICS continues unless you have specified in the dump table System action: A system dump is suppressed, unless you
that CICS should terminate. have specifically enabled dumps for this dumpcode in the
dump table. The request to signon is rejected.
If appropriate, an error return code is sent to the caller of this User response: Increase the amount of available 31-bit system
domain. In this case, CICS could be terminated by the caller GETVIS. For information on how to do this see the description
(for example, the domain manager, DFHDMDM). A message is of the SVA command in the z/VSE System Control Statements
issued to this effect. manual.
symptom string for this problem. Note: Do not attempt to reroute this message to a transient
User response: If CICS has been terminated by another data queue.
module, look out for the relevant termination messages (from, Module: DFHUSAD, DFHUSFL
for example, the domain manager), and look up the User XMEOUT Parameter: applid
Response for these messages. Destination: Console
which rights itself if more storage becomes available. If you

DFHUS0150 • DFHWB0002

DFHUS0150 applid An attempt to establish security has
data queue.
failed for userid userid in group groupid, {no
terminal, | netname | console }portname applid Module: DFHUSXM
applid. Unable to initialize the transaction XMEOUT Parameters: applid, userid,groupid, {99=no terminal,
tranid. SAF codes are (X'safresp',X'safreas'). 1=netname, 2=console }, portname, applid, tranid, X'safresp',
ESM codes are (X'esmresp',X'esmreas'). X'safreas', X'esmresp', X'esmreas'
Explanation: An attempt was made to establish security for Destination: Console
userid userid in group groupid with access to resources allowed
for the terminal or console portname and the application applid.
The attempt was rejected by the external security manager DFHUS0200 date time applid User userid in group groupid{ at
(ESM). netname | at console }portname has been timed
The transaction tranid cannot be initialized. out.
System action: Security has not been established for the Explanation: User userid in group groupid (at terminal
userid. The attempt to initialize the transaction has failed. portname if appropriate) has been removed from this CICS
User response: The response and reason codes (safresp and system because the userid has been unused for a period
safreas) returned by the system authorization facility (SAF), longer than that specified in the USRDELAY system
and the response and reason codes (esmresp and esmreas) initialization parameter.
returned by the external security manager (ESM) are those System action: Processing continues.
issued by the RACROUTE REQUEST=VERIFY or RACROUTE User response: See the CICS System Definition Guide for more
REQUEST=EXTRACT macros. For the meaning of the information about the USRDELAY system initialization
response and reason codes in the message see "BSM Return parameter.
Codes" in section "VSE/Advanced Functions Codes & SVC Module: DFHUSDM
XMEOUT Parameters: date, time,applid, userid, groupid, {1= at
There may be further messages produced by CICS or the netname, 2= at console }, portname
external security manager (ESM) which provide more Destination: CSCS
information.
DFHWBxxxx messages
cannot run without the full use of module modname you
DFHWB0001 applid An abend (code aaa/bbbb) has occurred
Explanation: An abnormal end (abend) or program check has You need further assistance from IBM to resolve this problem.
occurred in module modname. This implies that there may be See Part 4 of the CICS Problem Determination Guide for
an error in the CICS code. Alternatively, unexpected data has guidance on how to proceed.
been input, or storage has been overwritten. Destination: Console
Module: DFHWBWB
applicable), followed by a 4-digit alphanumeric CICS code. XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
hyphens. The CICS code is an abend code or a number DFHWB0002 applid A severe error (code X'code') has
referring to a CICS message (for example, AKEA is a CICS occurred in module modname.
abend code; 1310 refers to message DFHTS1310). Explanation: An error has been detected in module modname.
System action: An exception entry is made in the trace table. The code X'code' is the exception trace point ID, which gives
A system dump is taken, unless you have specifically an indication of the cause of the error:
suppressed dumps in the dump table. v 4643—DFHWBST was called with an invalid format
v 4644—DFHWBST was called with an invalid function
CICS continues unless you have specified in the dump table v 4647—The Web State manager was unable to update the
that CICS should terminate. If appropriate, an error return Web state token directory when creating a new state block
v 4654—The Web State manager was unable to browse the
Web state token directory during garbage collection
v 4652—The Web State manager was unable to perform a
Message DFHME0116 is normally produced containing the LOCK of the Web state data
symptom string for this problem. v 4653—The Web State manager was unable to perform an
User response: Notify the system programmer. If CICS is still UNLOCK of the Web state data
running, it is necessary to decide whether to terminate CICS. v 4683—DFHWBTC was called with an invalid format
v 4684—DFHWBTC was called with an invalid function
v 4685—An error was returned by the LE/370 pre-initialized
environment (CEEPIPI)
v 4686—Call to CICS Web 3270 emulator failed
Next, look up the CICS alphanumeric code. This tells you, for System action: An exception entry (code X'code' in the
example, whether the error was a program check, an abend, or message) is made in the trace table. A system dump is taken,
a runaway, and may give you some guidance concerning user unless you have specifically suppressed dumps in the dump
response. table.
If module modname is not crucial to the running of your CICS Message DFHME0116 is normally produced containing the
system, you may decide to continue to run and bring CICS symptom string for this problem.
down at a convenient time to resolve the problem. If you

DFHWB0004 • DFHWB0101
User response: You may need further assistance from IBM to During initialization, CICS may not have access to the user's
resolve this problem. See Part 4 of the CICS Problem applid coded in the SIT. If CICS produces this message in these
Determination Guide for guidance on how to proceed. circumstances, it uses the default applid value DBDCCICS.
Destination: Console System action: CICS will terminate with a system dump. An
Modules: DFHWBST, DFHWBTC exception entry is made in the trace table (code code in the
message).
DFHWB0004 applid A possible loop has been detected at User response: Inform the system programmer.
Explanation: A CICS function is taking more time to process You can get diagnostic information about the VSE return code
than CICS expects. A possible loop has been detected in vsecode in "OS/390 API Return Codes" in section
module modname at offset X'offset'. This is the offset of the "VSE/Advanced Functions Codes & SVC Errors" of z/VSE
instruction that was executing at the time the error was Messages and Codes - Volume 1.
detected.
Try decreasing the overall size limit of the DSAs or EDSAs.
Or, try increasing the size of the whole region, if it is not
already at maximum size. If CICS is not already terminated,
you will need to bring CICS down to do this. See the CICS
Either this is a critical error and CICS is terminated, even if System Definition Guide or the CICS Performance Guide for
you have specified in the dump table that CICS should not further information on CICS storage.
terminate. Destination: Console
Module: DFHWBST
Or CICS will continue unless you have specified in the dump
table that CICS should terminate. Message DFHME0116 is XMEOUT Parameters: applid, X'code',modname, vsecode
normally produced containing the symptom string for this
problem.
DFHWB0100 date time applid tranid The CICS Web Support
program cannot link to program DFHWBBLI.
EIBRESP: eibresp. EIBRESP2: resp2val. Host IP
address: hostaddr. Client IP address:
Because some CICS functions can use a lot of processor time, clientaddr.{ | TCPIPSERVICE: }tcpipservice
this message may have been caused by a long-running Explanation: The alias program used EXEC CICS LINK but
function. So there may not be an error here. Usually, CICS will was unable to link to program DFHWBBLI.
purge a CICS function that exceeds the runaway task time System action: The link is abandoned. An HTTP response
interval that you have specified in the SIT (this is the ICVR code of 500 (internal server error) is returned to the Web
which is measured in milliseconds). This means that the Browser. The alias abends with abend code AWBL.
module modname will be terminated and CICS will continue. User response: Use the CEDA transaction to ensure that
program DFHWBBLI has been correctly defined and installed.
If you have declared ICVR=0 in the SIT and you consider that Destination: CWBO
module modname has gone into a loop, you will have to Module: DFHWBA
XMEOUT Parameters: date, time,applid, tranid, eibresp, resp2val,
If CICS has terminated module modname, and you consider hostaddr,clientaddr, {1=, 2= TCPIPSERVICE: },tcpipservice
interval in the SIT. You will have to bring CICS down at a
suitable time to do this permanently. However, you can DFHWB0101 date time applid tranid The CICS Web Support
change the ICVR time interval temporarily online, using the alias program DFHWBA detected a failure in
CEMT transaction. program DFHWBBLI. Host IP address:
hostaddr. Client IP address: clientaddr.{ |
TCPIPSERVICE: }tcpipservice
Explanation: Program DFHWBBLI has returned an error
response to the alias.
how to proceed.
System action: The request is abandoned. The error response
returned by program DFHWBBLI is returned to the Web
Modules: DFHWBST, DFHWBTC
Browser in an HTTP response:
XMEOUT Parameters: applid, X'offset',modname 403 The userid associated with the request is not
authorized to invoke the requested converter
program, or the requested server program.
DFHWB0006 applid Insufficient storage to satisfy Getmain 404 A link to the converter program or to the server
(code X'code') in module modname. VSE code program failed because CICS could not locate the
vsecode. requested program.
Explanation: An OS/390 GETMAIN was issued by module 500 A link to the converter program or to the server
modname but there was insufficient storage available to satisfy program failed with an unexpected error.
the request. 503 A link to the converter program or to the server
The code X'code' is the exception trace point ID which program failed for one of the following reasons:
The code vsecode is the OS/390 GETMAIN return code.

v The server program is defined as remote, but the Destination: CWBO

link to this program failed with a SYSID error, so Module: DFHWBA
the remote connection is either not defined
XMEOUT Parameters: date, time,applid, tranid, {1=, 2=
correctly, or not active.
TCPIPSERVICE: },tcpipservice
v The link to the converter or the server program
failed with the ROLLEDBACK response.
The alias abends with abend code AWBM. alias program has detected an abend. Host IP
User response: Check program DFHWBBLI and the address: hostaddr. Client IP address:
programs which it calls. clientaddr.{ | TCPIPSERVICE: }tcpipservice
Destination: CWBO Explanation: The alias has detected an abend.
Module: DFHWBA System action: The alias abends with abend code AWBK.
User response: Examine the diagnostics to determine the
XMEOUT Parameters: date, time,applid, tranid, hostaddr,
reason for the error.
clientaddr, {1=, 2= TCPIPSERVICE: }, tcpipservice
Destination: CWBO
Module: DFHWBA
alias program has received an incorrect
response on a call made to CICS during alias
initialization. EIBRESP: eibresp EIBRESP2:
resp2val.{ | TCPIPSERVICE: }tcpipservice DFHWB0109I applid Web domain initialization has started.
Explanation: The alias program has received an unexpected Explanation: This is an informational message indicating the
response on a call made to CICS during alias initialization. start of Web domain initialization.
System action: The alias abends with abend code AWBI. System action: CICS initialization continues.
User response: You may need further assistance from IBM to User response: None. You can suppress this message with
resolve this problem. See Part 4 of the CICS Problem the system initialization parameter, MSGLVL=0.
Destination: CWBO Module: DFHWBDM
Module: DFHWBA
XMEOUT Parameters: date, time,applid, tranid, eibresp, resp2val,
{1=, 2= TCPIPSERVICE: }, tcpipservice
DFHWB0110I applid Web domain initialization has ended.
Explanation: Web domain initialization has completed
DFHWB0103 date time applid tranid The CICS Web Support successfully.
alias program has received an error response System action: CICS initialization continues.
(code X'code') on a call made to CICS during User response: None. You can suppress this message with
alias initialization.{ | TCPIPSERVICE: the system initialization parameter, MSGLVL=0.
}tcpipservice Destination: Console
Explanation: The alias program was unable to locate the Module: DFHWBDM
START data for this request, or the START data was invalid.
The error response code X'code' is the exception trace point id XMEOUT Parameter: applid
that uniquely identifies which error has occurred. A code of
'4565'X means that the START data was missing, and '4566'X DFHWB0111 applid WB Domain initialization failed.
means that the START data was invalid. Reason Code: X'rc'.
System action: The alias abends with abend code AWBF and Explanation: The CICS Web domain initialization failed with
a trace entry is made in the trace table. reason code rc.
User response: The alias program DFHWBA is only to be System action: CICS initialization continues. Subsequent calls
used for alias transactions started by the CICS Web Support. to the components of the CICS Web environment may fail.
User-written applications should not be starting alias User response: Use the reason code rc to determine why
transactions, as data passed to the alias will not be in the initialization failed. The possible reasons are:
expected format. 1 Storage for the Web anchor block could not be
Destination: CWBO obtained.
Module: DFHWBA 5 Storage for the State Manager anchor block could
XMEOUT Parameters: date, time,applid, tranid, X'code', {1=, 2= not be obtained.
TCPIPSERVICE: }, tcpipservice 6 The creation of the State Token Directory failed.
7 The subpool required for state management could
not be added.
DFHWB0106 date time applid tranid The CICS Web Support 8 The subpool required for HTTP buffers could not be
program DFHWBA has detected an error.{ | added.
TCPIPSERVICE: }tcpipservice 9 The addition of the Web State Manager lock failed.
Explanation: The alias had detected an error. A The subpool required for 3270 buffers could not be
System action: A system dump is taken. The alias abends added.
with abend code AWBH. Message DFHME0116 is normally B The initialization of the webrequest class failed.
produced containing the symptom string for this problem. Destination: Console
User response: Examine the diagnostics to determine the Module: DFHWBDM

XMEOUT Parameters: applid, X'rc' XMEOUT Parameters: date, time,applid, tranid,

program_name,eibresp, resp2val, {1=,2= TCPIPSERVICE: },
tcpipservice
program DFHWBBLI has received a corrupt
parameter list from the converter program DFHWB0121 date time applid tranid The CICS Web Support
program_name during {Decode | Encode} program DFHWBBLI encountered an error
processing.{ | TCPIPSERVICE: }tcpipservice during Decode processing in the converter
Explanation: Program DFHWBBLI received an error response program. Response code: respcode, reason code:
from the converter program program_name during either reasoncode.{ | TCPIPSERVICE: }tcpipservice
Decode or Encode processing, and the parameter list being Explanation: The Decode function of the converter has
passed was corrupt. returned an error.
System action: An error message is sent to the client and an System action: An error message is sent to the client.
exception trace entry is made in the trace table. User response: The response code insert gives the
User response: Ensure that the converter program being used RESPONSE code returned by the converter program. The
is correct. reason code insert gives the REASON code returned by the
Destination: CWBO converter program.
Module: DFHWBBLI
The values defined by CICS for these fields are defined in
XMEOUT Parameters: date, time,applid, tranid, copybook DFHWBUCD. The CICS defined values for the
program_name,{4=Decode, 5=Encode}, {1=, 2= TCPIPSERVICE: }, RESPONSE code are:
tcpipservice 0 OK
4 Exception
8 Invalid data supplied
DFHWB0118 date time applid tranid The CICS Web Support 16 Disaster
program DFHWBBLI has detected an error.{ |
The CICS defined values for the REASON code are:
Explanation: Program DFHWBBLI has detected an error.
1 Security failure
System action: A system dump is taken. The transaction
2 Corrupt client data
abends with abend code AWBR. Message DFHME0116 is
problem. Users can architect their own response and reason code values
User response: Examine the diagnostics to determine the to be returned by the analyzer, but they should use values
reason for the error. other than those defined in the CICS supplied copybook
Destination: CWBO DFHWBUCD.
Module: DFHWBBLI
Examine the response and reason codes returned to determine
XMEOUT Parameters: date, time,applid, tranid, {1=, 2= the cause of the error.
TCPIPSERVICE: },tcpipservice Destination: CWBO
Module: DFHWBBLI
DFHWB0119 date time applid tranid The CICS Web Support XMEOUT Parameters: date, time,applid, tranid, program,
program DFHWBBLI has been started respcode, reasoncode,{1=, 2=TCPIPSERVICE: }, tcpipservice
incorrectly.{ | TCPIPSERVICE: }tcpipservice
Explanation: Program DFHWBBLI has detected an error
while validating initialization information. This probably DFHWB0122 date time applid tranid The CICS Web Support
means that the program has been started incorrectly. program DFHWBBLI encountered an error
System action: The transaction abends with abend code during Encode processing in the converter
AWBQ. program. Response code: respcode, reason code:
User response: Check that the program was not started by a reasoncode.{ | TCPIPSERVICE: }tcpipservice
transient data trigger level or by a CECI user. Explanation: The Encode function of the converter program
Destination: CWBO has returned an error.
Module: DFHWBBLI System action: An error message is sent to the client.
User response: The response code insert gives the
XMEOUT Parameters: date, time,applid, tranid, {1=, 2= RESPONSE code returned by the converter program. The
TCPIPSERVICE: },tcpipservice reason code insert gives the REASON code returned by the
converter program.
DFHWB0120 date time applid tranid The CICS Web Support The values defined by CICS for these fields are defined in
program DFHWBBLI cannot link to program copybook DFHWBUCD. The CICS defined values for the
program_name. EIBRESP: eibresp EIBRESP2: RESPONSE code are:
resp2val.{ | TCPIPSERVICE: }tcpipservice 0 OK
Explanation: Program DFHWBBLI used an EXEC CICS LINK 4 Exception
but was unable to link to the given program and an EIB 8 Invalid data supplied
response was returned. 16 Disaster
System action: The link is abandoned.
User response: Ensure that the program definition is correct.
The CICS defined values for the REASON code are:
Destination: CWBO
1 Security failure
Module: DFHWBBLI
2 Corrupt client data

Users can architect their own response and reason code values the program that was servicing the request during Encode
to be returned by the analyzer, but they should use values processing.
other than those defined in the CICS supplied copybook System action: The alias returns control to the caller.
DFHWBUCD. User response: Examine the diagnostics to determine the
Examine the response and reason codes returned to determine Destination: CWBO
the cause of the error. Module: DFHWBBLI
Destination: CWBO XMEOUT Parameters: date, time,applid, tranid, program, {1=, 2=
Module: DFHWBBLI TCPIPSERVICE: }, tcpipservice
XMEOUT Parameters: date, time,applid, tranid, program,
respcode, reasoncode,{1=, 2=TCPIPSERVICE: }, tcpipservice
program DFHWBBLI has detected an abend
DFHWB0123 date time applid tranid The CICS Web Support issued by Decode in converter program.{ |
program DFHWBA1 has detected an error.{ | TCPIPSERVICE: }tcpipservice
TCPIPSERVICE: }tcpipservice Explanation: Program DFHWBBLI has detected an abend by
Explanation: Program DFHWBA1 has detected an error. the converter that was servicing the request during Decode
System action: A system dump is taken. The transaction processing.
abends with abend code AWBR. Message DFHME0116 is System action: The alias returns control to the caller.
normally produced containing the symptom string for this User response: Examine the diagnostics to determine the
problem. reason for the error.
User response: Examine the diagnostics to determine the Destination: CWBO
reason for the error. Module: DFHWBBLI
Destination: CWBO
XMEOUT Parameters: date, time,applid, tranid, program, {1=, 2=
Module: DFHWBA1
TCPIPSERVICE: }, tcpipservice
DFHWB0128 date time applid tranid An error has been
detected by program program.{ |
DFHWB0124 date time applid tranid The CICS Web Support TCPIPSERVICE: }tcpipservice
program DFHWBA1 has been started Explanation: Program DFHWBBLI has detected an error.
incorrectly.{ | TCPIPSERVICE: }tcpipservice System action: The alias returns control to the caller.
Explanation: Program DFHWBA1 has detected an error while User response: Examine the diagnostics to determine the
validating initialization information. This probably means that reason for the error.
the program has been started incorrectly. Destination: CWBO
System action: The transaction abends with abend code Module: DFHWBBLI
AWBQ.
User response: Check that the program was not started by a
transient data trigger level or by a CECI user.
Destination: CWBO
Module: DFHWBA1 DFHWB0130 date time applid tranid No state token passed to
program DFHWBLT.{ | TCPIPSERVICE:
}tcpipservice
Explanation: Program DFHWBLT was not passed the
expected state token.
DFHWB0125 date time applid tranid The CICS Web Support System action: The transaction abends with code AWC2, and
program DFHWBBLI has detected an abend an exception trace entry 410C is written.
issued by the program program.{ | User response: You may need further assistance from IBM to
TCPIPSERVICE: }tcpipservice resolve this problem. See Part 4 of the CICS Problem
Explanation: Program DFHWBBLI has detected an abend by Determination Guide for guidance on how to proceed.
the program that was servicing the request. Destination: CWBO
System action: The alias returns control to the caller. Module: DFHWBLT
User response: Examine the diagnostics to determine the
Destination: CWBO
Module: DFHWBBLI
DFHWB0131 date time applid tranid An error code X'code'
occurred in DFHWBLT while accessing the
Web state data for this transaction.{ |
DFHWB0126 date time applid tranid The CICS Web Support Explanation: The Web Bridge Exit program, DFHWBLT, has
program DFHWBBLI has detected an abend detected an error when attempting to access the Web state
issued by Encode in converter program data held for this transaction.
program.{ | TCPIPSERVICE: }tcpipservice System action: An exception trace entry is made in the trace
Explanation: Program DFHWBBLI has detected an abend by table using code X'code. The transaction abends with abend
code AWC1 if the Bridge Exit was trying to establish a

partnership with the CWI alias transaction. from IBM to resolve this problem. See Part 4 of the CICS
User response: Use the error code code to determine the Problem Determination Guide for guidance on how to proceed.
reason for the failure: Destination: CWBO
4106 Unable to establish a partnership with the associated Modules: DFHWBTTA, DFHWBLT
CWI alias transaction.
XMEOUT Parameters: date, time,applid, tranid, X'code', {1=, 2=
4107 A call to terminate the partnership between this
instance of DFHWBLT and its associated CWI alias
transaction failed.
4108 A call to wait for the CWI alias transaction DFHWB0134 date time applid tranid Error X'code' occurred
associated with this instance of DFHWBLT failed. resolving the AID from HTTP forms data in
4109 A call to reactivate the CWI alias transaction the CICS Web terminal translation
associated with this instance of DFHWBLT failed. application.{ | TCPIPSERVICE: }tcpipservice
4116 A call to suspend this instance of DFHWBLT failed. Explanation: Program DFHWBTTA is unable to resolve an
4112 A call to update the state data for this transaction attention identifier from the HTTP forms data returned from a
failed. web browser. DFHWBTTA translates the HTTP forms data into
4113 A call to retrieve the state data for this transaction the correct 3270 format required by the CICS terminal-oriented
failed. transaction that is the target of this request. The attention
4114 The alias task associated with this instance of identifier or AID is a mandatory part of this format.
DFHWBLT was not in the required state. DFHWBTTA cannot locate a name=value pair in the HTTP
411B A call to destroy the state data for this instance of forms data that adheres to the naming convention defined by
DFHWBLT failed. the CICS Web Support to represent an AID, and so cannot
return an AID value to the terminal-oriented transaction.
The most likely cause of the error is that the timeout interval System action: DFHWBTTA returns an internal server error
for the Web state data has been exceeded, and the relevant (HTTP response 500) to the HTTP client, and terminates the
state data has been deleted. Check that the timeout interval for exchange with the terminal-oriented transaction.
the state data is set to a suitable value. You may need further User response: The error code code identifies the CICS trace
assistance from IBM to resolve this problem. See Part 4 of the entry that corresponds to the failure. The HTTP forms data is
CICS Problem Determination Guide for guidance on how to produced as trace data. Collect the CICS trace output.
proceed. Examine the HTTP forms data to determine what was
Destination: CWBO returned from the web browser. Identify what HTML input
Module: DFHWBLT type caused the web browser to submit the HTML form.
Corruption of the HTTP forms data may be the cause of the
problem. You may need further assistance from IBM to resolve
DFHWB0132 date time applid tranid Program DFHWBLT Destination: CWBO
terminated due to storage problems.{ | Module: DFHWBTTA
Explanation: A getmain for storage issued by DFHWBLT
failed. Without the storage, processing cannot continue.
System action: The transaction abends with code AWC5, and
an exception trace entry 410D is written. DFHWB0135 date time applid tranid Error X'code' occurred
User response: If this error occurs repeatedly, you may need resolving the next transaction identifier from
to examine the storage setup of your CICS system. Refer to HTTP forms data in the CICS Web terminal
the CICS Customization Guide for further information on translation application.{ | TCPIPSERVICE:
controlling CICS storage. }tcpipservice
Destination: CWBO Explanation: Program DFHWBTTA is unable to resolve the
Module: DFHWBLT next transaction identifier from the HTTP forms data returned
from a web browser. DFHWBTTA translates the HTTP forms
data and extracts the identifier of the next transaction to be
executed. DFHWBTTA cannot locate a name=value pair in the
HTTP forms data that adheres to the naming convention
DFHWB0133 date time applid tranid Error X'code' occurred defined by CICS to represent the next transaction identifier
during CICS Web 3270 transaction and so it cannot determine which terminal-oriented
processing.{ | TCPIPSERVICE: }tcpipservice transaction to start.
Explanation: Program DFHWBTTA detected an error when System action: DFHWBTTA returns an internal server error
attempting to attach the Web bridge transaction or the Web (HTTP response 500) to the HTTP client.
3270 Bridge exit program DFHWBLT encountered an internal User response: The error code code identifies the CICS trace
error. entry that corresponds to the failure. The HTTP forms data is
System action: The transaction returns an internal server produced as trace data. Collect the CICS trace output.
error (HTTP response 500) to the HTTP client. Examine the HTTP forms data to determine what was
User response: The error code code identifies the CICS trace returned from the web browser. Corruption of the HTTP forms
entry that corresponds to the failure. You may determine the data may be the cause of the problem. You may need further
transaction identifier of the Web bridge transaction from this assistance from IBM to resolve this problem. See Part 4 of the
entry and its significant characteristics. CICS Problem Determination Guide for guidance on how to
proceed.
Collect the CICS trace output. You may need further assistance Destination: CWBO

Module: DFHWBTTA 420C A call to terminate the partnership between this

instance of DFHWBTTA and its associated CWI alias
XMEOUT Parameters: date, time,applid, tranid, X'code', {1=, 2= transaction failed.
TCPIPSERVICE: }, tcpipservice 4213 A call to update the state data for this transaction
failed.
DFHWB0136 date time applid tranid An error code X'code'
has occurred as a result of the Web State The most likely cause of the error is that the timeout interval
Garbage Collection process.{ | for the Web state data has been exceeded, and the relevant
TCPIPSERVICE: }tcpipservice state data has been deleted. Check that the timeout interval for
Explanation: Program DFHWBLT detected an error when the state data is set to a suitable value. You may need further
attempting to access the Web state data held for this assistance from IBM to resolve this problem. See Part 4 of the
transaction. The transaction wait time has exceeded the CICS Problem Determination Guide for guidance on how to
garbage collection limit and the state block has been deleted proceed.
by the garbage collection process. Destination: CWBO
System action: If the error occurs in DFHWBLT, a TERMERR Module: DFHWBTTA
condition is returned to the application and processing
continues. If the error occurs in DFHWBTTA, an error
response is sent to the browser and processing continues.
User response: Use the error code code to determine which
module received the error: DFHWB0150 date time applid tranid The CICS HTML
4108 The error occurred in DFHWBLT. template manager could not locate template
420B The error occurred in DFHWBTTA. template_name in the HTML template data
set.{ | TCPIPSERVICE: }tcpipservice
The cause of the error is that the garbage collection interval Explanation: The CICS HTML template manager DFHWBTL
for the Web state data has been exceeded, and the relevant could not find template name template_name in the HTML data
state data has been deleted. Check that the garbage collection set.
interval for the state data is set to a suitable value. See Part 4 System action: Because 3270 / HTML conversion cannot be
of the CICS Problem Determination Guide for guidance on how performed without the template, CICS returns a TERMERR
to proceed. condition to the application. Message DFHME0116 is normally
Destination: CWBO produced containing the symptom string for this problem.
Modules: DFHWBLT, DFHWBTTA User response: Make sure that the template exists in the
template library. See the CICS External Interfaces Guide for
XMEOUT Parameters: date, time,applid, tranid, X'code', {1=, 2= guidance on how to create HTML templates. Report the details
TCPIPSERVICE: }, tcpipservice of the symptom string given in message DFHME0116.
Destination: CWBO
DFHWB0137 date time applid tranid An error code X'code' Module: DFHWBTC
occurred in DFHWBTTA while accessing the XMEOUT Parameters: date, time,applid, tranid,
Web state data for this transaction.{ | template_name,{1=, 2= TCPIPSERVICE: }, tcpipservice
Explanation: The Web Terminal Translation Application
program, DFHWBTTA, has detected an error when attempting DFHWB0151 date time applid tranid The CICS Web Support
to access the Web state data held for this transaction. 3270 emulation code was unable to process
System action: An exception trace entry is made in the trace the data it was passed.{ | TCPIPSERVICE:
table using code X'code. }tcpipservice
User response: Use the error code code to determine the Explanation: The CICS Web Support routine that converts
reason for the failure: 3270 data streams to HTML, and vice versa, has detected an
4203 Unable to establish a partnership with the associated error. This is probably because it has been passed an invalid
CWI alias transaction. 3270 data stream on an EXEC CICS SEND command, or
4204 Unable to initialize a partnership with the associated because the browser has returned some data that it is
CWI alias transaction. incapable of handling in response to an EXEC CICS RECEIVE
4205 The alias task associated with this instance of command.
DFHWBTTA was not in the required state. System action: The transaction is abended with code AEIP
4206 A call to create the state data for this instance of (INVREQ). There will be subsequent messages from the web
DFHWBTTA failed. state management code as it tidies up for the abending task.
4207 A call to destroy the state data for this instance of Message DFHME0116 is normally produced containing the
DFHWBTTA failed. symptom string for this problem.
4208 A call to retrieve the state data for this instance of User response: Use CEDX or trace to look at the data that
DFHWBTTA failed. was in error and then correct the sending application. Report
4209 A call to break the established partnership between the details of the symptom string given in message
the associated transaction and DFHWBTTA has DFHME0116.
failed. Destination: CWBO
420A A call to reactivate the CWI alias transaction Module: DFHWBTC
associated with this instance of DFHWBTTA failed.
420B A call to wait for the CWI alias transaction
associated with this instance of DFHWBTTA failed.

DFHWB0360 date time applid An attempt to establish DFHWB0362 date time applid CICS Web alias transaction
security for userid userid has failed. tranid could not be started due to an
Transaction tranid cannot be started. SAF unexpected error. Host IP address: hostaddr.
codes are (X'safresp',X'safreas'). ESM codes are Client IP address: clientaddr. TCPIPSERVICE:
(X'esmresp',X'esmreas'). Host IP address: tcpipservice.
hostaddr. Client IP address: clientaddr. Explanation: An attempt was made to start transaction tranid
TCPIPSERVICE: tcpipservice. but the attach failed due to an unexpected error.
Explanation: An attempt was made to establish security for
userid userid but it was rejected by the external security CICS Web attach processing could not start transid tranid
processing due to an unexpected error.
manager (ESM).
System action: The attach for transaction tranid fails, then
In order to start transaction tranid CICS Web attach processing processing continues.
requires security to be established for userid userid, as selected User response: you may need further assistance from IBM to
for this transaction by the Analyzer URM specified for resolve this problem. See Part 4 of the CICS Problem
TCPIPSERVICE tcpipservice Determination Guide for guidance on how to proceed.
System action: Security has not been established for the Destination: CWBO
userid. The attempt to start the transaction has failed. Module: DFHWBXM
safreas) returned by the system authorization facility (SAF), XMEOUT Parameters: date, time,applid, tranid, hostaddr,
clientaddr, tcpipservice
issued by the RACROUTE REQUEST=VERIFY or RACROUTE DFHWB0500I date time applid tranid CICS Web Support
REQUEST=EXTRACT macros. These return codes are enable processing is complete. Host IP
described in the OS/390 MVS Programming: Authorized address: hostaddr.
Assembler Services Guide, and in External Security Interface Explanation: The enable process has completed successfully.
(RACROUTE) Macro Reference for MVS and VM (SC28-1366). System action: Processing continues.
See these manuals for an explanation of the codes. User response: None.
There may be further messages produced by CICS or the Destination: Console and Transient Data Queue CWBO
external security manager (ESM) which provide more Module: DFHWBM
information. XMEOUT Parameters: date, time,applid, tranid, hostaddr
Destination: CWBO
Module: DFHWBXM
XMEOUT Parameters: date, time, applid, userid, tranid, server controller detected an abend ACN1
X'safresp', X'safreas', X'esmresp', X'esmreas', hostaddr, clientaddr, processing a request from client clientaddr.
tcpipservice Host IP address: hostaddr.
Explanation: The HTTP caller detected an error after
DFHWB0361 date time applid An attempt to attach a CICS invoking program DFHCCNV to perform data conversion on
Web alias transaction for userid userid has incoming data.
failed because the user is not authorized to System action: If there is no DFHCNV table defined, the
execute transaction tranid. Host IP address: CICS Web Support cannot perform data conversion on
hostaddr. Client IP address: clientaddr. incoming data. An exception disable of the CICS Web Support
TCPIPSERVICE: tcpipservice. is initiated. Message DFHME0116 is normally produced
Explanation: An attempt was made to start transaction tranid containing the symptom string for this problem.
by userid userid but it was rejected. User response: Ensure that there is a valid DFHCNV table
link-edited into one of the libraries in the DFHRPL library
CICS Web attach processing could not start transid tranid concatenation.
processing because userid userid is not authorized to execute Destination: CWBO
transaction tranid, which was selected for this HTTP Request Module: DFHWBM
by the Analyzer URM specified for TCPIPSERVICE tcpipservice
System action: The attach for transaction tranid fails, then XMEOUT Parameters: date, time,applid, tranid, clientaddr,
processing continues. hostaddr
User response: Either determine why the Analyzer URM
selected transaction tranid, or modify the Analyzer URM to DFHWB0723 date time applid tranid The CICS Web analyzer
select an authorized transaction identifier. program returned an error response. Program
Destination: CWBO name: progname. RESPONSE: response.
Module: DFHWBXM REASON: reason. Host IP address: hostaddr.
XMEOUT Parameters: date, time, applid, userid, tranid, hostaddr, Client IP address: clientaddr.{ |
clientaddr, tcpipservice TCPIPSERVICE: }tcpipservice
Explanation: As part of its normal processing of a request,
CICS Web attach processing invokes the user replaceable
analyzer to tailor the required actions. This program returns
RESPONSE and REASON values. If a CICS supplied sample
analyzer is being used, possible RESPONSE code values are:
0 OK
4 Exception

8 Invalid
DFHWB0725 date time applid tranid CICS Web attach
12. Disaster
processing detected an error linking to the
analyzer user replaceable module progname.
possible REASON code values are: Host IP address: hostaddr. Client IP address:
1 URL of incoming HTTP request is too short clientaddr.{ | TCPIPSERVICE: }tcpipservice
2 No "/" character in the URI of the HTTP request Explanation: An error linking to the Analyzer user
3. There is more data to be received for this request replaceable module forced CICS Web attach processing to
4 Converter program name is less than 1 or greater abandon a client request. If the host IP address and the client
than 8 bytes long IP address are not available when this error occurred, these
5 Alias transaction ID is less than 1 or greater than 4 addresses will be displayed as "UNKNOWN.
bytes long System action: An error response is sent to the client and the
6 Server program name is less than 1 or greater than 8 request is terminated. The tcpipservice remains open but
bytes long unusable.
7 User token passed as query string data on this User response: Ensure that the program specified has been
request is not valid correctly installed and defined to CICS. If the user replaceable
8 URL passed on this request is not valid module (URM) has been set dynamically using CEMT or the
SPI command, then ensure that the module is defined to CICS
Users can also architect their own response and reason code and enabled, or available in the library if autoinstall is active.
values to be returned by the analyzer, but they should use Destination: CWBO
values other than those defined in the CICS supplied Module: DFHWBXN
copybook DFHWBUCD.
XMEOUT Parameters: date, time,applid, tranid, progname,
hostaddr, clientaddr,{1=, 2=TCPIPSERVICE: }, tcpipservice
If the host IP address and the client IP address are not
available when this error occurred, these addresses will be
displayed as "UNKNOWN" in the message. DFHWB0726 date time applid tranid CICS Web attach
System action: An error response is sent to the client and processing cannot link to the analyzer user
processing of the request is terminated. replaceable program. No analyzer specified.
User response: Examine the RESPONSE and REASON code Host IP address: hostaddr. Client IP address:
values in the message to determine the cause of the error. clientaddr.{ | TCPIPSERVICE: }tcpipservice
Destination: CWBO Explanation: CICS Web attach processing cannot invoke the
Module: DFHWBXN analyzer user replaceable module because none was specified
for the TCPIPSERVICE associated with the request being
XMEOUT Parameters: date, time, applid, tranid, progname,
processed. If the host IP address and the client IP address are
response, reason, hostaddr, clientaddr, {1=, 2= TCPIPSERVICE: },
not available when this error occurred, these addresses will be
tcpipservice
displayed as "UNKNOWN.
System action: An error response is sent to the client and the
DFHWB0724 date time applid tranid CICS Web attach request is terminated. Message DFHME0116 is normally
processing detected an error linking to the produced containing the symptom string for this problem.
codepage conversion module DFHCCNV. User response: Use CEMT SET TCPIPSERVICE to specify an
Host IP address: hostaddr. Client IP address: analyzer name on the URM parameter. CEDA can be used to
clientaddr.{ | TCPIPSERVICE: }tcpipservice alter the stored definitions. The URM name for CICS Web
Explanation: An error linking to program DFHCCNV has TCPIPSERVICEs (those TCPIPSERVICEs which have CWXN
forced CICS Web attach processing to abandon a client specified as the transaction ID) MUST specify a valid analyzer
request. If the host IP address and the client IP address are not program name for the URM keyword.
available when this error occurred, these addresses will be Destination: CWBO
displayed as "UNKNOWN. Module: DFHWBXN
System action: A system dump is taken. An error response is
sent to the client and the request is terminated. Message
User response: You may need further assistance from IBM to DFHWB0727 date time applid tranid CICS Web Support
resolve this problem. See Part 4 of the CICS Problem attach processing could not attach the
Determination Guide for guidance on how to proceed. Report requested alias transaction tranid. Userid:
the details of the symptom string given in message userid. Host IP address: hostaddr. Client IP
DFHME0116. address: clientaddr.{ | TCPIPSERVICE:
Destination: CWBO }tcpipservice
Module: DFHWBXN Explanation: Web attach processing could not attach a new
task with the requested alias transaction ID tranid. An error
response is sent to the client and processing of the request is
terminated with abend code AWB2. If the host IP address and
the client IP address are not available when this error
occurred, these addresses will be displayed as "UNKNOWN.
User response: Ensure that the alias transaction ID supplied
by the Analyzer user-replaceable program has been defined to
CICS.
Destination: CWBO

Module: DFHWBXN inferred from the user_data_offset field.

User response: Examine the input HTTP request and reduce
XMEOUT Parameters: date, time,applid, tranid, tranid, userid, the length of the header information to be within the allowed
hostaddr,clientaddr, {1=, 2= TCPIPSERVICE: },tcpipservice limit. See Part 4 of the CICS Problem Determination Guide for
DFHWB0728 date time applid tranid CICS Web attach Destination: CWBO
processing detected a storage error within the Module: DFHWBXN
Web receive module DFHWBSR. Host IP XMEOUT Parameters: date, time,applid, tranid, hostaddr,
address: hostaddr. Client IP address: clientaddr, {1=, 2= TCPIPSERVICE: }, tcpipservice
clientaddr.{ | TCPIPSERVICE: }tcpipservice
Explanation: A storage error in program DFHWBSR has
forced CICS Web attach processing to abandon a client DFHWB0732 date time applid tranid CICS Web attach
request. If the host IP address and the client IP address are not processing encountered a sockets I/O error
available when this error occurred, these addresses will be while receiving a client request. Client IP
displayed as "UNKNOWN." address: clientaddr. Host IP address: hostaddr.{
System action: An error response is sent to the client and the | TCPIPSERVICE: }tcpipservice
request is terminated. Explanation: A sockets I/O error has forced CICS Web
User response: The most probable cause of this error is there processing to abandon a client request. If the host IP address
being insufficient storage to process the client request. This and the client IP address are not available when this error
failure may indicate that you need to increase the size limits of occurred, these addresses will be displayed as "UNKNOWN."
the EDSAs. EDSA storage limits are specified by the EDSALIM System action: The Web error program DFHWBEP is driven,
system initialization parameter. See the CICS System Definition but no error response can be sent to the client. The request is
Guide for more guidance on EDSALIM. terminated.
Destination: CWBO User response: Check for any associated sockets domain
Module: DFHWBXN error messages, which may give more details on the error
which has occurred. The error may have been caused by a
XMEOUT Parameters: date, time,applid, tranid, hostaddr, user terminating their Web Browser before CICS has been able
clientaddr, {1=, 2= TCPIPSERVICE: }, tcpipservice to process the request. If the problem persists, there may be a
problem with the TCP/IP network. See Part 4 of the CICS
DFHWB0730 date time applid tranid CICS Web attach Problem Determination Guide for guidance on how to proceed.
processing encountered an internal error Destination: CWBO
while processing a client request. Client IP Module: DFHWBXN
address: clientaddr Host IP address: hostaddr.{ XMEOUT Parameters: date, time,applid, tranid, clientaddr,
| TCPIPSERVICE: }tcpipservice hostaddr, {1=, 2= TCPIPSERVICE: }, tcpipservice
Explanation: An internal error has forced CICS Web
processing to abandon a client request. If the host IP address
and the client IP address are not available when this error DFHWB1007 applid Initializing CICS Web environment.
occurred, these addresses will be displayed as "UNKNOWN." Explanation: Module DFHWBIP has been invoked to
System action: A system dump is taken. An error response is initialize the CICS Web 3270 environment.
sent to the client and the request is terminated. Message System action: Processing continues.
DFHME0116 is normally produced containing the symptom User response: None.
string for this problem. Destination: Console
User response: You may need further assistance from IBM to Module: DFHWBIP
Determination Guide for guidance on how to proceed. Report
the details of the symptom string given in message
DFHME0116. DFHWB1008 applid CICS Web environment initialization is
Destination: CWBO complete.
Module: DFHWBXN Explanation: The CICS Web 3270 environment has been
XMEOUT Parameters: date, time,applid, tranid, clientaddr, initialized, and it is now ready to process Web-related work.
hostaddr, {1=, 2= TCPIPSERVICE: }, tcpipservice System action: Processing continues.
DFHWB0731 date time applid tranid CICS Web attach Module: DFHWBIP
processing detected an HTTP header longer
than 32767 bytes. Host IP address: hostaddr. XMEOUT Parameter: applid
Client IP address: clientaddr.{ |
TCPIPSERVICE: }tcpipservice DFHWB1009 applid CICS Web environment initialization
Explanation: An HTTP request was being received by failed. Reason Code: X'rc'.
DFHWBSR when it detected that the header data of the Explanation: The CICS Web 3270 environment initialization
request exceeded the currently supported maximum of 32767 failed with reason code rc.
bytes. If the host IP address and the client IP address are not System action: CICS initialization continues. Subsequent calls
available when this error occurred, these addresses will be to the components of the CICS Web environment may fail.
displayed as "UNKNOWN". User response: Use the reason code rc to determine why
System action: Trace entry 0418 is issued containing the web initialization failed. The possible reasons are:
request block. The length of the HTTP header data can be

1 Storage for the Web anchor block could not be access it for the running task. Check that the system
obtained. initialization WEBDELAY parameters are appropriate values.
3 Load for module DFHWBST failed. See the CICS System Definition Guide for guidance on setting
4 Load for module DFHWBTC failed. the values of the Web garbage collection interval and the Web
5 Storage for the State Manager anchor block could terminal timeout interval.
not be obtained. Destination: CWBO
6 The creation of the State Token Directory failed. Module: DFHWBST
7 The subpool required for state management could
XMEOUT Parameters: date, time,applid, stoken, {1=initialize
not be added.
partnership, 2=make partnership, 3=break partnership, 4=trigger
8 The subpool required for HTTP buffers could not be
partner,5=wait for partner, 6=query partner, 7=terminate
added.
partnership}, taskid, X'cuowid', {1=, 2= TCPIPSERVICE: },
9 The addition of the WBST lock failed.
tcpipservice
A Load for module DFHWBIP failed.
Reason codes 1 to 9 originate in DFHWBIP. Reason code A DFHWB1100 E date time applid The CICS Web Support
originates from DFHSIJ1. received data from the user application that
Destination: Console is longer than expected.
Modules: DFHWBIP, DFHSIJ1 Explanation: The environment variables program has
received data from a user application. However, the data
XMEOUT Parameters: applid, X'rc'
received was longer than expected.
System action: Exception trace point 4623 is written. The
DFHWB1020 date time applid CICS Web State Manager environment variables program abnormally terminates with
could not find state data for state token stoken abend code AWB7.
for a {destroy | retrieve | store} request.{ | User response: Examine the data sent to CICS from the
TCPIPSERVICE: }tcpipservice application program.
Explanation: The CICS Web State Manager could not find the Destination: Console Routecodes 2 and 12 and Transient
state data for the state token stoken or the supplied state token Data Queue CWBO
stoken does not exist. Module: DFHWBENV
System action: The requested state data cannot be destroyed,
updated or retrieved by the Web State Manager. An exception
trace entry is made in the trace table.
User response: Ensure that the supplied state token stoken is DFHWB1200 date time applid tranid The CICS Web Support
correct. On a busy CICS region, the most likely cause of this analyzer program set parameter
error is that the state data has been discarded by the Web WBRA_USER_DATA_LENGTH to more than
garbage collection process before the Web state manager could the maximum. Program name: progname.
access it. Check that the system initialization WEBDELAY RESPONSE: response. REASON: reason. Host
parameters are appropriate values. See the CICS System IP address: hostaddr. Client IP address:
Definition Guide for guidance on setting the values of the Web clientaddr. Data offset: X'dataoffset'. Data
garbage collection interval and the Web terminal timeout length: X'datalength'. Buffer length:
interval. X'bufferlength'.{ | TCPIPSERVICE: }tcpipservice
Destination: CWBO Explanation: As part of its normal processing of a request,
Module: DFHWBST Web attach processing invokes the user replaceable analyzer to
tailor the required actions. This program is passed the length
XMEOUT Parameters: date, time,applid, stoken,
of the user data part of the HTTP request in parameter
{1=destroy,2=retrieve, 3=store}, {1=, 2= TCPIPSERVICE: },
WBRA_USER_DATA_LENGTH, which it can modify.
tcpipservice
However, the modified value is greater than the maximum
allowable value which represents the available space in the
DFHWB1021 date time applid CICS Web State Manager data buffer.
could not find state data for state token stoken System action: An error response is sent to the client and
in order to perform the {initialize partnership | processing of the request is terminated.
make partnership |break partnership | trigger User response: Modify the analyzer program so that it does
partner | wait for partner | query partner | not set the parameter WBRA_USER_DATA_LENGTH to be
terminate partnership} request for task number greater than the maximum. The sum of the data offset and the
taskid, CICS unit of work id X'cuowid'.{ | data length should not exceed the buffer length.
TCPIPSERVICE: }tcpipservice Destination: CWBO
Explanation: The CICS Web State Manager could not find the Module: DFHWBXN
state data for the state token stoken because the supplied state
XMEOUT Parameters: date, time, applid, tranid, progname,
token stoken does not exist. The running task is task number
response, reason, hostaddr, clientaddr, X'dataoffset', X'datalength',
taskid and the associated CICS unit of work id is cuowid.
X'bufferlength', {1=, 2=TCPIPSERVICE: }, tcpipservice
System action: The Web State Manager cannot therefore
perform the requested partnership function for the running
task. An exception trace entry is made in the trace table.
User response: Ensure that the supplied state token stoken is
correct. On a busy CICS region, the most likely cause of this
error is that the state data has been discarded by the Web
garbage collection process before the Web State Manager could

DFHWB1525 • DFHXA6526I
DFHWB1525 date time applid tranid The CICS Web Support DFHWB1551 date time applid The CWBC Transaction is no
connection manager received an unexpected longer used to manage CICS Web resources.
response from CICS. Explanation: An attempt has been made to run the
Explanation: The connection manager received an CICS-supplied transaction CWBC. This transaction is no
unexpected response to a CICS command. This is a logic error. longer used to manage CICS Web resources.
System action: A system dump is taken. Processing System action: None. Processing continues.
continues. Message DFHME0116 is normally produced User response: Refer to the CICS Internet and External
containing the symptom string for this problem. Interfaces Guide, and the Resource Definition Guide for details
User response: You may need further assistance from IBM to of how to manage CICS Web resources. See Part 4 of the CICS
resolve this problem. See Part 4 of the CICS Problem Problem Determination Guide for guidance on how to proceed.
Determination Guide for guidance on how to proceed. Report Destination: CWBO and Terminal End User
the details of the symptom string given in message Module: DFHWBC01
DFHME0116.
Destination: CWBO and Terminal End User
Module: DFHWBC01
DFHWKxxxx messages
DFHWK0101 applid Storage manager failure for DWE
Warm Restart.
Explanation: Warm keypoint is processing the saving of DFHWK0103I applid LUC resync required.
deferred work elements (DWEs) for LU6.1 and APPC sessions. Explanation: There are outstanding LUC unit of recovery
The buffer used to write the DWEs to the catalog has failed. descriptors (URDs) that require resynchronization.
The preceding storage (SM) manager domain message System action: CICS shutdown continues.
indicates the cause of the failure. User response: Outstanding resynchronization work was
System action: CICS abends with a system dump. present at shutdown. When CICS restarts, take the appropriate
User response: Refer to the preceding SM domain message action to initiate resynchronization.
for further information and guidance. Module: DFHWKP
Perform an AUTO or COLD CICS restart. XMEOUT Parameter: applid

Module: DFHWKP Destination: Console

Destination: Console DFHWK0104I applid External resource manager resync
required.
Explanation: There are outstanding RMI unit of recovery
DFHWK0102 applid Too large a DWE for warm restart - descriptors (URDs) that require resynchronization.
AUTO START should be performed. System action: CICS shutdown continues.
Explanation: Warm keypoint is processing the saving of User response: Outstanding resynchronization work was
deferred work elements (DWEs) for LU6.1 and APPC sessions. present at shutdown. When CICS restarts, take the appropriate
It has found that a DWE is too large to be saved. action to initiate resynchronization.
Module: DFHWKP
DWEs are saved in the catalog which imposes a maximum
record size constraint. The permitted maximum size is XMEOUT Parameter: applid
specified in the field DWEMAXLN in the DFHDWEDS Destination: Console
DSECT. See the CICS Data Areas for details.
System action: No further DWEs are saved.
DFHWK0105I applid Warm keypoint successful.
The catalog is updated to show that warm keypointing failed. Explanation: Keypointing has been successful.
The next AUTO start is forced to become an EMERGENCY System action: Shutdown continues.
restart. User response: None.
User response: Take the appropriate action for a forthcoming Module: DFHWKP
EMERGENCY restart.
Module: DFHWKP XMEOUT Parameter: applid
DFHXAxxxx messages
DFHXA6521I applid CICS shutdown initiated by CEBT
event
Explanation: This is an informational message issued from
the CICS task. DFHXA6526I applid MESSAGE RECEIVED FOR
System action: CICS terminates normally. UNSUPPORTED QUEUE X'queue'.
User response: None. Explanation: This message is issued from the CAVM task. A
Module: DFHXRCP tracking message has been received for a queue with

DFHXA6528I • DFHXA6561D
hexadecimal name X'queue'. However this queue is not are using the same pair of data sets for XRF surveillance. If
recognized by CICS. they are, this is almost certainly a CICS error affecting either
System action: CICS processing continues, but tracking the alternate system, the active system, or both.
messages for queue X'queue' are ignored.
User response: Check that the active CICS system and the You need further assistance from IBM to resolve this problem.
alternate CICS system are at the same functional level with See Part 4 of the CICS Problem Determination Guide for
respect to XRF. guidance on how to proceed.
Module: DFHWMRD
If both CICS systems are at the same level, check why the Destination: Console
active CICS system has written data to the alternate system.
Ensure that the queue name has not been corrupted.
DFHXA6541I XRF HAS FAILED. THE XRF MESSAGE
Module: DFHXRB
READER IN THE ALTERNATE SYSTEM
HAS FALLEN TOO FAR BEHIND.
Explanation: The alternate system has been unable to keep
DFHXA6528I applid Unable to link to program progname up with the messages generated by the active CICS system. Its
Explanation: This message is issued from the CICS task. read position in the wrap-round message data set has been
CICS is unable to link to program progname. 'lapped' by the active system.
System action: CICS terminates abnormally with a system System action: Surveillance by the alternate system ceases.
dump and abend code 0210. User response: Try to determine and correct the reason for
User response: Examine the dump to determine why CICS the delay to the alternate system. It may be that the message
was unable to link to program progname. data set is too small to allow adequate buffering, or the
Ensure that the named program is contained in a sublibrary of message data set has been reserved by the active CPC – not
the LIBDEF search chain for the CICS startup job stream. If necessarily by the active CICS.
progname is missing, obtain a copy of the program and include Module: DFHWMRD
it in the library. In addition, ensure that enough storage is Destination: Console
available for the dynamic storage areas.
Module: DFHXRE
DFHXA6560A applid TERMINATION COMMAND FAILED:
XMEOUT Parameters: applid, progname command.
Destination: Console Explanation: The command issued by the alternate CICS
during takeover to terminate the active CICS failed. VSE
rejected the system operator command command issued under
DFHXA6530 applid START=STANDBY specified. CICS program control as being invalid.
start-up is terminated because XRF=NO is
System action: Message DFHXA6581 or DFHXA6582 is also
specified
displayed. The alternate CICS continues with its processing to
Explanation: START=STANDBY and XRF=NO cannot be
detect termination of the active CICS job.
specified together.
User response: Ensure that the active CICS job terminates.
User response: Correct the conflicting values of the operands See messages DFHXA6581 and DFHXA6582. For problem
START and XRF. determination, hard copy of the console log may be required.
Module: DFHSIC1 Module: DFHWTI
DFHXA6561D applid WHEN ACTIVE JOB
'powerjobname,powerno' ENDS REPLY 'JOB' OR
DFHXA6540I XRF HAS FAILED. ERROR NUMBER nn ON WHEN CPC 'powersysid' HAS FAILED REPLY
XRF MESSAGE DATA SET IN CONTROL 'CPC'.
INTERVAL WITH RBA HEX'xx'. Explanation: During a takeover attempt, the issuing CICS
Explanation: The XRF message manager has encountered a system was unable to determine whether job powerjobname,
problem with the contents of the given control interval in the
running on a different CPC, has terminated. This is for one of
message data set. The message includes an error number nn
the following reasons:
which can take one of the following values:
v CICS was unable to issue a system operator command
01 The CI does not contain an XRF message manager
under program control to cancel the named job. In this case,
control record.
message DFHXA6560, DFHXA6569 or DFHXA6570 has been
02 The XRF message control record contains a cycle
produced.
number less than that of the current read cycle.
v CICS has successfully issued a cancel command but the job
03 The XRF message manager did not find a message
still appears to be running after the time period specified by
record boundary where it expected one.
the initialization parameter XRFTODI.
04 There is an XRF message sequence number error.
05 The CIDF is invalid (for example, the free area
length is negative). If powerjobname is the active CICS. Takeover cannot continue
06 The length in the RDF is less than the length of a until powerjobname has ended.
message record header, or is inconsistent with the System action: The system waits for a reply. In the
data length in the message record header. meanwhile, the issuing CICS system continues processing to
07 The end of the record lies outside the data area detect termination of the job.
defined by the data length field of the CIDF. If termination is detected while the reply is still outstanding,
System action: Surveillance by the alternate system ceases. this message is deleted and message DFHXA6564 is displayed.
User response: Check that the active and alternate systems In this case, a reply is no longer required.

DFHXA6562D • DFHXA6572I
If the reply is 'JOB', then processing continues as if CICS had System action: The alternate CICS continues with its
detected the termination itself. takeover processing.
This also happens if the reply is 'CPC', but in addition an Module: DFHWTI
internal record is created indicating that the CPC is Destination: Console
inoperative at this time. Other alternate CICS which have
issued this message for jobs executing on the CPC specified,
and which are still waiting for a reply, will detect the internal DFHXA6564I applid TERMINATION OF ACTIVE JOB
record of the failed CPC. Having done so they delete their 'powerjobname,powerno' DETECTED.
outstanding replies and issue message DFHXA6563. Explanation: During takeover, the alternate CICS has
User response: The operator should either:- detected that the active CICS job with specified POWER job
v Ensure that job powerjobname with POWER job number name and POWER job number has ended.
powerno terminates, and then reply 'JOB', or System action: The alternate CICS continues with its
v Ensure that the CPC with VSE system identifier powersysid takeover processing.
is inoperative at this time, for example by selecting SYSTEM User response: None.
RESET on that CPC, and then reply 'CPC'. Module: DFHWTI
No action is necessary if at any time CICS deletes this
message, as described above.
Module: DFHWTI DFHXA6566I applid modname NOT LINK-EDITED
Destination: Console REENTERABLE.
Explanation: Module modname, the CLT currently in use, was
found not to have been link-edited with the SVA attribute.
DFHXA6562D applid WHEN ACTIVE JOB
'powerjobname,powerno' ENDS REPLY 'GO.' The system initialization option CLT=xx specifies the suffix of
Explanation: Takeover by the alternate CICS cannot proceed the CLT currently in use by this alternate CICS.
for one of the following reasons: System action: Further messages are issued which describe
1. The alternate CICS issued a system operator command the action taken by CICS.
under program control to terminate the active CICS job but User response: The appropriate response is indicated by
it failed. Message DFHXA6560 was produced. subsequent messages.
2. Having issued a system operator command under program Module: DFHWTI
control to terminate the active CICS job, the time taken for Destination: Console
the active CICS job to terminate has exceeded the period
specified by the system initialization parameter XRFTODI.
DFHXA6567I applid APPLID applid2 NOT FOUND IN
modname.
The active CICS job was started on the same processor as the
Explanation: Module modname, the CLT currently in use by
alternate CICS.
this alternate CICS, was found not to contain the APPLID
applid2.
Takeover cannot continue until the active CICS job with the System action: Further messages are issued which describe
specified POWER job name and POWER job number has the action taken by CICS.
ended. User response: The appropriate response is indicated by
System action: The alternate CICS waits for a reply but subsequent messages.
continues with its processing to detect termination of the Module: DFHWTI
active CICS job. If termination of the active CICS job occurs Destination: Console
while a reply to this message is outstanding, this message is
deleted, message DFHXA6564 is displayed and takeover
continues. No reply is required. If reply GO is entered, DFHXA6568I applid JOBNAME jobname NOT FOUND IN
takeover continues. modname.
User response: If termination of the specified job occurs Explanation: The CLT was found not to contain the job name
while this reply is outstanding, the message is deleted and no jobname associated with the APPLID of this alternate CICS.
action by the system operator is required. In this case message
DFHXA6564 is displayed. Ensure the active CICS job with the jobname is the job name which the alternate CICS would have
specified job name and POWER job number terminates. When used to cancel the active CICS job during a takeover
termination has occurred, reply GO if message DFHXA6564 is System action: Further messages are issued which describe
not displayed. the action taken by CICS.
Module: DFHWTI User response: The appropriate response is indicated by
Destination: Console subsequent messages.
Module: DFHWTI
DFHXA6563I applid ACTIVE JOB 'powerjobname,powerno'
ENDED DUE TO FAILURE OF CPC
'powersysid'. DFHXA6572I applid UNABLE TO LOAD modname.
Explanation: During takeover, the alternate CICS has Explanation: The module modname, defined by the CLT for
detected that the CPC with VSE system identifier powersysid use by the alternate CICS that issued this message, cannot be
has failed and therefore that the active CICS job with job name loaded.
powerjobname and POWER job number powerno is regarded to System action: Further messages are issued by the alternate
have ended. CICS to describe the action taken.

DFHXA6573I • DFHXA6577D
User response: The appropriate response is indicated by or because job powerjobname cannot be found:
subsequent messages. v In the CLT, for an active CICS, or
Module: DFHWTI v Because the CLT is invalid.
Further messages specify the error with the CLT, or define
why the CLT is invalid.
DFHXA6573I applid LOAD MODULE modname IS NOT
VALID. In addition, takeover by the alternate CICS cannot proceed for
Explanation: Module modname, the CLT defined for use by one of the following reasons:
this CICS system, is not valid. 1. The alternate CICS cannot construct a suitable system
System action: Further messages are issued by the alternate operator command to terminate the CICS active due to
CICS to describe the action taken. missing information in the CLT currently in use. A
User response: The appropriate response is indicated by previous message specifying the CLT error has been
subsequent messages. issued.
Module: DFHWTI 2. The alternate CICS issued a system operator command
Destination: Console under program control to terminate the active CICS job but
it failed. Message DFHXA6560 was produced.
3. Having issued a system operator command under program
DFHXA6574I applid ERROR FOUND WITH DFHCLTxx. control to terminate the active CICS job, the time taken for
Explanation: The alternate CICS that issued this message is the active CICS job to terminate has exceeded the period
unable to load a CLT, or has performed a check on the CLT specified by the system initialization parameter XRFTODI.
contents and has found an error. If the specified CLT is used
during a future takeover, the takeover might not be successful.
The active CICS job was started on a different processor from
A new or corrected CLT can be made available and loaded at
that of the CICS alternate. Takeover cannot continue until:
takeover.
1. The active CICS job with POWER job name powerjobname
and POWER job number powerno has ended.
User response: Verify that the alternate CICS job is
2. The processor with the POWER system identifier
authorized to perform a takeover of the active CICS. Take
powersysid is inoperative.
appropriate action if not.
System action: The issuing CICS system cannot issue a
Locate the previous message issued by this alternate CICS, CANCEL, but attempts to alert the active CICS system to the
which provides details of the CLT error. takeover request via the XRF control data set. In most cases
this causes the active system to initiate termination.
Perform the appropriate source edit, assembly and link-edit
tasks necessary to make a correct CLT available for this The alternate CICS waits for a reply but continues with its
alternate CICS. processing to detect termination of the active CICS job.
Module: DFHWTI
If termination of the active CICS job occurs while a reply to
this message is outstanding, this message is deleted, message
DFHXA6564 is displayed and takeover continues. No reply is
DFHXA6576I applid CLT PROCESSING NOT POSSIBLE required.
OWING TO ERROR IN DFHCLTxx.
If reply JOB is entered, takeover continues.
Explanation: During takeover, the alternate CICS that issued
this message performed a check on the CLT contents and If reply CPC is entered, takeover continues but also an
found an error. internal record is created indicating that the processor is
inoperative at this time. Other alternate CICS systems that
A previous message specifies the error.
have issued this message and are waiting for a reply, and
System action: Commands in the CLT are not issued by this
whose active CICS jobs were executing on the processor
alternate CICS. Other takeover processing continues.
specified, detect the internal record of the failed processor.
User response: Verify that the alternate CICS job is
Having done so they delete the outstanding reply, issue
authorized to perform a takeover of the active CICS and take
message DFHXA6563 and continue with their takeover.
appropriate action if it is not.
User response: Verify the alternate CICS job is authorized to
If the takeover is to be successful, the system operator should perform a takeover of the active CICS and take appropriate
monitor and coordinate execution of the active CICS and action if not. If termination of the specified job occurs while
alternate CICS jobs in the XRF complex. this reply is outstanding, the message is deleted and no action
by the system operator is required. In this case message
Perform the source edit, assembly and link-edit tasks DFHXA6564 is displayed.
necessary to correct the CLT.
Module: DFHWTI If there are no other alternate CICS systems performing a
Destination: Console takeover:
1. Ensure the active CICS job with the specified job name and
POWER job number terminates. This must be done before
DFHXA6577D applid NOT AUTHORIZED TO CANCEL the next step.
'powerjobname,powerno' ON CPC 'powersysid'. IF 2. When termination has occurred reply JOB if message
OK AND ENDED, RELPY 'JOB' OR 'CPC'. DFHXA6564 is not displayed.
Explanation: The issuing alternate CICS is attempting a
takeover of the specified active CICS job. It has been unable to With more than one alternate CICS performing a takeover
find the data that is needed to fully authorize takeover in the
either respond as described above for each DFHXA6561
CLT. This may be because the alternate cannot load the table, message or:

DFHXA6578D • DFHXA6580I
1. Ensure the processor with the specified POWER system Perform the appropriate source edit, assembly, and link-edit
identifier (powersysid) is inoperative at this time. For tasks necessary to correct the CLT.
example, the system operator may choose to select System Module: DFHWTI
Reset on the processor concerned. This must be done Destination: Console
before the next step.
2. Reply CPC.
DFHXA6580I PROGRAM LOGIC ERROR DETECTED.
Explanation: An internal error has been detected that
Perform the appropriate source edit, assembly and link-edit
prevents the CICS XRF CAVM processing from continuing.
tasks necessary to correct the CLT.
Module: DFHWTI Depending on the CAVM service being processed at the time,
Destination: Console CICS may or may not abnormally terminate.
The CAVM task for processing the service has abnormally
DFHXA6578D applid NOT AUTHORIZED TO CANCEL terminated.
'powerjobname,powerno'. IF OK AND ENDED,
REPLY 'GO'. Diagnostics: Register 2 is the base register for DFHWTI global
Explanation: The issuing alternate CICS is attempting a storage. This storage begins with the eye catcher WTISTOR.
takeover of the specified active CICS job but the CLT in use The format of this storage is defined in DSECT WSTORAGE
does not have the necessary contents to fully authorize in source member DFHWTI.
takeover. This may be because the alternate cannot load the DFHWTI request arguments copied to global storage begin at
table, or because job powerjobname cannot be found: field WGLODATA.
v In the CLT, for an active CICS, or
v Because the CLT is invalid. Source member DFHWTADS defines the format of global
storage arguments.
Further messages specify the error with the CLT , or define
why the CLT is invalid. Field WGLOLOCA contains the address of the first register
save area for a routine in DFHWTI.
In addition, takeover by the alternate CICS cannot proceed for Register 4 is the base register for local storage for each routine
one of the following reasons: in DFHWTI. Its format is defined in a DSECT whose name is
1. The alternate CICS issued a system operator command of the form WLOCxxx where xxx is the short name of the
under program control to terminate the active CICS job but routine (see below for a list of routine names).
it failed. Message DFHXA6560 was produced.
2. Having issued a system operator command under program These DSECTs are in source member DFHWTI. The first
control to terminate the active CICS job, the time taken for halfword is the internal return code for the routine. The values
the active CICS job to terminate has exceeded the period used for internal return codes are the same as the DFHWTI
specified by the system initialization parameter XRFTODI. request reason codes as defined by field WTARRC in the
PRD1.BASE source member DFHWTADS.
The active CICS job was started on the same processor as the In addition, internal return codes of the format X'40nn' are
alternate CICS. used. X'40F0' is 'Internal Logic Error' variable name,
RCLOGERR.
Takeover cannot continue until the active CICS job with the
POWER job name powerjobname and POWER job number Other internal return codes of this format are defined in the
powerno has ended. local storage DSECTs.
System action: The issuing CICS system cannot issue a The DFHWTI request type for the CAVM supervisor state
CANCEL, but attempts to alert the active CICS system to the service is copied into local storage associated with the
takeover request via the XRF control data set. In most cases DFHWTI initialization and termination routine, field name
this causes the active system to initiate termination. WWTIREQ, DSECT WLOCWTI in source member DFHWTI.
The alternate CICS waits for a reply but continues with its Register 6 is the base register for each routine in DFHWTI.
processing to detect termination of the active CICS job. When set, it points at a location immediately following an eye
If termination of the active CICS job occurs while a reply to catcher of the routine's long name (see list of routine names).
this message is outstanding, this message is deleted, message Register 13 is the base register for a register save area local to
DFHXA6564 is displayed and takeover continues. No reply is a routine in DFHWTI. These save areas are standard VSE
required. format except the first fullword contains the routine's short
If you reply GO, takeover continues. name (see list of names). They are chained in the standard
User response: Verify the alternate CICS job is authorized to way with backward and forward pointers set on entry to a
perform a takeover of the active CICS and take appropriate routine and zeroed on return.
action if not. Register save areas physically precede the storage local to a
If termination of the specified job occurs while this reply is routine.
outstanding, the message is deleted and no action by the If a routine has to access the CLT, its address is in local
system operator is required. In this case message DFHXA6564 storage for the routine. The field name for the CLT address is
is displayed. of the form WxxxCLTA, where xxx is the short name of the
Ensure the active CICS job with the specified job name and routine.
POWER job number terminates. When termination has System action: In general, the CAVM request issued by this
occurred reply GO if message DFHXA6564 is not displayed. CICS job will fail. For the effect this has on processing by this

DFHXA6581I • DFHXA6583I
CICS job, refer to messages issued after this one.

DFHXA6581I applid FAILED IN XPCC-IDENT OR
CAVM XRF supervisor state processing issues a VSE abend CONNECT. R15=X'r15', IJBXRETC=X'retcode'.
with system abend code 0214 and a VSE SDUMP dump is Explanation: The alternate CICS failed in an attempt to
produced. establish a cross-partition connection to VSE/POWER, the
User response: Keep the job output and console log for operating system spooler. r15 is the contents of register 15.
problem determination. retcode is the return code from the VSE XPCC macro.
System action: Usually, the CAVM request issued by this
Using the SDUMP find the DFHWTI routine that detected the CICS XRF job will fail. For effect on processing by this CICS
error from the value of register 6 or register save area chain XRF job, see later messages.
fields. User response: For the meaning of the return code and
Find the internal return code currently set in local storage for register 15 contents, refer to the VSE/POWER Application
the routine. Programming manual. The failure can arise for one of the
following reasons:
Using the reason code value, remaining content of local v POWER was not started for the systems.
storage and global storage, try to determine the cause of the v POWER had not yet connected to VSE.
action by the routine. v VSE lacks storage to set up control blocks.
v There is an internal error in CICS.
An assembly listing of the CLT assembled with the PRINT
NOGEN option may be required.
If, after checking the return codes and any other messages
Routine names Long names are used for: received, you still cannot solve the problem, you may need
v The routine entry point name, and further assistance from IBM to fully resolve this problem. See
v The routine entry eye catcher. Part 4 of the CICS Problem Determination Guide for guidance on
how to proceed.
Short names are used for:
Module: DFHWTI
v The routine register save area eye catcher,
v Characters 2 to 4 of routine local storage field names,
v Characters 5 to 7 of routine local storage DSECT names, and
v Characters 1 to 3 of routine labels. DFHXA6582I applid UNEXPECTED OUTCOME OF
XPCC-SENDR R15=X'r15',
Routines are as follows:
IJBXRETC=X'retcode',
Long Name PXPFBKCD=X'powercode'.
Short Name Explanation: The alternate CICS sent a DISPLAY command
TIPENTRY to the VSE spooler POWER, requesting information about the
TIP active job. The request failed. r15 is the contents of register 15.
OATERM retcode is the return code from the VSE macro, XPCC.
OAT powercode is the POWER feedback code in field PXPFBKCD.
OAWAIT System action: The CICS XRF job is canceled.
OAW User response: This error should not occur, and implies
VERCLT either a mis-formatting of the call, or a fault in POWER or
VCL XPCC. For the meaning of the return code and register 15
CLPENTRY contents, refer to the VSE/POWER Application Programming
CLE manual.
CLPROC
You will need further assistance from IBM to resolve this
CLP
OPCLT OCL
CHECKT
Module: DFHWTI
CHT
OPCDATA
OPC
INQPWR DFHXA6583I applid CANNOT LOCATE DFHCDDAN IN
IPW SVA.
MUVENTRY Explanation: CICS tried to access information that is shared
MUV by other CICS systems in the same CPC. The attempt failed,
1. Module entry point with standard DFHVM fields. because the module DFHCDDAN, which serves as an anchor
2. Subtask with start of module as entry point and using in the SVA for shared data, either could not be loaded or was
SIJSTOR for local storage. found to be in nonshared storage.
For further guidance in error diagnosis, see the CICS Problem System action: CICS continues to run. This, or any
Determination Guide. subsequent, inquiry on the shared data is treated as a case of
Module: DFHWTI "nothing found".
Destination: Console User response: The error implies an error in system setup.
Ensure that DFHCDDAN is present and defined as an
SVA-eligible module. If that does not cure the fault, you will
need assistance from IBM to resolve the problem. See Part 4 of
the CICS Problem Determination Guide for guidance on how to
proceed.
Module: DFHWTI

DFHXA6599I • DFHXC6606I
Destination: Console User response: Increase the amount of partition GETVIS

available above the 16MB line by either increasing the size of
the CICS partition or reducing the size specified on the
DFHXA6599I applid STATE CHANGE WORK ELEMENT EDSALIM system initialization parameter for the CICS job.
GETVIS FAILURE Module: DFHXRB
Explanation: A GETVIS request issued by the CAVM for Destination: Console
work element storage above the 16MB line has failed.
DFHXCxxxx messages
v SIGNON found that one of the CAVM data sets had already
DFHXC6455I SVC GETVIS FAILED IN XRF SIGNOFF
been formatted by a different CICS job but that the other
Explanation: An SVC storage request issued by the CAVM
signoff component has failed. was either empty or could not be opened because of conflict
System action: CICS is abnormally terminated. with another user of the data set. SIGNON waited for the
User response: If the available GETVIS is exhausted, either other CICS job to finish the data set formatting, but 5
increase the size of the partition or reduce the value of the minutes later, this still had not been done. This might occur
EDSALIM system initialization parameter. if a CICS job failed during data set formatting. A specific
error reported in a previous message prevented successful
If this is not the case, the problem is probabaly due to a CICS completion of data set initialization.
logic error and you will need assistance from IBM to resolve System action: See the following message issued by this
the problem. See Part 4 of the CICS Problem Determination CICS job.
Guide for guidance on how to proceed. User response: Correct the JCL or redefine the CAVM data
Module: DFHWSSOF sets if necessary and resubmit the CICS job. See the CICS
Problem Determination Guide for information on CAVM data
sets.
DFHXC6456I SVC GETVIS FAILED IN XRF SIGNON Module: DFHWSSN3
Explanation: An SVC storage request issued by the CAVM Destination: Console
signon component has failed.
System action: CICS is abnormally terminated.
User response: If the available GETVIS is exhausted, either DFHXC6603I applid CAVM DATA SET dsname IS INVALID.
increase the size of the partition or reduce the value of the Explanation: The CICS job issued a SIGNON to the CAVM.
EDSALIM system initialization parameter. The CAVM is attempting to open the CAVM data sets, but the
error condition described in the message text has been
If this is not the case, the problem is probabaly due to a CICS detected.
logic error and you will need assistance from IBM to resolve System action: See the following message issued by this
the problem. See Part 4 of the CICS Problem Determination CICS job.
Guide for guidance on how to proceed. User response: See message DFHXC6600
Module: DFHWSSN2 Module: DFHWSSN3
DFHXC6457I SVC GETVIS FAILED IN XRF SIGNON

DFHXC6604I applid CAVM DATA SET dsname MUST BE A
Explanation: An SVC storage request issued by the CAVM
VSAM ESDS.
signon component has failed.
Explanation: The CICS job issued a SIGNON to the CAVM.
System action: CICS is abnormally terminated.
User response: If the available GETVIS is exhausted, either The CAVM is attempting to open the CAVM data sets, but the
increase the size of the partition or reduce the value of the error condition described in the message text has been
EDSALIM system initialization parameter. detected.
System action: See the following message issued by this
If this is not the case, the problem is probabaly due to a CICS CICS job.
logic error and you will need assistance from IBM to resolve User response: See message DFHXC6600
the problem. See Part 4 of the CICS Problem Determination Module: DFHWSSN3
Guide for guidance on how to proceed. Destination: Console
Module: DFHWSSN3
DFHXC6605I applid CI SIZE OF PAIRED CAVM DATA
SETS MUST BE EQUAL.
DFHXC6600I applid CAVM DATA SET INITIALIZATION
FAILED.
The CAVM is attempting to open the CAVM data sets, but the
Explanation: The CICS job attempted to sign on to the
error condition described in the message text has been
CAVM but the signon request failed because the CAVM data
detected.
sets could not be initialized properly. This is due to one of the
following: System action: See the following message issued by this
v The data set formatting subtask had not completed its CICS job.
processing in 2 minutes. This might occur if LOCK's issued User response: See message DFHXC6600
by jobs (not necessarily CICS) running in other CPC's cause Module: DFHWSSN3
a CAVM data set's DASD volume or a VSAM catalogue to Destination: Console
remain inaccessible for a protracted period.
DFHXC6606I applid CI SIZE OF CAVM DATA SET dsname

DFHXC6608I • DFHXC6621I
MUST BE AT LEAST 4K. first time as a pair by a single CICS job.

Explanation: The CICS job issued a SIGNON to the CAVM. System action: See the following message issued by this
The CAVM is attempting to open the CAVM data sets, but the CICS job.
error condition described in the message text has been User response: See message DFHXC6600
detected. Module: DFHWSSN3
System action: See the following message issued by this Destination: Console
CICS job.
User response: See message DFHXC6600
Module: DFHWSSN3 DFHXC6618I applid SPACE ALLOCATED TO CAVM DATA
Destination: Console SET dsname IS INADEQUATE.
Explanation: The CICS job which issued this message issued
a SIGNON to the CAVM. The CAVM is attempting to format
DFHXC6608I applid I/O ERROR ACCESSING CAVM the CAVM data sets, but the error condition described in the
DATA SET dsname DURING SIGNON. message text has been detected.
Explanation: The CICS job issued a SIGNON to the CAVM. System action: See the following message issued by this
The CAVM is attempting to access the CAVM data sets, but CICS job.
the error condition described in the message text has been User response: See message DFHXC6600
detected. Module: DFHWSSN3
CICS job.
Module: DFHWSSN3 DFHXC6620I applid SIGNON IS WAITING TO LOCK OR
Destination: Console ACCESS A CAVM DATA SET.
Explanation: The CICS job that displayed this message issued
a sign on to the CAVM. CAVM is attempting to LOCK the
DFHXC6609I applid CAVM DATA SET dsname IS OF THE CAVM control data set or access either the control or the
WRONG TYPE OR ITS FORMAT IS message data set, but for some considerable time either the
INCOMPATIBLE WITH THIS CODE LEVEL. required resource has remained unavailable or an outstanding
Explanation: The CICS job that displayed this message issued I/O request has not completed. The LOCK attempt should not
a SIGNON to the CAVM. However, the CAVM found that the fail unless another CICS job using the same CAVM data set
information in the data set's control record either did not and executing a sign on, sign-off or takeover request has been
agree with its intended use or had been placed there by an held up, possibly by I/O delays, after issuing a successful
incompatible level of CAVM code. This occurs if: LOCK.
v The data set with dlblname DFHXCTL is not empty and has System action: After a short delay, the CICS job that
already been used for something other than a CAVM displayed this message either reissues the LOCK macro or
control data set or by an incompatible level of CAVM code. checks for completion of the outstanding I/O. If the required
v The data set with dlblname DFHXMSG is not empty and resource is now available or the I/O request has completed,
has already been used for something other than a CAVM normal processing continues. Otherwise, this message is
message data set or by an incompatible level of CAVM reissued.
code. User response: If the cause is a failed processor, issue the
System action: See the following message issued by this VSE command UNLOCK The format of the UNLOCK
CICS job. command is:
User response: See message DFHXC6600 UNLOCK SYSTEM=sysid
Module: DFHWSSN3
where sysid is the processor ID of the inoperative processor.
Module: DFHWSSN2
DFHXC6610I applid CAVM DATA SET dsname DOES NOT Destination: Console
BELONG TO THE GENERIC APPLID
SPECIFIED AT SIGNON.
DFHXC6621I applid CAVM SIGNON CANNOT PROCEED
BECAUSE POWER IS EITHER NOT
However, the CAVM found that the generic APPLID specified
RUNNING OR NOT RESPONDING TO JOB
in the sign on request did not match that saved in the CAVM
STATUS ENQUIRIES.
data set's control record when the data set was first formatted.
Explanation: The CICS job that displayed this message issued
a sign on to the CAVM. To process the request, CAVM needs
CICS job.
to know the status of a job identified by an entry in the
control data set, but cannot obtain this information for the
Module: DFHWSSN3
reason given in the message text.
System action: After a one minute delay, the CICS job that
displayed this message reissues the failing job status enquiry.
DFHXC6611I applid CAVM DATA SETS DO NOT FORM A If the request is completed successfully this time, normal
VALID PAIR. processing continues. Otherwise, this message is reissued.
Explanation: The CICS job that displayed this message issued User response: If POWER is not running, restart it if
a SIGNON to the CAVM. However, the CAVM found that the possible. Otherwise, if the condition persists, try to correct the
time stamps that were placed in the control records of the two problem that is preventing job status enquiries from being
data sets when they were first formatted do not match. This answered. In some cases, just stopping POWER and restarting
will occur unless the two CAVM data sets were used for the it again may achieve the desired effect.
Module: DFHWSSN2

DFHXC6626D applid POSSIBLE CAVM SIGNON
CONFLICT. IS JOB powerjobname, powerno
DFHXC6622I applid ERROR IN INQUIRE HEALTH EXIT RUNNING ON SYSTEM powersysid? REPLY
DURING SIGNON. 'YES' OR 'NO'.
Explanation: The CICS job that displayed this message issued Explanation: The CICS job which issued this message issued
a SIGNON to the CAVM, but the return code passed back to a SIGNON to the CAVM but the CAVM needs the operator's
CAVM by the INQUIRE HEALTH exit (DFHXRC) when it was help in order to decide whether it is safe to accept the request.
called during sign on processing was nonzero. This message The CAVM has found that the control data set refers to a job
always indicates an internal error in CAVM or CICS. satisfying all the following conditions:
System action: CAVM SIGNON continues but XRF function v POWER believes that this job is still executing.
is probably degraded. v If POWER is right, the current sign on request must be
User response: Inform your installation's system rejected because the presence of this job would conflict with
programmer. it.
Module: DFHWSSN2 v This job is not running in the same CPC as the CICS job
Destination: Console which is attempting to sign on.
v This job's surveillance signals appear to be absent.
DFHXC6623I applid CAVM SIGNON IMPOSSIBLE AT Such a situation might have arisen as a result of a failure of
PRESENT BECAUSE ANOTHER JOB HAS the CPC in which the conflicting job was running and if so,
SIGNED ON WITH THE SAME SPECIFIC the CAVM should not reject the sign on request unless it finds
APPLID. another reason for doing so. If the job which displayed this
Explanation: The CICS job which issued this message issued message is a CICS active, the conflicting job is another active
a SIGNON to the CAVM, but the request cannot be accepted or an alternate which has started a takeover. If the job which
because the error condition described in the message text has displayed this message is a CICS alternate, the conflicting job
been detected. is another alternate. The POWER jobname, job identifier and
System action: See the following message issued by this system identifier of the conflicting job are specified in the
CICS job. message text.
User response: None unless the wrong specific applid has System action: The CICS job waits for a reply.
been requested for the new job or the conflicting job was User response: If the job which displayed this message is a
started by mistake. If so, resubmit the failing CICS job with CICS active job, reply NO only if:
appropriate corrections or after canceling the conflicting job. 1. You are certain that the job referred to in the message text
Module: DFHWSSN2 is not executing. It might be necessary to perform a System
Destination: Console Reset of the CPC where it was running to guarantee this.
AND
DFHXC6624I applid CAVM SIGN ON ABANDONED 2. The job which issued this message ought to continue with
BECAUSE THIS PARTITION IS NOT its CAVM sign on request and become the CICS active job.
RUNNING UNDER POWER
Otherwise reply YES.
Explanation: This is an informatory message issued by the
CAVM task, while attempting to sign on to the partition. It
indicates that CICS has been wrongly set up, because the If the job which displayed this message is a CICS alternate job,
correct operation of any later takeover would need the reply NO only if:
partition to be under the control of POWER. 1. You are certain that the job referred to in the message text
System action: CICS abandons the initialization. See later is not executing. It might be necessary to perform a system
message(s). reset of the CPC where it was running to guarantee this.
User response: Correct the setup. AND
Module: DFHWSSN2 2. The job which issued this message ought to continue with
Destination: Console its CAVM sign on request and become the CICS alternate
job.
DFHXC6625I applid CAVM SIGNON IMPOSSIBLE Otherwise reply YES.

BECAUSE CAVM DATA SETS ARE Module: DFHWSSN2
UNUSABLE. Destination: Console
a SIGNON to the CAVM, but the request cannot be accepted
DFHXC6627I applid CAVM SIGNON IMPOSSIBLE
because the error condition described in the message text has
BECAUSE THIS JOB IS CURRENTLY
been detected.
SIGNED ON OR WAS ONCE AN ACTIVE
SYSTEM.
CICS job.
a SIGNON to the CAVM, but the request cannot be accepted
Module: DFHWSSN2
because the error condition described in the message text has
been detected.
CICS job.
User response: This message indicates an internal error has
occurred.
Module: DFHWSSN2

DFHXC6632I applid NON PRE-EMPTIVE TAKEOVER
REJECTED BECAUSE LATEST ACTIVE
DFHXC6628I applid CAVM SIGNON IMPOSSIBLE AT VERSION NUMBER DOES NOT MATCH
PRESENT BECAUSE CONFLICTING JOB(S) THAT SPECIFIED.
HAVE NOT YET SIGNED OFF OR Explanation: The CICS job which issued this message issued
TERMINATED. a takeover request to the CAVM but the request has been
Explanation: The CICS job which issued this message issued rejected due to the error condition described in the message
a SIGNON to the CAVM, but the request cannot be accepted text.
because the error condition described in the message text has System action: See the following message issued by this
been detected. CICS job.
System action: See the following message issued by this User response: None
CICS job. Module: DFHWSTKV
User response: None unless the wrong START option has Destination: Console
been requested for the new job or the conflicting job(s) were
started by mistake. If so, resubmit the failing CICS job with
DFHXC6633I applid NON PRE-EMPTIVE TAKEOVER
appropriate corrections or after canceling the conflicting job(s).
REJECTED BECAUSE A TAKEOVER IS
Module: DFHWSSN2
ALREADY IN PROGRESS.
a takeover request to the CAVM but the request has been
DFHXC6629I applid CAVM SIGNON IMPOSSIBLE rejected due to the error condition described in the message
BECAUSE REQUESTING JOB AND text.
SIGNED-ON JOB(S) DO NOT SHARE System action: See the following message issued by this
POWER. CICS job.
Explanation: The CICS job which issued this message issued User response: None
a sign on to the CAVM, but the request cannot be accepted Module: DFHWSTKV
because the error condition described in the message text has Destination: Console
been detected.
DFHXC6634I applid TAKEOVER REJECTED BECAUSE
CICS job.
NECESSARY TOD CLOCK DIFFERENCE
User response: Resubmit the failing job and any that had to
INFORMATION IS NOT AVAILABLE.
be canceled, ensuring that the job names are unique.
Module: DFHWSSN2
a takeover request to the CAVM but the request has been
rejected due to the error condition described in the message
text. This error cannot occur unless both the following
DFHXC6630I applid TAKEOVER REJECTED BECAUSE conditions are satisfied:
LAST ACTIVE SIGNED OFF NORMALLY. v The CICS active and alternate jobs are running in different
Explanation: The CICS job that issued this message issued a CPCs.
takeover request to the CAVM but the request has been v A TAKEOVER has been attempted before the alternate job
rejected due to the error condition described in the message has had the chance to observe the active job's surveillance
text. signals for the short time (less than 1 minute) needed to
System action: See the following message issued by this deduce the maximum possible difference between the
CICS job. respective TOD clocks.
User response: None
The takeover cannot be performed unless the difference
Module: DFHWSTKV
between the CPC's TOD clocks is known because normal CICS
processing must not be resumed until the current TOD clock
reading is later than the TOD clock reading when the old
DFHXC6631I applid TAKEOVER REJECTED BECAUSE CICS active job terminated as observed in the CPC where it
LAST ACTIVE INSTANCE NUMBER DOES had been running.
NOT MATCH THAT SPECIFIED. System action: See the following message issued by this
Explanation: The CICS job which issued this message issued CICS job.
a takeover request to the CAVM but the request has been User response: None
rejected due to the error condition described in the message Module: DFHWSTKV
text. This error would occur if a new CICS active job signed Destination: Console
on to the CAVM after this CICS alternate job had already
made the decision to attempt to take over from the previous DFHXC6635I applid TAKEOVER PROCESSING
CICS active job. TERMINATED BECAUSE ANOTHER
System action: See the following message issued by this BACKUP HAS STARTED A PRE-EMPTIVE
CICS job. TAKEOVER.
User response: None Explanation: The CICS job which issued this message issued
Module: DFHWSTKV a takeover request to the CAVM and the request was accepted,
Destination: Console but the error condition described in the message text was
encountered before the completion of TAKEOVER.
CICS job.

User response: None displayed this message is a CICS active and the condition
Module: DFHWSTKV persists for long enough, it is possible that an unwanted
Destination: Console takeover will be initiated when the alternate (assuming that it
is able to read the CAVM data sets because it is running in a
different CPC) notices that the active system's surveillance
DFHXC6636I applid TAKEOVER PROCESSING signals have ceased.
TERMINATED BECAUSE STATUS OF User response: If this message is issued by an CICS active
ACTIVE JOB CANNOT BE DETERMINED. job which does not seem to be experiencing other problems, it
Explanation: The CICS job issued a takeover request to the might be advisable to issue a suitable command to the
CAVM and the request was accepted, but takeover processing corresponding alternate job to prevent it from initiating an
could not be completed because of an error encountered in unnecessary takeover. See also message DFHXC6620.
using the CAVM services provided by DFHWTI. Module: DFHWSSW
CICS job.
User response: For problem determination, see the CICS
Problem Determination Guide. The console log and job output DFHXC6641I applid STATUS WRITE I/O ERROR ON
may be required. dsname
Module: DFHWSTKV Explanation: The CICS job which displayed this message has
Destination: Console encountered an I/O error in writing its latest status to either
the control data set or the message data set.
System action: If the CICS job is able to write its status
DFHXC6637I applid TAKEOVER IS WAITING TO successfully to either the control data set or the message data
RESERVE OR ACCESS THE CAVM set, processing continues. Further writes to the failing data set
CONTROL DATA SET. might be attempted later on because it is possible that the
Explanation: The CICS job that issued this message issued a error condition was temporary. If both data sets become
TAKEOVER request to the CAVM. CAVM is attempting to unusable simultaneously, the CAVM task abends.
LOCK or access the CAVM control data set in order to process User response: Inform your installation's system
the request, but for some considerable time, either the required programmer.
resource has remained unavailable or an outstanding I/O Module: DFHWSSW
request has not completed. The LOCK attempt should not fail Destination: Console
unless another CICS job using the same CAVM data set and
executing a SIGNON, SIGNOFF or TAKEOVER request has
been held up, possibly by I/O delays, after issuing a DFHXC6642I applid ALL STATUS READERS ARE IN I/O
successful LOCK. WAIT.
System action: See message DFHXC6620. Explanation: The CICS job has found that the reads it has
User response: See message DFHXC6620. issued to the control data set and the message data set to
Module: DFHWSTKV obtain the latest available status of its partner system are both
Destination: Console taking a long time to complete.
System action: The CICS job reissues this warning message
at intervals until one of the status reads completes.
DFHXC6638I applid NOTIFY RC= retcode - text Meanwhile, it continues to perform any processing which is
Explanation: The CICS job has found that the return code not dependent on status read completion. If the job which
passed back to CAVM by the NOTIFY exit (DFHXRB) was displayed this message is a CICS alternate, It is possible that a
non-zero. The message includes the actual return code value takeover will not be initiated if the active fails, since the
retcode (or greater than 99) and some text identifying the type alternate cannot detect that the active's surveillance signals
of event which was being processed when the error occurred. have ceased.
This message always indicates either an internal error in User response: See message DFHXC6620.
CAVM or CICS or that code or data has become corrupted. Module: DFHWSSR
System action: Processing continues but XRF function is Destination: Console
probably degraded.
User response: Inform your installation's system
programmer. DFHXC6643I applid STATUS READ I/O ERROR ON dsname
Module: DFHWSTKV Explanation: The CICS job which displayed this message has
Destination: Console encountered an I/O error in reading the latest available status
of its partner system from either the control data set or the
message data set. dsname is the name of the data set.
DFHXC6640I applid ALL STATUS WRITERS ARE IN I/O System action: Processing continues but XRF function will be
WAIT. degraded because the affected system might not be able to
Explanation: The CICS job has found that the writes of its detect changes in its partner's status. Further reads from the
latest status issued to the control data set and the message failing data set might be attempted later on because it is
data set are both taking a long time to complete. This might possible that the error condition was transient. If this error is
occur if LOCK's issued by jobs (not necessarily CICS) running encountered in an alternate system while it is processing a
in other CPC's have made the DASD volumes of both CAVM takeover request, the takeover will fail.
data sets temporarily inaccessible. User response: Inform your installation's system
System action: The CICS job reissues this warning message programmer.
at intervals until one of its status writes completes. Module: DFHWSSR
Meanwhile, it continues to perform any processing which is Destination: Console
not dependent on status write completion. If the job which

Errors detected by DFHWSSN2 (20xx)

DFHXC6644I applid NOTIFY RC= retcode - text
2001 Function code in SIGNON parameter block is
Explanation: The CICS job which displayed this message has
invalid.
found that the return code passed back to CAVM by the
2002 Function modifier in SIGNON parameter block is
NOTIFY exit (DFHXRB) was non-zero. The message includes
invalid.
the actual return code value retcode (or a value greater than 99)
2003 Length of SIGNON parameter block extension is
and some text identifying the type of event that was being
incorrect.
processed when the error occurred. This message always
2004 Requested surveillance interval is not positive.
indicates either an internal error in CAVM or CICS or that
2006 Nonzero return code from asynchronous VSAM GET
code or data has become corrupted.
or CHECK while reading the state management
System action: Processing continues but XRF function is
record. (This could be caused by an I/O error.)
probably degraded.
2007 Nonzero return code from asynchronous VSAM PUT
User response: Inform your installation's system
or CHECK while updating the state management
programmer.
record. (This could be caused by an I/O error.)
Module: DFHWSSR
2008 Nonzero return code from a request to start a check
for the presence of surveillance signals.
2009 Unexpected return code from a request to complete
DFHXC6645I applid ERROR IN INQUIRE HEALTH EXIT. a check for the presence of surveillance signals.
Explanation: The CICS job which displayed this message has 200A Nonzero return code from asynchronous VSAM GET
found that the return code passed back to CAVM by the or CHECK while reading a status CI to check for the
INQUIRE HEALTH exit (DFHXRC) was nonzero. This presence of surveillance signals. (This could be
message indicates either an internal error in CAVM or in caused by an I/O error.)
CICS, or that code or data has become corrupted. 200B Routine to check for the presence of surveillance
System action: Processing continues but XRF function is signals found that the sequence number in a status
probably degraded. CI has decreased.
User response: Inform your installation's system 200C Nonzero return code from asynchronous VSAM GET
programmer. or CHECK while reading a status CI in order to
Module: DFHWSTI update it. (This could be caused by an I/O error.)
Destination: Console 200D Content of the state management record has
changed but its security count is unaltered.
200E Nonzero return code from asynchronous VSAM PUT
DFHXC6649I applid SIGNOFF IS UNABLE TO LOCK THE or CHECK while updating a status CI in the control
CAVM CONTROL DATA SET. data set. (This could be caused by an I/O error.)
Explanation: The CICS job which issued this message issued 200F Unexpected return code (>4) from the LOCK macro.
a SIGNOFF request to the CAVM or SIGNOFF processing was Possible causes include overflow in the LOCK file,
invoked implicitly by abnormal termination of the CAVM task. an I/O error, and various logic errors.
CAVM attempted to LOCK the CAVM control data set in 2010 Nonzero return code from VSAM MODCB macro to
order to process the request, but for some considerable time, change OPTCD in RPL to UPD.
the required resource remained unavailable. The LOCK 2011 Nonzero return code from VSAM MODCB macro to
attempt should not fail unless another CICS job using the change ACB address in RPL.
same CAVM data set and executing a SIGNON, SIGNOFF or 2013 Unexpected return code from DFHWTI.
TAKEOVER request has been held up, possibly by I/O delays, 2014 Unexpected return code from a requested POWER
after issuing a successful LOCK. job STATUS enquiry function.
System action: The CAVM task terminates without updating
the CAVM data sets to indicate that this CICS job has signed Errors detected by DFHWSSN3 (30xx)
off. See also any following message issued by this CICS job. 3001 Nonzero return code from VSAM GENCB macro to
User response: None. build an RPL.
Module: DFHWSSOF 3002 Nonzero return code from VSAM SHOWCB macro
Destination: Console to obtain the length of an ACB.
3003 Nonzero return code from VSAM SHOWCB macro
DFHXC6650I applid A SEVERE ERROR HAS OCCURRED to obtain the length of an RPL.
DURING CAVM PROCESSING. CODE = 3004 Nonzero return code from VSAM SHOWCB macro
code to obtain ACB OPEN error code.
Explanation: The CICS XRF job that issued this message has 3005 Nonzero return code from VSAM SHOWCB macro
encountered an unexpected severe error during CAVM to obtain ACB CI size and RBA data.
processing. The code code in the message identifies both the 3006 The high-used RBA of a CAVM data set is zero
error, and the CAVM module that detected it, as follows: when it should not be empty.
3007 Nonzero return code from asynchronous VSAM GET
Errors detected by DFHWSRTR (00xx) while reading the Control CI from a CAVM data set.
0001 Parameter block for a SIGNON, SIGNOFF or 3008 Nonzero return code from VSAM MODCB macro to
TAKEOVER request is invalid. change STRNO in an ACB.
0002 CAVM dispatcher has no ready processes to 3009 Unexpected return code from the LOCK macro.
dispatch and no external event to wait for. 300A Nonzero return code from ATTACH for subtask to
format a new pair of CAVM data sets.
Errors detected by DFHWSSN1 (10xx) 300B Internal logic error while processing a new pair of
1001 Nonzero return code from ATTACH for CAVM task. CAVM data sets.

DFHXC6650I
300C Nonzero return code from VSAM TESTCB macro to between the active's and alternate's TOD clocks
test whether the data set associated with an open derived from the time-stamp in the status CI which
ACB is an ESDS. has just been read is less than the existing estimate
300D Nonzero return code from VSAM SHOWCB macro of the lower bound of this difference.
to obtain ACB CI size and RBA data during the data 5007 The sequence numbers in an XRF partner job's pair
set formatting. of status CIs in the control and message data sets
300E Nonzero return code from synchronous VSAM PUT are equal but nonzero.
while formatting a new pair of CAVM data sets. 5008 The sequence number in a status CI of an XRF
(This could be caused by an I/O error.) partner job is now inconsistent with previously
300F Nonzero return code from VSAM GENCB macro to observed values.
build an ACB. 5009 The instance and version numbers in a status CI of
3010 Nonzero return code from VSAM SHOWCB macro an XRF partner job are now less than the
to obtain ACB CI size and RBA data. corresponding values in the public status area.
3011 Nonzero return code from VSAM MODCB macro to 500A The instance and version numbers in a status CI of
change the ACB address in RPL. an XRF partner job are unaltered but the job state
indicator has changed from 'signed off' to 'signed
Errors detected by DFHWSSOF (40xx) on'.
4001 Nonzero return code from VSAM GENCB macro to 500B Public status area seems to contain valid data about
build RPLs. an XRF partner job before it should.
4003 Nonzero return code from VSAM MODCB macro or 500C Attempt to indicate that public status is available for
synchronous GET, or I/O request was purged by the another XRF partner job when it is already available
timer exit, when trying to read the state for all partners.
management record. (This could be caused by an 500D The alternate has encountered I/O errors in
I/O error.) consecutive attempts to read the active's status CIs
4007 State management record contains invalid duplicate from both control and message data sets.
entries for this CICS XRF job. 500E The alternate has encountered an I/O error in trying
4008 The location of this CICS job's description in the to read one of the active's status CIs during a
state management record is inconsistent with the takeover.
current value of SMDR1NDX. 500F Logical error return code from VSAM CHECK of an
4009 The sequence numbers in this CICS XRF job's pair of asynchronous GET.
status CIs in the control and message data sets are 5010 Nonzero return code from asynchronous VSAM
equal but nonzero. GET.
400A Unexpected return code from the LOCK macro. 5011 This alternate has been invalidated by the active,
400B Unable to LOCK control data set after repeated probably because of message transmission
attempts. difficulties. This can also be caused by a message
400C Nonzero return code from VSAM MODCB macro or data set that is too small. In this case, increase the
return code 4 from synchronous PUT when trying to size of the message data set to allow the alternate
update status CI. CICS to apply its updates before they are
400D Nonzero return code from VSAM MODCB macro or overwritten by those of the active CICS.
synchronous GET, or I/O request was purged by the
timer exit, when trying to update the state Errors detected by DFHWSSW (60xx)
management record. (This could be caused by an 6001 Logical error return code from VSAM CHECK of an
I/O error.) asynchronous PUT.
6002 I/O errors have been encountered in consecutive
Errors detected by DFHWSSR (50xx) attempts to write to this job's status CIs in both
5001 Nonzero return code from VSAM GENCB macro to control and message data sets.
build an RPL. 6003 Nonzero return code from asynchronous VSAM
5002 The alternate has detected that the active's status CI PUT.
was still being updated after the active job had 6004 The 'status write completed' event masks have been
signed off or terminated. (This error could be caused corrupted.
by an invalid XRF configuration in which the active 6005 WSAGINDX has been corrupted.
and alternate do not share a common POWER job 6006 Nonzero return code from VSAM GENCB macro to
queue. The problem was not discovered when the build an RPL.
second job signed on to the CAVM because at that 6007 The sequence number in one of this job's status CIs
time it was unable to detect the first job's has been corrupted in the control or message data
surveillance signals.) set.
5003 The sequence number in a status CI of an XRF
partner job has decreased. Errors detected by DFHWSTKV (80xx)
5004 The alternate has detected that the sequence 8001 Nonzero return code from VSAM GENCB macro to
numbers in the active's pair of status CIs in the build an RPL.
control and message data sets are equal but nonzero. 8002 State management record indicates that the alternate
5005 The estimate of the lower bound of the difference attempting to take over already holds the takeover
between the active's and alternate's TOD clocks lock.
derived from the time-stamp in the status CI which 8003 State management record indicates that the alternate
has just been read is greater than the existing attempting to take over already holds the resources
estimate of the upper bound of this difference. which are freed by SIGNOFF of the active job.
5006 The estimate of the upper bound of the difference 8004 State management record indicates that the alternate

DFHXC6651I • DFHXG6400I
attempting to take over already holds the resources 8010 Unexpected return code from the LOCK macro.
which are freed by termination of the active job. 8011 Invalid request code passed to the routine which
8005 DFHWTI encountered an error in trying to confirm attaches a subtask to issue XRF requests to
termination of the active job after the alternate DFHWTI.
performing the takeover had already acquired the 8012 Nonzero return code from ATTACH for subtask to
resources freed by the active SIGNOFF. issue XRF request to DFHWTI.
8006 Another alternate has started a preemptive takeover 8013 Nonzero return code from DETACH for subtask.
after this alternate had already acquired the System action: An ABEND is issued with a reason code
resources freed by the active SIGNOFF. equal to the code in message DFHXC6650. This results in
8007 The time-stamp associated with the resources freed abnormal termination of the CICS XRF job. See also any
by termination of the active job cannot be updated following messages issued by this CICS XRF job.
because an unexpected problem has arisen with the User response: Inform your installation's system
TOD clock difference data after this alternate had programmer.
already acquired the resources freed by the active Module: DFHWSRTR, DFHWSSN1, DFHWSSN2,
SIGNOFF. DFHWSSN3, DFHWSSOF, DFHWSSR, DFHWSSW,
8009 Nonzero return code from VSAM CHECK of DFHWSTKV
asynchronous GET for the state management record. Destination: Console
(This could be caused by an I/O error.)
800B Nonzero return code from VSAM CHECK of
asynchronous PUT for the state management record. DFHXC6651I applid CAVM HAS DETECTED AN INVALID
(This could be caused by an I/O error.) REQUEST.
Explanation: CAVM has found that the parameter block
800C Nonzero return code from asynchronous VSAM GET
passed to it is invalid, or that the request is being made at an
to read the state management record in QUIESCE
inappropriate time.
routine.
System action: An ABEND is issued with reason code 1. This
800D Nonzero return code from VSAM CHECK of
results in the abnormal termination of the CICS job. See also
asynchronous GET for the state management record any following messages issued by this CICS job.
in QUIESCE routine. (This could be caused by an User response: Restart the failing CICS job and inform your
I/O error.) installation's system programmer.
800E Nonzero return code from VSAM MODCB macro to Module: DFHWSRTR
change OPTCD in RPL to UPD. Destination: Console
800F Nonzero return code from VSAM MODCB macro to
change OPTCD in RPL to NUP.
DFHXGxxxx (XRF general) messages

XMEOUT Parameters: applid, progname, operation, cccc, cccc,
DFHXG6215 applid progname operation failure, response
rrrr,{1=., 2= key: }, key
code cccc cccc keyrange: rrrr{. | key: }key
Explanation: Table builder services (DFHTBSS) failed in an Destination: Console
operation on the global catalog (DFHCCCC).
The failing operation is shown in the message, and is a DFHXG6400I applid Signing on to the CAVM as active with
DELETE, WRITE_NEXT, START_WRITE or END_WRITE. generic APPLID genericid
request. Explanation: This is an informational message issued from
v cccc cccc are the response and reason codes from the catalog the CICS task. It indicates that the system is about to sign on
domain. to the CICS availability manager (CAVM) as active. The
v rrrr is the internal RQ token passed to the catalog domain. message insert provides the generic applid.
v key appears in the message only for a WRITE or DELETE System action: CICS initialization is delayed until the signon
operation, and usually includes the name of the resource for request has been processed.
which CICS failed to record information on the global
In general the delay is insignificant. In those cases where the
catalog.
delay is significant messages are produced by the CAVM to
This is normally an internal CICS error, however, it can occur note the reasons.
during shut down if one task initiates a normal shut down, User response: None.
and another initiates an immediate shut down shortly
afterwards. This is because the immediate shut down closes Note: If the alternate CICS system tries to open the CAVM
resources that are being used by the normal shut down task. data sets (issuing message DFHXA6500I) at the same time as
the active system, you see two VSE VSAM open error
This can also occur if the global catalog is not big enough and messages for the system that is later in attempting the VSAM
a large group is being installed. open. The format of the messages is:
System action: CICS terminates. 4228I FILE DFHXMSG OPEN ERROR X’A8’.....
User response: Check the size of the global catalog. Redefine 4228I FILE DFHXCTL OPEN ERROR X’A8’.....
a larger one if necessary.
Alternatively this message could be caused by an immediate You can ignore these messages, because the affected CICS will
shutdown of CICS because tasks not yet quiesced may abend retry open after a short interval. This attempt succeeds,
trying to access a service removed by the shutdown process. provided the first system's open has ended normally, leaving
Module: DFHTBSS the data sets in shared status
Module: DFHXRA

DFHXG6401I • DFHXG6411I
XMEOUT Parameters: applid, genericid

DFHXG6406I applid Sign off normal from the CAVM
rejected.
DFHXG6401I applid Sign on to the CAVM as active the CICS task. It indicates that the system is about to sign off
accepted abnormally from the CAVM.
Explanation: This is an informational message issued from System action: CICS termination is delayed until the sign off
the CICS task. It indicates that the signon request (refer to request has been processed.
message DFHXG6400) has been accepted by the CAVM. User response: None.
System action: CICS initialization is resumed. Module: DFHXRF
User response: None Destination: Console
Module: DFHXRA
XMEOUT Parameter: applid DFHXG6407I applid Sign off normal from the CAVM
Destination: Console detected.
the CICS task. It indicates that CICS has been notified that
DFHXG6402I applid Sign on to the CAVM as active rejected alternate CICS has signed off from the CAVM.
Explanation: This is an informational message issued from System action: CICS processing continues.
the CICS task. It indicates that the signon request has been User response: None.
rejected by the CAVM. (Refer to message DFHXG6400.) Module: DFHXRSP
Messages are produced by the CAVM to note the reasons for
rejecting the request. XMEOUT Parameter: applid
System action: CICS is terminated abnormally. Destination: Console
User response: Correct the errors.
Module: DFHXRA
DFHXG6408I applid Signing off abnormally from the
XMEOUT Parameter: applid CAVM.
Destination: Console Explanation: This is an informational message issued from
the CICS task. It indicates that the sign off request has been
accepted by the CAVM.
DFHXG6403I applid Sign on of specificid to the CAVM as System action: CICS termination continues.
alternate detected. User response: None.
Explanation: This is an informational message issued from Module: DFHXRF
the CICS task. It indicates that CICS has been notified that the Destination: Console
named alternate CICS has signed on to the CAVM.
System action: Transaction CXCU is attached to send
keypoint data to alternate CICS. DFHXG6409I applid Sign off abnormal from the CAVM
User response: None. accepted.
Module: DFHXRSP Explanation: This is an informational message issued from
the CICS task. It indicates that the sign off request has been
XMEOUT Parameters: applid, specificid accepted by the CAVM. (Refer to message DFHXG6408).
Destination: Console System action: CICS termination continues.
DFHXG6404I applid Signing off normally from the CAVM. Module: DFHXRF
Explanation: This is an informational message issued from Destination: Console
the CICS task. It indicates that the system is about to sign off
normally from the CAVM. DFHXG6410I applid Sign off abnormal from the CAVM
System action: CICS termination is delayed until the sign off rejected.
request has been processed. Explanation: This is an informational message issued from
User response: None. the CICS task. It indicates that the sign off request has been
Module: DFHXRF rejected by the CAVM. (Refer to message DFHXG6408.)
rejecting the request.
DFHXG6405I applid Sign off normal from the CAVM System action: CICS termination continues.
accepted. User response: Refer to the messages produced by the CAVM
Explanation: This is an informational message issued from for further information.
the CICS task. It indicates that the sign off request has been Module: DFHXRF
accepted by the CAVM. (Refer to message DFHXG6404). Destination: Console
System action: CICS termination is continued.
Module: DFHXRF DFHXG6411I applid Sign off abnormal from the CAVM
Destination: Console detected.
the CICS task. It indicates that CICS has been notified that the
alternate CICS has signed off from the CAVM.
System action: The system continues with normal processing.

DFHXG6415I • DFHXG6432
However, you should be aware that takeover does not occur if

DFHXG6423I applid CAVM failure detected. CICS cannot
the active CICS fails.
continue as active.
User response: Determine the reason for the abnormal
sign-off.
Module: DFHXRSP
CAVM has failed.
failure.
DFHXG6415I applid CICS is being taken over. Execution User response: Correct the error.
will be terminated. Module: DFHXRSP
CAVM has accepted a takeover request from alternate CICS.
System action: CICS is terminated abnormally.
User response: None. DFHXG6427I applid Terminal control restart task has failed.
Module: DFHXRSP CICS execution will be terminated.
the CICS task. It indicates that the terminal control restart task
has failed. It is no longer possible for CICS to continue either
as active or as alternate.
DFHXG6416I applid APPARENT FAILURE OF ALTERNATE
Messages are produced by the terminal control restart task to
CICS DETECTED.
note the reasons for failure.
User response: Correct the error.
alternate CICS appears to have failed.
Module: DFHXRSP
System action: The system continues with normal processing.
However, you should be aware that takeover may not occur XMEOUT Parameter: applid
should the active CICS fail. Destination: Console
User response: Determine the reason for the apparent failure
of the alternate CICS.
Module: DFHXRSP DFHXG6429I applid Transaction CXCU cannot be attached.
Destination: Console Explanation: This is an informational message issued from
the CICS task. It indicates that CICS is unable to attach
transaction CXCU. Therefore, CICS is unable to initiate the
DFHXG6417I applid Recovery of alternate CICS detected. transmission of tracking messages. Takeover is adversely
Explanation: This is an informational message issued from affected if CXCU cannot be attached. This can occur if:
the CICS task. It indicates that CICS has been notified that 1. CXCU is not defined to CICS, or
alternate CICS has recovered from the apparent failure 2. CICS is short on storage
reported by message DFHXG6416. System action: CICS attempts to attach CXCU at regular
System action: The system continues with normal processing. intervals.
User response: None. User response: Either install CXCU using RDO, or alleviate
Module: DFHXRSP the storage shortage.
Module: DFHXRSP

assumed. DFHXG6430 applid START=LOGTERM specified. CICS
Explanation: This is an informational message issued from start-up is terminated because XRF=YES is
the CICS task. It indicates that CICS has assumed that the specified
alternate CICS has signed off from the CAVM. Explanation: Conflicting system initialization parameters,
START=LOGTERM and XRF=YES, have been specified.
This is likely to occur when the active CICS is running on System action: CICS is terminated abnormally with a dump.
CPC 1 and: User response: Resolve the conflict.
1. The CICS alternate is started on CPC 2, or Module: DFHSIC1
2. The CPC 2 initial program load is repeated, or
3. CICS alternate is restarted on CPC 2. XMEOUT Parameter: applid
System action: CICS processing is continued. Destination: Console
Module: DFHXRSP
DFHXG6432 applid Unable to open restart data set. CICS
XMEOUT Parameter: applid startup will be terminated because XRF=YES
Destination: Console is specified.
Explanation: CICS issued an OPEN for the restart data set,
but the OPEN failed.

DFHXG6433 • DFHXG6445I

DFHXG6441I LOGICAL ERROR ON XRF MESSAGE
the reason for the OPEN failure.
DATA SET. VSAM FEEDBACK DATA =
Module: DFHSIC1
X'xx'.
XMEOUT Parameter: applid Explanation: VSAM reported a logical error on the XRF
Destination: Console message data set.
System action: Surveillance by the XRF system ceases.
User response: This is an error in the CICS system. For
DFHXG6433 applid System log not defined in JCT. CICS diagnostic purposes the message contains the VSAM feedback
startup will be terminated because XRF=YES data for the error.
is specified. Module: DFHWMMT
Explanation: The system log must be defined if XRF=YES is Destination: Console
specified.
Following a takeover, the alternate CICS backs out in-flight DFHXG6442I INTERNAL ERROR IN XRF MESSAGE
changes made by the active. This requires the system log to be MANAGER.
defined to both the active and the alternate. Explanation: Request chains maintained by the CICS message
System action: CICS is terminated abnormally. manager are in an inconsistent state.
User response: Define the system log. System action: Surveillance by the XRF system ceases.
Note: The system log must be defined as DISK2 if XRF=YES resolve this problem. See Part 4 of the CICS Problem
is specified. Determination Guide for guidance on how to proceed.
Module: DFHSIC1 Module: DFHWMQS
DFHXG6443I INTERNAL ERROR IN XRF
SURVEILLANCE COMPONENT.
DFHXG6434 applid System log not defined as DISK2 in
Explanation: An invalid internal call has been made to a
JCT. CICS startup will be terminated because
routine in XRF surveillance component.
XRF=YES is specified.
System action: Surveillance by the XRF system ceases.
Explanation: The system log must be defined as DISK2 if
XRF=YES is specified. The XRF=YES option is not compatible
with a system log defined as TAPE1, TAPE2, or as DISK1.
Module: DFHWCCS
User response: Redefine the system log as DISK2.
Module: DFHSIC1
DFHXG6444I VSAM REQUEST REJECTED FOR XRF
MESSAGE DATA SET.
Explanation: A VSAM PUT or GET request directed to the
DFHXG6439I applid CICS startup is terminated for reasons XRF message data set has been rejected.
given above. System action: Surveillance by the XRF system ceases.
Explanation: This is an informational message indicating that User response: You need further assistance from IBM to
CICS startup is terminated. resolve this problem. See Part 4 of the CICS Problem
System action: CICS is terminated abnormally with a dump. Determination Guide for guidance on how to proceed.
User response: Refer to previous messages that have been Module: DFHWMMT
sent to the system console for further guidance. Destination: Console
Module: DFHSIC1
XMEOUT Parameter: applid DFHXG6445I XRF MESSAGE DATA SET FORMATTING
Destination: Console STARTED.
Explanation: The XRF message data set is new and must be
formatted before it can be used to pass messages from the
DFHXG6440I I/O ERROR ON XRF MESSAGE DATA SET. active to the alternate.
RPL ADDRESS = X'xx'. System action: Normal service continues.
Explanation: VSAM reported a physical I/O error on the User response: Depending on the size of the message data
XRF message data set. The address X'xx' is that of the VSAM set, there will be some delay before the active can send
RPL which reported the error. messages to the alternate. It may be advisable to defer starting
System action: Surveillance by the XRF system ceases. an alternate system until the corresponding message
User response: It is necessary to restart both the active and DFHXG6446 has been received.
alternate CICS systems with a fresh pair of surveillance data Module: DFHWMMT
sets. For diagnostic purposes, the message gives the address of Destination: Console
the RPL being used at the time the error was reported. The
RPL has an associated VSAM message area.
Module: DFHWMMT


DFHXG6446I XRF MESSAGE DATA SET FORMATTING
Module: DFHWLFRE
COMPLETED.
Explanation: The XRF message data set has now been
formatted. It can be used to pass messages from the active to
the alternate. DFHXG6453I INTERNAL ERROR IN XRF
System action: Normal service continues. SURVEILLANCE.
User response: None. See message DFHXG6445. Explanation: A consistency check made by the XRF process
Module: DFHWMMT manager has failed. A process has made an invalid internal
Destination: Console lock request.
DFHXG6447I NON CRUCIAL XRF MESSAGE(S)
DISCARDED.
Explanation: The XRF message data set is full. Some
Module: DFHWDWAT
messages are being discarded in preference to invalidating the
alternate system by overwriting messages that it has not yet
read.
System action: Normal service continues. DFHXG6454I PROGRAM CHECK IN XRF
User response: This situation is likely to arise in SURVEILLANCE. PSW = X'psw'. ADDRESS
circumstances similar to those described for message OF SAVE AREA = X'savearea'.
DFHXA6541. The alternate has not yet become invalid but is Explanation: A program check occurred from which the XRF
likely to become so and corrective action is warranted. Refer process was unable to recover.
to message DFHXA6541 for further guidance. System action: CICS terminates abnormally with a SDUMP.
Module: DFHWMWR User response: This is an error in the CICS system. The
Destination: Console message gives the PSW at which the check occurred. Further
information is preserved in the dump.
DFHXG6450I GETVIS FAILED IN XRF SURVEILLANCE. You need further assistance from IBM to resolve this problem.
Explanation: An SVC storage request issued by the CICS See Part 4 of the CICS Problem Determination Guide for
surveillance component has failed. The request may have been guidance on how to proceed.
issued under either the CICS task or the XRF task. Module: DFHWDSRP
System action: CICS terminates abnormally. Destination: Console
User response: If the available GETVIS is exhausted, either
increase the size of the partition or reduce the value of the
EDSALIM system initialization parameter. DFHXG6460I applid UNABLE TO LOAD TERMINAL
SWITCHING PROGRAM progname.
If this is not the case, the problem is probabaly due to a CICS CDLOAD FAILED. R15= retcode.
logic error and you will need assistance from IBM to resolve Explanation: DFHWSPX has attempted to use CDLOAD to
the problem. See Part 4 of the CICS Problem Determination load the terminal switching program named in the XSWITCH
Guide for guidance on how to proceed. system initialization parameter. This load has failed with
Module: DFHWCCS return code retcode.
retcode is the return code from the CDLOAD macro.
System action: The terminal switching subtask is ended.
DFHXG6451I GETVIS FAILED IN XRF SURVEILLANCE. User response: See the z/VSE System Macros Reference manual
Explanation: An SVC storage request issued by the CICS for the meaning of the CDLOAD return code. Use this code to
surveillance component has failed. The request may have been determine why the load failed.
issued under either the CICS task or the XRF task. Module: DFHWSPX
System action: CICS terminates abnormally. Destination: Console
User response: If the available GETVIS is exhausted, either
increase the size of the partition or reduce the value of the
EDSALIM system initialization parameter. DFHXG6461I applid ERROR RETURNED BY TERMINAL
SWITCHING PROGRAM. OPCODE= opcode
If this is not the case, the problem is probabaly due to a CICS RC= retcode
logic error and you will need assistance from IBM to resolve Explanation: DFHWSPX has called the terminal switching
the problem. See Part 4 of the CICS Problem Determination program named by the XSWITCH system initialization
Guide for guidance on how to proceed. parameter. The program has given a non-zero return code.
Module: DFHWLGET System action: If the return code is greater than 4, the
Destination: Console terminal switching program subtask is ended.
User response: Return codes are from the user written
program named by the XSWITCH system initialization
DFHXG6452I INTERNAL ERROR IN XRF
parameter.
SURVEILLANCE.
Module: DFHWSPX
Explanation: A consistency check made by the XRF LIFO
storage manager has failed. The failure may have occurred
while running under either the CICS task or the XRF task.

DFHXG6475 • DFHXG6482
Where:
DFHXG6475 applid iiii Backup simlogon(s) abandoned
v 'proc' is the procedure name for VTAM,
Explanation: An XRF alternate is taking over, and is
v 'generic-ID' is the VTAM application ID for the whole
processing the last few session tracking requests.
complex, and
CICS has issued a SIMLOGON for a standby session, but v 'specific-ID' is the VTAM application ID for the new CICS
VTAM has not yet returned the logon request to CICS's VTAM
logon exit. If it is not possible to change the USERVAR, end-user logons
which name the generic-ID value continue to be directed to
Message DFHXG6480 has been issued twice, and CICS has
the old specific-applid, with unpredictable results.
now assumed that the logons will not appear.
Normal processing continues, though the state of the sessions (However, logons quoting the specific-ID of the new system
currently pending backup SIMLOGON is unpredictable at the are routed to that system.)
end of CICS initialization. Module: DFHZXSTS
The reconnection process attempts to BIND these sessions XMEOUT Parameters: applid, nn
normally. Destination: Console
System action: Normal takeover processing continues.
User response: The CSTL log and CICS trace should be
collected. DFHXG6480I applid Waiting for backup simlogon
Module: DFHZXST processing to drain
Explanation: An XRF alternate is taking over, and is
XMEOUT Parameters: applid, iiii processing the last few session tracking requests.
CICS has issued SIMLOGON for a standby session, but VTAM
has not yet returned the logon request to the CICS VTAM
DFHXG6476I applid XRF catch-up abandoned - all XRF logon exit.
alternates signed off
Explanation: A run of the XRF catch-up transaction has been This message is issued every 5 seconds for 20 seconds while
abandoned because there are no XRF alternates. A failing the takeover is being held up.
alternate may have issued some messages. This indicates either a VTAM error or a CICS logic error.
System action: Normal processing continues. System action: This message is issued twice and then
User response: None. message DFHXG6475 is issued.
Module: DFHZXCU User response: If this message is repeated look for other
XMEOUT Parameter: applid evidence of failure in CICS or VTAM.
Destination: Console Module: DFHZXQO

DFHXG6477I applid Generic and Specific Ids have same Destination: Console
value
Explanation: A CICS system has issued the command to DFHXG6481I applid Autoconnect delayed for hh hours, mm
re-assign the VTAM USERVAR representing the XRF complex minutes, ss seconds.
so that from now on logon requests to the XRF complex are Explanation: CICS has delayed running the reconnection
directed to this CICS. However, this system is an XRF primary, transaction CXRE for an interval of hh hours, mm minutes, ss
and the value of the specific ID is the same as the generic ID seconds, to either:
for the XRF complex. v acquire AUTOCONNECT terminals after a CICS startup, or
System action: Normal processing continues. v reacquire terminal sessions after an XRF takeover.
User response: None. However special care must be taken
when using the application ID. You must make it clear
The delay value, hh hours, mm minutes, ss seconds, is taken
whether reference is being made to the CICS system or to the
from the AUTCONN system initialization parameter.
XRF complex.
Module: DFHZXSTS
In the case of XRF takeover, a value calculated from the
XMEOUT Parameter: applid number of standby BINDs held at the time of takeover. This
Destination: Console extra interval allows the switching of XRF-capable terminals
before non-XRF sessions are reconnected by CXRE.
DFHXG6479 applid Modify USERVAR issued
unsuccessfully. Return code nn
Module: DFHSIJ1
Explanation: A CICS system has unsuccessfully issued a
command to re-assign the VTAM USERVAR representing the XMEOUT Parameters: applid, hh,mm, ss
XRF complex. Destination: Console
User response: See the VTAM Programming manual for
diagnostic information about the return code in the message. DFHXG6482 applid Unable to issue SETLOGON HOLD
(reqcode,reg15,reg0)
The system operator can issue the command on CICS's behalf. Explanation: This message is issued if VTAM SETLOGON
The format is as follows: START fails during initialization or if in preparation for
F proc,USERVAR,ID=generic-id,VALUE=specific-id changing the routing of VTAM logons, this system (which is
currently doing an XRF takeover) has attempted to request

DFHXG6483I • DFHXG6488
VTAM to stop passing any more logon requests to it. The

DFHXG6486I applid termid may not be acquired after
attempt failed, and the details of the failure are given in the
takeover
message, as follows. The first insert is one of the following.
Explanation: The reconnection transaction, CXRE, is making
v 'S'—The SETLOGON START request failed.
its last run, but has discovered that terminal or session termid
v 'H'—The SETLOGON HOLD request failed.
is still not bound in the same status that it was in during the
previous failed run of CICS.
The second and third inserts are the values of registers 15 and System action: Normal processing continues.
0, respectively, at the time of the failure. User response: Note the terminal identification termid in the
message, and try to discover why previous reconnection
See the VTAM Programming manual for the interpretation of attempts failed. The terminal may not have been physically
these values. switched, for example, CEMT may be used to acquire
individual terminals after such problems have been cleared.
Valid logons reaching CICS before message DFHSI1517 is Module: DFHZXRE0
issued may be rejected.
XMEOUT Parameters: applid, termid
User response: Note the message.
Module: DFHZXSTS
DFHXG6487 applid Unexpected IC/PC error code X'code'.
XMEOUT Parameters: applid, reqcode,reg15, reg0
Module modname
Explanation: The reconnection transaction CXRE could not be
scheduled or rescheduled., as the DFHIC TYPE=INITIATE or
DFHXG6483I applid This will be the last pass. DFHPC TYPE=LINK was rejected with code X'code'. This is
Explanation: The reconnection transaction CXRE is about to caused by a CICS logic error.
scan the VTAM terminals and sessions that were to be This message follows either:
(re)connected for the last time. All those found are listed in v DFHXG6485 if CICS was unable to schedule CXRE, or
message DFHXG6486. v DFHXG6489 if CICS was unable to reschedule CXRE.
System action: Processing continues System action: The action taken by CICS depends upon
User response: If any of the VTAM terminals or sessions whether the error occurred during scheduling or rescheduling
listed in message DFHXG6486 are crucial, then check whether of CXRE.
they are successfully connected as a result of this pass.
Module: DFHZXRE Refer to the system action for either DFHXG6485 or
DFHXG6489 for further details about the action taken by
XMEOUT Parameter: applid CICS.
DFHXG6484I applid Autoconnect processing now complete. User response: You need further assistance from IBM to
Explanation: The reconnection transaction CXRE has just resolve this problem. See Part 4 of the CICS Problem
scanned all the VTAM terminals and sessions, and all those Determination Guide for guidance on how to proceed.
that were to be (re)connected are now connected. Module: DFHSIJ1, DFHZOPA
System action: Processing continues
User response: None. XMEOUT Parameters: applid, X'code',modname
Module: DFHZXRE Destination: Console

Destination: Console DFHXG6488 applid Required transaction CXRE is not
defined to CICS. Module modname
Explanation: The reconnection transaction, CXRE, could not
DFHXG6485 applid Unable to schedule Autoconnection / be rescheduled. This was because either the transaction code
Reconnection process. required no longer has an installed transaction definition, or
Explanation: CICS initialization attempted to schedule the the program required does not have an installed program
reconnection process, but was unable to do this as CICS definition.
rejected the DFHPC TYPE=LINK call.
This message follows DFHXG6489 or DFHXG6485
See following message DFHXG6487 or DFHXG6488 for the System action: The current run of the reconnection
reason. transaction is the last one. Message DFHXG6486 is issued for
System action: The reconnection process is not run. all terminals and sessions found.
User response: CEMT must be used to restore individual User response: If terminals are to be reconnected, correct the
terminals to the desired state. problem.
Module: DFHZOPA Module: DFHSIJ1, DFHZOPA
XMEOUT Parameter: applid XMEOUT Parameters: applid, modname

DFHXG6489 • DFHXG6493
v code for event being tracked (see 4 above)

DFHXG6489 applid Unable to schedule Autoconnection /
7 Incorrect entry named in tracking message.
Reconnection transaction CXRE. Module
modname. Inserts:
Explanation: The reconnection transaction, CXRE, attempted v name of terminal or session
to reschedule itself, but was unable to as CICS interval control v code for event being tracked (see 4 above)
rejected the DFHIC TYPE=INITIATE call. 8 Bad request code in tracking message.
This message is followed either by DFHXG6487 or Inserts:
DFHXG6488, which provides further information about the
v name of terminal or session
cause of the error.
v bad request code (see 4 above for valid DFHZXST
System action: The current run of the reconnection
codes)
transaction is the last one. Message DFHXG6486 is issued for
10 Unable to schedule standby BIND.
all terminals and sessions found.
User response: See the following message. CEMT may be Insert:
used to acquire individual terminals. v name of terminal or session.
Module: DFHSIJ1 System action: Normal processing continues.
XMEOUT Parameters: applid, modname User response: Note the message. Resources and states may
Destination: Console be incorrect should the backup take over. If many of these
messages are issued, then it is likely that there is a more
general problem.
DFHXG6490I applid Reconnecting VTAM session - pass Module: DFHSUSX, DFHZXST
number xxxx
Explanation: Control has recently been given to CICS after an XMEOUT Parameters: applid, rcode,terminal/session, event
XRF takeover. The reconnection transaction, CXRE, which Destination: Console
attempts to start acquire processing for logical units that were
in session in the failed active, has just started for the pass
number xxxx. DFHXG6492I applid XRF catch-up logic error reason length
System action: Normal processing continues. Explanation: The XRF catch-up program encountered an
User response: Note any error messages arising as CICS unexpected circumstance probably due to a CICS design error.
attempts to reconnect terminals and sessions. The reason, indicated by the first insert, is one of the
Module: DFHZXRE0 following:
1 Catalog record internal length value not correct.
XMEOUT Parameters: applid, xxxx 2 Catalog record format error. There is no room for a
Destination: Console key.
3 Catalog record format error. The key is longer than
16.
DFHXG6491 applid Logic error during session tracking.
4 Catalog record too long for buffer (variable
REASON rcode terminal/session event
CUBUFFER). The second insert gives the required
Explanation: XRF session tracking encountered an
unexpected circumstance probably due to a design error. The length.
reason code (rcode) is one of the following. 5 Unexpected ABEND or response from EXEC CICS
1 POST called but no pending action for terminal or command.
session. 6 Catalog record format error. There is no resource
manager prefix.
Inserts: System action: In cases 1, 2, 3, and 6 above, normal
v name of terminal or session. processing continues.
2 DFHZXST called with bad request value.
4 Could not get key to build tracking message. In case 4, DFHZXCU abends with abend code AZXB. In case
5, DFHZXCU abends with abend code AZXA.
Inserts: User response: Note the message. Resources and states may
v name of terminal or session be incorrect should the alternate take over. If many of these
v code for event being tracked messages are issued, it is likely that there is a more general
problem.
The following are valid for DFHSUSX only.
Module: DFHZXCU
v X'01'—Send sign on data
v X'02'—Send sign on data (catchup) XMEOUT Parameters: applid, reason,length
v X'03'—Receive sign on data Destination: Console
The following are valid for DFHZXST only.
v X'F1'—BIND DFHXG6493 date time applid XRF tracking record could not
v X'F2'—Free LOGON data be sent xxxx xxxx xxxx xxxx xxxx (Module:
v X'F3'—UNBIND modname)
5 Could not get send tracking message. Explanation: The XRF catch-up program obtained a bad
return code from the XRF message manager and was unable
Inserts: to send a record that the alternate would require to obtain a
v name of terminal or session correct copy of the active. The inserts (internal diagnostic
v code for event being tracked (see 4 above) information) are:
6 Could not find session named in tracking message. 1. WMSRETC
Inserts:
v name of terminal or session

DFHWMS return code. (For values and meanings of the Destination: CSMT
return codes, refer to the XRF CICS manager request
interface block (WMSPS) listing in the CICS Data Areas.)
2. WMSREASN DFHXG6497I date time applid XRF TCT contents catch-up
started
DFHWMS reason code. (For values and meanings of the Explanation: The XRF catch-up program is about to start an
reason codes, please refer to the XRF CICS manager attempt to send messages to allow a newly signed-on alternate
request interface block (WMSPS) listing in the CICS Data CICS to bring itself up to date with respect to the contents of
Areas.) the TCT.
3. XTR-KEY-VALUE is the key of the tracking record. System action: Normal processing continues.
4. XTR-ID is the record ID, where User response: None.
v zero = tracking, and Module: DFHZXCU
v non-zero = catch-up.
5. XTR-TYPE is the record type (see DFHZXTR), where
Destination: CSMT
v X = tracking control,
v C = TCT contents,
v S = ZCP session tracking, and DFHXG6498I date time applid XRF catch-up ended
v U = sign on data Explanation: The XRF catch-up program has just finished an
attempt to send messages to allow a newly signed-on alternate
The message is issued from module modname. CICS to bring itself up to date.
System action: Normal processing continues. System action: Normal processing continues.
User response: Note the message. Resources and states may User response: None.
be incorrect should the alternate take over. If many of these Module: DFHZXCU
messages are issued, then it is likely that there is a more XMEOUT Parameters: date, time,applid
general problem. Destination: CSMT
Module: DFHZXCU, DFHZXST, DFHTCRP, DFHTBSSP,
DFHSUSX
DFHXG6499I date time applid XRF catch-up started
XMEOUT Parameters: date, time,applid, xxxx, xxxx, xxxx,xxxx, Explanation: The XRF catch-up program is about to start an
xxxx, modname attempt to send messages to allow a newly signed-on alternate
Destination: Console and Transient Data Queue CSMT CICS to bring itself up to date.
DFHXG6494I date time applid XRF session state catch-up Module: DFHZXCU
ended
Explanation: The XRF catch-up program has just finished an XMEOUT Parameters: date, time,applid
attempt to send messages to allow a newly signed-on alternate Destination: CSMT
CICS to bring itself up to date with respect to the bound or
unbound session states.
System action: Normal processing continues. DFHXG6500I applid Signing on to the CAVM as alternate
User response: None. with generic APPLID genericid
Module: DFHZXCU Explanation: This is an informational message issued from
the CICS task. It indicates that the system is about to sign on
XMEOUT Parameters: date, time,applid to the CICS availability manager (CAVM) as alternate. The
Destination: CSMT message insert provides the generic applid.
System action: CICS initialization is delayed until the sign on
request has been processed. In general the delay is
DFHXG6495I date time applid XRF session state catch-up insignificant. In those cases where the delay is significant
started messages are produced by the CAVM to note the reasons.
Explanation: The XRF catch-up program is about to start an User response: None.
attempt to send messages to allow a newly signed-on alternate
CICS to bring itself up to date with respect to the bound or
unbound session states. Note: If the active CICS system tries to open the CAVM data
System action: Normal processing continues. sets (issuing message DFHXA6400I) at the same time as the
User response: None. alternate system, you see two VSE VSAM open error messages
Module: DFHZXCU for the system that is later in attempting the VSAM open. The
format of the messages is:
4228I FILE DFHXMSG OPEN ERROR X’A8’.....
Destination: CSMT
4228I FILE DFHXCTL OPEN ERROR X’A8’.....
DFHXG6496I date time applid XRF TCT contents catch-up You can ignore these messages, because the affected CICS will
ended retry open after a short interval. This attempt succeeds,
Explanation: The XRF catch-up program has just finished an provided the first system's open has ended normally, leaving
attempt to send messages to allow a newly signed-on alternate the data sets in shared status.
CICS to bring itself up to date with respect to the contents of Module: DFHXRA
the TCT.
System action: Normal processing continues. XMEOUT Parameters: applid, genericid
Module: DFHZXCU

DFHXG6501I applid Sign on to the CAVM as alternate
accepted
Explanation: This is an informational message issued from DFHXG6512I applid Takeover request passed to the CAVM
the CICS task. It indicates that the sign on request has been Explanation: This is an informational message issued from
accepted by the CAVM. (Refer to message DFHXG6500.) the CICS task. It indicates that the system is about to request
System action: CICS initialization is resumed. the CAVM to initiate takeover.
User response: None. System action: CICS initialization continues.
Module: DFHXRA User response: None.
Module: DFHXRA
DFHXG6502I applid Sign on to the CAVM as alternate
rejected DFHXG6513I applid Takeover request accepted by the
Explanation: This is an informational message issued from CAVM
the CICS task. It indicates that the sign on request has been Explanation: This is an informational message issued from
rejected by the CAVM. (Refer to message DFHXG6500.) the CICS task. It indicates that the takeover request (refer to
Messages are produced by the CAVM to note the reasons for message DFHXG6512) has been accepted by the CAVM.
rejecting the request. System action: CICS initialization continues.
System action: CICS initialization is terminated. User response: None.
User response: None. Module: DFHXRA
Module: DFHXRA
DFHXG6514I applid Takeover request rejected by the

DFHXG6503I applid Sign on of specificid to the CAVM as CAVM
active detected. Explanation: This is an informational message issued from
Explanation: This is an informational message issued from the CICS task. It indicates that the takeover request (refer to
the CICS task. It indicates that CICS has been notified that the message DFHXG6512) has been rejected by the CAVM.
named active CICS has signed on to the CAVM. Messages are produced by the CAVM to note the reasons for
System action: CICS initialization continues. rejecting the request.
User response: None. System action: CICS initialization continues.
Module: DFHXRSP User response: None.
XMEOUT Parameters: applid, specificid Module: DFHXRA
detected. DFHXG6516I applid Apparent failure of active CICS
Explanation: This is an informational message issued from detected.
the CICS task. It indicates that CICS has been notified that Explanation: This is an informational message issued from
active CICS has signed off from the CAVM. the CICS task. It indicates that CICS has been notified that
System action: CICS processing is terminated. active CICS appears to have failed.
User response: None. System action: The action taken depends on the current
Module: DFHXRSP value of the takeover option. This is specified in the system
initialization table. The CEBT SET TAKEOVER command is
used to change the value. A takeover request will be passed to
the CAVM if the current value of the takeover option is
AUTOMATIC. Message DFHXG6518 will be sent to the
DFHXG6511I applid Sign off abnormal from the CAVM console if the current value is MANUAL.
detected. User response: Determine the reason for the apparent failure
Explanation: This is an informational message issued from of active CICS.
the CICS task. It indicates that CICS has been notified that Module: DFHXRSP
active CICS has signed off from the CAVM.
System action: The action taken depends on the current
value of the takeover option. This is specified in the system
initialization table. The CEBT SET TAKEOVER command is
used to change the value. A takeover request is passed to the DFHXG6517I applid Recovery of active CICS detected.
CAVM if the current value of the takeover option is either Explanation: This is an informational message issued from
AUTOMATIC or MANUAL. the CICS task. It indicates that CICS has been notified that
User response: The user response, if any, is installation active CICS has recovered from the apparent failure reported
dependent. by message DFHXG6516.
Module: DFHXRSP System action: CICS initialization continues.

DFHXG6518D • DFHXG6539I
Module: DFHXRSP User response: Consider restarting (alternate) CICS.

Module: DFHXRSP
DFHXG6518D applid APPARENT FAILURE OF ACTIVE

CICS DETECTED. REPLY 'TAKEOVER' OR DFHXG6522I applid Sign off normal from the CAVM
'IGNORE' assumed.
Explanation: This is an action message issued from the CICS Explanation: This is an informational message issued from
task. It is issued when the current value of the active CICS the CICS task. It indicates that CICS has assumed that the
appears to have failed. active CICS has signed off from the CAVM. This is likely to
System action: If the reply is 'TAKEOVER', CICS requests the occur when the alternate CICS is running on CPC 1 and:
CAVM to initiate takeover. 1. Active CICS is started on CPC 2.
2. CPC 2 is reinitialized.
If the reply is 'IGNORE', CICS assumes one of the following: 3. Active CICS is restarted on CPC 2.
v The active CICS system recovers from the apparent failure. System action: CICS processing is terminated.
v The active CICS system is restarted. User response: None.
v The CEBT PERFORM TAKEOVER command is used to Module: DFHXRSP
initiate takeover.
Subsequent events may mean that the user need not reply to Destination: Console
message DFHXG6518. Examples of this are :
v If CICS is notified that the active CICS system has recovered
DFHXG6523I applid CAVM failure detected. CICS cannot
from the apparent failure reported by message DFHXG6516,
continue as Alternate.
messages DFHXG6517 and DFHXG6519 are sent to the
console.
v If CICS is notified that the active CICS system has signed
CAVM has failed. Messages are produced by the CAVM to
off abnormally from the CAVM, messages DFHXG6511 and
note the reasons for failure.
DFHXG6519 are sent to the console.
v If takeover is initiated (from the alternate CICS system) at
User response: Correct the error.
the same time as the active CICS recovers from the apparent
Module: DFHXRSP
failure reported by message DFHXG6516, messages
DFHXG6513 and DFHXG6539 are sent to the console. XMEOUT Parameter: applid
User response: Determine the reason for the apparent failure Destination: Console
of the active CICS. If possible, resolve the failure and make
the appropriate reply.
Module: DFHXRSP DFHXG6524I applid CAVM error detected. CICS cannot
Destination: Console continue as Alternate.
DFHXG6519I applid The reply to message DFHXG6518 is CAVM has detected an error that prevents CICS from
assumed to be IGNORE. continuing as an alternate.
the CICS task. It indicates that CICS no longer requires the This would be the case, for example, where the alternate CICS
user to respond to message DFHXG6518. has been unable to keep up with the messages generated by
System action: CICS initialization continues. the active CICS.
User response: None. Messages are produced by the CAVM to note the reasons for
Module: DFHXRSP failure.
XMEOUT Parameter: applid System action: CICS terminates abnormally.
Destination: Console User response: Correct the error.
Module: DFHXRSP
DFHXG6520I applid CICS shutdown initiated by CAVM XMEOUT Parameter: applid

event. Destination: Console
the CICS task. CICS initiated shutdown occurs in the DFHXG6539I applid The reply to message DFHXG6518 is
following situations: assumed to be TAKEOVER.
1. CICS is notified that active CICS has signed off normally Explanation: This is an informational message issued from
from the CAVM. Message DFHXG6507 is sent to the the CICS task. It indicates that CICS no longer requires the
console. user to respond to message DFHXG6518.
2. CICS is notified that active CICS has been restarted "in System action: CICS initialization continues.
place". Message DFHXG6511 is sent to the console. User response: None.
3. CICS assumes that the active CICS has signed off normally Module: DFHXRSP
from the CAVM. Message DFHXG6522 is sent to the
console. XMEOUT Parameter: applid
System action: CICS terminates normally, but note that Destination: Console
takeover does not occur if (active) CICS fails.

DFHXG6680I applid TIME-OF-DAY CLOCK DIFFERENCE DFHXG6683I applid XRF clock synchronization ended
IS AT LEAST sss SECONDS. Explanation: This is an informational message issued from
Explanation: This is an informational message issued from the CICS task. The time-of-day clock on the alternate CPC is
the CICS task. Active CICS and alternate CICS systems are now later than that on the active CPC; time dependent
executing on different CPCs, and the time-of-day clock on the processing can be resumed.
alternate CPC is earlier than that on the active CPC. If System action: CICS initialization continues.
takeover occurs then some CICS processing will have to be User response: None.
delayed until the time-of-day clock on the alternate CPC is Module: DFHXRA
later than that on the active CPC. The CAVM has estimated
the lower bound to the clock difference and this is at least 15
seconds; the message contains the estimated difference. Note Destination: Console
that the lower bound may change as more surveillance signals
are processed by the CAVM. This may be the case within the
first 3 to 5 surveillance signals of the active CICS starting. An
elapsed time of some 10 seconds. This message is repeated as
necessary.
User response: Ensure that the time-of day clocks are
synchronized as closely as possible. Note that takeover times
may be increased if the difference in values is significant.
Module: DFHXRSP
DFHXG6681I applid TIME-OF-DAY CLOCK DIFFERENCE

IS AT MOST sss SECONDS.
the CICS task. Active CICS and alternate CICS systems are
executing on different CPCs, and the time-of-day clock on the
alternate CPC is earlier than that on the active CPC. If
takeover occurs then some CICS processing will have to be
delayed until the time-of-day clock on the alternate CPC is
later than that on the active CPC. The CAVM has estimated
the upper bound to the clock difference and this is at least 15
seconds; the message contains the estimated difference. Note
that the upper bound may change as more surveillance signals
are processed by the CAVM; message DFHXG6681 will be
repeated as necessary.
User response: Ensure that the time-of day clocks are
synchronized as closely as possible. Note that takeover times
may be increased if the difference in values is significant.
Module: DFHXRSP
DFHXG6682I applid XRF clock synchronization started

the CICS task. The time-of-day clock on the alternate CPC is
earlier than that on the active CPC; time dependent processing
must be suspended. Such processing is delayed until the
time-of-day clock value on the alternate is later than that on
the active CPC when the active job terminated.
System action: Some CICS initialization continues.
User response: Ensure that the time-of-day clocks are
synchronized as closely as is possible. Note that takeover
times may be increased if the difference in values is
significant.
Module: DFHXRA

DFHXM0001 • DFHXM0004
DFHXMxxxx messages
User response: This indicates a possible error in CICS code.
DFHXM0001 applid An abend (code aaa/bbbb) has occurred
occurred in module modname. This implies that there may be CICS may not have been terminated. If the message occurs
an error in the CICS code. Alternatively, unexpected data has once and module modname is not crucial to the running of
been input, or storage has been overwritten. your CICS system, you may decide to continue to run and
bring CICS down at a convenient time to resolve the problem.
applicable), followed by a 4-digit alphanumeric CICS code. If the message recurs or if you cannot run without the full use
The VSE code is a system completion code, for example 0C1. of module modname, you should bring CICS down in a
If an VSE code is not applicable, this field is filled with three controlled shutdown.
referring to a CICS message (for example, AKEA is a CICS You need further assistance from IBM to resolve this problem.
abend code; 1310 refers to message DFHTS1310). See Part 4 of the CICS Problem Determination Guide for
System action: An exception entry is made in the trace table. guidance on how to proceed.
A system dump is taken, unless you have specifically Module: DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD,
suppressed dumps in the dump table. DFHXMDM, DFHXMER, DFHXMFD, DFHXMIQ, DFHXMLD,
DFHXMQD, DFHXMQC, DFHXMRP, DFHXMSR, DFHXMTA,
CICS continues unless you have specified in the dump table DFHXMXD, DFHXMXE
terminated directly if the error occurred in a crucial XM XMEOUT Parameters: applid, X'code',modname
domain module. Destination: Console

symptom string for this problem. DFHXM0004 applid A possible loop has been detected at
User response: If CICS is still running, it is necessary to offset X'offset' in module modname.
decide whether to terminate CICS. Explanation: A CICS function is taking more time to process
Look up the VSE code, if there is one, in "OS/390 API Abend module modname at offset X'offset'. This is the offset of the
Codes" in section "VSE/Advanced Functions Codes & SVC instruction which happened to be executing at the time when
Errors" of z/VSE Messages and Codes - Volume 1. the error was detected.
Next, look up the CICS alphanumeric code in “Transaction System action: An exception entry is made in the trace table.
Abend Codes (CICS Transaction Server for VSE/ESA)” on A system dump is taken unless you have specifically
page 453 for further guidance. suppressed the dump (by a user exit program at the XDUREQ
If module modname is not crucial to the running of your CICS exit, in the dump table or by global system dump
system, you may decide to continue to run and bring CICS suppression). CICS processing continues unless you have
down at a convenient time to resolve the problem. specified in the dump table that CICS should terminate.
If you cannot run without the full use of module modname you Message DFHME0116 is normally produced containing the
should bring CICS down in a controlled shutdown. symptom string for this problem.
You need further assistance from IBM to resolve this problem. necessary to decide whether the problem is serious enough to
See Part 4 of the CICS Problem Determination Guide for bring CICS down.
Module: DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD, Since some CICS functions can use a lot of CPU time, this
DFHXMDM, DFHXMER, DFHXMFD, DFHXMIQ, DFHXMLD, message may have been caused by a long-running function. So
DFHXMQD, DFHXMQC, DFHXMRP, DFHXMSR, DFHXMTA, there may not be an error. Usually, CICS purges a CICS
DFHXMXD, DFHXMXE function which exceeds the runaway task time interval which
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname parameter (ICVR is measured in milliseconds). This means
Destination: Console that execution of module modname is terminated and CICS
continues.
DFHXM0002 applid A severe error (code X'code') has If you have specifies ICVR=0 and you consider that module
occurred in module modname. modname has gone into a loop, you have to terminate CICS in
Explanation: An error has been detected in module modname. order to terminate the runaway function.
temporarily online using the CEMT transaction.
table.
need further assistance from IBM to resolve the problem. See
terminated directly if the error is critical.
how to proceed.
Message DFHME0116 is normally produced containing the Module: DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD,
symptom string for this problem. DFHXMDM, DFHXMER, DFHXMFD, DFHXMIQ, DFHXMLD,

DFHXMQD, DFHXMQC, DFHXMRP, DFHXMSR, DFHXMTA, XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
DFHXMXD, DFHXMXE transname
Destination: CSKL
DFHXM0110 date time applid Transaction definition transid1
DFHXM0101 date time applid terminal userid tranid has been installed with the same
TRANSACTION definition entry for REMOTENAME and REMOTESYSTEM as
transname has been added. existing definition transid2.
Explanation: This is an audit log message indicating that Explanation: Transaction definition transid1 has been installed
transaction definition entry transname has been added to the with the same REMOTENAME and REMOTESYSTEM as
system using the INSTALL command. transaction definition transid2.
If this CICS system routes a transaction to the CICS system
named as the REMOTESYSTEM of both the definitions and
that transaction issues an EXEC CICS START request for the
is suppressed.
transaction-id named as the REMOTENAME of transid1 and
transid2, CICS can either attach transid1 or transid2 on the local
system to satisfy the START request.
System action: The install of transaction definition transid1
continues normally.
Module: DFHXMXD If an EXEC CICS START request is issued on a remote system
as described in the message explanation, CICS attaches
transid1 and not transid2 on the local system.
transname
Destination: CSKL CICS does not always resolve this ambiguity in the same way
after a warm or emergency restart, however.
User response: This situation usually causes no problems
DFHXM0103 date time applid terminal userid tranid because the correct transaction is attached in the remote
TRANSACTION definition entry for system. However, the correct transaction in the local system
transname has been deleted. may not have been attached and this can manifest itself in the
Explanation: This is an audit log message indicating that following ways:
transaction definition entry transname has been deleted from v Inconsistent statistics being accumulated in the local system.
the system using the CEMT or EXEC CICS DISCARD v The incorrect TRPROF being used when routing the START
command. request back over to the remote system.
v terminal is the netname or termid of the terminal associated v CEMT INQUIRE TASK showing the wrong set of
with the transaction issuing the message. If there is no transactions running in the local system.
is suppressed. Although these are not necessarily problems, you may want to
v userid is the user identifier of the user associated with the check the definitions of the remote transactions in this system
transaction issuing the message. in case they have been defined incorrectly.
System action: The system continues normally. If remote START requests are issued as described, and it does
User response: None. matter which transaction CICS attaches in the local system,
Module: DFHXMDD you should modify and reinstall the transaction definition that
should not be attached. This removes any ambiguity.
Module: DFHXMXD
transname
Destination: CSKL XMEOUT Parameters: date, time,applid, transid1, transid2
Destination: CSMT
DFHXM0105 date time applid terminal userid tranid
TRANSACTION definition entry for DFHXM0111 date time applid Catalog failure while
transname has been replaced. processing {INSTALL | SET | DISCARD}
Explanation: This is an audit log message indicating that request for transaction definition transid.
transaction definition entry transname has been replaced in the Explanation: An error has occurred while altering the catalog
system using the CEDA INSTALL or EXEC CICS CREATE during the processing of an install, set, or discard request for
command. transaction definition transid.
v terminal is the netname or termid of the terminal associated System action: The request continues as normal.
Depending upon the error that has occurred with the catalog,
terminal associated with the transaction, the terminal name there may be severe problems if a warm or emergency restart
is suppressed. of CICS is attempted. The catalog domain will have issued a
v userid is the user identifier of the user associated with the message outlining the problem in this case.
v tranid is the transaction issuing the message. Alternatively the problem may only be local to the catalog
System action: The system continues normally. record containing the image of transaction definition transid
User response: None. and the following problems may occur only on a warm or
Module: DFHXMXD emergency restart.

INSTALL TASKREQ was expected, no action is required. However,

If it is a reinstall, the old version of the transaction transaction definition transid2 should be modified on the CSD
definition is recovered. If it is an install, the so that it no longer specifies the TASKREQ.
transaction definition is not recovered.
If the TASKREQ has been removed in error, reinstall
SET The change requested by the SET is not recovered.
transaction definition transid2 to reinstate its TASKREQ.
Instead the transaction definition is recovered to the Transaction definition transid1 should be modified on the CSD
state prior to the SET request being issued. so that it no longer specifies the TASKREQ.
DISCARD Module: DFHXMXD
The transaction definition is recovered on the restart
even though it is currently discarded. XMEOUT Parameters: date, time,applid, transid1, taskreq,
User response: No immediate action is required. Consider transid2
performing a cold start the next time CICS is restarted to Destination: CSMT
remedy the problem. If a cold start is not appropriate and the
problem is only localized to transaction definition transid,
DFHXM0114 date time applid The install of transaction
remedy the effects outlined for each case previously. definition transid1 has removed XTRANID
For example, X'xtranid' of transid2.
INSTALL Explanation: Transaction definition transid1 has been installed
Reinstall the tranclass definition after the restart. with a XTRANID of xtranid. However, XTRANID xtranid
SET Reissue the SET command after CICS has been currently invokes transaction definition transid2.
System action: The install of transid1 continues as normal.
restarted.
DISCARD The XTRANID xtranid now invokes transaction definition
Reissue the DISCARD command after CICS has transid1 and not transid2 as previously.
been restarted. User response: If removal of transaction definition transid2's
XTRANID was expected, no action is required. However,
If the catalog problem persists after the restart, you need transaction definition transid2 should be modified on the CSD
further assistance from IBM. See Part 4 of the CICS Problem so that it no longer specifies the XTRANID.
Determination Guide for guidance on how to proceed. If the XTRANID has been removed in error, reinstall
Module: DFHXMDD, DFHXMXD transaction definition transid2 to reinstate its XTRANID.
XMEOUT Parameters: date, time,applid, {1=INSTALL, Transaction definition transid1 should be modified on the CSD
so that it no longer specifies the XTRANID.
2=SET,3=DISCARD}, transid
Module: DFHXMXD
XMEOUT Parameters: date, time,applid, transid1,
X'xtranid',transid2
DFHXM0112 date time applid The install of transaction Destination: CSMT
definition transid1 has removed ALIAS alias
of transid2.
Explanation: Transaction definition transid1 has been installed DFHXM0115 date time applid The install of transaction
with an ALIAS of alias. However, ALIAS alias currently definition transid1 has removed TPNAME
invokes transaction definition transid2. tpname of transid2.
System action: The install of transid1 continues as normal. Explanation: Transaction definition transid1 has been installed
with a TPNAME of tpname. However, TPNAME tpname
The ALIAS alias now invokes transaction definition transid1
currently invokes transaction definition transid2.
and not transid2 as previously.
System action: The install of transid1 continues as normal.
User response: If removal of transaction definition transid2's
ALIAS was expected, no action is required. However, The TPNAME tpname now invokes transaction definition
transaction definition transid2 should be modified on the CSD transid1 and not transid2 as previously.
so that it no longer specifies the ALIAS. User response: If removal of transaction definition transid2's
TPNAME was expected, no action is required. However,
If the ALIAS has been removed in error, reinstall transaction
transaction definition transid2 should be modified on the CSD
definition transid2 to reinstate its ALIAS. Transaction definition
so that it no longer specifies the TPNAME.
transid1 should be modified on the CSD so that it no longer
specifies the ALIAS. If the TPNAME has been removed in error, reinstall
Module: DFHXMXD transaction definition transid2 to reinstate its TPNAME.
Transaction definition transid1 should be modified on the CSD
XMEOUT Parameters: date, time,applid, transid1, alias, transid2
so that it no longer specifies the TPNAME.
Destination: CSMT
Module: DFHXMXD
XMEOUT Parameters: date, time,applid, transid1, tpname,
DFHXM0113 date time applid The install of transaction transid2
definition transid1 has removed TASKREQ Destination: CSMT
taskreq of transid2.
Explanation: Transaction definition transid1 has been installed
with a TASKREQ of taskreq. However, TASKREQ taskreq DFHXM0116 date time applid PROGRAM parameter missing
currently invokes transaction definition transid2. from transaction definition transid.
System action: The install of transid1 continues as normal. PROGRAM is required because
REMOTESYSTEM is the same as the local
The TASKREQ taskreq now invokes transaction definition
system.
transid1 and not transid2 as previously.
Explanation: Transaction definition transid has been installed
User response: If removal of transaction definition transid2's
without a PROGRAM parameter. Since it has been defined

with a REMOTESYSTEM equal to the local system, a program XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
is required if the transaction is executed on this system. tranclassname
System action: The install of transid continues as normal. Destination: CSKL
Any attempt to run the transaction transid will fail because
there is no program to link to.
User response: This message is issued for information only. DFHXM0205 date time applid terminal userid tranid
There is no problem if transaction transid is not executed on TRANCLASS definition entry for
this system. If it is to be executed, the definition of transid tranclassname has been replaced.
needs to be modified and then reinstalled. Explanation: This is an audit log message indicating that
tranclass definition entry transname has been replaced in the
If the transaction is not executed, you may wish to investigate
system using the INSTALL command.
why the transaction definition has been installed. It could be
that the transaction is defined in an RDO group that is shared
between a number of different CICS systems. For example
transid may be TTT1 in the following pair of definitions used terminal associated with the transaction, the terminal name
to implement transaction routing to this local system CICB. is suppressed.
Transaction Remotesystem Remotename Program
TTT1 CICB TTT2 -
TTT2 - - PROGA v tranid is the transaction issuing the message.
In this example, a single definition would suffice if the
Module: DFHXMCL
transaction was made to have the same name on this system.
Transaction Remotesystem Remotename Program XMEOUT Parameters: date, time,applid, terminal, userid, tranid,
TTT1 CICB TTT1 PROGA tranclassname
Module: DFHXMXD Destination: CSKL
XMEOUT Parameters: date, time,applid, transid

Destination: CSMT DFHXM0211 date time applid Catalog failure while
processing {INSTALL | SET | DISCARD}
request for tranclass definition tranclassname.
DFHXM0201 date time applid terminal userid tranid Explanation: An error has occurred while altering the catalog
TRANCLASS definition entry for during the processing of an install, set, or discard request for
tranclassname has been added. tranclass definition tranclassname.
Explanation: This is an audit log message indicating that System action: The request continues normally.
tranclass definition entry tranclassname has been added to the
system using the INSTALL command. Depending upon the error that has occurred with the catalog,
v terminal is the netname or termid of the terminal associated there may be severe problems if a warm or emergency restart
with the transaction issuing the message. If there is no of CICS is attempted. The catalog domain will have issued a
terminal associated with the transaction, the terminal name message outlining the problem in this case.
is suppressed.
Alternatively the problem may only be local to the catalog
record containing the image of tranclass definition
tranclassname and the following problems may occur only on a
warm or emergency restart.
INSTALL
If it is a reinstall, the old version of the tranclass
Module: DFHXMCL
definition is recovered. If it is an install, the tranclass
XMEOUT Parameters: date, time,applid, terminal, userid, tranid, definition was not recovered.
tranclassname SET The change requested by the SET is not recovered.
Destination: CSKL Instead the tranclass definition is recovered to the
state it was in before the SET request was issued.
DISCARD
DFHXM0203 date time applid terminal userid tranid The tranclass definition is recovered on the restart
TRANCLASS definition entry for even though it is currently discarded.
tranclassname has been deleted. User response: No immediate action is required. To fully
Explanation: This is an audit log message indicating that resolve the problem, consider performing a cold start the next
tranclass definition entry tranclasssname has been deleted from time CICS is restarted. If a cold start is not appropriate and
the system using the DISCARD command. the problem is only localized, to tranclass definition
v terminal is the netname or termid of the terminal associated tranclassname, you can resolve each of the symptoms
with the transaction issuing the message. If there is no separately.
is suppressed. For example:
v userid is the user identifier of the user associated with the INSTALL
transaction issuing the message. Reinstall the tranclass definition after CICS has been
v tranid is the transaction issuing the message. restarted.
System action: The system continues normally. SET Reissue the SET command after CICS has been
User response: None. restarted.
Module: DFHXMCL

DISCARD
DFHXM0301 date time applid An attempt to link to the
Reissue the DISCARD command after CICS has
user-replaceable transaction restart program
been restarted.
(DFHREST) has failed for task number
tasknum. Transaction restart is not performed
If the catalog problem persists after the restart, you may need for transaction tranid.
further assistance from IBM to resolve the problem. See Part 4 Explanation: A restartable transaction abended and the
of the CICS Problem Determination Guide for guidance on how transaction manager attempted to link to the user-replaceable
to proceed. transaction restart program (DFHREST) but the link has failed.
Module: DFHXMCL Likely reasons are:
XMEOUT Parameters: date, time,applid, {1=INSTALL, v DFHREST is not defined (and not autoinstalled)
2=SET,3=DISCARD}, tranclassname v DFHREST is not present in any sublibrary of the LIBDEF
Destination: Console and Transient Data Queue CSMT search chain for the CICS startup job stream.
v DFHREST has been linked with AMODE(24).
System action: The transaction is not restarted.
DFHXM0212 applid Transaction transid has been attached User response: If the problem is not rectified, a message is
with unknown tranclass tranclassname. issued each time the link to DFHREST fails. To avoid this,
Explanation: Transaction transid has just been attached. It is ensure that DFHREST is properly defined and present in a
defined as belonging to tranclass tranclassname but sublibrary of the LIBDEF search chain for the CICS startup job
tranclassname does not exist. stream.
This message is only issued the first time transaction transid is See the CICS Customization Guide for more information about
attached with the unknown tranclass. user-replaceable programs.
System action: The attach of transaction transid proceeds as Module: DFHXMTA.
normal but without being subject to any tranclass scheduling
constraints. XMEOUT Parameters: date, time,applid, tasknum, tranid
User response: If transaction transid should belong to Destination: Console and Transient Data Queue CSMT
tranclass tranclassname, install that tranclass. If not, modify the
transaction definition for transid as appropriate, and reinstall. DFHXM0302 applid An abend abcode occurred in the
The CEDA CHECK command can be used to ensure that each user-replaceable transaction restart program
of the tranclasses referenced by transaction definitions are (DFHREST) under task number tasknum.
defined within the same startup GRPLIST. Transaction restart is not performed for
transaction tranid.
Explanation: A restartable transaction abended and the
transaction manager linked to the user-replaceable transaction
data queue.
restart program (DFHREST). DFHREST abended.
Module: DFHXMQC
System action: The transaction is not restarted.
XMEOUT Parameters: applid, transid,tranclassname User response: If the problem is not rectified, a message is
Destination: Console issued each time DFHREST abends. To avoid this, fix the
problem in DFHREST and ensure that it is properly defined
and present in a sublibrary specified in the LIBDEF search
DFHXM0213 applid Insufficient storage for system attach of chain for the CICS startup job stream.
transaction transid.
Explanation: There is insufficient storage for a new task to be See the CICS Customization Guide for more information about
created for the attach of transaction transid. user-replaceable programs.
Module: DFHXMTA.
Since the majority of the storage required for the new task is
obtained from DSA storage, CICS is probably short on storage XMEOUT Parameters: applid, abcode,tasknum, tranid
in one of the DSAs. Destination: Console
System action: The attach request is queued. It is retried later
when more storage should have become available. If the
DFHXM0303 applid A severe error (code X'code') has
retried attach fails, it is queued and retried repeatedly until it
occurred while initializing task number
succeeds.
tasknum with transaction identifier tranid.
User response: If CICS is short on storage, message
Terminal termid has not been released. The
DFHSM0133 is also issued. Refer to that message for advice
task is suspended indefinitely.
on how to resolve the condition.
Explanation: An internal error has prevented the
If message DFHSM0133 has not been issued, the problem has initialization of task number tasknum with identifier tranid.
been caused by insufficient VSE storage. In this case consider
The task cannot run and cannot be abended. The principal
lowering the EDSALIM of the system to increase the amount
facility of the task is a terminal. No message may be sent to
of available storage.
the terminal and it is unusable by CICS. Rather than terminate
CICS, the transaction manager keeps CICS running and
Note: Do not attempt to reroute this message to a transient preserves its integrity by suspending the task.
data queue.
Module: DFHXMAT The suspended task will hold its MXT slot until CICS is
terminated.
XMEOUT Parameters: applid, transid
Destination: Console Note that the task may hold resources (for example, locks and
enqueues) so you should cancel CICS at your earliest

convenience. Otherwise you may risk other tasks being Module: DFHXMTA.
prevented from running because they also need access to the
XMEOUT Parameters: applid, X'code',tasknum, tranid, tdqueue
same resources. You may wish to add a dump table entry to
always terminate CICS on this message.
System action: The task is suspended indefinitely. First
failure diagnostics should be produced by the component DFHXM0305 applid A severe error (code X'code') has
which first detects the error. The transaction manager also occurred while initializing task number
takes a dump. Message DFHME0116 is normally produced tasknum with transaction identifier tranid. The
containing the symptom string for this problem. interval control element has not been
The terminal principal facility of the task is unusable by CICS released. The task is suspended indefinitely.
until CICS is canceled. Explanation: An internal error has prevented the
initialization of task number tasknum with identifier tranid.
The task is suspended with a resource type of FOREVER and
a resource name of DFHXMTA. The task cannot run and cannot be abended. The principal
User response: You must cancel CICS if you need to release facility of the task is an interval control element. Any start
the terminal associated with the task. You cannot quiesce CICS data associated with the ICE will not be retrieved. Rather than
since this task will not terminate. You cannot purge or terminate CICS, the transaction manager keeps CICS running
force-purge the task. and preserves its integrity by suspending the task.
Note the error code X'code'. You need further assistance from The suspended task will hold its MXT slot until CICS is
IBM to resolve this problem. See Part 4 of the CICS Problem terminated.
Determination Guide for guidance on how to proceed. Note that the task may hold resources (for example, locks and
Module: DFHXMTA. enqueues) so you should cancel CICS at your earliest
XMEOUT Parameters: applid, X'code',tasknum, tranid, termid convenience. Otherwise you may risk other tasks being
Destination: Console prevented from running because they also need access to the
same resources. You may wish to add a dump table entry
always to terminate CICS on this message.
DFHXM0304 applid A severe error (code X'code') has System action: The task is suspended indefinitely. First
occurred while initializing task number failure diagnostics should be produced by the component
tasknum with transaction identifier tranid. which first detects the error. The transaction manager also
Transient data queue tdqueue has not been takes a dump. Message DFHME0116 is normally produced
released. The task is suspended indefinitely. containing the symptom string for this problem.
initialization of task number tasknum with identifier tranid. The task is suspended with a resource type of FOREVER and
a resource name of DFHXMTA.
The task cannot run and cannot be abended. The principal User response: You must cancel CICS if you need to destroy
facility of the task is a transient data queue. The TD queue the ICE. Any start data will remain in temporary storage until
will not trigger another task until CICS is terminated. Rather it is deleted unless it is nonrecoverable in which case it will
than terminate CICS, the transaction manager keeps CICS disappear on the next cold or emergency restart of CICS. You
running and preserves its integrity by suspending the task. cannot quiesce CICS since this task will not terminate. You
cannot purge or force-purge the task.
The suspended task will hold its MXT slot until CICS is
terminated. Note the error code X'code'. You need further assistance from
IBM to resolve this problem. See Part 4 of the CICS Problem
Note that the task may hold resources ( for example, locks and
Module: DFHXMTA.
convenience. Otherwise you risk other tasks being prevented
from running because they also need access to the same XMEOUT Parameters: applid, X'code',tasknum, tranid
resources. You may wish to add a dump table entry always to Destination: Console
terminate CICS on this message.
failure diagnostics should be produced by the component DFHXM0306 applid A severe error (code X'code') has
which first detects the error. The transaction manager also occurred while initializing task number
takes a dump. Message DFHME0116 is normally produced tasknum with transaction identifier tranid. The
containing the symptom string for this problem. task is suspended indefinitely.
The task is suspended with a resource type of FOREVER and initialization of task number tasknum with identifier tranid.
User response: You must cancel CICS if you need to release The task cannot run and cannot be abended. The task has no
the TD queue associated with the task. You cannot quiesce principal facility bound to it. Rather than terminate CICS, the
CICS since this task will not terminate. You cannot purge or transaction manager keeps CICS running and preserves its
force-purge the task. integrity by suspending the task.
Determination Guide for guidance on how to proceed. Note that the task may hold resources (for example, locks and
Note: Do not attempt to reroute this message to a transient convenience. Otherwise you may risk other tasks being
data queue. prevented from running because they also need access to the


DFHXM0308 applid A severe error (code X'code') has
occurred while terminating task number
tasknum with transaction identifier tranid. The
failure diagnostics should be produced by the component
transient data queue tdqueue has not been
which first detects the error. The transaction manager also
released. The task is suspended indefinitely.
takes a dump. Message DFHME0116 is normally produced
Explanation: An internal error has prevented the termination
of task number tasknum with identifier tranid. It is not possible
The task is suspended with a resource type of FOREVER and to abend the task. The principal facility of the task is a
a resource name of DFHXMTA. transient data queue. The TD queue will not trigger another
User response: You must cancel CICS if you need to destroy task until CICS is terminated. Rather than terminate CICS, the
the task. You cannot quiesce CICS since this task will not transaction manager keeps CICS running and preserves its
terminate. You cannot purge or force purge the task. integrity by suspending the task.
Note that the task may hold resources (for example, locks and
Module: DFHXMTA.
XMEOUT Parameters: applid, X'code',tasknum, tranid convenience. Otherwise you may risk other tasks being
Destination: Console prevented from running because they also need access to the
same resources. You may wish to add a dump table entry
always to terminate CICS on this message.
DFHXM0307 applid A severe error (code X'code') has System action: The task is suspended indefinitely. First
occurred while terminating task number failure diagnostics should be produced by the component
tasknum with transaction identifier tranid. The which detected the error. The transaction manager also takes a
terminal termid has not been released. The dump. Message DFHME0116 is normally produced containing
task is suspended indefinitely. the symptom string for this problem.
of task number tasknum with identifier tranid. It is not possible The task is suspended with a resource type of FOREVER and
to abend the task or send a message to its terminal principal a resource name of DFHXMTA.
facility. Rather than terminate CICS, the transaction manager User response: You must cancel CICS if you need to free up
keeps CICS running and preserves its integrity by suspending the transient data queue associated with the task. You cannot
the task. quiesce CICS since this task will not terminate. You cannot
purge or force purge the task.
terminated. Note the error code X'code'. You need further assistance from
Note that the task may hold resources (for example, locks and Determination Guide for guidance on how to proceed.
convenience. Otherwise you may risk other tasks being
data queue.
Module: DFHXMTA.
System action: The task is suspended indefinitely. First XMEOUT Parameters: applid, X'code',tasknum, tranid, tdqueue
failure diagnostics should be produced by the component Destination: Console
which detected the error. The transaction manager also takes a
dump. Message DFHME0116 is normally produced containing
the symptom string for this problem. DFHXM0309 applid A severe error (code X'code') has
occurred while terminating task number
The terminal principal facility of the task is unusable until tasknum with transaction identifier tranid. The
CICS is canceled. interval control element has not been
User response: You must cancel CICS if you need to free up
to abend the task. The principal facility of the task is an
the terminal associated with the task. You cannot quiesce CICS
interval control element. Rather than terminate CICS, the
since this task will not terminate. You cannot purge or force
transaction manager keeps CICS running and preserves its
purge the task.
integrity by suspending the task.
Note the error code X'code'. You need further assistance from
terminated.
Module: DFHXMTA. Note that the task may hold resources (for example, locks and
XMEOUT Parameters: applid, X'code',tasknum, tranid, termid
convenience. Otherwise you may risk other tasks being
failure diagnostics should be produced by the component

which detected the error. The transaction manager also takes a

DFHXM0501 applid CICS cannot satisfy request for MXT.
dump. Message DFHME0116 is normally produced containing
Value mxtvalue has been used instead.
the symptom string for this problem.
Explanation: The value entered for MXT cannot be handled
The task is suspended with a resource type of FOREVER and by the system. mxtvalue is the largest value for which CICS
a resource name of DFHXMTA. has been able to acquire task storage.
User response: You must cancel CICS if you need to destroy
The majority of the task storage required is now acquired from
the ICE associated with the task. Any start data remains in
CICS DSAs.
temporary storage until it is deleted unless it is
System action: The system continues to run with a MXT
nonrecoverable, in which case it disappears on the next cold
value of mxtvalue.
or emergency restart of CICS. You cannot quiesce CICS since
User response: Check that the original value entered for
this task does not terminate. You cannot purge or force purge
MXT was correctly typed. If the value is mistyped, use CEMT
the task.
to amend the MXT value (you are unlikely to be able to force
Note the error code X'code'. You need further assistance from the value higher). Remember that MXT now only includes
IBM to resolve this problem. See Part 4 of the CICS Problem user tasks and so it should not need to be set to a value as
Determination Guide for guidance on how to proceed. high as in previous releases.
Module: DFHXMTA.
If the value mxtvalue is acceptable, no action is necessary.
XMEOUT Parameters: applid, X'code',tasknum, tranid
If the value mxtvalue is too small, check to see which
programs, apart from CICS, are running in this region. To
relieve the storage constraint, either increase the DSALIM or
DFHXM0310 applid A severe error (code X'code') has EDSALIM of the system to give CICS more storage for its own
occurred while terminating task number use. For further details about storage allocation at
tasknum with transaction identifier tranid. If initialization, see the CICS System Definition Guide.
the task had a principal facility, it has been Module: DFHXMSR
XMEOUT Parameters: applid, mxtvalue
to abend the task. Rather than terminate CICS, the transaction
manager keeps CICS running and preserves its integrity by DFHXM0502 applid A catalog failure has occurred while
suspending the task. saving the MXT setting.
Explanation: An error has occurred while saving the
requested MXT setting on the catalog.
terminated.
System action: The requested MXT change request continues
Note that the task may hold resources (for example, locks and as normal.
Depending upon the error that has occurred with the catalog,
convenience. Otherwise you risk other tasks being prevented
there may be severe problems if a warm or emergency restart
from running because they also need access to the same
of CICS is attempted. The catalog domain will have issued a
resources. You may wish to add a dump table entry always to
message outlining the problem in this case.
terminate CICS on this message.
System action: If the task had a principal facility, it has been Alternatively the problem may only be local to the catalog
released. If this was a terminal, the terminal should be usable record containing the MXT value and only it may not be
by CICS. recovered on a warm or emergency restart.
User response: No immediate action is required. Consider
The task is suspended indefinitely. First failure diagnostics
performing a cold start, with the required MXT value specified
should be produced by the component which detects the error.
in the SIT the next time CICS is restarted. If a cold start is not
The transaction manager also takes a dump. Message
appropriate, add MXT as a SIT override specifying the
required MXT value.
Module: DFHXMSR
User response: You cannot quiesce CICS since this task will
not terminate. You cannot purge or force-purge the task.
DFHXM0503 applid CICS cannot support minimum MXT
Note the error code X'code'.
value of minmxt. CICS is terminated.
You need further assistance from IBM to resolve this problem. Explanation: A severe lack of storage has resulted in CICS
See Part 4 of the CICS Problem Determination Guide for not being able to acquire enough task storage to satisfy even
guidance on how to proceed. the minimum MXT value of minmxt.
Module: DFHXMTA.
CICS cannot perform any useful work without minmxt number
XMEOUT Parameters: applid, X'code',tasknum, tranid of user tasks.
Destination: Console System action: CICS is terminated.
User response: Investigate why there is insufficient storage
for CICS to support such a low number of user tasks.
To relieve the storage constraint, either increase the DSALIM

or EDSALIM of the system to give CICS more storage for its

DFHXO6700 • DFHXO6711
own use. For further details about storage allocation at XMEOUT Parameters: applid, minmxt
initialization, see the CICS Installation Guide. Destination: Console
Module: DFHXMSR
DFHXOxxxx messages
terminated after completion of parameter analysis.
DFHXO6700 OPTION STARTING xxx HAS ILLEGAL
User response: Correct the error and resubmit the overseer
SYNTAX.
program.
Explanation: The option xxx has incorrect syntax.
Module: DFHWOSA
System action: The overseer program is abnormally
program. DFHXO6707 VALUE OF option OPTION IS LONGER
Module: DFHWOSA THAN 5 DIGITS.
Destination: Console Explanation: The value of the given numeric option must
occupy no more than five digits.
DFHXO6701 OVERSEER GETVIS FAILURE - PROGRAM
TERMINATING
Explanation: A non-zero return code was received when
program.
attempting to obtain GETVIS storage for the READ/WRITE
Module: DFHWOSA
control block.
terminated.
User response: Increase the partition GETVIS available for DFHXO6708 VALUE OF option OPTION IS
the overseer job. NON-NUMERIC.
Module: DFHWOSA Explanation: The value of the option option must be numeric.
Destination: Console System action: The overseer program is abnormally
DFHXO6702 OVERSEER PARAMETER CHECK FAILURE
program.
- PROGRAM TERMINATING.
Module: DFHWOSA
Explanation: Either the parameter string passed to the
overseer was invalid, or no parameter string was passed to the
overseer.
System action: The overseer program is abnormally DFHXO6709 VALUE OF option OPTION IS LONGER
terminated. THAN 8 CHARACTERS.
User response: Correct the parameter string and resubmit the Explanation: The value of option optionmust occupy no more
job. than eight characters.
Module: DFHWOSA System action: The overseer program is abnormally
Destination: Console terminated after completion of parameter analysis.
program.
DFHXO6703 UNABLE TO SET UP AUTHORIZED
Module: DFHWOSA
FACILITY.
Explanation: Insufficient storage is available to initialize the
authorized facility required by the overseer.
System action: The overseer program is abnormally DFHXO6710 VALUE OF OPTION option IS NEITHER Y
terminated. NOR N.
User response: Ensure that the REGION parameter is Explanation: The value of option option must be either Y(yes)
sufficiently large. or N(no).
Module: DFHWOSA System action: The overseer program is abnormally
Destination: Console terminated after completion of parameter analysis.
program.
DFHXO6705 option OPTION IS MISSING.
Module: DFHWOSA
Explanation: The option option may not be omitted.
User response: Correct the error and resubmit the overseer DFHXO6711 option OPTION IS NO LONGER
program. SUPPORTED.
Module: DFHWOSA Explanation: Option option has been specified in one of the
Destination: Console job control statements used to run the CICS overseer. This
option was supported in a previous release of CICS, but is no
longer supported.
DFHXO6706 CYTIM OPTION MUST BE IN RANGE 20
System action: Option option is ignored. THe overseer
TO 32767.
program continues. parameter analysis.
Explanation: The CYTIM option must fall within the range
User response: Remove the redundant option option from the
20 through 32767.
job.
Module: DFHWOSA

DFHXO6712 • DFHXS0002
Destination: Console OVERSEER WILL TERMINATE.

Explanation: The AB STXIT procedure in the overseer has
been triggered.
DFHXO6712 option IS AN INVALID OPTION KEYWORD. System action: DFHWOSM FUNC=TERM is executed and
Explanation: The specified keyword option is an invalid the overseer job is terminated with VSE user abend code 220
option. and a dump.
System action: Option option is ignored. User response: Use the dump to determine the reason for the
User response: Correct the error. abend.
Module: DFHWOSA Module: DFHWOSB
DFHXO6713 OVERSEER CDLOAD ERROR - PROGRAM DFHXO6715 A PROGRAM CHECK HAS BEEN
TERMINATING. DETECTED. OVERSEER WILL TERMINATE.
Explanation: DFHWOSA has attempted to CDLOAD Explanation: The PC STXIT procedure in the overseer has
DFHWOSB or the users overseer program. This load has failed been triggered.
System action: The overseer program is abnormally System action: DFHWOSM FUNC=TERM is executed and
terminated. the overseer job is terminated with VSE user abend code 221
User response: Increase the partition GETVIS available to the and a dump.
overseer program. User response: Use the dump to determine the reason for the
Module: DFHWOSA abend.
Destination: Console Module: DFHWOSB
DFHXO6714 AN ABEND HAS BEEN DETECTED.
DFHXSxxxx messages
DFHXS0001 applid An abend (code aaa/bbbb) has occurred
Module: DFHXSAD, DFHXSCL, DFHXSDM, DFHXSFL,
DFHXSIS, DFHXSLU, DFHXSPW, DFHXSRC, DFHXSST,
DFHXSXM
If an VSE code is not applicable, this field is filled with three DFHXS0002 applid A severe error (code X'code') has
hyphens. The CICS code is an abend code or a number occurred in module modname.
referring to a CICS message (for example, AKEA is a CICS Explanation: An error has been detected in module modname.
abend code; 1310 refers to message DFHTS1310). The code X'code' is the exception trace point id which uniquely
System action: An exception entry is made in the trace table. identifies what the error is and where the error was detected.
A system dump is taken, unless you have specifically System action: An exception entry (code X'code' in the
suppressed dumps in the dump table. message) is made in the trace table. A system dump is taken,
CICS continues unless you have specified in the dump table unless you have specifically suppressed dumps in the dump
that CICS should terminate. If appropriate, an error return table.
code is sent to the caller of this domain. In this case CICS CICS continues unless you have specified in the dump table
could be terminated by the caller ( for example, the domain that CICS should terminate. If appropriate, an error return
manager, DFHDMDM). A message is issued to this effect. code is sent to the caller of this domain. In this case, CICS
Message DFHME0116 is normally produced containing the could be terminated by the caller (for example, the domain
symptom string for this problem. manager, DFHDMDM). A message is issued to this effect.
User response: Notify the system programmer. If CICS is still Message DFHME0116 is normally produced containing the
running, it is necessary to decide whether to terminate CICS. symptom string for this problem.
Look up the VSE code, if there is one, in "OS/390 API Abend User response: This indicates a possible error in CICS code.
Codes" in section "VSE/Advanced Functions Codes & SVC The severity of its impact depends on the importance of the
Errors" of z/VSE Messages and Codes - Volume 1. function being executed at the time of the error.
Next, look up the CICS alphanumeric code in “Transaction CICS may not have been terminated. If the message occurs
Abend Codes (CICS Transaction Server for VSE/ESA)” on once and module modname is not crucial to the running of
page 453. This tells you, for example, whether the error was a your CICS system, you may decide to continue to run and
program check, an abend, or a runaway, and may give you bring CICS down at a convenient time to resolve the problem.
some guidance concerning user response. If the message recurs or if you cannot run without the full use
If module modname is not crucial to the running of your CICS of module modname, you should bring CICS down in a
system, you may decide to continue to run and bring CICS controlled shutdown.
down at a convenient time to resolve the problem. You need further assistance from IBM to resolve this problem.
If you cannot run without the full use of module modname you See Part 4 of the CICS Problem Determination Guide for
should bring CICS down in a controlled shutdown. guidance on how to proceed.

DFHXS0004 • DFHXS0201I
Module: DFHXSAD, DFHXSCL, DFHXSDM, DFHXSFL, specifically suppressed dumps in the dump table.
DFHXSXM CICS continues unless you have specified in the dump table
Destination: Console If appropriate, an error return code is sent to the caller of this
DFHXS0004 applid A possible loop has been detected at issued to this effect.
detected.
response suggested for these messages.
A system dump is taken, unless you have specifically If CICS is still running, the problem may be a temporary one
suppressed dumps in the dump table. which rights itself if more storage becomes available. If you
return code in "OS/390 API Return Codes" in section
not been terminated, it is necessary to decide whether the
problem is serious enough to bring CICS down. Try decreasing the size limits of the DSAs or EDSAs. Or, try
increasing the size of the whole region, if it is not already at
maximum size. See the CICS System Definition Guide or the
CICS Performance Guide for further information on CICS
storage.
DFHXSXM
that module modname in the message is terminated and CICS
continues. XMEOUT Parameters: applid, X'code',modname, vsecode
CICS in order to terminate the runaway function. DFHXS0200I date time applid External security initialization
If CICS has terminated module modname, and you consider has been successfully tracked.
that it was not a runaway, you should increase the ICVR time Explanation: An external security initialization performed on
interval. You have to bring CICS down at a suitable time to do an active CICS system (via CEMT PERFORM SECURITY, or
this permanently. But you can change the ICVR time interval EXEC CICS SECURITY REBUILD) has been tracked to the
temporarily online, using the CEMT transaction. XRF alternate system, and has completed successfully.
System action: None.
If raising the ICVR time does not solve the problem, you will User response: None. You can suppress this message with
need further assistance from IBM. See Part 4 of the CICS the system initialization parameter, MSGLVL=0.
Problem Determination Guide for guidance on how to proceed. Module: DFHXSWM
DFHXSIS, DFHXSLU, DFHXSPW, DFHXSRC, DFHXSST, XMEOUT Parameters: date, time,applid
DFHXSXM Destination: Console

Destination: Console DFHXS0201I date time applid External security initialization
has been tracked, and has failed with return
code X'xx' and reason code X'yy'.
DFHXS0006 applid Insufficient storage to satisfy Getmain Explanation: An external security initialization was
(code X'code') in module modname. VSE code performed on an active CICS system by use of a CEMT
vsecode. PERFORM SECURITY, or EXEC CICS SECURITY REBUILD.
Explanation: An OS/390 GETMAIN was issued by module
modname, but there was insufficient storage available to satisfy The external security initialization has been tracked to the XRF
the request. alternate system, but has failed with return code xx and
reason code yy.
uniquely identifies the place where the error was detected. xx and yy are the values placed in registers 15 and 0 by the
external security manager.
The code vsecode is the OS/390 GETMAIN return code. System action: CICS provides a system dump of the XRF
System action: An exception entry is made in the trace table alternate system, and continues tracking security
(code X'code'). A system dump is taken, unless you have initializations.

DFHXS0202 • DFHXS1103I
Message DFHME0116 is normally produced containing the It has been tracked to an alternate system but the tracking
symptom string for this problem. data was corrupted in transit.
User response: The security characteristics of the alternate System action: CICS provides a system dump of the alternate
system no longer match those of the active system. Either shut systems, and ceases to track the security initializations.
down the alternate system, perform a security rebuild at
takeover, or accept the difference. Message DFHME0116 is normally produced containing the
Use the return codes in the message, to determine why the User response: The security characteristics of the alternate
security initialization failed. system no longer match those of the active system. Either shut
If the codes are invalid, you will need further assistance from takeover, or accept the difference.
IBM. See Part 4 of the CICS Problem Determination Guide for Module: DFHXSWM
Module: DFHXSWM XMEOUT Parameters: date, time,applid
Destination: CSCS
XMEOUT Parameters: date, time,applid, X'xx', X'yy'
DFHXS1100I applid Security initialization has started.
DFHXS0202 date time applid An attempt to track external security domain initialization has started.
security initialization has failed, tracking System action: System initialization continues.
data could not be sent. User response: None.
Explanation: An external security initialization was
performed on an active CICS system (via CEMT PERFORM This message can be suppressed with the system initialization
SECURITY, or EXEC CICS SECURITY REBUILD). parameter MSGLVL=0.
Module: DFHXSDM
It has not been tracked to an alternate system because the
tracking data could not be sent. XMEOUT Parameter: applid
System action: CICS provides a system dump of the active, Destination: Console
and continues tracking security initializations.
Message DFHME0116 is normally produced containing the DFHXS1101I applid Security initialization has ended.
symptom string for this problem. Explanation: This is an informational message indicating that
User response: The security characteristics of the alternate security domain initialization has completed successfully.
will no longer match those of the active. Either shut down the System action: System initialization continues.
alternate, perform a security rebuild at takeover, or accept the User response: None.
difference.
Module: DFHXSWM This message can be suppressed with the system initialization
parameter MSGLVL=0.
XMEOUT Parameters: date, time,applid Module: DFHXSDM
Destination: CSCS
DFHXS0203 date time applid An attempt to track external
security initialization has failed, tracking
data could not be received. DFHXS1102I applid Security is inactive.
Explanation: An external security initialization was Explanation: This is an informational message indicating that
performed on an active CICS system (via CEMT PERFORM security is not active.
SECURITY, or EXEC CICS SECURITY REBUILD). System action: System initialization continues.
The external security initialization has not been tracked to an
alternate system because the tracking data could not be This message can be suppressed with the system initialization
received. parameter MSGLVL=0.
Module: DFHXSDM
symptom string for this problem. XMEOUT Parameter: applid
System action: CICS provides a system dump of the alternate Destination: Console
system, and ceases to track the security initializations.
User response: The security characteristics of the alternate
DFHXS1103I applid Default security for userid dfltuser has
system no longer match those of the active system. Either shut
been established.
Explanation: CICS has established a security environment for
takeover, or accept the difference.
the default userid dfltuser.
Module: DFHXSWM
System action: The authorities that are assigned to this
XMEOUT Parameters: date, time,applid userid by the external security manager will be used in CICS
Destination: CSCS resource checks whenever no other userid has been
established.
DFHXS0204 date time applid An attempt to track external Module: DFHXSDM
security initialization has failed, tracking
data was corrupted. XMEOUT Parameters: applid, dfltuser
Explanation: An external security initialization was Destination: Console Routecodes 2, 9 and 11
performed on an active CICS system (via CEMT PERFORM
SECURITY, or EXEC CICS SECURITY REBUILD).

DFHXS1104 • DFHXS1109
Module: DFHXSRC
DFHXS1104 applid Default security could not be
established for userid dfltuser. The security XMEOUT Parameters: applid, classname, X'safresp', X'safreas',
domain cannot continue, so CICS is X'esmresp', X'esmreas'
terminated. SAF codes are (X'safresp',X'safreas'). Destination: Console Routecodes 2, 9, 10 and 11
Explanation: CICS could not establish a security environment
for the default userid dfltuser. The security domain cannot DFHXS1107 applid Partner-LU profiles for class APPCLU
continue without a default user. The response and reason have been built.
codes (safresp and safreas) returned by the system authorization Explanation: The partner-LU profiles for the class APPCLU
facility (SAF), and the response and reason codes (esmresp and have been successfully loaded into storage by the external
esmreas) returned by the external security manager (ESM) are security manager.
those issued by the RACROUTE REQUEST=VERIFY macro. System action: The profiles are used in subsequent bind
For the meaning of the response and reason codes in the authorization checks for LU6.2 sessions whose CONNECTION
message see "BSM Return Codes" in section "VSE/Advanced definition specifies BINDSECURITY(YES).
Volume 1.
Module: DFHXSRC
User response: Use the external security manager codes to XMEOUT Parameter: applid
determine why the RACROUTE REQUEST=VERIFY operation Destination: Console Routecodes 2, 9, 10 and 11
failed. Then, either correct the errors for the failing default
user and restart CICS, or restart CICS with a different default
userid. DFHXS1108 applid Partner-LU profiles could not be built
Module: DFHXSDM for class APPCLU. SAF codes are
XMEOUT Parameters: applid, dfltuser, X'safresp', X'safreas', (X'esmresp',X'esmreas').
X'esmresp',X'esmreas' Explanation: The partner-LU profiles for the class APPCLU
Destination: Console Routecodes 2, 9, 10 and 11 could not be loaded into storage by the external security
manager. CICS therefore has no APPCLU security profiles. The
DFHXS1105 applid Resource profiles for class classname response and reason codes (safresp and safreas) returned by the
have been built. system authorization facility (SAF), and the response and
Explanation: The security resource profiles for the class reason codes (esmresp and esmreas) returned by the external
classname have been successfully loaded into storage by the security manager (ESM) are those issued by the RACROUTE
external security manager. REQUEST=LIST macro. For the meaning of the response and
System action: The profiles are used in subsequent resource reason codes in the message see "BSM Return Codes" in
checks to determine users' authorizations to access resources section "VSE/Advanced Functions Codes & SVC Errors" of
in the named class. z/VSE Messages and Codes - Volume 1.
User response: None. The build of the profiles was requested by one of the
Module: DFHXSRC following:
XMEOUT Parameters: applid, classname v The initialization of VTAM support in terminal control
Destination: Console Routecodes 2, 9, 10 and 11 v The CEMT command SET VTAM OPEN
v The CEMT command PERFORM SECURITY REBUILD
v A user-supplied transaction invoking the EXEC CICS SET
DFHXS1106 applid Resource profiles could not be built for VTAM OPEN command.
class classname. CICS is terminated. SAF v A user-supplied transaction invoking the EXEC CICS
codes are (X'safresp',X'safreas'). ESM codes are PERFORM SECURITY REBUILD command.
(X'esmresp',X'esmreas'). System action: If the failure occurs during CICS initialization
Explanation: The security resource profiles for the class or PERFORM SECURITY REBUILD, CICS terminates. If the
classname could not be loaded into storage by the external failure occurs during SET VTAM OPEN, the VTAM ACB is
security manager. The response and reason codes (safresp and closed and CICS continues.
safreas) returned by the system authorization facility (SAF), User response: Use the external security manager codes to
and the response and reason codes (esmresp and esmreas) determine why the RACROUTE REQUEST=LIST operation
returned by the external security manager (ESM) are those failed. Rectify the problem in the external security manager,
issued by the RACROUTE REQUEST=LIST macro. For the
then restart CICS.
meaning of the response and reason codes in the message see
Module: DFHXSIS, DFHXSRC
"BSM Return Codes" in section "VSE/Advanced Functions
Codes & SVC Errors" of z/VSE Messages and Codes - Volume 1. XMEOUT Parameters: applid, X'safresp', X'safreas', X'esmresp',
X'esmreas'
The build of the profiles was requested by one of the
following: Destination: Console Routecodes 2, 9, 10 and 11
v The initialization of the security domain
v The CEMT command PERFORM SECURITY REBUILD DFHXS1109 applid APPC PROFILE profile COULD NOT
v A user-supplied transaction invoking the EXEC CICS BE AUDITED. SAF CODES ARE
PERFORM SECURITY REBUILD command. (X'safresp',X'safreas'). ESM CODES ARE
System action: CICS is unable to provide reliable resource (X'esmresp',X'esmreas').
security, so it terminates. Explanation: An audit request for a partner-LU verification
User response: Use the external security manager codes to check has failed for profile profile.
determine why the RACROUTE REQUEST=LIST operation
failed. Rectify the problem in the external security manager, During the start-up of an APPC session, each partner can
then restart CICS. validate the other. During this validation process, the system:

v Retrieves the relevant APPCLU profile from the external The response and reason codes (safresp and safreas) returned by
security manager the system authorization facility (SAF), and the response and
v Checks that the session key is still usable reason codes (esmresp and esmreas) returned by the external
v Requests the external security manager to write audit security manager (ESM) are those issued by the RACROUTE
records concerning this profile and the validation to the REQUEST=FASTAUTH or RACROUTE REQUEST=AUTH
data management facility (DMF). macros. For the meaning of the response and reason codes in
the message see "BSM Return Codes" in section
The following events are audited: "VSE/Advanced Functions Codes & SVC Errors" of z/VSE
v Whether the session partner was correctly validated Messages and Codes - Volume 1.
v Whether the session partner failed validation
v Whether the session key will expire in less than six days CICS can also issue this message when you use the EXEC
v Whether the retrieved profile is “locked” CICS QUERY SECURITY command with the
v Whether the session key is null, or all zero LOGMESSAGE(LOG) option.
v Whether the session key has expired. System action: CICS abnormally terminates the task
requesting the invalid access except under one of the
The response and reason codes (safresp and safreas) returned by following conditions:
the system authorization facility (SAF), and the response and v The command is issued within the scope of an EXEC CICS
reason codes (esmresp and esmreas) returned by the external HANDLE NOTAUTH command.
security manager (ESM) are those issued by the RACROUTE v The command is issued as a result of an EXEC CICS
REQUEST=AUDIT macro. For the meaning of the response QUERY SECURITY command.
and reason codes in the message see "BSM Return Codes" in User response: Note the security violation.
section "VSE/Advanced Functions Codes & SVC Errors" of Module: DFHXSRC
z/VSE Messages and Codes - Volume 1.
System action: The CICS system is not affected by this event, XMEOUT Parameters: date, time,applid, tranid, userid, {1= at
and CICS continues. netname, 2= at console }, portname, resource, classname, X'safresp',
User response: Use the external security manager codes to X'safreas', X'esmresp', X'esmreas'
determine why the RACROUTE REQUEST=AUDIT operation Destination: CSCS
failed. Correct the problem in the external security manager,
then perform a security rebuild, if appropriate.
Module: DFHXSSB DFHXS1112 applid The CICS region userid and groupid
Destination: Console Routecode 9 could not be determined. SAF codes are
DFHXS1110 applid Security is requested, but the external Explanation: CICS could not determine the userid and
security manager is inactive. groupid for this CICS region.
Explanation: Security was requested for this region, but the
external security manager (ESM) was found to be inactive. The The response and reason codes (safresp and safreas) returned by
SEC system initialization parameter was specified as YES or the system authorization facility (SAF), and the response and
left as its default value. CICS cannot initialize its security reason codes (esmresp and esmreas) returned by the external
manager unless the ESM is active. security manager (ESM) are those issued by the RACROUTE
System action: CICS terminates. REQUEST=EXTRACT macro. For the meaning of the response
User response: If you have an ESM installed on your system, and reason codes in the message see "BSM Return Codes" in
ensure that it is active before attempting to start CICS. section "VSE/Advanced Functions Codes & SVC Errors" of
Otherwise, restart CICS without security by specifying z/VSE Messages and Codes - Volume 1.
SEC=NO as a system initialization parameter. Note that the System action: An exception entry is made in the trace table.
SEC parameter cannot be entered as a console override. A system dump is taken, unless you have specifically
Module: DFHXSIS suppressed dumps in the dump table.
User response: Use the external security manager codes to
XMEOUT Parameter: applid determine why the RACROUTE REQUEST=EXTRACT
Destination: Console Routecodes 1, 9, 10 and 11 operation failed. Then, either correct the errors for the failing
region userid and groupid, and restart CICS, or restart CICS
with a different userid and groupid.
DFHXS1111 date time applid tranid Security violation by Module: DFHXSIS
user userid{ at netname | at console } portname
for resource resource in class classname. SAF XMEOUT Parameters: applid, X'safresp', X'safreas', X'esmresp',
codes are (X'safresp',X'safreas'). ESM codes are X'esmreas'
(X'esmresp',X'esmreas'). Destination: Console Routecodes 2, 9, 10 and 11
Explanation: CICS has detected a security violation by user
userid while performing an authority check for resource
DFHXS1113 applid The region userid cannot access system
resource in resource class classname.
transaction tranid. CICS will terminate. SAF
If the userid causing the violation is signed on at a VTAM codes are (X'safresp',X'safreas'). ESM codes are
terminal, the phrase “at netname portname” reports the (X'esmresp',X'esmreas').
netname at which the violation occurred. If the userid causing Explanation: The region userid for this CICS system is not
the violation is signed on at a console, the phrase “at console authorized to attach the system transaction tranid. It is a CICS
portname” reports the console name at which the violation requirement that the region userid must be able to access this
occurred. If the userid causing the violation is not signed on transaction.
or this is a non terminal task, then the entry port will not
The response and reason codes (safresp and safreas) returned by
appear in this message as it is not available.
the system authorization facility (SAF), and the response and

reason codes (esmresp and esmreas) returned by the external Module: DFHXSPW
security manager (ESM) are those issued by the RACROUTE
XMEOUT Parameters: date, time,applid, userid, tranid, userid,
REQUEST=FASTAUTH or AUTH macro. For the meaning of
netname
the response and reason codes in the message see "BSM
Destination: CSCS
Return Codes" in section "VSE/Advanced Functions Codes &
SVC Errors" of z/VSE Messages and Codes - Volume 1.
System action: CICS terminates. DFHXS1205 date time applid The userid userid supplied in a
User response: Authorize the CICS region userid to access all verification request is not defined in the
the required CICS system transactions, or specify a different ESM. This occurred in transaction tranid at
region userid that does have the required authority. (The netname netname.
required transactions are documented as the 'Category 1' Explanation: An undefined userid was supplied for user
transactions in the CICS RACF Security Guide.) verification.
Then restart CICS. System action: CICS continues. No dump is taken.
Module: DFHXSRC User response: Contact your security administrator for
assistance.
XMEOUT Parameters: applid, tranid,X'safresp', X'safreas', Module: DFHXSPW
X'esmresp',X'esmreas'
Destination: Console Routecodes 2, 9, 10 and 11 XMEOUT Parameters: date, time,applid, userid, tranid, netname
Destination: CSCS
DFHXS1201 date time applid The password supplied in the

verification request for userid userid was DFHXS1211 date time applid The password supplied in a
invalid. This occurred in transaction tranid change password request for userid userid
when userid userid was signed on at netname was invalid. This occurred in transaction
netname. tranid when userid userid was signed on at
Explanation: An invalid password was supplied for user netname netname.
verification. Explanation: An invalid password was supplied for change
System action: CICS continues. No dump is taken. password processing.
User response: Supply the correct password, or contact your System action: The external security manager may also issue
security administrator for assistance. If you continue to supply a message to the VSE console.
incorrect passwords, the userid may be revoked by the CICS continues. No dump is taken.
external security manager. A revoked userid can only be User response: Supply the correct password or contact your
reinstated by a security administrator. security administrator for assistance. If you continue to supply
Module: DFHXSPW incorrect passwords, the userid may be revoked by the
XMEOUT Parameters: date, time,applid, userid, tranid, userid, external security manager. A revoked userid can only be
netname reinstated by a security administrator.
Destination: CSCS Module: DFHXSPW
XMEOUT Parameters: date, time,applid, userid, tranid, userid,

DFHXS1202 date time applid The password supplied in the netname
verification request for userid userid has Destination: CSCS
expired. This occurred in transaction tranid
when userid userid was signed on at netname DFHXS1213 date time applid The userid supplied in a
netname. change password request for userid userid is
Explanation: An expired password was supplied for user revoked. This occurred in transaction tranid
verification. when userid userid was signed on at netname
System action: CICS continues. No dump is taken. netname.
User response: Change the password using the CICS signon Explanation: A revoked userid was supplied on a password
process, the EXEC CICS CHANGE PASSWORD API, or any change request
other method available to you. Alternatively, contact your System action: CICS continues. No dump is taken.
security administrator for assistance. User response: You should have the userid reinstated before
Module: DFHXSPW it can be used. Contact your security administrator for
XMEOUT Parameters: date, time,applid, userid, tranid, userid, assistance.
netname Module: DFHXSPW
Destination: CSCS XMEOUT Parameters: date, time,applid, userid, tranid, userid,
netname
DFHXS1203 date time applid The userid supplied in the Destination: CSCS
verification request for userid userid is
revoked. This occurred in transaction tranid DFHXS1214 date time applid The new password supplied
when userid userid was signed on at netname in a change password request for userid
netname. userid was not accepted. This occurred in
Explanation: A revoked userid was supplied for user transaction tranid when userid userid was
verification. signed on at netname netname.
System action: CICS continues. No dump is taken. Explanation: An invalid new password was supplied on a
User response: Contact your security administrator for password change request.
assistance.

DFHXS1215 • DFHZC0001
System action: CICS continues. No dump is taken. XMEOUT Parameters: date, time,applid, userid, tranid, netname
User response: Select a suitable new password and try again. Destination: CSCS
If necessary, contact your security administrator for assistance.
Module: DFHXSPW
DFHXS1216 date time applid The userid userid supplied in a
XMEOUT Parameters: date, time,applid, userid, tranid, userid, change password request has a revoked
netname connection to the default group in the ESM.
Destination: CSCS This occurred in transaction tranid at netname
netname.
Explanation: The userid supplied on a password change
DFHXS1215 date time applid The userid userid supplied in a
request is revoked in the ESM connection to the default group.
change password request is not defined in
System action: CICS continues. No dump is taken.
the ESM. This occurred in transaction tranid
User response: Contact your security administrator for
at netname netname.
assistance.
Explanation: An undefined userid was supplied on a
Module: DFHXSPW
password change request
System action: CICS continues. No dump is taken. XMEOUT Parameters: date, time,applid, userid, tranid, netname
User response: Contact your security administrator for Destination: CSCS
assistance.
Module: DFHXSPW
DFHZCxxxx messages
Messages that are generated because the VTAM SYNAD and LERAD exits have
been entered are followed by VTAM RETURN CODE xxyy where xx is the VTAM
recovery action return code and yy is the VTAM specific error return code, each
obtained from fields of the RPL.
Messages that are generated because system or user sense data has been received,
are followed by SENSE RECEIVED xxyy zzzz where xx is the VTAM system sense
information byte, yy is the VTAM system sense modifier byte, and zzzz represents
2 bytes of user sense information.
Values for xx, yy, and zzzz are hexadecimal. The VTAM system sense information
byte, xx, can have the following values:
xx meaning
X'00' User sense data only (see zzzz)
X'08' Request reject
X'10' Request error
X'20' State error
X'40' Request header (RH) usage error
X'80' Path error
For the meaning of yy, see the SNA Formats manual.
The sense insert is not included in DFHZCxxxx messages when no meaningful

feedback is available.
The instance field on some DFHZCxxxx messages is for IBM internal use only.
DFHZC0001 applid An abend (code aaa/bbbb) has occurred
an error in the CICS code. Alternatively, unexpected data has CICS continues unless you have specified in the dump table
been input, or storage has been overwritten. that CICS should terminate. If appropriate, an error return
If a VSE code is not applicable, this field is filled with three Message DFHME0116 is normally produced containing the
hyphens. The CICS code is an abend code or a number symptom string for this problem.

DFHZC0002 • DFHZC0004

DFHZC0003 applid Insufficient storage (code X'code') in
module modname.
Look up the VSE code, if there is one, in "OS/390 API Abend Explanation: A CICS GETMAIN was issued by module
Codes" in section "VSE/Advanced Functions Codes & SVC modname, but there was insufficient storage available to satisfy
Errors" of z/VSE Messages and Codes - Volume 1. the request.
Next, look up the CICS abend code in “Transaction Abend The code X'code' is the exception trace point ID which
Codes (CICS Transaction Server for VSE/ESA)” on page 453. uniquely identifies the place where the error was detected.
This tells you, for example, whether the error was a program System action: An exception entry is made in the trace table
check, an abend, or a runaway, and may give you some (code X'code' in the message). A system dump is taken, unless
guidance concerning user response. you have specifically suppressed dumps in the dump table.
If module modname is not crucial to the running of your CICS table that CICS should terminate.
down at a convenient time to resolve the problem. If appropriate, an error return code is sent to the caller of this
domain. In this case, CICS could be terminated by the caller A
If you cannot run without the full use of module modname you message will be issued to this effect. Message DFHME0116 is
should bring CICS down in a controlled shutdown. normally produced containing the symptom string for this
For further information about code, see the CICS Problem problem.
Determination Guide. User response: Inform the system programmer.
You need further assistance from IBM to resolve this problem. Try increasing the size limits of the DSAs or EDSAs. See the
See Part 4 of the CICS Problem Determination Guide for CICS System Definition Guide or the CICS Performance Guide for
guidance on how to proceed. more information on CICS storage.
Module: DFHZGBM, DFHZGCA, DFHZGCC, DFHZGCN, Module: DFHTCRP, DFHZGRP
DFHZGDA, DFHZGPC, DFHZGRP, DFHZGSL, DFHZGUB XMEOUT Parameters: applid, X'code',modname
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname Destination: Console
DFHZC0004 applid A possible loop has been detected at
DFHZC0002 applid A severe error (code X'code') has offset X'offset' in module modname.
occurred in module modname. Explanation: A CICS function is taking more time to process
Explanation: An error has been detected in module modname. than CICS expects. A possible loop has been detected in
The code X'code' is the exception trace point ID which module modname at offset X'offset'. This is the offset of the
uniquely identifies what the error is and where the error was instruction which was executing at the time the error was
detected. detected.
System action: An exception entry (code X'code' in the System action: An exception entry is made in the trace table.
message) is made in the trace table. A system dump is taken, A system dump is taken, unless you have specifically
unless you have specifically suppressed dumps in the dump suppressed dumps in the dump table.
table. CICS continues unless you have specified in the dump table
CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return
that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS
code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain
could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.
manager, DFHDMDM). A message is issued to this effect. Message DFHME0116 is normally produced containing the
symptom string for this problem. User response: Notify the system programmer. If CICS has
User response: This indicates a possible error in CICS code. not been terminated, it is necessary to decide whether the
The severity of its impact depends on the importance of the problem is serious enough to bring CICS down.
function being executed at the time of the error. Since some CICS functions can use a lot of processor time, this
CICS may not have been terminated. If the message occurs message may have been caused by a long-running function. So
once and module modname is not crucial to the running of there may not be an error here. Usually, CICS purges a CICS
your CICS system, you may decide to continue to run and function which exceeds the runaway task time interval which
bring CICS down at a convenient time to resolve the problem. you have specified on the ICVR system initialization
If the message recurs or if you cannot run without the full use that module modname in the message is terminated and CICS
of module modname, you should bring CICS down in a continues.
You need further assistance from IBM to resolve this problem. module modname has gone into a loop, you have to terminate
See Part 4 of the CICS Problem Determination Guide for CICS in order to terminate the runaway function.
Module: DFHZGCA, DFHZGCC, DFHZGCN, DFHZGDA, If CICS has terminated module modname, and you consider
DFHZGPC, DFHZGRP, DFHZGSL, DFHZGUB that it was not a runaway, you should increase the ICVR time
XMEOUT Parameters: applid, X'code',modname this permanently. But you can change the ICVR time interval
Destination: Console temporarily online, using the CEMT transaction.

DFHZC0101I • DFHZC0121I
need further assistance from IBM. See Part 4 of the CICS XMEOUT Parameters: date, time,applid, sysid, modename
Problem Determination Guide for guidance on how to proceed. Destination: CSNE
Module: XMEOUT Parameters: applid, X'offset', modname
DFHZC0112 date time applid No TCTME was found for
sysid sysid modename modename during a
DFHZC0101I date time applid A predatory takeover has persistent sessions restart.
forced VTAM to allow another application to Explanation: An error has occurred during persistent sessions
open the ACB which CICS was using. restart. VTAM passed a NIB to CICS containing the named
Explanation: A predatory takeover is occurring. This means modename, but CICS was unable to locate the corresponding
that a job is initializing which has the same applid as the CICS TCTME.
system. This initiates a takeover of the network. As a normal
System action: The attempt to match the NIB to a TCTTE is
part of this process, VTAM drives the TPEND exit.
terminated. The session is unbound.
System action: All requests on VTAM sessions are
abnormally terminated and the sessions closed. The VTAM A system dump is produced.
ACB is then opened by the application which is using the
same APPLID as the CICS region. The new system recovers The CNOS values not related to this modegroup are restored,
any persisting sessions. but the named modegroup cannot be recovered.
User response: None. User response: You need further assistance from IBM to
Module: DFHZNCA resolve this problem. See Part 4 of the CICS Problem
XMEOUT Parameters: date, time,applid Module: DFHZGPC
Destination: Console and Transient Data Queue CSNE
XMEOUT Parameters: date, time,applid, sysid, modename
Destination: CSNE
DFHZC0110 date time applid The LU6.2 NIB and the
TCTTE/BIND data for session sessid did not
match during a persistent sessions restart. DFHZC0120I applid VTAM sessions persisted for a COLD
Reason code X'n'. start. Sessions terminated. Inquires issued
Explanation: A node initialization block (NIB) has been icount, sessions persisting spcount, sessions
passed to CICS by VTAM during a persistent sessions restart. terminated stcount.
An attempt was made by CICS to match the NIB to a session Explanation: CICS is initializing with a COLD start, but some
TCTTE. The reason code explains the cause of the mismatch. VTAM sessions have persisted from a previous CICS with a
Reason Explanation nonzero PSDI value.
1 Single/parallel session indication did not match.
CICS has attempted to terminate all persisting sessions. The
2 LU type did not match.
message inserts are as follows:
3 LU type and single/parallel session did not match.
v icount is the number of VTAM INQUIRE OPTCD=PERSESS
System action: The attempt to match a persisting session
commands issued.
with a TCTTE has failed. The session is unbound. CICS
v spcount is the number of VTAM sessions that persisted.
ignores this session and continues with the next session if
v stcount is the number of sessions that CICS has terminated
there is one.
with a CLSDST or TERMSESS macro. This should be equal
User response: The production of this message means that
to spcount. If it is not, persistent session recovery probably
there is no suitable global catalog record to match the NIB
failed. Earlier messages explain why.
which VTAM has passed in. This implies that the wrong
global catalog is being used for this initialization of CICS, or If there are no earlier messages, it is possible that the count
that the catalog records are corrupted. Ensure that the global obtained from the VTAM INQUIRE counts macro,
catalog being used is correct. indicating the number of active sessions, was not equal to
Module: DFHZGPC the number of sessions that VTAM held persisting. This is
not a problem.
XMEOUT Parameters: date, time,applid, sessid, X'n' System action: CICS continues.
Destination: CSNE User response: None.
Module: DFHZGRP
DFHZC0111 date time applid No session TCTTE is available XMEOUT Parameters: applid, icount,spcount, stcount
to match sysid sysid for modename modename Destination: Console
because VTAM has returned more NIBs than
the CNOS session limit values require.
Explanation: During persistent sessions restart VTAM has DFHZC0121I applid VTAM sessions persisted for a WARM
returned more node initialization blocks (NIBs) than the start. Sessions terminated. Inquires issued
current CNOS session limit values require. This is probably icount, sessions persisting spcount, sessions
because a CNOS from a high session limit to a lower session terminated stcount.
limit was in progress when CICS failed. Explanation: CICS is initializing with a WARM start, but
System action: The process NIB function is terminated. The some VTAM sessions unexpectedly persisted from a previous
session is unbound. CICS ignores this session and continues CICS with a nonzero PSDI value.
with the next session if there is one. CICS has attempted to terminate all persisting sessions. The
This situation has no effect on the restored CICS. The last message inserts are as follows:
catalogued CNOS values are restored. v icount is the number of VTAM INQUIRE OPTCD=PERSESS
User response: None. commands issued.
Module: DFHZGPC v spcount is the number of VTAM sessions that persisted.

DFHZC0122I • DFHZC0125
v stcount is the number of sessions that CICS has terminated If there are no earlier messages, it is possible that the count
with a CLSDST or TERMSESS macro. This should be equal obtained from the VTAM INQUIRE counts macro,
to spcount. If it is not, persistent session recovery probably indicating the number of active sessions, was not equal to
failed. Earlier messages explain why. the number of sessions that VTAM held persisting. This is
If there are no earlier messages, it is possible that the count not a problem.
obtained from the VTAM INQUIRE counts macro, System action: CICS continues.
indicating the number of active sessions, was not equal to User response: None.
the number of sessions that VTAM held persisting. This is Module: DFHZGRP
not a problem. XMEOUT Parameters: applid, icount,spcount, stcount
System action: CICS continues. Destination: Console
User response: Examine the JOBLOG from the previous run
to determine why sessions persisted despite a WARM shut
down. DFHZC0124I applid VTAM sessions persisted for an
Module: DFHZGRP EMERGENCY start. Inquires issued icount,
sessions persisting spcount, sessions
XMEOUT Parameters: applid, icount,spcount, stcount terminated stcount, sessions OPNDSTed
Destination: Console socount, sessions in error secount.
Explanation: CICS was initializing with an EMERGENCY
DFHZC0122I applid VTAM sessions persisted for an start and some VTAM sessions persisted from a previous CICS
EMERGENCY, XRF=YES start. Sessions with a nonzero PSDI value.
terminated. Inquires issued icount, sessions Each of the persisting sessions has been restored or
persisting spcount, sessions terminated stcount. terminated. The message inserts are as follows:
Explanation: CICS is initializing with an EMERGENCY start, v icount is the number of VTAM INQUIRE OPTCD=PERSESS
but XRF = YES has been specified and some VTAM sessions commands issued.
persisted unexpectedly from a previous CICS with a nonzero v spcount is the number of VTAM sessions that persisted.
PSDI value.
This is obtained from a VTAM INQUIRE OPTCD=COUNTS
CICS has attempted to close all persisting sessions. The macro. This should be equal to the sum of the following 3
message inserts are as follows: fields.
v icount is the number of VTAM INQUIRE OPTCD=PERSESS If it is not, this could be because the number of active
commands issued. sessions reported by the INQUIRE is not the same as the
v spcount is the number of VTAM sessions that persisted. number of sessions that actually persist. This is not a
v stcount is the number of sessions that CICS has terminated problem. However, if the count is not equal to the following
with a CLSDST or TERMSESS macro. This should be equal three fields and DFHZGRP has issued an earlier message
to spcount. If it is not, persistent session recovery probably then persistent session recovery probably failed and the
failed. Earlier messages explain why. earlier messages should explain why.
If there are no earlier messages, it is possible that the count v stcount is the number of sessions that CICS terminated with
obtained from the VTAM INQUIRE counts macro, a CLSDST or TERMSESS macro. If an OPNDST failure
indicating the number of active sessions, was not equal to occurred for an entire NIBLIST (see message DFHZC0129),
the number of sessions that VTAM held persisting. This is the sessions in the NIBLIST have been terminated and this
not a problem. count includes these sessions.
System action: CICS continues. v socount is the number of VTAM sessions that CICS restored
User response: You should not mix XRF and persistent successfully with an OPNDST OPTCD=RESTORE macro.
sessions. If you wish to use XRF, do a COLD start. v secount is the number of sessions that CICS failed to restore.
Module: DFHZGRP System action: CICS continues.
XMEOUT Parameters: applid, icount,spcount, stcount
Module: DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount, socount,
secount
DFHZC0123I applid VTAM sessions persisted when OPEN Destination: Console
VTAM ACB issued. Sessions terminated.
Inquires issued icount, sessions persisting
spcount, sessions terminated stcount. DFHZC0125 date time applid netname persistent session will
Explanation: The VTAM ACB has been opened while CICS is be terminated. sense ((instance) Module name:
running, however some VTAM sessions persisted either from {DFHZGRP})
a previous CICS with a nonzero PSDI value, or when the Explanation: CICS was initializing with an EMERGENCY
VTAM ACB was closed. start and some VTAM sessions persisted from a previous CICS
with a nonzero PSDI value.
Persisting sessions have been terminated. The message inserts
are as follows: However, the session with a NETNAME of netname is
v icount is the number of VTAM INQUIRE OPTCD=PERSESS terminated for one of the following reasons as indicated by the
commands issued. instance in the message. An AP exception trace entry is made
v spcount is the number of VTAM sessions that persisted. for each instance as follows.
v stcount is the number of sessions that CICS terminated with
Instance Point ID and Explanation
a CLSDST or TERMSESS macro. This should be equal to
1 X'FB21' There is not enough storage to recover an
spcount. If it is not, persistent session recovery probably
APPC session.
failed. Earlier messages explain the reason.

DFHZC0126I • DFHZC0130
2 X'FB22' There is not enough storage to recover a not responding to the INQUIRE or OPNDST macro (if the
terminal session. message is issued by DFHZGRP), or the CLSDST or
3 X'FB25' The NIB and the TCTTE with the same TERMSESS macro (if the message is issued by DFHZGUB).
NETNAME were not of the same LU TYPE.
You can determine which macro is not responding by
System action: An AP exception trace with a point ID as
examining the TCP section of the dump and looking at the
above is issued. issued. The session is terminated and CICS RPLs in the PS POOL labeled PS_RPL. The first RPL is for use
continues. by INQUIRE or OPNDST, the next 10 by CLSDST or
User response: The exception trace point identifies where the TERMSESS.
message was issued and determines the action to take. Module: DFHZGRP, DFHZGUB
Module: DFHZGRP
XMEOUT Parameters: applid, module
XMEOUT Parameters: date, time,applid, netname, sense, instance, Destination: Console
{1=DFHZGRP, 2=DFHZGRP, 3=DFHZGRP}
Destination: CSNE
DFHZC0129 applid VTAM OPNDST RESTORE failed. All
sessions in the NIBLIST will be terminated
DFHZC0126I applid No VTAM sessions persisted for an instead. RTNCD,FDB2: X'rc',X'fd'. Code:
EMERGENCY restart. X'code'
Explanation: CICS was initializing with an EMERGENCY Explanation: CICS is processing VTAM persistent sessions
start but no VTAM sessions persisted from a previous CICS during an EMERGENCY restart but VTAM returned a
run. Possible reasons are: RTNCD,FDB2 of rc,fd in response to the OPNDST
v No persistence was specified in the previous run. OPTCD=RESTORE macro.
v CICS crashed with the ACB open but no sessions were in System action: An AP exception trace entry, X'code', is made.
use. A system dump is taken on the first occurrence of this
v The PSDI value expired. problem unless dumps have been specifically suppressed in
v An error occurred before DFHZGRP could determine if any the dump table.
sessions persist.
System action: CICS continues. CICS attempts to terminate all the sessions in the NIBLIST
User response: None. instead of restoring them.
Module: DFHZGRP User response: Use the dump taken on the first occurrence of
this problem or the exception trace entry and section "VTAM
XMEOUT Parameter: applid codes" in z/VSE Messages and Codes - Volume 2 to determine the
Destination: Console meaning of the RTNCD,FDB2 and the actions necessary to
correct it.
Module: DFHZGRP
DFHZC0127 applid Cannot reestablish persisting sessions -
VTAM ACB is closed. Code: X'code'. Module XMEOUT Parameters: applid, X'rc',X'fd', X'code'
name: module Destination: Console
Explanation: The VTAM ACB has been opened and CICS is
processing VTAM persisting sessions, however the ACB was
closed, or is being closed by operator action before all the DFHZC0130 applid VTAM INQUIRE PERSESS failed.
sessions could be restored or terminated. Cannot restore any persisting sessions.
System action: CICS continues to close the VTAM ACB and RTNCD,FDB2: X'rc',X'fd'. Code: X'code'
then runs without VTAM support. Explanation: CICS is processing VTAM persistent sessions
User response: Determine why the operator closed the ACB but VTAM returned a RTNCD,FDB2 of rc,fd in response to the
and either continue without VTAM, dynamically open the INQUIRE OPTCD=PERSESS macro.
ACB, or shut CICS down normally and restart it. System action: An AP exception trace entry, X'code', is made.
X'code' is the AP exception trace entry that determines which A system dump is taken unless dumps have been specifically
VTAM macro diagnosed the ACB as being closed and where it suppressed in the dump table.
was issued. If this occurs during initialization, CICS terminates.
Module: DFHZGRP DFHZGUB
If this occurs during a dynamic open of the ACB, CICS closes
XMEOUT Parameters: applid, X'code',module the ACB and continues to run without VTAM.
The sessions persist until the PSDI value times out or until
VTAM operator commands are issued to terminate the
DFHZC0128 applid Cannot reestablish persisting sessions - sessions.
VTAM not responding. Module name: module User response: Use the dump or the exception trace entry
Explanation: CICS is processing VTAM persisting sessions. and section "VTAM codes" in z/VSE Messages and Codes -
However it has issued a VTAM macro and has waited for 5 Volume 2 to determine the meaning of the RTNCD,FDB2 and
minutes for the response. the actions necessary to correct it.
System action: If this occurs during start up, CICS
terminates. If this occurs during dynamic open, the VTAM If the problem occurs during initialization, try to correct the
ACB is closed and CICS continues without VTAM. error and then retry the start up, or wait until the PSDI value
time expires and restart CICS.
A dump is taken for this message in both cases.
User response: You can restart CICS again immediately, or If the problem occurs when the ACB was opened dynamically,
wait for the persistent sessions to time out and then restart you can repeat the command to open the VTAM ACB, or wait
CICS. until the PSDI time expires and then repeat it.
Module: DFHZGRP
If this problem reoccurs you need to find out why VTAM is

XMEOUT Parameters: applid, X'rc',X'fd', X'code' order to take advantage of CICS persistent session support.
To prevent this message being issued when using an earlier
release of VTAM, set the PSDINT system initialization
DFHZC0131 date time applid netname termid VTAM parameter to zero, and when using the EXEC CICS SET
OPNDST RESTORE failed. VTAM command, either omit, or specify a value of zero for
Explanation: CICS is processing VTAM persistent sessions the PSDINTERVAL operand.
and has issued an OPNDST OPTCD=RESTORE against a Module: DFHZSLS
NIBLIST. However, the NIB identified by netname and a
session or termid of termid failed to open successfully. This is
probably because the session was terminated by the VTAM
operator after INQUIRE OPTCD=PERSESS was issued.
System action: CICS continues. DFHZC0137 applid PSDI value indicated persistence but
User response: Reopen the session in the normal way. the TCT assemble time VTAM does not
Module: DFHZGRP support persistent sessions.
XMEOUT Parameters: date, time,applid, netname, termid Explanation: The PSDI value is nonzero. This specifies that
Destination: CSNE VTAM sessions are to persist across CICS failures. However,
DFHTCTxx was assembled against a release of VTAM that
cannot support persistent sessions.
DFHZC0132 applid VTAM INQUIRE PERSESS failed. System action: CICS sets the PSDI value to 0 and continues
Cannot restore some persisting sessions. without persistent session support.
Network only partially restored. User response: Reassemble the TCT against the correct level
RTNCD,FDB2: X'rc',X'fd'. Code: X'code' of VTAM in order to take advantage of CICS persistent session
Explanation: CICS is processing VTAM persistent sessions support.
but VTAM returned a RTNCD,FDB2 of rc,fd in response to a
To prevent this message being issued when using an earlier
subsequent INQUIRE OPTCD=PERSESS macro.
release of VTAM, set the PSDINT system initialization
System action: An AP exception trace entry, X'code', is made.
parameter to zero, and when using the EXEC CICS SET
A system dump is taken unless you have specifically VTAM command, either omit, or specify a value of zero for
suppressed dumps in the dump table. the PSDINTERVAL operand.
Module: DFHZSLS
CICS continues with a partial network. Some of the sessions
are usable, others are not until the PSDI value times out or the XMEOUT Parameter: applid
VTAM operator terminates the sessions that failed. Destination: Console
User response: Use the dump or the exception trace entry
and section "VTAM codes" in z/VSE Messages and Codes -
Volume 2 to determine the meaning of the RTNCD,FDB2 and DFHZC0140 applid SETLOGON PERSIST failed.
the actions necessary to correct it. RTNCD,FDB2: X'rc',X'fd'. Code: X'code'
Explanation: CICS was opening the VTAM ACB, setting the
If enough of the network is available, wait until the PSDI PSDI value from an operator command or doing a WARM
value expires or use VTAM operator commands to terminate shut down. It attempted to issue the VTAM command
the sessions. SETLOGON OPTCD=PERSIST or OPTCD=NPERSIST.
However, VTAM returned a RTNCD,FDB2 of rc,fd.
If the network is unusable, either close and reopen the VTAM System action: An AP exception trace entry, code, is made.
ACB, or restart CICS.
Module: DFHZGRP A system dump is taken unless you have specifically
XMEOUT Parameters: applid, X'rc',X'fd', X'code'
Destination: Console If the ACB was being opened, no VTAM sessions persist and
the PSDI value is set to 0.
DFHZC0133A applid Persistent session recovery failed. If just the PSDI value was being changed, either by the
Explanation: CICS was initializing when an attempt to operator or during termination, the value is unchanged, both
process VTAM persistent session failed. The reasons are given to CICS and to VTAM.
in earlier messages.
If this occurs during a VTAM shut down and some sessions
are not closed, sessions may exist on VTAM start-up and are
User response: Examine earlier messages and exception trace
terminated then.
entries to determine the reason for failure.
User response: Use the dump or the exception trace entry
Module: DFHSII1
code to determine the meaning of the RTNCD,FDB2 and the
XMEOUT Parameter: applid actions necessary to correct it.
Destination: Console Module: DFHZGSL
XMEOUT Parameters: applid, X'rc',X'fd', X'code'
DFHZC0136 applid PSDI value indicated persistence but Destination: Console
the run time VTAM does not support
persistent sessions.
DFHZC0144 date time applid sysid termid Synclevel 2
Explanation: The PSDI value is nonzero. This specifies that
conversation started by netname before
VTAM sessions are to persist across CICS failures. However,
Exchange Lognames, and following a
this release of VTAM does not support persistent sessions.
persistent sessions restart. sense ((instance)
System action: CICS sets the PSDI value to 0 and continues
Module name: {DFHZGDA})
without persistent session support.
Explanation: Following a persistent sessions restart, CICS has
User response: A higher level of VTAM must be used in

received an attach FMH5 for a synclevel 2 conversation from a Definition Guide and the CICS Customization Guide for more
partner with netname netname before exchange lognames information.
processing is complete. Module: DFHZXRC
System action: A deallocate(Abend) with sense code
08640001 is issued for the conversation. XMEOUT Parameters: date, time,applid, termid, sense, instance,
User response: No further APPC synclevel 2 conversations {1=DFHZXRC}
should be started by the partner until exchange lognames has Destination: CSNE
completed. Use CEMT to inquire on the status of the
connection in order to determine whether Exchange Lognames
has completed (see the CICS Supplied Transactions for more DFHZC0147 date time applid sysid termid Error occurred
information). recovering persisting session. sense ((instance)
Module: DFHZGDA Module name: {DFHZGDA})
Explanation: An error has prevented the recovery of an
XMEOUT Parameters: date, time,applid, sysid, termid, netname, APPC conversation which persisted across an emergency
sense, instance, {1=DFHZGDA} restart.
Destination: CSNE
The session with a termid of termid is terminated. The reason
and the corresponding AP exception trace entry are indicated
DFHZC0145 date time applid netname termid Synclevel 2 by the instance in the message;
APPC conversation started before Exchange
Lognames completed. Error occurred Instance Point ID and explanation
executing Deallocate(Abend). sense ((instance) 1 X'FB79' SEND not executed due to invalid bracket
Module name: {DFHZGDA}) state.
Explanation: The APPC session termid with netname persisted 2 X'FB7B' Insufficient storage for session recovery.
during a CICS persistent sessions restart. The partner initiated 3 X'FB76' Recovery status byte TCTE_PRSS contains
a new synclevel 2 conversation before exchange lognames an unexpected value.
processing had completed. CICS attempted to issue a 4 X'FB7A' RECEIVE not executed due to invalid
Deallocate(Abend) for the conversation. The bracket state.
Deallocate(Abend) could not be completed for the reason 5 X'FB78' Unexpected sense received during persistent
indicated by the instance in the message as follows. sessions recovery.
Instance Explanation System action: An AP exception trace with a point ID as
01 DFHZGDA called with chain Finite State Machine in above is issued. The session is terminated and CICS continues.
unexpected state. User response: If recovery failed due to insufficient storage,
02 DFHZGDA called with bracket Finite State Machine try increasing the DSA or EDSA size limits. See the CICS
in unexpected state System Definition Guide for details of how to do this.
If any of the other instances occur, you will need further

For the meaning of the sense data, see the explanation on assistance from IBM. See Part 4 of the CICS Problem
topic “DFHZCxxxx messages” on page 356. Determination Guide for guidance on how to proceed.
System action: The state of the session after the persistent Module: DFHZGDA
sessions restart cannot be determined, and the session is
deactivated in order to reset the states The sessions are XMEOUT Parameters: date, time,applid, sysid, termid, sense,
reactivated. instance, {1=DFHZGDA, 2=DFHZGDA, 3=DFHZGDA,
User response: If the session is not successfully reactivated, 4=DFHZGDA, 5=DFHZGDA}
check the CSNE log for messages indicating why the new Destination: CSNE
BIND failed. The session may have been set out of service by
the VTAM operator.
DFHZC0148 date time applid sysid termid VTAM send or
Module: DFHZGDA
receive failed during persistent sessions
XMEOUT Parameters: date, time,applid, netname, termid, sense, recovery. sense ((instance) Module name:
instance, {1=DFHZGDA, 2=DFHZGDA} {DFHZGDA})
Destination: CSNE Explanation: As part of session recovery following a
persistent session restart CICS issued a VTAM SEND or
RECEIVE. The VTAM request failed leaving the session in an
DFHZC0146 date time applid VTAM session for termid unknown state.
successfully recovered following a persistent
sessions restart sense ((instance) Module name: For the meaning of the sense data, see the explanation on
{DFHZXRC}) topic “DFHZCxxxx messages” on page 356.
Explanation: CICS has restored the VTAM persistent session System action: The session is terminated.
for terminal termid following a persistent sessions restart. User response: To determine the cause of the problem, see
the associated DFHZCnnnn message in the CSNE log. This
The equivalent message for APPC sessions is DFHZC0156. message gives further diagnostic information on the failing
System action: If recovery notification is specified for this VTAM request.
terminal, the recovery message is sent to the terminal, or the Module: DFHZGDA
transaction requested to run at recovery notification time is
started. XMEOUT Parameters: date, time,applid, sysid, termid, sense,
User response: If required, code an NEP to override the instance, {1=DFHZGDA, 2=DFHZGDA}
recovery notification option originally specified in the Destination: CSNE
TYPETERM definition for this session. See the CICS Resource

DFHZC0149 date time applid termid Connection failure DFHZC0155 date time applid sysid termid Error occurred
occurred during a persistent sessions restart during processing of session state data
sense ((instance) Module name: {DFHZNSP}) returned after restart of persisting session.
Explanation: During a persistent sessions restart, CICS has sense ((instance) Module name: {DFHZXPS})
been notified of the failure of a session initiation request Explanation: The VTAM APPC session sysid termid persisted
issued during the previous instance of CICS. during a CICS persistent session restart, but an error occurred
while processing the session state data returned by VTAM
For the meaning of the sense data, see the explanation on
following an OPNDST OPTCD=RESTORE.
topic “DFHZCxxxx messages” on page 356.
System action: Processing continues. If the error needs further investigation, a dump is taken.
User response: None
Module: DFHZNSP No dump is taken if one has already been taken for an earlier
problem, or if the problem is known as one for which a
XMEOUT Parameters: date, time,applid, termid, sense, instance, session cannot be allowed to persist. An example of this is
{1=DFHZNSP} bind security processing not completing for this session when
Destination: CSNE CICS terminated.
The reason and the corresponding AP exception trace entry

DFHZC0150 date time applid termid Error processing the are indicated by the instance in the message.
session state data returned after a persistent
Instance Point ID and Explanation
sessions restart. sense ((instance) Module
1 X'FBFD'
name: {DFHZXRC})
Explanation: The VTAM session for terminal termid persisted During reject attach processing a call was made to
during a CICS persistent sessions restart, but an error occurred DFHZGDA but DFHZGDA rejected the call with
while processing the session state data returned by VTAM. invalid format or invalid function.
The reason is indicated by the instance in the message as 2 X'FBFD'
follows.
An error occurred during reject attach processing.
Instance Explanation The session is in an unknown state.
01 DFHZXRC called with an invalid request. 3 X'FBD2'
02 TCTTEDA contains null characters instead of the
expected address. The TCTE_PRSS status byte was set to 0 but reject
03 Reserved attach processing was not taking place. This session
04 The vector key of the data passed by VTAM is not state is not valid for entry to DFHZXPS.
correct. 4 X'FBE4'
05 The length of the vector_29 data is too short. An error occurred during DEALLOCATE ABEND
06 Unidentified cleanup action detected. processing. This will have been handled by
07 Unidentified recovery option detected. DFHZGDA so no dump is taken but the session is
08 Invalid cleanup action for RECOVOPTION(NONE). terminated.
09 Invalid cleanup action for 5 X'FBD2'
RECOVOPTION(MESSAGE).
10 Invalid cleanup action for The TCTE_PRSS byte (persistent sessions status
RECOVOPTION(TRANSACTION). byte) contained an unknown value on entry to
11 Reserved. DFHZXPS.
12 DFHZXRC has been driven to process an LU6 6 X'FBE6'
session.
The TCTE_PRSS_CV29_PTR (pointer to data
13 Neither XRF nor persistent sessions recovery is in
returned by VTAM) contained zeroes on entry to
progress DFHZXRC has been called in error.
DFHZXPS.
7 X'FBD3'
topic “DFHZCxxxx messages” on page 356. The CV29 data returned from VTAM had a zero
System action: The state of the session after the persistent length on entry to DFHZXPS.
sessions restart cannot be determined, and the session is 8 X'FBD4'
terminated in order to reset the states. Non-APPC sessions are
The BIS flow data returned by VTAM showed BIS
restarted.
RQE1 received but the outbound BIS flow was not
User response: If the session is not successfully restarted,
consistent with this.
check the CSNE log for messages indicating why the new
9 X'FBD4'
BIND failed. The session may have been set out of service by
the VTAM operator. The BIS flow data returned by VTAM showed BIS
Module: DFHZXRC RQE3 received but the outbound BIS flow was not
consistent with this.
XMEOUT Parameters: date, time,applid, termid, sense, instance,
10 X'FBD4'
{1=DFHZXRC, 2=DFHZXRC, 3=DFHZXRC, 4=DFHZXRC,
5=DFHZXRC, 6=DFHZXRC, 7=DFHZXRC, 8=DFHZXRC, The BIS flow data returned by VTAM showed that
9=DFHZXRC, 10=DFHZXRC, 11=DFHZXRC, 12=DFHZXRC, no BIS flow had been received but the outbound BIS
13=DFHZXRC} flow was not consistent with this.
Destination: CSNE 11 X'FBD4'

DFHZC0155
The BIS flow data returned from VTAM was not The RU category returned by VTAM in the CV29
recognized. data was not valid for LU6.2. (This session was the
12 X'FBD5' secondary and the last flow was an inbound
request.)
The bid flow data returned by VTAM showed a
26 X'FBD8'
request which was not recognized where this session
is the contention winner. The RU category returned by VTAM in the CV29
13 X'FBD5' data was not valid for LU6.2. (This session was the
secondary and the last flow was an outbound
The bid flow data returned by VTAM showed that a request.)
negative X'088B' response had been sent but there
27 X'FBD8'
was nothing to indicate that the session was closing
down. This session is the contention winner. The RU category returned by VTAM in the CV29
14 X'FBD5' data was not valid for LU6.2. (This session was the
secondary and the last flow was an inbound
The bid flow data returned by VTAM contained a response).
response which was not recognized where this
28 X'FBD8'
session is the contention winner.
15 X'FBD5' The RU category returned by VTAM in the CV29
data was not valid for LU6.2. (This session was the
The bid flow data returned by VTAM was not
secondary and the last flow was an outbound
recognized. This session is the contention winner. response).
16 X'FBD5'
29 X'FBD9'
The bid flow data returned by VTAM contained a
CICS could not determine the direction of the last
request which was not recognized where this session flow from the CV29 data returned by VTAM. (This
is the contention loser.
session was the secondary.)
17 X'FBD5' 30 X'FBD9'
The bid flow data returned by VTAM contained a The last_thing_to_flow byte contained an invalid
negative X'088B' response but there was nothing to value. This indicates a logic error in DFHZXPS.
indicate that the session was closing down. This 31 X'FBDA'
session is the contention loser.
18 X'FBD5' The last inbound flow was a response which was
not for the previous request.
The bid flow data returned by VTAM contained a 32 X'FBDA'
response which was not recognized where this
session is the contention loser. A negative response was received which was not for
19 X'FBD5' a command and was not a X'0846' negative
response.
The bid flow data returned by VTAM was not 33 X'FBDA'
recognized. This session is the contention loser.
not for this bracket. (This session is the primary and
The RU category returned by VTAM in the CV29 started the current bracket).
34 X'FBDA'
primary and the last flow was an outbound request).
not for this bracket. (This session is the secondary
The RU category returned by VTAM in the CV29 and started the current bracket
data was not valid for LU6.2. (This session was the 35 X'FBDA'
primary and the last flow was an inbound request).
not for this bracket. (This session is the primary and
The RU category returned by VTAM in the CV29
did not start the current bracket).
data was not valid for LU6.2. (This session was the 36 X'FBDA'
primary and the last flow was an outbound
response.) The last inbound flow was a response which was
23 X'FBD8' not for this bracket. (This session is the secondary
and did not start the current bracket).
The RU category returned by VTAM in the CV29 37 X'FBDA'
primary and the last flow was an inbound The last flow was a positive response outbound and
response). was not for the previous request.
24 X'FBD9' 38 X'FBDB'
DFHZXPS could not determine the direction of the The last flow was an inbound LUSTAT command
last flow from the CV29 data returned by VTAM. which could not be identified.
(This session was the primary). 39 X'FBDB'
25 X'FBD8'
The last flow was an inbound RTR which was not
processed by the bid analysis routine.
40 X'FBDB'

DFHZC0155
The last flow was an inbound command which The tctewin/tctelse bits in the TCTTE have not been
could not be identified. set correctly.
41 X'FBDB' 58 X'FBDF'
The last flow was an outbound LUSTAT command The session is not in CS mode when analysis of the
which could not be identified. CV29 data shows that a call to DFHZGDA to
42 X'FBDB' ABEND the current transaction is required.
59 X'FBE7'
The last flow was an outbound RTR request which
was not processed by the bid analysis routine. A SEND_FMH7 call to DFHZGDA was rejected with
43 X'FEDB' invalid_format or invalid_function.
60 X'FBE7'
The last flow was an outbound command request
which could not be identified. A SEND_FMH7 call to DFHZGDA was rejected
44 X'FBDC' because of a disastrous error in DFHZGDA.
61 X'FBE7'
The last flow was an inbound response to BIS which
was not processed with the BIS flow data. A RECEIVE_FMH7 call to DFHZGDA was rejected
45 X'FBDD' with invalid_format or invalid_function.
62 X'FBE7'
The last flow was an inbound positive response to a
command which could not be identified. A RECEIVE_FMH7 call to DFHZGDA was rejected
46 X'FBDA' because of a disastrous error in DFHZGDA.
63 X'FBE0'
The last flow was an inbound response to an
LUSTAT command but there was no corresponding Internal DFHZXPS logic error. The input parameters
outbound request. are invalid when a call is about to be made to
47 X'FBDA' DFHZGDA.
64 X'FBE5'
The last flow was an inbound negative response to
an LUSTAT request which could not be identified. An invalid return code was received from a call to
48 X'FBDC' DFHTCPCL with ENTRY=DFHZRST1.
65 X'FBDE'
The last flow was a negative response inbound to a
BIS request which did not show up in the BIS flow The tcte_bid_status byte contained an unrecognized
data. value.
49 X'FBDD' System action: An AP exception trace with a point ID is
issued. The state of the session after the restart cannot be
The last flow was a negative response inbound to a determined, and the session is terminated in order to reset the
command which could not be identified. states. The session is restarted. A system dump is produced
50 X'FBDC' for all instances except 04.
A the last flow was a positive response outbound to User response: If the session is not successfully restarted,
BIS which was not consistent with the BIS flow data. check the CSNE log for messages indicating why the new
51 X'FBDD' BIND failed. The session may have been set out of service by
the VTAM operator.
The last flow was a positive response outbound to a Module: DFHZXPS
command which could not be identified.
52 X'FBDC' XMEOUT Parameters: date, time,applid, sysid, termid, sense,
instance, {1=DFHZXPS, 2=DFHZXPS, 3=DFHZXPS,
The last flow was a negative response outbound to 4=DFHZXPS, 5=DFHZXPS, 6=DFHZXPS, 7=DFHZXPS,
BIS which was not consistent with the BIS flow data. 8=DFHZXPS, 9=DFHZXPS, 10=DFHZXPS, 11=DFHZXPS,
53 X'FBDD' 12=DFHZXPS, 13=DFHZXPS, 14=DFHZXPS, 15=DFHZXPS,
16=DFHZXPS, 17=DFHZXPS, 18=DFHZXPS, 19=DFHZXPS,
The last flow was an outbound negative response to
a command which could not be identified.
54 X'FBE1'
The last request to flow was SIGNAL (expedited 32=DFHZXPS, 33=DFHZXPS, 34=DFHZXPS, 35=DFHZXPS,
flow) but no normal flow data appears in the CV29 36=DFHZXPS, 37=DFHZXPS, 38=DFHZXPS, 39=DFHZXPS,
normal flow data area. 40=DFHZXPS, 41=DFHZXPS, 42=DFHZXPS, 43=DFHZXPS,
55 X'FBE1' 44=DFHZXPS, 45=DFHZXPS, 46=DFHZXPS, 47=DFHZXPS,
The last flow was a SIGNAL request (expedited 52=DFHZXPS, 53=DFHZXPS, 54=DFHZXPS, 55=DFHZXPS,
flow). However analysis of the normal flow data 56=DFHZXPS, 57=DFHZXPS, 58=DFHZXPS, 59=DFHZXPS,
shows both sides sending which is not possible. 60=DFHZXPS, 61=DFHZXPS, 62=DFHZXPS, 63=DFHZXPS,
(Outbound flow was with EC.) 64=DFHZXPS, 65=DFHZXPS}
56 X'FBE1' Destination: CSNE
The last flow was a SIGNAL request (expedited
flow). However analysis of the normal flow data
shows both sides sending which is not possible.
(Outbound flow was in chain.)
57 X'FBD5'

are not as required, reissue the original command.

DFHZC0156 date time applid sysid VTAM APPC session
Module: DFHZGCA
termid successfully recovered following a
persistent sessions restart. sense ((instance) XMEOUT Parameters: date, time,applid, tranid, modename,
Module name: {DFHZXPS}) netname, sysid
Explanation: CICS has restored the VTAM APPC persisting Destination: CSNE
session for sysid termid following a persistent sessions restart.
The equivalent message for non-APPC sessions is DFHZC0161 date time applid tranid CNOS command for
DFHZC0146. Note that the RECOVNOTIFY option which modename modename to node netname
applies to message DFHZC0146 is not applicable to APPC connection sysid has failed with code X'code'.
sessions. Explanation: CICS has encountered an error while attempting
System action: Processing continues. to execute a change number of sessions (CNOS) command for
User response: None. the modename modename on the APPC connection sysid. The
Module: DFHZXPS failure code X'code' is one of the following:
X'FBA2' The request to create a lock manager lock for
XMEOUT Parameters: date, time,applid, sysid, termid, sense,
modename failed.
instance, {1=DFHZXPS, 2=DFHZXPS}
X'FBA3' CICS could not allocate a session for the CNOS
Destination: CSNE
negotiation conversation.
X'FBA6' The request to obtain a lock manager lock for
DFHZC0157 date time applid sysid VTAM APPC session modename failed.
termid could not be recovered following a X'FBAA'
persistent sessions restart. The session will modename was not found or has been defined with
be unbound.sense ((instance) Module name: one of the reserved names SNASVCMG or
{DFHZXPS}) CPSVCMG.
Explanation: CICS was unable to restore the APPC persisting X'FBAB' sysid is known, but not as a connection.
session for sysid termid following a persistent sessions restart. X'FBAC' The specified connection sysid has no modegroups.
There are three possible reasons for this: This is probably caused by a storage overwrite.
1. The BIND processing was incomplete when CICS failed. X'FBAD'
2. Resynchronization was in progress for the session when The first modegroup on the specified connection
CICS failed. sysid has no sessions. This is probably caused by a
3. The recovery data returned by VTAM for the session was storage overwrite.
capable of more than one interpretation. X'FBAF' The receive command for the CNOS reply failed.
X'FBB1' The send command for the CNOS command or
The TCTTE and TIOA are output for information only. CNOS reply failed.
System action: The session is unbound and rebound. X'FBB2' The session for the single-session connection could
User response: None. not be found. This is probably caused by a storage
Module: DFHZXPS overwrite.
X'FBB3' sysid is not a known connection name.
XMEOUT Parameters: date, time,applid, sysid, termid, sense, X'FBB4' The connection is defined to CICS as not supporting
instance, {1=DFHZXPS} CNOS. This is probably caused by a storage
Destination: CSNE overwrite.
System action: CICS makes an exception trace with ID
AP xxxx; where xxxx is the code in the message. CICS takes a
DFHZC0160 date time applid tranid CNOS changes for
system dump for all failure codes except X'FBA2', X'FBA3',
modename modename to node netname
X'FBA6', X'FBAF', and X'FBB1'. CICS continues without
connection sysid are incomplete.
completing the request. The task does not abend. Message
Explanation: CICS has made two attempts to implement the
change number of sessions (CNOS) command for the
modename modename on the APPC connection sysid. The
User response: This depends on the error code as follows:
command was not successful because of other activity on the
X'FBA2' Follow the guidance given for the lock manager
modegroup. This only happens on modegroups which are
console message that precedes this.
very busy. The state of one or more of the sessions has
X'FBA3' If all the sessions are busy, make one available and
changed during the processing of the CNOS request.
retry.
The CNOS command results from a connection acquire, a X'FBA6' Follow the guidance given for the lock manager
connection release, or a request for a specific modename on message that precedes this.
this system or the connected system. If the connected system X'FBAA'
is not CICS, commands specific to that system may have been Reissue the request with the correct modename.
used. X'FBAB' Reissue the request with the correct connection
System action: The modegroup is left in the state reached name.
after the second attempt to implement the changes. X'FBAC' See the CICS Problem Determination Guide for further
User response: Use the CEMT INQUIRE MODENAME guidance on storage problems.
command to determine the current state of the modegroup. X'FBAD'
The command may show the modegroup as you expect for Same as for X'FBAC'.
successful CNOS completion. This is because the command X'FBAF' The connected system, or the link to it, has failed.
only shows data for available and active sessions. CICS may Determine the reason for this from any other
have had problems with CNOS values for loser sessions, messages produced.
which would not be apparent by using CEMT. If the values X'FBB1' Same as for X'FBAF'.

DFHZC0162 • DFHZC2102I
X'FBB2' Same as for X'FBAC'. User response: Sign on if required, and take any recovery
X'FBB3' Reissue the request with the correct connection actions required.
name. Module: DFHZNAC
X'FBB4' Same as for X'FBAC'. Destination: Terminal End User
Module: DFHZGCN
XMEOUT Parameters: date, time,applid, tranid, modename, DFHZC0200 applid An attempt by the COVR transaction to
netname, sysid, X'code' OPEN VTAM has failed with return code
Destination: CSNE X'retcode'; CICS will retry.
Explanation: The COVR transaction has attempted an EXEC
CICS SET VTAM OPEN, but the operation failed with the
DFHZC0162 date time applid tranid CNOS transaction for
return code retcode from the OPEN ACB.
connection sysid has failed with code X'code'
System action: CICS continues. The COVR transaction retries
subcode X'subcode'.
the operation every 5 seconds. This message is reissued every
Explanation: The change number of sessions (CNOS)
minute until the operation succeeds, or until 10 minutes has
transaction program DFHZLS1 could not complete
passed, in which case message DFHZC0201 is issued.
successfully. The error code X'code' is one of the following:
User response: Investigate the reason for VTAM being
X'FB92' The transaction was not started as an IC request
unavailable.
with data or by an attach flow from a connected
Module: DFHZCOVR
system. The insert subcode is the start code from
XMIQ_START_CODE. XMEOUT Parameters: applid, X'retcode'
X'FB93' The transaction was started with data, but no data Destination: Console
was found.
X'FB94' The transaction was started with data, but the data
was not in the form of the correct parameter list. DFHZC0201 applid An attempt by the COVR transaction to
X'FB95' The transaction was started with the correct format OPEN VTAM has failed with return code
parameter list, but the function code was invalid. X'retcode'; the COVR transaction will
X'FB96' The transaction was started by an attach from a terminate.
connected system but there was no CNOS data. Explanation: The COVR transaction has repeatedly attempted
X'FB97' The transaction was started by an attach from a an EXEC CICS SET VTAM OPEN, but the operations have
connected system but the associated data was not a failed. The OPEN ACB has issued the return code retcode.
CNOS command. System action: CICS continues. The COVR transaction
System action: CICS produces an exception trace, and except terminates and the SET VTAM OPEN is not retried.
for in the case of an invalid start, a system dump is taken. The User response: Investigate the reason for VTAM being
task terminates. Message DFHME0116 is normally produced unavailable.
containing the symptom string for this problem. Module: DFHZCOVR
User response: This depends on the error code as follows: XMEOUT Parameters: applid, X'retcode'
X'FB92' The transaction was probably started by entering the Destination: Console
transaction ID at a terminal. This is not allowed.
X'FB93' Analyze the dump to determine why IC could not
find the data. DFHZC2102I date time applid Intersystem session recovery.
X'FB94' Analyze the dump to determine what the data was. Data base changes found to be synchronized.
X'FB95' Analyze the dump to determine what the data was. Original failure details: time. Remote
X'FB96' Analyze the dump to determine why no data was system=sysid. Intersystem terminal=termid.
available. Transaction=tranid. Task number=taskno.
X'FB97' Analyze the dump to determine why the correct Operator terminal=termid. Operator=operid.
data was not sent with the attach. Unit of work ID=uowid ((instance) Module
Module: DFHZLS1 name {DFHZRSY | DFHZSCX | DFHZSEX})
Explanation: Intersystem session recovery has been
XMEOUT Parameters: date, time,applid, tranid, sysid, X'code', successful. An error occurred on an intersystem session
X'subcode' recovery which has now been successfully recovered and
Destination: CSNE resynchronized. This message is normally issued as a follow
up to message DFHZN2101, which may have been issued at
the time of the failure. This happens if the session failed at a
DFHZC0199 CICS has recovered after a system failure. critical time during syncpoint processing.
Execute recovery procedures. { Already
signed on. | Please sign on. } This message may also be issued during syncpoint processing
Explanation: The associated VTAM session has successfully when there are pending unit of recovery descriptors (URDs)
which are awaiting the next inbound flow on the session.
recovered following a persistent sessions restart of CICS.
This is the default message issued by CICS if User response: None.
RECOVNOTIFY(MESSAGE) is specified on the TYPETERM for Module: DFHZRSY, DFHZSEX, DFHZSCX
a device (see the CICS Resource Definition Guide), or in the
node error program (see the CICS Customization Guide). tranid, taskno, termid,operid, uowid, instance, {1=DFHZRSY,
If RECOVNOTIFY(MESSAGE) is used, it is recommended that 2=DFHZRSY, 3=DFHZSEX,4=DFHZSCX, 5=DFHZSCX,
the CICS supplied sample mapset DFHXMSG be tailored to 6=DFHZSCX}
meet the installation recovery requirements. Destination: CSNE

DFHZC2103E • DFHZC2114E
DFHZC2103E date time applid Intersystem session recovery. DFHZC2107E date time applid Intersystem session recovery.
Data base changes found to be out of sync. Suspended changes now being backed out.
Original failure details: time. Remote Original failure details: Time= time. Remote
system=sysid. Intersystem terminal=termid. system=sysid. Intersystem terminal=termid.
Transaction=tranid. Task number=taskno. Transaction=tranid. Task number=taskno.
Operator terminal=termid. Operator=operid. Operator terminal=termid. Operator=operid.
Unit of work ID=uowid ((instance) Module Unit of work ID=uowid ((instance) Module
name {DFHZRSY | DFHZSCX | DFHZSEX}) name {DFHZRSY | DFHZSCX | DFHZSEX})
Explanation: This message is issued as a follow-up to Explanation: This message is issued at intersystem session
message DFHZN2101. The original failure information recovery as a follow-up to message DFHZN2105. It has now
provides a cross-reference. been established that the remote system sysid did not complete
System action: Processing continues. the unit of work. Local changes are being backed out
User response: Take user-defined action to resynchronize the accordingly.
local and remote databases. System action: The system backs out local changes and
Module: DFHZRSY, DFHZSEX, DFHZSCX unlocks.
User response: If required, restart the interrupted transaction
XMEOUT Parameters: date, time,applid, time, sysid, termid, tranid.
tranid, taskno, termid,operid, uowid, instance, {1=DFHZRSY, Module: DFHZRSY, DFHZSEX, DFHZSCX
2=DFHZRSY, 3=DFHZSEX,4=DFHZSCX, 5=DFHZSCX,
6=DFHZSCX} XMEOUT Parameters: date, time,applid, time, sysid, termid,
Destination: CSNE tranid, taskno, termid,operid, uowid, instance, {1=DFHZRSY,
6=DFHZSCX}
DFHZC2104E date time applid Intersystem session recovery Destination: CSNE
error when data base changes may be out of
sync. Original failure details: time. Remote
system=sysid. Intersystem terminal=termid. DFHZC2108E date time applid Intersystem session recovery.
Transaction=tranid. Task number=taskno. Error while local recoverable changes are
Operator terminal=termid. Operator=operid. suspended. Original failure details: Time=
Unit of work ID=uowid ((instance) Module time. Remote system=sysid. Intersystem
name {DFHZRSY | DFHZSCX | DFHZSEX}) terminal=termid. Transaction=tranid. Task
Explanation: This message is issued as a follow-up to number=taskno. Operator terminal=termid.
message DFHZN2101 when the system has been unable to Operator=operid. Unit of work ID=uowid
discover whether database changes are out of synchronization ((instance) Module name {DFHZRSY |
during session recovery. DFHZSCX | DFHZSEX})
System action: Processing continues. Explanation: This message is issued at intersystem session
User response: Make the necessary database enquiries to recovery as a follow-up to message DFHZN2105.
detect whether changes are synchronized. If they are not, take Resynchronization has failed, therefore it still cannot be
user-defined action to resynchronize the databases. established whether the remote system sysid committed or
Module: DFHZRSY, DFHZSEX, DFHZSCX backed out.
System action:
XMEOUT Parameters: date, time,applid, time, sysid, termid, v The locks on the suspended changes are released to allow
tranid, taskno, termid,operid, uowid, instance, {1=DFHZRSY,
access by a user transaction
v Any associated suspended start commands are canceled to
6=DFHZSCX}
prevent premature action.
Destination: CSNE
User response: Examine the data to see whether the local
and remote changes made by the interrupted transaction took
DFHZC2106E date time applid Intersystem session recovery. effect. Make any changes required to restore consistency.
suspended changes now being committed. Module: DFHZRSY, DFHZSEX, DFHZSCX
Original failure details: Time= time. Remote
system=sysid. Intersystem terminal=termid. XMEOUT Parameters: date, time,applid, time, sysid, termid,
Transaction=tranid. Task number=taskno. tranid, taskno, termid,operid, uowid, instance, {1=DFHZRSY,
Operator terminal=termid. Operator=operid. 2=DFHZRSY, 3=DFHZSEX,4=DFHZSCX, 5=DFHZSCX,
Unit of work ID=uowid ((instance) Module 6=DFHZSCX}
name {DFHZRSY | DFHZSCX | DFHZSEX}) Destination: CSNE
Explanation: This is an informatory message issued during
intersystem session recovery as a follow-up to message
DFHZN2105. It has now been established that the remote DFHZC2114E date time applid termid tranid A SEND response
system completed the sync point, so the local changes are failed during receive-any processing. sense
being committed accordingly. ((instance) Module name: {DFHZRAC})
System action: The system commits local changes and Explanation: A SEND response issued on a receive-any RPL
unlocks. failed, or was not accepted by VTAM.
Module: DFHZRSY, DFHZSEX, DFHZSCX
XMEOUT Parameters: date, time,applid, time, sysid, termid, System action: If a task is attached, it is abnormally
tranid, taskno, termid,operid, uowid, instance, {1=DFHZRSY, terminated with a transaction dump. Message DFHME0116 is
2=DFHZRSY, 3=DFHZSEX,4=DFHZSCX, 5=DFHZSCX, normally produced containing the symptom string for this
6=DFHZSCX} problem.
Destination: CSNE User response: A subsequent message in the log, indicates

DFHZC2115 • DFHZC2301I
the reasons for the failure. Refer to this message for further
DFHZC2118 applid Receive Any stall for netname netname.
information and guidance.
Explanation: All the CICS Receive Any RPLs have been
Module: DFHZRAC
posted but the TCTTE for each one is waiting for a response
XMEOUT Parameters: date, time,applid, termid, tranid, sense, from a VTAM terminal or session. All the Receive Any RPLs
instance, {1=DFHZRAC, 2=DFHZRAC} have been stalled for 10 dispatches of the TCP task (CSTP).
Destination: CSNE This message is produced for each session that is in this
situation. A VTAM session has not responded to a command
such as BID or SHUTD sent by CICS. This is typically caused
DFHZC2115 applid termid Potential CICS hang detected by a protocol error.
following a SEND to node netname, CID System action: CICS is NOT running with system
X'cid'. Investigation is required. ((instance) initialization parameter RAPOOL=(n,FORCE) so CICS VTAM
Module name: {DFHZRAC}) activity is held up until one of the commands completes.
Explanation: CICS has issued a VTAM SEND macro to send User response: Issue the VTAM command V
a response but no notification has been received that the NET,INACT,ID=netname,I for one or more of the sessions
response has completed. Until this SEND operation completes, indicated by netname, to try and free a Receive Any RPL. Note
one of the limited number of receive-any RPLs remains - if the sessions are LU6.2 then the above command will
unusable (the number of receive-any RPLs is defined by the inactivate the partner APPLID to VTAM.
RAPOOL system initialization parameter).
Investigate why the CICS terminal control commands that
This is a serious condition. If all the receive-any RPLs become have caused the stall have not completed. If this is due to a
unusable in this way, CICS is unable to accept any new protocol error from the partner or device, attempt to get the
requests from VTAM. Similarly, a reduction in the number of protocol error corrected.
available receive-any RPLs can adversely affect terminal
performance and transaction throughput. Consider increasing the number of Receive Any RPLs
specified in the RAPOOL system initialization parameter. For
Additionally, while the RPL is hanging, a normal CICS instance, if you were using the old default of 2, increase this to
shutdown might be unable to complete. the new default of 50.
The CID is the 32-bit VTAM communication identifier which If you still get this message after changing the RAPOOL value
was assigned when the session was established. consider running CICS with system initialization parameter
System action: CICS continues to monitor for the SEND RAPOOL=(n,FORCE), which attempts to issue CLSDST for all
operation to complete. Until this happens, CICS reissues this the offending sessions or terminals and to re-issue the Receive
message at approximately three minute intervals. Any RPLs.
User response: This problem is usually caused by a failure in Module: DFHZRAC
the network which stops the SEND completing. Check the
session and the associated logical unit to ensure that there is XMEOUT Parameters: applid, netname
no error condition which stops VTAM completing the SEND Destination: Console
request.
Module: DFHZRAC
DFHZC2300 applid Recovery action requested for
XMEOUT Parameters: applid, termid,netname, X'cid', instance, connection sysid.
{1=DFHZRAC} Explanation: The XZIQUE global user exit program has been
Destination: Console invoked by CICS because of a potential problem with the
connection. The global user exit has used return code
UERCAKLL indicating that throughput on the connection is
DFHZC2117E date time applid termid tranid Data received on abnormally low and some exceptional action is required. The
pipeline session exceeds RAIA size. ((instance) poor performance of the connection can be caused by:
Module name: {DFHZRAC}) v Poor response on the receiving end
Explanation: CICS has received data on a pipeline session v Increased load on the sending end.
which is larger than the initial I/O area allocated for the
receive any RPL. The size of the receive any input area (RAIA) The condition may be intermittent. Message DFHZC2301 may
is specified on the RAMAX system initialization parameter. follow indicating that the connection has recovered.
System action: CICS ends the session which sent the data System action: CICS cancels all transactions which have
and marks it out of service. CICS will also attempt to outstanding queued requests to use the connection.
abnormally terminate any running transactions which where User response: Investigate the cause of the poor performance
initiated from this session. of the connection. Check the availability and condition of the
User response: Increase the value of the RAMAX system connected system.
initialization parameter so that it is at least equal to the largest Module: DFHZISP
RUSIZE (from the CINIT) specified for a pipeline session.
XMEOUT Parameters: applid, sysid
Module: DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, instance,
{1=DFHZRAC}
DFHZC2301I applid Connection sysid operating normally
Destination: CSNE
following recovery action.
Explanation: Message DFHZC2300 has been issued for this
connection. The connection has now recovered and is
operating normally.
User response: None

Module: DFHZISP System action: An exception entry code is made in the trace
table.
XMEOUT Parameters: applid, sysid
Destination: Console A system dump is taken unless you have specifically
DFHZC2302 applid SETLOGON start command rejected If the error occurs during CICS initialization, CICS issues
Explanation: CICS issues the SETLOGON START command message DFHZC0133 and terminates.
after a successful OPEN VTAM ACB. The SETLOGON START
If the error occurs as a result of a CEMT or EXEC CICS SET
command is rejected in the following cases:
VTAM OPEN, CICS closes the VTAM ACB.
v The CICS OPEN VTAM ACB was successful, but VTAM
User response: The VTAM return code can be found in
subsequently terminated abnormally, or
RTNCD-FDBK2 in the RPL, which is either in the exception
v The CICS OPEN VTAM ACB was successful, but insufficient
trace entry code, or in the RA pool addressed from TCTVRVRA
system storage was available to satisfy the SETLOGON
in the system dump.
START command, or
v The CICS OPEN VTAM ACB was successful, but VTAM Use section "VTAM codes" in z/VSE Messages and Codes -
was subsequently terminated by a VTAM HALT QUICK Volume 2 to determine the cause of the error and the actions
command. necessary to correct it.
System action: If the error occurs during CICS initialization,
CICS abnormally terminates with a U2302 abend and a system After correcting the error, either reinitialize CICS or reopen the
dump. VTAM ACB.
Module: DFHZGRP
If the error occurs as a result of a CEMT or EXEC CICS SET
VTAM OPEN, CICS terminates the task abnormally with XMEOUT Parameters: applid, X'code'
abend code ATC2 and a transaction dump, and the VTAM Destination: Console
ACB is closed.
User response: The VTAM return code can be found in DFHZC2305I applid Termination of VTAM sessions
RTNCD-FDBK2 in the first RPL in the RA pool addressed beginning
from TCTVRVRA in the system dump or the transaction Explanation: Either CICS or VTAM is being terminated, or a
dump. dynamic close of the VTAM ACB has been requested.
Use section "VTAM codes" in z/VSE Messages and Codes - System action: All CICS-VTAM sessions are closed and the
Volume 2 to determine the cause of the error and the actions ACB is closed. If termination is not orderly, active transactions
necessary to correct it. are abnormally terminated.
User response: When VTAM is active, communication may
After correcting the error, either reinitialize CICS (for abend be resumed by using the master terminal operator command
U2302) or follow the suggestions documented for abend ATC2. CEMT SET VTAM OPEN.
Module: DFHZSLS Module: DFHZSHU
DFHZC2303 applid No storage available when initiating DFHZC2307 applid CICS VTAM ABNORMALLY
RECEIVE-ANY's. Code: X'code' QUIESCING (modname).
Explanation: While trying to acquire receive-any I/O areas, Explanation: An RPL request has completed without a
the SETLOGON START VTAM command found that storage TCTTE token, for other than a VTAM storage shortage.
was not available. System action: CICS performs a FORCECLOSE of the ACB.
System action: CICS terminates with a dump. An exception
entry code is made in the trace table. CICS may produce this message twice as both module
DFHZRAC and module DFHZSYX may detect the condition.
A system dump is taken unless dumps have been specifically User response: When VTAM has been restarted, issue a
suppressed in the dump table. CEMT SET VTAM OPEN.
Module: DFHZRAC, DFHZSYX
Message DFHZC0133 is issued.
User response: Reduce the size of the RAMAX system Destination: Console
initialization parameter.
For further information, see the CICS Performance Guide. DFHZC2308 applid TCP Task WAIT failed. Unexpected
Module: DFHZGRP response from DSSR WAIT_OLDW call
(RESPONSE X'xx', REASON X'yy').
XMEOUT Parameters: applid, X'code' Explanation: The TCP task wait has failed. The TCP
Destination: Console dispatcher module, DFHZDSP, has received an unexpected
response, with response code X'xx' and reason code X'yy' from
the DSSR WAIT_OLDW call.
DFHZC2304 applid RECEIVE-ANY command rejected.
System action: CICS abends with abend U1800 and a system
Code: X'code'
dump is produced.
Explanation: This message is issued when the ACB has been
User response: Determine the cause of the TCP task wait
opened either during initialization or dynamic open.
failure. Investigate the dump in conjunction with any other
DFHZGRP was initiating the VTAM RECEIVE-ANY's but
accompanying error messages or exception trace entries which
VTAM was short on storage or the VTAM HALT QUICK
may have been issued by dispatcher domain.
command was issued.

DFHZC2309 • DFHZC2350A
Module: DFHZDSP Destination: Console
XMEOUT Parameters: applid, X'xx',X'yy'

Destination: Console DFHZC2318 applid The autoinstall user program progname
is not enabled. Module modname.
Explanation: While opening the VTAM ACB, CICS found
DFHZC2309 applid Recovery action requested for
that no installed program definition exists for the autoinstall
connection sysid using mode group modename.
user-program progname specified in the SIT.
Explanation: The XZIQUE global user exit program has been
invoked by CICS because of a potential problem with the
User response: If you want to use autoinstall, produce an
connection. The global user exit has used return code
installed program definition for the autoinstall user-program
UERCAKLM indicating that throughput on the connection is
progname specified in the SIT.
abnormally low and some exceptional action is required. The
Module: DFHSIJ1, DFHZOPA
poor performance of the connection can be caused by:
v Poor response on the receiving end XMEOUT Parameters: applid, progname, modname
v Increased load on the sending end. Destination: Console
The condition may be intermittent. Message DFHZC2310 may
follow indicating that the mode group has recovered. DFHZC2319 applid Unable to close VTAM ACB RC=xx
System action: CICS cancels all transactions which have error code=yy
outstanding queued requests to use this mode group. Explanation: The VTAM ACB CLOSE request failed.
User response: Investigate the cause of the poor performance System action: CICS continues as if the ACB is closed. (It is
of the mode group. Check the availability and condition of the not really closed.)
connected system. User response: Refer to section "VTAM codes" in z/VSE
Module: DFHZISP Messages and Codes - Volume 2 for an explanation of the return
and error codes.
XMEOUT Parameters: applid, sysid,modename
Destination: Console The return code xx is the VTAM return code in Register 15.
The error code yy is the ACB error flag 'ACBERFLG'.
Module: DFHZSHU
DFHZC2310I applid Connection sysid using mode group
modename operating normally following XMEOUT Parameters: applid, xx,yy
recovery action. Destination: Console
Explanation: Message DFHZC2309 has been issued for this
mode group. The mode group has now recovered and is
operating normally. DFHZC2320 CORRUPTED TCTTE ADDRESS FOUND
System action: Processing continues. DURING SHUTDOWN.
User response: None Explanation: A DFHTC CTYPE=LOCATE macro has returned
Module: DFHZISP an error indication while shutting down VTAM. This implies
that the TCTTE chain has been corrupted, possibly by an
XMEOUT Parameters: applid, sysid,modename overlay of the table manager control blocks.
Destination: Console System action: CICS is abnormally terminated with a system
dump.
User response: Investigate the dump to determine the cause
DFHZC2312 *** WELCOME TO CICS ***
of the problem.
Explanation: This is the CICS default good morning message
Module: DFHZSHU
for VTAM LUs. It is displayed unless an alternative GMTEXT
has been specified as a system initialization parameter, or the
typeterm definition logon message (LOGONMSG) has been set
to NO. DFHZC2350A date time applid CICS Terminal Control
System action: Processing continues. shutdown threshold (mm minutes) exceeded.
User response: None. Sessions still active: sesslist ((instance) Module
Module: DFHSIT name: {DFHZSHU})
Destination: Terminal End User Explanation: CICS' attempt to shut down the network has
not been completed within the time period allowed. This time
period, the terminal control shutdown wait threshold, is
DFHZC2316 applid VTAM ACB is closed
specified by the TCSWAIT system initialization parameter.
Explanation: CICS and VTAM have been disconnected. This
may be because: In the message, mm is the value of TCSWAIT, and sesslist is
v CICS is terminating, or the VTAM network names of the first 10 (if there are that
v VTAM is terminating, or many) hung VTAM terminals.
v The CICS master terminal operator has issued System action: CICS issues this message to both the CSNE
CEMT SET {VTAM CLOSED|IMMCLOSE|FORCECLOSE} transient data queue and the operating system console. This
System action: The VTAM ACB is closed. message is issued to the operating system console with a write
User response: If VTAM has not terminated, connection with to operator (WTO) message descriptor code of 2. This means
VTAM can be reestablished by using master terminal operator that the message is held by the operating system (that is, it
commands. does not roll off the screen) until the operator deletes it. For
Module: DFHZSHU each hung VTAM session, message DFHZC2351 is also issued.
DFHZC2351 gives further details of the session and is issued
XMEOUT Parameter: applid only to the CSNE transient data queue. CICS may attempt a

FORCECLOSE on the session (see message DFHZC2351 for Note: CLSDST is not guaranteed to work in all circumstances.
further details) but otherwise CICS terminal control shutdown The first 10 terminals (if there are that many) reported by this
continues as normal. message are also included in message DFHZC2350.
User response: Check the state of the terminal. Check
This message, DFHZC2350, is not processed by DFHZNAC whether the associated DFHZC3437 message includes
(node abnormal condition program), so the condition cannot CLSDST. If DFHZC3437 does not include CLSDST, or it does
be intercepted by the installation's DFHZNEP (node error but the CLSDST still fails to complete, take appropriate action
program). Note however that DFHZC2351 is processed by outside of CICS to shut down the terminal.
DFHZNAC and may be intercepted by the installation's
DFHZNEP. If after a reasonable interval, terminal control shutdown still
User response: Note the message, then delete it from the fails to complete (message DFHZC2316 is not displayed), take
operating system console using the CONTROL E (or K E) one of the following actions:
system command. See message DFHZC2351 for further v FORCECLOSE the CICS/VTAM ACB.
guidance. v Perform a CICS CEMT PERFORM SHUTDOWN
Module: DFHZSHU IMMEDIATE.
v Cancel the CICS job from the operating system console.
XMEOUT Parameters: date, time,applid, mm, sesslist, instance,
{1=DFHZSHU} Warning: Do not perform one of these actions unless there are
Destination: Console and Transient Data Queue CSNE no other suitable actions to take.
The reason why the terminal does not shutdown is more likely
DFHZC2351 date time applid termid netname Session still
to be a problem with the terminal device or the network, than
active after TC shutdown threshold expired.
with CICS.
Reason: {01 Request in progress | 02 Task
still active | 03 Waiting for SHUTC | 04
Waiting for BIS | 05 Waiting for UNBIND | If messages DFHZC2350, DFHZC2351, and DFHZC2352 are
06 Waiting for RTR | 07 BID in progress | 08 issued too early or too late in the shutdown process, take
Other TC work pending | 99 Undetermined} appropriate steps to change the TCSWAIT system initialization
sense ((instance) Module name: {DFHZSHU}) parameter on future runs of CICS. Once CICS has initialized,
Explanation: CICS' attempt to shut down the network has TCSWAIT cannot be changed.
not been completed within the time period allowed. The time Module: DFHZSHU
period, the terminal control shutdown wait threshold, is XMEOUT Parameters: date, time,applid, termid, netname, {1=01
specified by the TCSWAIT system initialization parameter. Request in progress, 2=02 Task still active, 3=03 Waiting for
This message is issued for each VTAM terminal that is still SHUTC, 4=04 Waiting for BIS,5=05 Waiting for UNBIND, 6=06
active (not shut down) after the time period has expired. Waiting for RTR, 7=07 BID in progress, 8=08 Other TC work
In the message termid and netname are respectively, the CICS pending,99=99 Undetermined}, sense, instance, {1=DFHZSHU}
terminal identifier, and the VTAM network name of the hung Destination: CSNE
terminal. One of the following is also included in the message
to indicate the reason for the hang: DFHZC2352 date time applid sysid netname Intersystem
01 Request in progress parallel connection still active after TC
02 Task still active shutdown threshold expired. ((instance)
03 Waiting for SHUTC Module {DFHZSHU}).
04 Waiting for BIS Explanation: CICS' attempt to shut down the network has
05 Waiting for UNBIND not been completed within the time period allowed. The time
06 Waiting for RTR period, the terminal control shutdown wait threshold, is
07 BID in progress specified by the TCSWAIT system initialization parameter.
08 Other TC work pending This message is issued for the first VTAM intersystem parallel
99 Undetermined session in each connection ( LU Type 6.1 and LU Type 6.2, but
System action: CICS may attempt a FORCECLOSE on the not LU Type 6.2 single-session APPC terminals) that is still
session but otherwise CICS terminal control shutdown active (not shut down) after the time period has expired.
continues normally. Whether CICS attempts a FORCECLOSE
depends upon: In the message sysid and netname are, respectively, the CICS
v The coding of the TCSACTN system initialization system identifier and the VTAM network name of the hung
parameter, and connection.
v How the installation's DFHZNEP (node error program) System action: CICS terminal control shutdown continues as
handles this condition. normal. Unlike terminals (see message DFHZC2351), terminal
control does not attempt a FORCECLOSE on hung parallel
If either of the following conditions is true: connections. This message is not processed by DFHZNAC
v TCSACTN=UNBIND, and this action is not changed by (node abnormal condition program), so the condition cannot
DFHZNEP, be intercepted by the installation''s DFHZNEP (node error
v TCSACTN=NONE, and this action is changed to program). Parallel connections reported by this message are
FORCECLOSE (UNBIND) by DFHZNEP not included in message DFHZC2350.
CICS terminal control issues a VTAM CLSDST and sends an User response: Check the state of the connection. Take
SNA UNBIND command. If neither of the conditions is true, appropriate action outside of this CICS system to shut down
no special action is taken. the connection.
If messages DFHZC2350, DFHZC2351, and DFHZC2352 are

issued too early or too late in the shutdown process, take

appropriate steps to change the TCSWAIT system initialization For the meaning of the sense data, see the explanation on
parameter on future runs of CICS. Once CICS has initialized topic “DFHZCxxxx messages” on page 356.
TCSWAIT cannot be changed. System action: The request is ignored. CICS prints the
Module: DFHZSHU associated session TCTTE on the CSNE transient data
destination. The RPL returned by VTAM is included in
XMEOUT Parameters: date, time,applid, sysid, netname, instance, exception trace entry AP FCA2.
{1=DFHZSHU} User response: Determine from the RPL in the exception
Destination: Console and Transient Data Queue CSNE trace why VTAM raised the error.
Module: DFHZRAS
DFHZC2400E date time applid termid tranid Error not XMEOUT Parameters: date, time,applid, termid, tranid, netname,
supported. sense ((instance) Module name: sense, instance, {1=DFHZRAS}
{DFHZSYX}) Destination: CSNE
Explanation: CICS received an unexpected error code from
VTAM.
DFHZC2403E date time applid termid tranid Bind failure. sense
For the meaning of the sense data, see the explanation on ((instance) Module name: {DFHZSYX})
topic “DFHZCxxxx messages” on page 356. Explanation: An attempt to establish a session has failed.
System action: CICS terminates the session. If a task is This could be because a physical path to the device could not
attached, it is abnormally terminated with a transaction dump. be found, because the device does not exist or has been
Message DFHME0116 is normally produced containing the defined incorrectly, or because the device has rejected the
symptom string for this problem. bind.
User response: Use the symptom string, and if necessary the For the meaning of the sense data, see the explanation on
transaction dump, to determine the source of the error. topic “DFHZCxxxx messages” on page 356.
Module: DFHZSYX
If this is an LU62 or LU61 session and the partner LU has sent
XMEOUT Parameters: date, time,applid, termid, tranid, sense, sense bytes of X'08350000' and oooo is the offset of the
instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX, NETNAME in the BIND, this indicates that the partner LU
4=DFHZSYX, 5=DFHZSYX, 6=DFHZSYX, 7=DFHZSYX, was unable to find a suitable session.
8=DFHZSYX, 9=DFHZSYX, 10=DFHZSYX}
Destination: CSNE If the sense bytes are X'08010000', this may mean that the
partner LU has failed to autoinstall a connection.
System action: Because communication cannot be established
DFHZC2401E date time applid termid tranid RPL Active. sense with a node, a VTAM CLSDST macro is issued to release any
((instance) Module name: {DFHZRVL | control blocks previously built, and the node could be placed
DFHZRVS | DFHZSDA | DFHZSDL | out of service.
DFHZSDR | DFHZSDS | DFHZSES | User response: Use the VTAM sense code given in the
DFHZSKR}) message to determine the cause of failure. If appropriate,
Explanation: CICS attempted to request VTAM services using ensure that the node name was included in the network
a request parameter list (RPL) that is currently active. control program/virtual storage (NCP/VS) generation deck
For the meaning of the sense data, see the explanation on and investigate for a possible bad communication line.
topic “DFHZCxxxx messages” on page 356. If the sense bytes were X'0835oooo' (where oooo is the offset
System action: CICS terminates the session. If a task is of the NETNAME in the BIND), the partner LU has been
attached, it is abnormally terminated with a transaction dump. unable to find a suitable session. If the partner LU is CICS,
Message DFHME0116 is normally produced containing the look in the partner LU's log for DFHZC2411 and previous
symptom string for this problem. messages for the same session. This should give some
User response: Use the symptom string, and if necessary, the indication as to why no session could be found.
transaction dump to determine the source of the error. If LU62 autoinstall is in use and the sense bytes were
Module: DFHZRVS, DFHZSDA, DFHZSDR, DFHZSDS, X'08010000' look in the partner LU's log for message
DFHZSES, DFHZSDL, DFHZRVL, DFHZSKR DFHZC2411 and message DFHZC69xx which should indicate
XMEOUT Parameters: date, time,applid, termid, tranid, sense, the reason for failure to autoinstall a connection.
instance, {1=DFHZRVS, 2=DFHZSDA, 3=DFHZSDL, Module: DFHZSYX
4=DFHZSDS, 5=DFHZSES, 6=DFHZSKR, 7=DFHZRVL, XMEOUT Parameters: date, time,applid, termid, tranid, sense,
8=DFHZSDR, 9=DFHZRVL, 10=DFHZRVL, 11=DFHZRVL, instance, {1=DFHZSYX}
12=DFHZSDL} Destination: CSNE
Destination: CSNE
DFHZC2404E date time applid termid tranid VTAM Detected

DFHZC2402I date time applid termid tranid netname VTAM Logic Error. sense ((instance) Module name:
has returned error on synchronous receive. {DFHZLEX})
sense ((instance) Module name: {DFHZRAS}) Explanation: VTAM detected an error in a request. The
Explanation: VTAM has indicated that a synchronous receive request was either incomplete or not executable.
issued by DFHZRAS during receive-any slow-down
processing did not complete successfully. This indicates a For the meaning of the sense data, see the explanation on
serious mismatch between CICS's view of the state of the topic “DFHZCxxxx messages” on page 356.
session and that of VTAM. System action: CICS breaks communication with the node
(CLSDST), abnormally terminates any attached task, places the

DFHZC2405E • DFHZC2409I
node out of service and produces a transaction dump. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
instance, {1=DFHZSYX}
Message DFHME0116 is normally produced containing the Destination: CSNE
User response: Ensure that all application programs running
concurrently have proper addressability, thereby avoiding DFHZC2407E date time applid termid tranid Permanent
alteration of CICS control blocks such as the TCTTE or the channel failure. sense ((instance) Module
RPL. If this message occurs during normal system execution, name: {DFHZSYX})
you will need further assistance from IBM. See Part 4 of the Explanation: Network Control Program/Virtual Storage
CICS Problem Determination Guide for guidance on how to (NCP/VS) was either shut down by the network operator or
proceed. was abnormally terminated. Alternatively, there could have
been a channel failure.
This message may also occur if VTAM is terminating. Under
these conditions it is not a serious problem, and usually no For the meaning of the sense data, see the explanation on
response is necessary. topic “DFHZCxxxx messages” on page 356.
Module: DFHZLEX System action: Since communication with the logical unit
was broken, the VTAM CLSDST macro is issued to release
XMEOUT Parameters: date, time,applid, termid, tranid, sense,
control blocks previously built by VTAM. If a task is attached,
instance, {1=DFHZLEX, 2=DFHZLEX, 3=DFHZLEX,
it is abnormally terminated with a transaction dump.
4=DFHZLEX, 5=DFHZLEX, 6=DFHZLEX}
User response: Use the supplied dump to check for a
Destination: CSNE
possible NCP/VS or channel problem.
Module: DFHZSYX
DFHZC2405E date time applid termid tranid Node netname not
activated. sense ((instance) Module name:
instance, {1=DFHZSYX, 2=DFHZSYX}
{DFHZSIM | DFHZSIX | DFHZSYX})
Destination: CSNE
Explanation: The node was not activated, or was deactivated
by the network operator.
DFHZC2408E date time applid termid tranid Apparent VTAM
Error. sense ((instance) Module name:
{DFHZSYX})
System action: All outstanding SEND and RECEIVE requests
Explanation: VTAM encountered an error during its own
are purged. If a task is attached, it is abnormally terminated
processing.
with a transaction dump. A VTAM CLSDST macro is issued to
halt communication with the node, and internal LOGONs are For the meaning of the sense data, see the explanation on
prevented. topic “DFHZCxxxx messages” on page 356.
System action: If a task is attached, it is abnormally
If this message is issued during takeover, the acquire is retried
terminated with a transaction dump. The node is placed out of
at intervals of 1, 2, 4 and 8 minutes after the first attempt. This
service.
allows time for sessions which require manual intervention
before the acquire can succeed. Message DFHME0116 is normally produced containing the
User response: Use the VTAM VARY command to activate symptom string for this problem.
the node before using it in the network. User response: Use the sense data to determine the nature of
the error.
It is possible that the node in question has previously been
Module: DFHZSYX
used as a generic APPLID (or in VTAM terms – a USERVAR).
Use the VTAM operator command DISPLAY USERVAR to see XMEOUT Parameters: date, time,applid, termid, tranid, sense,
if this is the case. If it is, you can use MODIFY instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX,
USERVAR,OPTION=DELETE,ID=node to delete the USERVAR. 4=DFHZSYX}
Module: DFHZSYX, DFHZSIX, DFHZSIM Destination: CSNE
XMEOUT Parameters: date, time,applid, termid, tranid, netname,
sense, instance, {1=DFHZSIM, 2=DFHZSIM, 3=DFHZSIM, DFHZC2409I date time applid termid tranid VTAM Recovered
4=DFHZSIM, 5=DFHZSIM, 6=DFHZSYX, 7=DFHZSYX, Node. LOSTERM Error Code X'xx'. sense
8=DFHZSYX, 9=DFHZSIX, 10=DFHZSYX, 11=DFHZSYX} ((instance) Module name: {DFHZLTX})
Destination: CSNE Explanation: VTAM successfully reestablished
communication with a node. The reason for entering the
LOSTERM exit is given by xx, which has one of the following
DFHZC2406E date time applid termid tranid Terminate self
values:
command received. sense ((instance) Module
name: {DFHZSYX}) Value Meaning
Explanation: The logical unit (LU) has requested termination 0 Dial-disconnect on dial-in.
of the session. 4 Dial-disconnect on dial-out.
0C Deactivate immediate.
14 Unconditional terminate self.
1C Segmenting error.
System action: The VTAM CLSDST macro is issued to stop
20 Conditional terminate self.
communications with the node. If a task is attached, it is
24 BUFLIM value exceeded.
abnormally terminated with a transaction dump.
Module: DFHZSYX

For the meaning of the sense data, see the explanation on 12 RESERVED.
topic “DFHZCxxxx messages” on page 356. 13 No address is present in the RPL.
System action: CICS reestablishes communication and places 14 LU6.1 cannot autoinstall.
the node in service. 15 ISC support is not present.
User response: None. 16 Modename is either not present or is the reserved
Module: DFHZLTX name SNASVCMG.
17 Session is not bound.
XMEOUT Parameters: date, time,applid, termid, tranid, X'xx', 18 Not used.
sense, instance, {1=DFHZLTX, 2=DFHZLTX} 19 LU is not enabled. Typically it is an XRF alternate
Destination: CSNE CICS.
20 A second CINIT with the same netname has arrived.
DFHZC2410E date time applid termid tranid Node 21 Logon rejected due to CATA abend.
Unrecoverable. VTAM LOSTERM Error Code
X'xx'. sense ((instance) Module name: For the meaning of the sense data, see the explanation on
{DFHZLTX}) topic “DFHZCxxxx messages” on page 356.
Explanation: Communication with a node was interrupted
and cannot be reestablished by VTAM. The reason for entering If ???????? is displayed in the second half of the nodeid field,
the LOSTERM exit is given by the error code X'xx'. the BIND may contain a SESSION QUALIFIER or
MODENAME with an invalid length.
System action: The logon is rejected. If the reject is from
DFHZSCX via the dummy TCTTE, an attempt is made to
System action: The VTAM CLSDST macro is issued to release
print the failing BIND and sense code with which it was
any control blocks previously built for the node. If a task is
rejected as part of the message.
attached, it is abnormally terminated with a transaction dump.
User response: Use the instance number to determine why
User response: See the VTAM Programming manual for an
the attempted logon has been rejected and take the
explanation of the error code.
appropriate action.
Module: DFHZLTX
Module: DFHACP, DFHZATA, DFHZLGX, DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, X'xx',
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid,
sense, instance, {1=DFHZLTX, 2=DFHZLTX, 3=DFHZLTX,
sense, instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZSCX,
4=DFHZLTX}
4=DFHZSCX, 5=DFHZSCX, 6=DFHZSCX, 7=DFHZATA,
Destination: CSNE
8=DFHZLGX, 9=DFHZLGX, 10=DFHZLGX, 11=DFHZSCX,
12=RESERVE, 13=DFHZLGX, 14=DFHZLGX, 15=DFHZLGX,
DFHZC2411E date time applid termid tranid nodeid attempted 16=DFHZLGX, 17=DFHZLGX, 18=DFHZLGX, 19=DFHZLGX,
invalid logon. sense ((instance) Module name: 20=DFHZLGX, 21=DFHACP}
{DFHACP | DFHZATA | DFHZLGX | Destination: CSNE
DFHZSCX | RESERVE})
Explanation: Node nodeid attempted to log on to CICS but
DFHZC2412E date time applid termid tranid Receive any
the logon is invalid.
request failed. sense ((instance) Module name:
If the message is issued by DFHZATA, CICS has failed in its {DFHZRAC})
attempt to autoinstall the terminal or connection. Explanation: A receive-any request to VTAM failed. VTAM
was terminated.
The instance instance is one of the following:
1 No suitable TCTTE can be found, or no session For the meaning of the sense data, see the explanation on
TCTTE exists. The nodeid in the message is displayed topic “DFHZCxxxx messages” on page 356.
as 'netname' followed by either eight blanks or eight System action: The VTAM RPL control block is logged to the
dots. The reason for this is that the bind did not CSMT log for visual inspection.
contain a modename.
2 The connection has not been acquired.
3 The logon would have exceeded the connection
User response: Determine the reason why the receive-any
session limit.
failed. First, check to see if the VTAM RPL has been altered. If
4 Autoinstall is not allowed because the system is
it has been altered, check to see if the alterations could have
terminating.
caused any problems. Correct any obvious errors. It may be
5 Autoinstall is not allowed because the VTAM ACB is
useful to refer to section "VTAM codes" in z/VSE Messages and
closing.
Codes - Volume 2 during problem determination to interpret the
6 ISC support is not present.
sense data.
7 Used by DFHZATA for several reasons, for example
Module: DFHZRAC
BIND bad and user exit bad.
8 The TCTTE address restored and the address found XMEOUT Parameters: date, time,applid, termid, tranid, sense,
by NIBSEARCH do not agree. instance, {1=DFHZRAC, 2=DFHZRAC}
9 The system is terminating. Destination: CSNE
10 VTAM is terminating.
11 An APPC BIND has been received by the SCIP exit
for which no suitable TCTTE exists. Autoinstall
could not proceed because the modegroup was not
SNASVCMG. The request is rejected with sense 0805
0000.

further requests and the node is placed out of service.

DFHZC2413E date time applid termid tranid nodeid CLSDST
failed. sense ((instance) Module name:
Module: DFHZSYX
{DFHACP | DFHZATA | DFHZLGX})
Explanation: A CLSDST request for the node identified by XMEOUT Parameters: date, time,applid, termid, tranid, sense,
nodeid failed. VTAM may not have sufficient space to respond instance, {1=DFHZSYX, 2=DFHZSYX}
to the request. Destination: CSNE
topic “DFHZCxxxx messages” on page 356. DFHZC2417E date time applid termid tranid VTAM Inactive to
System action: No further communication with the node is TCB. sense ((instance) Module name:
initiated. {DFHZCLS | DFHZCLX | DFHZOPN |
User response: Inspect the CSNE, CSMT and CSTL logs for DFHZOPX | DFHZRAC | DFHZRLP |
indication of a VTAM storage problem or error message. Also DFHZRST | DFHZRVL | DFHZRVS |
check for any messages indicating an I/O problem. DFHZRVX | DFHZSDA | DFHZSDL |
Module: DFHACP, DFHZATA, DFHZLGX DFHZSDR | DFHZSDS | DFHZSES |
DFHZSIM | DFHZSIX | DFHZSKR |
DFHZSLX | DFHZSYX | DFHZTAX})
sense, instance, {1=DFHZATA, 2=DFHZLGX, 3=DFHACP}
Explanation: Either CICS has not opened its VTAM ACB or
Destination: CSNE
VTAM has halted.

DFHZC2414E date time applid termid tranid Temporary VTAM
Storage Problem. sense ((instance) Module
System action: The VTAM network is quiesced to prevent
name: {DFHZSYX})
further requests and a dump is produced.
Explanation: A VTAM request has failed because VTAM is
User response: If VTAM was not halted by the network
short of storage.
operator, use the supplied dump to determine the problem.
For the meaning of the sense data, see the explanation on Module: DFHZSYX, DFHZCLS, DFHZCLX, DFHZOPN,
topic “DFHZCxxxx messages” on page 356. DFHZOPX, DFHZRAC, DFHZRLP, DFHZRST, DFHZRVL,
System action: The failing VTAM request is retried until DFHZRVS, DFHZRVX, DFHZSDL, DFHZSDR, DFHZSDS,
VTAM is able to accept it. DFHZSES, DFHZSIM, DFHZSIX, DFHZSKR, DFHZSLX,
User response: Increase the VTAM working buffer storage if DFHZTAX, DFHZSDA
this condition recurs and causes problems.
Module: DFHZSYX
instance, {1=DFHZOPX, 2=DFHZCLS, 3=DFHZOPN,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, 4=DFHZRLP, 5=DFHZRST, 6=DFHZRVS, 7=DFHZRVX,
instance, {1=DFHZSYX} 8=DFHZSDA, 9=DFHZSDL, 10=DFHZSDS, 11=DFHZSES,
Destination: CSNE 12=DFHZSIM, 13=DFHZSKR, 14=DFHZSLX, 15=DFHZRAC,
16=DFHZCLX, 17=DFHZRVL, 18=DFHZSDR, 19=DFHZSIX,
20=DFHZTAX, 21=DFHZOPX, 22=DFHZSYX}
DFHZC2415E date time applid termid tranid Node netname out Destination: CSNE
of service. sense ((instance) Module name:
{DFHZNAC})
Explanation: A node error condition has occurred on node DFHZC2418E date time applid termid tranid Unknown
nodeid. command in RPL. sense ((instance) Module
name: {DFHZSEX})
For the meaning of the sense data, see the explanation on Explanation: An unknown command was detected in the
topic “DFHZCxxxx messages” on page 356. VTAM request parameter list (RPL) by the CICS SESSIONC
System action: CICS places the node out of service. exit routine. The RPL address could be invalid or the RPL
User response: Use the sense data to determine the nature of could have been altered.
the error.
Module: DFHZNAC For the meaning of the sense data, see the explanation on
XMEOUT Parameters: date, time,applid, termid, tranid, netname, System action: All outstanding send and receive requests are
sense, instance, {1=DFHZNAC} purged. If a task is attached, it is abnormally terminated with
Destination: CSNE a transaction dump.
DFHZC2416E date time applid termid tranid VTAM is halting. symptom string for this problem.
sense ((instance) Module name: {DFHZSYX})
Explanation: A VTAM HALT command was entered by the A CLSDST is issued to halt communication with the node, and
network operator while a SIMLOGON or OPNDST request the node is placed out of service.
was in progress. The instance number indicates what type of User response: First, check if the VTAM RPL has an invalid
halt was requested: address. If the address is valid, check to see if the RPL has
1 Orderly shutdown been altered. If it has been altered, check to see if the
2 Quick shutdown. alterations could have caused any problems. Correct any
obvious errors. It may be useful to refer to section "VTAM
For the meaning of the sense data, see the explanation on codes" in z/VSE Messages and Codes - Volume 2 during problem
topic “DFHZCxxxx messages” on page 356. determination to interpret the sense data.
System action: The VTAM network is quiesced to prevent Module: DFHZSEX


DFHZC2421E date time applid termid tranid Unsupported
instance, {1=DFHZSEX, 2=DFHZSEX}
command received. sense ((instance) Module
Destination: CSNE
name: {DFHZRAC | DFHZRLP |
DFHZRVX})
DFHZC2419E date time applid termid tranid Unknown Explanation: An unknown command or request was
command in RPL. sense ((instance) Module detected, or the RPL contains logical unit (LU) status.
name: {DFHZRAC | DFHZSLX | DFHZSSX})
Explanation: An unknown command was detected in the
request parameter list (RPL) by the send-data-flow
System action: If an invalid command or request was
synchronous exit routine. The RPL address could be invalid or
detected, all outstanding send and receive requests are purged.
the RPL could have been altered.
If a task is attached, it is abnormally terminated with a
For the meaning of the sense data, see the explanation on transaction dump. A VTAM CLSDST macro is issued to halt
topic “DFHZCxxxx messages” on page 356. communication with the node.
System action: All outstanding send and receive requests are
For ISC sessions, this error may be caused by specifying
purged. If a task is attached, it is abnormally terminated with
incompatible session types at each node. (For example,
a transaction dump.
SESSIONTYPE=SEND in one node and
Message DFHME0116 is normally produced containing the SESSIONTYPE=FASTRECV in the other node.)
If the RPL contains logical unit (LU) status, one of the
A VTAM CLSDST macro is issued to halt communication with following messages is issued: DFHZC2461, DFHZC2462,
the node, and the node is placed out of service. DFHZC2464, DFHZC2465, or DFHZC2466.
User response: In the first instance, check if the VTAM RPL
has an invalid address. If the address is valid, check to see if
the RPL has been altered. If it has been altered, check to see if
User response: An invalid command or request indicates
the alterations could have caused any problems. Correct any
inconsistencies or errors in the definitions of the named
obvious errors. It may be useful to refer to section "VTAM
terminals/sessions in CICS, VTAM or the connected system
codes" in z/VSE Messages and Codes - Volume 2 during problem
for LU6 sessions. Ensure that these definitions are consistent
determination to interpret the sense data.
and correct for the device or session characteristics.
Module: DFHZSSX, DFHZSLX, DFHZRAC
Module: DFHZRAC, DFHZRVX, DFHZRLP
instance, {1=DFHZSSX, 2=DFHZSLX, 3=DFHZRAC,
instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRVX,
4=DFHZRAC, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC,
4=DFHZRVX, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC,
8=DFHZRAC}
8=DFHZRAC, 9=DFHZRAC}
Destination: CSNE
Destination: CSNE
DFHZC2420E date time applid termid tranid Unknown DFHZC2422E date time applid termid tranid ZCP Logic Error.
command in RPL. sense ((instance) Module sense ((instance) Module name: {DFHZARL |
name: {DFHZSAX}) DFHZDET | DFHZERH | DFHZEV1 |
Explanation: An unknown command was detected in the DFHZEV2 | DFHZNAC | DFHZOPN |
request parameter list (RPL) by the send-data-flow DFHZRAC | DFHZRVS | DFHZSDS |
asynchronous exit routine. The RPL address could be invalid DFHZSIM | DFHZSKR | DFHZSLX |
or the RPL could have been altered. DFHZSSX})
For the meaning of the sense data, see the explanation on Explanation: During terminal processing, CICS detected an
topic “DFHZCxxxx messages” on page 356. invalid internal state in DFHZCP.
System action: All outstanding send and receive requests are For the meaning of the sense data, see the explanation on
purged. If a task is attached, it is abnormally terminated with topic “DFHZCxxxx messages” on page 356.
a transaction dump. System action: All outstanding send and receive requests are
Message DFHME0116 is normally produced containing the purged, and the task is abnormally terminated with a
symptom string for this problem. transaction dump. The node is placed out of service and the
TCTTE, RPL, and action flags are logged to the CSMT
A VTAM CLSDST macro is issued to halt communication with destination for debugging purposes.
the node, and the node is placed out of service.
User response: In the first instance, check if the VTAM RPL Message DFHME0116 is normally produced containing the
has an invalid address. If the address is valid, check to see if symptom string for this problem.
the RPL has been altered. If it has been altered, check to see if User response: Ensure that the application programs running
the alterations could have caused any problems. Correct any concurrently do not alter the TCTTE. If the TCTTE is not
obvious errors. It may be useful to refer to section "VTAM being altered, use the dump to locate the source of the error.
codes" in z/VSE Messages and Codes - Volume 2 during problem It may be useful to examine the debugging data printed on
determination to interpret the sense data. the CSMT log for clues about what possibly went wrong.
Module: DFHZSAX Module: DFHZARL, DFHZDET, DFHZERH, DFHZEV1,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, DFHZEV2, DFHZOPN, DFHZRAC, DFHZRVS, DFHZSDS,
instance, {1=DFHZSAX} DFHZSIM, DFHZSKR, DFHZSLX, DFHZNAC, DFHZSSX
Destination: CSNE XMEOUT Parameters: date, time,applid, termid, tranid, sense,

instance, {1=DFHZDET, 2=DFHZSIM, 3=DFHZSIM, Communication with the node is terminated by issuing the
4=DFHZERH, 5=DFHZERH, 6=DFHZERH, 7=DFHZERH, VTAM CLSDST macro.
8=DFHZERH, 9=DFHZERH, 10=DFHZERH, 11=DFHZERH, User response: Ensure that application programs running
12=DFHZERH, 13=DFHZERH, 14=DFHZNAC, 15=DFHZERH, concurrently do not alter the TCTTE.
16=DFHZERH, 17=DFHZERH, 18=DFHZERH, 19=DFHZSDS,
If the TCTTE is not altered, check for conditions 2 or 3.
20=DFHZEV1, 21=DFHZEV1, 22=DFHZOPN, 23=DFHZOPN,
Module: DFHZSES
24=DFHZRVS, 25=DFHZRVS, 26=DFHZSKR, 27=DFHZSSX,
28=DFHZSLX, 29=DFHZSLX, 30=DFHZRAC, 31=DFHZRAC, XMEOUT Parameters: date, time,applid, termid, tranid, sense,
32=DFHZRAC, 33=DFHZRAC, 34=DFHZRAC, 35=DFHZRAC, instance, {1=DFHZSES, 2=DFHZSES}
36=DFHZRAC, 37=DFHZRAC, 38=DFHZRAC, 39=DFHZARL, Destination: CSNE
40=DFHZARL, 41=DFHZEV2, 42=DFHZEV2, 43=DFHZRAC,
44=DFHZRAC, 45=DFHZOPN}
Destination: CSNE DFHZC2425E date time applid termid tranid ASYNC command
request invalid. sense ((instance) Module
name: {DFHZSDA})
DFHZC2423E date time applid termid tranid Attempted to Explanation: A request to send data asynchronously was
send unsupported command. sense ((instance) incomplete or invalid. This condition can be caused by the
Module name: {DFHZSDS}) TCTTE being altered.
Explanation: A request to send data synchronously was
incomplete. Possible reasons are as follows: For the meaning of the sense data, see the explanation on
1. The TCTTE was altered. topic “DFHZCxxxx messages” on page 356.
2. A logic error was encountered. System action: All outstanding send and receive requests are
3. The TCTTE was inadvertently placed on the purged. If a task is attached, it is abnormally terminated with
send-synchronous queue. a transaction dump.

For the meaning of the sense data, see the explanation on symptom string for this problem.
System action: All outstanding send and receive requests are Communication with the node is terminated by issuing the
purged. If a task is attached, it is abnormally terminated with VTAM CLSDST macro.
a transaction dump. Communication with the node is User response: Check the TCTTE. Ensure that application
terminated by issuing the VTAM CLSDST macro. programs running concurrently do not alter the TCTTE.
User response: For reasons 1 to 3 listed above, ensure that Module: DFHZSDA
application programs running concurrently do not alter the
TCTTE.
instance, {1=DFHZSDA, 2=DFHZSDA}
If you suspect a logic error (2), check that the VTAM RPL has Destination: CSNE
not been corrupted. If you still cannot resolve the problem,
you will need further assistance from IBM. See Part 4 of the
DFHZC2426E date time applid termid tranid Node Status Error.
Node is out of service or receive only. sense
proceed.
((instance) Module name: {DFHZATT})
Module: DFHZSDS
Explanation: Input was received from a node identified
XMEOUT Parameters: date, time,applid, termid, tranid, sense, either as output-only or as permanently out of service.
instance, {1=DFHZSDS}
Destination: CSNE
DFHZC2424E date time applid termid tranid SESSIONC purged. If a task is attached, it is abnormally terminated with
command request invalid. sense ((instance) a transaction dump.
Module name: {DFHZSES}) User response: Change the terminal entry in the TCT to
Explanation: A SESSIONC request is incomplete or invalid. indicate that the node is not an output-only device. If the node
Possible reasons are as follows: is out of service, the master terminal operator should place the
1. The TCTTE was altered. node back into service.
2. The command request bits are incomplete. DFHZSES Module: DFHZATT
checks TCTEISDT for a start data traffic (SDT) command,
TCTEISTS for a set and test sequence number (STSN)
instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT}
command, and TCTEICLR for a CLEAR command. If it
Destination: CSNE
does not find any of these, DFHZSES causes the message
to be issued.
3. The wrong request was queued to SESSIONC. DFHZC2427I date time applid termid tranid NCP Restarted.
sense ((instance) Module name: {DFHZSYX})
For the meaning of the sense data, see the explanation on Explanation: Network Control Program/Virtual Storage
topic “DFHZCxxxx messages” on page 356. (NCP/VS) has been restarted after failing during an OPNDST.
a transaction dump.
System action: The OPNDST request is reissued.
Message DFHME0116 is normally produced containing the User response: None.
symptom string for this problem. Module: DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, User response: Check the VTAM RPL for obvious errors.
instance, {1=DFHZSYX} Ensure that application programs running concurrently do not
Destination: CSNE alter the TCTTE. If the TCTTE is not being altered, use the
dump to determine the source of the error.
Module: DFHZSDR
DFHZC2428E date time applid termid tranid Send DFSYN
request incomplete. sense ((instance) Module XMEOUT Parameters: date, time,applid, termid, tranid, sense,
name: {DFHZSDS}) instance, {1=DFHZSDR}
Explanation: A send-synchronous request was issued without Destination: CSNE
indicating that either a command or data was to be sent.
For the meaning of the sense data, see the explanation on DFHZC2431E date time applid termid tranid Request to a
topic “DFHZCxxxx messages” on page 356. released node. sense ((instance) Module name:
System action: All outstanding send and receive requests are {DFHZSYX})
purged. If a task is attached, it is abnormally terminated with Explanation: CICS requested VTAM to perform a close
a transaction dump. destination for a node currently “owned” by CICS.
Message DFHME0116 is normally produced containing the For the meaning of the sense data, see the explanation on
symptom string for this problem. topic “DFHZCxxxx messages” on page 356.
User response: Check the VTAM RPL for obvious errors. System action: If the CICS ACB is open, all outstanding
Ensure that application programs running concurrently do not requests are purged and the task is abnormally terminated
alter the TCTTE. If the TCTTE is not being altered, use the with a transaction dump if a task is attached.
symptom string, and if necessary, the dump to determine the User response: If the CICS ACB is open, use the dump to
source of the error. determine the source of the error. Check that the TCTTE is
Module: DFHZSDS valid.
Module: DFHZSYX
instance, {1=DFHZSDS} XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Destination: CSNE instance, {1=DFHZSYX}
Destination: CSNE
DFHZC2429E date time applid termid tranid RESETSR request

invalid RTYPE. sense ((instance) Module name: DFHZC2432E date time applid termid tranid Exception
{DFHZRST}) response received. sense ((instance) Module
Explanation: An invalid RESETSR request was made in the name: {DFHZRAC | DFHZRVX |
VTAM macro issued by CICS. The invalid request can be DFHZSSX})
because an RTYPE was not specified or was incorrectly Explanation: CICS has received an exception response.
specified, or the TCTTE was altered.
For the meaning of the sense data, see the explanation on topic “DFHZCxxxx messages” on page 356.
topic “DFHZCxxxx messages” on page 356. System action: Another CICS message is issued in
System action: All outstanding receive requests are purged. conjunction with this message.
If a task is attached, it is abnormally terminated with a User response: Perform the action specified for the associated
transaction dump. CICS message.
Module: DFHZRAC, DFHZRVX, DFHZSSX
symptom string for this problem. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
User response: Check the VTAM RPL for obvious errors. instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX,
Ensure that application programs running concurrently do not 4=DFHZRVX, 5=DFHZRVX, 6=DFHZRVX, 7=DFHZRVX,
alter the TCTTE. If the TCTTE is not being altered, use the 8=DFHZSSX, 9=DFHZSSX, 10=DFHZSSX, 11=DFHZSSX,
symptom string, and if necessary the dump, to determine the 12=DFHZRAC, 13=DFHZRAC, 14=DFHZRAC, 15=DFHZRAC,
source of the error. 16=DFHZRAC, 17=DFHZRAC, 18=DFHZRAC, 19=DFHZRAC,
Module: DFHZRST 20=DFHZRAC, 21=DFHZRAC, 22=DFHZRAC, 23=DFHZRAC}
Destination: CSNE
instance, {1=DFHZRST, 2=DFHZRST, 3=DFHZRST}
Destination: CSNE DFHZC2433E date time applid termid tranid nodeid Logon has
failed because autoinstall is disabled. sense
((instance) Module name: {DFHZLGX |
DFHZC2430E date time applid termid tranid Send response
DFHZSCX})
command request invalid. sense ((instance)
Explanation: Node nodeid attempted to log on to CICS. The
Module name: {DFHZSDR})
logon has failed because autoinstall is disabled. Possible
Explanation: A send-response request was invalid. Either the
reasons are:
request did not specify the response level (DR1 or DR2), or the
v Autoinstall system initialization parameters have been
TCTTE was altered.
incorrectly defined.
For the meaning of the sense data, see the explanation on v An error has been detected in CICS terminal attach
topic “DFHZCxxxx messages” on page 356. processing.
System action: All outstanding send requests are purged. If a v The system is short on storage. Autoinstall is reenabled once
task is attached, it is abnormally terminated with a transaction the SOS condition ends.
dump and the node is placed out of service. System action: The logon is rejected.

User response: Ensure that the value for the AIQMAX For the meaning of the sense data, see the explanation on
system initialization parameter is greater than zero. If an topic “DFHZCxxxx messages” on page 356.
autoinstall user program has been specified for system System action: All outstanding receive requests are purged.
initialization parameter AIEXIT, check that the program name If a task is attached, it is abnormally terminated with a
has been defined to CICS. See the CICS System Definition Guide transaction dump.
for further information about autoinstall parameters. User response: Use the dump to determine if the TCTTE was
altered by an application program.
If the system is short on storage, see the associated messages Module: DFHZRVS, DFHZRVX
for further guidance.
Module: DFHZLGX, DFHZSCX XMEOUT Parameters: date, time,applid, termid, tranid, sense,
instance, {1=DFHZRVS, 2=DFHZRVX, 3=DFHZRVS}
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, Destination: CSNE
sense, instance, {1=DFHZLGX, 2=DFHZLGX, 3=DFHZSCX,
4=DFHZSCX}
Destination: CSNE DFHZC2437E date time applid termid tranid Invalid WRITE
request to an input only device. sense
((instance) Module name: {DFHZSDS})
DFHZC2434E date time applid termid tranid Invalid copy
Explanation: An output request was issued to a VTAM
request - Copy not supported. sense ((instance)
terminal that is defined as an input-only device. Either the
Module name: {DFHZARQ})
TCTTETS was altered or a task that was attached issued a
Explanation: A DFHTC TYPE=COPY request has been issued
send request.
to a 3270 compatibility mode logical unit. The request is
invalid because the 3270 COPY command is not supported by For the meaning of the sense data, see the explanation on
a 3270 compatibility mode logical unit. topic “DFHZCxxxx messages” on page 356.
System action: All outstanding send requests are purged. If a
task is attached, it is abnormally terminated with a transaction
dump. The terminal status remains unchanged.
System action: The task abends.
User response: Either ensure that the node is defined
User response: Change the application program to avoid
correctly in the TCTTE, or prevent the task from issuing an
issuing a COPY request.
output request to the node.
Module: DFHZARQ
Module: DFHZSDS
instance, {1=DFHZARQ}
instance, {1=DFHZSDS}
Destination: CSNE
Destination: CSNE
DFHZC2435E date time applid termid tranid RPL missing. sense

DFHZC2438E date time applid termid tranid Invalid READ
((instance) Module name: {DFHZRVS})
request to an output only device. sense
Explanation: CICS issued a receive-specific request VTAM
((instance) Module name: {DFHZRVS |
without specifying a request parameter list (RPL). This
DFHZSDS})
condition could result from one of the following reasons:
Explanation: An input request was issued to a VTAM
v An RPL was not allocated
terminal that is identified as an output-only device. Either the
v An RPL was allocated, but later freed TCTTETS was altered or a task was attached that issued a
v TCTERPLA was altered.
read request.
For the meaning of the sense data, see the explanation on For the meaning of the sense data, see the explanation on
topic “DFHZCxxxx messages” on page 356. topic “DFHZCxxxx messages” on page 356.
System action: All outstanding receive requests are purged. System action: All outstanding receive requests are purged.
If a task is attached, it is abnormally terminated with a If a task is attached, it is abnormally terminated with a
transaction dump. A CLSDST macro is issued to terminate transaction dump. The terminal status remains unchanged.
communication with the node. User response: Either change the definition of the terminal in
User response: Use the dump to determine whether the the TCTTE, or prevent the task from issuing input requests to
TCTTE was altered by an application program. If it was, the node.
correct the error. If the TCTTE has not been altered, check for Module: DFHZRVS, DFHZSDS
potential RPL problems.
Module: DFHZRVS
instance, {1=DFHZRVS, 2=DFHZSDS}
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Destination: CSNE
instance, {1=DFHZRVS}
Destination: CSNE
DFHZC2439E date time applid termid tranid Invalid RESUME
request. sense ((instance) Module name:
DFHZC2436E date time applid termid tranid TIOA missing. {DFHZACT})
sense ((instance) Module name: {DFHZRVS | Explanation: An invalid resume request was received. The
DFHZRVX}) CICS activate-scan function detected a resume request in a
Explanation: The TIOA was missing while a receive-specific TCTTE, but the TCTTE was not part of any transaction.
request was being processed. This condition could result from
the TIOA being freed or TCTTEDA being altered.

DFHZC2440I • DFHZC2445E
System action: The TCTTE is printed and logged to the

DFHZC2443E date time applid termid tranid Request
CSNE destination for debugging purposes.
outstanding when node released. sense
Message DFHME0116 is normally produced containing the ((instance) Module name: {DFHZRVL |
symptom string for this problem. DFHZRVS | DFHZSDL | DFHZSDS |
User response: Use the symptom string to determine the DFHZSHU})
cause of the problem. Check the TCTTE data printed and Explanation: CICS received a request from an application
logged to the CSNE destination for obvious alterations and program, when its node was either not in session or queued to
errors. be CLSDSTed.
Module: DFHZACT
XMEOUT Parameters: date, time,applid, termid, tranid, sense, topic “DFHZCxxxx messages” on page 356.
instance, {1=DFHZACT} System action: All outstanding requests are ignored. If a task
Destination: CSNE is attached, it is abnormally terminated with a transaction
dump.
DFHZC2440I date time applid termid tranid CICS quiesced by Module: DFHZSDS, DFHZRVL, DFHZRVS, DFHZSDL,
node. sense ((instance) Module name: DFHZSHU
{DFHZASX})
Explanation: A VTAM logical unit has requested CICS to XMEOUT Parameters: date, time,applid, termid, tranid, sense,
quiesce all I/O activity with that node. instance, {1=DFHZRVS, 2=DFHZSDL, 3=DFHZSDS,
4=DFHZSDS, 5=DFHZSDS, 6=DFHZSHU, 7=DFHZSHU,
For the meaning of the sense data, see the explanation on 8=DFHZRVL, 9=DFHZSHU}
topic “DFHZCxxxx messages” on page 356. Destination: CSNE
System action: All data transmission to the node is halted
until CICS receives a release-quiesce indicator.
User response: None. DFHZC2444E date time applid termid tranid CICS bracket
Module: DFHZASX state error. sense ((instance) Module name:
{DFHZRVS | DFHZSDS})
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Explanation: A CICS application program violated bracket
instance, {1=DFHZASX} protocol. It is possible that the application program issued an
Destination: CSNE I/O request following a write (last) request.

DFHZC2441I date time applid termid tranid CICS released by topic “DFHZCxxxx messages” on page 356.
node. sense ((instance) Module name: System action: All outstanding send and receive requests are
{DFHZASX}) purged. If a task is attached, it is abnormally terminated with
Explanation: CICS received a release-quiesce indicator from a a transaction dump.
VTAM logical unit that had previously quiesced CICS. User response: Correct the application program.
For the meaning of the sense data, see the explanation on Module: DFHZRVS, DFHZSDS
topic “DFHZCxxxx messages” on page 356. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
System action: Data transmission to the node is resumed by instance, {1=DFHZRVS, 2=DFHZSDS}
CICS. Destination: CSNE
Module: DFHZASX
DFHZC2445E date time applid termid tranid Output area
XMEOUT Parameters: date, time,applid, termid, tranid, sense, exceeded. sense ((instance) Module name:
instance, {1=DFHZASX} {DFHZSDS})
Destination: CSNE Explanation: The TIOA was not large enough to hold all the
output data. The application program either set up the TIOA
DFHZC2442E date time applid termid tranid Exception incorrectly or it overran the TIOA.
response received to a definite response send. For the meaning of the sense data, see the explanation on
sense ((instance) Module name: {DFHZRVX}) topic “DFHZCxxxx messages” on page 356.
Explanation: An exception response was received when a System action: All outstanding send requests are purged. If a
definite response protocol was requested. task is attached, it is abnormally terminated with a transaction
For the meaning of the sense data, see the explanation on dump.
topic “DFHZCxxxx messages” on page 356. User response: Correct the application program to acquire a
System action: CICS issues a second message in conjunction larger TIOA.
with this message that explains the reason for the exception Module: DFHZSDS
response. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
User response: Perform the action specified for the second instance, {1=DFHZSDS, 2=DFHZSDS}
CICS message received. Destination: CSNE
Module: DFHZRVX
instance, {1=DFHZRVX, 2=DFHZRVX}
Destination: CSNE

terminated by issuing a VTAM CLSDST macro, and the node

DFHZC2446E date time applid termid tranid Invalid response
is placed out of service.
to a bid. sense ((instance) Module name:
User response: Correct the application program.
{DFHZRAC | DFHZRVX | DFHZSSX})
Module: DFHZRAC, DFHZRVX
Explanation: An invalid response was received for a bid
request. A normal response was received in response to a bid XMEOUT Parameters: date, time,applid, termid, tranid, sense,
indicator while the transaction was in bracket state. The instance, {1=DFHZRVX, 2=DFHZRAC, 3=DFHZRAC}
controller application program is in error. Destination: CSNE
topic “DFHZCxxxx messages” on page 356. DFHZC2449E date time applid termid tranid Bracket Error.
System action: All outstanding requests are purged. If a task sense ((instance) Module name: {DFHZRAC |
is attached, it is abnormally terminated with a transaction DFHZRVX})
dump. Communication with the node is terminated by issuing Explanation: The application program either sent a
a VTAM CLSDST macro instruction, and the node is placed begin-bracket indicator while the transaction was in bracket
out of service. state, or sent an end-bracket indicator.
User response: Correct the controller application program to
return an exception response to a bid indicator when in the For the meaning of the sense data, see the explanation on
bracket state, followed by a ready-to-receive indicator when topic “DFHZCxxxx messages” on page 356.
ready to honor the bid. System action: If a task is attached, it is abnormally
Module: DFHZRAC, DFHZRVX, DFHZSSX terminated with a transaction dump. Communication with the
node is terminated by issuing the VTAM CLSDST macro, and
XMEOUT Parameters: date, time,applid, termid, tranid, sense, the node is placed out of service.
instance, {1=DFHZRVX, 2=DFHZSSX, 3=DFHZRAC} User response: Correct the application program.
Destination: CSNE Module: DFHZRAC, DFHZRVX

DFHZC2447E date time applid termid tranid A severe error has instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRAC,
occurred as a result of a previous failure. 4=DFHZRAC}
sense ((instance) Module name: {DFHZACT | Destination: CSNE
DFHZFRE | DFHZGET | DFHZOPN |
DFHZRAC | DFHZRLP | DFHZRVS |
DFHZSDA}) DFHZC2450E date time applid termid tranid Bid issued but
Explanation: A domain call failed and the response could not ATI cancelled. sense ((instance) Module name:
be handled by module modname because of a previous failure. {DFHZRAC | DFHZRVX | DFHZSSX})
The domain concerned should have issued a message to the Explanation: An automatic task initiation (ATI) request was
console which gives further information about the failure. issued without an ATI pending for that terminal.
System action: All outstanding send and receive requests for System action: CICS will satisfy the BB pending condition by
terminal termid are purged. If a task is attached, it is sending a standalone BB-EB.
abnormally terminated with a transaction dump. Terminal User response: If ATI is time-initiated, increase the timer
termid is placed out of service and the TCTTE is logged to the value.
CSNE destination. Module: DFHZRAC, DFHZRVX, DFHZSSX
User response: Refer to the message issued by the domain XMEOUT Parameters: date, time,applid, termid, tranid, sense,
that is in error. It indicates the source of the original error. instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX,
Module: DFHZRAC, DFHZRVS, DFHZSDA, DFHZOPN, 4=DFHZSSX, 5=DFHZSSX, 6=DFHZSSX, 7=DFHZRAC,
DFHZFRE, DFHZRLP, DFHZACT, DFHZGET 8=DFHZRAC, 9=DFHZRAC}
instance, {1=DFHZOPN, 2=DFHZRVS, 3=DFHZSDA,
4=DFHZRAC, 5=DFHZRAC, 6=DFHZOPN, 7=DFHZOPN,
DFHZC2451E date time applid termid tranid Outstanding
8=DFHZFRE, 9=DFHZRLP, 10=DFHZACT, 11=DFHZGET,
request when clear was issued. sense
12=DFHZGET, 13=DFHZOPN}
((instance) Module name: {DFHZSYX})
Destination: CSNE
Explanation: A request was outstanding when clear was
issued. A receive-specific request was pending when a clear
DFHZC2448E date time applid termid tranid Invalid response indicator was issued. A clear indicator is sent when any of the
requested. sense ((instance) Module name: following occurs:
{DFHZRAC | DFHZRVX}) v The logical unit is lost (LOSTERM).
Explanation: An invalid response was requested. An v CICS issues a VTAM CLSDST macro.
application program transmitted data to CICS without v CICS issues the clear during message resynchronization.
requesting a response from CICS.
System action: All outstanding requests are purged. If a task
System action: All outstanding receive requests are purged.
is attached, it is abnormally terminated with a transaction
If a task is attached, it is abnormally terminated with a
dump.
transaction dump. Communication with the node is

Module: DFHZSYX XMEOUT Parameters: date, time,applid, termid, tranid, sense,

Destination: CSNE
DFHZC2455E date time applid termid tranid In CA mode -
Task attached. sense ((instance) Module name:
DFHZC2452E date time applid termid tranid Invalid command
{DFHZATT})
received. sense ((instance) Module name:
Explanation: An attempt to attach a task to a logical unit
{DFHZSCX})
(LU) was made, despite the task being in continue-any (CA)
Explanation: CICS received an invalid command (VTAM
mode. However, terminal termid already had a task attached to
indicator). The CICS session-control input exit-routine (SCIP)
it.
encountered an indicator other than request-recovery. This
routine should be scheduled only when a request-recovery For the meaning of the sense data, see the explanation on
indicator is received from the controller application program. topic “DFHZCxxxx messages” on page 356.
System action: The task that is already attached to terminal
termid is abnormally terminated with a transaction dump.
System action: If a task is attached, it is abnormally Message DFHME0116 is normally produced containing the
terminated with a transaction dump. The session is terminated symptom string for this problem. Communication with the
and the node is placed out of service. node is terminated by issuing the VTAM CLSDST macro. CICS
User response: Check the VTAM RPL for obvious errors. Use then reestablishes communication with the node by issuing the
the dump to help determine the source of the problem. SIMLOGON macro.
Module: DFHZSCX User response: Use the symptom string, and if necessary the
dump, to determine the source of the error. Try to determine
why there was an attempt to attach a task to terminal termid
instance, {1=DFHZSCX}
while it already had a task attached to it.
Destination: CSNE
Module: DFHZATT

DFHZC2453E date time applid termid tranid Request recovery instance, {1=DFHZATT}
received. sense ((instance) Module name: Destination: CSNE
{DFHZSCX})
Explanation: A request for recovery was received. The
secondary logical unit requested message resynchronization by DFHZC2456E date time applid termid tranid Exception
sending a request-recovery indicator, but a message sequence response received to a command. sense
number is inconsistent with the sequence number maintained ((instance) Module name: {DFHZRAC |
by the 3601 application program. DFHZSYX})
Explanation: CICS received an exception response to a
For the meaning of the sense data, see the explanation on command (VTAM indicator) that it sent to a logical unit.
System action: All outstanding send and receive requests are For the meaning of the sense data, see the explanation on
purged. If a task is attached, it is abnormally terminated with topic “DFHZCxxxx messages” on page 356.
a transaction dump. Message resynchronization is then System action: In conjunction with this message, CICS issues
initiated by CICS. a second message that explains the reason for the exception
User response: None. response.
Module: DFHZSCX User response: Perform the action specified in the second
CICS message received.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Module: DFHZSYX, DFHZSSX
instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX,
4=DFHZRAC}
DFHZC2454E date time applid termid tranid Exception in Destination: CSNE
chain. sense ((instance) Module name:
{DFHZSYX})
Explanation: An exception response was returned on a DFHZC2457E date time applid termid tranid Multiple Errors
POST=RESP chain-data send. CICS normally does not send Encountered. sense ((instance) Module name:
chained data using POST=RESP. {DFHZEMW | DFHZRAC | DFHZSYX})
Explanation: A node encountered consecutive errors. That is,
For the meaning of the sense data, see the explanation on the node abnormal condition program, NACP, encountered a
topic “DFHZCxxxx messages” on page 356. second error while processing the first error.
purged. If a task is attached, it is abnormally terminated with For the meaning of the sense data, see the explanation on
a transaction dump. topic “DFHZCxxxx messages” on page 356.
Message DFHME0116 is normally produced containing the terminated with a transaction dump. Communication with the
symptom string for this problem. node is terminated by issuing a VTAM CLSDST macro. The
User response: Use the symptom string, and if necessary the first error is accompanied by an error message.
transaction dump, to determine the source of the error. User response: Use the dump to determine the source of the
Module: DFHZSYX

errors. Refer to the error message produced by the first XMEOUT Parameters: date, time,applid, termid, tranid, sense,
problem and to any VTAM messages that may have been instance, {1=DFHZNAC}
issued. Destination: CSNE
Module: DFHZRAC, DFHZSYX, DFHZEMW
XMEOUT Parameters: date, time,applid, termid, tranid, sense, DFHZC2461E date time applid termid tranid Intervention
instance, {1=DFHZEMW, 2=DFHZSYX, 3=DFHZSYX, required. sense ((instance) Module name:
4=DFHZRAC, 5=DFHZRAC} {DFHZNAC})
Destination: CSNE Explanation: Operator action is requested for a physical
component of terminal termid before a request can be
completed.
DFHZC2458E date time applid termid tranid Exception
response received to an exception response For the meaning of the sense data, see the explanation on
send. sense ((instance) Module name: topic “DFHZCxxxx messages” on page 356.
{DFHZRAC | DFHZRVX}) System action: The request is retried, unless the device is one
Explanation: CICS received an exception response to a send that sends a logical unit status message after intervention is
for which an exception response was requested. required. In the latter case, the relevant system action is taken.
User response: Correct the problem with the device.
Module: DFHZNAC
System action: In conjunction with this message, CICS issues XMEOUT Parameters: date, time,applid, termid, tranid, sense,
a second message that explains the reason for the exception instance, {1=DFHZNAC}
response. Destination: CSNE
User response: Perform the action specified in the second
CICS message received.
Module: DFHZRAC, DFHZRVX DFHZC2462E date time applid termid tranid Bracket Error.
sense ((instance) Module name: {DFHZNAC})
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Explanation: The secondary logical unit and CICS both sent a
instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX, begin-bracket indicator concurrently.
4=DFHZRVX, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC,
8=DFHZRAC, 9=DFHZRAC, 10=DFHZRAC, 11=DFHZRAC, For the meaning of the sense data, see the explanation on
12=DFHZRAC} topic “DFHZCxxxx messages” on page 356.
Destination: CSNE System action: All outstanding send and receive requests are
a transaction dump. Communication with the node is
DFHZC2459E date time applid termid tranid No TIOA terminated by issuing the VTAM CLSDST macro.
available for send. sense ((instance) Module User response: Correct the controller application program so
name: {DFHZSDS}) that it cannot send a begin-bracket indicator.
Explanation: TCTTEDA was not loaded before issuing a Module: DFHZNAC
DFHTC TYPE=WRITE, or it was inadvertently cleared.
For the meaning of the sense data, see the explanation on instance, {1=DFHZNAC}
terminated with a transaction dump. The send is purged.
User response: Ensure that TCTTEDA is loaded with the DFHZC2463E date time applid termid tranid Node nodeid
TIOA address before issuing the write. resource pending deletion, connection
Module: DFHZSDS request rejected. sense ((instance) Module
name: {DFHZLGX | DFHZSCX})
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Explanation: Node nodeid tried to connect to CICS. CICS
instance, {1=DFHZSDS, 2=DFHZSDS} rejected the request because it was deleting the terminal
Destination: CSNE definition for termid.

DFHZC2460E date time applid termid tranid Sense receive not topic “DFHZCxxxx messages” on page 356.
supported. sense ((instance) Module name: System action: CICS continues with the resource alteration,
{DFHZNAC}) or for instance 3 of the message, the autoinstall delete
Explanation: Sense codes not supported by CICS were transaction, CATD, is restarted.
received from the logical unit. User response: When the resource alteration is complete,
retry the connection or logon request.
Module: DFHZSCX, DFHZLGX
System action: All outstanding send and receive requests are XMEOUT Parameters: date, time,applid, termid, tranid, nodeid,
purged. If a task is attached, it is abnormally terminated with sense, instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZLGX,
a transaction dump. Communication with the node is 4=DFHZLGX}
terminated by issuing a VTAM CLSDST macro, and the node Destination: CSNE
User response: The user's node error program (DFHZNEP)
can process the sense codes.
Module: DFHZNAC

tried to use it before the process was complete.

DFHZC2464E date time applid termid tranid Terminate chain.
sense ((instance) Module name: {DFHZNAC}) For the meaning of the sense data, see the explanation on
Explanation: The secondary logical unit asked CICS to topic “DFHZCxxxx messages” on page 356.
terminate transmission of further data in the current chain. System action: All outstanding send and receive requests are
a transaction dump. If the failing request is not a CLSDST, the
node is placed out of service. If the losterm exit was driven
with return code X'0C', X'10', or X'14', CICS issues a CLSDST
to VTAM and reset action flag 23, "keep node out of service".
a transaction dump. A cancel indicator is issued to the logical
User response: Ensure that application programs running
unit permitting discard of the data in the current chain.
concurrently do not alter the TCTECID field in the TCTTE.
User response: Use the supplied dump to determine why the
Also check that the session is still active; that is, that the
logical unit requested the chain to be discarded.
system being communicated with is still functioning.
Module: DFHZNAC
Module: DFHZLEX
instance, {1=DFHZNAC}
instance, {1=DFHZLEX}
Destination: CSNE
Destination: CSNE
DFHZC2465E date time applid termid tranid Insufficient

DFHZC2468E date time applid termid tranid Name netname
resources. sense ((instance) Module name:
unknown or vary activate required. sense
{DFHZNAC})
((instance) Module name: {DFHZLEX})
Explanation: The subsystem controller application program
Explanation: Either the node has not been activated by VARY
has insufficient resources to handle the request. For instance,
ACTIVATE or CICS issued a VTAM request containing an
in the case of 3601, the 3601 diskette might be full, or the data
invalid symbolic node name where:
segment in the 3601 might not be large enough to handle the
v The name may have been altered in the node initialization
data set.
block (NIB)
For the meaning of the sense data, see the explanation on v The name was specified during VTAM definition and does
topic “DFHZCxxxx messages” on page 356. not agree with the name in the TCT.
System action: The subsystem is temporarily suspended.
User response: Determine why the controller application For the meaning of the sense data, see the explanation on
program encountered this condition. topic “DFHZCxxxx messages” on page 356.
Module: DFHZNAC System action: All outstanding send and receive requests are
a transaction dump. The node is placed out of service.
User response: Either issue VARY ACTIVATE for the node, or
Destination: CSNE
ensure that application programs running concurrently do not
alter the NIB name. Names specified during VTAM definition
DFHZC2466E date time applid termid tranid Function not must agree with those in the TCT.
executable. sense ((instance) Module name: Module: DFHZLEX
{DFHZNAC})
Explanation: The controller application program cannot
sense, instance, {1=DFHZLEX}
transmit a message to terminal termid. Either a data check
Destination: CSNE
occurred, or the node is not available.
DFHZC2469E date time applid termid tranid Exception
response received. sense ((instance) Module
name: {DFHZSYX})
Explanation: An exception response (negative response) was
a transaction dump. Terminal status remains unchanged.
sent by the secondary logical unit.
User response: Use the supplied dump to determine why the
application program could not execute the request. For the meaning of the sense data, see the explanation on
Module: DFHZNAC topic “DFHZCxxxx messages” on page 356.
System action: For a non-3270 device, an exception response
is returned to the node, along with the sense codes supplied
by VTAM in the request parameter list (RPL) for the inbound
Destination: CSNE
message. For a 3270 device, the exception request contains
3270 sense/status.
DFHZC2467E date time applid termid tranid Invalid User response: Analyze the sense codes in DFHZNEP.
communications ID (CID) detected. sense Module: DFHZSYX
((instance) Module name: {DFHZLEX})
Explanation: CICS issued a VTAM request containing a
instance, {1=DFHZSYX, 2=DFHZSYX}
communications identifier (CID) which VTAM did not
Destination: CSNE
recognize. This may be due to the TCTECID field having been
altered. Alternatively, it may mean that the session is in the
process of being closed down by VTAM and that CICS has

instance, {1=DFHZRAC, 2=DFHZRAC}

DFHZC2470E date time applid termid tranid Task active at
Destination: CSNE
Shutdown. sense ((instance) Module name:
{DFHZASX})
Explanation: One of the following has occurred: DFHZC2473E date time applid termid tranid Outbound
v A request shutdown indicator was received from the chaining not supported. sense ((instance)
controller application program on behalf of the node while Module name: {DFHZSDS})
a task was still attached. Explanation: The application program has attempted to send
v During VTAM shutdown, a shutdown complete indicator more data than the generated maximum allowable length.
was received from the controller application program on
behalf of the node while a task was still attached For the meaning of the sense data, see the explanation on
v During VTAM shutdown, a task was still attached to a topic “DFHZCxxxx messages” on page 356.
VTAM 3270 (which cannot send request shutdown or System action: All send requests are purged. If a task is
shutdown complete). attached, it is abnormally terminated with a transaction dump.
User response: Correct the application program so that it is
sensitive to the maximum allowable length of data that can be
sent to the terminal (such as checking the device type),
providing the terminal does not support outbound chaining of
System action: In the first two cases, CICS honors the
data (such as a pipeline session).
command. In all cases, all outstanding send and receive
requests are purged, and if a task is attached, it is abnormally Note: The generated maximum allowable length is specified in
terminated with a transaction dump. Communication with the the TCTTE.
node is terminated by issuing a VTAM CLSDST macro. Module: DFHZSDS
Module: DFHZASX XMEOUT Parameters: date, time,applid, termid, tranid, sense,
instance, {1=DFHZSDS, 2=DFHZSDS}
instance, {1=DFHZASX}
Destination: CSNE
DFHZC2475E date time applid termid tranid Function
cancelled by LU device. sense ((instance)
DFHZC2471E date time applid termid tranid FMH length error. Module name: {DFHZNAC})
sense ((instance) Module name: {DFHZATT | Explanation: The logical unit (LU) has terminated all
DFHZRAC}) processing connected with one of its components.
Explanation: The function management header (FMH) length
was greater than that of the data received from the logical For the meaning of the sense data, see the explanation on
unit. topic “DFHZCxxxx messages” on page 356.
System action: All send and receive requests are purged. If a
For the meaning of the sense data, see the explanation on task is attached, it is abnormally terminated with a transaction
topic “DFHZCxxxx messages” on page 356. dump.
System action: All data received is purged. If a task is User response: Correct the problem with the LU component
attached, it is abnormally terminated with a transaction dump. and bring it back online. Possible causes of the problem
User response: Correct the application program in the logical include the following:
unit. v Power for the device is switched off
v A line that is down
Note: The first 16 bytes of the I/O area in error are put to the v A hardware problem
CSNE log data set to aid in error determination. v In the case of an LU6 link, the connected transaction, for
Module: DFHZRAC, DFHZATT example, CSMI, has terminated abnormally.
Module: DFHZNAC
instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT, XMEOUT Parameters: date, time,applid, termid, tranid, sense,
4=DFHZATT, 5=DFHZATT, 6=DFHZRAC} instance, {1=DFHZNAC}
Destination: CSNE Destination: CSNE
DFHZC2472E date time applid termid tranid Unable to retrieve DFHZC2476E date time applid termid tranid Resource
overlength data. sense ((instance) Module unavailable. sense ((instance) Module name:
name: {DFHZRAC}) {DFHZNAC})
Explanation: The receive request for the remainder of data in Explanation: A component of the logical unit (LU) is no
excess of the input area for the receive-any module was not longer available.
accepted by VTAM.
topic “DFHZCxxxx messages” on page 356. System action: All send and receive requests are purged. If a
System action: All associated data is purged. task is attached, it is abnormally terminated with a transaction
User response: A subsequent message follows in the log, dump.
indicating reasons for the request failing. Refer to this message User response: Correct the problem with the LU component
for further information and guidance. and bring it back online. Possible causes of the problem
Module: DFHZRAC include the following.
v Power for the device is switched off.

v A line that is down. Module: DFHZNAC

v A hardware problem.
Module: DFHZNAC
Destination: CSNE
DFHZC2480E date time applid termid tranid Retry requested.
DFHZC2477E date time applid termid tranid Chaining not Explanation: The logical unit (LU) has indicated, via sense
supported. sense ((instance) Module name: codes contained in an exception response or an LU status
{DFHZNAC}) message, that it requires the data to be retransmitted.
Explanation: The logical unit (LU) does not support chaining
of data from the host. For the meaning of the sense data, see the explanation on
For the meaning of the sense data, see the explanation on System action: Retransmission of data will be attempted only
topic “DFHZCxxxx messages” on page 356. in the case of protected tasks (message integrity). If the
System action: All send requests are purged. If a task is exception response containing the retry sense codes is received
attached, it is abnormally terminated with a transaction dump. for an unprotected task while in chain processing, a cancel
User response: Ensure that the maximum amount of data command will be sent to the LU and the task will be resumed.
being transmitted to the LU does not exceed the length If CICS is not in chain processing, the transaction will be
specified in the buffer parameter of the DFHTCT macro resumed.
instruction. User response: If message retransmission is necessary for the
LU, ensure that the retry sense codes are imbedded in the
Note: The buffer parameter value can be increased only to the
exception response. Also ensure that the host transaction is
maximum acceptable limit of the LU.
defined as a protected task (message integrity).
Module: DFHZNAC
Module: DFHZNAC
Destination: CSNE
Destination: CSNE
DFHZC2478E date time applid termid tranid Invalid FMH.

DFHZC2481E date time applid termid tranid RU Error. sense
((instance) Module name: {DFHZNAC})
Explanation: The function management header (FMH)
Explanation: The response unit (RU) received by the logical
transmitted to the logical unit (LU) had no counterpart on the
unit (LU) was either not translatable or had an invalid length.
translate table.
System action: All send and receive requests are purged. If a
System action: All send and receive requests are purged. If
task is attached, it is abnormally terminated with a transaction
the batch data interchange program is not being used, the
dump.
transaction is abnormally terminated with a transaction dump.
User response: Retrying the request a number of times by
The first part of the TIOA, containing the FMH, is written to
use of the node error program (NEP) mechanism may be
the CSNE log.
necessary. This is because this type of error may stem from a
User response: Correct the application program so that the
bad communication line. If this fails, check for possible invalid
LU has a counterpart on the translate table.
or inappropriate terminal specifications at terminal control
Module: DFHZNAC
table (TCT) generation time.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Module: DFHZNAC
Destination: CSNE
Destination: CSNE
DFHZC2479E date time applid termid tranid Function not
supported. sense ((instance) Module name: DFHZC2482E date time applid termid tranid Pipeline session
{DFHZNAC}) bracket error. sense ((instance) Module name:
Explanation: The response unit (RU) received by the logical {DFHZATT})
unit (LU) contains a request that this device does not support. Explanation: Terminal termid was defined in the terminal
For the meaning of the sense data, see the explanation on control table (TCT) as running in pipeline session mode.
topic “DFHZCxxxx messages” on page 356. However, the BRACKET operand in that definition was either
System action: All send and receive requests are purged. If a omitted or was specified as BRACKET=YES. Bracket protocol
task is attached, it is abnormally terminated with a transaction is not enforced on a pipeline session terminal.
dump. For the meaning of the sense data, see the explanation on
User response: Ensure that the terminal control table (TCT) topic “DFHZCxxxx messages” on page 356.
generation specifications for the device are valid as well as System action: All send and receive requests are purged and
able to accommodate the application requests. (For example, a the session is terminated. If a task is attached, it is abnormally
read-only device being defined as transceiver, yet having a bid terminated with a transaction dump.
sent to it.)

User response: Correct the TCT entry by inserting the

DFHZC2486E date time applid termid tranid Cancel received in
BRACKET=NO operand.
'CA'-mode. sense ((instance) Module name:
Module: DFHZNAC
{DFHZRAC})
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Explanation: A CANCEL indicator was received while no
instance, {1=DFHZATT} task was active.
Destination: CSNE
DFHZC2483E date time applid termid tranid Receiver in System action: Processing continues.
transmit mode. sense ((instance) Module name: User response: None.
{DFHZNAC}) Module: DFHZRAC
Explanation: Normal data flow has been interrupted.
For the meaning of the sense data, see the explanation on instance, {1=DFHZRAC}
User response: Retry the WRITE.
DFHZC2487E date time applid termid tranid nodeid Session
Module: DFHZNAC
connection failed. Node unavailability return
XMEOUT Parameters: date, time,applid, termid, tranid, sense, code returncode. sense ((instance) Module name:
instance, {1=DFHZNAC} {DFHZLGX | DFHZSCX})
Destination: CSNE Explanation: A connection request was rejected. CICS is
temporarily unable to carry out the connection request. The
TCTTE for node nodeid indicated that the session could not be
DFHZC2484E date time applid termid tranid Component not established. returncode gives the reason, as follows:
available. sense ((instance) Module name: 1. The CLSDST macro has been scheduled for this node
{DFHZNAC}) 2. The node is in an abnormal condition
Explanation: An application request could not be satisfied 3. The node has an error condition raised against it
because the required component was not available. 4. The node is already in use
For the meaning of the sense data, see the explanation on 5. CICS is terminating
topic “DFHZCxxxx messages” on page 356. 6. VTAM is terminating.
terminated with a transaction dump. All outstanding send and For the meaning of the sense data, see the explanation on
receive requests are purged. topic “DFHZCxxxx messages” on page 356.
System action: The connection request is rejected.
Message DFHME0116 is normally produced containing the User response: Retry the connection request when the node
symptom string for this problem. becomes available. See the CICS Customization Guide for more
User response: Check the terminal environment, or use the information on abnormal node conditions.
symptom string, and if necessary the dump, to determine the Module: DFHZLGX, DFHZSCX
cause of the error.
Module: DFHZNAC XMEOUT Parameters: date, time,applid, termid, tranid, nodeid,
returncode, sense, instance, {1=DFHZSCX, 2=DFHZSCX,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, 3=DFHZSCX,4=DFHZSCX, 5=DFHZSCX,
instance, {1=DFHZNAC} 6=DFHZSCX,7=DFHZSCX, 8=DFHZSCX,
Destination: CSNE 9=DFHZLGX,10=DFHZLGX, 11=DFHZLGX,
12=DFHZLGX,13=DFHZLGX, 14=DFHZLGX, 15=DFHZLGX}
Destination: CSNE
DFHZC2485E date time applid termid tranid Cancel received in
'CS'-mode. sense ((instance) Module name:
{DFHZRVX}) DFHZC2488E date time applid termid tranid nodeid logon
Explanation: A CANCEL indicator was received while a task request rejected as terminal recovery is in
was active. progress. sense ((instance) Module name:
{DFHZLGX | DFHZSCX})
Explanation: A connection request was rejected because the
CICS terminal recovery program was still executing.
terminated with a transaction dump. All outstanding send and For the meaning of the sense data, see the explanation on
receive requests purged. topic “DFHZCxxxx messages” on page 356.
User response: None. System action: The connection request is rejected.
Module: DFHZRVX User response: Retry the connection request. Message
DFHRU2800 is produced when the recovery program has
completed processing.
instance, {1=DFHZRVX}
Module: DFHZLGX, DFHZSCX
Destination: CSNE
sense, instance, {1=DFHZLGX, 2=DFHZSCX}
Destination: CSNE

Module: DFHZNAC
DFHZC2489E date time applid termid tranid 3270 - Invalid
copy request. sense ((instance) Module name: XMEOUT Parameters: date, time,applid, termid, tranid, sense,
{DFHZARQ}) instance, {1=DFHZNAC}
Explanation: The terminal control table terminal entry Destination: CSNE
(TCTTE) of the device from which the information is to be
copied (“from” device) did not specify the COPY feature.
Alternatively, the “from” device: DFHZC2493E date time applid termid tranid Intervention
v Is not defined in the TCT, or required on 3270 device. sense ((instance)
v Is not a 3270, or Module name: {DFHZNAC})
v Is not connected to CICS via VTAM. Explanation: This message occurs when an INTERVENTION
REQUIRED condition arises on the 3270 Information Display
System.
topic “DFHZCxxxx messages” on page 356. For the meaning of the sense data, see the explanation on
System action: If a task is attached, it is abnormally topic “DFHZCxxxx messages” on page 356.
terminated with a transaction dump. System action: No action is performed.
User response: Ensure that the application program is aware User response: Correct the intervention condition.
of the device configuration. Furthermore, ensure that the Module: DFHZNAC
“from” device is defined in the TCT as a 3270 device AND is
connected to CICS. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Module: DFHZARQ instance, {1=DFHZNAC}
Destination: CSNE
instance, {1=DFHZARQ, 2=DFHZARQ, 3=DFHZARQ}
Destination: CSNE DFHZC2494E date time applid termid tranid Error status sense
received from 3270. ((instance) Module name:
{DFHZNAC})
DFHZC2490E date time applid termid tranid Request for Explanation: An error status message sense was received
TOLTEP. sense ((instance) Module name: from a 3270 Information Display System. An INTERVENTION
{DFHZSYX}) REQUIRED condition causes an "intervention required"
Explanation: On a request for TOLTEP, a receive request message to be output instead of this message.
completes in error. System action: If a task is attached, it is abnormally
For the meaning of the sense data, see the explanation on terminated with a transaction dump. If bad data, sent by basic
topic “DFHZCxxxx messages” on page 356. mapping support (BMS), causes an operation check, the bad
System action: If a transaction is currently attached, it is data is purged.
abnormally terminated. The terminal is disconnected from User response: Analyze the error status codes to determine
CICS by a VTAM CLSDST macro, and is queued for logon to the proper course of action required to correct the unit error or
CICS when TOLTEP has finished. program error.
User response: None. For non-SNA 3270 devices, the sense code is 0000 xxxx, where
Module: DFHZSYX xxxx is sense data returned by the control unit to which the
XMEOUT Parameters: date, time,applid, termid, tranid, sense, 3270 device is attached. Datastream errors are rejected with an
instance, {1=DFHZSYX} Operation Check, and commands with a Command Reject.
Destination: CSNE Details of error status codes are given in the IBM 3270
Information Display System 3274 Control Unit Description and
Programmer's Guide.
DFHZC2492E date time applid termid tranid Intervention Module: DFHZNAC
required on 3270 printer. sense ((instance)
Module name: {DFHZNAC})
Explanation: This message is sent to the CSNE message log
Destination: CSNE
when an INTERVENTION REQUIRED condition is detected
on a 3270 printer. This condition could occur for any of the
reasons listed below. DFHZC2495E date time applid termid tranid Printer
v A transaction has requested the use of a printer that does Outserv/int reqd/ineligible. Req queued. sense
not exist. ((instance) Module name: {DFHZNAC})
v The printer adapter feature is not present. Explanation: DFHZNAC has performed an interval control
v There is no paper in the printer. PUT to a 3270 printer on behalf of a DFHZC2497 "unavailable
v The printer cover is open. printer" condition. The printer is:
v The printer is offline. v Out of service,
v Has an intervention situation, or
For the meaning of the sense data, see the explanation on v Does not have a RECEIVE or TRANSCEIVE status.
System action: No action is performed except printing of the For the meaning of the sense data, see the explanation on
RPL and the TCTTE. topic “DFHZCxxxx messages” on page 356.
User response: Check that the terminal control table (TCT) is System action: Other processing continues.
properly defined and that the transaction requests proper User response: Determine why the printer is unavailable. If
printer operations. If this is correct, check that the printer itself the terminal is out of service, put it back into service. If the
is in proper working order. terminal has an intervention situation, determine what this

situation is and correct it. If the terminal does not have a For the meaning of the sense data, see the explanation on
RECEIVE or TRANSCEIVE status, place it into RECEIVE or topic “DFHZCxxxx messages” on page 356.
TRANSCEIVE status. System action: Processing continues.
Module: DFHZNAC User response: Check that transaction CSPP is an installed
transaction definition and that you have sufficient temporary
XMEOUT Parameters: date, time,applid, termid, tranid, sense, storage to accommodate the data to be printed.
instance, {1=DFHZNAC} Module: DFHZARQ
Destination: CSNE
instance, {1=DFHZARQ}
DFHZC2496E date time applid termid tranid IC put to printer Destination: CSNE
failed { | IOERROR | TRNIDER |
TRMIDER | INVREQ}. sense ((instance)
Module name: {DFHZNAC}) DFHZC2499 date time applid The following message was
Explanation: DFHZNAC has attempted to perform a DFHIC destined for a read only terminal. The text is
TYPE=PUT macro as the result of a DFHZC2497 "unavailable 'msgtext'
printer" condition and has failed. This message is written to Explanation: The user has entered an invalid entry, the entry
the CSNE log. is rejected, and the request is backed out.
System action: Terminal Control backs out the request and
For the meaning of the sense data, see the explanation on issues this message with the error information contained in
topic “DFHZCxxxx messages” on page 356. msgtext.
System action: DFHZNEP is recalled by DFHZNAC to allow User response: Read the error information that is contained
for further processing. in msgtext and reenter the request.
User response: Ensure that:
v The interval control program (ICP) is capable of handling XMEOUT Parameters: date, time,applid, msgtext
the request that DFHZNAC is issuing for the IOERROR and
INVREQ errors
v CSPP is an installed transaction definition for the TRNIDER DFHZC3202E date time applid Transaction CCIN - VTAM
error netname netname. The value codepage in the
v DFHZNEP is passing DFHZNAC as a valid terminal codepage parameter is not supported.
address for the TRMIDER error. Explanation: A CCIN transaction has been run from a CICS
Module: DFHZNAC client. The codepage which the CICS client has requested is
not supported.
XMEOUT Parameters: date, time,applid, termid, tranid, {1= , 2=
IOERROR, 3= TRNIDER, 4=TRMIDER, 5= INVREQ}, sense, netname is the VTAM netname of the CICS client.
instance, {1=DFHZNAC} System action: CICS cannot perform the translations required
Destination: CSNE to support the CICS client with the requested character set
and codepage. CICS continues but uses a default codepage
instead of the supplied one. For details of the default
DFHZC2497E date time applid termid tranid Unavailable codepage, see the CICS Intercommunication Guide manual.
printer. sense ((instance) Module name:
{DFHZARQ}) The request to install the CICS client continues, but uses the
Explanation: A print function was requested on a 3270 default codepage. A response code of EXCEPTION and a
display device. Neither the PRINTTO or the ALTPRT printer reason code of INVALIDCODEPAGE is sent to the client.
was available to receive the information. User response: See the CICS Family: Communicating from CICS
on System/390 manual for a list of the client codepage values
For the meaning of the sense data, see the explanation on which are supported. It may be necessary to reconfigure the
topic “DFHZCxxxx messages” on page 356. client locale.
System action: If no NEP action is specified, the print request Module: DFHZCN2
is halted.
User response: A possible solution is to route the data XMEOUT Parameters: date, time,applid, netname, codepage
available at TCTTEDA in the provided terminal entry to a Destination: CSCC
transient data queue that causes automatic task initiation later
to a printer. This would be done in DFHZNEP. For more DFHZC3203E date time applid Transaction CCIN - VTAM
information, see the CICS Customization Guide. netname netname. The capabilities parameter
Module: DFHZARQ is not valid.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Explanation: A CCIN transaction has been run from a CICS
instance, {1=DFHZARQ} client. The capabilities which have been received are not valid.
Destination: CSNE The CICS client has specified that it supports features which
no CICS client is supposed to support. The CICS client is
violating the CICS client communications architecture.
DFHZC2498E date time applid termid tranid IC put to printer
failed. sense ((instance) Module name: netname is the VTAM netname of the CICS client.
{DFHZARQ}) System action: Exception trace point AP301A is written.
Explanation: A 3270 print request has failed because The request to install the CICS client is rejected. A response
transaction CSPP could not be initiated. Either transaction code of DISASTER and a reason code of INVALIDREQUEST is
CSPP is not an installed transaction definition, or the message sent to the client.
to be printed cannot be written to temporary storage. User response: You need further assistance from IBM to

Determination Guide for guidance on how to proceed. unsupported combination of CICS client and virtual
Module: DFHZCN2 terminal codepage.
A response code of ERROR and a reason code of
XMEOUT Parameters: date, time,applid, netname INSTALLCANCELLED is sent to the client. The
Destination: CSCC virtual terminal is NOT installed.
unsupported CICS client codepage
DFHZC3204E date time applid Transaction CCIN - VTAM The request to install the virtual terminal continues
netname netname. The codepage parameter and the invalid codepage is replaced by a default as
has not been specified. specified in the CICS Intercommunication Guide
Explanation: A CCIN transaction has been run from a CICS manual.
client. One of the parameters which must be supplied is the A response code of EXCEPTION and a reason code
codepage which the CICS client intends to use. This parameter of INVALIDCODEPAGE is sent to the client.
is missing. unsupported virtual terminal codepage
netname is the VTAM netname of the CICS client. A response code of ERROR and a reason code of
System action: Exception trace point AP301B is written. INSTALLCANCELLED is sent to the client. The
virtual terminal is NOT installed.
The request to install the CICS client is rejected. A response User response: See the CICS Family: Communicating from CICS
code of DISASTER and a reason code of INVALIDREQUEST is on System/390 manual and check the list of the client codepage
sent to the client. values then reconfigure the workstation locale or correct the
User response: You need further assistance from IBM to virtual terminal TYPETERM definition.
Determination Guide for guidance on how to proceed. The exception trace point AP3035 contains the CICS client
Module: DFHZCN1 codepage and the virtual terminal CGCSGID values.
Module: DFHZCT1
Destination: CSCC XMEOUT Parameters: date, time,applid, termid, netname,
{4=combination of client and virtual terminal codepage.,5=client
codepage., 6=virtual terminal codepage.}
DFHZC3205E date time applid Transaction CTIN - virtual Destination: CSCC
terminal termid VTAM netname netname.
CICS cannot support the {combination of
client and virtual terminal codepage. | client DFHZC3206E date time applid Transaction CTIN - virtual
codepage. | virtual terminal codepage.} terminal termid VTAM netname netname. The
Explanation: A CTIN install request has been received from a client's terminal install limit has been
CICS client as a result of a CICS_EpiAddTerminal function or exceeded.
terminal emulator operation. Explanation: A CTIN install request has been received from a
CICS client as a result of a CICS_EpiAddTerminal function or
CICS was checking the codepage specified by the CICS client terminal emulator operation. However the CICS client whose
and the codepage specified by the virtual terminal. However VTAM netname is netname already has 512 virtual terminals.
one of the following occurred:
unsupported combination of CICS client and virtual termid is the name that would have been given to the new
terminal codepage virtual terminal. If the CICS client did not supply the name it
Indicates that the two codepages above are known is blank.
about but CICS does not support data conversion System action: The request to install the virtual terminal is
between the CICS client codepage and the virtual rejected. A response code of DISASTER and a reason code of
terminal codepage. INVALIDREQUEST is sent to the client.
unsupported CICS client codepage User response: Check why the CICS client has sent so many
Indicates that CICS is unable to support the CTIN installs
codepage supplied by the CICS client in the CCIN To correct the problem the CICS client must send a CTIN
or CTIN transaction. uninstall for each virtual terminal that needs to be deleted.
unsupported virtual terminal codepage Module: DFHZCT1
Indicates that the CGCSGID parameter defining the
virtual terminal codepage is not supported for CICS XMEOUT Parameters: date, time,applid, termid, netname
data conversion. If the virtual terminal was Destination: CSCC
autoinstalled, CGCSGID was specified in the
autoinstall model requested by the CICS client. If the
DFHZC3207E date time applid Transaction CTIN - VTAM
virtual terminal was defined, CGCSGID was defined
netname netname. The request has failed
in the TYPETERM named by the virtual terminal
because CCIN has not been run.
definition.
Explanation: A CTIN install request has been received from a
CICS cannot perform the translations required to support the terminal emulator operation. However there was no previous
CICS client with the requested codepage. CCIN install request for the CICS client with the VTAM
netname of netname. CCIN must always run before CTIN.
netname is the VTAM netname of the CICS client.
System action: Exception trace point AP3035 is written. This may have been caused by a CICS restart.

System action: The CTIN transaction abnormally terminates

DFHZC3210E date time applid Transaction CTIN - virtual
with abend code AZAI.
User response: The CICS client must carry out CCIN
CICS cannot attach the CITS transaction.
uninstall/install before the next CTIN install.
Module: DFHZCT1
XMEOUT Parameters: date, time,applid, netname terminal emulator operation. As part of the installation process
Destination: CSCC the CITS transaction is called to create a virtual terminal
termid. However CICS was unable to attach the CITS
transaction.
terminal termid VTAM netname netname. netname is the VTAM netname of the CICS client.
Model modelid cannot be found. System action: Exception trace point AP3025 is written.
The request to install the virtual terminal is rejected. A
response code of ERROR and a reason code of
terminal emulator operation. However CICS was unable to
INSTALLCANCELLED is sent to the client.
find the model modelid which was specified in the
User response: Check that the CITS transaction and the
CICS_EpiAddTerminal DEVTYPE parameter or terminal
DFHZATS program are defined correctly as specified in the
emulator Modelid parameter.
DFHSPI IBM supplied group and are installed.
netname is the VTAM netname of the CICS client. Module: DFHZCT1
System action: The request to install the virtual terminal is
XMEOUT Parameters: date, time,applid, termid, netname
rejected. A response code of ERROR and a reason code of
Destination: CSCC
UNKNOWNMODEL is sent to the client.
User response: Either correct the DevType in the
CICS_EpiAddTerminal function or terminal emulator DFHZC3211E date time applid Transaction CTIN - virtual
parameter or install a model of this name using RDO to define terminal termid VTAM netname netname. The
the autoinstall model with the RDO TERMINAL and NetName parameter starts with an invalid
TYPETERM definitions. character.
Module: DFHZCT1 Explanation: A CTIN install request has been received from a
XMEOUT Parameters: date, time,applid, termid, netname, modelid
terminal emulator operation. The NetName parameter termid
Destination: CSCC
starts or ends with a character that conflicts with CICS
standards.
netname netname. CICS cannot supply a
terminal name because all available names
rejected. A response code of DISASTER and a reason code of
are in use.
INVALIDREQUEST is sent to the client.
User response: Change the NetName to start or end with a
different character. It cannot start with *,-,<,>,+,{,} or blank. It
terminal emulator operation. The parameter list did not
cannot end with an -. If the NetName was specified correctly,
supply a NetName indicating that CICS should supply the
check the input to the CTIN transaction.
name. However there are only 46,656 possible names available
Module: DFHZCT1
and they are all currently in use.
Destination: CSCC
INSTALLCANCELLED is sent to the client. DFHZC3212E date time applid Transaction CTIN - virtual
User response: As CICS clients issue CTIN uninstalls for terminal termid VTAM netname netname. The
autoinstalled virtual terminals these termids will be freed. transaction has timed out waiting for CITS to
run.
It is possible that some of the CICS clients were switched off
leaving autoinstalled virtual terminals around. When these are
switched back on again they should issue CCIN install which
terminal emulator operation. As part of the installation process
will free the virtual terminals if they are not in use.
the CITS transaction is called to create virtual terminal termid.
If the SIT VTPREFIX coincides with the first character of the However the CTIN transaction has waited for one minute for
termid allocated to a normal autoinstall terminal by the the CITS transaction to run.
autoinstall URM (default DFHZATDX), there may be some
names reserved because the autoinstall terminal existed when
System action: Exception trace point AP3027 is written.
CTIN install tried to use the same name. Avoid doing this if
possible because the only way to free these names is to restart The request to install the virtual terminal is rejected. A
CICS (COLD or AUTO). response code of ERROR and a reason code of
Module: DFHZCT1 INSTALLCANCELLED is sent to the client.
User response: Investigate why the CITS transaction was
unable to start or was hanging.
Destination: CSCC

You may need to increase MAXTASK or the CITS ALREADYINSTALLED is sent to the client.
TRANCLASS allocation. User response: Investigate why a transaction is still running
Module: DFHZCT1 for the virtual terminal.
Module: DFHZCT1
Destination: CSCC XMEOUT Parameters: date, time,applid, termid, netname
Destination: CSCC

terminal termid VTAM netname netname. DFHZC3216E date time applid Transaction CTIN - virtual
CICS cannot attach the CDTS transaction. terminal termid VTAM netname netname.
Explanation: A CTIN uninstall request has been received CICS cannot find the terminal.
from a CICS client as a result of a CICS_EpiAddTerminal Explanation: A CTIN install request has been received from a
function or terminal emulator operation. As part of the delete CICS client as a result of a CICS_EpiAddTerminal function or
process the CDTS transaction is called to delete virtual terminal emulator operation. TIN specified that a pre defined
terminal termid. However CICS was unable to attach the CDTS virtual terminal termid should be used, but CICS cannot find it
transaction. and no ModelId was provided (DevType) so an autoinstall
was not attempted.
System action: Exception trace point AP3028 is written. The netname is the VTAM netname of the CICS client.
attempt to delete the virtual terminal is rejected. System action: The request to install the virtual terminal is
User response: Check to see if the CDTS transaction and the rejected. A response code of ERROR and a reason code of
DFHZATS program are defined correctly as specified in IBM UNKNOWNTERMINAL is sent to the client.
supplied group DFHSPI and that they are installed. User response: Ensure that there is an installed predefined
Module: DFHZCT1 terminal for termid that has a remote system parameter
(REMOTESYSTem) specifying the name of this CICS clients
XMEOUT Parameters: date, time,applid, termid, netname connection and that the VTAM NETNAMEs match. Then
Destination: CSCC install the definition with the correct parameters.
Module: DFHZCT1
DFHZC3214E date time applid Transaction CTIN - virtual XMEOUT Parameters: date, time,applid, termid, netname
terminal termid VTAM netname netname. The Destination: CSCC
CTIN transaction has timed out waiting for
CDTS to run.
Explanation: A CTIN uninstall request has been received DFHZC3217E date time applid Transaction CTIN - VTAM
from a CICS client as a result of a CICS_EpiDelTerminal netname netname. The specified function is
function or terminal emulator operation. As part of the not valid.
installation process the CDTS transaction is called to delete Explanation: A CTIN request has been received from a CICS
virtual terminal termid. However the CTIN transaction has client with a VTAM netname of netname. However the
waited for the CDTS transaction for one minute and so ends function specified was not INSTALL or UNINSTALL.
with this message. System action: Exception trace point AP3034 is written. The
CTIN transaction abnormally terminates with abend code
netname is the VTAM netname of the CICS client. AZAI.
System action: Exception trace point AP3029 is written. The User response: Determine where the request originated.
CDTS attempt to delete the virtual terminal continues and will Ensure that the input has not been corrupted. You may need
occur when the CDTS transaction starts or is 'unsuspended'. further assistance from IBM. See Part 4 of the CICS Problem
User response: Check to see why the CDTS transaction was Determination Guide for guidance on how to proceed.
unable to start or was hanging. Module: DFHZCT1
You may need to increase MAXTASK or the CDTS XMEOUT Parameters: date, time,applid, netname
TRANCLASS allocation. Destination: CSCC
Module: DFHZCT1

Destination: CSCC
terminal termid VTAM netname netname. A
resource with the same name as the terminal
DFHZC3215E date time applid Transaction CTIN - virtual is already installed.
terminal termid VTAM netname netname. The Explanation: A CTIN install request has been received from a
terminal is in use by another transaction. CICS client as a result of a CICS_EpiAddTerminal function or
Explanation: A CTIN install request has been received from a terminal emulator operation. CTIN specified that a virtual
CICS client as a result of a CICS_EpiAddTerminal function or terminal termid should be autoinstalled. However another
terminal emulator operation. However the virtual terminal resource was installed with the same name after the CTIN
termid is in use, that is the surrogate TCTTE indicates that a transaction had ensured that the name was free.
transaction is still running against this terminal.
netname is the VTAM netname of the CICS client. System action: Exception trace point AP3026 is written.
System action: Exception trace point AP302E is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of
response code of ERROR and a reason code of ALREADYINSTALLED is sent to the client.

User response: Investigate where the duplicate resource came CICS client as a result of a CICS_EpiAddTerminal function or
from. It is possible that the terminal/APPC autoinstall URM terminal emulator operation. CTIN specified that the virtual
created the name dynamically. If NetName was specified in terminal termid should be autoinstalled. However, the name
the CTIN parameters, ensure that the CICS client names do specified is already in use by another CICS resource.
not conflict with existing CICS terminal or connection names.
If NetName was not specified, examine the SIT VTPREFIX
override to check that the URM does not create names starting
with the VTPREFIX character.
ALREADYINSTALLED is sent to the client.
Module: DFHZCT1
User response: Investigate where the duplicate resource came
XMEOUT Parameters: date, time,applid, termid, netname from. It is possible that the terminal/APPC autoinstall URM
Destination: CSCC created the name dynamically.
If NetName was specified on the CTIN install ensure that

DFHZC3219E date time applid Transaction CTIN - virtual NetName does not conflict with other CICS resources.
terminal termid VTAM netname netname. The
If NetName was not specified, examine the SIT VTPREFIX
terminal is already in use.
override to check that the URM does not create names starting
with the VTPREFIX character.
Module: DFHZCT1
terminal emulator operation. CTIN supplied a NetName termid
but CICS found a resource with the same name which is either XMEOUT Parameters: date, time,applid, termid, netname
an existing virtual terminal for this client, an existing virtual Destination: CSCC
terminal for another client or another CICS terminal or
connection resource.
netname is the VTAM netname of the CICS client. terminal termid VTAM netname netname. The
System action: The request to install the virtual terminal is CITS task has terminated abnormally.
rejected. A response code of ERROR and a reason code of Explanation: A CTIN install request has been received from a
ALREADYINSTALLED is sent to the client. CICS client as a result of a CICS_EpiAddTerminal function or
User response: Investigate where the duplicate resource came terminal emulator operation. CICS attempted to autoinstall the
from. It is possible that the terminal/APPC autoinstall URM virtual terminal termid. However, the CITS task which was
created the name dynamically and that the CICS client used a attached to install the virtual terminal, abended.
name that clashes with the URM.
If this ABEND was an AZVE, this is because a resource
It is also possible that a client created the virtual terminal and already exists with that name. However, this only occurs if the
then tried to reuse it without an intervening uninstall, via duplicate resource was added after this CTIN transaction
CCIN or CTIN. started and checked for any duplicate.
Module: DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname System action: Exception trace point AP3030 is written.
Destination: CSCC
DFHZC3220E date time applid Transaction CTIN - virtual INSTALLCANCELLED is sent to the client.
terminal termid VTAM netname netname. The User response: Investigate where the duplicate resource came
terminal has already been installed. from. It is possible that the terminal/APPC autoinstall URM
Explanation: A CTIN install request has been received from a created the name dynamically.
terminal emulator operation. CTIN specified that the virtual If NetName was specified on the CTIN install, ensure that the
terminal termid should be autoinstalled. However, the virtual names do not conflict.
terminal was already installed. If NetName was not specified, examine the SIT VTPREFIX
netname is the VTAM netname of the CICS client. override to check that the URM does not create names starting
System action: The request to install the virtual terminal is with the VTPREFIX character.
rejected. A response code of ERROR and a reason code of For any other abend, see the description of the abend code in
ALREADYINSTALLED is sent to the client. “Transaction Abend Codes (CICS Transaction Server for
User response: The CICS client should issue CTIN uninstall VSE/ESA)” on page 453.
before any attempt to issue another CTIN install for the same Module: DFHZCT1
NetName.
Module: DFHZCT1 XMEOUT Parameters: date, time,applid, termid, netname
Destination: CSCC
Destination: CSCC
DFHZC3221E date time applid Transaction CTIN - virtual surrogate TCTTE is in use and cannot be
terminal termid VTAM netname netname. The deleted.
name specified is already in use by another Explanation: A CTIN uninstall request has been received
CICS resource. from a CICS client as a result of a CICS_EpiDelTerminal
Explanation: A CTIN install request has been received from a function or terminal emulator operation. However, the

surrogate TCTTE attached to the virtual terminal is still in use details from the virtual terminal that has just been created and
and cannot be deleted. return them back to the CICS client. However the attempt to
extract the details in the form of a builder parameter set (BPS)
netname is the VTAM netname of the CICS client. failed.
System action: Exception trace point AP302F is written. The
attempt to delete the virtual terminal is rejected. netname is the VTAM netname of the CICS client.
User response: Either wait for the transaction to finish or System action: Exception trace point AP3031 is written.
PURGE the transaction. Once the transaction has ended the
virtual terminal will be deleted when the client issues CCIN
install or uninstall.
INSTALLCANCELLED is sent to the client.
Module: DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname resolve this problem. See Part 4 of the CICS Problem
Destination: CSCC Determination Guide for guidance on how to proceed.
Module: DFHZCT1
DFHZC3224E date time applid Transaction CTIN - virtual XMEOUT Parameters: date, time,applid, termid, netname
terminal termid VTAM netname netname. The Destination: CSCC
terminal specified for deletion cannot be
found.
Explanation: A CTIN uninstall request has been received
netname netname. The client data is longer
from a CICS client as a result of a CICS_EpiDelTerminal
than expected.
function or terminal emulator operation. However the virtual
terminal termid does not exist as a remote terminal for this
CICS client.
terminal emulator operation. However the data received was
netname is the VTAM netname of the CICS client. longer than expected. netname is the VTAM netname of the
System action: The attempt to delete the virtual terminal is CICS client.
rejected. System action: Exception trace point AP302D is written –
User response: Determine why a CICS client requested that a data 2 contains the length that was received. The CTIN
non existent virtual terminal be deleted. transaction abnormally terminates with abend code AZAI.
User response: Examine the data sent to CICS from the CICS
If the CTIN uninstall was issued correctly and the virtual client. You may need to contact IBM for assistance. See Part 4
terminal should exist, examine the CICS log for message of the CICS Problem Determination Guide for guidance on how
DFHZC5966 and for DFHZC32xx messages referring to this to proceed.
terminal. Module: DFHZCT1
Module: DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname Destination: CSCC
Destination: CSCC

netname netname. The client header data
netname netname. The terminal cannot be
contains an invalid group.
deleted because the NetName parameter is
missing.
Explanation: A CTIN uninstall request has been received
terminal emulator operation. However the header contains an
from a CICS client as a result of a CICS_EpiDelTerminal
invalid group. netname is the VTAM netname of the CICS
function or terminal emulator operation. However the
client.
NetName parameter, defining which virtual terminal is to be
System action: Exception trace point AP3024 is written – data
deleted, is missing.
2 contains the data received. The CTIN transaction abnormally
netname is the VTAM netname of the CICS client. terminates with abend code AZAI.
System action: Exception trace point AP3037 is written – data User response: Examine the data sent to CICS from the CICS
2 contains the data received. The attempt to delete the virtual client. You may need to contact IBM for assistance. See Part 4
terminal is rejected. of the CICS Problem Determination Guide for guidance on how
User response: Examine the input to CTIN. You may need to proceed.
further assistance from IBM. See Part 4 of the CICS Problem Module: DFHZCT1
Module: DFHZCT1
Destination: CSCC
Destination: CSCC
netname netname. CICS has received invalid
DFHZC3226E date time applid Transaction CTIN - virtual data from the client.
terminal termid VTAM netname netname. Explanation: A CTIN install request has been received from a
CICS cannot access the builder parameter set. CICS client as a result of a CICS_EpiAddTerminal function or
Explanation: A CTIN install request has been received from a terminal emulator operation. CICS attempted to parse this
CICS client as a result of a CICS_EpiDelTerminal function or data but found a discrepancy between the number of
terminal emulator operation. CICS is attempting to extract the parameters, the length of the parameters and the length of the

data received. netname is the VTAM netname of the CICS

DFHZC3241E date time applid Transaction CCIN - VTAM
client.
netname netname. The client data is longer
than expected.
Explanation: A CCIN install request has been received from a
terminates with abend code AZAI.
CICS client. However the data received was longer than
expected. netname is the VTAM netname of the CICS client.
client. You may need further assistance from IBM. See Part 4
2 contains the length that was received. The CCIN transaction
to proceed.
abnormally terminates with abend code AZAF.
Module: DFHZCT1
XMEOUT Parameters: date, time,applid, netname client. You may need further assistance from IBM. See Part 4
Destination: CSCC of the CICS Problem Determination Guide for guidance on how
to proceed.
Module: DFHZCN1
netname netname. CICS has received a client XMEOUT Parameters: date, time,applid, netname
request on an unsupported sync level. Destination: CSCC
Explanation: A CTIN request has been received on a
conversation which is not at synchronization level 0 or 1.
System action: Exception trace point AP302B is written. The
contains an invalid group.
CTIN transaction abnormally terminates with abend code
Explanation: A CCIN request has been received from a CICS
AZAI.
client. However there is an invalid group in the header.
User response: Ensure that the CICS client converses at sync
level 0 or 1.
Module: DFHZCT1
2 contains the data received. The CCIN transaction abnormally
XMEOUT Parameters: date, time,applid, netname terminates with abend code AZAF.
Destination: CSCC User response: Examine the data sent to CICS from the CICS
client.
Module: DFHZCN1
netname netname. The client header data XMEOUT Parameters: date, time,applid, netname
contains an invalid version number. Destination: CSCC
terminal emulator operation. However there is an invalid
version number in the header. netname is the VTAM netname
contains an invalid version number.
of the CICS client.
CICS client. However the header contains an invalid version
value. netname is the VTAM netname of the CICS client.
terminates with abend code AZAI.
User response: Since the version used in the CICS client Either the CICS client is setting up the CCIN header
must match with the version used by the server, one or the incorrectly or a new version of the CICS client software is
other is at the wrong level and should be changed. You may being used which is not supported on CICS Transaction Server
need further assistance from IBM. See Part 4 of the CICS for VSE/ESA Release 1.
Problem Determination Guide for guidance on how to proceed. System action: Exception trace point AP300B is written –
Module: DFHZCT1 data 2 contains the data received. The CCIN transaction
abnormally terminates with abend code AZAF.
User response: Since the version used in the CICS client
Destination: CSCC
must match with the version used by the server, one or the
other is at the wrong level and should be changed. You may
DFHZC3240E date time applid Transaction CCIN - VTAM need further assistance from IBM. See Part 4 of the CICS
netname netname. CICS has received a client Problem Determination Guide for guidance on how to proceed.
request on an unsupported sync level. Module: DFHZCN1
Explanation: A CCIN request has been received on a
conversation which is not at synchronization level 0 or 1.
Destination: CSCC
System action: Exception trace point AP3003 is written. The
CCIN transaction abnormally terminates with abend code DFHZC3244E date time applid Transaction CCIN - VTAM
AZAF. netname netname. The client header data
User response: Ensure that the CICS client converses at sync contains an invalid function.
level 0 or 1. Explanation: A CCIN request has been received from a CICS
Module: DFHZCN1 client. However there is an invalid function in the header.
System action: Exception trace point AP3002 is written - data
Destination: CSCC
2 contains the data received. The CCIN transaction abnormally

terminates with abend code AZAF. You may need to increase the value specified for the MXT
User response: Investigate why the CICS client has sent an system initialization parameter or the CITS TRANCLASS
unknown function call to CCIN. You may need further allocation.
assistance from IBM. See Part 4 of the CICS Problem Module: DFHZCN2
Module: DFHZCN1
Destination: CSCC
Destination: CSCC
DFHZC3248E date time applid Transaction CCIN - virtual
DFHZC3245E date time applid Transaction CCIN - VTAM surrogate TCTTE is in use and cannot be
netname netname. The capabilities parameter deleted.
has not been specified. Explanation: A CCIN request has been received from a CICS
Explanation: A CCIN transaction has been run from a CICS client. There should not be any virtual terminals installed,
client. One of the parameters which must be supplied is the however, one or more were located. The surrogate TCTTE
CAPABILITIES parameter which specifies the capabilities the attached to the virtual terminal is still in use and cannot be
CICS client can support. This parameter is missing. deleted. If this was caused by an immediate shut down of the
client the transaction abend might not have completed before
CICS attempted to delete the client.
System action: The request to install a CICS client is rejected.
A response code of DISASTER and a reason code of netname is the VTAM netname of the CICS client.
INVALIDREQUEST is sent to the client. System action: Exception trace point AP301C is written. The
User response: You need further assistance from IBM to attempt to delete the virtual terminal is rejected.
Determination Guide for guidance on how to proceed. If this is a CCIN install request, the install continues.
Module: DFHZCN1 User response: Determine why the virtual terminal was
installed when CCIN was run.
Destination: CSCC Either wait for the transaction to finish or PURGE the
transaction. Once the transaction completes the virtual
terminall will be deleted at the next CCIN install/uninstall.
DFHZC3246 date time applid Transaction CCIN - virtual Module: DFHZCN2
CICS cannot attach the CDTS transaction.
Destination: CSCC
Explanation: A CCIN request has been received from a CICS
client. As part of the processing, the CDTS transaction was
called to delete virtual terminal termid. However CICS was DFHZC3249E date time applid Transaction CCIN - VTAM
unable to attach the CDTS transaction. netname netname. CICS has received invalid
data from the client.
System action: The attempt to delete the virtual terminal
CICS client. CICS attempted to parse this data but found a
fails. If this is a CCIN install request, the install continues.
discrepancy between the number of parameters, the length of
User response: Ensure that the CDTS transaction and the
the parameters, and the length of the data received. netname is
DFHZATS program are defined correctly as specified in IBM
the VTAM netname of the CICS client.
supplied group DFHSPI and that they are installed.
System action: Exception trace point AP300E is written –
Module: DFHZCN2
data 2 contains the data received. The CCIN transaction
XMEOUT Parameters: date, time,applid, termid, netname abnormally terminates with abend code AZAF.
Destination: CSCC User response: Examine the data sent to CICS from the CICS
client. You may need further assistance from IBM. See Part 4
DFHZC3247 date time applid Transaction CCIN - virtual to proceed.
terminal termid VTAM netname netname. The Module: DFHZCN1
CCIN transaction has timed out waiting for
CDTS to run. XMEOUT Parameters: date, time,applid, netname
Explanation: A CCIN request has been received from a CICS Destination: CSCC
client. As part of the processing, the CDTS transaction is called
to delete virtual terminal termid. However the CCIN
DFHZC3400E date time applid termid tranid Chain exceeds
transaction has waited for the CDTS transaction for one
max chain size. sense ((instance) Module name:
minute and has timed out.
{DFHZRAC | DFHZRVS | DFHZRVX})
netname is the VTAM netname of the CICS client. Explanation: If chain assembly (BUILDCHAIN) has been
System action: The CDTS attempt to delete the virtual specified in the TCTTE, the chain being assembled does not fit
terminal continues and occurs when the CDTS transaction into the IOAREALEN for a maximum chain (IOAREALEN
starts or is 'unsuspended'. Value 2). The remaining space in the IOAREALEN for a
maximum chain is smaller than the maximum RECEIVESIZE.
If this is a CCIN install request, the install continues.
User response: Check to see why the CDTS transaction was If chain assembly (BUILDCHAIN) has been specified in the
TCTTE, but maximum chain value equals zero, either the
unable to start or was hanging.

maximum chain value has been set incorrectly at build time or Module: DFHZNAC
the value has been overwritten.
For the meaning of the sense data, see the explanation on instance, {1=DFHZNAC}
terminated with a transaction dump.
User response: Ensure that the maximum chain size, DFHZC3406E date time applid termid tranid Parameter error.
generated in the RDO TYPETERM with IOAREALEN (value sense ((instance) Module name: {DFHZNAC})
2) keyword, is large enough for the maximum chain expected. Explanation: The request/response unit (RU) received by the
Module: DFHZRVS, DFHZRVX, DFHZRAC logical unit (LU) contains a control function with invalid
parameters.
instance, {1=DFHZRVS, 2=DFHZRVS, 3=DFHZRVS, For the meaning of the sense data, see the explanation on
4=DFHZRVS, 5=DFHZRVS, 6=DFHZRVX, 7=DFHZRAC, topic “DFHZCxxxx messages” on page 356.
8=DFHZRAC} System action: All send and receive requests are purged. If a
Destination: CSNE task is attached, it is abnormally terminated with a transaction
dump. A portion of the TIOA is put to the CSNE log.
User response: Correct the application program.
DFHZC3401I date time applid termid tranid Resource now Module: DFHZNAC
available. sense ((instance) Module name:
{DFHZNAC}) XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Explanation: A resource of the logical unit (LU) is now instance, {1=DFHZNAC}
available. It had previously been temporarily unavailable or Destination: CSNE
had required intervention.
For the meaning of the sense data, see the explanation on DFHZC3407E date time applid termid tranid READ command
topic “DFHZCxxxx messages” on page 356. does not carry change direction indicator.
System action: Any outstanding read or write operation is sense ((instance) Module name: {DFHZNAC})
retried. Explanation: A request for input (for example, a READBUF
User response: None. command) sent to a logical unit (LU) type 2 (3270
Module: DFHZNAC compatibility mode logical unit) must carry the SNA change
direction indicator. The LU has received such a request, but
XMEOUT Parameters: date, time,applid, termid, tranid, sense, the indicator is not set.
Destination: CSNE Since the setting of the change direction indicator is controlled
by terminal control, this message indicates that an internal
logic error may have occurred. The error is not necessarily in
DFHZC3402E date time applid termid tranid Invalid READ terminal control, but may be in the logical unit or some other
with outbound chain control. sense ((instance) element of the network.
Module name: {DFHZRVS})
Explanation: A DFHTC TYPE=READ request is being For the meaning of the sense data, see the explanation on
processed, although the previously issued DFHTC topic “DFHZCxxxx messages” on page 356.
TYPE=WRITE request did not complete a chain. System action: The task and the VTAM session for the logical
unit are abnormally terminated.
topic “DFHZCxxxx messages” on page 356. Message DFHME0116 is normally produced containing the
System action: All outstanding receive requests are purged. symptom string for this problem.
If a task is attached, it is abnormally terminated with a User response: Identify the request that caused the error, and
transaction dump. locate the element of the network responsible.
User response: Correct the application program. Module: DFHZNAC
Module: DFHZRVS XMEOUT Parameters: date, time,applid, termid, tranid, sense,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
instance, {1=DFHZRVS} Destination: CSNE
Destination: CSNE
DFHZC3408E date time applid termid tranid Presentation space
DFHZC3405E date time applid termid tranid Catastrophic integrity lost. sense ((instance) Module name:
bracket error. sense ((instance) Module name: {DFHZNAC})
{DFHZNAC}) Explanation: The contents of data for screen presentation by
Explanation: The logical unit detected a failure of CICS to a logical unit has been altered. This is usually due to operator
enforce bracket rules. action. For example, the TEST/NORMAL key may have been
used or the 3270 SYS REQ key may have been pressed.
topic “DFHZCxxxx messages” on page 356. It may also have been caused by factors other than operator
System action: All outstanding send and receive requests are action, for example, 3270 regeneration buffer failure.
purged. If a task is attached, it is abnormally terminated with For the meaning of the sense data, see the explanation on
a transaction dump. The session is terminated. topic “DFHZCxxxx messages” on page 356.
Message DFHME0116 is normally produced containing the System action: Any outstanding requests are canceled. If a
symptom string for this problem. task is attached, it is abnormally terminated with a transaction
User response: Use the symptom string, a VTAM trace, and dump.
if necessary the dump, to determine the source of the problem.

User response: Determine reason for failure at the remote If "resource temporarily unavailable" notification is received,
terminal. an associated VTAM message is usually issued.
Module: DFHZNAC User response: Refer to the associated VTAM message, if
applicable, and follow the guidance provided.
Destination: CSNE
DFHZC3409E date time applid termid tranid Unexpected
negative response received. sense ((instance)
Module name: {DFHZRAC}) DFHZC3412E date time applid termid tranid Intervention
Explanation: CICS received a negative response to a required on secondary resource. sense
command for which a negative response would not normally ((instance) Module name: {DFHZNAC})
be expected. Explanation: Operator action is requested for the secondary
resource of a logical unit (LU). However, no such resource is
For the meaning of the sense data, see the explanation on immediately available. In the case of a 3270-compatible LU,
topic “DFHZCxxxx messages” on page 356. this message means that the printer most likely to be available
System action: All outstanding send and receive requests are for a PRINT request has an Intervention Required status.
a transaction dump. The node is placed out of service and the For the meaning of the sense data, see the explanation on
TCTTE, RPL, and action flags are logged to CSNE. topic “DFHZCxxxx messages” on page 356.
System action: The system waits for a logical unit status
Message DFHME0116 is normally produced containing the message and, when this is received, takes appropriate system
symptom string for this problem. action.
User response: Ensure that the application programs running User response: Correct the problem that relates to the device.
concurrently do not alter the TCTTE. Check that the SNA Module: DFHZNAC
flows on the session are valid and that the logical unit is not
violating SNA protocols. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Module: DFHZRAC instance, {1=DFHZNAC}
Destination: CSNE
instance, {1=DFHZRAC}
Destination: CSNE DFHZC3413E date time applid termid tranid Logical Unit busy.
Explanation: The logical unit has rejected a request because
DFHZC3410E date time applid termid tranid Invalid input its resources are busy (for example, it is communicating with
when LU status expected. sense ((instance) the system services control point (SSCP)), and thus is unable
Module name: {DFHZRVX}) to process the request.
Explanation: Input (other than a logical unit status message)
was received after a request was rejected with a system sense For the meaning of the sense data, see the explanation on
code indicating a possibly rectifiable error condition at the topic “DFHZCxxxx messages” on page 356.
terminal node: for example, Intervention Required. The System action: The system waits for a logical unit status
subsequent LU status message indicates that the error message and then takes appropriate action.
situation has now been corrected, or that the request is User response: None.
permanently not executable. Module: DFHZNAC
For the meaning of the sense data, see the explanation on XMEOUT Parameters: date, time,applid, termid, tranid, sense,
topic “DFHZCxxxx messages” on page 356. instance, {1=DFHZNAC}
System action: If a task is attached, it is abnormally Destination: CSNE
User response: Conform to SNA protocol by ensuring that
the next transmission is an LUSTATUS message with a system DFHZC3414E date time applid termid tranid Request not
sense for either Resource Available (0001) or Function Not executable. Secondary resource unavailable.
Executable (081C). sense ((instance) Module name: {DFHZNAC})
Module: DFHZRVX Explanation: The secondary resource of a logical unit is
permanently unavailable to complete a request. For a
XMEOUT Parameters: date, time,applid, termid, tranid, sense, 3270-compatible LU, this means that a printer was not
instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX} available for a PRINT request.
Destination: CSNE
DFHZC3411E date time applid termid tranid Resource System action: All outstanding send and receive requests are
temporarily unavailable. sense ((instance) purged. If a task is attached, it is abnormally terminated with
Module name: {DFHZNAC}) a transaction dump.
Explanation: A terminal resource required to complete a User response: Determine the reason why the resource is not
request is temporarily unavailable. available at the remote terminal.
Module: DFHZNAC
topic “DFHZCxxxx messages” on page 356. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
System action: The request is retried unless the device is one instance, {1=DFHZNAC}
that sends an LUSTATUS message after receiving a "resource Destination: CSNE
temporarily unavailable" notification.

DFHZC3415E date time applid termid tranid No data available. DFHZC3418E date time applid termid tranid System generation
sense ((instance) Module name: {DFHZNAC}) error. The netname logon request was rejected.
Explanation: A receive request has been rejected by the sense ((instance) Module name: {DFHZLGX |
logical unit because it has no data to send for one of the DFHZSCX})
following reasons: Explanation: A logon request was rejected because the
v The device is not capable of input (for instance, it is a TCTTE for the ISC session had been generated with an
printer) incompatible SESSIONTYPE.
v The logical unit is not capable of sending data at the time.
For example, a requested 3790 data set is not available at For the meaning of the sense data, see the explanation on
the time. topic “DFHZCxxxx messages” on page 356.
System action: The request is rejected.
For the meaning of the sense data, see the explanation on User response: Change the TCTTE generation to specify a
topic “DFHZCxxxx messages” on page 356. secondary logical unit at one end of the connection, and a
System action: The receive request is halted. If a task is primary logical unit at the other end.
attached, it is abnormally terminated with a transaction dump. A primary logical unit should have SESSIONTYPE=SEND or
User response: Verify that the request was issued to the SESSIONTYPE=FASTSEND, and a secondary logical unit
correct device and that the device is capable of data should have SESSIONTYPE=RECEIVE or
transmission. SESSIONTYPE=FASTRECV.
Module: DFHZNAC Module: DFHZSCX, DFHZLGX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, XMEOUT Parameters: date, time,applid, termid, tranid, netname,
instance, {1=DFHZNAC} sense, instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZLGX}
Destination: CSNE Destination: CSNE
DFHZC3416E date time applid termid tranid Session failure. A DFHZC3419E date time applid termid tranid Session failure.
connection request for an invalid node nodeid The bind parameter for node netname is
could not be terminated. sense ((instance) unacceptable. sense ((instance) Module name:
Module name: {DFHZSCX}) {DFHZSCX})
Explanation: The requested logon was to be rejected, but the Explanation: A connection request was rejected because the
attempt to send a negative response was rejected by VTAM. characteristics specified for the connecting system were
For the meaning of the sense data, see the explanation on unacceptable.
System action: No further attempts are made to topic “DFHZCxxxx messages” on page 356.
communicate with the invalid node. System action: The request is rejected. The bind parameter is
User response: Inspect the CSNE, CSMT and CSTL logs for printed on the CSNE log.
an indication of a VTAM storage problem or error message. User response: Determine whether the connecting system has
Determine whether the node was invalid. If it was valid, specified its characteristics correctly. If it has not, correct the
update the CICS TCT for that node. requesting system.
Module: DFHZNAC Module: DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, XMEOUT Parameters: date, time,applid, termid, tranid, netname,
sense, instance, {1=DFHZSCX} sense, instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZSCX,
Destination: CSNE 4=DFHZSCX, 5=DFHZSCX, 6=DFHZSCX, 7=DFHZSCX,
8=DFHZSCX, 9=DFHZSCX, 10=DFHZSCX, 11=DFHZSCX,
DFHZC3417E date time applid termid tranid Session
processing error. A request for
synchronization has been ignored. sense
((instance) Module name: {DFHZSDR})
Explanation: A request for a sync point to be taken was
ignored. COMMIT or ABORT has not been issued.
36=DFHZSCX, 37=DFHZSCX, 38=DFHZSCX}
For the meaning of the sense data, see the explanation on Destination: CSNE
terminated with a transaction dump. DFHZC3420E date time applid termid tranid Session
User response: To determine the cause of the problem, connection error. Node netname is out of
inspect the CSNE, CSMT and CSTL logs for further diagnostic service. sense ((instance) Module name:
information. Also inspect transaction tranid. {DFHZOPN | DFHZSCX})
Module: DFHZSDR Explanation: A logon request was rejected because the
TCTTE is out of service.
instance, {1=DFHZSDR} For the meaning of the sense data, see the explanation on
Destination: CSNE topic “DFHZCxxxx messages” on page 356.
System action: The request is rejected.
User response: Place the terminal in service by using the
master terminal program and reissuing the connection request.
Module: DFHZSCX, DFHZOPN


DFHZC3424E date time applid termid tranid Session failure.
sense, instance, {1=DFHZOPN, 2=DFHZSCX, 3=DFHZSCX}
Session terminated immediately. sense
Destination: CSNE
((instance) Module name: {DFHZNSP})
Explanation: Communication with a node was interrupted
DFHZC3421E date time applid termid tranid Session shutdown during a session because a session outage was detected, or
request received. Node netname is receiving because a VTAM VARY INACT command was issued.
orderly shutdown. sense ((instance) Module
Error messages produced for the same session after this
name: {DFHZASX})
message may be caused by the session failure and may not be
Explanation: A shutdown request was received for the
the reason for it. If this is the case, they can be ignored.
system. An orderly termination procedure has begun.
System action: The session is canceled. The session may be
System action: Orderly termination of the session is started.
recovered later by VTAM. See also messages DFHZC2409 and
Access to the remote system is stopped after the current
DFHZC2410.
transaction has finished.
User response: Check if the failure was caused by an
operator-issued VTAM VARY INACT. If this is not the case,
Module: DFHZASX
use the sense data and any associated messages to investigate
XMEOUT Parameters: date, time,applid, termid, tranid, netname, the reason for the failure.
sense, instance, {1=DFHZASX} Module: DFHZNSP
Destination: CSNE
instance, {1=DFHZNSP, 2=DFHZNSP, 3=DFHZNSP}
DFHZC3422E date time applid termid tranid Connection Destination: CSNE
failure. Request rejected before a session
could be started. sense ((instance) Module DFHZC3425E date time applid termid tranid Session recovery.
name: {DFHZNSP}) Resynchronization failed. Possibly logging
Explanation: An error occurred while trying to connect the error or one side cold started. sense ((instance)
two systems. The request was terminated before a session had Module name: {DFHZSCX})
been established. Explanation: Either one side of the intersystem link has not
For the meaning of the sense data, see the explanation on recovered sequence numbers, or the mismatch of sequence
topic “DFHZCxxxx messages” on page 356. numbers is such that it could not have been caused solely by
System action: The request is terminated. session failure.
User response: Determine the cause of the problem by For the meaning of the sense data, see the explanation on
inspecting the VTAM logs. If the problem is due to a shortage topic “DFHZCxxxx messages” on page 356.
of storage or another temporary error, reissue the request System action: Processing continues.
when the system is less heavily loaded. User response: Check that cold start is not being used when
Module: DFHZNSP the other system is under emergency restart. Check that the
XMEOUT Parameters: date, time,applid, termid, tranid, sense, correct version of the system log is being used.
instance, {1=DFHZNSP, 2=DFHZNSP} Module: DFHZCSX
DFHZC3423I date time applid termid tranid FM function not Destination: CSNE
supported. A function requested in an FMD
RU is not supported by the receiver. sense DFHZC3426E date time applid termid tranid Resource
((instance) Module Name: {DFHZNAC}) unknown. sense ((instance) Module name:
Explanation: CICS has received a negative response (VTAM {DFHZNAC})
sense code 0826). The receiver does not support the function Explanation: During intersystem connection, no matching
requested by the sender. TCTTE could be found.
System action: All outstanding SENDs and RECEIVEs are System action: The request is terminated.
purged. If a task is attached, it is abnormally terminated with User response: Ensure that the name of the requested TCTTE
a transaction dump. is correctly specified in the requesting system.
User response: Investigate the reason for issuing a request Module: DFHZNAC
for a function that the receiver does not support.
Module: DFHZNAC XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Destination: CSNE

User response: Check whether this resynchronization

DFHZC3427E date time applid termid tranid Invalid parameter
mismatch is acceptable.
in bind area. sense ((instance) Module name:
Module: DFHZRSY
{DFHZNAC})
Explanation: During intersystem connection, either one or XMEOUT Parameters: date, time,applid, termid, tranid, sense,
more parameters contained in the bind area of the request instance, {1=DFHZRSY}
were invalid, or were not supported. Destination: CSNE
topic “DFHZCxxxx messages” on page 356. DFHZC3431E date time applid termid tranid Resynch error -
System action: The request is terminated. inbound flow sequence numbers do not
User response: Determine which parameters in the bind area agree. sense ((instance) Module name:
are incorrect, and correct them. {DFHZRSY})
Module: DFHZNAC Explanation: The logical sequence number for CICS inbound
flow, as used by CICS in the set-and-test-sequence-number
(STSN) request or response, does not agree with the sequence
number for the same flow maintained by the other LU.
Destination: CSNE
DFHZC3428E date time applid termid tranid Resynch error -
Other logical unit did not resynchronize.
sense ((instance) Module name: {DFHZRSY |
DFHZSCX})
Module: DFHZRSY
Explanation: CICS expected a resynchronization process to
occur during system initiation, but the logical unit (LU) did XMEOUT Parameters: date, time,applid, termid, tranid, sense,
not resynchronize. instance, {1=DFHZRSY}
Destination: CSNE
System action: Processing continues. DFHZC3432E date time applid termid tranid Resynch error -
User response: Check whether this resynchronization unexpected code received in response to
mismatch is acceptable. STSN. sense ((instance) Module name:
Module: DFHZRSY, DFHZSCX {DFHZRSY})
Explanation: "Test Positive", "Test Negative", or "Test Invalid"
was not one of the codes in the response to STSN.
instance, {1=DFHZRSY, 2=DFHZRSY, 3=DFHZSCX}
Destination: CSNE For the meaning of the sense data, see the explanation on
CICS did not resynchronize, other logical
unit was expecting resynch. sense ((instance)
Module: DFHZRSY
Module name: {DFHZRSY | DFHZSYX})
Explanation: CICS did not go through a resynchronization XMEOUT Parameters: date, time,applid, termid, tranid, sense,
process that was expected to occur by the other LU. instance, {1=DFHZRSY, 2=DFHZRSY}
Destination: CSNE
System action: Processing continues. DFHZC3433E date time applid termid tranid FMH7 was
User response: Check whether this resynchronization received on ISC session. Sense code is :
mismatch is acceptable. xxxxxxxx {Error log data is : No error log data
Module: DFHZRSY, DFHZSYX received. | No error log data available. } sense
((instance) Module name: {DFHZERH |
DFHZRAC | DFHZRVX})
instance, {1=DFHZRSY, 2=DFHZRSY, 3=DFHZRSY,
Explanation: The transaction is communicating with a logical
4=DFHZRSY, 5=DFHZSYX}
unit (LU) type LU6.1 or LU6.2.
Destination: CSNE
The logical unit sent an FMH7 which may carry error log
data. If error log data is included, then the text is inserted in
this message.
Outbound flow sequence numbers do not
agree. sense ((instance) Module name: For the meaning of the sense data, see the explanation on
{DFHZRSY}) topic “DFHZCxxxx messages” on page 356.
Explanation: The CICS outbound flow sequence number System action: The action taken depends upon the sense
does not agree with that maintained by the other LU. code.
User response: If the receiving transaction is designed to
handle this situation, no action is necessary. However, if this is
not the case, use the sense code and any error log data to
determine why the connected logical unit sent the FMH7.

If the connected LU is another CICS system, the error log data System action: The session is terminated.
is a CICS message. User response: Determine why the end user is not
authorized to perform the request.
If the connected LU is not a CICS system, see that product's Module: DFHZNAC
documentation for details of error log data. Some products
permit the user to define the contents of error log data. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Module: DFHZRVX, DFHZRAC, DFHZERH instance, {1=DFHZNAC}
Destination: CSNE
XMEOUT Parameters: date, time,applid, termid, tranid, xxxxxxxx,
{1= Error log data is :, 2=No error log data received., 3=No error
log data available. }, xxxxxxxx, sense, instance, {1=DFHZRVX, DFHZC3437I date time applid termid tranid Node netname
2=DFHZRAC, 3=DFHZRAC, 4=DFHZERH} action taken: action ((instance) Module name:
Destination: CSNE {DFHZNAC})
Explanation: After an error has been processed by
DFHZNAC, certain actions may be taken to correct the error.
DFHZC3434E date time applid termid tranid Unbind received
This message indicates the actions that were set. The actions
while session still active. sense ((instance)
taken can differ from the actions set, depending on the type
Module name: {DFHZSCX})
and state of the node at the time of the error.
Explanation: One side of the intersystem link (secondary)
System action:
received an unbind command without normal termination
protocol being observed. This means an abnormal termination Action Effect
of the session was performed, possibly caused by the other ABRECV
side of the intersystem link abnormally terminating. Cancel receive.
ABSEND
Cancel send.
ABTASK
System action: The session is terminated.
Abend task
User response: Determine the cause of the termination by
CLSDST
using CICS Trace and the diagnostic information available on
Close session.
the CSNE log. Try to reestablish the session.
GMM Send good morning message.
Module: DFHZSCX
OUTSRV
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Place session out of service.
instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZSCX, CREATE
4=DFHZSCX, 5=DFHZSCX, 6=DFHZSCX, 7=DFHZSCX, Allow ATI to acquire the session if required.
8=DFHZSCX, 9=DFHZSCX, 10=DFHZSCX} NOCREATE
Destination: CSNE Do not allow ATI to acquire the session.
NEG RESP
Send an exception response.
DFHZC3435E date time applid termid tranid Path error SIMLOGON
detected. Device cannot be contacted. sense Generate SIMLOGON request for the session.
((instance) Module name: {DFHZNAC}) CNTASK
Explanation: VTAM can no longer transmit to a device Cancel the task.
because there is no access path to that device. This usually SYSDUMP
occurs because the device or 3270 has been powered off. Take a system dump.
PURGEBMS
Purge any BMS pages.
User response: The user action depends on what action has
been taken by the system. This is indicated by action in the
message text.
Module: DFHZNAC
is placed out of service. The session is terminated. XMEOUT Parameters: date, time,applid, termid, tranid, netname,
User response: Determine the cause of the termination. Try to action, instance, {1=DFHZNAC}
reestablish the session. Destination: CSNE
Module: DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, DFHZC3438E date time applid termid tranid Device powered
instance, {1=DFHZNAC} off. sense ((instance) Module name:
Destination: CSNE {DFHZNAC})
Explanation: A request has been rejected by the logical unit
because the associated device has been powered off. This
DFHZC3436E date time applid termid tranid End user not
message may be caused by operator action. For example, the
authorized. sense ((instance) Module name:
TEST/NORMAL key may have been used.
{DFHZNAC})
Explanation: A sense code has been received specifying that For the meaning of the sense data, see the explanation on
an unauthorized request was made to the remote node. The topic “DFHZCxxxx messages” on page 356.
request was rejected. System action: The system waits for a logical unit status
message and, when the message has been received, takes
appropriate system action.

User response: Correct the problem that relates to the device.

DFHZC3442I date time applid Immediate termination of
Module: DFHZNAC
VTAM sessions requested. sense ((instance)
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Module name: {DFHZSHU | DFHZTPX})
instance, {1=DFHZNAC} Explanation: A request for an immediate close of all VTAM
Destination: CSNE sessions and subsequent close of CICS VTAM ACB has been
received. The request may have been initiated by the CICS
master terminal command or by the VTAM network closing
DFHZC3439E date time applid termid tranid Negative response down.
received to SDT. sense ((instance) Module
name: {DFHZNAC}) This message is also issued if V NET,ID=...,INACT is issued
Explanation: A negative response has been received to the by the VTAM operator.
START DATA TRAFFIC (SDT) command.
topic “DFHZCxxxx messages” on page 356. System action: All requests on a VTAM session are
System action: Processing continues. abnormally terminated and the session is closed. The VTAM
User response: None. ACB is then closed.
Module: DFHZNAC
If V NET,ID=...,INACT was issued by the VTAM operator,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, VTAM waits for all sessions to be closed before informing
instance, {1=DFHZNAC} CICS. In this case there are no sessions to be abnormally
Destination: CSNE terminated. This message may be issued twice, once by
DFHZTPX and once by DFHZSHU. The messages will have
different instance numbers.
DFHZC3440E date time applid termid tranid Unable to send User response: None.
error message - session in free status. sense Module: DFHZSHU, DFHZTPX
((instance) Module name: {DFHZEMW})
Explanation: DFHZEMW was attempting to write a message XMEOUT Parameters: date, time,applid, sense, instance,
to another node, but was unable to do so because the session {1=DFHZSHU, 4=DFHZTPX, 5=DFHZSHU}
was in "between bracket" status. Destination: CSNE
In this state, it is not possible to send the message in the

normal way. The session was in free status, probably because DFHZC3443I date time applid VTAM has been cancelled or
the application program had issued a SEND command with the ACB has been forceclosed. VTAM
the LAST option. sessions terminated.sense ((instance) Module
name: {DFHZSHU | DFHZSYX | DFHZTPX})
For the meaning of the sense data, see the explanation on Explanation: VTAM has been cancelled or force closed by the
topic “DFHZCxxxx messages” on page 356. CICS/VTAM operator.
User response: Check to see why the other node sent its For the meaning of the sense data, see the explanation on
request EXCEPTION response mode. Change the response topic “DFHZCxxxx messages” on page 356.
mode to DEFINITE if error messages are to be sent. System action: CICS will close its ACB. All transactions
Module: DFHZEMW running on VTAM sessions are abnormally terminated.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Module: DFHZSHU, DFHZTPX, DFHZSYX
instance, {1=DFHZEMW, 2=DFHZEMW}
Destination: CSNE XMEOUT Parameters: date, time,applid, sense, instance,
{1=DFHZSHU, 3=DFHZSYX, 4=DFHZTPX,5=DFHZSHU}
Destination: CSNE
DFHZC3441I date time applid Orderly termination of VTAM
sessions requested. sense ((instance) Module
name: {DFHZSHU}) DFHZC3444E date time applid termid tranid Unexpected
Explanation: A request for an orderly close of VTAM sessions condition detected during RECEIVE
and subsequent close of CICS VTAM ACB has been received. processing. sense ((instance) Module name:
The request may have been initiated by the CICS master {DFHZRVS})
terminal command or by the VTAM network closing down. Explanation: CICS has detected a data runaway condition
while receiving data from terminal termid.
System action: All nodes are quiesced and each session is topic “DFHZCxxxx messages” on page 356.
closed as it becomes inactive. When all sessions have been System action: CICS terminates the session and places the
closed, the ACB is closed. terminal out of service. If a task is attached, it is abnormally
User response: None. terminated with a transaction dump.
Module: DFHZSHU Message DFHME0116 is normally produced containing the
XMEOUT Parameters: date, time,applid, sense, instance, symptom string for this problem.
{1=DFHZSHU} User response: To determine the cause of this error,
Destination: CSNE v Check for a terminal malfunction, for example the device
may be sending the same data repeatedly, or
v Check for a network problem.

Module: DFHZRVS
DFHZC3448E date time applid termid tranid Security
XMEOUT Parameters: date, time,applid, termid, tranid, sense, identification error. sense ((instance) Module
instance, {1=DFHZRVS} name: {DFHZNAC})
Destination: CSNE Explanation: CICS has received a negative response to a
request to access a resource because it was not authorized. If it
was an OPNDST (BIND) request, CICS did not send the
DFHZC3445E date time applid termid tranid State error. sense authorization sequence expected by a logical unit. CICS does
((instance) Module name: {DFHZNAC}) not support the security feature in the bind.
Explanation: CICS has received a state error negative
response (VTAM sense code 20yy). For the meaning of the sense data, see the explanation on
For the meaning of the sense data, see the explanation on System action: The logical unit is placed out of service and
topic “DFHZCxxxx messages” on page 356. the session is closed.
System action: User response: CICS does not support the security feature in
System action: All outstanding send and receive requests are the bind. Modify the authorization parameters in the remote
purged. If a task is attached, it is abnormally terminated with logical unit so that it does not require authorization to initiate
a transaction dump. Communication with the node is a session.
terminated by issuing a VTAM CLSDST macro, and the node Module: DFHZNAC
User response: Determine the reason for the error before XMEOUT Parameters: date, time,applid, termid, tranid, sense,
restarting the session. instance, {1=DFHZNAC}
Module: DFHZNAC Destination: CSNE

instance, {1=DFHZNAC} DFHZC3449I date time applid termid tranid Leaving
Destination: CSNE unattended mode. sense ((instance) Module
name: {DFHZNAC})
Explanation: CICS has received a status message from a
DFHZC3446E date time applid termid tranid Request error. logical unit indicating that the terminal is now attended.
Explanation: CICS has received a request error negative Note that this is the default mode of operation.
response (VTAM sense code 10yy) for which it does not
recognize the minor code yy.
For the meaning of the sense data, see the explanation on System action: The mode of operation bit TCTEMOPU is
topic “DFHZCxxxx messages” on page 356. reset in the TCTTE.
System action: All outstanding send and receive requests are User response: For logical units that can operate in
purged. If a task is attached, it is abnormally terminated with unattended mode, the application programmer should test the
a transaction dump. Communication with the node is mode of operation before starting a conversational sequence
terminated by issuing a VTAM CLSDST macro, and the node with the terminal operator. If the bit is on, no operator action
is placed out of service. can be expected.
User response: Determine the reason for the error.
For command level, use the EXEC CICS ASSIGN UNATTEND
Module: DFHZNAC
(data area) command to obtain the value of TCTEMOPU.
Destination: CSNE
Destination: CSNE
DFHZC3447E date time applid termid tranid Request reject
error. sense ((instance) Module name: DFHZC3450I date time applid termid tranid Entering
{DFHZNAC}) unattended mode. sense ((instance) Module
Explanation: CICS has received a request reject negative name: {DFHZNAC})
response (VTAM sense code 08yy) for which it does not Explanation: CICS has received a status message from a
recognize the minor code yy. logical unit indicating that the terminal is no longer attended.
System action: All outstanding send and receive requests are System action: The mode of operation bit TCTEMOPU is set
purged. If a task is attached, it is abnormally terminated with in the TCTTE.
a transaction dump. Communication with the node is User response: For logical units that can operate in
terminated by issuing a VTAM CLSDST macro, and the node unattended mode, the application programmer should test the
is placed out of service. mode of operation before starting a conversational sequence
User response: Determine the reason for the error. with the terminal operator. If the bit is on, no operator action
Module: DFHZNAC can be expected.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, For command level, use the EXEC CICS ASSIGN UNATTEND
instance, {1=DFHZNAC} (data area) command to obtain the value of TCTEMOPU.
Destination: CSNE Module: DFHZNAC

instance, {1=DFHZNAC} System action: All outstanding send and receive requests are
Destination: CSNE purged. If a task is attached, it is abnormally terminated with
DFHZC3451I date time applid termid tranid Currently no data is placed out of service.
to send. sense ((instance) Module name: User response: None.
{DFHZNAC}) Module: DFHZNAC
Explanation: Following the issue of a READ command to a
logical unit, or the completion of a transaction associated with XMEOUT Parameters: date, time,applid, termid, tranid, sense,
the logical unit, CICS has received a status message from the instance, {1=DFHZNAC}
logical unit indicating that it currently has no data to send. Destination: CSNE

topic “DFHZCxxxx messages” on page 356. DFHZC3454E date time applid termid tranid Session initiation
System action: If a data interchange (DFHDI) receive request failure. Bind response from node netname is
is outstanding, it will complete with DSSTAT condition and a unacceptable. sense ((instance) Module name:
response code X'15'. {DFHZOPX})
Explanation: A remote secondary's response to a negotiable
If no task is active and no work is outstanding for the bind contained unacceptable parameters.
terminal, the soft CLSDEST action flag is set and DFHZNEP is
called. Unless it is reset by DFHZNEP, the session is For the meaning of the sense data, see the explanation on
terminated. topic “DFHZCxxxx messages” on page 356.
User response: Ensure that no more receive requests are System action: Session initialization fails. The sent and
issued to the terminal. received bind parameters are printed on the CSNE log.
Module: DFHZNAC User response: Look at the parameters printed on the CSNE
log. Ensure that the remote system has correctly specified its
XMEOUT Parameters: date, time,applid, termid, tranid, sense, characteristics. If there is an invalid format, change it to LEN
instance, {1=DFHZNAC} PSQ LEN SSQ.
Destination: CSNE Module: DFHZOPX
DFHZC3452E date time applid termid tranid Signal received - sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZOPX,
Code xxxx. sense ((instance) Module name: 4=DFHZOPX, 5=DFHZOPX, 6=DFHZOPX, 7=DFHZOPX,
{DFHZASX}) 8=DFHZOPX, 9=DFHZOPX, 10=DFHZOPX, 11=DFHZOPX,
Explanation: CICS has received a SIGNAL command from a 12=DFHZOPX, 13=DFHZOPX, 14=DFHZOPX, 15=DFHZOPX,
logical unit. The SIGNAL codes received with the SIGNAL 16=DFHZOPX, 17=DFHZOPX, 18=DFHZOPX, 19=DFHZOPX,
command are made available to the DFHZNEP user program. 20=DFHZOPX, 21=DFHZOPX, 22=DFHZOPX, 23=DFHZOPX,
If a task is active, the SIGNAL condition is raised on return to 24=DFHZOPX, 25=DFHZOPX, 26=DFHZOPX, 27=DFHZOPX,
the application program. This message is produced only when 28=DFHZOPX, 29=DFHZOPX, 30=DFHZOPX, 31=DFHZOPX,
SIGNAL codes are passed to the node abnormal condition 32=DFHZOPX, 33=DFHZOPX, 34=DFHZOPX, 35=DFHZOPX,
program (DFHZNAC). CICS does this for Type 4 logical units 36=DFHZOPX, 37=DFHZOPX, 38=DFHZOPX, 39=DFHZOPX,
only. 40=DFHZOPX, 41=DFHZOPX, 42=DFHZOPX, 43=DFHZOPX,
44=DFHZOPX, 45=DFHZOPX}
For the meaning of the sense data, see the explanation on Destination: CSNE
System action: If the SIGNAL code is 0001 0000 (request
change direction), any further output request will cause the DFHZC3455E date time applid termid tranid Session initiation
IGREQCD condition to be raised. All SIGNAL codes will failure. Bind response from node netname
cause the SIGNAL condition to be raised. contains an invalid session qualifier pair.
User response: For logical units for which CICS enforces sense ((instance) Module name: {DFHZOPX})
SIGNAL request change direction, if the code is 0001 0000, Explanation: A remote secondary's response to a negotiable
issue a receive request or terminate transaction tranid. bind contained an invalid session qualifier pair in the user
data field. Either it had an invalid format, or the primary SQ
If the code is NOT 0001 0000, terminate transaction tranid and had been altered.
refer to the VTAM Programming manual for further guidance.
Module: DFHZASX For the meaning of the sense data, see the explanation on
XMEOUT Parameters: date, time,applid, termid, tranid, xxxx, System action: Session initialization fails. The sent and
sense, instance, {1=DFHZASX, 2=DFHZASX} received bind images are printed on the CSNE log.
Destination: CSNE User response: Correct the error in the remote system. If
there is an invalid format, change it to LEN PSQ LEN SSQ.
Module: DFHZOPX
DFHZC3453E date time applid termid tranid RH usage error.
sense ((instance) Module name: {DFHZNAC}) XMEOUT Parameters: date, time,applid, termid, tranid, netname,
Explanation: CICS has received a request header (RH) usage sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZOPX}
error negative response for which it does not recognize the Destination: CSNE
minor code yy.

DFHZC3456E date time applid termid tranid No outboard DFHZC3460E date time applid termid tranid Requested
formats loaded. sense ((instance) Module name: character set not present. sense ((instance)
{DFHZNAC}) Module name: {DFHZNAC})
Explanation: An outboard format has been referenced, but no Explanation: The Referenced Logical Character Set Identifier
outboard formats are loaded on this logical unit. (LCID) specified in the define alternate character set is not
System action: Transaction tranid is abnormally terminated known.
with a transaction dump.
User response: Load the necessary outboard formats.
Module: DFHZNAC topic “DFHZCxxxx messages” on page 356.
System action: Transaction tranid is abnormally terminated
XMEOUT Parameters: date, time,applid, termid, tranid, sense, with a transaction dump.
instance, {1=DFHZNAC} User response: Ensure that the character set referenced by
Destination: CSNE the LCID is loaded.
Module: DFHZNAC
DFHZC3457E date time applid termid tranid Requested XMEOUT Parameters: date, time,applid, termid, tranid, sense,
outboard format not loaded. sense ((instance) instance, {1=DFHZNAC}
Module name: {DFHZNAC}) Destination: CSNE
Explanation: An outboard format has been referenced, but
the requested format is not loaded on this logical unit.
DFHZC3461I date time applid termid tranid Node netname
For the meaning of the sense data, see the explanation on session started. sense ((instance) Module name:
topic “DFHZCxxxx messages” on page 356. {DFHZEV1 | DFHZEV2 | DFHZOPX})
System action: Transaction tranid is abnormally terminated Explanation: CICS has successfully issued or received a bind
with a transaction dump. to the node netname.
User response: Load the requested outboard format.
Module: DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, System action: Processing continues.
instance, {1=DFHZNAC} User response: None.
Destination: CSNE Module: DFHZOPX, DFHZEV1, DFHZEV2
DFHZC3458E date time applid termid tranid Requested format sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZEV1,
group not loaded. sense ((instance) Module 4=DFHZEV2}
name: {DFHZNAC}) Destination: CSNE
Explanation: An outbound format group has been referenced,
but that format group is not loaded on this logical unit.
DFHZC3462I date time applid termid tranid Node netname
For the meaning of the sense data, see the explanation on session terminated. sense ((instance) Module
topic “DFHZCxxxx messages” on page 356. name: {DFHZCLS})
System action: Transaction tranid is abnormally terminated Explanation: A session with node netname has been closed.
User response: Load the required format group.
Module: DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, User response: None.
instance, {1=DFHZNAC} Module: DFHZCLS
Destination: CSNE
sense, instance, {1=DFHZCLS, 2=DFHZCLS}
DFHZC3459E date time applid termid tranid Unsupported data Destination: CSNE
stream. sense ((instance) Module name:
{DFHZNAC})
DFHZC3463I date time applid VTAM ACB opened. VTAM
Explanation: The data stream sent to the device contains
Return Code = X'rc'. Time = time sense
control data for functions that the device does not support.
((instance) Module name: {DFHZOPA})
For the meaning of the sense data, see the explanation on Explanation: The master terminal operator issued a CEMT or
topic “DFHZCxxxx messages” on page 356. CSMT command to open the VTAM ACB.
System action: Transaction tranid is abnormally terminated.
User response: Either ensure that transaction tranid is not run
against the terminal, or change the terminal to one that
supports the data stream.
User response: If the return code is zero, VTAM sessions can
Module: DFHZNAC
be enabled.
If the return code X'rc' is not zero, see section "VTAM codes"
in z/VSE Messages and Codes - Volume 2 to determine why the
Destination: CSNE
VTAM ACB was not opened.
Module: DFHZOPA

XMEOUT Parameters: date, time,applid, X'rc', time, sense, terminal operator should issue the command CEMT SET TER
instance, {1=DFHZOPA} (XXXX) INS ACQ. This puts the terminal back in service, and
Destination: CSNE start up the session for use.
Module: DFHZSEX, DFHZSKR
DFHZC3464I date time applid termid tranid Node netname XMEOUT Parameters: date, time,applid, termid, tranid, sense,
released by MT Operator/LU Services instance, {1=DFHZSEX, 2=DFHZSKR}
Manager. sense ((instance) Module name: Destination: CSNE
{DFHZSTU})
Explanation: The master terminal operator issued a CEMT
DFHZC3467E date time applid termid tranid Permanent
command to release the logical unit (LU).
insufficient resource. sense ((instance) Module
For the meaning of the sense data, see the explanation on name: {DFHZNAC})
topic “DFHZCxxxx messages” on page 356. Explanation: The PS buffer resource required by load PS is
System action: The LU is closed. Any task associated with not available.
the LU is terminated either abnormally (if the master terminal
operator so desired) or normally.
Module: DFHZSTU
XMEOUT Parameters: date, time,applid, termid, tranid, netname, User response: Look at the CSNE log. A second message
sense, instance, {1=DFHZSTU} with a sense received code of 084C should have been issued.
Destination: CSNE Refer to this message for full details.
Module: DFHZNAC
DFHZC3465E date time applid termid tranid Unexpected XMEOUT Parameters: date, time,applid, termid, tranid, sense,
response received. sense ((instance) Module instance, {1=DFHZNAC}
name: {DFHZRAC | DFHZRLP | Destination: CSNE
DFHZRVX})
Explanation: CICS received a positive response in one of the
DFHZC3468E date time applid termid tranid CLEAR command
following circumstances:
v The response was to data sent with exception response
{DFHZSCX})
v The response was to a command sent with exception
Explanation: An SNA clear command was received by the
response
node. The other end of the session was unable to handle the
v The response was to a send to which a response has already
current requests for some reason, and purged any outstanding
been sent.
messages on the session.
System action: All outstanding send and receive requests are System action: The session is canceled immediately, and any
purged. If a task is attached, it is abnormally terminated with transaction executing on that session is also abnormally
a transaction dump. The node is placed out of service and the terminated and a transaction dump is produced.
TCTTE, RPL, and action flags are logged to CSNE. User response: Check the other end of the session to
User response: Ensure that the application programs running determine why the clear command was sent. It may be due to
concurrently do not alter the TCTTE. Check that the SNA a lack of buffers in the VTAM region attached to the other
flows on the session are valid and that the logical unit is not session.
violating SNA protocols. Module: DFHZSCX
Module: DFHZRVX, DFHZRAC, DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
instance, {1=DFHZRLP, 2=DFHZRVX, 3=DFHZRVX, Destination: CSNE
4=DFHZRVX, 5=DFHZRVX, 6=DFHZRAC, 7=DFHZRAC,
8=DFHZRAC, 9=DFHZRAC, 10=DFHZRAC, 11=DFHZRAC,
12=DFHZRAC} DFHZC3469E date time applid termid tranid Session
Destination: CSNE re-establishment being awaited. sense
((instance) Module name: {DFHZSCX})
Explanation: The secondary LU is being passed to a new
DFHZC3466E date time applid termid tranid Out of session application program via CLSDST(PASS).
during session start up .sense ((instance)
Module name: {DFHZSEX | DFHZSKR}) For the meaning of the sense data, see the explanation on
Explanation: A CICS master terminal command was used to topic “DFHZCxxxx messages” on page 356.
put terminal termid out of service while session startup was System action: If a task is attached, it is abnormally
taking place. terminated with a transaction dump.
For the meaning of the sense data, see the explanation on Module: DFHZSCX
System action: The session is terminated and the TCTTE for XMEOUT Parameters: date, time,applid, termid, tranid, sense,
terminal termid is left out of service. instance, {1=DFHZSCX}
User response: To establish the session for use, the master Destination: CSNE

DFHZC3470E date time applid termid tranid LU session failure DFHZC3474E date time applid termid tranid Virtual route
caused by: {restart/takeover. LU does not deactivated. sense ((instance) Module name:
support ACTLU(ERP). | route extension to {DFHZSCX})
cluster failed. | LU abend, discontact, Explanation: The session has had to be deactivated because
DACTPU or ANS. }sense ((instance) Module of a forced deactivation of the virtual route being used.
name: {DFHZSCX})
Explanation: An LU session has failed because an UNBIND
command has been received.
Possible reasons are: terminated with a transaction dump. Afterwards CICS
v Restart or takeover. LU does not support ACTLU(ERP) attempts to reestablish the session.
v Route extension to cluster failed User response: Determine the cause of the session failure and
v Session failed due to LU abend, disconnect, DACTPU, or attempt to reestablish the session.
ANS. Module: DFHZSCX
User response: Use the symptom string, a VTAM trace, and DFHZC3475E date time applid termid tranid Unrecoverable LU
the dump, if available, to determine the source of the failure. sense ((instance) Module name:
UNBIND before attempting to reestablish the session. {DFHZSCX})
Module: DFHZSCX Explanation: The session has had to be deactivated because
of an abnormal termination of an LU.
XMEOUT Parameters: date, time,applid, termid, tranid,
{1=restart/takeover. LU does not support ACTLU(ERP).,2=route For the meaning of the sense data, see the explanation on
extension to cluster failed., 3=LU abend, discontact, DACTPU or topic “DFHZCxxxx messages” on page 356.
ANS. }, sense,instance, {1=DFHZSCX, 2=DFHZSCX, System action: If a task is attached, it is abnormally
3=DFHZSCX, 4=DFHZSCX} terminated with a transaction dump. Session reinitiation is not
Destination: CSNE attempted.
Module: DFHZSCX
DFHZC3471E date time applid termid tranid Virtual route
inoperative. sense ((instance) Module name: XMEOUT Parameters: date, time,applid, termid, tranid, sense,
{DFHZSCX}) instance, {1=DFHZSCX}
Explanation: The session has been broken because the virtual Destination: CSNE
route it was using has failed.
For the meaning of the sense data, see the explanation on DFHZC3476E date time applid termid tranid Recoverable LU
topic “DFHZCxxxx messages” on page 356. failure. sense ((instance) Module name:
System action: If a task is attached, it is abnormally {DFHZSCX})
terminated with a transaction dump. For APPC sessions, CICS Explanation: The session has had to be deactivated because
attempts to reestablish the failing session. of an abnormal termination of an LU; recovery of the session
User response: None. may be possible.
Module: DFHZSCX
instance, {1=DFHZSCX} System action: If a task is attached, it is abnormally
Destination: CSNE terminated with a transaction dump. CICS attempts to
reinitiate the session.
DFHZC3472E date time applid termid tranid Device end
Module: DFHZSCX
{DFHZSYX}) XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Explanation: Device end was received from a non-SNA instance, {1=DFHZSCX}
VTAM supported 3270 Destination: CSNE
topic “DFHZCxxxx messages” on page 356. DFHZC3477E date time applid termid tranid Cleanup received.
System action: The good morning message is displayed, sense ((instance) Module name: {DFHZSCX})
unless the terminal is associated with an active task. Explanation: The sending LU has reset its half-session before
User response: None. receiving a response from CICS; recovery of the session may
Module: DFHZSYX be possible.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, For the meaning of the sense data, see the explanation on
instance, {1=DFHZSYX} topic “DFHZCxxxx messages” on page 356.
Destination: CSNE System action: If a task is attached, it is abnormally
terminated with a transaction dump. CICS attempts to
reinitiate the session.

User response: None. Module: DFHZRAC, DFHZRVX

Module: DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRAC}
instance, {1=DFHZSCX} Destination: CSNE
Destination: CSNE
DFHZC3482E date time applid tranid Logon from node nodeid

DFHZC3479E date time applid termid tranid Unbind received rejected. Insufficient storage for autoinstall
after session failure detected. sense ((instance) request. sense ((instance) Module name:
Module name: {DFHZSCX}) {DFHZLGX | DFHZSCX})
Explanation: The logical unit in session with CICS has Explanation: A node nodeid, unknown to CICS, attempted to
detected a session failure, and has unbound the session with logon. CICS could not obtain sufficient storage to complete
CICS. autoinstall processing.
System action: The session is terminated, and the transaction System action: CICS rejects the logon request.
using it is abnormally terminated or informed by return code. User response: Retry the logon.
User response: Determine the reason for the session failure Module: DFHZLGX, DFHZSCX
by using Trace. Check the CSNE log for a second error
message associated with DFHZC3479. This message should be XMEOUT Parameters: date, time,applid, tranid, nodeid, sense,
instance, {1=DFHZLGX, 2=DFHZLGX, 3=DFHZSCX,
located immediately after DFHZC3479.
4=DFHZSCX}
Refer to the sense code shown in the associated message. Destination: CSNE
Module: DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, DFHZC3484I date time applid netname is now connected to
instance, {1=DFHZSCX, 2=DFHZSCX} applid. sense ((instance) Module name:
Destination: CSNE {DFHZNSP})
Explanation: By successful execution of an ISSUE PASS
command, a VTAM logical unit whose network name is
DFHZC3480E date time applid termid tranid Session could not
netname has been passed to the VTAM application whose
be started due to insufficient CICS nucleus
VTAM APPLID (netname) is applid.
function - ISC not loaded. sense ((instance)
Module name: {DFHZLGX | DFHZSCX | For the meaning of the sense data, see the explanation on
DFHZSIM}) topic “DFHZCxxxx messages” on page 356.
Explanation: A session initiation has been attempted to an System action: CICS processing continues.
APPC system or terminal. The session cannot be established User response: None.
because the CICS ISC nucleus modules are required. Module: DFHZNSP
For the meaning of the sense data, see the explanation on XMEOUT Parameters: date, time,applid, netname, applid, sense,
topic “DFHZCxxxx messages” on page 356. instance, {1=DFHZNSP}
System action: The session initiation request is rejected. Destination: CSNE
User response: If APPC connections are to be used, ensure
that ISC=NO is not used for CICS initialization.
Module: DFHZSCX, DFHZLGX, DFHZSIM DFHZC3485E date time applid netname A CLSDST Pass
Procedure error occurred at applid. Status byte
XMEOUT Parameters: date, time,applid, termid, tranid, sense, xx Reason byte yy.sense ((instance) Module
instance, {1=DFHZSIM, 2=DFHZSCX, 3=DFHZLGX} name: {DFHZNSP})
Destination: CSNE Explanation: In executing an ISSUE PASS command, CICS
attempted to pass control of a VTAM logical unit whose
network name is netname, to a system whose VTAM APPLID
DFHZC3481E date time applid termid tranid 3270 Data Stream
is applid. VTAM has notified CICS of an error at applid.
protocol error. sense ((instance) Module name:
{DFHZRAC | DFHZRVX}) For the meaning of the sense data, see the explanation on
Explanation: CICS has received zero length data from a topic “DFHZCxxxx messages” on page 356.
device defined in the TCT as a 3270 terminal. This violates the System action: CICS saves the status byte xx and reason byte
protocol for 3270 devices. yy passed by VTAM in the notify request unit. CICS
User response: The reason for the error can be determined by
investigating the status byte xx and reason byte yy given in
System action: CICS cancels the session and any transactions
the message. These bytes are documented in the NSEXIT
attached to the terminal.
routine section of the VTAM Programming manual.
User response: Determine why zero length data was received
Module: DFHZNSP
from a device purporting to be a 3270 terminal, and correct
the error. XMEOUT Parameters: date, time,applid, netname, applid, xx, yy,
sense, instance, {1=DFHZNSP}
The most likely reasons are an incorrect TCT definition for the
Destination: CSNE
terminal, or incorrect programming of a terminal that is
simulating 3270 protocols.

DFHZC3486E date time applid netname The named LU cannot DFHZC3489E date time applid netname The LU is inhibited
be connected for sessions at applid. sense for sessions. sense ((instance) Module name:
((instance) Module name: {DFHZSYX}) {DFHZSYX})
Explanation: In executing an ISSUE PASS command, CICS Explanation: CICS has attempted to acquire a session to the
attempted to pass control of a VTAM logical unit whose logical unit (LU), but VTAM has rejected the request because
network name is netname, to a system whose VTAM APPLID the LU is inhibited for sessions.
is applid. VTAM has notified CICS that applid is currently not
The partner LU could be inhibited because it has issued the
available.
VTAM macro SETLOGON OPTCD=QUIESCE.
System action: Processing continues. topic “DFHZCxxxx messages” on page 356.
System action: The request is rejected and the session is set
into NOINTLOG state to prevent further requests being
Module: DFHZSYX
issued.
XMEOUT Parameters: date, time,applid, netname, applid, sense, User response: After the partner LU has enabled itself, it can
instance, {1=DFHZSYX, 2=DFHZSYX} initiate the session request to CICS. Alternatively, the CICS
Destination: CSNE master terminal operator could reset the NOINTLOG state and
allow CICS to initiate the session request.
Module: DFHZSYX
DFHZC3487E date time applid netname Unable to PASS to
node nodeid. CLSDST PASS is not authorized. XMEOUT Parameters: date, time,applid, netname, sense, instance,
sense ((instance) Module name: {DFHZLEX}) {1=DFHZSYX}
Explanation: In executing an ISSUE PASS command, CICS Destination: CSNE
attempted to pass control of a VTAM logical unit whose
network name is netname. VTAM has notified CICS that CICS
DFHZC3490E date time applid netname Unable to pass to
is not authorized to use this function.
node nodeid. sense ((instance) Module name:
For the meaning of the sense data, see the explanation on {DFHZCLX | DFHZLEX | DFHZSYX})
topic “DFHZCxxxx messages” on page 356. Explanation: In executing an ISSUE PASS command, CICS
System action: CICS continues. attempted to pass control of the named VTAM logical unit to
a system identified as node nodeid. VTAM has notified CICS
CICS may or may not be able to display the applid it was that this request has failed.
being passed. If CICS can display this applid, it appears in the
text of this message. For the meaning of the sense data, see the explanation on
User response: To use the ISSUE PASS command, you must topic “DFHZCxxxx messages” on page 356.
code AUTH=PASS on the VTAM definition of the CICS APPL, System action: A VTAM CLSDST macro is issued to halt
then reactivate the APPL. communication with the node.
Module: DFHZLEX User response: Ensure that the node nodeid is defined and
active to VTAM.
XMEOUT Parameters: date, time,applid, netname, nodeid, sense, Module: DFHZSYX, DFHZLEX, DFHZCLX
instance, {1=DFHZLEX, 2=DFHZLEX}
Destination: CSNE XMEOUT Parameters: date, time,applid, netname, nodeid, sense,
instance, {1=DFHZLEX, 2=DFHZSYX, 3=DFHZCLX}
Destination: CSNE
DFHZC3488E date time applid netname ISC session
connection failure. sense ((instance) Module
name: {DFHZSIX}) DFHZC3492E date time applid tranid Logon for node nodeid
Explanation: A simlogon request to an ISC system was contained invalid NIBUSER token. sense
rejected because the netname was not known. CICS has now ((instance) Module name: {DFHZLGX})
issued the INQUIRE OPTCD=USERVAR command in order to Explanation: DFHZLGX has been driven for SIMLOGON
determine if netname had been defined as a user variable. That with a token that is no longer a valid TCTTE address.
INQUIRE command has been rejected because the user
variable does not exist in the USERVAR table. This may be
because the USERVAR is either not known or invalid, or the
System action: An unexpected condition has occurred during
MODIFY USERVAR command has not been issued to define
SIMLOGON. CICS will continue processing normally.
the user variable.
For the meaning of the sense data, see the explanation on Module: DFHZLGX
XMEOUT Parameters: date, time,applid, tranid, nodeid, sense,
System action: CLSDST is issued to reset the session.
instance, {1=DFHZLGX}
User response: Determine if the netname has been defined
Destination: CSNE
correctly to CICS. If the netname is to be used as a user
variable then determine why the MODIFY USERVAR
command has not been issued to set it.
Module: DFHZSIX
XMEOUT Parameters: date, time,applid, netname, sense, instance,

{1=DFHZSIX}
Destination: CSNE

As terminal termid had no task attached to it at the time of the

DFHZC3493E date time applid termid tranid Invalid device
error, DFHZNAC was unable to cause a transaction abend
type for a print request. sense ((instance)
Module name : {DFHZARQ})
Explanation: A print function was requested on a 3270 The TWAODNTA flag in the DFHZNAC-DFHZNEP
information display system. However, the print function was commarea is set ON and DFHZNAC produces a system dump
unable to find an eligible printer because the function does not for terminal termid instead.
support the device type. System action: An exception trace entry is made in the trace
table at trace point FC73.
topic “DFHZCxxxx messages” on page 356. A system dump is produced unless you have specifically
System action: If no other action is specified in the network suppressed dumps in the dump table.
error program (NEP). the print request is halted. CICS User response: To determine the nature of the problem that
processing continues. caused the dump to be taken, refer to the CSNE log. There
User response: Check that the printers specified for the should be an associated CICS message which will provide
information display system are valid. Valid devices are 3270P, further information.
LUTYPE3, SCSPRINT and 3790. Module: DFHZNAC
Module: DFHZARQ
XMEOUT Parameters: date, time,applid, termid, instance,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, {1=DFHZNAC}
instance, {1=DFHZARQ} Destination: CSNE
Destination: CSNE
DFHZC3497E date time applid Link to module DFHZNEP

DFHZC3494E date time applid termid tranid Request error from DFHZNAC failed because {module
sense ((instance) Module name : {DFHZNAC}) DFHZNEP is not AMODE 31. | module
Explanation: The request unit (RU) received by the secondary DFHZNEP could not be loaded. | module
logical unit (LU) contains a request which terminal termid DFHZNEP could not be autoinstalled. | of an
cannot handle. unexpected error.} ((instance) Module name:
{DFHZNAC})
Explanation: While processing an error for a VTAM terminal,
CICS attempted to link to user-replaceable module DFHZNEP.
System action: All send and receive requests are purged and
The link failed.
transaction tranid is abnormally terminated with a dump.
User response: Check that the TYPETERM specifications for See message DFHZC3437 for the default action or actions
terminal termid are valid. This error could occur if, for taken.
example, QUERY was sent to a nonqueriable 3270 defined System action: The default action or actions set by
with QUERY=COLD|ALL. DFHZNAC are taken.
Module: DFHZSYX User response: The reason for the failure is specified in the
message. Possible solutions are:
v Ensure that DFHZNEP is linked with AMODE 31.
v Ensure that DFHZNEP has the correct name and is
Destination: CSNE
contained in one of the sublibraries of the LIBDEF search
chain for the CICS startup job stream.
DFHZC3495E date time applid Logon occurred for terminal v Ensure that there is a valid entry for DFHZNEP in the PPT,
with netname netname before Notify received and that DFHZNEP can be successfully autoinstalled.
sense ((instance) Module name : {DFHZLGX}) Module: DFHZNAC
Explanation: A terminal with netname netname has logged on
XMEOUT Parameters: date, time,applid, {1=module DFHZNEP is
before a NOTIFY request was received for an outstanding
not AMODE 31., 2=module DFHZNEP could not be loaded.,
CLSDST PASS with CLSDST=NOTIFY.
3=module DFHZNEP could not be autoinstalled., 4=of an
For the meaning of the sense data, see the explanation on unexpected error.}, instance, {1=DFHZNAC}
System action: CICS processing continues. Any subsequent
NOTIFY requests for the terminal identified will be ignored.
DFHZC3498E date time applid Abend abcode has occurred in
User response: It is recommended that any user processing
module DFHZNEP. ((instance) Module name:
for CLSDST PASS messages incorporates this message.
{DFHZNAC})
Module: DFHZLGX
Explanation: While processing an error for a VTAM terminal,
XMEOUT Parameters: date, time,applid, netname, sense, instance, user-replaceable module DFHZNEP was linked and the
{1=DFHZLGX} program abended with abend code abcode. See message
Destination: CSNE DFHZC3437 for the default action or actions that are taken.
System action: Control is passed back to the calling module,
DFHZNAC. DFHZNAC reinstates the default actions set
DFHZC3496E date time applid System dump has been taken before DFHZNEP was called. The actions are then taken.
for terminal termid ((instance) Module name: User response: Refer to abend code abcode in “Transaction
{DFHZNAC}) Abend Codes (CICS Transaction Server for VSE/ESA)” on
Explanation: Terminal termid has been found to be in error page 453 for details of the original error. Follow the user
by terminal control. response given in the abend code to solve the problem.
Module: DFHZNAC

XMEOUT Parameters: date, time,applid, abcode, instance, If the "CNOS failed" option is displayed, the CNOS command
{1=DFHZNAC} could not be implemented because the modename lock was
Destination: CSNE still held on the remote system when a second CNOS
command was sent by this CICS, as the CNOS race winner,
following a previous CNOS race condition.
DFHZC3499E date time applid Getmain failure in module
DFHmodname with return code X'return_code'
If a modename of ALL is produced, it has been set internally
while attempting to process message
by CICS and all of the modegroups for this connection will be
DFHZCmessage_number. sense ((instance)
affected by the CNOS command.
Module name: {DFHZATA | DFHZLEX |
System action: The negotiated values are applied.
DFHZLGX | DFHZRAC | DFHZSCX |
DFHZSHU | DFHZSYX | DFHZTPX})
Module: DFHZGCN
Explanation: An error has been detected by module modname.
The OS/390 GETMAIN request by this module has failed with XMEOUT Parameters: date, time,applid, termid, tranid, {1=sent
return code X'return_code', and as a result, the diagnostic to, 2=received from}, netname, sysid, modename, n1,n2, {1=race
information relating to the original error has not been saved detected, 2=successful, 3=values amended, 4=modename not
and cannot be processed by DFHZNAC. recognized,5=modename closed, 6=CNOS failed},
instance,{1=DFHZGCN}
The only information available for diagnosis of the error is
Destination: CSNE
message_number which is the number of the message that
would have been issued had the OS/390 GETMAIN request
not failed. DFHZC4901I date time applid termid tranid Node netname
System sysid Modename modename,
Negotiated values: Max=n1, Win=n2.
((instance) Module name: {DFHZGCN})
Explanation:
User response: Refer to message message_number for further
v modename is the modename,
guidance.
v n1 is the maximum session count,
Refer to "OS/390 API Return Codes" in section v n2 is the maximum source contention winner sessions.
This message follows message DFHZC4900 when the
Messages and Codes - Volume 1 for the meaning of the OS/390
maximum session count (n1) and the maximum source
GETMAIN return code.
contention winner sessions (n2) have been renegotiated.
Module: DFHZATA, DFHZLGX, DFHZRAC, DFHZSCX,
DFHZSHU, DFHZTPX, DFHZLEX, DFHZSYX
If a modename of ALL is produced, it has been set internally
XMEOUT Parameters: date, time,applid, modname, by CICS and all of the modegroups for this connection will be
X'return_code',message_number, sense, instance,{1=DFHZLEX, affected by the CNOS command.
2=DFHZSHU, 3=DFHZSCX, 4=DFHZSCX, 5=DFHZSYX, System action: The negotiated values are applied.
6=DFHZSYX, 7=DFHZTPX, 8=DFHZRAC, 9=DFHZRAC, User response: None.
10=DFHZATA, 11=DFHZLGX, 12=DFHZLGX} Module: DFHZGCN
Destination: CSNE
sysid, modename, n1,n2, instance, {1=DFHZGCN}
DFHZC4900I date time applid termid tranid CNOS {sent to | Destination: CSNE
received from} Node netname System sysid
Modename modename, Max = n1, Win=n2,
{race detected | successful | values amended DFHZC4902E date time applid termid tranid Attach FMH or
| modename not recognized | modename subfield length error. sense ((instance) Module
closed | CNOS failed}. ((instance) Module name: {DFHZATT})
name: {DFHZGCN}) Explanation: A request to attach a task has been received
Explanation: A CHANGE-NUMBER-OF-SESSIONS command across an APPC link. However, there is an error in the
has been sent or received. The inserts are identified as follows: function management header (FMH) length or in the length of
v sysid is the system identifier. one of the subfields. As a result, CICS is unable to determine
v modename is the modename. which task to attach.
v n1 is the maximum session count. For the meaning of the sense data, see the explanation on
v n2 is the maximum source contention winner sessions. topic “DFHZCxxxx messages” on page 356.
System action: The task is abnormally terminated with a
If the "values amended" option is displayed, the values of the dump.
n1 (maximum session count) and n2 (maximum source User response: The remote APPC system is sending an
contention winner sessions) have been renegotiated by the invalid attach header (FMH type 5). Use the supplied dump to
target system. determine the error and investigate the cause at the remote
system.
If the "race detected" option is displayed, the CNOS command Module: DFHZATT
could not be implemented because the modename modename
was already locked for a CNOS command from the other
instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT,
system.
4=DFHZATT, 5=DFHZATT, 6=DFHZATT, 7=DFHZATT}
Destination: CSNE

If this message occurs during normal system execution,

DFHZC4903E date time applid termid tranid Attach FMH not
investigate any transactions running on the session at the time
found. sense ((instance) Module name:
of failure because the error can be caused by using both the
{DFHZATT})
LAST and WAIT options on an EXEC CICS SEND command
Explanation: A request to attach a task has been received
in an APPC DTP application. This combination of parameters
across an APPC link. However, no APPC attach header has
is not recommended. If this is not the cause of the problem,
been found at the start of the input data stream.
For the meaning of the sense data, see the explanation on CICS Problem Determination Guide for guidance on how to
topic “DFHZCxxxx messages” on page 356. proceed.
System action: The task is abnormally terminated with a Module: DFHZRAC, DFHZRLP, DFHZSDL, DFHZSLX,
dump. DFHZERH, DFHZDET
User response: The remote APPC system is failing to send a
valid attach header (FMH type 5). Use the supplied dump to
instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP,
determine the error and investigate the cause at the remote
4=DFHZRLP, 5=DFHZRLP, 6=DFHZRLP, 7=DFHZRLP,
system.
8=DFHZDET, 9=DFHZERH, 10=DFHZSDL, 11=DFHZSDL,
Module: DFHZATT
12=DFHZSLX, 13=DFHZSLX, 14=DFHZSLX, 15=DFHZSLX,
XMEOUT Parameters: date, time,applid, termid, tranid, sense, 16=DFHZSLX, 17=DFHZSLX, 18=DFHZSLX, 19=DFHZSLX,
instance, {1=DFHZATT, 2=DFHZATT} 20=DFHZSLX, 21=DFHZSLX, 22=DFHZRAC, 23=DFHZRAC,
Destination: CSNE 24=DFHZRAC, 25=DFHZRAC, 26=DFHZRAC, 27=DFHZRAC,
28=DFHZRAC}
Destination: CSNE
DFHZC4904E date time applid termid tranid Bracket FSM
error. sense ((instance) Module name:
{DFHZRAC | DFHZRLP | DFHZSDL | DFHZC4906E date time applid termid tranid Contention FSM
DFHZSLX}) error. sense ((instance) Module name:
Explanation: The bracket finite state machine (FSM) has {DFHZDET | DFHZRAC | DFHZRLP})
reported an error in the use of APPC bracket protocols. Explanation: The contention finite state machine (FSM) has
reported an error in the use of APPC contention protocols.
System action: The task is abnormally terminated with a topic “DFHZCxxxx messages” on page 356.
dump. System action: The task is abnormally terminated with a
dump.
symptom string for this problem. Message DFHME0116 is normally produced containing the
User response: If this message occurs after a persistent symptom string for this problem.
sessions restart, look for associated messages for more User response: If this message occurs after a persistent
guidance. The problem might be temporary. sessions restart, look for associated messages for more
guidance. The problem might be temporary.
If this message occurs during normal system execution, you
will need further assistance from IBM. See Part 4 of the CICS If this message occurs during normal system execution, you
Problem Determination Guide for guidance on how to proceed. will need further assistance from IBM. See Part 4 of the CICS
Module: DFHZRAC, DFHZRLP, DFHZSDL, DFHZSLX Problem Determination Guide for guidance on how to proceed.
Module: DFHZRAC, DFHZRLP, DFHZDET DFHZCC
instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, XMEOUT Parameters: date, time,applid, termid, tranid, sense,
4=DFHZRLP, 5=DFHZSDL, 6=DFHZSDL, 7=DFHZSLX, instance, {1=DFHZDET, 2=DFHZRAC, 3=DFHZRAC,
8=DFHZSLX, 9=DFHZSLX, 10=DFHZSLX, 11=DFHZSLX, 4=DFHZRAC, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC,
12=DFHZSLX, 13=DFHZRAC, 14=DFHZRAC, 15=DFHZRAC} 8=DFHZRAC, 9=DFHZRAC, 10=DFHZRAC, 11=DFHZRLP,
Destination: CSNE 12=DFHZRAC, 13=DFHZRAC, 14=DFHZRAC, 15=DFHZRAC,
16=DFHZRAC}
Destination: CSNE
DFHZC4905E date time applid termid tranid Chain FSM error.
sense ((instance) Module name: {DFHZDET |
DFHZERH | DFHZRAC | DFHZRLP | DFHZC4907E date time applid termid tranid Invalid request to
DFHZSDL | DFHZSLX}) send data routine. sense ((instance) Module
Explanation: The chain finite state machine (FSM) has name: {DFHZSDL})
reported an error in the use of APPC chaining protocols. Explanation: DFHZSDL was entered, but no valid request
was passed to it.
System action: The task is abnormally terminated with a topic “DFHZCxxxx messages” on page 356.
dump. System action: The task is abnormally terminated with a
dump.
symptom string for this problem. Message DFHME0116 is normally produced containing the
User response: If this message occurs after a persistent symptom string for this problem.
sessions restart, look for associated messages for more User response: You need further assistance from IBM to
guidance. The problem might be temporary. resolve this problem. See Part 4 of the CICS Problem

Module: DFHZSDL XMEOUT Parameters: date, time,applid, termid, tranid, sense,

instance, {1=DFHZRLP}
instance, {1=DFHZSDL, 2=DFHZSDL, 3=DFHZSDL,
4=DFHZSDL, 5=DFHZSDL}
Destination: CSNE DFHZC4912E date time applid termid tranid BID received with
invalid DFC indicators. sense ((instance)
Module name: {DFHZRAC | DFHZRLP})
DFHZC4909E date time applid termid tranid Invalid request to
Explanation: BID with data received, but not OIC.
receive data routine. sense ((instance) Module
name: {DFHZRVL}) For the meaning of the sense data, see the explanation on
Explanation: DFHZRVL was entered, but no valid request topic “DFHZCxxxx messages” on page 356.
was passed. System action: The task is abnormally terminated.
User response: Incorrect flows have been received on an
APPC session. The CICS trace gives further details of the flow.
It may help to run a VTAM trace TYPE=IO/BUF and repeat
the error to obtain complete details of the line flow.
dump.
Module: DFHZRAC, DFHZRLP
instance, {1=DFHZRLP, 2=DFHZRAC, 3=DFHZRAC}
Destination: CSNE
Module: DFHZRVL DFHZC4913E date time applid termid tranid BID with data
received with invalid DFC indicators. sense
((instance) Module name: {DFHZRLP})
instance, {1=DFHZRVL}
Explanation: A BID with data was received in an invalid
Destination: CSNE
state for rejection.

DFHZC4910E date time applid termid tranid Receive buffer too
small. sense ((instance) Module name:
System action: The task is abnormally terminated.
{DFHZRVL})
Explanation: The receive buffer passed to DFHRVL is too
small to accommodate a maximum size request unit.
For the meaning of the sense data, see the explanation on the error to obtain complete details of the line flow.
topic “DFHZCxxxx messages” on page 356. Module: DFHZRLP
System action: The task will be abnormally terminated with
a dump.
Message DFHME0116 is normally produced containing the 4=DFHZRLP}
symptom string for this problem. Destination: CSNE
DFHZC4914E date time applid termid tranid Data length
exceed max RU size. sense ((instance) Module
Module: DFHZRVL
name: {DFHZRLP})
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Explanation: The record length received exceeds the buffer
instance, {1=DFHZRVL, 2=DFHZRVL, 3=DFHZRVL, length.
4=DFHZRVL}
Destination: CSNE
DFHZC4911E date time applid termid tranid LU6.2 exception User response: Incorrect flows have been received on an
response received. sense ((instance) Module APPC session. The CICS trace gives further details of the flow.
name: {DFHZRLP}) It may help to run a VTAM trace TYPE=IO/BUF and repeat
Explanation: A non-process-level exception response has the error to obtain complete details of the line flow.
been received. Module: DFHZRLP
For the meaning of the sense data, see the explanation on XMEOUT Parameters: date, time,applid, termid, tranid, sense,
topic “DFHZCxxxx messages” on page 356. instance, {1=DFHZRLP}
System action: The task is abnormally terminated with a Destination: CSNE
dump.
DFHZC4915E date time applid termid tranid EOC received
with invalid DFC indicators. sense ((instance)
Try to recreate the error by running a VTAM trace
Module name: {DFHZRLP})
TYPE=IO/BUF to obtain complete details of the line flow.
Explanation: An end chain was received with invalid DFC
Module: DFHZRLP
indicators.

For the meaning of the sense data, see the explanation on error to obtain complete details of the line flow.
topic “DFHZCxxxx messages” on page 356. Module: DFHZRLP
4=DFHZRLP, 5=DFHZRLP}
Destination: CSNE
the error to obtain complete details of the line flow.
Module: DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, DFHZC4919E date time applid termid tranid Invalid indicators
instance, {1=DFHZRLP} received. sense ((instance) Module name:
Destination: CSNE {DFHZARER | DFHZARL})
Explanation: An indicator other than CD, CEB, RQD2, or
error response has been received.
DFHZC4916E date time applid termid tranid Send response
failed. sense ((instance) Module name: For the meaning of the sense data, see the explanation on
{DFHZRLP}) topic “DFHZCxxxx messages” on page 356.
Explanation: A response, sent to acknowledge successful System action: The task is abnormally terminated with a
receipt of data, was rejected by VTAM. dump.
For the meaning of the sense data, see the explanation on Message DFHME0116 is normally produced containing the
topic “DFHZCxxxx messages” on page 356. symptom string for this problem.
System action: The task is abnormally terminated with a User response: You need further assistance from IBM to
dump. resolve this problem. See Part 4 of the CICS Problem
Message DFHME0116 is normally produced containing the Module: DFHZARL, DFHZARER, DFHZARL
User response: You need further assistance from IBM to XMEOUT Parameters: date, time,applid, termid, tranid, sense,
resolve this problem. See Part 4 of the CICS Problem instance, {1=DFHZARL, 2=DFHZARL, 3=DFHZARL,
Determination Guide for guidance on how to proceed. 4=DFHZARL, 5=DFHZARER}
Module: DFHZRLP Destination: CSNE

instance, {1=DFHZRLP} DFHZC4920E date time applid termid tranid Invalid data
Destination: CSNE received. sense ((instance) Module name:
{DFHZARER | DFHZARL | DFHZERH})
Explanation: Data received from the remote system or
DFHZC4917E date time applid termid tranid BIS received with terminal is not in correct generalized data stream (GDS)
invalid DFC indicators. sense ((instance) format.
Module name: {DFHZRLP})
Explanation: Bracket initiation stopped (BIS) received with For the meaning of the sense data, see the explanation on
invalid DFC flags. topic “DFHZCxxxx messages” on page 356.
For the meaning of the sense data, see the explanation on dump.
System action: The task is abnormally terminated. Message DFHME0116 is normally produced containing the
User response: Incorrect flows have been received on an symptom string for this problem.
APPC session. The CICS trace will give further details of the User response: You need further assistance from IBM to
flow. It may help to run a VTAM trace TYPE=IO/BUF and resolve this problem. See Part 4 of the CICS Problem
repeat the error to obtain complete details of the line flow. Determination Guide for guidance on how to proceed.
Module: DFHZRLP Module: DFHZARL, DFHZARER, DFHZERH
XMEOUT Parameters: date, time,applid, termid, tranid, sense, XMEOUT Parameters: date, time,applid, termid, tranid, sense,
instance, {1=DFHZRLP, 2=DFHZRLP} instance, {1=DFHZERH, 2=DFHZERH, 3=DFHZERH,
Destination: CSNE 4=DFHZERH, 5=DFHZERH, 6=DFHZERH, 7=DFHZARL,
8=DFHZARL, 9=DFHZARL, 10=DFHZARER, 11=DFHZARER,
12=DFHZARER}
DFHZC4918E date time applid termid tranid Unexpected Destination: CSNE
response received. sense ((instance) Module
name: {DFHZRLP})
DFHZC4921E date time applid sysid LU services manager
Explanation: An unexpected response was received that was
failure. R15 =X'xxxxx' R0 =X'yyyyy'
either a positive response to data of a previous bracket, or a
Explanation: An error situation has been detected during the
response to a command that cannot be accepted when the
operation of the LU services manager transaction program
logical unit is in "continue specific" mode.
(DFHLUP).
Registers 15 and 0 are set to indicate the nature of the error as
shown below:
User response: Incorrect flows have been received on a APPC Register 15 = X’0’ Task invalidly started ...
session. The CICS trace will give further details of the flow. It Register 0 = X’3’ ... via a perm transid.
may help to run a VTAM trace TYPE=IO/BUF and repeat the Register 0 = X’4’ ... by a TD trigger.

Register 0 = X’5’ ... without data. this message to the connected logical unit at the nonfailing
Register 0 = >X’6’ ... or is out of range of end of the conversation.
a valid start code for
this service. The application in system sysid abnormally terminates with an
abend.
Register 15 = X’4’ Call code did not match a User response: Correct the application program. To find the
supported function (1-5). command in error, use the state diagrams in the CICS
Register 0 = call code Intercommunication Guide.
Register 15 = X’8’ Invalid parameters passed Module: DFHZARL
for this function. XMEOUT Parameters: date, time,applid, termid, tranid, sysid
Register 0 = keyword #
Destination: CSMT
Register 15 = X’0C’ Function-specific checks
failed for this keyword.
DFHZC4924E date time applid termid tranid Bind security
Register 0 = keyword #
password missing or invalid. sense ((instance)
Register 15 = X’10’ No input data supplied. Module name: {DFHZOPX | DFHZSCX})
Register 0 = ¬0 The IC_GET for the TS START Explanation: Bind-time security data sent to CICS by its
data failed. partner LU is missing or invalid. CICS's password for the
Register 0 = X’0’ The LUTYPE6.2 RECEIVE partner LU system differs from the partner's password for
returned data CICS. This can be caused by an attempt to sign on to CICS by
length=0. an unauthorized user.
Register 15 = X’14’ The GDS-ID is not for XLN. For the meaning of the sense data, see the explanation on
Register 0 = GDS-ID topic “DFHZCxxxx messages” on page 356.
System action: The task is allowed to complete but the System action: The bind is rejected.
required function is not executed. User response: Check that an unauthorized user has not tried
Message DFHME0116 is normally produced containing the to log on to CICS. Ensure that the unsuccessful connection is
symptom string for this problem. correctly defined to CICS (using RDO or the DFHTCT macro)
User response: If one of the errors mentioned above has and to its partner LU system. Ensure that the security
occurred, try to discover the reason for the failure. If you fail requirements are equal at both partners, that is, both have
in this, you will need further assistance from IBM. See Part 4 security off, or both have security on. A mismatch is one cause
of the CICS Problem Determination Guide for guidance on how of this message.
to proceed. Module: DFHZSCX, DFHZOPX
Module: DFHLUP XMEOUT Parameters: date, time,applid, termid, tranid, sense,
XMEOUT Parameters: date, time,applid, sysid, X'xxxxx', X'yyyyy' instance, {1=DFHZOPX, 2=DFHZSCX, 3=DFHZSCX,
Destination: CSNE 4=DFHZSCX, 5=DFHZSCX, 6=DFHZOPX, 7=DFHZOPX,
8=DFHZOPX, 9=DFHZOPX, 10=DFHZSCX}
Destination: CSNE
DFHZC4922E date time applid termid tranid Single session
shutdown with DRAIN=CLOSE. sense
((instance) Module name: {DFHZERH | DFHZC4925E date time applid termid tranid Inconsistent
DFHZGDA | DFHZRAC}) attach security required. sense ((instance)
Explanation: The connected logical unit has sent Bracket Module name: {DFHZOPN | DFHZOPX})
Initiation Stopped (BIS) and can accept no more work. Explanation: This message can be issued for any of the
reasons listed below.
For the meaning of the sense data, see the explanation on 1. CICS has received a bind request specifying attach time
topic “DFHZCxxxx messages” on page 356. security requirements different from those specified in the
System action: If a conversation was active, it is treated as first bind.
though rollback had occurred on it for full syncpoint 2. CICS has received a bind requesting persistent verification.
(syncpoint level 2), or as session failure for confirm-level 3. CICS has received a bind which does not include an SNA
syncpoint (syncpoint level 1). functional management header (FMH12).
If there was no conversation, it is treated as a BID failure (as
for 0813 sense code). For the meaning of the sense data, see the explanation on
User response: None. topic “DFHZCxxxx messages” on page 356.
Module: DFHZRAC, DFHZGDA, DFHZERH System action: CICS rejects the bind.
User response: CICS does NOT allow subsequent binds to
XMEOUT Parameters: date, time,applid, termid, tranid, sense, specify different security requirements from the first bind. It
instance, {1=DFHZRAC, 2=DFHZGDA, 3=DFHZERH} will not support persistent verification on input either.
Destination: CSNE
Where applicable, alter your applications to meet these
requirements.
DFHZC4923I date time applid termid tranid Conversation Module: DFHZOPX, DFHZOPN
abnormally terminated by transaction end in
system sysid
instance, {1=DFHZOPX, 2=DFHZOPN, 3=DFHZOPN,
Explanation: Transaction tranid, engaged in an SNA session
4=DFHZOPX}
with a CICS system, issued a command that was inconsistent
Destination: CSNE
with the transaction's current state in the conversation.
System action: The conversation terminates and CICS sends

DFHZC4926E • DFHZC4929
X'04' The BIND supplied does not match the TCTTE –

DFHZC4926E date time applid termid tranid Bind security
detected by DFHZBANS.
encryption error. sense ((instance) Module
X'08' The BIND supplied is unsupported – detected by
name: {DFHZEV1 | DFHZEV2})
DFHZBANV.
Explanation: CICS detected an error while verifying an
X'0C' The BIND supplied is invalid – detected by
encrypted bind security password.
DFHZBANV.
topic “DFHZCxxxx messages” on page 356. The reason code for a response of X'04' is as follows:
System action: CICS rejects the bind. X'1B' Unsupported TCTTE type or not VTAM
User response: Investigate the CSNE and CSMT logs. X'1C' No NIB descriptor chained from TCTTE
X'1D' No BMS extension chained from TCTTE
Find out whether an unauthorized user tried to log on to
X'1E' Same as for reason code X'1D'
CICS, or whether an authorized user entered his password
X'1F' LU6.2 BIND, but TCTTE does not match.
incorrectly.
Module: DFHZEV1, DFHZEV2
The reason code for a response of X'08' or X'0C' is as follows:
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Reason Invalid Explanation
instance, {1=DFHZEV1, 2=DFHZEV2, 3=DFHZEV1} Hex byte
Destination: CSNE 1 3 Should be hex 02, 03, 04 or 07
2-8 4|5|6|7 Invalid for this FM profile
9 2 Should be hex 00, 02, 03, 04,
DFHZC4927E date time applid termid tranid Bind FMH 07, 13 or 14
response error. sense ((instance) Module name: 0A,0D,10 1 Invalid for LUTYPE 1,2 or 3
{DFHZRAC}) - must be hex 01
Explanation: CICS received a bind with bind security 0B 4|5|6|7 Invalid for LUTYPE 1
without an FMH12. 0C 22 Invalid for LUTYPE 1
0E 4|5|6|7 Invalid for LUTYPE 2
For the meaning of the sense data, see the explanation on 0F 24 Invalid for LUTYPE 2 should
topic “DFHZCxxxx messages” on page 356. be hex 00, 01, 02, 03, 7E,
System action: CICS rejects the bind. or 7F
11 4|5|6|7 Invalid for LUTYPE 3
Message DFHME0116 is normally produced containing the 12 24 Invalid for LUTYPE 3 should
symptom string for this problem. be hex 00, 01,
User response: This is an error either in CICS or in SNA. 02, 03, 7E, or 7F
13 16 Invalid for LUTYPE 6.2
Keep the CSNE and CSMT logs. You need further assistance 14 23 Invalid for LUTYPE 6.2
from IBM to resolve this problem. See Part 4 of the CICS 15-18 24 Invalid for LUTYPE 6.2
Problem Determination Guide for guidance on how to proceed. 19 15 Should be hex 00 or 02
Module: DFHZRAC 1A 14 Should be hex 00, 01, 02, 03, 06
1B and User Data The reason code matches the byte
XMEOUT Parameters: date, time,applid, termid, tranid, sense, over position in the BIND for the
instance, {1=DFHZRAC, 2=DFHZRAC, 3=DFHZRAC, error detected.
4=DFHZRAC} These can be:
Destination: CSNE - Session ID length unsupported
- should be 3 to 11
- PLU/SLU name length unsupported
DFHZC4928E date time applid termid tranid Bind security - should be 2 to 19
GETMAIN of a TIOA failed. sense ((instance) - PLU/SLU defined twice
Module name: {DFHZEV1}) - Length invalid
- Session qualifier pairs have
Explanation: CICS required a TIOA work area for bind
inconsistent lengths.
security validation, but the GETMAIN failed because
System action: CICS rejects the logon request. The BIND
insufficient storage was available.
being validated is printed with this message.
System action: CICS rejects the bind.
User response: Use the response and reason codes and the
User response: Consider increasing the size of the CICS
printed BIND, together with the VTAM definition of the BIND
region or reducing the number of concurrent CICS tasks (MXT
for the relevant LOGMODE to determine the reason for the
system initialization parameter).
rejection.
Module: DFHZEV1
Either change the logmode or use a different one that matches
CICS requirements.
instance, {1=DFHZEV1}
Module: DFHZOPN
Destination: CSNE
XMEOUT Parameters: date, time, applid, termid, tranid, logmode,
X'response', X'reason', instance, {1=DFHZOPN}
DFHZC4929 date time applid termid tranid Invalid or Destination: CSMT
unsupported BIND for logmode logmode.
Response X'response', Reason X'reason'
((instance) Module: {DFHZOPN})
Explanation: CICS has detected an error while validating the
BIND supplied by VTAM for a CICS typeterm definition
defined with LOGMODE=0 or LOGMODE=logmode.
The response code indicates:


DFHZC4930E date time applid termid tranid Session unbound
instance, {1=DFHZSUP}
following read timeout. sense ((instance)
Destination: CSNE
Module name: {DFHZARER | DFHZARL})
Explanation: A READ timeout has occurred on the SNA link.
SNA unbinds the session and CICS returns control to the DFHZC4933E date time applid termid tranid Invalid DBA
application program. This allows the program to override the requested. sense ((instance) Module name:
system action (for example, the program could free the APPC {DFHZSUP})
session). Explanation: A request to attach a task has been received
across an APPC link. However, there is an error in the DBA
field.
System action: CICS abends the task abnormally with a For the meaning of the sense data, see the explanation on
dump. topic “DFHZCxxxx messages” on page 356.
User response: This is probably a network problem caused System action: The task abends and a dump is produced.
by a high level of network traffic. To avoid this problem, The session is unbound.
increase the Read Timeout (RTIMOUT) to a sufficiently high User response: The remote APPC system sends an invalid
value to compensate for the level of network traffic. attach header (FMH Type 5). Use the supplied dump to
Alternatively, this problem may have arisen simply because determine the error and investigate the cause at the remote
the partner application failed to respond due to a system.
programming error. If this is the case, correct the partner Module: DFHZSUP
application and retry the request.
Module: DFHZARL, DFHZARER. XMEOUT Parameters: date, time,applid, termid, tranid, sense,
instance, {1=DFHZARL, 2=DFHZARL, 3=DFHZARER}
Destination: CSNE
DFHZC4934E date time applid termid tranid Invalid syncpoint
level requested. sense ((instance) Module
DFHZC4931E date time applid termid tranid VTAM detected name: {DFHZSUP})
bad logmode name. sense ((instance) Module Explanation: A request to attach a task has been received
name: {DFHZLEX}) across an APPC link. However, the synchronization level
Explanation: Either a MODENAME passed to VTAM during requested is invalid.
an attempt to bind an APPC session is not known to VTAM,
or the logmode name of a VTAM 3270-type terminal is not For the meaning of the sense data, see the explanation on
valid. topic “DFHZCxxxx messages” on page 356.
System action: The task abends and a dump is produced.
For the meaning of the sense data, see the explanation on User response: The remote APPC system sends an invalid
topic “DFHZCxxxx messages” on page 356. attach header (FMH Type 5). Use the supplied dump to
System action: CICS places the session permanently out of determine the error and investigate the cause at the remote
service and for APPC, the mode entry is flagged unusable. system.
User response: Either redefine the sessions using a
MODENAME that is known to VTAM, or add the Check the sync level in the ATTACH header against that in
MODENAME to the VTAM LOGMODE table. Alternatively, if the BIND.
the logmode name specified for a VTAM terminal is invalid, Module: DFHZSUP
redefine the terminal entry using the correct name.
Module: DFHZLEX
instance, {1=DFHZLEX}
Destination: CSNE
DFHZC4935E date time applid termid tranid Invalid UOWID
supplied. sense ((instance) Module name:
DFHZC4932E date time applid termid tranid Invalid {DFHZSUP})
conversation type requested. sense ((instance) Explanation: A request to attach a task has been received
Module name: {DFHZSUP}) across an APPC link and either the unit of work ID is invalid,
Explanation: A request to attach a task has been received or no UOWID was received when the sync point level
across an APPC link. However, there is an error in the required it.
conversation type field. It must be TYPE=MAPPED or
TYPE=UNMAPPED.
For the meaning of the sense data, see the explanation on System action: The task abends and a dump is produced.
topic “DFHZCxxxx messages” on page 356. The session is unbound.
System action: The task is abended and a dump is produced. User response: The remote APPC system sends an invalid
The session is unbound. attach header (FMH Type 5). Use the supplied dump to
User response: The remote APPC system sends an invalid determine the error and investigate the cause at the remote
attach header (FMH Type 5). Use the supplied dump to system.
determine the error and investigate the cause at the remote Module: DFHZSUP
system.
Module: DFHZSUP
instance, {1=DFHZSUP, 2=DFHZSUP, 3=DFHZSUP,

4=DFHZSUP, 5=DFHZSUP, 6=DFHZSUP}

DFHZC4938E date time applid SAF request for LU6.2 bind
Destination: CSNE
has failed with ESM return code RF= X'rf'
and reason code R0= X'r0' sense ((instance)
DFHZC4936E date time applid termid tranid Attach FMH or Module name: {DFHZEV1 | DFHZEV2 |
subfield length error. sense ((instance) Module DFHZOPN})
name: {DFHZSUP}) Explanation: The external security manager (ESM) was
Explanation: A request to attach a task has been received attempting to process a security authorization facility (SAF)
across an APPC link. However, there is an error in the FMH request. Processing has failed with return code RF=X'rf' and
length or in the length of one of the sub-fields. This results in reason code R0=X'r0'.
CICS being unable to determine which task to attach.
The instance instance is one of the following: topic “DFHZCxxxx messages” on page 356.
1 The FMH Length is not equal to the length of the System action: CICS rejects the bind.
fixed length portion + the length of all the sub User response: For the meaning of the response and reason
fields. codes in the message see "BSM Return Codes" in section
2 The Conversation Correlator length within the FMH "VSE/Advanced Functions Codes & SVC Errors" of z/VSE
is greater than 8. Messages and Codes - Volume 1.
Module: DFHZEV1, DFHZEV2, DFHZOPN
For the meaning of the sense data, see the explanation on XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense,
topic “DFHZCxxxx messages” on page 356. instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,
System action: The task abends and a dump is produced. 4=DFHZEV2}
User response: The remote APPC system sends an invalid Destination: CSNE
attach header (FMH Type 5). Use the supplied dump to
determine the error and investigate the cause at the remote
system. DFHZC4939E date time applid Extraction of LU6.2 security
Module: DFHZSUP data has failed with ESM returncode RF=
X'rf' and reason code R0= X'r0' sense ((instance)
XMEOUT Parameters: date, time,applid, termid, tranid, sense, Module name: {DFHZEV1 | DFHZEV2 |
instance, {1=DFHZSUP, 2=DFHZSUP} DFHZOPN})
Destination: CSNE Explanation: A request to extract APPC bind-time security
information has failed with return code RF=X'rf' and reason
DFHZC4937E date time applid SAF request for LU6.2 bind code R0=X'r0'. The profile information which was requested
has been rejected. Return Codes from the had not been previously defined to the external security
Security Manager are: RF= X'rf' and R0= X'r0' manager (ESM).
sense ((instance) Module name: {DFHZEV1 | For the meaning of the sense data, see the explanation on
DFHZEV2 | DFHZOPN}) topic “DFHZCxxxx messages” on page 356.
Explanation: A security authorization facility (SAF) request to System action: CICS rejects the bind.
extract APPC bind-time security information from the external User response: Check the profiles defined to the ESM. Create
security manager (ESM) has been rejected with return code the missing APPC profile entry.
RF=X'rf'. and R0=X'r0'.
For the meaning of the response and reason codes in the
This is due either to the ESM being inactive or to the message see "BSM Return Codes" in section "VSE/Advanced
appropriate APPC profile not being defined to the ESM. Functions Codes & SVC Errors" of z/VSE Messages and Codes -
For the meaning of the sense data, see the explanation on Volume 1.
topic “DFHZCxxxx messages” on page 356. Module: DFHZEV1, DFHZEV2, DFHZOPN
System action: CICS rejects the bind. XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense,
User response: For the meaning of the response and reason instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,
codes in the message see "BSM Return Codes" in section 4=DFHZEV2}
"VSE/Advanced Functions Codes & SVC Errors" of z/VSE Destination: CSNE
If the appropriate APPC profile had not been defined to the DFHZC4940E date time applid Bind time failure. No session
ESM, define the profile, perform a CICS security rebuild and key found in LU6.2 profile. sense ((instance)
then attempt to reestablish the APPC connection. Module name: {DFHZEV1 | DFHZEV2 |
Module: DFHZEV1, DFHZEV2, DFHZOPN DFHZOPN})
XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense, Explanation: APPC bind-time validation has failed. No
instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZOPN, session key has been found in the requested APPC profile
4=DFHZOPN, 5=DFHZOPN, 6=DFHZOPN, 7=DFHZOPN, information. When bind-time security has been defined
8=DFHZOPN, 9=DFHZEV1, 10=DFHZEV1, 11=DFHZEV1, between two logical units (LUs), a valid session key must
12=DFHZEV1, 13=DFHZEV2, 14=DFHZEV2, 15=DFHZEV2, have been defined for the encryption process. A null session
16=DFHZEV2} key (that is, when no key is defined) is regarded as an error.
Destination: CSNE For the meaning of the sense data, see the explanation on
User response: Check the profiles defined to the external
security manager (ESM). Create a valid session key for the

appropriate APPC profile entry. will need further assistance from IBM. See Part 4 of the CICS
For the meaning of the response and reason codes in the Module: DFHZSDL
message see "BSM Return Codes" in section "VSE/Advanced
Functions Codes & SVC Errors" of z/VSE Messages and Codes - XMEOUT Parameters: date, time,applid, termid, tranid, sense,
Volume 1. instance, {1=DFHZSDL}
Module: DFHZEV1, DFHZEV2, DFHZOPN Destination: CSNE
XMEOUT Parameters: date, time,applid, sense, instance,

{1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2} DFHZC4944 date time applid termid tranid Protocol Violation
Destination: CSNE detected within bind security indicators. sense
((instance) MODULE NAME: {DFHZOPX |
DFHZSCX})
DFHZC4941E date time applid Bind time failure. LU6.2
Explanation: CICS has detected an error while validating the
profile locked. sense ((instance) Module name:
bind security specification. LOCAL security has been specified,
{DFHZEV1 | DFHZEV2 | DFHZOPN})
but the bind contains data that indicates NON LOCAL
Explanation: The external security manager (ESM) has
security.
requested profile information during bind-time validation but
the requested profile is locked. When a profile is locked no For the meaning of the sense data, see the explanation on
sessions can be established. topic “DFHZCxxxx messages” on page 356.
User response: Ensure that the correct data is sent in the
bind for the required type of security.
Module: DFHZSCX, DFHZOPX
User response: Check the profiles defined to the ESM. The
system administrator may have locked the profile. Request XMEOUT Parameters: date, time,applid, termid, tranid, sense,
that the profile be unlocked. Try once more when the profile instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZOPX,
has been unlocked. 4=DFHZOPX}
Module: DFHZEV1, DFHZEV2, DFHZOPN Destination: CSMT
XMEOUT Parameters: date, time,applid, sense, instance,
{1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2} DFHZC4945E date time applid termid tranid Session unbind
Destination: CSNE request due to the forcepurge of a task. sense
((instance) Module name: {DFHZARER})
Explanation: A task was purged or forcepurged while it was
DFHZC4942E date time applid Bind time failure. Expired
suspended, waiting for an ISC request to complete.
LU6.2 profile found. sense ((instance) Module
name: {DFHZEV1 | DFHZEV2 | DFHZOPN}) For the meaning of the sense data, see the explanation on
Explanation: The external security manager (ESM) has topic “DFHZCxxxx messages” on page 356.
requested profile information during bind-time validation but System action: An unbind is requested for the session against
the requested profile has expired. which the ISC request was waiting and the task is abended A
FORCEPURGE command causes the task to be abended
irrespective of the state of the session. Other VTAM error
messages may result from this action.
User response: Investigate the reasons the task was purged
User response: Check the profiles defined to the ESM. The
or forcepurged because it may have been the result of an
system administrator needs to update the required profile.
application error. In addition, the partner task in the connected
Request that the profile be updated. Try once more when the
CICS system will have session failure notification returned on
profile has been updated.
the next ISC request after the session has been unbound.
Module: DFHZEV1, DFHZEV2, DFHZOPN
Check that the partner task has handled the situation.
XMEOUT Parameters: date, time,applid, sense, instance, Module: DFHZARER
{1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}
Destination: CSNE
instance, {1=DFHZARER}
Destination: CSNE
DFHZC4943E date time applid termid tranid RPL B FSM error.
sense ((instance) Module name: {DFHZSDL}) DFHZC4946E date time applid termid tranid Invalid attach
Explanation: The finite state machine (FSM), for the APPC parameter was received. sense ((instance)
alternate RPL (RPL 'B'), has detected an error in the use of the Module name: {DFHZSUP})
RPL. Explanation: A request to attach a task has been received
For the meaning of the sense data, see the explanation on across an APPC link. However there is an error in the FMH
topic “DFHZCxxxx messages” on page 356. attach parameters. An attach parameter is present that is not
System action: The task is abnormally terminated with abend authorized by the bind security indicators.
code ATNI and a dump is produced. The instance data can take the following values:
User response: If this message occurs when VTAM is
terminating, it is not a serious problem and usually no instance Meaning
response is necessary. 1 The bind security indicators show that the
connection is defined as ATTACHSEC(LOCAL)
If this message occurs during normal system execution, you indicating that this LU does not accept any security

parameters in an attach from the partner LU. One or

DFHZC4948E date time applid An error has been detected
more of the following security parameters has been
when processing an { unknown | inbound |
found: Userid, Password, Profile, AV, PV1 and PV2.
outbound} { request. | Persistent Verify
2 An already-verified (AV) indicator has been received
Signoff request. | Persistent Verify Timeout
in an attach from the partner LU, but the bind
request.} Transaction tranid is { continuing. |
security indicators show that this LU does not
terminating. | terminating abnormally.} Error
support the receipt of the AV indicator.
code: X'xxxxx' Connection: yyyy
3 A persistent verification signon (PV2) indicator, or a
Explanation: An error has been detected during the execution
persistent verification signed-on (PV1) indicator, has
of transaction CLS3. The error code indicates the nature of the
been received in an attach from the partner LU, but
error:
the bind security indicators show that this LU does
X'01' Transaction CLS3 issued an unsuccessful
not support the receipt of the PV indicators.
communications request on an APPC session.
System action: The task abends and a dump is produced and
X'02' Transaction CLS3 was started by a START command
the session is unbound. An exception trace point (number
with data, but the format of the data was incorrect.
1737) for component TF is issued, tracing the invalid attach
X'04' Transaction CLS3 is attempting to send a signoff
header (FMH type 5).
request to a remote system, but the connection to the
User response: Investigate the cause of the error which is in
remote system is not an APPC connection.
the remote system. Use the FMH5 in the exception trace to
X'06' Transaction CLS3 was not started by terminal input,
nor by a START command.
request.
X'09' Transaction CLS3 was started by a START command
Module: DFHZSUP
with data, but the data could not be retrieved.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, X'0A' Transaction CLS3 is attempting to send a signoff
instance, {1=DFHZSUP, 2=DFHZSUP, 3=DFHZSUP, request to a remote system, but there is no
4=DFHZSUP, 5=DFHZSUP} connection to the remote system.
Destination: CSNE X'0B' Transaction CLS3 unsuccessfully attempted to
allocate an APPC session to a remote system.
System action: Depending upon the nature of the event that
DFHZC4947E date time applid termid tranid Attach time gave rise to the message, the transaction continues execution,
security check has failed. Security not valid. terminates normally, or terminates abnormally. The message
sense ((instance) Module name: {DFHZSUP}) text indicates which action is being taken.
Explanation: A request to attach a task has been received User response: This depends upon the error code:
over an APPC link. However the FMH5 attach parameters do X'01' Determine why the communications request on the
not conform to the APPC protocol. APPC session failed. Possible reasons are:
The instance data can take the following values: v There has been a session failure.
v The connected transaction has abended.
instance Meaning
1 Unrecognized access security subfield This error produces an exception trace, which helps
2 Multiple userid access security subfields present to determine the cause of the problem.
3 Multiple profile access security subfields present X'02' Ensure that transaction CLS3 was started by
4 Multiple password access security subfields present CICS-supplied code, and not by application code. If
5 Userid required in FMH but not received it was started by CICS-supplied code, contact your
6 PV1 and PV2 security indicators both present in IBM Support Center.
FMH5 X'04' Check the connection definition for the remote
7 Password received when AV indicator set system. It should be an APPC connection.
8 Password received when PV1 indicator set X'06' Ensure that transaction CLS3 was started by
9 Password required for PV2 but not received. CICS-supplied code, and not by application code. If
System action: The attach request is rejected and the session it was started by CICS-supplied code, contact your
is unbound. An exception trace point (number 1737) for IBM Support Center.
component TF is issued tracing the invalid attach header X'09' Determine why the data could not be retrieved. If
(FMH type 5). you are unable to do so, contact your IBM Support
User response: Investigate the cause of the error which is in Center
the remote system. Use the FMH5 in the exception trace, to X'0A' Ensure that the connection has been correctly
determine why the remote system sent an invalid attach defined
request. X'0B' Ensure that the connection is acquired and in service
Module: DFHCLS3
If the remote system has an earlier release of CICS or CICS on
another platform and the sense value given is 5 then you may XMEOUT Parameters: date, time,applid, {1= unknown, 2=
need to set USEDFLTUSER. inbound, 3= outbound}, {1= request., 2=Persistent Verify Signoff
Module: DFHZSUP request., 3=Persistent Verify Timeout request.}, tranid,{1=
continuing., 2= terminating.,3= terminating
XMEOUT Parameters: date, time,applid, termid, tranid, sense, abnormally.},X'xxxxx',yyyy
instance, {1=DFHZSUP, 2=DFHZSUP, 3=DFHZSUP, Destination: CSNE
4=DFHZSUP, 5=DFHZSUP, 6=DFHZSUP, 7=DFHZSUP,
8=DFHZSUP, 9=DFHZSUP, 10=DFHZSUP, 11=DFHZSUP,
12=DFHZSUP, 13=DFHZSUP, 14=DFHZSUP}
Destination: CSNE

address space. Otherwise, consider reducing the number of

DFHZC4949E date time applid termid tranid netname Receive
resources used in one CICS run.
Any stall - {data lost. | response lost. | command
Destination: CSMT
lost. }CLSDST return code X'rc'sense ((instance)
Module: DFHBSMIR, DFHBSMPP, DFHBSM62, DFHBSS,
Module name: {DFHZRAC})
DFHBSSZM, DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ,
Explanation: All the CICS Receive Any RPLs have been
DFHBSTZB, DFHBSTZO, DFHBSTZR, DFHBSTZV,
posted but the TCTTE for each one is waiting for a response
DFHBSTZ1, DFHBSTZ2, DFHBSZZS
from a VTAM terminal or session. All the Receive Any RPLs
have been stalled for 10 dispatches of the TCP task (CSTP). XMEOUT Parameters: date, time,applid, resource, xxxx, yyyy
This message is produced for each session that is in this
situation. A VTAM session has not responded to a command
such as BID or SHUTD sent by CICS. This is typically caused DFHZC5902E date time applid Deletion of terminal termid
by a protocol error. failed. BMS Paging session still active
System action: CICS is running with system initialization Explanation: CICS cannot delete terminal termid because a
parameter RAPOOL=(n,FORCE) causing CICS to issue a BMS paging session is still active for the terminal.
VTAM CLSDST against the session, which causes the TCTTE's System action: CICS continues.
RPL to be completed and the session to be unbound. User response: Sign on to terminal termid and purge the
pages.
The default NEP action is CLSDST, which causes CICS to Destination: CSMT
clean up the TCTTE after the pending command has been Modules: DFHBSTB
terminated.
The Receive Any data received is discarded and the RA RPL is
reissued.
User response: Investigate the reason why the command has DFHZC5903E date time applid Deletion of terminal termid
not completed. The TCTTE RPL is printed with the message. failed. CICS logic error
Explanation: CICS cannot delete the terminal termid, because
It is important to look at any earlier DFHZC4949 messages the CICS batch data attach function (DIP) is still active for this
because of the asynchronous nature of DFHZNAC. If the terminal.
CLSDST has not completed, the RPL printed will be active System action: CICS continues. A system dump is taken with
and will show the RPL that can not complete. If the CLSDST dumpcode ZC5903. Message DFHME0116 is normally
has completed when DFHZNAC runs, the RPL printed will produced containing the symptom string for this problem.
have a RTNCD/FDB2 of X'0C0B' but RPLREQ still shows User response: You need further assistance from IBM to
what command would not complete. resolve this problem. See Part 4 of the CICS Problem
If the CLSDST return code rc is non 0, the CLSDST macro has Determination Guide for guidance on how to proceed.
failed in DFHZRAC and the session remains hung. You may Destination: CSMT
be able to free the session by using VTAM command V Modules: DFHBSTD
NET,INACT,ID=netname,I. You can find the reason for the XMEOUT Parameters: date, time,applid, termid
CLSDST failure by looking at the RPL in the AP FC90 trace
point for the CLSDST.
Module: DFHZRAC DFHZC5904E date time applid Deletion of terminal termid
failed. CEDF is still active
XMEOUT Parameters: date, time,applid, termid, tranid, netname, Explanation: CICS cannot delete the terminal termid because
{1=data lost. , 2=response lost. , 3=command lost. }, X'rc', sense, an EDF session is still active for this terminal.
instance, {1=DFHZRAC, 2=DFHZRAC, 3=DFHZRAC} System action: CICS continues.
Destination: CSNE User response: Deactivate EDF for the terminal, and reinstall
the group.
DFHZC5900E date time applid System sysid has shipped Destination: CSMT
definitions but connection cccc is not known Modules: DFHBSTE
to this system. XMEOUT Parameters: date, time,applid, termid
Explanation: CICS has received definitions from remote
system sysid, but cannot find a connection named cccc.
System action: CICS continues. DFHZC5905E date time applid Deletion of terminal termid
User response: If you want these definitions to be accepted, failed. CICS logic error
install the necessary connection using CEDA, and retransmit Explanation: CICS cannot delete terminal termid because the
the definitions from the remote system. command level interface is still active for this terminal.
Destination: CSMT System action: CICS continues. A system dump is taken with
Module: DFHBSTZ1, DFHBSTZ2 dumpcode ZC5905. Message DFHME0116 is normally
produced containing the symptom string for this problem.
XMEOUT Parameters: date, time,applid, sysid, cccc User response: You need further assistance from IBM to
DFHZC5901E date time applid Install for resource failed. xxxx Determination Guide for guidance on how to proceed.
could not obtain yyyy storage Destination: CSMT
Explanation: When installing resource resource, CICS module Modules: DFHBSTH
xxxx could not get storage for the extent specified by the value XMEOUT Parameters: date, time,applid, termid
of yyyy.
User response: If possible, increase the size of your CICS

DFHZC5906E date time applid Install failed because 'xxxx' is DFHZC5911E date time applid Install for resource resource
not a permitted value for a terminal or failed. Connection cccc not found
connection name Explanation: CICS could not find the connection cccc
Explanation: A name of hexadecimal zeros has been used for associated with resource resource.
a TERMINAL or CONNECTION definition. System action: CICS continues.
User response: Install connection cccc.
This is a reserved value. CICS has failed to install the terminal
Destination: CSMT
or connection.
Modules: DFHBSMIR
xxxx is the reserved value converted to printable hexadecimal. XMEOUT Parameters: date, time,applid, resource, cccc
The error has probably been made using autoinstall.
User response: Correct the definition to use a valid name DFHZC5912E date time applid Install for terminal termid
and reinstall the group. failed. It is incompatible with connection cccc
Destination: CSMT Explanation: The terminal termid and the connection cccc are
Module: DFHBSS, DFHBSTZ, DFHBSTZ1, DFHBSTZ2 mutually incompatible.
DFHBSMPP System action: CICS continues.
User response: Modify your definition of termid or cccc.
XMEOUT Parameters: date, time,applid, xxxx
Destination: CSMT
Module: DFHBSTZ, DFHBSTZ2
DFHZC5907E date time applid Deletion of remote shipped
XMEOUT Parameters: date, time,applid, termid, cccc
terminal failed for connection cccc.
Explanation: During the deletion of connection cccc, the
connection was found to have shipped remote terminals. The DFHZC5913E date time applid Deletion of node id failed. {A
deletion of one or more of these shipped remote terminals has table entry is locked. | A table entry was not
failed. found. | There was a logic error.}
System action: CICS continues. Table=tabname Key(key) Module(modname)
User response: See message DFHZC5915 for further Instance=inst.
information. Explanation: CICS cannot delete node id. The message
explains the reason for the failure.
Use CEMT to release the connection and put it OUT OF
1. One of its TMP table entries is locked by other tasks.
SERVICE, then retry the install of the connection.
2. A TMP table entry could not be found, possibly because
Destination: CSMT
the node was already deleted by another task.
Modules: DFHBSSZ
3. There was a CICS logic error. A DFHTM0002 error message
XMEOUT Parameters: date, time,applid, cccc may have been issued as well.
The TMP table entry is identified by tabname. The key used in

DFHZC5908E date time applid Install for terminal termid the table has a value key. The module that issued the message
failed. The security manager gave return code is identified by modname and the instance of the message in
retcode that module by inst.
Explanation: CICS cannot install terminal termid. DFHXSMN System action: The resource is not deleted. If the entry was
gave the return code retcode. locked, CICS issues one or more message DFHZC5980.
System action: CICS continues. User response: Choose the action which corresponds to the
User response: Check the value of the return code retcode in reason identified in the message:
the CICS Customization Guide. 1. See message DFHZC5980 for further information and
Destination: CSMT guidance. If DFHZC5980 identifies CRMD as the tranid
Modules: DFHBSTS then the entry was locked by the mass terminal delete task,
and will have been deleted.
XMEOUT Parameters: date, time,applid, termid, retcode 2. If the node is deleted, no action is needed. If the node
exists, determine whether it was replaced while this
request was running. If the entry exists and has not been
DFHZC5909E date time applid Install of resource resource
replaced, you will need assistance from IBM. See Part 4 of
failed. Call to DFHIRP irp_function
the CICS Problem Determination Guide for guidance on how
Return_code did not succeed, See DFHIRSDS
to proceed.
for return code.
Explanation: When installing resource resource, the CICS
module DFHBSSZR made a call to an IR service irp_function
which failed due to the specified return code.
Destination: CSMT
System action: CICS continues. The MRO connection resource
Module: DFHBSS, DFHBSSZ, DFHBSTZ, DFHBSTZ1,
is not installed.
DFHBSTZ2, DFHBSTZV, DFHBSTZS, DFHBSTZZ
User response: For an explanation of the return code, see
DFHIRSDS in the CICS Data Areas manual. XMEOUT Parameters: date, time,applid, id, {1=A table entry is
Destination: CSMT locked.,2=A table entry was not found., 3=There was a logic
Modules: DFHBSSZR error.},tabname, key, modname, inst
XMEOUT Parameters: date, time,applid, resource,
irp_function,Return_code

DFHZC5914E date time applid Deletion of terminal termid DFHZC5917E date time applid Deletion of terminal termid
found another deletion of it in progress failed. Error message writer still active
Explanation: CICS has failed to delete terminal termid Explanation: CICS cannot delete terminal termid because the
because it is already marked as pending deletion. error message writer is still active for this terminal.
It is likely that a CEDA user is installing this terminal. User response: Put the terminal briefly into service and then
take it out of service again, using the CEMT transaction.
User response: Check if a CEDA user is installing the
Destination: CSMT
terminal. Modules: DFHBSTZE
Destination: CSMT
Module: DFHBSMIR, DFHBSMPP, DFHBSS, DFHBSTZ XMEOUT Parameters: date, time,applid, termid
DFHZC5918E date time applid Deletion of terminal termid
Console consname failed. It has pending
DFHZC5915E date time applid Deletion of node id failed. {The DFHZCP activity.
node is still in service. | The system entry is still Explanation: The VSE console consname has outstanding
in service. | The node has a task attached.} activity that prevents its deletion.
Module(modname). System action: CICS continues.
Explanation: CICS cannot delete node id The reason is User response: After replying to any outstanding replies
identified in the message. requested of this console, put the console briefly into service
1. The terminal or session is still in service. and then take it out of service again, using the CEMT
2. The system entry of this session is still in service. transaction.
3. A task is still attached to this terminal or session. Destination: CSMT
The module issuing the message is identified as modname. Modules: DFHBSTZO
System action: CICS continues and does not delete the node. XMEOUT Parameters: date, time,applid, termid, consname
User response: Before retrying the deletion or replacement,
perform the action which corresponds to the reason given in
the message. DFHZC5919E date time applid Deletion of terminal termid
1. Set the node OUT OF SERVICE failed. CICS logic error
2. Set the system entry OUT OF SERVICE. Explanation: CICS cannot delete terminal termid because of
3. Wait for activity to cease for this node. an error in disconnecting remote terminals.
Module: DFHBSMIR, DFHBSTZ dumpcode ZC5919. Message DFHME0116 is normally
XMEOUT Parameters: date, time,applid, id, {1=The node is still in
service., 2=The system entry is still in service., 3=The node has a
task attached.},modname
Destination: CSMT
DFHZC5916E date time applid Deletion of terminal termid Modules: DFHBSSZ
failed. It has pending DFHZCP activity
Explanation: CICS cannot delete resource termid because
DFHZCP activity is pending for this terminal. The resource
could be a session belonging to a connection or a terminal DFHZC5920E date time applid Install of terminal termid
TCTTE. failed. CICS logic error
System action: CICS continues. Explanation: This CICS system failed to install terminal
User response: Use exception trace point AP FCDE to termid. No terminals can be accepted yet because the system
determine what sort of activity is pending. does not have a local system entry. There was probably a
failure during CICS initialization.
If this indicates that the VTAM CLSDST command is in
System action: CICS continues. A system dump is taken with
progress, VTAM could be trying to contact a nonexistent or
dumpcode ZC5920. Message DFHME0116 is normally
unavailable resource (indicated by NETNAME in the CEDA
definition for the resource). In this case, wait for a few
minutes and retry the reinstall or discard. If you have access
to the JOBLOG, message DFHZC3462 for the resource in
question indicates that the CLSDST has finished.
Destination: CSMT
If the resource is a terminal, put the terminal briefly into Module: DFHBSTZ, DFHBSTZ2
service and then take it out of service again, using the CEMT
transaction.
Destination: CSMT
Modules: DFHBSTZA DFHZC5921E date time applid Install of terminal termid
failed. VTAM support not loaded.
Explanation: CICS failed to install terminal termid because
CICS was initialized without VTAM support.
System action: CICS continues processing.
User response: To use VTAM, shut down CICS and restart

with the system initialization parameter VTAM=YES, a TCT XMEOUT Parameters: date, time,applid, cccc
assembled with ACCESSMETHOD=VTAM, and appropriate
RDO terminal definitions.
Destination: CSMT DFHZC5927E date time applid Install for connection cccc
Modules: DFHBSZZV failed. CICS logic error
Explanation: CICS did not install the connection cccc because
XMEOUT Parameters: date, time,applid, termid DFHZCP did not receive a RECORDFORMAT operand.
DFHZC5923E date time applid Install for terminal termid
failed. CICS logic error
the bind-image was invalid.
Destination: CSMT
Modules: DFHBSSZ6
User response: You need further assistance from IBM to XMEOUT Parameters: date, time,applid, cccc
Destination: CSMT DFHZC5929E date time applid Deletion of connection cccc
Modules: DFHBSZZV failed. It is in use by n indirect connections
Explanation: CICS did not delete the connection cccc because
XMEOUT Parameters: date, time,applid, termid the connection is still in use by n indirect connections.
User response: Carry out the following procedure to delete
DFHZC5924E date time applid Install for terminal termid
the indirect connections:
1. Use the CEDA transaction to change the remote system
named in the INDSYS parameter.
the TCTTE contained no node information block (NIB)
2. Reinstall the indirect connection.
descriptor.
3. Reinstall the 'main' connection.
4. Change the indirect connection to reset the remote system
named in the INDSYS parameter back to name the 'main'
connection.
5. Reinstall the indirect connection.
Destination: CSMT
Modules: DFHBSS
Destination: CSMT
Modules: DFHBSZZV XMEOUT Parameters: date, time,applid, cccc, n
DFHZC5931E date time applid Install for modename
modename failed. Maximum number of APPC
DFHZC5925E date time applid Deletion of connection cccc
sessions would have been exceeded
failed. Its AID-Chains are not empty
Explanation: CICS did not install a SESSIONS definition
Explanation: CICS did not delete connection cccc because the
using MODENAME modename because it would have
AID-chains for the remote system cccc are not empty.
exceeded the maximum number of permitted sessions.
User response: Using the CEMT transaction, put the
User response: Either wait for the system to become less
connection into service to allow the outstanding AIDs to be
busy, or delete some APPC sessions.
processed. Then take the connection out of service to allow
deletion. The system programmer should consider increasing the
Destination: CSMT number of CICS TORs.
Modules: DFHBSSA Destination: CSMT
Modules: DFHBSM61
XMEOUT Parameters: date, time,applid, cccc
XMEOUT Parameters: date, time,applid, modename
DFHZC5926E date time applid Install for connection cccc

failed. CICS logic error DFHZC5932E date time applid Install for modename
Explanation: CICS did not install the connection cccc because modename failed. Connection cccc not found
DFHZCP received no DATASTREAM operand. Explanation: CICS did not install a SESSIONS definition
System action: CICS continues. A system dump is taken with using MODENAME modename because of an unknown name
dumpcode ZC5926. Message DFHME0116 is normally cccc in the CONNECTION parameter.
produced containing the symptom string for this problem. System action: CICS continues.
User response: You need further assistance from IBM to User response: Install connection cccc.
resolve this problem. See Part 4 of the CICS Problem Destination: CSMT
Determination Guide for guidance on how to proceed. Modules: DFHBSM62
Destination: CSMT
XMEOUT Parameters: date, time,applid, modename, cccc
Modules: DFHBSSZ6

DFHZC5933E date time applid Install for modename DFHZC5939E date time applid Install for name failed.
modename failed. Connection cccc is not valid Duplicate session- or modegroup-name for
here connection sysid
Explanation: CICS did not install a SESSIONS definition Explanation: CICS is unable to install a session or
using MODENAME modename because the CONNECTION is modegroup as the session-name or modegroup-name name is
not valid in this context. duplicated.
System action: CICS continues. System action: CICS continues processing, but the session or
User response: Modify your definition of remote system cccc. modegroup is not installed.
Destination: CSMT User response: Change the duplicated session-name or
Modules: DFHBSM62 modegroup-name.
Destination: CSMT
XMEOUT Parameters: date, time,applid, modename, cccc
Module: DFHBSMIR, DFHBSM62
XMEOUT Parameters: date, time,applid, name, sysid
DFHZC5934E date time applid Install for modename
modename failed. Single-session connection
cccc is already in use. DFHZC5940E date time applid Install for terminal termid
Explanation: CICS did not install a SESSIONS definition failed. Error console cannot be deleted
using MODENAME modename because the single-session Explanation: You have tried to replace the error console,
CONNECTION cccc is already in use. CERR. CICS does not allow this.
System action: CICS continues. System action: CICS continues with original error console.
User response: Modify the definition of cccc. User response: Note this restriction.
Module: DFHBSM61, DFHBSM62 Modules: DFHZCQDL
XMEOUT Parameters: date, time,applid, modename, cccc XMEOUT Parameters: date, time,applid, termid
DFHZC5936E date time applid Install for modename DFHZC5941E date time applid Install for terminal termid
modename failed. Connection cccc has active failed. Console consname has a conversation
modegroup xxxx outstanding
Explanation: CICS has not installed a SESSIONS definition Explanation: CICS was unable to install terminal termid
with MODENAME modename because the connection cccc because the console consname has posted an ECB.
already has an active MODEGROUP, xxxx. System action: Processing continues.
System action: CICS continues. User response: Put the terminal briefly into service and then
User response: Put the connection briefly into service and take it out of service again, using the CEMT transaction.
then take it out of service again, using the CEMT transaction. Destination: CSMT
Destination: CSMT Modules: DFHBSTZO
Modules: DFHBSM62
XMEOUT Parameters: date, time,applid, termid, consname
XMEOUT Parameters: date, time,applid, modename, cccc, xxxx
DFHZC5942E date time applid Node nodeid was not installed.

DFHZC5937I date time applid Deletion of modename The addition of key key to table tablename
modename found another deletion of it in failed. RC=X'return'. Module(modname).
progress Explanation: CICS cannot install the definition of node nodeid
Explanation: CICS has not deleted a SESSIONS definition because an addition to a TMP table failed. CICS was trying to
with MODENAME modename because the definition is already add the key key to the table tablename.
pending deletion.
System action: CICS continues. The return code from TMP is given in return. If the return
User response: Check if a CEDA user was installing the code is 4, the entry was a duplicate. It is possible that another
SESSIONS definition. entry was added at the same time as this entry and used the
Destination: CSMT same key. If this is not the case, CICS has suffered a logic
Modules: DFHBSM62 error. The module that issued the message is indicated by
modname.
XMEOUT Parameters: date, time,applid, modename System action: CICS does not install the definition.
User response: If the entry was not overlapped by another
definition which conflicted with its key, or if the return code is
DFHZC5938E date time applid Deletion of modename not 4, you will need assistance from IBM to resolve the
modename failed. Unable to delete session(s) problem. See Part 4 of the CICS Problem Determination Guide
Explanation: CICS is unable to delete a SESSIONS definition for guidance on how to proceed.
with MODENAME modename because of one or more errors Destination: CSMT
reported in previous messages. Module: DFHBSS, DFHBSTZ, DFHBSTZZ, DFHBSTZ1,
System action: CICS continues. DFHBSTZ2
User response: Refer to any preceding messages for further
information and guidance. Correct the reported errors. XMEOUT Parameters: date, time,applid, nodeid, key, tablename,
Destination: CSMT X'return',modname
Modules: DFHBSM61

DFHZC5943E date time applid MRO connection connname DFHZC5949E date time applid Install for sessions ssss failed.
could not be deleted because IRC is open. It is incompatible with connection cccc
Explanation: CICS cannot delete the connection conname Explanation: CICS has not installed the SESSIONS definition,
because it is an MRO connection and interregion ssss, because the CONNECTION specified does not support
communication (IRC) is open. the required type of session. If you are replacing a connection
System action: The connection is not deleted. of the same name but of a different type and the install fails
User response: Close the IRC definition and retry the Delete for some other reason then this message may occur.
or Replace. System action: CICS continues.
Destination: CSMT User response: Modify your definition of cccc.
Modules: DFHBSS Destination: CSMT
Module: DFHBSMIR, DFHBSTZS, DFHBSTZR
XMEOUT Parameters: date, time,applid, connname
XMEOUT Parameters: date, time,applid, ssss, cccc
DFHZC5945E date time applid Deletion of sessions ssss

failed. Connection cccc is defined to IRC DFHZC5950E date time applid Install for terminal termid
Explanation: CICS has not deleted the SESSIONS definition, failed. Console consname already exists
ssss, because the CONNECTION is still defined to IRC. Explanation: CICS has not installed the CONSOLE definition
System action: CICS continues. termid because the console ID, consname, already exists.
User response: Issue a CEMT SET IRC CLOSED command. System action: CICS continues without installing the
Destination: CSMT terminal.
Modules: DFHBSTZR User response: Use the CEDA transaction to define a
different console ID and reinstall the terminal.
XMEOUT Parameters: date, time,applid, ssss, cccc Destination: CSMT
Module: DFHBSS, DFHBSTZ, DFHBSTZO
DFHZC5946E date time applid Install for sessions ssss failed. XMEOUT Parameters: date, time,applid, termid, consname
Connection cccc is defined to IRC
Explanation: CICS has not installed the SESSIONS definition,
ssss, because the CONNECTION is already defined to IRC. DFHZC5951E date time applid Deletion of connection ssss
System action: CICS continues. failed. Unable to delete sessions
User response: Issue a CEMT SET IRC CLOSED command. Explanation: CICS has not deleted the CONNECTION
Destination: CSMT definition, ssss, because it cannot delete one or more sessions.
Modules: DFHBSTZR A preceding message or messages should explain this failure.
XMEOUT Parameters: date, time,applid, ssss, cccc User response: Refer to the preceding message for further
DFHZC5947E date time applid Install for sessions ssss failed. Destination: CSMT
CICS logic error Module: DFHBSSZR, DFHBSSZ6
Explanation: CICS has not installed the SESSIONS definition, XMEOUT Parameters: date, time,applid, ssss
ssss, because the CONNECTION name is not specified.
dumpcode ZC5947. Message DFHME0116 is normally DFHZC5952E date time applid Deletion of terminal termid
produced containing the symptom string for this problem. failed. It needs to be SET RELEASED
User response: You need further assistance from IBM to Explanation: CICS cannot delete terminal termid because of
resolve this problem. See Part 4 of the CICS Problem its current state.
Determination Guide for guidance on how to proceed. System action: CICS continues.
Destination: CSMT User response: Use the CEMT transaction to set terminal
Module: DFHBSMIR, DFHBSTZR termid released and out of service.
Destination: CSMT
XMEOUT Parameters: date, time,applid, ssss Modules: DFHBSTZV
DFHZC5948E date time applid Install for sessions ssss failed.
Connection cccc is not suitable for IRC
Explanation: CICS has not installed the SESSIONS definition, DFHZC5953E date time applid CICS logic error
ssss, because the CONNECTION specified is not suitable for Explanation: An object being installed did not have a
IRC. bind-image.
System action: CICS continues. System action: CICS continues. A system dump is taken with
User response: Modify your definition of cccc. dumpcode ZC5953. Message DFHME0116 is normally
Destination: CSMT produced containing the symptom string for this problem.
Modules: DFHBSTZR User response: You need further assistance from IBM to
XMEOUT Parameters: date, time,applid, ssss, cccc Determination Guide for guidance on how to proceed.
Destination: CSMT
Modules: DFHBSM62

DFHZC5954E date time applid Install for resource resource DFHZC5962E date time applid Install for resource resource
failed. Unable to install sessions component failed. Modename parameter not found
Explanation: CICS has failed to install resource resource. Explanation: CICS has failed to install resource resource
Previous message(s) should give the reason for the failure. because the MODENAME parameter is missing.
System action: CICS continues. System action: CICS continues.
User response: Refer to any preceding messages for further User response: Supply the missing parameter.
information and guidance. Destination: CSMT
Destination: CSMT Modules: DFHBSTZS
Modules: DFHBSTZC
XMEOUT Parameters: date, time,applid, resource
DFHZC5963E date time applid operation RUSIZE xxxx from

DFHZC5957E date time applid Arch. User-Data ID X'xx occurs terminal termid was greater than TYPETERM
in bind. CICS logic error RUSIZE yyyy.
Explanation: The APPC SESSIONS object being installed is Explanation: An autoinstall has been attempted with
invalid because architected user-data IDs greater than X'02' terminal termid that has a VTAM RECEIVESIZE greater than
occur in the bind. the corresponding TYPETERM RECEIVESIZE|SENDSIZE.
System action: CICS does not install the object. A system System action: CICS continues. The autoinstall is rejected.
dump is taken with dumpcode ZC5957. Message DFHME0116 User response: Increase the TYPETERM RECEIVESIZE or the
is normally produced containing the symptom string for this TYPETERM SENDSIZE, OR decrease the RECEIVESIZEs in
problem. the VTAM LOGMODE table.
User response: You need further assistance from IBM to Destination: CSMT
resolve this problem. See Part 4 of the CICS Problem Modules: DFHBSZZV
Destination: CSMT XMEOUT Parameters: date, time,applid, operation, xxxx, termid,
Modules: DFHBSM62 yyyy
XMEOUT Parameters: date, time,applid, xx

DFHZC5964E date time applid Install for sessions ssss failed.
CICS logic error.
DFHZC5958E date time applid Install failed for xxxx. This is Explanation: CICS has failed to install SESSIONS ssss because
the name of the local system which must not the length of the BINDPASSWORD exceeds the limit of 8.
be replaced. System action: CICS continues. A system dump is taken with
Explanation: A terminal or a connection was defined with dumpcode ZC5964. Message DFHME0116 is normally
the same name as the local system entry during the last run of produced containing the symptom string for this problem.
CICS. This is not allowed as the local system entry cannot be User response: You need further assistance from IBM to
replaced. resolve this problem. See Part 4 of the CICS Problem
During cold start of the current run of CICS, CICS attempted
Destination: CSMT
to install the group which included the invalid definition.
Modules: DFHBSSZS
CICS then issued this message.
System action: CICS continues, but this terminal or XMEOUT Parameters: date, time,applid, ssss
connection is not installed.
User response: Use the CEDA transaction to correct the
terminal or connection name and install the group. DFHZC5966I date time applid {INSTALL | DELETE |
Destination: CSMT RESTORE} started for resource (termid) SYSID
Modules: DFHBSSZL (sysid) (Module : modname).
Explanation: CICS has started an install, delete or restore of
XMEOUT Parameters: date, time,applid, xxxx resource termid. The resource may be either a terminal, a
connection, a modegroup, a session or a pool_entry. For
connections sysid will always be blank. For a local terminal or
DFHZC5961E date time applid Deletion of surrogate xxxx
a pool_entry sysid will be the sysidnt of the local CICS system.
For a remote terminal sysid will be the sysidnt of the remote
Explanation: CICS cannot delete a surrogate TCT entry.
system which owns the terminal. For a modegroup or a
session sysid will be the name of the sysidnt with which the
modegroup or session is associated.
Destination: CADL
Module: DFHBSTZ, DFHBSMPP, DFHBSM62, DFHBSS,
Destination: CSMT
DFHBSMIR
Module: DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters: date, time, applid, {1=INSTALL,
2=DELETE, 3=RESTORE}, resource, termid, sysid, modname

DFHZC5967E date time applid Install for modename DFHZC5973E date time applid Install for sessions ssss failed.
modename failed. Unable to install sessions Max session-count reached for modename
Explanation: CICS has failed to install a SESSIONS definition modename
using MODENAME modename. Previous message(s) should Explanation: CICS failed to delete a SESSIONS definition ssss
give the reason for the failure. because the maximum session-count was reached for
System action: CICS continues. MODENAME modename.
User response: Refer to the preceding message for further System action: CICS continues.
information and guidance. User response: Delete some sessions in modename, or redefine
Destination: CSMT modename with a higher maximum session-count.
Modules: DFHBSM61 Destination: CSMT
Modules: DFHBSTZS
XMEOUT Parameters: date, time,applid, ssss, modename
DFHZC5968E date time applid Unable to install LU Services

Manager for modename modename DFHZC5974E date time applid Deletion of pool pppp failed.
Explanation: CICS has failed to install a CONNECTION Unable to delete pool entries
definition for MODEGROUP modename. Previous message(s) Explanation: CICS failed to delete a POOL pppp. Previous
should give the reason for the failure. messages(s) should explain the cause of this failure.
System action: CICS continues. System action: CICS continues.
User response: Refer to any preceding messages for further User response: Refer to any previous messages for further
information and guidance. guidance and information.
Modules: DFHBSSZP Modules: DFHBSMPP
XMEOUT Parameters: date, time,applid, modename XMEOUT Parameters: date, time,applid, pppp
DFHZC5969E date time applid Deletion of dependent DFHZC5975E date time applid Install for resource pppp failed.
modename(s) failed for connection modename CICS logic error
Explanation: CICS has failed to replace a CONNECTION Explanation: CICS failed to install the POOL definition pppp
definition for MODEGROUP modename. Previous message(s) because the required POOLID parameter was missing. This is
should give the reason for the failure. a CICS logic error (probably in DFHTRZPP).
System action: CICS continues. System action: CICS continues. A system dump is taken with
User response: Refer to any preceding messages for further dumpcode ZC5975. Message DFHME0116 is normally
information and guidance. produced containing the symptom string for this problem.
Destination: CSMT User response: You need further assistance from IBM to
Modules: DFHBSSZS resolve this problem. See Part 4 of the CICS Problem
XMEOUT Parameters: date, time,applid, modename Destination: CSMT
Module: DFHBSMPP, DFHBSTZP
DFHZC5971E date time applid Delete of resource resource XMEOUT Parameters: date, time,applid, pppp
Explanation: CICS failed to delete resource resource because
of an unexpected signon state during the destroy operation. DFHZC5976E date time applid CICS logic error
System action: CICS continues. A system dump is taken with Explanation: CICS failed to install a POOL definition because
dumpcode ZC5971. Message DFHME0116 is normally the required POOLCNT parameter was missing. This is a
produced containing the symptom string for this problem. CICS logic error (probably in DFHTRZPP).
User response: You need further assistance from IBM to System action: CICS continues. A system dump is taken with
resolve this problem. See Part 4 of the CICS Problem dumpcode ZC5976. Message DFHME0116 is normally
Determination Guide for guidance on how to proceed. produced containing the symptom string for this problem.
Destination: CSMT User response: You need further assistance from IBM to
Modules: DFHBSTS resolve this problem. See Part 4 of the CICS Problem
XMEOUT Parameters: date, time,applid, resource Destination: CSMT
Modules: DFHBSMPP
DFHZC5972E date time applid Delete of resource resource XMEOUT Parameters: date, time,applid
failed. It is still signed on
Explanation: CICS failed to delete a TERMINAL or
SESSIONS resource resource because a terminal or session is DFHZC5977E date time applid Failure building pool entries
still signed on. Explanation: CICS failed to install a POOL definition,
System action: CICS continues. because of a failure in building pool entries. Previous
User response: Run the signoff transaction CESF and retry. messages should explain the cause of this failure.
Destination: CSMT System action: CICS continues.
Modules: DFHBSTS User response: Refer to any previous messages for further
XMEOUT Parameters: date, time,applid, resource Destination: CSMT

Modules: DFHBSMPP
DFHZC5983E date time applid Unable to replace resource
XMEOUT Parameters: date, time,applid Explanation: CICS failed to install resource resource either
because it already exists, or for reasons explained in previous
messages.
DFHZC5978E date time applid Unable to replace pool pppp
Explanation: CICS failed in an attempt to install or delete a Possible causes are:
POOL definition. Previous messages should explain the cause v Non-VTAM and VTAM terminals defined with the same
of this failure. name. If a non-VTAM terminal is installed, CICS will not
System action: CICS continues. autoinstall a VTAM terminal with the same name.
User response: Refer to previous messages for further v An attempt to replace your own terminal, or a terminal
information and guidance. with the same name as the terminal being used to issue the
Destination: CSMT CEDA command.
Modules: DFHBSMPP v An attempt to replace a terminal with the same
REMOTENAME and REMOTESYSTEM as an earlier
XMEOUT Parameters: date, time,applid, pppp definition in the same group.
User response: Refer to previous messages for further
DFHZC5979E date time applid Deletion of pool pppp failed. It
still has session termid
Explanation: CICS has failed to delete pool pppp because the If no previous messages were issued, check your terminal
pool still has an active session for terminal termid. identifiers.
System action: CICS continues. Destination: CSMT
User response: Put the terminal out of service (using the Module: DFHBSS, DFHBSTZ, DFHBSS2, DFHBSTZ1,
CEMT transaction) and retry. DFHBSTZ2
Destination: CSMT
Modules: DFHBSTZP XMEOUT Parameters: date, time,applid, resource
XMEOUT Parameters: date, time,applid, pppp, termid

DFHZC5985E date time applid Install for resource resource
failed. Unable to install connection
DFHZC5980E date time applid Resource resource is in use by component
task taskid Transaction tranid Explanation: CICS has failed to install resource resource.
Explanation: The resource resource is in use. taskid is the task Previous message(s) should give the reason for the failure.
number, and tranid is the transaction ID. System action: CICS continues.
System action: CICS continues. User response: Refer to previous messages for further
User response: Wait for the termination of task taskid, and information and guidance.
retry the operation. Destination: CSMT
Destination: CSMT Modules: DFHBSTZC
Module: DFHBSS, DFHBSSZ, DFHBSTZ, DFHBSTZ1,
DFHBSTZ2 DFHBST2V XMEOUT Parameters: date, time,applid, resource
XMEOUT Parameters: date, time,applid, resource, taskid, tranid

DFHZC5986E date time applid CICS logic error
Explanation: Either the warm keypoint program (DFHWKP),
DFHZC5981E date time applid Pool pppp not found or the query transaction (DFHQRY), made an invalid request
Explanation: CICS has failed to install a resource because which could not be implemented.
POOL pppp does not exist. Previous messages should explain System action: CICS continues. A system dump is taken with
the cause of this failure. dumpcode ZC5986. Message DFHME0116 is normally
System action: CICS continues. produced containing the symptom string for this problem.
User response: Refer to the previous messages for further User response: You need further assistance from IBM to
information and guidance. resolve this problem. See Part 4 of the CICS Problem
Destination: CSMT Determination Guide for guidance on how to proceed.
Modules: DFHBSTZP Destination: CSMT
Modules: DFHZCQCH
XMEOUT Parameters: date, time,applid, pppp
DFHZC5982E date time applid Deletion of pool pppp failed.
Pool entry is in use for termid DFHZC5988E date time applid Install for resource resource
Explanation: CICS has failed to delete POOL pppp because failed. VTAM support not generated
the pool still has an entry in use for terminal termid. Explanation: CICS failed to install resource resource because
System action: CICS continues. CICS was initialized without VTAM support.
User response: Put the terminal out of service (using the System action: CICS continues.
CEMT transaction) and retry. User response: If you want to install VTAM resources
Destination: CSMT urgently, shut down CICS, and restart it with the system
Modules: DFHBSMPP initialization parameter ACCESSMETHOD=VTAM, and
appropriate TCT or RDO terminal definitions.
XMEOUT Parameters: date, time,applid, pppp, termid
Destination: CSMT
Module: DFHBSSZS, DFHBSSZ6, DFHBSTZV


Explanation: CICS rejected a RESTORE request because the
DFHZC5989E date time applid Deletion of resource resource resource types table (DFHZCQRT) in DFHZCQ is
failed. Remote deletion in connection cccc incompatible with the recovery record from the log or CICS
failed catalog.
Explanation: CICS failed to delete resource resource because a System action: CICS continues. A system dump is taken with
remote delete in system cccc failed. dumpcode ZC5993. Message DFHME0116 is normally
Previous messages should explain the cause of this failure. User response: You need further assistance from IBM to
System action: CICS continues. resolve this problem. See Part 4 of the CICS Problem
User response: Refer to the previous message for further Determination Guide for guidance on how to proceed.
information and guidance. Destination: CSMT
Destination: CSMT Modules: DFHZCQRS
Module: DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters: date, time,applid, resource, cccc

DFHZC5990E date time applid CICS logic error Explanation: CICS rejected a RESTORE request because no
Explanation: CICS rejected an INSTALL or DELETE request recovery record was passed.
because it does not recognize the request code. System action: CICS continues. A system dump is taken with
System action: CICS continues. A system dump is taken with dumpcode ZC5994. Message DFHME0116 is normally
dumpcode ZC5990. Message DFHME0116 is normally produced containing the symptom string for this problem.
produced containing the symptom string for this problem. User response: You need further assistance from IBM to
User response: You need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem
resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.
Determination Guide for guidance on how to proceed. Destination: CSMT
Destination: CSMT Modules: DFHZCQRS
Modules: DFHZCQ00
DFHZC5995E date time applid CICS logic error. Resource

DFHZC5991E date time applid CICS logic error Type Code xxxx Subtype yyyy not recognized
Explanation: CICS rejected a VALIDATE BIND request with associated bind image
because no BIND was supplied. Explanation: CICS failed to install a resource with resource
System action: CICS continues. A system dump is taken with type code (RTC) xxxx and subtype yyyy (from the Builder
dumpcode ZC5991. Message DFHME0116 is normally Parameter Set) because a resource with type code xxxx,
produced containing the symptom string for this problem. sub-type yyyy, and the associated BIND-image, is not a builder
User response: You need further assistance from IBM to resource type.
Determination Guide for guidance on how to proceed. This is a CICS logic error (probably in DFHTRZxP).
Modules: DFHZCQ00 dumpcode ZC5995. Message DFHME0116 is normally
XMEOUT Parameters: date, time,applid User response: You need further assistance from IBM to
DFHZC5992E date time applid Resource Types Table does not
Destination: CSMT
support recovery record
Modules: DFHZCQIS
Explanation: CICS rejected RESTORE request because the
resource types table (DFHZCQRT) in DFHZCQ is XMEOUT Parameters: date, time,applid, xxxx, yyyy
incompatible with the recovery record from the log or CICS
catalog.
System action: CICS continues. A system dump is taken with DFHZC5996E date time applid CICS logic error
dumpcode ZC5992. Message DFHME0116 is normally Explanation: CICS has rejected an INSTALL request because
produced containing the symptom string for this problem. the resource type code in the request is zero.
User response: CICS is unable to warm start correctly. You System action: CICS continues. A system dump is taken with
should therefore shut CICS down and perform a COLD start. dumpcode ZC5996. Message DFHME0116 is normally
Destination: CSMT produced containing the symptom string for this problem.
Modules: DFHZCQRS User response: You need further assistance from IBM to
XMEOUT Parameters: date, time,applid Determination Guide for guidance on how to proceed.
Destination: CSMT
Modules: DFHZCQIS

DFHZC5997E date time applid CICS logic error DFHZC6202E date time applid Pattern pattern not valid for
Explanation: CICS has rejected an INQUIRE request because builder
no TCT entry was passed. Explanation: While executing a request, CICS table builder
System action: CICS continues. A system dump is taken with services has detected that the pattern pattern cites a builder
dumpcode ZC5997. Message DFHME0116 is normally that is not declared with DFHBSHDR(ENTRY). pattern is the
produced containing the symptom string for this problem. name of the pattern as coded in the DFHBSPTE macro.
User response: You need further assistance from IBM to System action: CICS rejects the request. A system dump is
resolve this problem. See Part 4 of the CICS Problem taken with dumpcode ZC6202. Message DFHME0116 is
Determination Guide for guidance on how to proceed. normally produced containing the symptom string for this
Destination: CSMT problem.
Modules: DFHZCQIQ User response: You need further assistance from IBM to
XMEOUT Parameters: date, time,applid Determination Guide for guidance on how to proceed.
Destination: CSMT
DFHZC5998E date time applid Install specified a resource Module: DFHTBSB, DFHTBSL, DFHTBSQ, DFHTBSR
that cannot be replaced XMEOUT Parameters: date, time,applid, pattern
Explanation: CICS rejected a DELETE request because the
entry passed is of a type that cannot be deleted, for example, a
non-VTAM terminal. DFHZC6203E date time applid Unable to obtain DWE
System action: CICS continues. action-list storage
User response: The failing delete/replace was necessitated by Explanation: While executing a request, CICS table builder
an INSTALL request. Correct the resource type in that request. services could not obtain storage to build an element for the
Destination: CSMT DWE action list.
Module: DFHZCQCH, DFHZCQDL System action: CICS rejects the request.
User response: This failure may be a symptom of a dynamic
XMEOUT Parameters: date, time,applid storage area (DSA) that is too small. If so, you can solve the
problem by increasing the size of your CICS region. For advice
DFHZC5999E date time applid CICS logic error. on estimating the size of the DSA and the CICS region, see the
Explanation: If DFHZCQCH issues this message, CICS has CICS System Definition Guide and the CICS Performance Guide.
rejected a CATALOG request because the required entry The failure may also be caused by an error in another
parameter was not passed. transaction, for example, a looping program with an EXEC
If DFHZCQDL issues this message, CICS has rejected a CICS GETMAIN within the loop.
DELETE request because the required entry parameter was not Destination: CSMT
passed. Module: DFHTBSBP, DFHTBSDP, DFHTBSL
System action: CICS continues. A system dump is taken with XMEOUT Parameters: date, time,applid
User response: CICS Performance Guide. You need further DFHZC6204E date time applid Illegal subpattern definition
assistance from IBM to resolve this problem. See Part 4 of the pattern
CICS Problem Determination Guide for guidance on how to Explanation: While executing a request, CICS table builder
proceed. services has detected that the subpattern pattern cites a builder
Destination: CSMT that is not declared with DFHBSHDR(ENTRY). pattern is the
Module: DFHZCQCH, DFHZCQDL name of the subpattern as coded in the DFHBSPTE macro.
System action: CICS rejects the request. A system dump is
XMEOUT Parameters: date, time,applid taken with dumpcode ZC6204. Message DFHME0116 is
DFHZC6200E date time applid Could not obtain DWE storage problem.
Explanation: While executing a BUILD or DESTROY request, User response: You need further assistance from IBM to
the CICS table builder services could not obtain deferred work resolve this problem. See Part 4 of the CICS Problem
element (DWE) storage. Determination Guide for guidance on how to proceed.
System action: CICS rejects the request. Destination: CSMT
User response: This failure may be a symptom of a dynamic Module: DFHTBSBP, DFHTBSDP
storage area (DSA) that is too small. If so, you can solve the XMEOUT Parameters: date, time,applid, pattern
problem by increasing the size of your CICS region. For advice
on estimating the size of the DSA and the CICS region, see the
CICS System Definition Guide and the CICS Performance Guide. DFHZC6205E date time applid Illegal subpattern definition
pattern
The failure may also be caused by an error in another Explanation: While executing a request, CICS table builder
transaction, for example, a looping program with an EXEC services has detected that the subpattern pattern is invalidly
CICS GETMAIN within the loop. defined. pattern is the name of the subpattern as coded in the
Destination: CSMT DFHBSPTE macro.
Module: DFHTBSB, DFHTBSD, DFHTBSL System action: CICS rejects the request. A system dump is
XMEOUT Parameters: date, time,applid taken with dumpcode ZC6205. Message DFHME0116 is
problem.


DFHZC6212E date time applid Level mismatch with catalog
record. DFHBS xxx
Explanation: While executing a request during a warm or
Destination: CSMT
emergency start, CICS table builder services has detected that
Module: DFHTBSBP, DFHTBSDP
the CC record is not compatible with the pattern it names. xxx
XMEOUT Parameters: date, time,applid, pattern is the builder ID.
System action: CICS rejects the request.
User response: The CC record was probably written by an
DFHZC6206E date time applid Pattern pattern not valid for earlier level of CICS. That is, you have applied one or more
destroy PTF maintenance fixes to the system since the CC record was
Explanation: While executing a DESTROY request, CICS written. Assuming this is the case, you must either:
table builder services has detected that the pattern pattern is v Cold start CICS, or
not valid for a DESTROY request. pattern is the name of the v Remove the maintenance to enable a warm start or
pattern as coded in the DFHBSPTE macro. emergency restart.
System action: CICS rejects the request. A system dump is Destination: CSMT
taken with dumpcode ZC6206. Message DFHME0116 is Module: DFHTBSR, DFHTBSRP
problem. XMEOUT Parameters: date, time,applid, xxx
DFHZC6213E date time applid Recovery record abandoned.
Key is key
Destination: CSMT
Explanation: While processing a RESTORE request, CICS
Modules: DFHTBSD
Table Builder Services detected an error reported in a previous
XMEOUT Parameters: date, time,applid, pattern message. key is the catalog key for the abandoned record, or, if
the key is unknown to CICS, key is the single character ?.
System action: See the previously issued message for the
DFHZC6207E date time applid Catalog key too long or zero. cause of the problem, and follow the recommended user
Pattern pattern action.
Explanation: While executing a request, CICS table builder Destination: CSMT
services has detected that builder cited in the pattern pattern Modules: DFHTBSR
has returned an invalid CC key on MAKEKEY. pattern is the
name of the pattern as coded in the DFHBSPTE macro. XMEOUT Parameters: date, time,applid, key
System action: CICS rejects the request. A system dump is
taken with dumpcode ZC6207. Message DFHME0116 is
DFHZC6214E date time applid Unable to obtain recovery
record storage
problem.
Explanation: While processing a CATALOG request, CICS
Table Builder Services could not obtain recovery record
storage.
System action: CICS rejects the request.
Destination: CSMT
User response: This failure may be a symptom of a dynamic
Module: DFHTBSBP, DFHTBSDP, DFHTBSL
storage area (DSA) that is too small. If so, you can solve the
XMEOUT Parameters: date, time,applid, pattern problem by increasing the size of your CICS region. For advice
on estimating the size of the DSA and the CICS region, see the
CICS System Definition Guide and the CICS Performance Guide.
DFHZC6209E date time applid Invalid ZC catalog request
code xxxx The failure may also be caused by an error in another
Explanation: While executing a request, CICS table builder transaction, for example, a looping program with an EXEC
services has detected that the code, xxxx, for a catalog request CICS GETMAIN within the loop.
is invalid. Destination: CSMT
System action: CICS rejects the request. A system dump is Modules: DFHTBSLP
taken with dumpcode ZC6209. Message DFHME0116 is
problem.
User response: You need further assistance from IBM to DFHZC6301E date time applid Install for tttt failed. Duplicate
resolve this problem. See Part 4 of the CICS Problem netname netname for resource rrrr found.
Determination Guide for guidance on how to proceed. Explanation: A resource tttt was being installed but was
Destination: CSMT found to have the same network name netname as resource
Modules: DFHTBSL rrrr.
System action: The resource is not installed, CICS continues.
User response: If you want the definitions to be installed, use
CEDA to correct the network name and reinstall the definition.
Destination: CSMT
Modules: DFHBSTZV
XMEOUT Parameters: date, time,applid, tttt, netname, rrrr


DFHZC6302E date time applid Install for connection cccc
failed. Duplicate netname netname for
resource rrrr found. DFHZC6305E date time applid Install for EXCI generic
Explanation: A connection cccc was being installed but was connection cccc failed. Duplicate EXCI
found to have the same network name netname as resource generic connection rrrr found.
rrrr. Explanation: A connection cccc specifying protocol(exci) and
System action: The resource is not installed, CICS continues. conntype(generic) was being installed but an existing EXCI
User response: You cannot have an APPC connection with generic connection rrrr was found.
the same network name as another APPC connection or an System action: The resource is not installed. CICS continues.
LU6.1 connection. That is, you cannot have more than one User response: There can be only one EXCI generic
APPC connection between two systems and an APPC connection installed in a CICS system. Determine which EXCI
connection cannot be installed with an LU6.1 connection generic connection definition is required and remove the
between two systems. duplicate definition.
Neither APPC or LU6.1 network names can be the same as a If you need to replace the EXCI generic connection definition,
terminal's network name. it must have the same connection name as the one you are
replacing.
Also you cannot have an IRC connection with the same
Destination: CSMT
network name as another IRC connection. However, an IRC
Modules: DFHBSS
network name can be the same as any VTAM network name
(APPC or LU61 connection or terminal). XMEOUT Parameters: date, time,applid, cccc, rrrr
If you want the definitions to be installed, use CEDA to
correct the network name and then reinstall the definition. DFHZC6315E date time applid User userid is not authorized to
If you need to replace a connection with a different network install terminal tttt with preset security.
name, it must have the same connection name as the one you Explanation: User userid was attempting to install terminal
are replacing. tttt but the userid does not have sufficient authority. This is
Destination: CSMT because the terminal has preset authority (the definition for
Modules: DFHBSS terminal tttt specifies a userid value.) Installing a resource with
preset security requires special authorization.
XMEOUT Parameters: date, time,applid, cccc, netname, rrrr System action: Resource security violation messages are
logged to the CSCS transient data queue and to the system
console. The resource is not installed. CICS continues.
DFHZC6303E date time applid Install for tttt failed. Duplicate
User response: In order to install this resource, do one of the
netname netname found.
following:
Explanation: A resource tttt was being installed but was
v Use the CESN transaction to sign on with a userid that is
found to have a duplicate network name netname.
permitted to install terminals with preset security.
This message occurs: v Ask your security administrator to authorize userid userid to
v If the duplicate NETNAME occurred in the same group as install terminals with preset security. See the CICS RACF
this definition, or Security Guide for guidance.
v If two CEDA transactions were run at the same time and v Remove the USERID specification from the resource
the other CEDA transaction added a NETNAME between definition and install the resource without preset security.
the BUILD and CONNECT routines of DFHBSTZV. Destination: CSMT
System action: The resource is not installed; CICS continues. Modules: DFHBSTS
User response: If you want the definitions to be installed, use
XMEOUT Parameters: date, time,applid, userid, tttt
CEDA to correct the network name and then reinstall the
definition.
Destination: CSMT DFHZC6330E date time applid Install for tttt failed. LDCLIST
Modules: DFHBSTZV parameter ldclist not found.
Explanation: A resource tttt was being installed but was
XMEOUT Parameters: date, time,applid, tttt, netname
found to have an invalid LDCLIST ldclist.
System action: The resource is not installed, CICS continues.
DFHZC6304W date time applid Deletion of remote terminal User response: If you want the definition to be installed, use
termid failed because it is in use by another the DFHTCT TYPE=LDCLIST macro to define the listname.
transaction. Destination: CSMT
Explanation: CICS has issued a logoff transaction to the Modules: DFHBSTBL
remote terminal termid but this terminal cannot be deleted
XMEOUT Parameters: date, time,applid, tttt, ldclist
because it is in use by another transaction.
System action: The remote terminal can be reused. CICS
continues. DFHZC6331E date time applid Install for connection tttt
User response: This situation usually occurs because the failed. Non-VTAM terminal with same name
remote CICS is under stress. Consider allocating more already exists.
resources. For example, you might need to allocate more Explanation: A connection tttt was being installed but a
storage. non-VTAM terminal with the same name already exists.
Destination: CSMT System action: The resource is not installed; CICS continues.
Modules: DFHBSTZ User response: Change the name of the connection and
reinstall.

Destination: CSMT Message DFHME0116 is normally produced containing the

Modules: DFHBSS symptom string for this problem.
User response: See the associated message for more
XMEOUT Parameters: date, time,applid, tttt guidance.
Destination: CADL
DFHZC6332E date time applid Install for terminal tttt failed. Module: DFHBSM61 DFHBSTZS
Non-VTAM terminal with same name already XMEOUT Parameters: date, time,applid, inmodule, bymodule
exists.
Explanation: A terminal tttt was being installed but a
non-VTAM terminal with the same name already exists. DFHZC6350I date time applid The type session name
System action: The resource is not installed; CICS continues. BITMAP was corrupt and has been rebuilt.
User response: Change the name of the terminal and Error code: AP FB05.
reinstall. Explanation: A connection was being installed but the APPC
Destination: CSMT or MRO session name BITMAP which is used to create a
Modules: DFHBSTZ session name, was corrupt. The corrupt BITMAP has been
rebuilt.
XMEOUT Parameters: date, time,applid, tttt
The APPC session name BITMAP is always used for an APPC
session, however the MRO session name BITMAP is only used
DFHZC6333E date time applid INSTALL for modename if the session name is prefixed with '<' or '>'.
modename failed. Zero sessions specified System action: A dump is taken with dumpcode ZC6350.
Explanation: CICS has not installed a mode group modename Trace point ID AP X'FB05' is produced. The install continues.
because the maximum number of sessions specified was 0. CICS continues.
The CEDA SESSION MAXIMUM parameter cannot be set to 0, User response: Use the dump provided to determine the
so this was possibly caused by a storage overwrite, or by an cause of the storage overwrite. See the CICS Problem
invalid builder parameter set being shipped into CICS. Determination Guide for guidance on dealing with storage
System action: The install fails, but CICS continues. problems.
User response: Find the offending builder parameter set and Destination: CSMT
set ZC_MAXSESS_1 to a minimum value of 1. Modules: DFHZGBM
Destination: CSMT
Modules: DFHBSM62 XMEOUT Parameters: date, time,applid, type

DFHZC6360W date time applid A GETMAIN failed to obtain
storage for a message set.
DFHZC6340E date time applid CICS has detected an error in Explanation: A ZCP install has failed. This would normally
delete processing for termid. Module name: result in a message being issued. However, the GETMAIN
modname. attempting to obtain storage from the CDSA for use as a
Explanation: CICS has found terminal input output areas message area has failed. This means that there is no more free
(TIOAs) chained to a TCTTE during deletion of a terminal. storage available in the CDSA.
This is a CICS logic error. System action: The message which should have reported the
System action: A system dump is taken, the TCTTE is ZCP install failure cannot be issued. Subsequent messages also
deleted and CICS continues. Message DFHME0116 is normally cannot be issued while there is no free storage available in the
produced containing the symptom string for this problem. CDSA. However, subsequent messages can be issued if storage
User response: You need further assistance from IBM to becomes available on subsequent GETMAIN attempts.
Determination Guide for guidance on how to proceed. Message DFHME0116 is normally produced containing the
It would aid IBM support if you used the system dump to User response: Use trace to determine the source of the
determine why TIOAs are still chained to the TCTTEs. The problem. Trace point AP FCDD, the TBSM entry, gives the
TIOAs are normally freemained before deletion. message number which should have been issued and the
Answers to the following questions would also be helpful: message insert data. Refer to the description of this message
v Is this is a shipped TCTTE? for further guidance.
v Why is the TCTTE being deleted? Destination: CSMT
v Is the correct TCTTE being deleted? Modules: DFHBSMSG
Destination: CADL XMEOUT Parameters: date, time,applid
Modules: DFHBST
XMEOUT Parameters: date, time,applid, termid, modname DFHZC6361E date time applid Install for {netname | console
| terminal }portname with userid userid failed
DFHZC6341E date time applid Loop or ABEND has been because the preset userid is invalid.
detected in inmodule by module bymodule. Explanation: The terminal could not be installed with preset
Explanation: CICS has previously detected a loop or abend. userid userid because the userid is not known to the external
Module bymodule called module inmodule which looped or security manager (ESM).
abended. System action: CICS continues.
System action: CICS issues message DFHZC0001 if an abend User response: Correct the userid, or contact your security
is detected or DFHZC0004 if a loop is detected. The install or administrator to have the unknown userid added to your
delete being performed is backed out. CICS continues. ESM. Then reinstall the terminal definition.

Destination: CSMT System action: CICS continues.

Modules: DFHBSTS User response: Contact your security administrator to restart
the ESM. Reinstall the terminal definition when the ESM is
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , active again.
3=terminal },portname, userid Destination: CSMT
Modules: DFHBSTS
DFHZC6362E date time applid Install for {netname | console XMEOUT Parameters: date, time,applid, {1=netname, 2=console ,
| terminal } portname with userid userid failed 3=terminal },portname, userid
because the preset userid has been revoked.
Explanation: The terminal could not be installed with preset
userid userid because the userid has been revoked by the DFHZC6366E date time applid Install for {netname | console
external security manager (ESM). | terminal } portname with userid userid failed
System action: CICS continues. because the userid is not authorized to access
User response: Contact your security administrator, who can this CICS system.
reauthorize the revoked userid by issuing the ALTUSER Explanation: The terminal could not be installed with a
RESUME function. Then reinstall the terminal definition. preset userid because the preset userid is not authorized to
Destination: CSMT use application applid.
Modules: DFHBSTS System action: CICS continues.
User response: Contact your security administrator, who can
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , authorize the preset userid to access the application applid.
3=terminal },portname, userid Then reinstall the terminal definition.
Destination: CSMT
DFHZC6363E date time applid Install for {netname | console Modules: DFHBSTS
| terminal } portname with userid userid failed XMEOUT Parameters: date, time,applid, {1=netname, 2=console ,
because the preset userid's group access has 3=terminal },portname, userid
been revoked.
userid userid because the access of that userid to the group DFHZC6367E date time applid Install for {netname | console
containing it has been revoked by the external security | terminal } termid with userid userid failed
manager (ESM). because the SECLABEL check failed.
System action: CICS continues. Explanation: The terminal could not be installed with preset
User response: Contact your security administrator, who can userid userid because the security label associated with the
restore the access of the preset userid to its group by issuing userid in the external security manager (ESM) does not have
the CONNECT RESUME function. Then reinstall the terminal the necessary authority.
definition. System action: CICS continues.
Destination: CSMT User response: Contact your security administrator to assign
Modules: DFHBSTS a new security label to the preset userid. Then reinstall the
terminal definition.
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , Destination: CSMT
3=terminal },portname, userid Modules: DFHBSTS
XMEOUT Parameters: date, time,applid, {1=netname, 2=console ,

DFHZC6364E date time applid Install for {netname | console 3=terminal },termid, userid
| terminal } portname with userid userid failed
because the ESM returned an unrecognized
response. DFHZC6368E date time applid Install for {netname | console
Explanation: The terminal could not be installed with preset | terminal } portname with userid userid failed
userid userid because of unexpected return codes from the because the external security manager is
external security manager (ESM). quiesced.
System action: CICS continues. Either message DFHSN1401 Explanation: The terminal could not be installed with preset
or DFHSN1801 is issued. userid userid because the external security manager (ESM) has
User response: See the accompanying message for further been placed in a “tranquil” state, and is not allowing new
guidance. Reinstall the terminal definition when you have users to be added to the system.
corrected the problem. System action: CICS continues.
Destination: CSMT User response: Contact your security administrator to
Modules: DFHBSTS establish when the ESM will be fully available again. When it
is, reinstall the terminal definition
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , Destination: CSMT
3=terminal },portname, userid Modules: DFHBSTS
XMEOUT Parameters: date, time,applid, {1=netname, 2=console ,
DFHZC6365E date time applid Install for {netname | console 3= terminal },portname, userid
| terminal } portname with userid userid failed
because the external security manager is
inactive.
userid userid because the external security manager (ESM) is
no longer active.

DFHZC6369E • DFHZC6904W
DFHZC6369E date time applid Install for {netname | console DFHZC6901W date time applid Autoinstall BIND for
| terminal } portname failed because national NETNAME netname is invalid. Internal
language langcode is invalid. RC:X'response'.
Explanation: The terminal could not be installed because the Explanation: The bind passed for AUTOINSTALL of a
national language langcode specified in the terminal definition resource has shown an error in the bind image check call. The
is not recognized. fixed part of the BIND is printed (this is the part on which the
System action: CICS continues. validation code operates — see the SNA Network Protocol
User response: Change the national language on the terminal Formats manual for details of the BIND RU). The internal
definition to a valid value and reinstall the terminal definition. return code X'code' identifies the location within the module
Destination: CSMT that invalidated the BIND.
Modules: DFHBSTS System action: CICS continues but the session is not
installed. The request is rejected and message DFHZC2411 is
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , issued. The terminal is not usable until a VTAM LOGOFF
3=terminal },portname, langcode
command is issued.
User response: Investigate the fixed part of the BIND data to
DFHZC6370E date time applid Install for {netname | console determine the reason for the rejection. The internal return code
| terminal } portname failed because national gives more information that can be used by IBM to help you
language langcode is unavailable. to determine the cause of the problem. See Part 4 of the CICS
Explanation: The terminal could not be installed because the Problem Determination Guide for guidance on how to proceed.
national language langcode specified in the terminal definition Destination: CADL
is not supported in this run of CICS. Modules: DFHZATA
System action: CICS continues. XMEOUT Parameters: date, time,applid, netname, X'response'
User response: Change the national language in the terminal
definition to one that has been initialized. Then reinstall the
terminal definition. DFHZC6902E date time applid Autoinstall failed because no
Destination: CSMT models are defined.
Modules: DFHBSTS Explanation: An attempt was made to AUTOINSTALL a
terminal; however there are no AUTOINSTALL models
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , defined.
3=terminal },portname, langcode System action: CICS processing continues, but the
AUTOINSTALL logon attempt is rejected.
DFHZC6371E date time applid Install for {netname | console User response: Use CEDA to define AUTOINSTALL
| terminal } portname with userid userid failed model(s). For information on this, refer to the CICS Resource
because the userid is not authorized to use Definition Guide.
this portname. Destination: CADL
Explanation: The terminal could not be installed with preset Modules: DFHZATA
userid userid because the specified userid is not authorized to XMEOUT Parameters: date, time,applid
use that terminal.
System action: CICS continues. Either message DFHSN1401
or DFHSN1801 is issued. DFHZC6903W date time applid Autoinstall for resource resid,
User response: See the accompanying message for further NETNAME netname using model-name model
guidance. Reinstall the terminal definition when you have failed.
corrected the problem. Explanation: TCTTE build process failed. The reason is given
Destination: CSMT in a following DFHZC59xx or DFHZC62xx message referring
Modules: DFHBSTS to the same termid. The message is followed by message
DFHZC6942.
XMEOUT Parameters: date, time,applid, {1=netname, 2=console , System action: Processing continues.
3=terminal },portname, userid User response: Refer to following messages for further
information.
DFHZC6598 applid VTAM Shutdown in XRF Alternate Destination: CADL
system. CICS will abend. sense ((instance) Modules: DFHZATA
Module name: {DFHZTPX}) XMEOUT Parameters: date, time,applid, resource, resid, netname,
Explanation: The TPEND exit has been driven because model
VTAM has been shutdown. This is an XRF alternate system
and it cannot continue without VTAM.
DFHZC6904W date time applid Autoinstall for NETNAME
For the meaning of the sense data, see the explanation on netname failed. CATA task abended (abend
topic “DFHZCxxxx messages” on page 356. abend).
System action: The system is abnormally terminated. Explanation: Transaction CATA, program DFHZATA was
User response: Determine why and how VTAM was autoinstalling a terminal of NETNAME netname, when the task
shutdown. abended with abend abend.
Destination: Console System action: CICS continues but the terminal is not
Modules: DFHZTPX installed.
XMEOUT Parameters: applid, sense,instance, {1=DFHZTPX} User response: Retry the logon attempt. If the abend
indicates a TIMEOUT and this occurs frequently, increase the
DTIMOUT value on the RDO TRANSACTION definition for

DFHZC6905W • DFHZC6912I
the CATA transaction. If you do not want the CATA Note that CFTS and CMTS do not have a DTIMOUT
transaction to time out, specify DTIMOUT(NO) on CATA's parameter and should not be given one because they only run
RDO TRANSACTION definition. However, if you do this, and once after a warm or emergency restart and should not be
if the system is short on storage, a large number of CATA allowed to time out.
transactions running at the some time with no other Destination: CADL
transactions present could cause a deadlock. Modules: DFHZATS
Destination: CADL
XMEOUT Parameters: date, time,applid, termid, tranid, abend
Modules: DFHZATA
XMEOUT Parameters: date, time,applid, netname, abend
DFHZC6910W date time applid Install for remote terminal
termid failed.
DFHZC6905W date time applid Autoinstall delete for terminal Explanation: An INSTALL for the remote terminal termid has
termid, NETNAME netname failed. CATD task failed. The reason for the failure is specified in associated
abended (abend abend). DFHZC59xx and DFHZC62xx messages.
Explanation: Transaction CATD, program DFHZATD was System action: DFHZATS terminates abnormally with a CICS
deleting an autoinstalled terminal termid, when the task transaction dump.
abended with abend abend. User response: See the associated messages for further
System action: CICS continues. If the TCTTE still exists, it is guidance.
reused next time the same TERMID is used. Destination: CADL
User response: See the description of abend abend for further Modules: DFHZATS
guidance.
If the abend indicates a TIMEOUT and this occurs frequently,
increase value of DTIMOUT on CATD's RDO TRANSACTION
definition. If you do not want the CATD transaction to time DFHZC6911W date time applid Delete for remote terminal
out, specify DTIMOUT(NO) on CATD's RDO TRANSACTION termid failed.
definition. However, a large number of CATD tasks running at Explanation: A DELETE for remote terminal termid has failed.
the same time with no purgeable tasks present could cause a Possible causes are that the terminal has already been deleted
deadlock if the system is also short on storage. or that it is in use by another task.
Destination: CADL If this message is repeated a number of times, there could be a
Modules: DFHZATD more serious problem.
XMEOUT Parameters: date, time,applid, termid, netname, abend System action: If the message is associated with message
DFHZC6912, CICS continues normally. If message DFHZC6912
is not issued, DFHZATS is abnormally terminated with a
DFHZC6906 date time applid Install or delete of remote transaction dump.
terminal termid failed. tranid task abended User response: If the message is associated with message
(abend abend). DFHZC6912, no action is necessary. If DFHZC6912 is not
Explanation: One of the functions of DFHZATS (transaction issued, see the associated DFHZC59xx and DFHZC62xx
CITS, CDTS, CMTS or CFTS) has abended with abend abend. messages for the reason for the DELETE failure.
System action: CICS continues. Destination: CADL
Modules: DFHZATS
For CITS (remote install), if the remote terminal (skeleton) was
actually built, CICS might use it. XMEOUT Parameters: date, time,applid, termid
For CDTS (remote delete), If the remote terminal (skeleton)
has not been deleted, it might be reused. DFHZC6912I date time applid Unable to delete remote
terminal.
For CMTS (remote mass delete), terminals which have not
Explanation: This message is issued during a mass delete of
been deleted by CMTS might be deleted at a later stage.
remote terminals following a warm or emergency restart. A
For CFTS (remote mass flag), terminals which have been terminal which had been flagged for deletion could not be
flagged for deletion might be deleted at a later stage. If any deleted. The most likely explanation is that the terminal has
terminals have not been flagged, attempts might be made to already been deleted by another task.
reuse them. This can have unpredictable results.
An associated DFHZC6911 message gives the identity of the
User response: See the description of abend abend for further
terminal. This might be associated with one or more
guidance.
DFHZC59xx and DFHZC62xx messages giving the reason for
The most likely reason for this message is a timeout of CITS the failure.
or CDTS. In the case of CITS, reissue your transaction if System action: Processing continues normally.
necessary. User response: See the associated messages for further
information.
If the TIMEOUTs occur frequently, consider increasing the Destination: CADL
value of the DTIMOUT on the CITS or CDTS RDO Modules: DFHZATS
TRANSACTION definition. If you do not want the
transactions to time out, specify DTIMOUT(NO) on the CITS XMEOUT Parameters: date, time,applid
or CDTS RDO TRANSACTION definition. However, a large
number of CITS tasks running at the same time with no
purgeable tasks present could cause a deadlock if the system
is also short on storage.

possible error within the user exit program. Check

DFHZC6913I date time applid Remote delete of terminal
for any abend codes that may have been issued.
termid failed. Terminal not found.
5 Loading of the user exit program failed for some
Explanation: A remote DELETE has been attempted for a
other reason. Check the DFHPGLU exit trace entry
terminal which has already been deleted by another task.
(PG 0A02) to see why the program manager was
unable to load the program.
Destination: CADL
Destination: CADL
Modules: DFHZGAI
Modules: DFHZATS
XMEOUT Parameters: date, time,applid, netname, x
DFHZC6921W date time applid Autoinstall for NETNAME

DFHZC6914E date time applid Autoinstall for Terminal
netname has been disallowed by the
termid, Netname netname failed. Bad Return
autoinstall control program. Code X'code'
Code (RC = X'retcode' ) from internal function
Explanation: An APPC connection not known to CICS has
call.
attempted to connect to CICS. However, the autoinstall control
Explanation: The TCTTE build process failed due to the
program has given a nonzero return code indicating that the
failure of an internal function call.
install cannot go ahead.
System action: The terminal autoinstall process fails. CICS
processing continues. If you do not support APPC autoinstall, the autoinstall control
User response: Retry the logon attempt. program (DFHZATDX is the default name) automatically
Destination: CADL returns a nonzero return code to disallow this function.
Modules: DFHZATA System action: The exception trace entry code shows the
parameter list for the autoinstall control program. The session
XMEOUT Parameters: date, time,applid, termid, netname,
is terminated. CICS continues.
X'retcode'
User response: The failure code X'code' is as follows:
X'FA07' If APPC autoinstall is not supported, use the
DFHZC6915E date time applid Unable to sign off remote netname to determine which device is attempting
terminal termid. Bad Return Code (RC = autoinstall.
X'snus_response' ) from signon domain call.
If APPC autoinstall is supported, examine the
Explanation: An unexpected response (INVALID, DISASTER
autoinstall control program to determine why it has
or EXCEPTION) has been received on a call by DFHZATS to
not set the return code to allow the install.
function SIGNOFF_TERMINAL_USER during signoff
Destination: CADL
processing for a remote terminal session running under CRTE.
Modules: DFHZGAI
System action: The terminal signoff process fails to complete
and the terminal user remains signed on. CICS processing XMEOUT Parameters: date, time,applid, netname, X'code'
continues.
User response: See the related message produced by the
domain that detected the original error. DFHZC6922E date time applid Parameter list error during
Destination: CADL autoinstall for NETNAME netname. Code
Modules: DFHZATS X'code'
Explanation: An APPC connection not known to CICS has
XMEOUT Parameters: date, time,applid, termid, X'snus_response' attempted to connect to CICS. However, the autoinstall control
program has returned an invalid parameter, or a parameter
that has led to an invalid template being used.
DFHZC6920E date time applid APPC autoinstall for
System action: The exception trace entry code shows the
NETNAME netname failed. RC x
parameter list for the autoinstall control program. The session
Explanation: An autoinstall attempt to install APPC
is terminated. CICS continues.
NETNAME netname has failed. The autoinstall program call to
User response: The failure code X'code' is one of the
the autoinstall control program failed with return code x.
following:
The return codes are mapped from the program manager X'FA08' No netname or sysid was supplied for the template.
LINK_URM response and reason. More precise reasons for Change the autoinstall control program to supply
failure can be obtained from trace point PG 0A02. either the netname or the sysid.
System action: CICS continues. X'FA09' The sysid for the new connection has invalid
User response: The appropriate response depends on the characters. It can only contain A-Z a-z 0-9 and $ # @
return code as follows: (where $ is X'5B'). Redefine the connection name in
1 The user exit program should be linked with the autoinstall control program.
AMODE(31). Ensure that the user exit is linked to X'FA0A' The sysid for the new connection already exists.
the correct AMODE. Change the autoinstall control program to supply a
2 The user exit program has no PPT entry. Ensure that unique name.
the PPT entry for the user exit program exists and is X'FA0B' CICS is unable to locate the supplied template
valid. netname. Change the autoinstall control program to
3 The user exit program could not be loaded. Ensure supply the correct template name, or use CEDA to
that the user exit program has the correct name and install the template connection.
is contained in one of the sublibraries of the LIBDEF X'FA0C' CICS is unable to locate the supplied template sysid.
4 The user exit program has abended. This is a

Change the autoinstall control program to supply XMEOUT Parameters: date, time,applid, netname, X'code'
the correct template sysid or use CEDA to install the
template connection.
X'FA0D' The template is not an APPC connection. Change the DFHZC6923E date time applid Unacceptable bind parameter
autoinstall control program to supply the correct during autoinstall for NETNAME netname.
template name, or use CEDA to reinstall the Code X'code'
template correctly. Explanation: CICS has received a BIND from an unknown
X'FA0E' The bind indicates that a parallel session connection APPC node. The autoinstall process was initiated, but an
is required. The template is a single session invalid bind parameter has been detected. The parameter in
connection. Change the autoinstall control program error is indicated by the failure code X'code' which is one of
to supply the correct template name, or use CEDA the following:
to reinstall the template correctly. X'FA18' There was no session instance ID field in the bind
X'FA0F' The bind indicates that a single session connection is user data.
required. The template is a parallel session X'FA19' There was no primary logical unit (PLU) name in
connection. Change the autoinstall control program the bind user data.
to supply the correct template name or use CEDA to X'FA1A' The PLU name in the bind user data is the same as
reinstall the template correctly. the LU name of this CICS.
X'FA10' The modename in the bind does not match the X'FA1B' Security information (an encryption seed) was
modename in the connection. expected, but not present, in the bind user data.
X'FA1C' Security information (an encryption seed) was found
For parallel sessions, the SNASVCMG modegroup is in the bind user data but its length was too high for
missing. The install for the template may have failed it to be valid.
- check for any CADL messages mentioning the X'FA1D' Security information (an encryption seed) was found
template name. The template connection may have in the bind user data when none was expected.
been corrupted. Try and re-install the template. X'FA1E' The received bind indicated that it was not
negotiable. This is not acceptable for an APPC
For single sessions, the user modegroup name does
connection.
not match. Change the autoinstall control program
X'FA1F' The received bind specified a primary RU size of
to supply the correct template name or use CEDA to
zero.
reinstall the template correctly.
X'FA20' The received bind specified a secondary RU size of
X'FA11' The program that attempted to INQUIRE on the
zero.
template has detected an error in the template and is
X'FA21' The received bind contained inconsistent access
unable to create a BPS with which to install the new
security indicators.
connection. This problem may be caused by a failure
X'FA22' Two security information fields (seed and nonce
in the initial install of the template. Check the
field) were found in the received BIND where only
console and CADL log to determine whether the
one was expected.
template installed correctly. Also, use CEMT to
X'FA23' The received BIND contained a nonce field with an
ensure that the CONNECTION is correct.
incorrect length.
X'FA12' The program that attempted to INQUIRE on a user
X'FA24' The received BIND did not contain a nonce field.
modegroup for the named template has detected an
X'FA25' The received BINDs security mechanisms field
error in the template and is unable to create a BPS
length was smaller than the minimum defined by
with which to install a user modegroup. This
the Architecture.
problem may be caused by a failure in the initial
X'FA26' The received BINDs security mechanisms field
install of the template. Check the console and CADL
contained an invalid length for the mechanism
log to determine whether the template installed
identifier field.
correctly. Also use CEMT to ensure that the
System action: The exception trace entry with trace point ID
MODEGROUP is correct.
'AP xxxx' (where xxxx is X'code') shows the bind that was
X'FA13' The template connection has no user modegroup.
received. The session is terminated. CICS continues.
This problem may be caused by a failure in the
User response: Change the definitions on the connecting LU
initial install of the template. Check the console and
so that the bind parameters are acceptable to CICS.
the CADL log to determine whether the template
Destination: CADL
installed correctly. Also, use CEMT to ensure that
Modules: DFHZGAI
the MODEGROUP is correct.
X'FA14' The template connection is out of service so this XMEOUT Parameters: date, time,applid, netname, X'code'
install cannot continue. If the install should have
been allowed to continue, put the relevant template
connection INSERVICE using CEMT. DFHZC6935I date time applid Autoinstall for restype resid
X'FA15' The incoming bind user data does not have a with NETNAME netname using model or
PLUNAME Network Name subfield (id 04). This is template model successful.
required and should have been supplied by the Explanation: CICS has successfully installed resource restype
PLU. resid, with NETNAME netname, using model or template
X'FA16' The incoming bind user data does not have a model. restype can be TERMINAL or CONNECTION
MODENAME Network Name subfield (id 02). This depending on whether a terminal or APPC connection has just
is required and should have been supplied by the been autoinstalled.
PLU. System action: CICS continues.
Destination: CADL User response: None.
Modules: DFHZGAI Destination: CADL
Modules: DFHZATA

DFHZC6936I • DFHZC6944W
XMEOUT Parameters: date, time,applid, restype, resid, netname, requests. The first point of failure may be at offset or before it
model since CICS verification checks are permissive.
If the format is incorrect, the origin of the invalid CINIT
DFHZC6936I date time applid Autoinstall for NETNAME should be tracked and the problem resolved there.
netname, model_name modelname in MTS
If the format is correct, this is a CICS logic error. In this case
control vector not known to CICS.
Explanation: The VTAM MTS control vector contained a
model name modelname not defined to CICS.
proceed.
System action: CICS continues. This message is
Destination: CADL
informational.
Modules: DFHZATA
User response: There are four possible ways of correcting
this problem: XMEOUT Parameters: date, time,applid, netname, nn, offset
v Use the CEDA transaction to define and install the
autoinstall model
v Change the VTAM MTS MDLTAB MODEL= entry to the DFHZC6942W date time applid Autoinstall for resource resid
name of an existing autoinstall model failed.
v Logon to CICS with a MODEL= parameter that defines an Explanation: An AUTOINSTALL attempt to install terminal
existing autoinstall model. termid has failed.
v Code an autoinstall user program. Examples are given in System action: CICS continues.
the CICS Customization Guide. User response: For the cause of the failure, look for a
Destination: CADL previous message containing the same termid.
Modules: DFHZATA Destination: CADL
Modules: DFHZATA
XMEOUT Parameters: date, time,applid, netname, modelname
XMEOUT Parameters: date, time,applid, resource, resid
DFHZC6937I date time applid Autoinstall for NETNAME

netname, MTS model modelname and bind DFHZC6943W date time applid Autoinstall delete for terminal
image mismatch. termid, NETNAME netname failed.
Explanation: An autoinstall attempt occurred using the Explanation: An AUTOINSTALL attempt to delete terminal
modelname printed. The MODEL BIND (from the CICS model termid has failed.
definition) did not match with the incoming bind in CINIT. System action: CICS continues.
The MISMATCH_BITS show which bind bits did not match. User response: For the cause of the failure, look for a
System action: CICS continues. previous message containing the same termid.
User response: There are four possible ways of correcting Destination: CADL
this problem: Modules: DFHZATD
v Change the CICS autoinstall MODEL modelname to produce XMEOUT Parameters: date, time,applid, termid, netname
a bind that matches the incoming CINIT.
v Change the MTS MDLTAB MODEL= entry to a model name
defined to CICS whose bind matches the CINIT defined in DFHZC6944W date time applid Autoinstall for NETNAME
the LOGMODE for this terminal. netname failed with RC= x
v Change the VTAM LOGMODE for this terminal to match Explanation: An autoinstall attempt to install terminal termid
the chosen CICS MODEL_BIND. has failed. The Autoinstall program call to the user exit
v Code an autoinstall user program. Examples are given in program failed with return code x.
the Sample Programs and Copybooks section of the CICS System action: CICS continues.
Customization Guide. User response: Possible causes of the problem and an
Destination: CADL indication of how to solve them are given in the following list
Modules: DFHZATA of return code meanings:
1 The user exit program should be linked with
XMEOUT Parameters: date, time,applid, netname, modelname
AMODE(31). Ensure that the user exit is linked to
the correct AMODE.
DFHZC6939W date time applid Autoinstall for NETNAME 2 The user exit program has no PPT entry. Ensure that
netname, Invalid length nn found in cinit the PPT entry for the user exit program exists and is
control vector at offset offset valid.
Explanation: CICS verification checks on the format of the 3 The user exit program could not be loaded. Ensure
control vectors in the CINIT have failed. that the user exit program has the correct name and
is contained in one of the sublibraries of the LIBDEF
offset indicates the first point of failure. This is either a length search chain for the CICS startup job stream. name.
field greater than 128, or a length field which would cause 4 The user exit program has abended. This is a
CICS to overrun the end of a CINIT vector or subvector. possible error within the user exit program. Check
This is either due to incorrect format of the CINIT RU (and for any abend codes that may have been issued.
therefore probably a VTAM logic error), or due to incorrect Destination: CADL
parsing of the CINIT RU by DFHZATD, which is a CICS logic Modules: DFHZATA
error. XMEOUT Parameters: date, time,applid, netname, x
System action: CICS continues. The logon request is rejected.
User response: Inspect the format of the CINIT RU as
captured by the autoinstall program for all rejected logon

DFHZC6945W • DFHZC6958W
Return Code
DFHZC6945W date time applid Autoinstall delete for
Meaning and Solution
NETNAME netname failed with RC= x
1 The user exit program is not linked with
Explanation: An autoinstall attempt to install terminal termid
has failed. DFHZATA called the user exit program for
the correct AMODE.
DELETE but the user exit failed for reasons given in return
2 The user exit program has no PPT entry. Ensure that
code x.
the PPT entry for the user exit program exists and is
valid.
User response: Possible causes of the problem and an
3 The user exit program could not be loaded. Ensure
indication of how to solve them are given in the following list
that the user exit program has the correct name and
of return code meanings:
1 The user exit program should be linked with
4 The user exit program has abended. This is a
the correct AMODE.
possible error within the user exit program. Check
2 The user exit program has no PPT entry. Ensure that
for any abend codes that may have been issued.
the PPT entry for the user exit program exists and is
Destination: CADL
valid.
Modules: DFHZATS
3 The user exit program could not be loaded. Ensure
that the user exit program has the correct name and XMEOUT Parameters: date, time,applid, termid, x
4 The user exit program has abended. This is a DFHZC6951W date time applid Autoinstall for terminal termid
possible error within the user exit program. Check failed with RC= x.
for any abend codes that may have been issued. Explanation: An autoinstall attempt to install terminal termid
Destination: CADL has failed. The autoinstall program call to the user exit
Modules: DFHZATA program failed with return code x.
XMEOUT Parameters: date, time,applid, netname, x User response: Possible causes of the problem and an
indication of how to solve them are as follows:
DFHZC6946W date time applid Delete user exit for Return Code
autoinstalled terminal termid, NETNAME Meaning and solution
netname failed with RC= x 1 The user exit program is not linked with
Explanation: CICS has deleted the autoinstalled terminal AMODE(31). Ensure that the user exit is linked to
termid. The call to the delete user exit program failed for the correct AMODE.
reasons given in return code x. 2 The user exit program has no PPT entry. Ensure that
System action: CICS continues. the PPT entry for the user exit program exists and is
User response: Possible causes of the problem and an valid.
indication of how to solve them are given in the following list 3 The user exit program could not be loaded. Ensure
of return code meanings: that the user exit program has the correct name and
1 The user exit program should be linked with is contained in one of the sublibraries of the LIBDEF
AMODE(31). Ensure that the user exit is linked to search chain for the CICS startup job stream.
the correct AMODE. 4 The user exit program has abended. This is a
2 The user exit program has no PPT entry. Ensure that possible error within the user exit program. Check
the PPT entry for the user exit program exists and is for any abend codes that may have been issued.
valid. Destination: CADL
3 The user exit program could not be loaded. Ensure Modules: DFHZATMD
that the user exit program has the correct name and
is contained in one of the sublibraries of the LIBDEF XMEOUT Parameters: date, time,applid, termid, x
4 The user exit program has abended. This is a DFHZC6958W date time applid Autoinstall for NETNAME
possible error within the user exit program. Check netname, terminal X'termid' failed.
for any abend codes that may have been issued. {TERMINAL | PRINTER | ALTPRINTER}
Destination: CADL ID is invalid. RC=n.
Modules: DFHZATD Explanation: The terminal, printer or altprinter ID supplied
XMEOUT Parameters: date, time,applid, termid, netname, x by the AUTOINSTALL exit program is invalid. The return
code n can be one of the following:
1 Invalid blank in column one
DFHZC6950W date time applid Autoinstall for terminal termid 2 Invalid imbedded blank
failed with RC= x. 3 Invalid character used.
Explanation: An autoinstall attempt to install terminal termid System action: CICS continues but does not install the object.
has failed. The autoinstall program call to the user exit User response: Change the AUTOINSTALL exit program to
program failed with return code x. create IDs that contain only valid characters. These are
System action: CICS continues. specified in the CICS Resource Definition Guide.
User response: Possible causes of the problem and an Destination: CADL
indication of how to solve them are as follows: Modules: DFHZATA
XMEOUT Parameters: date, time, applid, netname, X'termid',

DFHZC6966I • DFHZN2101
{1=TERMINAL, 2=PRINTER, 3=ALTPRINTER}, n mismatch in that position between the BIND image from
VTAM and the BIND image associated with the model.
DFHZC6966I date time applid Autoinstall delete for restype User response:
resid with NETNAME netname successful. 1. Determine whether the model model is suitable. If there are
Explanation: CICS has successfully deleted the autoinstalled several models which have options, such as
resource restype resid. The resource type restype can be a TRANSECKEYS, then only the first such model is named
terminal or an APPC connection. in the above message. It will be up to the user-program to
System action: CICS continues. make the choice, when the logmode table entry is
User response: None. corrected.
Destination: CADL 2. Identify the entry in the VTAM logmode table that is being
Modules: DFHZATD used.
XMEOUT Parameters: date, time,applid, restype, resid, netname 3. Check that this logmode table entry is not successfully in
use with other applications, so that to change it might
cause this other use of it to fail.
DFHZC6987W date time applid Autoinstall best failure for 4. Amend the logmode table entry by switching the bits
NETNAME netname was model_name model. corresponding to '1' bits in the mismatch string. That is, if
Explanation: An autoinstall attempt has failed for lack of an the bit in the VTAM bind image corresponding to the bit
exact match. position set to '1' in xxxxxxxx... is '1', set it to '0'. If it is '0',
set it to '1'.
netname is the netname of the LU which failed to logon,
model is the name of the model that gave the best failure (that For further information, refer to the CICS Customization Guide.
is, the one that had the fewest bits different from the BIND
image supplied by VTAM). More on the meaning of the various bits in a bind image may
The following associated information is also written to CADL: be found in VTAM Programming manual.
xxxxxxxx... is a string of hexadecimal digits, where xx
represents one byte, and each byte position represents the Details of the preparation of VTAM logmode table entries are
corresponding byte position in the BIND image. given in VTAM Resource Definition Reference manual.
CINIT BIND: xxxxxxxx is the bind image supplied by Destination: CADL
VTAM. Modules: DFHZATA
MODEL BIND: xxxxxxxx is the best model. XMEOUT Parameters: date, time,applid, netname, model
MISMATCH BITS: xxxxxxxx represents a comparison of the
relevant bits from above. A bit set to '1' indicates a
DFHZExxxx messages
DFHZE2600 Syst.sense systsense,termid,taskid, Unidentified DFHZE2604 Syst.sense 0811,termid,taskid, Unprocessed data
sense information at detach
Explanation: The error message writer (DFHEMW) was Explanation: The task to be detached did not completely
scheduled to send an error message, but could not identify the process the inbound data chain.
system sense code. System action: Purging of data is done until end-of-chain
System action: The task is abnormally terminated. (EOC) or CANCEL has been received.
User response: Refer to the associated messages that were User response: None.
issued previously for further information and guidance. Module: DFHZDET
Module: DFHZEMW Destination: Terminal End User
DFHZNxxxx messages
DFHIR2124 (for an MRO link).
DFHZN2101 date time applid Intersystem session failure.
Data base changes may be out of sync. Time The original failure information provides correlation between
time. Remote system=sysid. Intersystem this message and its follow-up. UOWID's can be used to
terminal=termid. Transaction=tranid. Task correlate these messages with journal records indicating the
number=taskno. Operator terminal=termid. resources which may be out of synchronization. UOWID's are
Operator=operid. Unit of work ID=uowid. not transmitted across LU6.1 connections.
(Module name:xxxx) System action: Processing continues.
Explanation: An intersystem session failed at a critical time
User response: Take user-defined action, if any, to protect
during sync point processing. It may be that one side
data integrity until the remote and the local data can be
completed and the other side backed out, leaving changes out
synchronized.
of synchronization. This is checked for at session recovery, and
Module: DFHSPP, DFHTCBP
one of the following messages is issued:
DFHZN2102 XMEOUT Parameters: date, time,applid, time, sysid, termid,
DFHZN2103 tranid, taskno, termid,operid, uowid, xxxx
DFHZN2104 Destination: CSMT
DFHIR2122 (for an MRO link)
DFHIR2123 (for an MRO link)

DFHZN2102 • DFHZN2107
Destination: CSMT
DFHZN2102 date time applid Intersystem session recovery.
Data base changes found to be synchronized.
Original failure details: time. Remote DFHZN2105 date time applid Intersystem session failure.
system=sysid. Intersystem terminal=termid. Data base changes will not be committed or
Transaction=tranid. Task number=taskno. backed out until session recovery. Time=time.
Operator terminal=termid. Operator=operid. Remote system=sysid. Intersystem
Unit of work ID=uowid. (Module name:xxxx) terminal=termid. Transaction=tranid. Task
Explanation: Intersystem session recovery has been number=taskno. Operator terminal=termid.
successful. An error occurred on an intersystem session Operator=operid. Unit of work ID=uowid.
recovery which has now been successfully recovered and (Module name: xxxx)
resynchronized. This message is normally issued as a Explanation: An intersystem session failed at a critical time
follow-up to message DFHZN2101, which may have been during sync point processing. The local system has no
issued at the time of the failure (if the session failed at a information as to whether the remote system committed or
critical time during syncpoint processing). backed out. The local changes will, therefore, be held locked
System action: Processing continues. until session recovery. They will then be committed or backed
User response: None. out, according to the action of the other system. One of the
Module: DFHSPP following messages will be issued: DFHZN2106, DFHZN2107
XMEOUT Parameters: date, time,applid, time, sysid, termid, or DFHZN2108. The original failure information provides
tranid, taskno, termid,operid, uowid, xxxx correlation between this message and its follow-up.
Destination: CSMT System action: Locks on local recoverable changes are
preserved.
User response: Reacquire the session as soon as possible.
DFHZN2103 date time applid Intersystem session recovery. Module: DFHTCBP, DFHSPP
Data base changes found to be out of sync.
Original failure details: time. Remote
tranid, taskno, termid,operid, uowid, xxxx
system=sysid. Intersystem terminal=termid.
Destination: CSMT
Transaction=tranid. Task number=taskno.
Unit of work ID=uowid. (Module name:xxxx) DFHZN2106 date time applid Intersystem session recovery.
Explanation: Resynchronization has diagnosed that the local Suspended changes now being committed.
resources associated with the logical unit of work are out of Original failure details: Time= time. Remote
synchronization with remote resources. system=sysid. Intersystem terminal=termid.
This message may be issued as a follow-up to message Transaction=tranid. Task number=taskno.
DFHZN2101. Operator terminal=termid. Operator=operid.
System action: Processing continues. Unit of work ID=uowid. (Module name:xxxx)
User response: Take user-defined action to resynchronize the Explanation: This is an informatory message issued during
local and remote databases. intersystem session recovery as a follow-up to message
Module: DFHSPP DFHZN2105. It has now been established that the remote
system completed the sync point, so the local changes are
XMEOUT Parameters: date, time,applid, time, sysid, termid, being committed accordingly.
tranid, taskno, termid,operid, uowid, xxxx System action: The system commits local changes and
Destination: CSMT unlocks.
Module: DFHSPP
DFHZN2104 date time applid Intersystem session recovery
error. Data base changes may be out of sync. XMEOUT Parameters: date, time,applid, time, sysid, termid,
Original failure details: time. Remote tranid, taskno, termid,operid, uowid, xxxx
system=sysid. Intersystem terminal=termid. Destination: CSMT
Transaction=tranid. Task number=taskno.
Unit of work ID=uowid. (Module name:xxxx) DFHZN2107 date time applid Intersystem session recovery.
Explanation: This error can be caused by: Suspended changes now being backed out.
v An invalid combination of LUW states at the local and Original failure details: Time= time. Remote
remote systems, or system=sysid. Intersystem terminal=termid.
v A decision to preempt resynchronization activity taken at Transaction=tranid. Task number=taskno.
the local system by setting a connection, NOTPENDING.
Unit of work ID=uowid. (Module name: xxxx)
This message may be issued as a follow-up to message Explanation: This message is issued at intersystem session
DFHZN2101 when the system has been unable to discover recovery as a follow-up to message DFHZN2105. It has now
whether database changes are out of synchronization during been established that the remote system sysid did not complete
session recovery. the unit of work. Local changes are being backed out
System action: Processing continues. accordingly.
User response: Make the necessary database enquiries to System action: The system backs out local changes and
detect whether changes are synchronized. If they are not, take unlocks.
User response: If required, restart the interrupted transaction
user-defined action to resynchronize the databases.
tranid.
Module: DFHSPP
Module: DFHSPP

Destination: CSMT
DFHZN2111 date time applid Cold/Warm restart mismatch
with system sysid.
DFHZN2108 date time applid Intersystem session recovery. Explanation: A cold start indication was received in a reply
Error while local recoverable changes are to an exchange log name command. However, this system has
suspended. Original failure details: Time= units of work that need resynchronizing from the previous
time. Remote system=sysid. Intersystem run. An exchange log name command is sent either following
terminal=termid. Transaction=tranid. Task a session failure or at first session initiation after system
number=taskno. Operator terminal=termid. restart.
Operator=operid. Unit of work ID=uowid. System action: Any sync point level 2 attaches are inhibited.
(Module name: xxxx) This means that recoverable activity between the two systems
Explanation: This message is issued at intersystem session is prevented.
recovery as a follow-up to message DFHZN2105. User response: There are two ways to solve this problem:
Resynchronization failed. Therefore it still cannot be v Emergency restart the remote system with the correct
established whether the remote system sysid committed or system log.
backed out. v Override the error situation by issuing CEMT SET
System action:
CONN(xxxx) NOTPENDING commands for the failing
1. The locks on the suspended changes are released to allow
connection.
access by a user transaction.
2. Any associated suspended start commands are canceled to
prevent premature action. Note: If this command is issued, CICS unilaterally commits
User response: Examine the data to see whether the local any resources which may be waiting for APPC
and remote changes made by the interrupted transaction took resynchronization. In addition, CICS does not carry out any
effect. Make any changes required to restore consistency. APPC resynchronization activity with the remote system.
Module: DFHSPP Module: DFHSPP
XMEOUT Parameters: date, time,applid, time, sysid, termid, XMEOUT Parameters: date, time,applid, sysid
tranid, taskno, termid,operid, uowid, xxxx Destination: Console and Transient Data Queue CSMT
Destination: CSMT
DFHZN2112 date time applid Log name mismatch with
DFHZN2110 date time applid Abnormal reply to exchange system sysid Expected LUNAME.LOGNAME
log name command received from system: xxxx Received LUNAME.LOGNAME yyyy.
xxxxxx. Explanation: This system's memory of the other system's log
Explanation: This message is issued when an abnormal reply name conflicts with the log name being used for
has been received in response to an exchange log name resynchronization.
command. An exchange log name command is sent either System action: Any sync point level 2 attaches are inhibited.
following a session failure or at first session initiation after This means that recoverable activity between the two systems
system restart. The abnormal reply may indicate that the other is prevented.
system detected a warm/cold mismatch or a log name User response: There are two ways to solve this problem:
mismatch. v Emergency restart the remote system with the correct
System action: Any sync point level 2 attaches are inhibited. system log.
This means that recoverable activity between the two systems v Override the error situation by issuing CEMT SET
is prevented. CONN(xxxx) NOTPENDING commands for the failing
User response: Ensure that neither system was cold-started connection.
(as opposed to emergency restarted or its equivalent) and that
the correct log was used. Note: If this command is issued, CICS unilaterally commits
any resources which may be waiting for APPC
There are two ways to solve this problem: resynchronization. In addition, CICS does not carry out any
v Ensure that both systems are emergency restarted with the APPC resynchronization activity with the remote system.
correct system logs. Module: DFHSPP
v Override the error situation by issuing CEMT SET
CONN(xxxx) NOTPENDING commands for the failing XMEOUT Parameters: date, time,applid, sysid, xxxx, yyyy
connection. It may be necessary to issue this command on Destination: Console and Transient Data Queue CSMT
both sides of the connection.
DFHZN2113 date time applid Log name mismatch with
Note: If this command is issued, CICS unilaterally commits system xxxx. Local LOGNAME yyyy.
any resources which may be waiting for APPC Received LOGNAME zzzz.
resynchronization. In addition, CICS does not carry out any Explanation: System xxxx has sent an exchange log names
APPC resynchronization activity with the remote system. request which contains the remote system's memory (zzzz) of
Module: DFHSPP this system's logname (yyyy).
XMEOUT Parameters: date, time,applid, xxxxxx This system has detected a logname mismatch. This indicates
Destination: Console and Transient Data Queue CSMT that system xxxx and this system do not have the correct logs
for resynchronization.
System action: The local system sends an abnormal exchange
log names reply in response to the request. Any sync level 2
attaches are inhibited. That is, recoverable activity between the
two systems is prevented.

User response: There are two ways to solve this problem: the intention of committing as many synclevel 1 resources as
v Ensure that both systems are emergency restarted with the possible. For APPC synclevel 1, CICS does not attempt to
correct system logs. resolve the situation any further.
v Override the error situation by issuing CEMT SET
On completion of the syncpoint, CICS abends the user task
with abend code ASPK.
connection. It may be necessary to issue this command on
User response: The action to take depends on local
procedures and the design of the application program. For
example, it may be possible to rerun the application but only
Note: If this command is issued, CICS unilaterally commits making updates to remote resources. Refer to the CICS
any resources which may be waiting for APPC Intercommunication Guide for information on design
resynchronization. In addition, CICS does not carry out any considerations in a distributed environment.
APPC resynchronization activity with the remote system. Module: DFHSPZ
Module: DFHSPP
XMEOUT Parameters: date, time,applid, xxxx, yyyy, zzzz tranid, taskno, termid,operid, xxxx
Destination: Console and Transient Data Queue CSMT Destination: CSMT
DFHZN2131 date time applid Intersystem session failure

DFHZN2133 date time applid Error detected during CICS
during CICS synclevel one commit. Data
synclevel one commit. Reason code rc. Data
base changes may be out of sync. Time time.
base changes may be out of sync. Time time.
Remote system=sysid. Intersystem
Remote system=sysid. Intersystem
terminal=termid. Transaction=tranid. Task
terminal=termid. Transaction=tranid. Task
Operator=operid. (Module name:xxxx)
Operator=operid. (Module name:xxxx)
Explanation: A CICS application has been using APPC
synclevel 1 to process remote function shipped resources. The
application took a syncpoint, either implicitly or explicitly, and
this has caused all local resources and synclevel 2 partners to
be committed. However, a session failure occurred at a critical
be committed. However, when a commit message was sent to
time during the synclevel 1 commit processing, and the
a synclevel 1 function shipped resource, the reply indicated
synclevel 1 function shipped resources may have committed
that an error has occurred. The reason code provides details of
successfully or may have backed out.
the error and has the following values:
System action: CICS synclevel 1 commit processing
01 Protocol violation by partner system – unexpected
continues, with the intention of committing as many synclevel
FMH data
1 resources as possible. For APPC synclevel 1, CICS does not
02 Protocol violation by partner system – unexpected
attempt to resolve the situation any further.
syncpoint message data
On completion of the syncpoint, CICS abends the user task 03 Abend received
with abend code ASPK. 04 Deadlock or read timeout.
User response: Determine whether the remote function System action: CICS synclevel 1 commit processing
shipped resources are out of synchronization. The action to continues, with the intention of committing as many synclevel
take depends on local procedures and the design of the 1 resources as possible.
application program. For example, it may be possible to rerun
For reason code 01, a transaction dump with dump code ASPI
the application but only making updates to remote resources. is taken. For reason code 02, a transaction dump with dump
Refer to the CICS Intercommunication Guide for information on
code ASPJ is taken. On completion of the syncpoint, CICS
design considerations in a distributed environment.
abends the user task with abend code ASPK.
Module: DFHSPZ
User response: The action to take depends on local
XMEOUT Parameters: date, time,applid, time, sysid, termid, procedures.
tranid, taskno, termid,operid, xxxx For reason codes 01 and 02, examine the dump to determine
Destination: CSMT
what message data was received from the partner. This
information is held in one of the terminal input/output areas.
DFHZN2132 date time applid Rollback received in response A failure in the communication system might have caused
to CICS synclevel one commit. Data base corruption of the data.
changes are out of sync. Time time. Remote Reason code 03 indicates that the partner system has sent an
system=sysid. Intersystem terminal=termid. abend. There is an error in the partner system which may
Transaction=tranid. Task number=taskno. need to be investigated.
(Module name:xxxx) Reason code 04 indicates that the partner system took too long
Explanation: A CICS application has been using APPC to respond to the synclevel 1 commit. There could be a
synclevel 1 to process remote function shipped resources. The problem with the remote system, or the communication
application took a syncpoint, either implicitly or explicitly, and system. It may be necessary to increase the deadlock timeout
this has caused all local resources and synclevel 2 partners to or read timeout values to prevent this recurring.
be committed. However, when a commit message was sent to Module: DFHSPZ
a synclevel 1 function shipped resource, the resource voted to
XMEOUT Parameters: date, time,applid, rc, time, sysid,termid,
backout.
tranid, taskno, termid, operid, xxxx
System action: Synclevel 1 commit processing continues with

Destination: CSMT Examine the log of the remote system. If a protocol violation
was detected in the local system's exchange log names GDS
variable, the remote system may have generated diagnostic
DFHZN2134 date time applid An error has occurred while information itself. This information may help to diagnose the
sending an Exchange Log Names request on cause of the protocol violation.
session sessid to remote system sysid. Module: DFHSPZ
Explanation: An error has occurred during the transmission
of an exchange log names request to a remote system. CICS XMEOUT Parameters: date, time,applid, sessid, sysid
was attempting to resynchronize distributed resources Destination: Console and Transient Data Queue CSMT
following an earlier failure of a protected conversation during
sync point processing.
DFHZN2135 date time applid An error has occurred while
This implies one of the following: sending a Compare States request on session
v The remote system has detected a protocol violation in the sessid to remote system sysid.
local system's exchange log names generalized data stream Explanation: An error has occurred during the transmission
(GDS) variable. of a compare states request to a remote system. CICS was
v There has been an internal error in CICS APPC processing. attempting to resynchronize distributed resources following an
System action: A system dump is taken, unless you have earlier failure of a protected conversation during sync point
specifically suppressed dumps in the dump table. processing.
Message DFHME0116 is normally produced containing the This implies one of the following:
symptom string for this problem. v The remote system has detected a protocol violation in the
local system's exchange log names GDS variable.
In many cases, CICS continues to operate normally, and the v The remote system has detected a protocol violation in the
resynchronization attempt is retried at the next opportunity. local system's compare states GDS variable.
However, the failure may have resulted in no exchange log v There has been an internal error in CICS APPC processing.
names flows being successful, preventing any synclevel 2 System action: A system dump is taken, unless you have
attaches between the local system and the remote system. specifically suppressed dumps in the dump table.
User response: Issue CEMT INQUIRE CONN(xxxx), and look
at the XOK field. If exchange log names has not been done, Message DFHME0116 is normally produced containing the
the error situation can be overridden by issuing CEMT SET symptom string for this problem.
In many cases, CICS continues to operate normally, and the
resynchronization attempt is retried at the next opportunity.
However, the failure may have resulted in no exchange log
names flows being successful, preventing any synclevel 2
Note: If this command is issued, CICS unilaterally commits attaches between the local system and the remote system.
any resources which may be waiting for APPC User response: Issue CEMT INQUIRE CONN(xxxx), and look
resynchronization. In addition, CICS does not carry out any at the XOK field. If exchange log names has not been done,
APPC resynchronization activity with the remote system. the error situation can be overridden by issuing CEMT SET
Investigate the cause of the error using the system dump and CONN(xxxx) NOTPENDING commands for the failing
any previously output diagnostic information provided by connection. It may be necessary to issue this command on
CICS, the access methods or the operating system. both sides of the connection.
Format the system dump to show the control blocks belonging Note: If this command is issued, CICS unilaterally commits
to the trace domain and the terminal control program. (For any resources which may be waiting for APPC
guidance on how to do this, see the CICS Problem resynchronization. In addition, CICS does not carry out any
Determination Guide.) APPC resynchronization activity with the remote system.
Investigate the cause of the error using the system dump and
Determine from the message which APPC session was being any previously output diagnostic information provided by
used for this exchange log names conversation. CICS, the access methods or the operating system.
If the internal trace table is available, use it to track the Format the system dump to show the control blocks belonging
commands issued against that session, and check that the state to the trace domain and the terminal control program. (For
transitions of the User state machine are correct. If any of the guidance on how to do this, see the CICS Problem
state transitions are not valid, it is possible that there has been Determination Guide.)
a CICS logic error.
Determine from the message which APPC session was being
The APPC send and receive buffers for a session are clearly used for this compare states conversation.
labelled in the dump and are printed below the TCTTE for the
session to which they belong. Locate the send/receive buffer If the internal trace table is available, use it to track the
for the session in question, and check that the contents of the commands issued against that session, and check that the state
buffer are correct. The contents of the buffer differ depending transitions of the user state machine are correct. If any of the
on the exact point the error is detected, but may contain the state transitions are not valid, it is possible that there has been
attach FMH5, and the exchange log names GDS variable. The a CICS logic error.
correct format of these SNA defined fields can be found in the
SNA Formats manual.
The APPC send and receive buffers for a session are clearly

session to which they belong. Locate the APPC send/receive If the internal trace table is available, use this to track the
buffer for the session in question, and check that the contents commands issued against that session, and check that the state
of the buffer are correct. The contents of the buffer differ transitions of the User state machine are correct. If any of the
depending on the exact point the error is detected, but may state transitions are not valid, it is possible that there has been
contain the attach FMH5, the exchange log names GDS a CICS logic error.
variable, and the compare states GDS variable. The correct
format of these SNA defined fields can be found in the SNA The APPC send and receive buffers for a session are clearly
Formats manual. labelled in the dump and are printed below the TCTTE for the
session to which they belong. Locate the APPC send/receive
Examine the log of the remote system. If a protocol violation buffer for the session in question, and check that the contents
was detected in the local system's resynchronization data, the of the buffer are correct. The contents of the buffer differ
remote system may have generated diagnostic information depending on the exact point at which the error is detected,
itself. This information may help to diagnose the cause of the but may contain the attach FMH5, the exchange log names
protocol violation. GDS variable, and the compare states GDS variable. The
Module: DFHSPZ correct format of these SNA defined fields are in the SNA
Formats manual.
XMEOUT Parameters: date, time,applid, sessid, sysid
Examine the log of the remote system. If a protocol violation
was detected in the local system's resynchronization data, the
DFHZN2136 date time applid An error has occurred while remote system may have generated diagnostic information
receiving an Exchange Log Names reply on itself. This information may help to diagnose the cause of the
session sessid from remote system sysid. protocol violation.
Explanation: An error has occurred during the receipt of an Module: DFHSPZ
exchange log names reply from a remote system. CICS was
attempting to resynchronize distributed resources following an
earlier failure of a protected conversation during sync point
processing.
DFHZN2137 date time applid An error has occurred while
This implies one of the following:
receiving a Compare States reply on session
v The remote system has detected a protocol violation in the
sessid from remote system sysid.
Explanation: An error has occurred during the receipt of a
compare states reply from a remote system. CICS was
local system's compare states GDS variable.
attempting to resynchronize distributed resources following an
v There has been an internal error in CICS APPC processing.
System action: A system dump is taken, unless you have
processing.
This implies one of the following:
In many cases, CICS continues to operate normally, and the v The remote system has detected a protocol violation in the
resynchronization attempt is retried at the next opportunity. local system's compare states GDS variable.
However, the failure may have resulted in no exchange log v There has been an internal error in CICS APPC processing.
names flows being successful, preventing any synclevel 2 System action: A system dump is taken, unless you have
attaches between the local system and the remote system. specifically suppressed dumps in the dump table.
at the XOK field. If exchange log names has not been done,
the error situation can be overridden by issuing CEMT SET
CONN(xxxx) NOTPENDING commands for the failing In many cases, CICS continues to operate normally, and the
connection. It may be necessary to issue this command on resynchronization attempt is retried at the next opportunity.
both sides of the connection. However, the failure may have resulted in no exchange log
names flows being successful, preventing any synclevel 2
Note: If this command is issued, CICS unilaterally commits attaches.
any resources which may be waiting for APPC User response: Issue CEMT INQUIRE CONN(xxxx), and look
resynchronization. In addition, CICS does not carry out any at the XOK field. If exchange log names has not been done,
APPC resynchronization activity with the remote system. the error situation can be overridden by issuing CEMT SET
Investigate the cause of the error using the system dump and CONN(xxxx) NOTPENDING commands for the failing
any previously output diagnostic information provided by connection. It may be necessary to issue this command on
CICS, the access methods or the operating system. both sides of the connection.
used for this resynchronization conversation. CICS, the access methods or the operating system.

used for this resynchronization conversation. CICS, the access methods or the operating system.
If the internal trace table is available, use this to track the Format the system dump to show the control blocks belonging
commands issued against that session, and check that the state to the terminal control program. (For guidance on how to do
transitions of the User state machine are correct. If any of the this, refer to the CICS Problem Determination Guide.)
state transitions are not valid, it is possible that there has been
a CICS logic error. Determine from the message which APPC session was being
used for this resynchronization conversation.
labelled in the dump and are printed below the TCTTE for the The APPC send and receive buffers for a session are clearly
session to which they belong. Locate the APPC send/receive labelled in the dump and are printed below the TCTTE for the
buffer for the session in question, and check that the contents session to which they belong. Locate the APPC receive buffer
of the buffer are correct. The contents of the buffer differ for the session in question, and check its contents. In
depending on the exact point at which the error is detected, particular, check the format of the exchange log names GDS
but may contain the attach FMH5, the exchange log names variable. The correct format of this SNA defined field can be
GDS variable, and the compare states GDS variable. The found in the SNA Formats manual.
correct format of these SNA defined fields can be found in the
SNA Formats manual. The format of the GDS variable is incorrect, and the cause of
the error should be located. The most likely cause is that the
Examine the log of the remote system. If a protocol violation remote system did not send a valid exchange log names reply,
was detected in the local system's resynchronization data, the in which case it may be necessary to obtain further diagnostic
remote system may have generated diagnostic information material from the remote system.
itself. This information may help to diagnose the cause of the Module: DFHSPZ
protocol violation.
Module: DFHSPZ
DFHZN2139 date time applid An invalid Compare States
reply has been received on session sessid
DFHZN2138 date time applid An invalid Exchange Log from remote system sysid.
Names reply has been received on session Explanation: The local system has received an invalid
sessid from remote system sysid. compare states reply from the remote system. CICS was
Explanation: The local system has received an invalid attempting to resynchronize distributed resources following an
exchange log names reply from the remote system. CICS was earlier failure of a protected conversation during sync point
attempting to resynchronize distributed resources following an processing.
processing. This implies one of the following:
v An error in the remote system
This implies one of the following: v A storage overlay
v An error in the remote system v A CICS logic error.
v A storage overlay System action: A system dump is taken, unless you have
v A CICS logic error. specifically suppressed dumps in the dump table.
specifically suppressed dumps in the dump table. Message DFHME0116 is normally produced containing the
symptom string for this problem. In many cases, CICS continues to operate normally, and the
In many cases, CICS continues to operate normally, and the However, the failure may have resulted in no exchange log
resynchronization attempt is retried at the next opportunity. names flows being successful, and this prevents any synclevel
However, the failure may have resulted in no exchange log 2 attaches between the local system and the remote system.
names flows being successful, preventing any synclevel 2 User response: Issue CEMT INQUIRE CONN(xxxx), and look
attaches between the local system and the remote system. at the XOK field. If exchange log names has not been done,
User response: Issue CEMT INQUIRE CONN(xxxx), and look the error situation can be overridden by issuing CEMT SET
at the XOK field. If exchange log names has not been done, CONN(xxxx) NOTPENDING commands for the failing
the error situation can be overridden by issuing CEMT SET connection. It may be necessary to issue this command on
CONN(xxxx) NOTPENDING commands for the failing both sides of the connection.
both sides of the connection. Note: If this command is issued, CICS unilaterally commits
resynchronization. In addition, CICS does not carry out any

APPC resynchronization activity with the remote system. session to which they belong. Locate the buffers for the
Investigate the cause of the error using the system dump and session in question, and check that the contents are correct.
any previously output diagnostic information provided by
Locate the APPC receive buffer for the session in question,
CICS, the access methods or the operating system.
and check its contents. In particular, check the format of the
compare states GDS variable. The correct format of this SNA
Format the system dump to show the control blocks belonging defined field can be found in the SNA Formats manual.
to the terminal control program. (For guidance on how to do
this, see the CICS Problem Determination Guide.) The GDS variable is probably incorrect, and the cause of the
error should be located. The most likely cause is that the
Determine from the message which APPC session was being remote system did not send a valid compare states reply, in
used for this resynchronization conversation. which case it may be necessary to obtain further diagnostic
material from the remote system.
The APPC send and receive buffers for a session are clearly If the GDS variable is correct, the error is caused by an
labelled in the dump and are printed below the TCTTE for the unexpected session protocol. To check this, compare the
session to which they belong. Locate the APPC receive buffer resynchronization flows with those documented in the SNA
for the session in question, and check its contents. In LU6.2 Reference: Peer Protocols manual.
particular, check the format of the compare states GDS Module: DFHSPZ
variable (the correct format of this SNA defined field can be
found in the SNA Formats manual). XMEOUT Parameters: date, time,applid, sysid, sessid
The format of the GDS variable is incorrect, and the cause of
the error should be located. The most likely cause is that the DFHZN2141 date time applid A protocol violation has
remote system did not send a valid compare states GDS occurred while resynchronizing with remote
variable, in which case it may be necessary to obtain further system sysid via session sessid. The
diagnostic material from the remote system. resynchronization was initiated by the
Module: DFHSPZ remote system.
XMEOUT Parameters: date, time,applid, sessid, sysid Explanation: The local system has detected a protocol
Destination: Console and Transient Data Queue CSMT violation while resynchronizing with the remote system. CICS
was attempting to resynchronize distributed resources
following an earlier failure of a protected conversation during
DFHZN2140 date time applid A protocol violation has sync point processing. The resynchronization was initiated by
occurred while resynchronizing with remote the remote system.
system sysid via session sessid. The
resynchronization was initiated by the local This implies one of the following:
system. v An error in the remote system
Explanation: The local system has detected a protocol v A storage overlay
violation while resynchronizing with the remote system. CICS v A CICS logic error.
was attempting to resynchronize distributed resources System action: A system dump is taken, unless you have
following an earlier failure of a protected conversation during specifically suppressed dumps in the dump table.
sync point processing. The resynchronization was initiated by Message DFHME0116 is normally produced containing the
the local system. symptom string for this problem.
This implies one of the following: CICS continues to operate normally, and the resynchronization
v An error in the remote system attempt is retried at the next opportunity.
v A storage overlay User response: Investigate the cause of the error using the
v A CICS logic error. system dump and any previously output diagnostic
System action: A system dump is taken, unless you have information provided by CICS, the access methods or the
specifically suppressed dumps in the dump table. operating system.
Message DFHME0116 is normally produced containing the Format the system dump to show the control blocks belonging
symptom string for this problem. to the terminal control program. (For guidance on how to do
CICS continues to operate normally, and the resynchronization this, see the CICS Problem Determination Guide.)
attempt is retried at the next opportunity. Determine from the message which APPC session was being
User response: Investigate the cause of the error using the used for this resynchronization conversation.
system dump and any previously output diagnostic
information provided by CICS, the access methods or the The APPC send and receive buffers for a session are clearly
operating system. labelled in the dump and are printed below the TCTTE for the
session to which they belong. Locate the APPC receive buffer
Format the system dump to show the control blocks belonging for the session in question, and check its contents. In
to the terminal control program. (For guidance on how to do particular, check the format of the compare states GDS
this, see the CICS Problem Determination Guide.) variable. The correct format of this SNA defined field can be
Determine from the message which APPC session was being found in the SNA Formats manual.
used for this resynchronization conversation. The GDS variable is incorrect, and the cause of the error
The APPC send and receive buffers for a session are clearly should be located. The most likely cause is that the remote
labelled in the dump and are printed below the TCTTE for the system did not send a valid compare states reply, in which

case it may be necessary to obtain further diagnostic material Module: DFHSPZ

from the remote system.
Module: DFHSPZ
XMEOUT Parameters: date, time,applid, sysid, sessid
DFHZN2701 date time applid Log data sent on ISC session
is xxxxxxxx
DFHZN2142 date time applid An invalid Compare States Explanation: This is an informational message. The
request has been received on session sessid transaction is communicating with a logical unit type APPC. It
from remote system sysid. has sent an FMH (function management header) which carries
Explanation: The local system has received an invalid log data.
compare states request from the remote system. CICS was System action: The transaction continues processing.
attempting to resynchronize distributed resources following an User response: None.
earlier failure of a protected conversation during sync point Module: DFHZERH
processing.
XMEOUT Parameters: date, time,applid, xxxxxxxx
This implies one of the following: Destination: CSNE
v An error in the remote system
v A storage overlay
v A CICS logic error.
In many cases, CICS continues to operate normally, and the

However, the failure may have resulted in no exchange log
names flows being successful, and this prevents any synclevel
2 attaches between the local system and the remote system.
at the XOK field. If exchange log names has not been done,
the error situation can be overridden by issuing CEMT SET
Note: If this command is issued, CICS unilaterally commits

resynchronization. In addition, CICS does not carry out any
APPC resynchronization activity with the remote system.
any previously output diagnostic information provided by
CICS, the access methods or the operating system.
Format the system dump to show the control blocks belonging

to the terminal control program. (For guidance on how to do
this, see the CICS Problem Determination Guide.)
Determine from the message which APPC session was being

used for this resynchronization conversation.
session to which they belong.
Locate the APPC receive buffer for the session in question,

and check its contents. In particular, check the format of the
compare states GDS variable. The correct format of this SNA
defined field can be found in the SNA Formats manual.
The format of the GDS variable is incorrect, and the cause of

the error should be located. The most likely cause is that the
remote system did not send a valid compare states variable, in
which case it may be necessary to obtain further diagnostic
material from the remote system.

Transaction Abend Codes (CICS Transaction Server for
VSE/ESA)
When abnormal conditions occur, CICS can send a message to the CSMT transient
data destination containing the transaction ID, the program name and the abend
code. Here is an example:

termid backout successful. {EXCI id= }
exci_id.condmsg
abend codes
Alternatively, the application can intercept abends by including an active EXEC
CICS HANDLE ABEND command. The actual abend code can be determined by
issuing the EXEC CICS ASSIGN command with the ABCODE option.
The transaction identification code tranid usually consists of the 4 characters

defined to CICS. However, when a transaction is initiated by using a light pen, an
operator identification (OPID) card reader, or 3270 PA or PF keys (specified in the
TASKREQ= operand), CICS creates an internal transaction identification in the
form of a 1-byte 3270 attention identification (AID) code followed by 3 bytes of
X'FF'.
The code that may actually appear in the message in place of the internally-created
transaction identification will be *xx*, where xx is the character translation of the
3270 AID code. To prevent ambiguity, the user should avoid using these codes as
transaction identifiers.
The keys, the light pen (LPA), and OPID, and their corresponding printed AID
codes are given in the following list:
PF1 *F1* PF13 *C1* LPA *7E*

PF2 *F2* PF14 *C2* OPID *E6*
PF3 *F3* PF15 *C3* PA1 *6C*
PF4 *F4* PF16 *C4* PA2 *6E*
PF5 *F5* PF17 *C5* PA3 *6B*
PF6 *F6* PF18 *C6*
PF7 *F7* PF19 *C7*
PF8 *F8* PF20 *C8*
PF9 *F9* PF21 *C9*
PF10 *7A* PF22 *4A*
PF11 *7B* PF23 *4B*
PF12 *7C* PF24 *4C*
An abend code indicates the cause of an error that may have been originated by
CICS or by a user program. For most of the abend codes described, a CICS
transaction dump is provided at abnormal termination.
All CICS transaction abend codes abcode are 4-character alphanumeric codes of the
form Axxy, where:
© Copyright IBM Corp. 1999, 2014 453

AACA • AAL6
Aack 'M'
is the IBM-assigned designation of a CICS transaction abend.
xx is the 2-character code assigned by CICS to identify the module that
detected an error.
y is the 1-character alphanumeric code assigned by CICS.
Format of information
For each transaction abend code, the following information is given:
v An explanation of events leading to or following the message.
v The action that has been or will be taken by CICS (system action).
v The action recommended for the user (console or terminal operator).
v The module or modules that can determine that the message should be sent (not
necessarily the module or modules that can issue the macro to write the
message.)
Transaction abend codes

System action: The transaction is abnormally terminated with
AACA
a dump.
Explanation: An invalid error code has been passed to the
User response: Check the return code from the resume or the
DFHACP program.
suspend to determine the cause of the error.
System action: CICS terminates the task abnormally with a
Module: DFHALP
dump.
Module: DFHACP AAL3
Explanation: The task has been purged before a GETMAIN
request to the storage manager (SM) domain was able to
AAKP
complete successfully. The task that first detected the purged
Explanation: An I/O error occurred while CICS was
condition provides an exception trace.
attempting to write the DFHAK5801 message to the master
terminal log.
CICS transaction dump.
User response: Investigate the reason why the task was
dump.
purged. It was purged either by the master terminal operator
User response: Use the messages relating to the I/O error,
or as a result of a deadlock timeout.
and if necessary, the supplied dump to determine the cause of
Module: DFHALP
the problem.
Module: DFHAKP
AAL4
Explanation: An error (INVALID, DISASTER or unexpected
AAL1
EXCEPTION response) has occurred on a call to the storage
Explanation: DFHALP was processing a request that
manager (SM) domain. The domain that detected the original
deadlocked. The most likely reason for the abend is that an
error provides an exception trace, a console message and,
ALLOCATE QUEUE request has been suspended because
possibly, a system dump (depending on the options specified
there are no contention-winning links available.
in the dump table).
System action: CICS terminates the task abnormally. A dump
is taken only if the abend is nontime-out related. A dump is
not taken for stall purges and deadlock time-outs.
User response: Ensure that there are enough
domain that detected the original error.
contention-winning sessions available to satisfy the
Module: DFHALP
ALLOCATE QUEUE request.
If you are running with modegroups, ensure that there are
contention-winning sessions available to satisfy the AAL6
ALLOCATE request in that modegroup. Explanation: An error (INVALID, DISASTER or EXCEPTION
response) has occurred on a call to
It might be necessary to increase the deadlock timeout SIGNOFF_TERMINAL_USER by DFHALP during signoff for a
(DTIMOUT) value for the transaction to prevent this abend surrogate terminal session running CRTE. The domain that
from recurring. detected the original error provides an exception trace, a
Module: DFHALP console message and, possibly, a system dump (depending on
the options specified in the dump table).
AAL2 CICS transaction dump.
Explanation: Either an incorrect response (other than User response: See the related message produced by the
PURGED) was returned from the suspend of the allocated domain that detected the original error.
task, or an incorrect response was returned from the resume. Module: DFHALP

AAL7 • AAMN
AAL7 AAMG
Explanation: An error (INVALID, DISASTER or EXCEPTION Explanation: An unexpected return code has been received
response) has occurred on a call to schedule a remote terminal following a call to DFHAFMT. This might be due to an
delete by DFHALP during signoff for a surrogate terminal internal logic error.
session running CRTE. The domain that detected the original System action: The task is abnormally terminated with a
error provides an exception trace, a console message and, CICS transaction dump.
possibly, a system dump depending on the options specified User response: You need further assistance from IBM to
in the dump table). resolve this problem. See Part 4 of the CICS Problem
System action: The task is abnormally terminated with a Determination Guide for guidance on how to proceed.
CICS transaction dump. Module: DFHAMP
Module: DFHALP AAMH
Explanation: An unexpected return code has been received
following a call to DFHFCMT. This might be due to an
AALN internal logic error.
Explanation: An error (INVALID, DISASTER or unexpected System action: CICS terminates the task abnormally with a
EXCEPTION response) has occurred on a call to the TD dump.
manager. The domain that detected the original error provides User response: You need further assistance from IBM to
a trace entry and possibly a system dump (depending on the resolve this problem. See Part 4 of the CICS Problem
options specified in the dump table). Determination Guide for guidance on how to proceed.
System action: The task is abnormally terminated with a Module: DFHAMP
User response: Inform the system programmer. Examine the
trace and the dump to identify the point of error. AAMI
Module: DFHAMTD Explanation: An unexpected return code has been received
following a call to DFHFCRL. This might be due to an internal
logic error.
AAMA System action: CICS terminates the task abnormally with a
Explanation: There is an internal logic error in DFHAMP. dump. You need further assistance from IBM to resolve this
System action: The task is abnormally terminated with a problem. See Part 4 of the CICS Problem Determination Guide
CICS transaction dump. for guidance on how to proceed.
User response: You need further assistance from IBM to User response:
resolve this problem. See Part 4 of the CICS Problem Module: DFHAMP
Module: DFHAMP
AAMJ
Explanation: While installing a file, using RDO, a call was
AAMC made to DFHFCFS to enable the file. An irrecoverable error
Explanation: The task was purged before a GETMAIN was returned from DFHFCFS.
request to the storage manager domain was able to complete System action: The task is abnormally terminated with a
successfully. CICS transaction dump.
CICS transaction dump. At the time the error is detected, CICS writes a message to the
User response: Investigate the reason the task was purged. It console, records an exception trace entry and takes a system
was purged either by the master terminal operator or as a dump.
result of deadlock timeout. User response: Inform the system programmer. Examine the
Module: DFHAMP trace and the dump to identify the point of error.
Module: DFHAMP
AAMD
Explanation: An unexpected return code has been received AAMK
from DFHDMP. This is due to an internal logic error. Explanation: While installing a file, using RDO, a call was
System action: The task is abnormally terminated with a made to DFHFCDN. An irrecoverable error was returned from
CICS transaction dump. DFHFCDN.
User response: You need further assistance from IBM to System action: The task is abnormally terminated with a
resolve this problem. See Part 4 of the CICS Problem CICS transaction dump. At the time the error is detected, CICS
Determination Guide for guidance on how to proceed. writes a message to the console, records an exception trace
Module: DFHAMP entry, and takes a system dump.
User response: Inform the system programmer, Examine the
trace and dump to identify the point of error.
AAMF Module: DFHAMP
following a call to the kernel (KE) domain. This might be due
to an internal logic error. AAMN
System action: CICS terminates the task abnormally with a Explanation: There has been an unexpected return code from
dump. a call to DFHPRPT. This might be due to an internal logic
User response: You need further assistance from IBM to error.
resolve this problem. See Part 4 of the CICS Problem System action: The task is abnormally terminated with a
Determination Guide for guidance on how to proceed. CICS transaction dump.
Module: DFHAMP User response: You need further assistance from IBM to
Transaction Abend Codes (CICS Transaction Server for VSE/ESA) 455

AAMO • AAOB

AAM1
Explanation: DFHXMCL has returned an unexpected
Module: DFHAMP
response during the install of a transaction class. This can be
caused by the task being purged during the install.
AAMO System action: The transaction is abnormally terminated with
Explanation: An invalid return code was returned from a CICS transaction dump.
DFHTOR, the CICS terminal object resolution program. If an error has occurred, at the time the error is detected, CICS
System action: The task is abnormally terminated with a issues a DFHXMnnnn console message, records an exception
CICS transaction dump. trace entry and takes a system dump.
User response: You need further assistance from IBM to User response: Determine why the task has failed. If there is
resolve this problem. See Part 4 of the CICS Problem a system dump, use it together with the trace entry and the
Determination Guide for guidance on how to proceed. console message to resolve the problem. If there is no system
Module: DFHAMP dump, the task has been purged either by the master terminal
operator or as a result of deadlock timeout.
AAMP Module: DFHAMP
from DFHPUP. This might be due to an internal logic error. AAM2
System action: The task is abnormally terminated with a Explanation: DFHXMXD has returned an unexpected
CICS transaction dump. response during the install of a transaction definition. This can
User response: You need further assistance from IBM to be caused by the task being purged during the install.
resolve this problem. See Part 4 of the CICS Problem System action: The transaction is abnormally terminated with
Determination Guide for guidance on how to proceed. a CICS transaction dump.
Module: DFHAMP
If an error has occurred, at the time the error is detected, CICS
issues a DFHXMnnnn console message, records an exception
AAMQ trace entry and takes a system dump.
Explanation: An attempt has been made to install a partner User response: Determine why the task has failed. If there is
using RDO. However, the partner resource manager (PRM) is a system dump, use it together with the trace entry and the
unavailable having failed to initialize during CICS console message to resolve the problem. If there is no system
initialization. dump, the task has been purged either by the master terminal
System action: The task is abnormally terminated with a operator or as a result of deadlock timeout.
CICS transaction dump. Module: DFHAMP
User response: If you need to use the PRM, correct the
problem which prevented the PRM from initializing, and
restart CICS. AAOA
Module: DFHAMP 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
AAMS function requested could not be resolved when control passed
Explanation: There has been an unexpected return code to CICS.
following a GETMAIN request to the storage manager. This is
due to an internal logic error. There are two possible reasons for this:
System action: The task is abnormally terminated with a v You have linkedited your application program with a CPI
CICS transaction dump. stub which supports more function than this release of
User response: You need further assistance from IBM to CICS.
resolve this problem. See Part 4 of the CICS Problem v The linkedit stub has been corrupted.
Determination Guide for guidance on how to proceed. System action: The transaction is abnormally terminated with
Module: DFHAMP a CICS transaction dump. An exception trace entry is also
written.
User response: At the time of the error, general register 0
AAMT
points to an 8-byte character string which should match the
Explanation: There is an internal logic error in DFHAMP due
name of the issued CPI call. Use the trace or the dump to
to an unexpected return code from DFHTMP.
System action: The task is abnormally terminated with a verify that this character string is the name of a CPI function
CICS transaction dump. which is supported.
User response: You need further assistance from IBM to If the character string is not an intelligible character string, the
resolve this problem. See Part 4 of the CICS Problem stub has probably been corrupted.
Determination Guide for guidance on how to proceed. Module: DFHCPI
Module: DFHAMP
AAOB
AAMZ
Explanation: An application has issued a CPI verb which
specifies more than eight parameters.
from DFHZCP. This is due to an internal logic error.
System action: The task is abnormally terminated with a System action: The transaction is abnormally terminated with
CICS transaction dump. a CICS transaction dump and an exception trace entry is also
User response: You need further assistance from IBM to written.
resolve this problem. See Part 4 of the CICS Problem User response: Change your application program so that the
Determination Guide for guidance on how to proceed. correct number of parameters is specified on the CPI call.
Module: DFHAMP Module: DFHCPI

AAOC • AAOK
AAOC AAOH
Explanation: CPI Communications is invoked with an invalid Explanation: Journaling of data sent on a CPI
number of parameters for call Communications mapped conversation has failed. This
System action: The transaction is abnormally terminated with condition is caused by a bad response from journal control.
a CICS transaction dump. System action: The transaction is abnormally terminated with
User response: The exception trace point produced with this a CICS transaction dump.
abend contains the incorrectly issued CPI Communications User response: Use the dump to ascertain why the journal or
verb name. Use this to determine where the application log record could not be written correctly. If a journal record
program was in error and amend it accordingly. length error is indicated, TIOATDL may have been corrupted.
Problem determination: Register 12 addresses the current
The SAA CPI Communications Reference manual provides a TCA and field TCAJCAAD and register 4 address the JCA.
detailed description of all the CPI Communications verbs and
The journal control request is contained in JCATR2 and the
how they should be called. response code is in JCAJCRC.
Module: DFHCPARH
Possible request codes are:
AAOD X’8001’ - WRITE

X’8003’ - PUT
Explanation: The task was purged before a GETMAIN
complete successfully. The domain that first detected the Possible response codes are:
purged condition provides an exception trace. X’01’ - IDERROR - Journal identification error
System action: The task is abnormally terminated with a X’02’ - INVREQ - Invalid request
CICS transaction dump. X’03’ - STATERR - Status error
User response: Investigate the reason the task was purged. It X’05’ - NOTOPEN - Journal not open
X’06’ - LERROR - Journal record length error
was purged either by the master terminal operator or as a
X’07’ - IOERROR - I/O error.
result of deadlock timeout.
Module: DFHCPCBI
The address of the TIOA is contained in register 8 and its data
length is in TIOATDL.
AAOE
Explanation: The task was purged before a GETMAIN Analysis:
Register Label Description
complete successfully. The domain that first detected the
purged condition provides an exception trace. R4=@JCA TCZARQPJ JCAJCRC is nonzero.
System action: The task is abnormally terminated with a Module: DFHCPCOJ
User response: Investigate the reason the task was purged. It
was purged either by the master terminal operator or as a AAOJ
result of deadlock timeout. Explanation: CPI Communications has detected an
Module: DFHCPCBA unexpected response from one of its internal routines.
a CICS transaction dump.
AAOF 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
purged condition provides an exception trace.
error itself.
CICS transaction dump. You need further assistance from IBM to resolve this problem.
User response: Investigate the reason the task was purged. It See Part 4 of the CICS Problem Determination Guide for
was purged either by the master terminal operator or as a guidance on how to proceed.
result of deadlock timeout. Module: DFHCPIC
Module: DFHCPCBS
AAOK
AAOG Explanation: CPI Communications has detected an
Explanation: During the processing of CMACCP (accept unexpected call to one of its internal routines.
conversation), CPI Communications detected that the System action: The transaction is abnormally terminated with
application was attached with an unsupported sync level. a CICS transaction dump.
User response: This is a CICS internal logic error.
a CICS transaction dump. A level 2 trace for 'CP' of the transaction shows the course of
User response: This condition is caused by a back-end CPI events prior to this error, for example, the modules called and
Communications transaction being attached with a sync level their parameters. The level 2 trace also provides details of the
that is not CM_NONE (0) or CM_CONFIRM (1). error itself.
Change the front-end transaction, (that is, the initiator of the You need further assistance from IBM to resolve this problem.
conversation in the other system) so that it defines the sync See Part 4 of the CICS Problem Determination Guide for
level correctly. guidance on how to proceed.
Module: DFHCPCBA Module: DFHCPIC

AAOL • AAOS
AAOL AAOP
Explanation: CPI Communications has made an invalid call Explanation: The CPI Communications state machine has
to DFHLUC. been requested to perform a state transition request that is
System action: The transaction is abnormally terminated with considered to be an 'impossible' situation. (The SAA CPI
a CICS transaction dump. Communications Reference manual documents all these
User response: This is a CICS internal logic error. situations.)
A level 2 trace for 'CP' of the transaction shows the course of There are two possible causes of this error:
events prior to this error, for example, the modules called and v The CPC (conversation control block) has been overwritten
their parameters. The level 2 trace also provides details of the in such a way that the conversation state has been altered,
error itself. or
v There is an error in the CPI Communications state machine.
guidance on how to proceed. a CICS transaction dump.
Module: DFHCPCLR User response: A level 2 trace for 'CP' of the transaction
shows the course of events prior to this error, for example, the
modules called and their parameters. The level 2 trace also
AAOM provides details of the error itself.
Explanation: The CPI Communications and the DFHZUSR
state machines are out of synchronization. The transaction dump shows the CPC. You may need further
System action: The transaction is abnormally terminated with assistance from IBM to fully resolve this problem. See Part 4 of
a CICS transaction dump. the CICS Problem Determination Guide for guidance on how to
User response: This is a CICS internal logic error. proceed.
Module: DFHCPCFS
events prior to this error. For example, the modules called and
their parameters. The level 2 trace also provides details of the AAOQ
error itself. 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
guidance on how to proceed. detected by the CPI Communications state machine.
Module: DFHCPCLR, DFHCPSRH System action: The transaction is abnormally terminated with
AAON
Explanation: CPI Communications has detected an A level 2 trace for 'CP' of the transaction shows the course of
unexpected response from DFHLUC. events prior to this error, for example, the modules called and
System action: The transaction is abnormally terminated with their parameters. The level 2 trace also provides details of the
a CICS transaction dump. error itself.
A level 2 trace for 'CP' of the transaction shows the course of See Part 4 of the CICS Problem Determination Guide for
events prior to this error. For example, the modules called and guidance on how to proceed.
their parameters. The level 2 trace also provides details of the Module: DFHCPCFS
error itself.
You need further assistance from IBM to resolve this problem. AAOR
See Part 4 of the CICS Problem Determination Guide for Explanation: CPI Communications has detected an invalid
guidance on how to proceed. value in the CPC (conversation control block).
Module: DFHCPCLR, DFHCPCLC
There are 2 possible causes of this error:
v The CPC (conversation control block) has been overwritten,
AAOO or
Explanation: CPI Communications has been invoked with an v There is an error in CPI Communications which causes it to
invalid first parameter. The first parameter should be the code reject valid values.
of the function to be performed. This is a CICS internal logic System action: The transaction is abnormally terminated with
error. a CICS transaction dump.
User response: A level 2 trace for 'CP' of the transaction
shows the course of events before this error occurred (such as
provides details of the error itself.
the modules called and their parameters) plus details of the
error itself. Module: DFHCPIC

See Part 4 of the CICS Problem Determination Guide for AAOS
guidance on how to proceed. Explanation: CPI Communications has detected that the
Module: DFHCPARH conversation state is RESET for a situation where this should
not occur. That is, the conversation control block (CPC) is
about to be deleted.

AAOT • AAOY
There are two possible causes of this error: System action: The transaction is abnormally terminated with
v The CPC has been overwritten, or a CICS transaction dump.
v There is an error in CPI communications. User response: This is a CICS internal logic error.
events prior to this error, for example, the modules called and
error itself.
provides details of the error itself. You may need further You need further assistance from IBM to resolve this problem.
assistance from IBM to fully resolve this problem. See Part 4 of See Part 4 of the CICS Problem Determination Guide for
the CICS Problem Determination Guide for guidance on how to guidance on how to proceed.
proceed. Module: DFHCPCFS
Module: DFHCPIC
AAOW
AAOT Explanation: CPI Communications has detected an internal
Explanation: While chaining through the CPCs (conversation logic error in DFHCPCLC.
control blocks) for a given conversation, CPI Communications System action: The transaction is abnormally terminated with
detected that the chain was broken. a CICS transaction dump.
There are two possible causes of this error. User response: This is a CICS internal logic error.
1. The CPC chain has been overwritten, or A level 2 trace for 'CP' of the transaction shows the course of
2. There is an error in the CPI Communications chaining events prior to this error, for example, the modules called and
mechanism. their parameters. The level 2 trace also provides details of the
System action: The transaction is abnormally terminated with error itself.
User response: Determine which of the above caused the You need further assistance from IBM to resolve this problem.
error. See Part 4 of the CICS Problem Determination Guide for
A level 2 trace for 'CP' of the transaction shows the course of Module: DFHCPCLC
events prior to this error, for example, the modules called and
error itself. AAOX
Explanation: CPI Communications has detected a bad
You may need further assistance from IBM to fully resolve this syncpoint return code which has been set on a synclevel 0 or 1
problem. See Part 4 of the CICS Problem Determination Guide conversation. The bad return code is only expected on a
for guidance on how to proceed. synclevel 2 conversation.
Module: DFHCPCBI System action: The transaction is abnormally terminated with
AAOU User response: This is a CICS internal logic error.
Explanation: CPI Communications has detected an error in A level 2 trace for 'CP' of the transaction shows the course of
the TP_name or partner_LU_name while processing an events prior to this error, for example, the modules called and
initialize conversation request. The TP_name or their parameters. The level 2 trace also provides details of the
partner_LU_name is obtained by lookup of the error itself.
sym_dest_name in the partner resource table (PRT).
There are two possible causes of this error. See Part 4 of the CICS Problem Determination Guide for
1. The entry in the PRT contains invalid data, or guidance on how to proceed.
2. There is an error in the mechanism that returns the data Module: DFHCPIC
from the PRT and interprets it.
a CICS transaction dump. AAOY
User response: A level 2 trace for 'CP' of the transaction Explanation: CPI Communications detected an invalid LL
shows the course of events prior to this error, for example, the field in the GDS records from which it was receiving on a
modules called and their parameters. The level 2 trace also mapped conversation.
provides details of the error itself.
Although it is possible that the remote system is sending
You need further assistance from IBM to resolve this problem. invalid records, it is more likely to be an error in the receive
See Part 4 of the CICS Problem Determination Guide for logic because DFHZARRC (a lower level receive module) also
guidance on how to proceed. checks the LLs before passing them to CPI Communications.
Module: DFHCPCBI System action: The transaction is abnormally terminated with
User response: Use CICS traces and, possibly a VTAM trace,
AAOV to determine the data that was sent between both systems.
Explanation: CPI Communications has detected that its
internal state table is corrupted. A level 2 CICS trace for 'CP' of the transaction documents the
course of events prior to this error (such as the modules called
This error is detected by the CPI Communications state and their parameters). The level 2 trace also provides details
machine. of the error itself.

AAOZ • AAO9
You may need further assistance from IBM to fully resolve this
AAO4
Explanation: DFHZARL, or a module called by DFHZARL,
has detected a logic error. This error is almost certainly caused
Module: DFHCPCRB
by the module receiving invalid data or indicators from
VTAM.
AAOZ System action: Before returning to the CPI Communications
Explanation: CPI Communications has detected an invalid ID layer, DFHZARL calls DFHZNAC to clean up the session and
field in the GDS records it was receiving on a mapped put out messages on the CSNE log. CPI Communications
conversation. The exception trace point that accompanies this abnormally terminates the transaction with a CICS transaction
abend gives the ID field in data 3. The valid IDs are '12FF'X dump, and produces an exception trace entry.
for application data and '12F1'X for null data. User response: Check the CSNE log to determine the type of
System action: The transaction is abnormally terminated with error. You may need further assistance from IBM to fully
a CICS transaction dump. resolve this problem. See Part 4 of the CICS Problem
User response: Use CICS traces and, possibly, a VTAM trace Determination Guide for guidance on how to proceed.
to determine the data that was sent between both systems. Module: DFHCPCLR
A level 2 CICS trace for 'CP' of the transaction documents the

course of events prior to this error (such as the modules called AAO5
and their parameters). The level 2 trace also provides details Explanation: The task was purged before a GETMAIN
of the error itself. request to the storage manager (SM) domain was able to
You may need further assistance from IBM to fully resolve this purged condition provides an exception trace.
problem. See Part 4 of the CICS Problem Determination Guide System action: The task is abnormally terminated with a
for guidance on how to proceed. CICS transaction dump.
Module: DFHCPCRB User response: Investigate the reason why the task was
purged. It was purged either by the master terminal operator
or as a result of deadlock timeout.
AAO2 Module: DFHCPCBA, DFHCPCBI, DFHCPCBS
Explanation: CPI Communications has detected an
unexpected response from DFHLUC.
System action: The transaction is abnormally terminated with AAO7
a CICS transaction dump. Explanation: The CPI Communications syncpoint request
User response: This is a CICS internal logic error. handler has been passed an invalid DFHLUC parameter list.
This is a CICS internal logic error.
A level 2 CICS trace for 'CP' of the transaction documents the System action: The transaction is abnormally terminated with
course of events prior to this error (such as the modules called a CICS transaction dump.
and their parameters). The level 2 trace also provides details User response: A level 2 trace for 'CP' of the transaction
of the error itself. shows the course of events before this error occurred (such as
the modules called and their parameters) plus details of the
You need further assistance from IBM to resolve this problem. error itself. You need further assistance from IBM to resolve
See Part 4 of the CICS Problem Determination Guide for this problem. See Part 4 of the CICS Problem Determination
guidance on how to proceed. Guide for guidance on how to proceed.
Module: DFHCPCBA Module: DFHCPSRH
AAO3 AAO8
Explanation: The CPI interface detected that a call was made Explanation: The CPI Communications syncpoint request
to a CPI Communications function without CPI handler has been passed an invalid conversation control block
Communications being initialized. This implies that CPI (CPC). This is a CICS internal logic error.
Communications initialization failed while CICS was System action: The transaction is abnormally terminated with
initializing. a CICS transaction dump.
System action: The transaction is abnormally terminated with User response: A level 2 trace for 'CP' of the transaction
a CICS transaction dump. An exception trace entry is also shows the course of events before this error occurred (such as
written when this event occurs. the modules called and their parameters) plus details of the
User response: Check the console listing to determine the error itself. You need further assistance from IBM to resolve
reason why CPI Communications failed to initialize during this problem. See Part 4 of the CICS Problem Determination
CICS initialization. Correct the problem and restart CICS.
Module: DFHCPSRH
If the console listing indicates that CPI Communications
initialized successfully, you need further assistance to resolve
AAO9
the problem. Collect the console listing, the traces and the
Explanation: A task has been purged either as a result of a
transaction dump. See Part 4 of the CICS Problem Determination
purge from the master terminal operator via the CEMT
transaction, or by the task being timed out after waiting for
Module: DFHCPI longer than the DTIMOUT (deadlock timeout) value specified
for the transaction.
User response: Investigate why the task was purged.

ABLA • ABMB
If the task was purged by the master terminal operator, this command, or in the TRAILER or HEADER option on an EXEC
may have been in an attempt to clear the system which CICS SEND TEXT or an EXEC CICS SEND PAGE command.
appeared to be deadlocked for some reason. Check the data item for zero length.
If the task was timed out automatically as a result of the Header and trailer records have a special format described in
DTIMOUT value being exceeded, this may be due to the CICS Application Programming Reference. An ABMA abend
insufficient main storage being available for the number of occurs if the first halfword (the length) is not positive. Check
tasks in the system. If the amount of main storage cannot be the remainder of the header/trailer record for validity when
increased, the number of tasks in the system should be the length is checked.
reduced to avoid short-on-storage situations. Another Problem determination: The output services work area
possibility would be to increase the value of the DTIMOUT (OSPWA) is in user storage and will be printed in a
option for the transaction. transaction dump. It is addressed by register 2 at the time of
Module: DFHCPCLR the abend. Relevant fields are:
v OSPTR7
v OSPHDRA
ABLA v OSPTRLA
complete successfully. The domain that first detected the Register 4 or OSPTIOA points to the TIOA. In the TIOA, the
purged condition provides an exception trace. following fields are relevant:
CICS transaction dump. TIOATDL TIOASAL
User response: Investigate why the task was purged. It was
purged either by the master terminal operator or as a result of
deadlock timeout. Analysis:
If the task was purged by the master terminal operator, this Register Label Description
may have been in an attempt to clear the system which
appeared to be deadlocked for some reason. R4=@TIOA PBCKTDL TIOATDL is zero or greater
than TIOASAL-12.
If the task was timed out automatically as a result of the
DTIMOUT value being exceeded, this may be due to R2=@OSPWA PBD20080 R0 (= first halfword of
insufficient main storage being available for the number of R0=length trailer) is zero.
tasks in the system. If the amount of main storage cannot be of trailer R8=OSPTRLA.
increased, the number of tasks in the system should be R8=@trailer OSPTR7 has X’20’ bit set.
reduced to avoid short-on-storage situations. Another
R2=@OSPWA PBDTXHDR R0 (= first halfword of
possibility would be to increase the value of the DTIMOUT
R8=@header header) is zero.
option for the transaction.
R0=length R8=OSPHDRA.
Module: DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR of header. OSPTR7 has X’40’ bit set.
Module: DFHPBP, DFHMCP
ABLB
Explanation: An error (INVALID, DISASTER, or unexpected
ABMB
Explanation: The user has specified a cursor position in the
BMS output request. It is larger than the current screen size
possibly, a system dump (depending on the options in the for the 3270 for which output is being built.
dump table). System action: The transaction is abnormally terminated with
System action: The task is abnormally terminated with a a CICS transaction dump.
CICS transaction dump. User response: Correct the program that specified the
User response: Please see the related message produced by incorrect cursor location.
the domain that originally detected the error.
Use trace to identify the statement issuing the request. Check
Module: DFHMCP, DFHMCPE, DFHM32, DFHPBP, DFHRLR
that the cursor position is being correctly set. The program
may have been designed to run in alternate screen size mode
ABMA but is being run in default screen size mode, or it may have
Explanation: The user has supplied a terminal I/O area been designed to run on a 3270 model different from the one
(TIOA) with an invalid data length that was either equal to in use. If the program is routing a message, the route list
zero or greater than the storage accounting length minus 12. should be checked. If the program is to run with various 3270
models, the cursor position should be within the size of the
Alternatively, the length field of a header or trailer area smallest screen.
provided by the application program is invalid (that is, not
Problem determination: If the abend occurs in DFHPBP:
positive).
System action: The transaction is abnormally terminated with At the time of the abend, register 2 points to the OSPWA and
a CICS transaction dump. register 1 to the TTP. Relevant fields are:
User response: Correct the program that supplied the v OSPTR3 has X'10' bit set to indicate a user-specified cursor
erroneous data length. position
Check the TIOA. If either of the conditions described is v OSPCP contains a halfword cursor position specified by
present, check the application program. For programs using user
command-level interface, the TIOA is obtained by CICS using v TTPSCSZ contains the halfword value of the screen size to
the length of the data item passed in the FROM option on an compare against.
EXEC CICS SEND MAP or EXEC CICS SEND TEXT

ABMC • ABML
If the abend occurs in DFHMCP or DFHMCX:

ABMF
v Register 6 points to the OSPWA (in LIFO storage)
Explanation: The value specified for the length option of the
v OSPCP contains a halfword cursor position specified by basic mapping support (BMS) send map is greater than the
user length of the 'from' area.
v OSPTR3 has X'10' bit set to indicate a user-specified cursor System action: The transaction is abnormally terminated with
position a CICS transaction dump.
v OSPSCSZ contains the halfword value of the screen size to User response: Redefine the value for the length option.
compare against. Module: DFHPBP
Analysis:
ABMG
Register Label Description Explanation: The user has requested a basic mapping
support (BMS) service that was not specified at system
In DFHPBP:
generation, or at initialization.
R2=@OSPWA PBDBADC OSPTR3 X’10’ bit set
indicates the user-
R1=@TTP specified cursor a CICS transaction dump.
position. User response: Correlate services requested against options
TTPSCSZ halfword screen specified in the system generation of BMS.
size.
Follow this procedure:
OSPCP halfword cursor
position. 1. Scan the trace table for the transaction ID that issued the
abend. If this is CSPQ (page cleanup), module DFHTPQ
In DFHKCP or DFHMCX: abnormally terminated because a message purge delay of
R6=@OSPWA MCENEAU2 OSPTR3 X’10’ bit set zero has been specified and CSPQ has been entered via a
indicates the user- terminal. The message purge delay is specified in the
specified cursor PRGDLAY of the DFHSIT macro, and its value can be
position. found in SITPRGD.
OSPSCSZ halfword screen
2. Scan the trace table for the last BMS request (code 'FA').
size.
OSPCP halfword cursor Use the option bytes at the start of the failing module to
position. see if the requested functions have been generated. For
Module: DFHPBP, DFHMCP (for minimum-function BMS), example, paging may have been requested, but standard or
DFHMCX 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
ABMC amongst BMS modules must have occurred. This can
Explanation: The CMSG transaction is attempting to send a happen if the DFHSIT macro specified individual suffixes
message to a greater number of terminals than is possible. for the BMS modules.
There is no fixed maximum because the value depends on the
other operands specified on the routing command.
The following modules differ between standard and
full-function BMS:
User response: Redefine the route list.
Module: DFHMCP DFHMCP DFHRLR DFHPBP DFHTPP
Module: DFHMCP, DFHTPQ

ABMD
Explanation: DFHTPR or DFHTPP has issued a DFHDI
TYPE=SEND and has received a return code other than ABMI
"FUNCERR-REQUEST FOR CHANGE DIRECTION Explanation: The map specified for a BMS input mapping
SIGNALED" or "NORESP" request was not an input map.
System action: The transaction is abnormally terminated with System action: The transaction is abnormally terminated with
a CICS transaction dump. a CICS transaction dump.
User response: Inform your system programmer. User response: Either define another input map or redefine
Module: DFHTPP, DFHTPR the existing map.
Module: DFHMCP, DFHMCX, DFHMCY
ABME
Explanation: DFHTPR or DFHTPP has detected an invalid ABML
datastream while processing a basic mapping support (BMS) Explanation: The terminal control locate routine received
request. invalid data from DFHRLR and returns with an error return
System action: The transaction is abnormally terminated with code. DFHRLR is attempting to scan the TCT for a BMS
a CICS transaction dump in which register 7 indicates the
ROUTE request with LIST=ALL or operator class or operator
location at which the abend was detected.
ID specified in the route list. The terminal control table may
User response: Examine the transaction dump for bad data
have been corrupted.
in the TIOA. If the origin of the bad data is an application
program, correct the program.
Module: DFHTPP, DFHTPR a CICS transaction dump.

ABMM • ABMV
The terminal control table has probably been corrupted during dump, register 8 contains the address of the TCTTE for the
execution. Attempt to scan through the TCT in a dump. associated terminal. If register 8 contains zero, this indicates
(Because the system dump uses the same technique for that the task is not terminal-oriented.
printing all TCTTEs, the system dump fails at the same point.) System action: The task is abnormally terminated with a
CICS dump.
Determine which entry is incorrect. It may be that the TCTTE User response: Ensure that the terminal associated with
has been overwritten by user data that is recognizable in the CQRY is of the 3270 or SCSPRINT family of devices.
dump. Module: DFHQRY
Check the application program for references to the TCTTE
pointer. Check for user data that may be addressed from the ABMR
same pointer. Explanation: The Page Retrieval transaction (CSPG) has been
initiated but the task is not terminal-oriented.
In an assembler program, there may be multiple equates for
the TCTTE base register. CICS dump.
It may be that the TCT is being overwritten by some earlier User response: Ensure that a terminal is associated with the
transaction. If this is so, it is probably one associated with the CSPG transaction.
terminal whose TCTTE is overwritten. Module: DFHTPR
Problem determination: Register 11 points to the current
TCTTE in the search. ABMT
The TCT prefix (DFHTCTFX) can be located from CSATCTBA. Explanation: Minimum function BMS is being used for a
non-3270 terminal type.
The first terminal entry (TCTTE) in the TCT is addressed by System action: The transaction is abnormally terminated with
TCTVTEBA. a CICS transaction dump.
TCTTETEL is the halfword offset from current TCTTE to the resolve this problem. See Part 4 of the CICS Problem
next. Determination Guide for guidance on how to proceed.
Module: DFHTPS
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 ABMU
TCTTETEL to the current address, is invalid. This check is Explanation: The application program supplied an address
made by locate code (DFHZLOC) in DFHZCX. that is not within region boundaries. The low-order 3 bytes of
Register Label Description general register 1 in the transaction dump contain the
R11=@TCTTE RLRLOCN Issue DFHTC CTYPE=LOCATE erroneous address. The high-order byte of register 1 indicates
Module: DFHRLR for full-function BMS the address type as follows:
Hex Value Address Type

ABMM 01 Title address (TCAMSTA)
Explanation: An invalid map was specified.
02 Alternate I/O area address
a CICS transaction dump. (TCAMSIOA)
User response: Use the supplied dump to diagnose the 03 Map address (TCABMSMA)
problem. Register 6 contains the address of the BMS 04 Header address (TCAMSHDR)
instruction being executed when the error was recognized.
05 Route list address (TCAMSRLA)
Module: DFHPBP
06 Trailer address (TCAMSTRL)
07 Map set address (TCAMSMSA)
ABMO
08 TIOA address (TCTTEDA)
Explanation: The map specified for a BMS output mapping
request was not an output map.
User response: Either define another output map or redefine User response: Correct the application program that is
the existing map. supplying the erroneous address.
Module: DFHMCP, DFHMCX, DFHMCY Module: DFHMCP, DFHEMS
ABMQ ABMV
Explanation: The query transaction (CQRY) has been Explanation: DFHRLR has detected an invalid route list
initiated and either the task is not terminal-oriented, or the entry.
associated terminal is not defined to CICS as a 3270 or System action: The transaction is abnormally terminated with
SCSPRINT device. This abend will occur if CQRY is entered at a CICS transaction dump.
a console, even when the console is a 3270 device, since the User response: Check that the route list is correctly built with
console has the appearance to CICS of a keyboard/printer reserved field in the entry containing blank and a stopper of
device. The CQRY transaction does not have an operator halfword X'FFFF' to terminate the list.
interface, and under normal conditions there is no need for an Module: DFHRLR
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

ABMX • ABM2
and the map set suffix have

ABMX
loaded into the lower two
Explanation: A text string passed to BMS contained a set bytes of register 3 by the
attribute order that was invalid for one of the following subroutine RLRSUFXS.
reasons: Module: DFHRLR
1. The set attribute sequence was less than three characters.
2. The attribute type was invalid.
System action: The task is abnormally terminated with a ABM2
CICS transaction dump. Explanation: No user data was supplied for this BMS
User response: Correct the application program. request. That is, the address of a user data area was not found
Module: DFHPBP in either TCTTEDA or TCAMSIOA.
When a BMS macro level output request is issued, the user

ABMZ must have placed the address of the data to be passed to BMS
Explanation: The address of the terminal I/O area (TIOA) in in TCTTEDA or TCAMSIOA before issuing the macro. The
TCTTEDA was found to be zero. choice is made on the following criteria:
v If the data is to be passed in a TIOA by a terminal-oriented
When using BMS fast path as a result of an EXEC CICS
task, the address of this TIOA may be placed either at
RECEIVE MAP, DFHEMS always initializes TCTTEDA with
the address of the TIOA. If TCTTEDA is subsequently found TCTTEDA, or in TCAMSIOA together with the setting of
to be zero by DFHMCX, an overwrite must have occurred. binary zeros into TCTTEDA.
System action: The transaction is abnormally terminated with v If the data is being passed by a terminal-oriented task but
a CICS transaction dump. not in a TIOA, the address of the TIOA-like area of this data
User response: Investigate why TCTTEDA is zero. must be placed in TCAMSIOA and binary zeros set into
TCTTEDA.
Scan the trace table for the last BMS request (code FA) for the v If the data is being passed by a non-terminal-oriented task,
failing task and try to determine which user programs have the address of the TIOA-like area of this data must be
been given control since that BMS request. placed in TCAMSIOA. TCTTEDA cannot be referenced,
Module: DFHMCP, DFHMCX, DFHMCY because there is no TCTTE associated with this task.
ABM0 If a task attempts to pass addresses from both TCTTEDA and

Explanation: The map specified for a basic mapping support TCAMSIOA, the address in TCTTEDA is the one selected.
(BMS) request could not be located. System action: The transaction is abnormally terminated with
System action: The transaction is abnormally terminated with a CICS transaction dump.
a CICS transaction dump. User response: The programmer must place the address of
User response: Check if the map has been defined. If it has, the data into TCTTEDA or TCAMSIOA, whichever is
check that it has been specified correctly. appropriate.
Module: DFHMCP, DFHMCX, DFHMCY
Firstly, check that the user has loaded TCTTEDA or
TCAMSIOA with the address of the user data, by checking the
ABM1 application listing and the contents of TCTTEDA and/or
Explanation: A basic mapping support (BMS) service is TCAMSIOA.
requested by a task associated with a terminal that is not
supported by BMS. The request is not a routing request. Next, check that the BMS request has been correctly decoded
System action: The transaction is abnormally terminated with by CICS by referring to the OSPWA request bytes (OSPTR1-8)
a CICS transaction dump. or decoding the last BMS entry in the trace table. See
User response: Do not use terminals not supported by BMS OSPIND01 to check correct decoding of PAGEBLD or
for applications using BMS services. TEXTBLD, and TCAFCI bit 7 to identify whether the task is
terminal-oriented or not.
Check the terminal type and model number. Confirm that it is
a terminal that is not supported by BMS. A list of terminals At the abend point, register 1 contains the user data address
supported by BMS is given in the CICS Application last loaded, and register 4 the address of OSPTIOA as an
Programming Guide. Check that the TCT macro for the terminal address of null data.
accurately describes the physical terminal.
Problem determination: At the time of the abend, register 11 If a CICS error is suspected, concentrate initially on subroutine
addresses the TCTTE, and TCTTETEA and register 6 address MCPFTIOA, because this is a simple piece of code that shows
the TCTTE extension, TCTETTE. the data-fetch logic. ABM2 condition is trapped early in the
CICS decoding of the DFHBMS request and involves module
Relevant fields are:
DFHMCP only.
TCTTEDDS the device dependent suffix.
Case/Register Label Description
TCTTEMSS the map set suffix.
R9=@OSPWA MCPMAP OSPTR4 has OSPTRM
Analysis: DFHRLR tests the device dependent suffix and the (X’04’) bit set for
map set suffix in the TCTTE extension. If both of these are TYPE=MAP.
zero, the terminal is not supported by BMS and DFHRLR
abends the task with the abend code ABM1. R9=@OSPWA MCPPGBLD OSPTR5 has OSPTRB
(X’80’) bit set and
Register Label Description BMS sets bit
OSPLMPB (X’08’) in
R4= RLRSFXCK TCTEDDS=X’00’ and OSPIND01 for
@TCTTETE TCTEMSS=X’00’. TYPE=PAGEBLD.
The device dependent suffix OSPTR4 has X’40’,

ABM3 • ABM4
X’80’, or X’C0’ set OSPTR1-8

for DATA=NO, ONLY, BMS request data saved from the TCA
or YES respectively, TCTTEDA
so should be X’80’ Terminal data area address
or X’C0’.
TCAFCI Facility control indicator
R9=@OSPWA MCPTXBLD OSPTR7 has OSPTRX TCAMSIOA
(X’80’) bit set and Alternate I/O area address
BMS sets bit
OSPLMTB (X’04’) in Analysis: The ABM2 abend is invoked at one point in
OSPIND01 for DFHMCP, at label MCPABEND. There are five regions in
TYPE=PAGEBLD.
DFHMCP in which the user's data is sought:
OSPTR4 has X’40’,
X’80’, or X’C0’ set Labels
for DATA=NO, ONLY,
or YES respectively, TYPE=MAP MCPMAP
so should be X’80’ TYPE=PAGEBLD,DATA=YES/ONLY MCPPGBLD
or X’C0’. MCPGTIOA
TYPE=TEXTBLD,DATA=YES/ONLY MCPPGBLD
R9=@OSPWA MCPMAPNG OSPTR3 has OSPTSN MCPGTIOA
(X’01’), OSPTSA Mapping but not PAGEBLD,DATA=YES/ONLY MCPMAPNG
(X’02’), or OSPTMN No (mapping,PAGEBLD,TEXTBLD,PAGEOUT) MCPDFALT
(X’04’) bits set, or
OSPTR4 has OSPTMA "Mapping" refers to BMS requests that specify maps, that is
(X’10’) bit set for
OSPTR3 bits 5 or 6 or 7 or OSPTR4 bit 3 set on.
mapping.
OSPTR4 has X’04’ or
X’80’ or X’C0’ set for Each of these functional regions does a BAL to subroutine
DATA=NO, ONLY, or YES MCPFTIOA to search for a user data area. If a valid area
respectively, so should (abend ABMU if not) is found, its address is put into
be X’80’ or X’C0’. OSPTIOA and the address of the data address (of TCAMSIOA
or TCTTEDA) is set into OSPSIOA. If a data area is not found,
All R12=@TCA MCPFTIOA TCAFCI has
TCAFCTRM (X’01’) bit OSPTIOA is cleared and OSPSIOA is now loaded with the
set if the task is address of OSPTIOA as a null data area.
terminal-oriented.
On the BAL return, OSPTIOA is tested for a nonzero value. If
All R11=@TCTTE MCPFTIOA TCTTEDA could point it is zero, a branch to MCPABEND is taken.
to a use TIOA but does
Module: DFHMCP
not, thus causing the
abend.
All R12=@TCA MCPFTIOA TCAMSIOA could point
ABM3
to a user data area
(TIOA or otherwise), Explanation: A BMS input or output request has been issued
but does thus causing from a task that is not terminal-oriented.
the abend. System action: The task is abnormally terminated with a
CICS dump.
All R9=@OSPWA MCPNTOTM OSPTIOA contains the User response: The task issuing a BMS input or output
address of the user request must be attached to a terminal.
area found, so is Module: DFHMCP
zero.
OSPSIOA points
to OSPIOA (which is ABM4
copied from TCAMSIOA)
Explanation: An invalid request response has been received
as being the second-dry
data area sought by to a temporary storage PUT or PUTQ request issued by BMS.
BMS for data . The data passed to the temporary storage program has an
OSPIA (TCAMSIOA) was invalid length.
also zero so causing System action: The transaction is abnormally terminated with
the abend. a CICS transaction dump.
Problem determination: The output services work area User response: You need further assistance from IBM to
(OSPWA) is addressed by register 9. The TCTTE is addressed resolve this problem. See Part 4 of the CICS Problem
by register 11. The TCA is addressed by register 12. Determination Guide for guidance on how to proceed.
The relevant fields are: Determine from the trace table whether the abend occurred in
DFHMCP or DFHTPP.
Field Description
OSPIND01 Check the length of the appropriate area.
OSPWA indicator byte 1 If the MCR length is invalid, possible reasons are:
OSPIOA v The title record specified in the TITLE option on a BMS
Alternate I/O area address ROUTE request has an invalid format, that is, it does not
OSPSIOA begin with a halfword length field or is more than 64
Address of address of data (TCTTEDA/TCAMSIOA) characters.
OSPTIOA
Address of user data found by BMS

ABM5
v The message is being routed to more terminals than number of characters available on the screen, particularly if
intended. OSPTTCNT is very large, for example, if extended 3270 attributes are used). For messages directed to
LIST=ALL is specified on a ROUTE request and there are a other devices, the page buffer consists of a message formatted
large number of terminals in the TCT. with NL characters, a 4-byte page control area following it.
The length in TSIOAVRL should be less than the length in the
If the page buffer length is too large, this may be because preceding storage accounting area, otherwise an error has
more data than intended is being built into the page. If the occurred in constructing the page, possibly in prior BMS
page buffer length is greater than the length of the storage requests.
area indicated in the preceding storage accounting area, an
error has occurred in page or text building, and the page In either of the above cases, if the length of the area being
buffer extends beyond the area allocated to it (that is, storage output appears valid, it is necessary to increase the control
violation). interval size for the temporary storage data set.
Problem determination: Abend in DFHMCP (see Analysis) Register Label Description
The OSPWA (output services work area) is in user storage and
DFHMCP
is printed in a transaction dump. It is addressed by register 9 R8=@MCR MCPMCRTS The MCR is too long or
at the time of the abend. Relevant fields are: has invalid length ($4).
OSPTITLE
OSPTTCNT DFHTPP
OSPPLTI R7=@pgbufTPNOPGL The page buffer is
OSPTOTPG or too large.
TPNODDS
Module: DFHMCP, DFHTPP
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 ABM5
information. MCRLLBB contains the length of the MCR Explanation: A DFHTS TYPE=PURGE request has been
(halfword) abend in DFHTPP. issued with an invalid REQID. This incorrect request was
issued by basic mapping support (BMS).
The page buffer is addressed by register 7 at the time of the
abend. It contains storage accounting fields in the first 8 bytes DFHTPR cannot find the terminal identifier for the current
and a halfword length at offset 8 (TSIOAVRL). terminal in the terminal list in the message control record
(MCR).
In both cases, the temporary storage use map (DFHTSMAP) is
addressed from CSATSATA. TSMAPCOM contains the number
User response: Check the trace table and find the preceding
of available bytes in a control interval on the temporary
PUT/PUTQ TS requests. Check whether the identifier for the
storage data set.
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
Analysis: If the temporary storage request preceding the corrupted.
abend is a DFHTS PUT, the abend occurred in DFHMCP. If
the temporary storage request preceding the abend is a This error is very unlikely, as the label indicates (TPRSNH -
DFHTS PUTQ, the abend occurred in DFHTPP. If the abend “Should Not Happen”). DFHTPS has scanned the MCR to
occurred in DFHMCP, DFHMCP is attempting to put the identify the terminals to which this message is directed, and
message control record to temporary storage. Check the length has created an AID to initiate CSPG (DFHTPR) at each of
of the MCR (MCRLLBB). It may be negative. them. However, when DFHTPR retrieves the MCR, it cannot
find the current terminal identifier in the list of terminals.
The length of the MCR is calculated by code following label Presumably the MCR has been corrupted between creation of
MCPNODDS and is: the AID and dispatching of CSPG at the terminal. Check back
through the trace table to find the instance of DFHTPS that
28 + 21 * OSPTTCNT + (length of title record) built the AID for this terminal (transaction CSPS); it will have
+ (space for page/LDC table,
issued a TC LOCATE request to verify that the terminal
if needed)
identifier is valid, and this identifier can be seen in the trace
entry.
The address of the title record is at OSPTITLE and the length Problem determination: The TS identifier is built in
is contained in the first halfword. Space for the page/LDC TCATSDI before the TS purge is issued, although this has
table is required if OSPPLT1 is nonzero, which should occur probably been overwritten before the dump is taken. The trace
only for messages routed to LDC devices (3600, 3650, 3767, table entry for the DFHTS TYPE=PURGE contains the TS
3770, 3790). The number of entries is in OSPTOTPG. 2 bytes identifier in the last 8 bytes.
are required per entry.
The OSPWA is addressed by register 9.
If the abend occurred in DFHTPP, BMS is attempting to add a OPSTSID temporary storage identifier (8 bytes).
page to the temporary storage queue, and the page buffer will
not fit in the control interval. TSIOAVRL contains the length of Register 8 points to the MCR.
the page buffer.
Register 5 points to the current entry.
For messages directed to 3270 devices, the page buffer consists Register 0 points to the end of table.
of a 3270 data stream with a 4-byte page control area
Register 9 points to the TCTTE.
following it (a 3270 data stream may be larger than the

ABM6 • ABNH
The terminal list starts at MCRIDLST and the terminal

ABNA
identifier is at the start of the terminal entry. Each terminal
Explanation: No route list was supplied with a route request
entry is X'15' bytes long. received from the remote system.
Analysis: DFHMCP uses the temporary storage identifier in System action: The task is abnormally terminated with a
OSPTSID. CICS transaction dump.
Cannot find the terminal identifier for this terminal in the resolve this problem. See Part 4 of the CICS Problem
terminal list in the MCR. Determination Guide for guidance on how to proceed.
Register Label Description Module: DFHTPS
R9=@(OSPWA) MCPCKPGS Code builds the temporary

ABNB
storage code in TCATSDI
and issues DFHTS Explanation: Either the principal facility of the task is not a
TYPE=PURGE macro, TCTTE of the correct type, or the task has no principal facility.
specifying IDERROR exit System action: The task is abnormally terminated with a
of MCPTSIDE, where the CICS transaction dump.
abend is raised. User response: Ensure that DFHTPS has not been specified
as the initial program of a transaction other than CSPS. Check
R8=@(MCR) TPRCKID
Code scans terminal list that the operator did not enter CSPS from the terminal.
for a terminal entry that Module: DFHTPS
has the id of the current
terminal, and if it
cannot be found, links to ABNC
TPRSNH to raise the abend. Explanation: An attempt to access a temporary storage queue
Module: DFHMCP, DFHTPR failed.
ABM6 User response: Ensure that temporary storage is correctly
Explanation: Transaction CSPS, scheduled internally by BMS, generated.
has not been installed. Module: DFHTPS
User response: Install the transaction CSPS (Group ABNE
DFHBMS). Explanation: An error response was received from an
Module: DFHMCP invocation of a BMS TYPE=ROUTE or TYPE=STORE request.
ABM7 User response: Check that BMS was correctly generated.
Explanation: The trailer specified to be used while building Module: DFHTPS
pages of text data is longer than the page.
a CICS transaction dump. ABNF
User response: Correct the application program that issues Explanation: The transaction was not in send mode when it
the request with too long a trailer. sent data to the remote system.
Module: DFHPBP System action: The task is abnormally terminated with a
ABM8 resolve this problem. See Part 4 of the CICS Problem
Explanation: A BMS text request specified a value for the Determination Guide for guidance on how to proceed.
JUSTIFY option which is zero or too large for the page being Module: DFHTPS
built.
a CICS transaction dump. ABNG
User response: Correct the application program that specified Explanation: An attach request was received from the remote
too large or zero value for the JUSTIFY option. system without any data indicating the reason for the request.
Module: DFHPBP System action: The task is abnormally terminated with a
ABM9 resolve this problem. See Part 4 of the CICS Problem
Explanation: The text data overflow routines have been Determination Guide for guidance on how to proceed.
reentered while text overflow was in process. This condition Module: DFHTPS
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. ABNH
System action: The transaction is abnormally terminated with Explanation: An attempt to ship data to the remote system
a CICS transaction dump. failed.
User response: Reduce the number of lines required for the System action: The task is abnormally terminated with a
header and/or trailer or increase the page size of the terminal. CICS transaction dump.
Module: DFHPBP User response: You need further assistance from IBM to

ABNI • ABRE
Module: DFHTPS This abend code never appears at the head of a transaction
dump, but can appear in the body of a dump after a CICS
restart failure.
ABNI User response: Using the associated messages, determine the
Explanation: CICS could not find a profile for an LU6.2
cause of the backout failure. Restore the data set before
transaction routing request.
restarting CICS.
System action: CICS terminates the task abnormally.
Module: DFHDLBP, DFHTSBP
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 ABP3
error before resubmitting the transaction. Explanation: During CICS emergency restart, one of the
Module: DFHTPS
named CICS modules detected a CICS internal logic error.
System action: One of the following CICS modules traps this
ABNJ abend and abends CICS restart with a covering message:
Explanation: The task was purged before a GETMAIN v DFHTCRP (terminal control recovery program) traps for
request to the storage manager (SM) domain was able to DFHTCBP
complete successfully. The task that first detected the purged v DFHTSRP (temporary storage restart program) traps for
condition provides an exception trace. DFHTSBP.
CICS transaction dump. This abend code never appears at the head of a transaction
User response: Investigate the reason why the task was dump, but can appear in the body of a dump after a CICS
purged. It was purged either by the master terminal operator restart failure.
or as a result of a deadlock timeout. User response: You need further assistance from IBM to
Module: DFHTPS resolve this problem. See Part 4 of the CICS Problem
Module: DFHTCBP, DFHTSBP
ABNK
EXCEPTION response) has occurred on a call to the storage ABP4
manager (SM) domain. The domain that detected the original Explanation: During a CICS emergency restart, storage
error provides an exception trace, a console message and, management was found to be unusable.
possibly, a system dump (depending on the options specified System action: The CICS module, DFHDLRP (the DL/I
in the dump table). restart program), traps this abend and abends CICS restart
System action: The task is abnormally terminated with a with a covering message. This abend code never appears at
CICS transaction dump. the head of a transaction dump, but may be found in the body
User response: See the related message produced by the of a dump after a CICS restart failure.
domain that detected the original error. User response: Using the associated messages, determine the
Module: DFHTPS cause of the I/O error on the restart data set. Restore the data
set before restarting CICS.
Module: DFHDLBP
ABP1
Explanation: An I/O error occurred when one of the named
CICS modules was attempting to read the recovery file in the ABRC
restart data set. Explanation: The bridge exit is not defined and could not be
System action: One of the following CICS modules traps this autoinstalled.
abend and abends CICS restart with a covering message: System action: The task is abnormally terminated with a
v DFHDLRP (DL/I recovery program) traps for DFHDLBP CICS transaction dump. The user transaction will not be
v DFHTCRP (terminal control recovery program) traps for started.
DFHTCBP User response: Either define the program using RDO or
v DFHRCRP (recovery control restart program) traps for change the program autoinstall exit to allow it to be
DFHUSBP. autoinstalled.
Module: DFHBRMS, DFHBRTC
This abend code never appears at the head of a transaction
dump, but may be found in the body of a dump after a CICS
restart failure. ABRD
User response: Using the associated messages, determine the Explanation: The bridge exit is disabled.
cause of the I/O error on the restart data set. Restore the data System action: The task is abnormally terminated with a
set before restarting CICS. CICS transaction dump. The user transaction will not be
started.
Module: DFHDLBP, DFHTCBP, DFHUSBP
User response: Identify why the bridge exit is disabled.
Enable the bridge exit and retry the action.
ABP2 Module: DFHBRMS, DFHBRTC
Explanation: A backout failure occurred during execution of
one of the named CICS modules. For example, an I/O error ABRE
occurred on the resource being backed out. Explanation: The bridge exit could not be loaded.
System action: One of the following CICS modules traps this System action: The task is abnormally terminated with a
abend and abends CICS restart with a covering message. CICS transaction dump. The user transaction will not be
v DFHDLRP (DL/I recovery program) traps for DFHDLBP started.
v DFHTSRP (temporary storage restart program) traps for User response: Investigate why it cannot be loaded. It may
DFHTSBP.

ABRF • ABRS
not have been defined in the LIBDEF search chain

ABRJ
concatenation.
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
ABRF value in the user transaction profile definition is used. If no
Explanation: The bridge exit is defined as remote. FACILITYLIKE value is specified in the profile definition, a
System action: The task is abnormally terminated with a value of CBRF is used.
CICS transaction dump. The user transaction will not be
started. The name must be that of an installed VTAM 3270 terminal.
User response: Define the bridge exit as a local program. System action: The task is abnormally terminated with a
Module: DFHBRMS, DFHBRTC CICS transaction dump. The user transaction will not be
started.
User response: Define the terminal specified by
ABRG FACILITYLIKE, change the value on the profile definition,
Explanation: An invalid bridge facility token was specified. change the value supplied by the client application, or install a
System action: The task is abnormally terminated with a terminal definition for CBRF.
CICS transaction dump. The user transaction will not be Module: DFHBRXM
started.
User response: This error was probably caused by the
incorrect data being sent to the bridge exit from the client ABRK
application. Explanation: The USERID check failed following the call to
the bridge exit.
Check the data set by tracing the data sent from the client System action: The task is abnormally terminated with a
application. CICS transaction dump. The user transaction will not be
Ensure that the bridge facility token in the data transmitted by started.
the application is correct. User response: Enter the correct password. If the password is
Module: DFHBRXM correct or was not supplied, review the external security
manager definitions.
Module: DFHBRXM
ABRH
Explanation: The bridge facility token specified is not known
to CICS. ABRN
System action: The task is abnormally terminated with a Explanation: The bridge exit returned a value in BRXA_RESP
CICS transaction dump. The user transaction will not be that is not valid for the command for which it was invoked.
started. System action: The transaction is backed out.
User response: The most likely error is that the client User response: Change the bridge exit to only return valid
application specified too small a keep time for the bridge response settings.
facility. Before the client reused the bridge facility token, CICS Module: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC
had already discarded it. Check the bridge facility keep time
in the outbound messages. CICS will use the keep time value
ABRQ
specified in the last message used by a transaction.
Explanation: The bridge exit issued an abend.
Alternatively use the trace or CEDX to look at the keep time
System action: The transaction is backed out.
in the BRXA passed back on the terminate call to the bridge
User response: Identify why the bridge exit abended.
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 ABRR
CICS system. Explanation: The user transaction's profile could not be
Module: DFHBRXM found.
CICS transaction dump. The user transaction is not started.
ABRI User response: Check that the profile name in the user
Explanation: There are no free bridge facility tokens transaction definition is correct, and that this profile has been
available. This is probably due to excessive keep time values defined.
being specified on the bridge exit termination call. Module: DFHBRXM
CICS transaction dump. The user transaction will not be
started. ABRS
User response: Review the keep time values used by the Explanation: CICS was unable to obtain storage to create the
client applications. If some client applications are returning bridge facility.
excessive values, modify the bridge exit to specify a limit to System action: The task is abnormally terminated with a
the values. CICS transaction dump. The user transaction is not started.
Module: DFHBRXM User response: Identify why CICS is running short on
storage.
Module: DFHBRXM

ABRY • ACHA
User response: Ensure that the DFHEITCU module is in the

ABRY
library and is valid for this release of CICS.
Explanation: CICS returned an unexpected error running the
bridge exit. This is a CICS internal error. If a valid version of DFHEITCU is already in the library, a
System action: The task is abnormally terminated with a CICS logic error has occurred. See Part 4 of the CICS Problem
CICS transaction dump. Determination Guide for guidance on how to proceed.
User response: You need further assistance from IBM to Module: DFHCAP
Module: DFHBRMS, DFHBRTC ACAD
Explanation: See ACAA.
ABRZ
Explanation: The bridge exit returned invalid data in the ACAI
BRXA. Explanation: An internal error has occurred when module
System action: The task is abnormally terminated with a DFHCAP was invoked. There was an invalid function code for
a domain call to DFHCAP.
User response: If a user supplied bridge exit was used,
System action:
review the format of the data returned by the exit.
v In a CICS environment, the CEDA transaction is abnormally
If a CICS supplied exit was used, this is a CICS error. You terminated with a CICS transaction dump.
need further assistance from IBM to resolve this problem. See v In a batch environment, processing is abnormally
Part 4 of the CICS Problem Determination Guide for guidance terminated with an operating system dump.
on how to proceed. User response: You need further assistance from IBM to
Module: DFHBRIC, DFHBRMS, DFHBRSP, DFHBRTC, resolve this problem. See Part 4 of the CICS Problem
DFHXMBR Determination Guide for guidance on how to proceed.
Module: DFHCAP
ABR3
Explanation: An unsupported BMS request was received by ACAJ
the bridge exit. Explanation: An internal error has occurred when module
System action: The task is abnormally terminated with a DFHCAP was invoked while processing an EXEC CICS
CICS transaction dump. CREATE command. The preallocated dynamic storage area
User response: The bridge only supports minimum function
was too small.
BMS and SEND TEXT. This transaction cannot be used in a
System action: The transaction executing the EXEC CICS
bridge environment.
CREATE command is abnormally terminated with a CICS
Module: DFHEMS
transaction dump.
ABSA resolve this problem. See Part 4 of the CICS Problem
Explanation: A message passed to DFHBSMSG is too long. Determination Guide for guidance on how to proceed.
This is a CICS internal error. Module: DFHCAP
dump.
User response: You need further assistance from IBM to ACEx
resolve this problem. See Part 4 of the CICS Problem Explanation: Abend codes with 'ACE' as the first three
Determination Guide for guidance on how to proceed. characters are issued by Language Environment, and are
Module: DFHTBS described in further detail in the IBM Language Environment for
z/VSE, Debugging Guide and Run-Time Messages manual.
ACAA
Explanation: This explanation applies to the two transaction ACHA
abend codes, ACAA and ACAD. CICS cannot find a match for Explanation: The remote server transaction, CEHS, is not at a
a function code in the language definition table because the compatible level to operate with the CICS/CMS system. This
parameterized resource definition contains an unrecognized usually indicates that the service levels of CICS/CMS and the
resource type code. The abend code issued depends on the remote server are different.
DFHCAP operation that was invoked before the error System action: CICS terminates the remote server transaction
occurred: abnormally with a dump.
Abend DFHCAP operation User response: You need further assistance from IBM to
ACAA ANALYZE resolve this problem. See Part 4 of the CICS Problem
ACAD DEFAULTS Determination Guide for guidance on how to proceed.
Problem determination: To diagnose a problem with the
remote server, it is generally helpful to obtain a trace of the
The cause of the abend is either:
remote server's activity up to the point of failure.
v The language definition table, DFHEITCU, in the library is
invalid for the release of CICS you are running, or A remote server trace is obtained by invoking the remote
v A CICS logic error has occurred. server with the TRACE option, (type CEHS TRACE). The
System action: remote server operates as normal but causes entries to be
v In a CICS environment, the CEDA transaction is abnormally written to a trace log in temporary storage. Note that main
terminated with a CICS transaction dump. storage, not auxiliary, is used for this queue hence large
v In a batch environment, processing is abnormally
terminated with an operating system dump.

ACHB • ACHH
amounts of memory can be used up if this trace is left on for

ACHE
long.
Explanation: The remote server received an unexpected data
The trace is found in a queue whose name is 'CEHSxxxx', frame from CICS/CMS. This indicates a logic error in the
where 'xxxx' is the four-character terminal identifier. The remote server.
queue can be browsed in text form or in hexadecimal form System action: CICS terminates the remote server abnormally
using CEBR. To find the terminal identifier, invoke CEBR on with a dump.
the terminal that has run CEHS, without giving a queue name. User response: Reestablish the connection between
The queue name will default to 'CEBRxxxx', where 'xxxx' is the CICS/CMS and the remote CICS system and try to use the
terminal identifier. remote server again. For further information, see the 'Problem
Determination' section for abend code ACHA.
Note: CEBR requires the queue name to be in UPPER CASE.
If the problem persists, you will need assistance from IBM to
For a description of the remote server and its trace entries and resolve the problem. See Part 4 of the CICS Problem
abend codes, see the CICS/VS Remote Server Diagnosis Manual Determination Guide for guidance on how to proceed.
(LC33-0438). Module: DFHCHS
Module: DFHCHS
ACHF
ACHB Explanation: The remote server attempted to send one of a
Explanation: The remote server has received a data frame series of data frames to CICS/CMS when, at this time, only a
from CICS/CMS that is out of sequence. A frame may have single frame is allowed. This indicates a logic error in the
been lost in transmission. remote server.
System action: CICS terminates the remote server abnormally System action: CICS terminates the remote server abnormally
with a dump. with a dump.
User response: Reestablish the connection between User response: Reestablish the connection between
CICS/CMS and the remote CICS system and try to use the CICS/CMS and the remote CICS system and try to use the
remote server again. For further information, see the 'Problem remote server again. For further information, see the 'Problem
Determination' section for abend code ACHA. Determination' section for abend code ACHA.
If the problem persists, you will need assistance from IBM to If the problem persists, you will need assistance from IBM to
resolve the problem. See Part 4 of the CICS Problem resolve the problem. See Part 4 of the CICS Problem
Determination Guide for guidance on how to proceed. Determination Guide for guidance on how to proceed.
Module: DFHCHS Module: DFHCHS
ACHC ACHG
Explanation: The remote server did not receive the expected Explanation: The remote server attempted to send data to
acknowledgement type data frame from CICS/CMS. CICS/CMS. However, it was not set to the correct mode to do
System action: CICS terminates the remote server abnormally so. This indicates a logic error in the remote server.
with a dump. System action: CICS terminates the remote server abnormally
User response: Reestablish the connection between with a dump.
CICS/CMS and the remote CICS system and try to use the User response: Reestablish the connection between
remote server again. For further information, see the 'Problem CICS/CMS and the remote CICS system and try to use the
Determination' section for abend code ACHA. remote server again. For further information, see the 'Problem
If the problem persists, you will need assistance from IBM to Determination' section for abend code ACHA.
resolve the problem. See Part 4 of the CICS Problem If the problem persists, you will need assistance from IBM to
Determination Guide for guidance on how to proceed. resolve the problem. See Part 4 of the CICS Problem
Module: DFHCHS Determination Guide for guidance on how to proceed.
Module: DFHCHS
ACHD
Explanation: The remote server did not receive the expected ACHH
response type data frame from CICS/CMS. Explanation: A TIOA has not been created from the data
System action: CICS terminates the remote server abnormally received by the remote server from CICS/CMS.
User response: Reestablish the connection between with a dump.
CICS/CMS and the remote CICS system and try to use the User response: Reestablish the connection between
remote server again. For further information, see the 'Problem CICS/CMS and the remote CICS system and try to use the
Determination' section for abend code ACHA. remote server again. For further information, see the 'Problem
If the problem persists, you will need assistance from IBM to Determination' section for abend code ACHA.
resolve the problem. See Part 4 of the CICS Problem If the problem persists, you will need assistance from IBM to
Determination Guide for guidance on how to proceed. resolve the problem. See Part 4 of the CICS Problem
Module: DFHCHS Determination Guide for guidance on how to proceed.
Module: DFHCHS

ACHI • ACHR
ACHI ACHN
Explanation: The remote server has received an unexpected Explanation: The remote server has tried to receive a request
return code from the Transformer 2 program. from CICS/CMS which failed repeatedly until the retry limit
System action: CICS terminates the remote server abnormally was exceeded.
User response: For further information, see the 'Problem with a dump.
Determination' section for abend code ACHA. User response: Reestablish the connection between
Module: DFHCHS CICS/CMS and the remote CICS system and try to use the
remote server again. For further information, see the 'Problem
ACHJ
Explanation: An error has occurred processing a request from If the problem persists, you will need assistance from IBM to
CICS/CMS which had the 'No-Reply' option. The remote resolve the problem. See Part 4 of the CICS Problem
server cannot, therefore, return the error condition to Determination Guide for guidance on how to proceed.
CICS/CMS. Module: DFHCHS
System action: CICS terminates the remote server abnormally
with a dump.
ACHO
User response: Reestablish the remote server and diagnose
Explanation: The remote server has tried to receive a reply
the problem by executing the same command from CECI
from CICS/CMS which failed repeatedly until the retry limit
under CICS/CMS without the NOCHECK option. For further
was exceeded.
information, see the 'Problem Determination' section for abend
code ACHA.
with a dump.
Module: DFHCHS
User response: Reestablish the connection between
CICS/CMS and the remote CICS system and try to use the
ACHK remote server again. For further information, see the 'Problem
Explanation: The transformer program has requested neither Determination' section for abend code ACHA.
EIP nor DLI to execute the request received from CICS/CMS.
This indicates a logic error because the request has to be
resolve the problem. See Part 4 of the CICS Problem
destined for either EIP or DLI.
Module: DFHCHS
with a dump.
User response: For further information, see the 'Problem
Determination' section for abend code ACHA. ACHP
Module: DFHCHS 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
ACHL
logic error has occurred.
Explanation: CICS/CMS has supplied a buffer to the remote
server which is not large enough to hold the reply that the
with a dump.
remote server has to return.
User response: For further information, see the 'Problem
with a dump.
Module: DFHCHS
remote server again. For further information, see the 'Problem ACHQ
Determination' section for abend code ACHA. Explanation: The remote server has a request from
CICS/CMS for DL/I resources but DL/I does not exist on the
CICS system.
resolve the problem. See Part 4 of the CICS Problem
with a dump.
Module: DFHCHS
User response: Either install DL/I into the CICS system, or
remove the DL/I call. For further information, see the
ACHM 'Problem Determination' section for abend code ACHA.
Explanation: The remote server has tried to receive a Module: DFHCHS
response from CICS/CMS which failed repeatedly until the
retry limit was exceeded.
ACHR
Explanation: The CICS/CMS remote server transaction
with a dump.
(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
remote server again. For further information, see the 'Problem
with a dump.
User response: Ensure the transaction is initiated with an
If the problem persists, you will need assistance from IBM to associated terminal and that the terminal is not defined as a
resolve the problem. See Part 4 of the CICS Problem console. For further information, see the 'Problem
Determination Guide for guidance on how to proceed. Determination' section for abend code ACHA.
Module: DFHCHS Module: DFHCHS

ACHS • ACN8
ACHS ACN3
Explanation: The CICS/OS2 remote server transaction Explanation: The program DFHUCNV cannot be linked. A
(CEHP) has been initiated and either the task is not user conversion program must be available (even if it only
terminal-oriented, or the associated terminal is a console. returns).
System action: CICS abnormally terminates the remote server System action: The transaction is abnormally terminated with
with a dump. a transaction dump.
User response: Ensure the transaction is initiated with an User response: Check that the DFHUCNV module is in the
associated terminal and that the terminal is not defined as a library and is valid for this release of CICS. Check the linkage
console. For further information, see the 'Problem of DFHUCNV and relink it with the correct AMODE if
Determination' section for abend code ACHA. necessary.
Module: DFHCHS Module: DFHCCNV
ACNA ACN4
Explanation: The table DFHCNV cannot be loaded. This is a Explanation: An unrecognized format of a DFHCNV table
general purpose abend code indicating that the LOAD request has been encountered.
for the conversion table, DFHCNV, has failed. System action: The transaction is abnormally terminated with
System action: The transaction is abnormally terminated with a transaction dump.
a transaction dump. User response: Re-assemble and re-link edit the DFHCNV
User response: Examine the transaction dump to determine macro.
the exact condition returned from LOAD request. Module: DFHCCNV
Module: DFHCCNV
ACN5
ACNB Explanation: An override for the default client code page has
Explanation: The program DFHUCNV cannot be linked This been received; however the value is not recognized.
is a general purpose abend code indicating that the LINK System action: The transaction is abnormally terminated with
request for the conversion program DFHUCNV, has failed. a transaction dump.
System action: The transaction is abnormally terminated with User response: Check that the client system is using one of
a transaction dump. the client code pages supported by CICS/390.
User response: Examine the transaction dump to determine Module: DFHCCNV
the exact condition returned from LINK request.
Module: DFHCCNV
ACN6
Explanation: The conversion between client code page and
ACN1 server code page is not supported by CICS/390; for example
Explanation: The table DFHCNV cannot be loaded. This is conversion has been requested between Japanese code page
probably because a table has not been pregenerated. It could 932 and Latin-1 code page 500.
also occur if the table DFHCNV has been linked above 16MB System action: The transaction is abnormally terminated with
but DFHCCNV has been linked below 16MB. a transaction dump.
System action: The transaction is abnormally terminated with User response: Ensure that the Client codepage, both default
a transaction dump. and overrides are in the same group as the Server codepage.
User response: Check that the DFHCNV module is in the for example client code page 852 from Latin-2 group, is only
library and is valid for this release of CICS. Check the linkage supported to server code page 870.
of DFHCNV and relink it with the correct AMODE if Module: DFHCCNV
necessary.
Module: DFHCCNV
ACN7
Explanation: An override for the default binary format has
ACN2 been received; however the value is not recognized.
Explanation: The table DFHCNV has been loaded but the System action: The transaction is abnormally terminated with
first record is in the wrong format. This is probably due to an a transaction dump.
error during assembly or linkedit, but could also be the result User response: Data formats should be either S/370 or
of a storage overwrite. INTEL, anything else is unsupported by CICS/390.
System action: The transaction is abnormally terminated with Module: DFHCCNV
a transaction dump.
User response: The table should be reassembled and linked.
Check the assemble and linkedit output. Check for any ACN8
messages issued from CICS indicating that storage overwrites Explanation: CICS data conversion is processing a FIELD
have occurred. defined as containing GRAPHIC characters (which are only
Module: DFHCCNV 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
a transaction dump.

ACN9 • ACRH
User response: Correct the FIELD definition.

ACRD
Module: DFHCCNV
Explanation: The system entry for the system to which
routing is to be performed could not be found.
ACN9 System action: The task is abnormally terminated with a
Explanation: The table DFHCNV cannot be loaded. This CICS transaction dump.
abend code is issued following a NOTAUTH condition being User response: Check the installed transaction definition to
raised during loading of the DFHCNV table. confirm that the system was correctly specified. Check that the
System action: The transaction is abnormally terminated with system entry is defined in the TCT.
a transaction dump. Module: DFHAPRT
User response: Ensure the resource security definitions are
correct.
ACRE
Module: DFHCCNV
Explanation: A transaction invoked from an APPC terminal
and specified in the installed transaction definition as remote
ACP1 has abnormally terminated because the link is out of service.
Explanation: DFHIC TYPE=GET response code is other than System action: The task is abnormally terminated.
the normal response during print key processing. User response: Wait until the link is available. The CICS
System action: The transaction is abnormally terminated with supplied transaction CEMT INQUIRE CONNECTION can be
a CICS transaction dump. The keyboard of the terminal on used to check the states of the links.
which the print key was depressed remains locked to indicate Module: DFHAPRT
the failure of the operation.
User response: Analyze the dump. The response code is in
ACRF
the low order byte of register 0.
Explanation: The relay program received a nonzero return
Module: DFHCPY
code from the dynamic router following its first invocation.
ACP2 CICS transaction dump.
Explanation: DFHIC TYPE=INITIATE response code is other User response: Use the dump to determine why the dynamic
than the normal response during print key processing. routing program has failed by checking the contents of the
System action: The transaction is abnormally terminated with passed COMMAREA DFHDYE for correctness. The
a CICS transaction dump. The keyboard of the terminal on COMMAREA address can be found from field TCACOMM in
which the print key was depressed remains locked to indicate the system TCA for the task. The COMMAREA fields are
the failure of the operation. mapped via the DFHDYPDS DSECT.
User response: Analyze the dump. The response code is in Module: DFHAPRT
low-order byte of register 0.
Module: DFHCPY
ACRG
Explanation: An ATI initiated remote transaction defined
ACRA with DYNAMIC(YES) has failed because there is no matching
Explanation: The relay program has been invoked without a entry in the AID chain.
terminal as its principal facility. Each AID in the chain has been checked and none has been
System action: The task is abnormally terminated with a found where
v The AID terminal ID matches that of the TCTTE
User response: Ensure that DFHAPRT has not been specified
v The installed transaction definition and the AID transaction
as the initial program of a task that is not terminal-related. IDs match
Module: DFHAPRT
v The AID is for a remote transaction
v The AID has not been canceled.
ACRB System action: The task is abnormally terminated with a
Explanation: The relay program has been invoked by a CICS system dump.
transaction that is not defined as remote. User response: The dump can be used to help ascertain the
System action: The task is abnormally terminated with a mismatch. Check the transactions listed in the TCTTE and
CICS transaction dump. PCT fields of the system dump against the AID chain.
User response: Check that the relay program is defined Module: DFHAPRT
correctly. Determine why DFHAPRT was invoked if the
transaction is not a remote transaction. ACRH
Module: DFHAPRT Explanation: The profile for the session that will carry
intersystem flows during transaction routing could not be
ACRC found.
Explanation: The relay program received an invalid response System action: The task is abnormally terminated with a
from DFHZCX. CICS transaction dump.
System action: The task is abnormally terminated with a User response: Check the installed transaction definition to
CICS transaction dump. confirm that TRPROF is correctly specified.
User response: You need further assistance from IBM to Module: DFHAPRT
Module: DFHAPRT

ACRI • ACSE
v The program cannot be loaded.

ACRI
v The program is defined as remote.
Explanation: An error occurred when attempting to link to
Module: DFHAPRT
the dynamic transaction routing program.
a CICS transaction dump. ACRO
Explanation: An attempt has been made to invoke the CRSQ
A message in the range DFHRT4417 to DFHRT4420 is written
transaction from a terminal. CRSQ is an internal CICS
to the CSMT log.
transaction and cannot be invoked in this way.
User response: Refer to the message sent to the CSMT log. It
identifies the cause of the link failure and provides further
User response: None. You can use CEMT and EXEC CICS
user guidance.
commands to cancel AIDs.
Module: DFHAPRT
Module: DFHCRQ
ACRJ
Explanation: An abend has occurred in the dynamic ACSA
Explanation: The remote scheduler task (CRSR) does not own
transaction routing program after a link has been executed
from DFHAPRT. an intersystem link TCTTE as its principal facility.
a CICS transaction dump. Message DFHRT4416 is written to CICS transaction dump.
User response: Ensure that DFHCRS is not specified as the
the CSMT log.
User response: Refer to message DFHRT4416. It identifies the initial program of a task other than CRSR. Check that the
abend in the dynamic transaction routing program and terminal operator did not enter CRSR.
provides further user guidance. Module: DFHCRS
Module: DFHAPRT
ACSB
ACRK Explanation: An unexpected reply was received from a
Explanation: The relay program has been invoked with no remote system in response to a request to schedule a task on
address for the principal facility. that system.
System action: The task is abnormally terminated with a System action: The task is abnormally terminated with a
CICS transaction dump. CICS transaction dump.
User response: You need further assistance from IBM to User response: You need further assistance from IBM to
resolve this problem. See Part 4 of the CICS Problem resolve this problem. See Part 4 of the CICS Problem
Module: DFHAPRT Module: DFHCRS
ACRL ACSC
Explanation: The task does not own the facility. Explanation: An unexpected request was received from a
remote system when expecting a request to schedule a task.
User response: You need further assistance from IBM to CICS transaction dump.
Module: DFHAPRT Determination Guide for guidance on how to proceed.
Module: DFHCRS
ACRM
ACSD
Explanation: In response to a request from the dynamic
Explanation: An internal logic error has been detected.
routing program, DFHAPRT has attempted an INITIAL_LINK
to a program that is not the initial program of the transaction System action: The task is abnormally terminated with a
for which the dynamic router has been invoked. The attempt
has failed.
System action: The transaction is abnormally terminated with resolve this problem. See Part 4 of the CICS Problem
Module: DFHCRS
User response: Examine the following possibilities:
v The autoinstall user-replaceable module (URM) was called
but is unable to do the autoinstall. ACSE
v The autoinstall URM was called but data supplied by the Explanation: Module DFHCRS has been attached in an
autoinstall URM is invalid. unsupported manner.
v The autoinstall URM was called, but there is no processing System action: CICS abnormally terminates the transaction
program table (PPT) entry for the autoinstall model. with a transaction dump.
v There is a problem with the autoinstall URM. User response: Module DFHCRS should be executed only by
v There is no PPT entry for the program, and either transaction CRSR, which executes with an MRO session, an
autoinstall is not active or the autoinstall URM indicated LU6.1 session or an LU type 6.2 conversation as its principal
that the program should not be autoinstalled. facility. Ensure that the transaction is being attached by a
v The program is disabled.

ACSF • ACTC
CRSR transaction in the connected system, and not by a user User response: You need further assistance from IBM to
transaction. resolve this problem. See Part 4 of the CICS Problem
If the transaction is being attached by a CRSR transaction, you Module: DFHCRS
will need assistance from IBM to resolve the problem. See Part
4 of the CICS Problem Determination Guide for guidance on how
to proceed. ACSM
Module: DFHCRS Explanation: Transaction CFTS has abended. The mass
flagging of terminals for deletion has failed.
ACSF
complete successfully. The task that first detects the purged
condition provides an exception trace.
Module: DFHCRS
User response: Investigate the reason why the task was ACSN
purged. It was purged either by the master terminal operator Explanation: Transaction CFTS has stalled. The mass flagging
or as a result of a deadlock timeout. of terminals for deletion has exceeded the expected time and
Module: DFHCRS is therefore assumed to have failed.
CICS transaction dump. A flag is set in the remote work
ACSG
element (RWE) to indicate that the mainline transaction has
assumed that CFTS has failed.
error will have provided an exception trace, a console message
and, possibly, a system dump (depending on the options
Module: DFHCRS
specified in the dump table).
CICS transaction dump. ACTA
User response: Please see the related error message produced Explanation: The relay program running in the
by the domain that detected the original error. terminal-owning region has received an unexpected request
Module: DFHCRS from the application owning region. The request received is in
violation of CICS transaction routing protocols.
ACSH The request will be in the DFHLUCDS DSECT in DFHZTSP's
Explanation: The processing of APPC mapped data requires LIFO – field LUCOPN0
the generation of an LU6.2 attach FMH with default values. In System action: The task is abnormally terminated with a
particular, the sync level requested is defaulted to 2. However, CICS transaction dump.
the session that is to be used has been bound with a sync level User response: You need further assistance from IBM to
of 1. resolve this problem. See Part 4 of the CICS Problem
CICS transaction dump. Module: DFHZTSP
User response: Check that:
v The entry in the TCT for the remote system has been
defined with parallel sessions ACTB
v The remote system can support a sync level of 2 Explanation: The relay program running in the
v The correct sync level has been requested. terminal-owning region issued a terminal control WRITE,LAST
Module: DFHCRS request to the application-owning system, and received a
nonzero return code from terminal control.
ACSI This is the usual return code from terminal control in

Explanation: An APPC conversation failure occurred when TCATPAPR.
an attach between CICS systems was issued. System action: The task is abnormally terminated with a
System action: The task is abnormally terminated with a CICS transaction dump.
CICS transaction dump. User response: Use the transaction dump to determine why
User response: Check the connection to the remote CICS terminal control was unable to process the request.
system and try to reestablish it. Module: DFHZTSP
Module: DFHCRS
ACTC
ACSL Explanation: The relay program running in the
Explanation: CICS has been unable to attach a transaction to terminal-owning region issued a terminal control request to
perform a mass flag (CFTS) or mass remote delete (CDTS) free its session to the application-owning system, and received
request. a nonzero return code from terminal control.
System action: The task is abnormally terminated with a This is the usual return code from terminal control in
CICS transaction dump. TCATPAPR.

ACTD • ACTL
System action: The task is abnormally terminated with a Module: DFHZTSP

User response: Use the transaction dump to determine why
terminal control was unable to process the request. ACTH
Module: DFHZTSP Explanation: A privileged allocate was issued against a
remote LU 6.2 system.
ACTD CICS transaction dump.
Explanation: The relay program running in the User response: You need further assistance from IBM to
terminal-owning region issued a terminal control resolve this problem. See Part 4 of the CICS Problem
WRITE,WAIT,READ request to the application-owning system, Determination Guide for guidance on how to proceed.
and received a nonzero return code from terminal control. Module: DFHZISP
This is the usual return code from terminal control in
TCATPAPR. ACTI
System action: The task is abnormally terminated with a Explanation: The relay transaction has an ISC or MRO
CICS transaction dump. session as its principal facility. However the TCTTE for that
User response: Use the transaction dump to determine why session is not owned by the task.
terminal control was unable to process the request. System action: The task is abnormally terminated with a
Module: DFHZTSP CICS transaction dump.
ACTE
Explanation: The relay program running in the
Module: DFHCRT
terminal-owning region attempted to free its session with the
APPC terminal, and received a nonzero return code from
terminal control. ACTJ
Explanation: The principal facility of the relay transaction is
The return code will be in the DFHLUCDS DSECT in
not a TCTTE.
DFHZTSP's LIFO field, LUCRCODE.
User response: Task CXRT should only be started in a
terminal-owning region by an ALLOCATE request issued in
terminal control was unable to process the request. The
an application-owning region against a remote APPC device.
terminal session may have failed.
The principal facility of the task should be an ISC or MRO
Module: DFHZTSP
link. Check that your CICS system is defined in such a way
that this will always be the case. Also ensure that program
ACTF DFHCRT is started only by task CXRT.
Explanation: The relay program running in the Module: DFHCRT
terminal-owning region issued a terminal control request to
free its session to the application-owning system, and received
ACTK
a nonzero return code from terminal control.
This return code can be found in the TCA field, TCATPAPR. request to the storage manager (SM) domain was able to
System action: The task is abnormally terminated with a complete successfully. The task that first detected the purged
CICS transaction dump. condition will have provided an exception trace.
User response: Use the transaction dump to determine why System action: The task is abnormally terminated with a
terminal control was unable to process the request. The CICS transaction dump.
transaction on the application-owning region may have User response: Investigate the reason why the task was
abnormally terminated or the session may have failed. purged. It was either purged by the master terminal operator
Module: DFHZTSP or as a result of a deadlock timeout.
Module: DFHZISP
ACTG
Explanation: The relay program running in the ACTL
terminal-owning region issued a request to attach a Explanation: An error (INVALID, DISASTER or unexpected
transaction in the application-owning region, but the response EXCEPTION response) has occurred on a call to the storage
received from that region was invalid. manager (SM) domain. The domain that detected the original
The return code in the TCA (field TCATPAPR) will be and, possibly, a system dump (depending on the options
nonzero, and either there will be no TIOA (field TCTTEDA in specified in the dump table).
the TCTTE is zero) or there will be no FMH7 at the start of the System action: The task is abnormally terminated with a
TIOA. CICS transaction dump.
System action: The task is abnormally terminated with a User response: See the related message produced by the
CICS transaction dump. domain that detected the original error.
User response: Use the transaction dump to determine why Module: DFHZISP
transaction on the application-owning region may have
abnormally terminated or the session may have failed.

ACUA • ACUJ
ACUA ACUF
Explanation: DFHZXRL was called with a request which is Explanation: A session between the application-owning
not supported for transaction routing. region and the terminal-owning region was not allocated
because the request was incorrectly specified.
The request is located in the DFHLUC parameter list which is
printed in the exception trace. DFHZXRL is called from transaction dump and an exception trace entry.
DFHZARL, which will put details of the request in its trace
entry.
transaction dump and an exception trace entry.
Module: DFHZXRL
Determination Guide for guidance on how to proceed. ACUG
Module: DFHZXRL 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
ACUB
that the profile could not be located as an installed transaction
Explanation: The parameter list passed to DFHZXRL for an
definition, although an earlier attempt to locate it was
ALLOCATE request does not contain the TCTSE address of a
successful.
remote APPC terminal.
The return code is located both in TCATPAPR and in the trace
The TCTSE address is located in the DFHLUC parameter list
entry on return from DFHZARQ.
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
Module: DFHZXRL ACUH
Explanation: A request to allocate a session between the
application-owning region and the terminal-owning region
ACUC
failed. The return code from the ALLOCATE request indicated
Explanation: The TCTSE address passed to DFHZXRL is not
that the requested session is already owned by the TCA.
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
Module: DFHZXRL ACUI
Explanation: An ISC session between the application-owning
region and the terminal-owning region was not allocated
ACUD
because the MODENAME named in the profile could not be
Explanation: The profile DFHCICSR could not be located as
found. The profile DFHCICSR as supplied by IBM does not
an installed profile definition.
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
User response: Check that the IBM-supplied profile
definition for the terminal-owning region.
DFHCICSR is correctly defined and installed to CICS.
Module: DFHZXRL
User response: Ensure that the MODENAME specified in
ACUE profile DFHCICSR was also specified when defining the
Explanation: A request to DFHZTSP to build a surrogate SESSIONS to the terminal-owning region.
TCTTE was not satisfied. Module: DFHZXRL
transaction dump and an exception trace entry. ACUJ
User response: You need further assistance from IBM to Explanation: A session between the application-owning
resolve this problem. See Part 4 of the CICS Problem region and the terminal-owning region was not allocated
Determination Guide for guidance on how to proceed. because the maximum session count for the mode group
Module: DFHZXRL specified in profile DFHCICSR is zero.

ACUK • ACUT

ACUO
User response: Use the CEMT transaction to set sessions in
Explanation: A terminal control READ request has failed.
the required mode group available for use.
The transaction routing program in the application-owning
Module: DFHZXRL
region attempted to receive data from the terminal-owning
region, and received a nonzero return code from terminal
ACUK control.
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
terminal control was unable to process the request. This abend
defined in the remote system entry is also defined with a
code may result when:
system entry in the TCT.
v The relay program in the terminal-owning region terminates
Module: DFHZXRL
abnormally. In this case, determine the reason why the relay
program has abnormally terminated.
ACUL v The session has failed.
Explanation: The transaction routing program in the Module: DFHZXRL
application-owning region issued a terminal control Note: The description of this abend also applies to ACUQ,
WRITE,WAIT,READ request to the terminal-owning region, ACUS and ACU1.
and received a nonzero return code from terminal control.
The return code is located both in TCATPAPR and in the trace ACUP
entry on return from DFHZARQ. Explanation: The transaction routing program in the
System action: The task is abnormally terminated with a application-owning region did not receive a rollback from the
transaction dump and an exception trace entry. terminal-owning region. This violates CICS transaction routing
User response: Use the transaction dump to determine why protocols.
terminal control was unable to process the request. This abend The trace from the terminal-owning region will show its
code may result when: response to the application-owning region.
v The relay program in the terminal-owning region terminates System action: The task is abnormally terminated with a
abnormally. In this case, determine the reason why the relay transaction dump and an exception trace entry.
program has abnormally terminated. User response: You need further assistance from IBM to
v The session has failed. resolve this problem. See Part 4 of the CICS Problem
Module: DFHZXRL Determination Guide for guidance on how to proceed.
Note: The description of this abend also applies to ACUX Module: DFHZXRL
and ACUZ. Note: The description of this abend also applies to ACUR.
ACUM ACUQ
Explanation: A request to DFHZTSP to free a surrogate
Explanation: Refer to the description of abend ACUO.
TCTTE was not satisfied.
transaction dump and an exception trace entry. ACUR
User response: You need further assistance from IBM to Explanation: Refer to the description of abend ACUP.
Module: DFHZXRL ACUS
Explanation: Refer to the description of abend ACUO.
ACUN
Explanation: A terminal control FREE request has failed. The ACUT
transaction routing program in the application-owning region Explanation: The transaction routing program in the
attempted to free the session with the terminal-owning region, application-owning region did not receive either a syncpoint
and received a nonzero return code from terminal control. or a rollback from the terminal-owning region. This violates
CICS transaction routing protocols.
entry on return from DFHZARQ. The trace from the terminal-owning region will show its
System action: The task is abnormally terminated with a response to the application-owning region.
transaction dump and an exception trace entry. System action: The task is abnormally terminated with a
User response: Use the transaction dump to determine why transaction dump and an exception trace entry.
terminal control was unable to process the request. This abend User response: You need further assistance from IBM to
code may result when: resolve this problem. See Part 4 of the CICS Problem
v The relay program in the terminal-owning region terminates Determination Guide for guidance on how to proceed.
abnormally. In this case, determine the reason why the relay Module: DFHZXRL
v The session has failed.
Module: DFHZXRL

ACUV • ACU4
ACUV ACUZ
Explanation: The transaction routing program in the Explanation: Refer to the description of abend ACUL.
application-owning region issued a terminal control ISSUE
ABEND request on an MRO link to the terminal-owning
region, and received a nonzero return code from terminal ACU0
control. Explanation: The transaction routing program in the
application-owning region issued a terminal control
The return code is located both in TCATPAPR and in the trace WRITE,LAST,WAIT request to the terminal-owning region,
entry on return from DFHZIS1. and received a nonzero return code from terminal control.
transaction dump and an exception trace entry. The return code is located both in TCATPAPR and in the trace
User response: Use the transaction dump to determine why entry on return from DFHZARQ.
terminal control was unable to process the request. This abend System action: The task is abnormally terminated with a
code may result when: transaction dump and an exception trace entry.
v The relay program in the terminal-owning region terminates User response: Use the transaction dump to determine why
abnormally. In this case, determine the reason why the relay terminal control was unable to process the request. This abend
program has abnormally terminated. code may result when:
v The session has failed. v The relay program in the terminal-owning region terminates
Module: DFHZXRL abnormally. In this case, determine the reason why the relay
ACUW Module: DFHZXRL
Explanation: The transaction routing program in the
application-owning region issued a terminal control ISSUE
ERROR request on an MRO link to the terminal-owning ACU1
region, and received a nonzero return code from terminal Explanation: Refer to the description of abend ACUO.
control.
The return code is located both in TCATPAPR and in the trace ACU2
entry on return from DFHZIS1. Explanation: The transaction routing program in the
System action: The task is abnormally terminated with a application-owning region received a response from the
transaction dump and an exception trace entry. terminal-owning region which violates CICS transaction
User response: Use the transaction dump to determine why routing protocols.
terminal control was unable to process the request. This abend The trace from the terminal-owning region will show its
code may result when: response to the application-owning region.
v The relay program in the terminal-owning region terminates System action: The task is abnormally terminated with a
abnormally. In this case, determine the reason why the relay transaction dump and an exception trace entry.
program has abnormally terminated. User response: You need further assistance from IBM to
v The session has failed. resolve this problem. See Part 4 of the CICS Problem
Module: DFHZXRL Determination Guide for guidance on how to proceed.
Module: DFHZXRL
ACUX
Explanation: Refer to the description of abend ACUL. ACU3
ACUY application-owning region attempted to set the conversation
Explanation: The transaction routing program in the state machine to a state which violates CICS transaction
application-owning region issued a terminal control routing protocols.
WRITE,WAIT request to the terminal-owning region, and The register containing the state can be determined from the
received a nonzero return code from terminal control. assembler listing.
The return code is located both in TCATPAPR and in the trace System action: The task is abnormally terminated with a
entry on return from DFHZARQ. transaction dump and an exception trace entry.
System action: The task is abnormally terminated with a User response: You need further assistance from IBM to
transaction dump and an exception trace entry. resolve this problem. See Part 4 of the CICS Problem
User response: Use the transaction dump to determine why Determination Guide for guidance on how to proceed.
terminal control was unable to process the request. This abend Module: DFHZXRL
v The relay program in the terminal-owning region terminates ACU4
abnormally. In this case, determine the reason why the relay Explanation: The transaction routing program in the
program has abnormally terminated. application-owning region issued a SET request to the
v The session has failed. conversation state machine and received a nonzero return
Module: DFHZXRL code. This violates CICS transaction routing protocols.
The trace entry on return from DFHZUSR will show the
request type and current state.

ACU5 • ACVG

ACVD
terminal-owning region issued a READ,WAIT request to the
Module: DFHZXRL
application-owning region, and received a nonzero return code
from terminal control.
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
v The program in the application-owning region terminates
regions.
abnormally. In this case, determine the reason why the
Module: DFHZXRL
ACVA Module: DFHZXRT
terminal-owning region issued a terminal control ACVE
WRITE,WAIT,READ request to the application-owning region, Explanation: The transaction routing program in the
and received a nonzero return code from terminal control. terminal-owning region issued a WRITE request to the
The return code is located both in TCATPAPR and in the trace application-owning region, and received a nonzero return code
entry on return from DFHZARQ. from terminal control.
System action: The task is abnormally terminated with a The return code is located both in TCATPAPR and in the trace
transaction dump and an exception trace entry. entry on return from DFHZARQ.
User response: Use the transaction dump to determine why System action: The task is abnormally terminated with a
terminal control was unable to process the request. This abend transaction dump and an exception trace entry.
code may result when: User response: Use the transaction dump to determine why
v The program in the application-owning region terminates terminal control was unable to process the request. This abend
abnormally. In this case, determine the reason why the code may result when:
program has abnormally terminated. v the program in the application-owning region terminates
v The session has failed. abnormally. In this case, determine the reason why the
Module: DFHZXRT program has abnormally terminated.
v the session has failed.
ACVB Module: DFHZXRT
terminal-owning region attempted to issue an ISSUE SIGNAL ACVF
request on an MRO link to the application-owning region. Explanation: The transaction routing program in the
This violates CICS transaction routing protocols. terminal-owning region issued a WRITE,LAST,WAIT request
System action: The task is abnormally terminated with a to the application-owning region, and received a nonzero
transaction dump and an exception trace entry. return code from terminal control.
resolve this problem. See Part 4 of the CICS Problem The return code is located both in TCATPAPR and in the trace
Determination Guide for guidance on how to proceed. entry on return from DFHZARQ.
Module: DFHZXRT System action: The task is abnormally terminated with a
ACVC terminal control was unable to process the request. This abend
Explanation: The transaction routing program in the code may result when:
terminal-owning region issued an ISSUE SIGNAL request on v The program in the application-owning region terminates
an LU 6.2 link to the application-owning region, and received abnormally. In this case, determine the reason why the
a nonzero return code from terminal control. program has abnormally terminated.
The return code is located in the DFHLUC parameter list v The session has failed.
which is printed in the exception trace. Module: DFHZXRT
transaction dump and an exception trace entry. ACVG
User response: Use the transaction dump to determine why Explanation: The transaction routing program in the
terminal control was unable to process the request. This abend terminal-owning region issued a FREE request to free the
code may result when: session with the LU 6.2 terminal, and received a nonzero
v The program in the application-owning region terminates return code from terminal control.
program has abnormally terminated. The return code is located in the DFHLUC parameter list
v The session has failed. which is printed in the exception trace.
Module: DFHZXRT System action: The task is abnormally terminated with a

ACVH • ACVO

ACVM
terminal-owning region issued an ISSUE ERROR request on
terminal session may have failed.
an LU 6.2 link, and received a nonzero return code from
Module: DFHZXRT
terminal control.
The return code is located in the DFHLUC parameter list
ACVH
which is printed in the exception trace.
terminal-owning region issued a FREE request to free the
session with the application-owning region, and received a
The return code is located both in TCATPAPR and in the trace code may result when:
entry on return from DFHZARQ. v The program in the connected region terminates abnormally.
System action: The task is abnormally terminated with a In this case, determine the reason why the program has
transaction dump and an exception trace entry. abnormally terminated.
User response: Use the transaction dump to determine why v The session has failed.
terminal control was unable to process the request. This abend Module: DFHZXRT
ACVN
terminal-owning region issued an ISSUE ERROR request on
an MRO link to the application-owning region, and received a
Module: DFHZXRT

ACVK
entry on return from DFHZIS1.
terminal-owning region issued an ISSUE ABEND request on
an LU 6.2 link, and received a nonzero return code from
terminal control.
The return code is located in the DFHLUC parameter list code may result when:
which is printed in the exception trace. v The program in the application-owning region terminates
System action: The task is abnormally terminated with a abnormally. In this case, determine the reason why the
transaction dump and an exception trace entry. program has abnormally terminated.
User response: Use the transaction dump to determine why v The session has failed.
terminal control was unable to process the request. This abend Module: DFHZXRT
v The program in the connected region terminates abnormally.
ACVO
In this case, determine the reason why the program has
terminal-owning region issued an ISSUE PREPARE request
and received either a nonzero return code or a response which
Module: DFHZXRT
violates CICS transaction routing protocols.
The return code is located in TCASPRC and the response is
ACVL
located in TCASPSN1.
terminal-owning region issued an ISSUE ABEND request on
an MRO link to the application-owning region, and received a
User response: Use the transaction dump to determine
whether the problem is caused by the return code or the
The return code is located both in TCATPAPR and in the trace response. If terminal control was unable to process the request,
entry on return from DFHZIS1. the abend may occur when:
System action: The task is abnormally terminated with a v The program in the connected region terminates abnormally.
transaction dump and an exception trace entry. In this case, determine the reason why the program has
User response: Use the transaction dump to determine why abnormally terminated.
terminal control was unable to process the request. This abend v The session has failed.
Otherwise the distributed application programs may have
violated APPC conversation protocols.
Module: DFHZXRT
Module: DFHZXRT

ACVP • ADBE
System action: The catch-up transaction, CXCU, is

ACVP
abnormally terminated with a CICS transaction dump. Both
active and alternate CICS systems continue, but the alternate
terminal-owning region did not receive an FMH43 from the
CICS system is less effective in the event of a takeover. For
application-owning region. This violates CICS transaction
example, terminal back-up sessions may not be established.
routing protocols.
The trace from the application-owning region will show its the error persists, diagnose the problem from the dump.
response to the terminal-owning region. Module: DFHCXCU
ADBA
Explanation: A failure occurred while CICS was attempting
to read the dynamic log.
System action: The backout process is abnormally
Module: DFHZXRT terminated. Because it is possible that data integrity might not
be maintained, CICS is abnormally terminated.
ACVQ User response: CICS should be emergency restarted to
ensure that data integrity is maintained. You need further
terminal-owning region issued a request to the APPC terminal,
and received a nonzero return code from terminal control.
proceed.
Both the request and the return code are located in the Module: DFHDBP
DFHLUC parameter list which is printed in the exception
trace.
ADBB
System action: The task is abnormally terminated with a Explanation: The deferred work element (DWE) chain from
transaction dump and an exception trace entry. the TCA has become corrupted during DWE processing.
User response: Use the transaction dump to determine why System action: The backout process is abnormally
terminal control was unable to process the request. The terminated. Because it is possible that data integrity might not
terminal session may have failed or be in the wrong state, for be maintained, CICS is abnormally terminated.
example, as the result of both the terminal and application User response: CICS should be emergency restarted to
issuing SYNCPOINT ROLLBACK at the same time. ensure that data integrity is maintained. You need further
Module: DFHZXRT assistance from IBM to resolve this problem. See Part 4 of the
proceed.
ACVR Module: DFHDBP
terminal-owning region issued a SEND,LAST,WAIT request to
the LU 6.2 terminal, and received a nonzero return code from ADBC
terminal control. Explanation: A DL/I log record is too large for the DL/I
interface.
The return code is located in the DFHLUC parameter list System action: The backout process is abnormally
which is printed in the exception trace. terminated. Since it is possible that data integrity might not be
System action: The task is abnormally terminated with a maintained, CICS is abnormally terminated.
transaction dump and an exception trace entry. User response: CICS should be emergency restarted to
User response: Use the transaction dump to determine why ensure that data integrity is maintained. You need further
terminal control was unable to process the request. The assistance from IBM to resolve this problem. See Part 4 of the
terminal session may have failed. CICS Problem Determination Guide for guidance on how to
Module: DFHZXRT proceed.
Module: DFHDBP
ACWA
Explanation: CICS CWTO transaction has failed because the ADBE
task does not own a terminal (TCTTE) as its principal facility. Explanation: An invalid filename (DBRFID) was found on
This has probably happened because CWTO has been started the dynamic log.
as an EXEC CICS START transid without a terminal ID. System action: The backout process is abnormally
System action: The transaction is abnormally terminated terminated. Since it is possible that data integrity might not be
maintained, CICS is abnormally terminated.
without a transaction dump.
User response: CICS should be emergency restarted to
User response: Retry with a terminal ID value or enter
ensure that data integrity is maintained. You need further
CWTO from a terminal.
Module: DFHCWTO
proceed.
ACXA Module: DFHDBP
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.

ADBF • AEC1
ADBF ADIR
Explanation: The PSB name in a DL/I backout record differs Explanation: The abend code is issued for either of the
from that scheduled to the current task. following reasons:
System action: The backout process is abnormally v A DFHDI or DFHBMS request was issued when the
terminated. Because it is possible that data integrity might not DFHDIP program was generated as a dummy.
be maintained, CICS is abnormally terminated. v A DFHDI TYPE=RECEIVE or TYPE=NOTE was attempted
User response: CICS should be emergency restarted to but the transaction identification did not specify either
ensure that data integrity is maintained. You need further INBFMH=DIP or INBFMH=ALL.
assistance from IBM to resolve this problem. See Part 4 of the System action: A CICS transaction dump is provided to
CICS Problem Determination Guide for guidance on how to assist in problem determination.
proceed. User response: Either generate a DFHDIP program into the
Module: DFHDBP system or specify INBFMH correctly on the profile definition.
Module: DFHDIP
ADBH
Explanation: An invalid service module identifier was found
ADLH
on the dynamic log (DBRSVMID).
Explanation: The CICS DL/I restart task could not complete
because a necessary step failed. The task has done some
terminated. Since it is possible that data integrity might not be
maintained, CICS is abnormally terminated. essential recovery operations and abnormally terminated itself
User response: CICS should be emergency restarted to with abend code ADLH.
ensure that data integrity is maintained. You need further System action: CICS writes a transaction dump for the DL/I
assistance from IBM to resolve this problem. See Part 4 of the restart task.
CICS Problem Determination Guide for guidance on how to CICS sends two messages to the console, one to identify the
proceed.
error detected by the DL/I restart task, and one, DFHDL3928,
Module: DFHDBP
to say that the task has failed. A third message follows either
to say that CICS has terminated abnormally with a dump, or
ADBK to ask you to reply GO or CANCEL. Depending on the nature
Explanation: An invalid function id was found of the original error, you may see messages from some other
(DBRMODFN) while CICS was attempting file backout from system component (for example, an access method).
the dynamic log. User response: First, if CICS has requested a response, you
System action: The backout process is abnormally must reply. If you reply 'GO', CICS continues processing, but
terminated. Since it is possible that data integrity might not be without DL/I.
User response: CICS should be emergency restarted to If you reply 'CANCEL', CICS terminates abnormally with a
ensure that data integrity is maintained. You need further dump.
assistance from IBM to resolve this problem. See Part 4 of the Use the messages and dumps to find out the cause of the
failure.
proceed.
Module: DFHDLRP
Module: DFHDBP
ADPL
ADBL
Explanation: A server program has issued a command which
Explanation: An invalid error code was found (DBRERRCD)
is restricted in the distributed program link (DPL)
while CICS was attempting to retry file backout.
environment. Certain API and CPI-RR requests are not
allowed in the DPL environment. See the CICS Application
terminated. Since it is possible that data integrity might not be
Programming Guide for a list of these restricted commands.
User response: CICS should be emergency restarted to A server program is a program which has been remotely
ensure that data integrity is maintained. You need further linked, or a program defined to run with the DPL subset.
assistance from IBM to resolve this problem. See Part 4 of the System action: CICS abends the transaction with a
CICS Problem Determination Guide for guidance on how to transaction dump.
proceed. User response: Remove the restricted commands from the
Module: DFHDBP server program, or run the server program locally.
Module: DFHEIP, DFHCPIR
ADEF
Explanation: A severe error has been encountered when AEC1
executing transaction CLS3. Explanation: An attempt has been made to use the
System action: CLS3 is abnormally terminated with a Command Level Interpreter (CECI) or the Enhanced Master
transaction dump. CICS issues message DFHZC4948. Terminal (CEMT) or an RDO (CEDA, CEDB, CEDC)
User response: See message DFHZC4948 for further transaction on a terminal that is not supported.
guidance. System action: The task is abnormally terminated with a
Module: DFHCLS3 CICS transaction dump.
User response: Use a terminal that is supported by the
Command Level Interpreter, Enhanced Master Terminal, or
RDO transaction.
Module: DFHECIP, DFHECSP, DFHEMTP, DFHESTP,
DFHEOTP, DFHEDAP

AEC2 • AED2

AEC2
Explanation: An attempt has been made to use the
Module: DFHEDFX
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. AEDC
System action: The task is abnormally terminated with a Explanation: The program EDF has terminated because a
CICS transaction dump. GETMAIN request to the storage manager failed.
User response: Use a display terminal that is supported by System action: The task is abnormally terminated with a
the Command Level Interpreter or Enhanced Master Terminal CICS transaction dump.
or RDO transaction. User response: Use the transaction dump to determine why
Module: DFHECIP, DFHECSP, DFHEMTP, DFHESTP, the request has failed.
DFHEOTP, DFHEDAP Module: DFHEDFX
AEC7 AEDD
Explanation: LE for z/VSE has encountered an unexpected Explanation: CICS has attempted to attach the EDF task to
error during the THREAD INITIALIZATION phase while display the user request but the attach has failed.
attempting to execute a LE for z/VSE enabled program. The System action: The task is abnormally terminated with a
return code received from LE for z/VSE is placed into the CICS transaction dump.
field EIBRESP2. User response: Use the transaction dump to determine why
System action: Message DFHAP1200 is issued and the the attach has failed.
transaction is abnormally terminated. The program is disabled. Module: DFHEDFX
User response: Refer to the error message or messages issued
by LE for z/VSE to determine the cause of the problem.
Module: DFHAPLI AEDE
Explanation: CICS has suspended the user task to allow the
EDF task to complete but an error has occurred while
AEC8 performing the suspend.
Explanation: LE for z/VSE has encountered an unexpected System action: The task is abnormally terminated with a
error during the RUNUNIT INITIALIZATION phase while CICS transaction dump.
attempting to execute a LE for z/VSE enabled program. User response: Use the transaction dump to determine why
System action: The return code received from LE for z/VSE the suspend has failed.
is placed into the field EIBRESP2. Message DFHAP1200 is Module: DFHEDFX
issued and the transaction is abnormally terminated. The
program is disabled.
User response: Refer to the error message or messages issued AEDH
by LE for z/VSE to determine the cause of the problem. Explanation: An error occurred when CICS called the
Module: DFHAPLI Program Manager in order to discover details of the user
program that has invoked EDF.
AEC9 CICS transaction dump.
Explanation: LE for z/VSE has encountered an unexpected User response: Use the transaction dump to determine why
error during the RUNUNIT BEGIN INVOCATION phase the call has failed.
while attempting to execute a LE for z/VSE enabled program. Module: DFHEDFX
System action: The return code received from LE for z/VSE
is placed into the field EIBRESP2. Message DFHAP1200 is
issued and the transaction is abnormally terminated. The AED1
program is disabled. Explanation: This abend is produced as a result of either:
User response: Refer to the error message or messages issued v An attempt to use the execution diagnostic facility (EDF) on
by LE for z/VSE to determine the cause of the problem. an unsupported terminal, or
Module: DFHAPLI v An attempt to initiate the temporary storage browse
transaction (CEBR) with a non-terminal principal facility.
v Using the temporary storage browse transaction (CEBR) on
AEDA
an unsupported device.
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). User response: Use a terminal or device that is properly
System action: The task is abnormally terminated with a supported.
CICS transaction dump. Module: DFHEDFP, DFHEDFBR
the start has failed.
AED2
Module: DFHEDFX
Explanation: The program EDF has terminated a task and
placed this abend code in the terminated task's TCA. This
AEDB occurs because execution of EDF is about to be abnormally
Explanation: DFHEDFP has been passed an invalid EDFXA. terminated. A probable reason for EDF being terminated is
This is an internal CICS error. that a line, control unit, or a terminal has been put out of
System action: The task is abnormally terminated with a service.
CICS transaction dump. System action: The task is abnormally terminated with a
User response: You need further assistance from IBM to CICS transaction dump.

AED3 • AEIA
User response: Use a terminal that is supported as a display

AED9
terminal by EDF. A CICS transaction dump of the task
Explanation: A temporary storage error has occurred in EDF.
terminated with this abend code is available for review.
This could be caused by an input/output error on temporary
Module: DFHEDFX
storage or because temporary storage data is full.
System action: EDF is abnormally terminated with a CICS
AED3 transaction dump.
Explanation: The program EDF has terminated a task and User response: Investigate the reason for the temporary
placed this abend code in the terminated task's TCA. The storage request failure. Ensure that the definition of the
termination occurs because execution of EDF is about to be temporary storage data set is correct.
abnormally terminated. See the CICS Problem Determination Guide for further guidance
One possible cause of an abend in EDF is incorrect data being in dealing with temporary storage problems.
sent to the terminal by the user task. Module: DFHEDFD
AEIA
User response: A CICS transaction dump of the terminated
Explanation:
task and also a similar dump for EDF, when its termination
was abnormally terminated, are available for review.
Module: DFHEDFX Note: The description of this abend also applies to AEID to
AEI9, AEXC to AEXF, AEXI to AEXL, AEXS, AEXU, AEXW,
AEXX, AEX0 to AEX3, AEX5, AEX6, AEX7, AEYA to AEYC,
AED4 AEYE to AEY3, and AEY7.
Explanation: An internal logic error has been detected in
EDF module DFHEDFP.
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
User response: This indicates a CICS logic error. You need
application program has not executed an EXEC CICS
of the CICS Problem Determination Guide for guidance on how HANDLE CONDITION command for that condition. This will
to proceed. cause DFHEIP to take the system action for the condition in
Module: DFHEDFP question. In most cases, the system action will be to abend the
transaction.
AED5 Because of their similar characteristics, the abend codes for the
Explanation: An internal logic error was been detected in EXEC interface program are described as a group. The codes
EDF. Insufficient dynamic storage was pre-allocated. and their corresponding exceptional conditions are as follows:
System action: EDF is terminated abnormally with dumps
having dump codes CXSP, RMIN, PAGE, LDIN. The user task
continues.
Code Condition
User response: The problem may be avoided by less complex
user interactions with EDF. If the problem persists, you may AEIA ERROR
need further assistance. See Part 4 of the CICS Problem AEID EOF
Determination Guide for guidance on how to proceed. AEIE EODS
Module: DFHEDFD
AEIG INBFMH
AEIH ENDINPT
AED6 AEII NONVAL
Explanation: An internal logic error was detected in EDF.
AEIJ NOSTART
System action: EDF is terminated abnormally with dumps
having dump codes CXSP, RMIN, PAGE, LDIN. The user task AEIK TERMIDERR
continues. AEIL FILENOTFOUND
User response: The problem may be avoided by less complex AEIM NOTFND
user interactions with EDF. If the problem persists, you may
AEIN DUPREC
need further assistance. See Part 4 of the CICS Problem
Determination Guide for guidance on how to proceed. AEIO DUPKEY
Module: DFHEDFU AEIP INVREQ
AEIQ IOERR
AED8 AEIR NOSPACE
Explanation: A terminal control error has occurred in AEIS NOTOPEN
DFHEDFX. AEIT ENDFILE
AEIU ILLOGIC
User response: You need further assistance from IBM to AEIV LENGERR
resolve this problem. See Part 4 of the CICS Problem AEIW QZERO
Determination Guide for guidance on how to proceed. AEIZ ITEMERR
Module: DFHEDFX
AEI0 PGMIDERR
AEI1 TRANSIDERR
AEI2 ENDDATA

AEID • AEIH
using the EXEC CICS HANDLE CONDITION command). If

Code Condition necessary, use the contents of the EIBRESP2 field or the
EIBRCODE in the EIB to assist in determining the cause of the
AEI3 INVTSREQ exceptional condition.
AEI4 EXPIRED Problem determination: The function code of the command
AEI8 TSIOERR that produced the exceptional response and the response code
AEI9 MAPFAIL can be found in the EXEC interface block (EIB). The EIB is
AEXC RESIDERR part of a larger control block, used by DFHEIP, known as the
EXEC interface storage block (EIS). The EIS is addressed by
AEXD CCERROR the TCAEISA, which is the system part of the TCA + X'90' The
AEXE MAPERROR EIB is pointed to from the EIS + X'8'.
AEXF ESCERROR
The function code may be located at offset X'1B' in the EIB
AEXI TERMERR while the response codes may be one of the following at the
AEXJ ROLLEDBACK given offsets:
AEXK END EIBRCODE
AEXL DISABLED X'1D'
AEXS OUTDESCRERR EIBRESP
X'4C'
AEXU NOTPOSS EIBRESP2
AEXW SUPPRESSED X'50'
AEXX TASKIDERR
AEX0 TCIDERR The CICS Application Programming Reference gives translations
AEX1 DSNNOTFOUND of the encoded functions and their responses.
AEX2 LOADING
AEX3 MODELIDERR Analysis: Because these abend codes are directly related to
exceptional conditions that can be specified in HANDLE
AEX5 PARTNERIDERR CONDITION commands, the application programmer should
AEX6 PROFILEIDERR decide whether the condition is one that should be handled by
AEX7 NETNAMEIDERR the application (for example ENDFILE), or one that requires
AEYA INVERRTERM modifications to the application or CICS tables.
AEYB INVMPSZ Module: DFHEIP
AEYC IGREQID
AEYE INVLDC AEID
AEYG JIDERR Explanation: EOF condition not handled.
AEYH QIDERR This is one of a number of abends issued by the EXEC
AEYJ DSSTAT interface program. Because of their similar characteristics these
AEYK SELNERR abends are described as a group.
AEYL FUNCERR See the description of abend AEIA for further details.
AEYM UNEXPIN
AEYN NOPASSBKRD AEIE
AEYO NOPASSBKWR Explanation: EODS condition not handled.
AEYP SEGIDERR
This is one of a number of abends issued by the EXEC
AEYQ SYSIDERR interface program. Because of their similar characteristics these
AEYR ISCINVREQ abends are described as a group.
AEYT ENVDEFERR
See the description of abend AEIA for further details.
AEYU IGREQCD
AEYV SESSIONERR
AEYX USERIDERR AEIG
Explanation: INBFMH condition not handled.
AEYY NOTALLOC
AEYZ CBIDERR This is one of a number of abends issued by the EXEC
AEY0 INVEXITREQ interface program. Because of their similar characteristics these
abends are described as a group.
AEY1 INVPARTNSET
AEY2 INVPARTN See the description of abend AEIA for further details.
AEY3 PARTNFAIL
AEY7 NOTAUTH AEIH
Explanation: ENDINPT condition not handled.
a CICS transaction dump. This is one of a number of abends issued by the EXEC
User response: Change the application program either to interface program. Because of their similar characteristics these
prevent the condition recurring, to check it by using the RESP abends are described as a group.
option, or to handle the condition when it does occur (by See the description of abend AEIA for further details.

AEII • AEIV
AEII AEIP
Explanation: NONVAL condition not handled. Explanation: INVREQ condition not handled.
This is one of a number of abends issued by the EXEC This is one of a number of abends issued by the EXEC
interface program. Because of their similar characteristics these interface program. Because of their similar characteristics these
abends are described as a group. abends are described as a group.
See the description of abend AEIA for further details. See the description of abend AEIA for further details.
AEIJ AEIQ
Explanation: NOSTART condition not handled. Explanation: IOERR condition not handled.
AEIK AEIR
Explanation: TERMIDERR condition not handled. Explanation: NOSPACE condition not handled.
AEIL AEIS
Explanation: FILENOTFOUND condition not handled. Explanation: NOTOPEN condition not handled.
AEIM AEIT
Explanation: NOTFND condition not handled. Explanation: ENDFILE condition not handled.
AEIN AEIU
Explanation: DUPREC condition not handled. Explanation: ILLOGIC condition not handled.
AEIO AEIV
Explanation: DUPKEY condition not handled. Explanation: LENGERR condition not handled.

AEIW • AELB
AEIW AEI8
Explanation: QZERO condition not handled. Explanation: TSIOERR condition not handled.
AEIZ AEI9
Explanation: ITEMERR condition not handled. Explanation: MAPFAIL condition not handled.
AEI0 AELA
Explanation: PGMIDERR condition not handled. Explanation: The executing function has been purged before
control could be returned.
This is one of a number of abends issued by the EXEC System action: The transaction is marked to be abnormally
interface program. Because of their similar characteristics these terminated with abend code AELA.
abends are described as a group. User response: Investigate the reason the task was purged. It
See the description of abend AEIA for further details. was purged either by the master terminal operator, or as a
result of a deadlock timeout.
AEI1 If the task was purged by the master terminal operator, this
Explanation: TRANSIDERR condition not handled. may have been in an attempt to clear the system which
appeared to be deadlocked for some reason.
interface program. Because of their similar characteristics these If the task was timed out automatically as a result of the
abends are described as a group. DTIMOUT value being exceeded, this may be due to
insufficient main storage being available for the number of
See the description of abend AEIA for further details. tasks in the system. If the amount of main storage cannot be
increased then the number of tasks in the system should be
reduced to avoid short-on-storage situations. Another
AEI2
Explanation: ENDDATA condition not handled.
option for the transaction.
This is one of a number of abends issued by the EXEC Module: DFHETL
interface program. Because of their similar characteristics these
AELB
See the description of abend AEIA for further details. Explanation: The executing function has been purged before
control could be returned.
System action: The transaction is marked to be abnormally
AEI3 terminated with abend code AELB.
Explanation: INVTSREQ condition not handled. User response: Investigate the reason the task was purged. It
This is one of a number of abends issued by the EXEC was purged either by the master terminal operator, or as a
interface program. Because of their similar characteristics these result of a deadlock timeout.
abends are described as a group. If the task was purged by the master terminal operator, this
See the description of abend AEIA for further details. may have been in an attempt to clear the system which

AEI4
DTIMOUT value being exceeded, this may be due to
Explanation: EXPIRED condition not handled.
This is one of a number of abends issued by the EXEC tasks in the system. If the amount of main storage cannot be
interface program. Because of their similar characteristics these increased then the number of tasks in the system should be
abends are described as a group. reduced to avoid short-on-storage situations. Another
See the description of abend AEIA for further details. option for the transaction.
Module: DFHEGL

AEMA • AETG
been in an attempt to clear the system which appeared to be

AEMA
deadlocked for some reason.
Explanation: An error (INVALID or DISASTER response) has
occurred on a call to the application (AP) domain when a If the task was timed out automatically as a result of the
request for set user exit active could not be serviced. DTIMOUT value being exceeded, this may be due to
System action: The task is abnormally terminated. The insufficient main storage being available for the number of
domain that detected the original error issues a console tasks in the system. If the amount of main storage cannot be
message and might provide an exception trace, and depending increased, reduce the number of tasks in the system to avoid
on the options specified in the dump table, a system dump. short-on-storage situations. Another possibility is to increase
User response: See the associated console message for further the value of the DTIMOUT option for the transaction.
guidance. Module: DFHUEM
Module: DFHUEM
AETA
AEMB Explanation: A CICS transaction has issued a non-CICS
Explanation: An error (INVALID or DISASTER response) has command via an application "stub" (an expansion of a
occurred on a call to the loader (LD) domain. The domain that DFHRMCAL macro). Program DFHERM has determined that
detected the original error will have provided an exception the exit has been disabled since the previous DFHRMCAL
trace, a console message, and possibly a system dump request was issued from the transaction.
(depending on the options in the dump table). System action: The task is abnormally terminated with a
System action: The task is abnormally terminated with a transaction dump
CICS transaction dump (depending on the options in the User response: Notify your system programmer.
dump table). Module: DFHERM
User response: See the related message from the domain that
detected the original error.
Module: DFHUEM AETC
Explanation: A CICS transaction has issued a non-CICS
command via an application "stub" (an expansion of a
AEMP DFHRMCAL macro). However, the task-related user exit
Explanation: The task was purged before a set active request (TRUE) is not known to program manager.
to the application (AP) domain was able to complete System action: The task is abnormally terminated with a
successfully. The domain that first detected the purged transaction dump
condition may provide an exception trace. User response: Ensure that the TRUE as identified to the
System action: The task is abnormally terminated with a DFHRMCAL macro has been correctly defined to CICS.
CICS transaction dump. Module: DFHERM
User response: Investigate why the task was purged. This is
either as a result of a purge from the master terminal operator
via the CEMT transaction, or by the task being timed out after AETF
waiting for longer than the DTIMOUT (deadlock timeout) Explanation: The task was purged before a request to the
value specified for the transaction. storage manager (SM) domain was able to complete
successfully. The domain that first detected the purged
If the master terminal operator purged the task, this may have condition will have provided an exception trace.
been in an attempt to clear the system which appeared to be System action: The task is abnormally terminated with a
deadlocked for some reason. CICS transaction dump.
via the CEMT transaction, or by the task being timed out after
waiting for longer than the DTIMOUT (deadlock timeout)
tasks in the system. If the amount of main storage cannot be
value specified for the transaction.
increased, reduce the number of tasks in the system to avoid
short-on-storage situations. Another possibility is to increase If the master terminal operator purged the task, this may have
the value of the DTIMOUT option for the transaction. been in an attempt to clear the system which appeared to be
Module: DFHUEM deadlocked for some reason.
AEMQ DTIMOUT value being exceeded, this may be due to
Explanation: The task was purged before an insufficient main storage being available for the number of
IDENTIFY_PROGRAM request to the loader (LD) domain was tasks in the system. If the amount of main storage cannot be
able to complete successfully. The domain that first detected increased, reduce the number of tasks in the system to avoid
the purged condition provides an exception trace. short-on-storage situations. Another possibility is to increase
System action: The task is abnormally terminated with a the value of the DTIMOUT option for the transaction.
CICS transaction dump (depending on the options in the Module: DFHERM
dump table).
either as a result of a purge from the master terminal operator AETG
via the CEMT transaction, or by the task being timed out after Explanation: An error (INVALID, DISASTER or unexpected
waiting for longer than the DTIMOUT (deadlock timeout) EXCEPTION response) has occurred on a call to the storage
value specified for the transaction. manager (SM) domain. The domain that detected the original
If the master terminal operator purged the task, this may have

AETH • AEXU
and, possibly, a system dump (depending on the options

AEXE
specified in the dump table).
Explanation: MAPERROR condition not handled.
CICS transaction dump. This is one of a number of abends issued by the EXEC
User response: See the related message produced by the interface program. Because of their similar characteristics these
domain that detected the original error. abends are described as a group.
Module: DFHERM
AETH AEXF
Explanation: The task was purged before a request to the Explanation: ESCERROR condition not handled.
storage manager (SM) domain was able to complete
successfully. The domain that first detected the purged This is one of a number of abends issued by the EXEC
condition will have provided an exception trace. interface program. Because of their similar characteristics these
System action: The task is abnormally terminated with a abends are described as a group.
CICS transaction dump. See the description of abend AEIA for further details.
via the CEMT transaction, or by the task being timed out after AEXI
waiting for longer than the DTIMOUT (deadlock timeout) Explanation: TERMERR condition not handled.
If the master terminal operator purged the task, this may have interface program. Because of their similar characteristics these
been in an attempt to clear the system which appeared to be abends are described as a group.
deadlocked for some reason. See the description of abend AEIA for further details.
AEXJ
insufficient main storage being available for the number of Explanation: ROLLEDBACK condition not handled.
increased, reduce the number of tasks in the system to avoid This is one of a number of abends issued by the EXEC
short-on-storage situations. Another possibility is to increase interface program. Because of their similar characteristics these
the value of the DTIMOUT option for the transaction. abends are described as a group.
Module: DFHERM
AETI AEXK
Explanation: An error (INVALID, DISASTER or unexpected Explanation: END condition not handled.
manager (SM) domain. The domain that detected the original This is one of a number of abends issued by the EXEC
error will have provided an exception trace, a console message interface program. Because of their similar characteristics these
and, possibly, a system dump (depending on the options abends are described as a group.
specified in the dump table). See the description of abend AEIA for further details.
User response: See the related message produced by the AEXL
domain that detected the original error. Explanation: DISABLED condition not handled.
Module: DFHERM
AEXC abends are described as a group.
Explanation: RESIDERR condition not handled. See the description of abend AEIA for further details.
AEXS
Explanation: OUTDESCRERR condition not handled.
AEXD abends are described as a group.
Explanation: CCERROR condition not handled. See the description of abend AEIA for further details.
AEXU
Explanation: During execution of an EXEC CICS command, a
See the description of abend AEIA for further details. NOTPOSS condition has been raised on encountering an
invalid parameter. This is probably caused by a previous
storage overlay.

AEXW • AEYA
User response: Refer to abend AEIA for an explanation of

AEX0
how to determine the function code of the CICS command
Explanation: TCIDERR condition not handled.
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.
Module: DFHEIDTI, DFHEIQDS, DFHEIQSA, DFHEIQSC,
DFHEIQSM, DFHEIQSP DFHEIQST, DFHEIQSX AEX1
Explanation: DSNNOTFOUND condition not handled.
AEXW This is one of a number of abends issued by the EXEC
Explanation: SUPPRESSED condition not handled. interface program. Because of their similar characteristics these
interface program. Because of their similar characteristics these See the description of abend AEIA for further details.
See the description of abend AEIA for further details. AEX2
Explanation: LOADING condition not handled.
AEXX This is one of a number of abends issued by the EXEC
Explanation: TASKIDERR condition not handled. interface program. Because of their similar characteristics these
interface program. Because of their similar characteristics these See the description of abend AEIA for further details.
See the description of abend AEIA for further details. AEX3
Explanation: MODELIDERR condition not handled.
AEXY This is one of a number of abends issued by the EXEC
Explanation: The executing transaction has been purged interface program. Because of their similar characteristics these
before control could be returned. abends are described as a group.
This can arise when the transaction is purged while See the description of abend AEIA for further details.
v A CICS command was being processed
v The transaction was waiting to be dispatched
System action: The transaction is abnormally terminated with AEX5
a CICS transaction dump. Explanation: PARTNERIDERR condition not handled.
User response: Contact your system programmer to This is one of a number of abends issued by the EXEC
determine why the transaction has been purged. interface program. Because of their similar characteristics these
Module: DFHEDCP, DFHEEI, DFHEIPRT, DFHEIPSE, abends are described as a group.
DFHEIPSH, DFHEIQDN, DFHEIQDS, DFHEIQDU,
DFHEIQIR, DFHEIQMS, DFHEIQMT, DFHEIQSA, See the description of abend AEIA for further details.
DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSM, DFHEIQSP,
DFHEIQSQ, DFHEIQST, DFHEIQSX, DFHEIQTR, DFHEIQUE, AEX6
DFHEIQVT, DFHEOP, DFHESC, DFHESE, DFHESN, Explanation: PROFILEIDERR condition not handled.
DFHTIEM, DFHETRX, DFHXTP, DFHZTSP
AEXZ abends are described as a group.
Explanation: A command has failed due to a serious failure
in a CICS component (resource manager). See the description of abend AEIA for further details.
abend code AEXZ. CICS takes a transaction dump, unless AEX7
module DFHDUIO is not loaded. Explanation: NETNAMEIDERR condition not handled.
User response: Use the transaction dump to determine the
cause of the failure. For further assistance, or if module This is one of a number of abends issued by the EXEC
DFHDUIO is not loaded and no transaction dump is available, interface program. Because of their similar characteristics these
contact your system programmer. abends are described as a group.
Module: DFHEDCP, DFHEEI, DFHEIACQ, DFHEIPRT, See the description of abend AEIA for further details.
DFHEIPSE, DFHEIPSH, DFHEIQDN, DFHEIQDS,
DFHEIQDU, DFHEIQIR, DFHEIQMS, DFHEIQMT,
DFHEIQSA, DFHEIQSC, DFHEIQSJ, DFHEIQSK, DFHEIQSM, AEYA
DFHEIQSP, DFHEIQSQ, DFHEIQST, DFHEIQSX, DFHEIQTR, Explanation: INVERRTERM condition not handled.
DFHEIQUE, DFHEIQVT, DFHEOP, DFHESC, DFHESE,
DFHESN, DFHTIEM, DFHETRX, DFHXTP, DFHZTSP interface program. Because of their similar characteristics these

AEYB • AEYO

AEYH
Explanation: QIDERR condition not handled.
AEYB
Explanation: INVMPSZ condition not handled.
This is one of a number of abends issued by the EXEC abends are described as a group.
abends are described as a group. See the description of abend AEIA for further details.

AEYJ
Explanation: DSSTAT condition not handled.
AEYC
Explanation: IGREQID condition not handled. This is one of a number of abends issued by the EXEC
This is one of a number of abends issued by the EXEC abends are described as a group.
abends are described as a group. See the description of abend AEIA for further details.

AEYK
Explanation: SELNERR condition not handled.
AEYD
Explanation: A transaction has requested that CICS access a This is one of a number of abends issued by the EXEC
storage area that the transaction itself could not access. This interface program. Because of their similar characteristics these
occurred when an invalid storage area was passed to CICS as abends are described as a group.
an output parameter on an EXEC CICS command.
System action: The transaction is abnormally terminated with See the description of abend AEIA for further details.
User response: Examine the trace to find the exception trace
entry created by DFHEISR and then identify the parameter in AEYL
error. If the abend is handled, EXEC CICS ASSIGN ASRASTG, Explanation: FUNCERR condition not handled.
ASRAKEY, and ASRAREGS give additional information about This is one of a number of abends issued by the EXEC
the abend. At the time of the abend, register 2 points to the interface program. Because of their similar characteristics these
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. AEYM
v If storage protection is active, change the EXECKEY on the Explanation: UNEXPIN condition not handled.
CEDA definition for the program that issued the EXEC
CICS command from USER to CICS. This is one of a number of abends issued by the EXEC
v If storage protection is active, change the TASKDATAKEY interface program. Because of their similar characteristics these
attributes on the transaction definition from CICS to USER. abends are described as a group.
Module: DFHSRP
AEYE
AEYN
Explanation: INVLDC condition not handled.
Explanation: NOPASSBKRD condition not handled.
AEYG
AEYO
Explanation: JIDERR condition not handled.
Explanation: NOPASSBKWR condition not handled.

AEYP • AEY6
AEYP AEYY
Explanation: SEGIDERR condition not handled. Explanation: NOTALLOC condition not handled.
AEYQ AEYZ
Explanation: SYSIDERR condition not handled. Explanation: CBIDERR condition not handled.
AEYR AEY0
Explanation: ISCINVREQ condition not handled. Explanation: INVEXITREQ condition not handled.
AEYT AEY1
Explanation: ENVDEFERR condition not handled. Explanation: INVPARTNSET condition not handled.
AEYU AEY2
Explanation: IGREQCD condition not handled. Explanation: INVPARTN condition not handled.
AEYV AEY3
Explanation: SESSIONERR condition not handled. Explanation: PARTNFAIL condition not handled.
AEYX AEY6
Explanation: USERIDERR condition not handled. 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
abends are described as a group. have been found. But the activation count for the program in
See the description of abend AEIA for further details. 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.

AEY7 • AFCB
User response: You need further assistance from IBM to User response: Either redefine and install a new definition
resolve this problem. See Part 4 of the CICS Problem for the transaction with TASKDATALOC(BELOW), or relink
Determination Guide for guidance on how to proceed. the programs as AMODE 31.
Module: DFHUEM Module: DFHEIP
AEY7 AEZB
Explanation: NOTAUTH condition not handled. Explanation: A transaction has been defined with a
TASKDATALOC(ANY), and the application is attempting to
This is one of a number of abends issued by the EXEC call a task related user exit. However the task related user exit
interface program. Because of their similar characteristics these has been linkedited AMODE 24 and enabled with the
abends are described as a group. LINKEDITMODE option, thereby directing CICS to invoke it
in AMODE 24. An AMODE 24 task related user exit cannot
See the description of abend AEIA for further details. run when the calling application is running with
TASKDATALOC(ANY), as this would cause a protection
exception, or a storage overwrite.
AEY8
Explanation: No DSA was found on the chain while trying to
User response: Either redefine and install a new definition
free dynamic storage for an assembler language program
for the transaction with TASKDATALOC(BELOW), or modify
using an EXEC CICS command. the task related user exit so that it is invoked in AMODE 31.
System action: The transaction is abnormally terminated with Module: DFHERM
User response: Ensure that the DFHEIENT, DFHEISTG, and
DFHEIEND macro invocations are correctly positioned and AEZC
retry. If the error persists, you will need further assistance. See Explanation: A transaction has been defined with a
Part 4 of the CICS Problem Determination Guide for guidance on TASKDATALOC(ANY), but a program within the transaction
how to proceed. is defined to run AMODE 24. CICS cannot invoke the AMODE
Module: DFHEIP 24 program when the transaction is running with
TASKDATALOC(ANY), as this would cause a protection
exception, or a storage overwrite.
AEY9 System action: The transaction is abnormally terminated with
Explanation: One of the following: a CICS transaction dump.
v An EXEC CICS command has been issued that is not User response: Either redefine and install a new definition
supported by the EXEC interface program DFHEIP. for the transaction with TASKDATALOC(BELOW), or relink
v A transaction has issued an EXEC CICS command which is the program as AMODE 31.
supported in principle by the EXEC interface program Module: DFHAPLI
DFHEIP, but for which the prerequisite function has not
been included in the current CICS start-up.
AEZD
v A non-CICS command has been issued via an application
Explanation: An attempt has been made to run a program
"stub" (expansion of a DFHRMCAL macro), and the
defined as EXECKEY(USER) as part of a transaction defined as
program DFHERM has detected that the necessary TASKDATAKEY(CICS). These attributes are incompatible and
non-CICS support is not available. the transaction is abended. This incompatibility could occur as
v An attempt has been made to use remote resources, but the a result of the program definition being autoinstalled. See the
local SYSID has been specified in an EXEC CICS command, CICS Customization Guide and the CICS Resource Definition
or vice versa. Guide for more information about program autoinstall.
v An attempt has been made to use remote resources, but ISC System action: The transaction is abnormally terminated with
is not supported. a CICS transaction dump.
v An EXEC CICS command contains an invalid AID or User response: Redefine and install a new definition either
CONDITION identifier. This indicates that the EXEC CICS for the transaction with TASKDATAKEY(USER), or for the
command has become corrupted. 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
User response: Check that the sysid specified and the
definition for the program. If you are using your own copies
resource names were correct. If not, notify the system
of CICS-supplied program definitions, they must be defined as
programmer. Either the command (or an application stub) has
EXECKEY(CICS).
become corrupted, or the unavailable function needs to be Module: DFHAPLI
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. AFCB
Module: DFHEIP, DFHEEI Explanation: Module DFHFCEI issued a resource level
security check (RSLC) request to module DFHXSRC and
received a response other than OK or EXCEPTION.
AEZA System action: The transaction is abnormally terminated with
Explanation: A transaction has been defined with a a transaction dump.
TASKDATALOC(ANY), but the programs within the User response: Examine the trace to find the exception trace
transaction are running AMODE 24. The exec interface entry created by DFHXSRC at the time of the error. Use this
program is therefore is unable to access the TCA for the trace entry to determine the cause of the return code from
application. Furthermore, any reference to the EIB would DFHXSRC.
cause the transaction to fail with an protection exception. Module: DFHFCEI

AFCC • AFCN
AFCC AFCH
Explanation: An internal logic error was detected when Explanation: The transaction has issued a request for a
calling the file control request processing module DFHFCFR. remote shared data table for which it has an active browse,
Either DFHFCFR returned an INVALID response to its caller but the table has in the meantime been disabled or closed by
indicating an error in the caller's parameter list, or DFHFCFR the owning CICS system, or the owning CICS system has
passed back a return code that was not recognized by its failed.
caller. System action: The requesting transaction abends with a
System action: The transaction is abnormally terminated with transaction dump.
a transaction dump.
User response: You need further assistance from IBM to CICS continues normally.
resolve this problem. See Part 4 of the CICS Problem User response: In the application owning region, take
Determination Guide for guidance on how to proceed. whatever action normally follows the issue of a FORCE
Module: DFHFCEI, DFHDMPCA, DFHDBP request in, or the failure of, the file owning CICS system.
See the CICS Shared Data Tables Guide for further guidance.
Module: DFHFCEI
AFCD
Explanation: During an attempt to locate an AFCT entry, the
table manager program DFHTMP has returned a "disastrous AFCJ
error" response that could not be handled by its caller. Explanation: DFHFCU issued a call to DFHFCFS to open a
System action: The transaction is abnormally terminated with file. A purged error was returned from DFHFCFS because the
a transaction dump. task has been waiting for a resource longer than the
User response: You need further assistance from IBM to DTIMEOUT interval specified for the CSFU transaction.
Determination Guide for guidance on how to proceed. CICS transaction dump. CICS processing continues.
Module: DFHFCEI 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
AFCE
TRDUMPCODE command.
Explanation: A GETMAIN for FFLE storage has failed.
Module: DFHFCU
a transaction dump.
User response: Retry the failed transaction. AFCM
Module: DFHFCEI Explanation: During the loading of a data table by the CSSY
transaction, an abend was detected, or a domain call returned
a response (such as DISASTER) after which normal processing
AFCF
could not continue.
Explanation: A deadlock has been detected between two or
System action: A message is issued (one of DFHFC0945,
more tasks issuing file control requests.
DFHFC0946, DFHFC0947 or DFHFC0948). Loading of the data
System action: The task that would have entered deadlock is
table is terminated and CSSY abends.
abended with a CICS transaction dump.
User response: If this abend is produced as a result of an
User response: Examine this transaction and other
abend during loading, message DFHFC0945 is issued. If it is a
transactions in the system that update the same files to find
result of a domain call failure, depending on which domain
the cause of the deadlock, then correct the error.
the failure was returned by, one of the messages DFHFC0946,
When transactions update several files within the same unit of DFHFC0947 or DFHFC0948 is issued. Refer to the description
work, all transactions should update these files in the same of the message for further information and guidance.
order. A transaction that abends AFCF may be retried by Module: DFHDTLDX
specifying RESTART(YES) in the transaction definition and by
coding a suitable DFHREST program.
Module: DFHFCEI AFCN
Explanation: The transaction issued a file request that caused
file control to attempt to create a journal record but the record
AFCG is too large. This indicates that a journal referenced in the file
Explanation: A file has issued a sequence of file control control table (FCT) entry for this file has a block size that is
requests that would cause it to deadlock itself. too small to allow the journal record to be written.
System action: The task that would have entered deadlock is System action: The task is abnormally terminated with a
abended with a CICS transaction dump. CICS transaction dump.
User response: Examine the previous requests made by this User response: Correct the discrepancy between the FCT and
transaction against this file to identify the cause of the the journal control table (JCT). Either a journal number is
deadlock, then correct the error. incorrect in the FCT entry, or the journal should be redefined
with a larger block size.
A common cause of self deadlock occurs with VSAM LSR
files, when an attempt is made to read a record that is in the The journal in error can be the system log, the forward
same CI as a record that is the subject of a READ UPDATE or recovery log, or the journal used for auto-journalling. Look for
WRITE MASSINSERT request. the exception trace taken at the time of the error. This formats
Module: DFHFCEI the journal control area (JCA). The JCA identifies the number
of the journal in error.
If the module that detected the error is DFHDMPCA, the error
is associated with a journal referenced in the definition of the
CSD (DFHCSD).
Module: DFHDMPCA, DFHFCEI

AFCP • AFC7
the purge is detected and the issuing of the ABEND.

AFCP
User response: In some instances, for example if the
Explanation: The transaction issued a file request that caused
transaction was explicitly cancelled, no further action is
file control to attempt to create a journal record but journal
necessary.
control has issued an IDERROR response. This indicates that a
journal referenced in the file control table (FCT) entry for this Otherwise examine the exception trace and the transaction
file is not defined in the journal control table (JCT). dump to identify the point at which the purge occurred.
System action: Because this is a severe error that can affect Module: DFHDBP, DFHDMPCA, DFHFCEI
the ability to perform forward recovery or backout,
immediately after the IDERROR is received from journal
control, CICS writes a message to the console, records an AFCZ
exception trace entry and takes a system dump. Subsequently, Explanation: The transaction issued a file request resulting in
the task is abnormally terminated with a CICS transaction a call to the main file control program (DFHFCFR). A
dump. "disastrous error" response was returned from DFHFCFR to its
User response: Correct the discrepancy between the FCT and caller.
the JCT. Either a journal number is incorrect in the FCT entry, System action: At the time the disastrous error is detected,
or a JCT entry is missing. CICS writes a message to the console, records an exception
trace entry and takes a system dump. The trace and dump
The journal in error can be the system log, the forward identify the point of error.
recovery log, or the journal used for auto-journalling. Look for
the exception trace taken at the time of the error. This formats Subsequently, the task is abnormally terminated with a CICS
the JCA. The JCA identifies the number of the journal in error. transaction dump.
User response: The system programmer should use the trace
If the module that detected the error is DFHDMPCA, the error and dumps to determine what the error is, and why it has
is in the definition of the CSD (DFHCSD). occurred.
Module: DFHDMPCA, DFHFCEI Module: DFHDBP, DFHDMPCA, DFHFCEI
AFCQ AFC0
Explanation: The transaction issued a file request that caused Explanation: An attempt has been made to update a file after
file control to attempt to create a journal record but journal file control restart failed.
control has issued a LERROR response. This indicates that a System action: The transaction is abnormally terminated with
journal referenced in the file control table (FCT) entry for this a transaction dump.
file has a block size that is too small to allow the journal User response: Determine the cause of the failure in file
record to be written. If the file has been defined for forward control restart. Restart CICS.
recovery, the system attempts to back out any changes made Module: DFHFCEI, DFHDMPCA
immediately prior to the abend, and tries to record this in the
backout log. This may result in a second LERROR which
causes a system abend. AFC2
System action: Because this is a severe error that can affect Explanation: DFHFCU issued a call to DFHFCFS to open a
the ability to perform forward recovery or backout, file. A disastrous error was returned from DFHFCFS.
immediately after the IDERROR is received from journal System action: The task is abnormally terminated with a
control, CICS writes a message to the console, records an CICS transaction dump.
exception trace entry and takes a system dump. Subsequently,
the task is abnormally terminated with a CICS transaction At the time the disastrous error is detected, CICS writes a
dump. message to the console, records an exception trace entry and
User response: Correct the discrepancy between the FCT and takes a system dump.
the JCT. Either a journal number is incorrect in the FCT entry, CICS processing continues.
or the journal should be redefined with a larger block size. User response: The system programmer should examine the
The journal in error can be the system log, the forward trace, the system dump and any related CICS messages to
recovery log, or the journal used for auto-journalling. Look for identify the cause of the error.
the exception trace taken at the time of the error. This formats Module: DFHFCU
the JCA. The JCA identifies the number of the journal in error.
If the module that detected the error is DFHDMPCA, the error AFC4
is associated with a journal referenced in the definition of the Explanation: The transaction issued a file request for a record
CSD (DFHCSD). whose length does not match the defined record length of the
Module: DFHDMPCA, DFHFCEI recoverable fixed length file.
AFCY User response: Adjust the length of the record to that of the
Explanation: The transaction issued a file request resulting in fixed length of the file.
a call to the main file control program (DFHFCFR). During the Module: DFHFCEI
processing of the request the transaction was purged (that is,
was the subject of an explicit CANCEL request, or timed out,
or selected by CICS for termination in an attempt to alleviate AFC7
an SOS condition). A "purged" response was returned from Explanation: The CICS definition file (CSD) manager
DFHFCFR to its caller. (DFHDMPCA) issued a request to DFHFCFS to enable, open
System action: The task is abnormally terminated with a or close the DFHCSD file. A "disastrous error" response was
CICS transaction dump. returned from DFHFCFS to DFHDMPCA.
Exception trace entries are made between the point at which CICS transaction dump.

AFC9 • AICH
At the time the disastrous error is detected, CICS writes a

AICC
message to the console, records an exception trace entry and
Explanation: An incorrect response was returned from a
takes a system dump.
timer (TI) domain request.
CICS processing continues. System action: The task is abnormally terminated with a
User response: The system programmer should examine the CICS transaction dump.
trace, the system dump and any related CICS messages to User response: You need further assistance from IBM to
identify the cause of the error. resolve this problem. See Part 4 of the CICS Problem
Module: DFHDMPCA Determination Guide for guidance on how to proceed.
Module: DFHTAJP, DFHICP
AFC9
Explanation: A task attempted to update a file that was AICD
associated with a data set that has failed backout. Because the Explanation: A incorrect response was returned from a kernel
data set is in a corrupt state, no further updates are allowed (KE) domain request.
and as part of backout failure processing, all files referencing System action: The task is abnormally terminated with a
the corrupt data set are closed. Existing users of the file are CICS transaction dump.
allowed to complete their requests if these do not modify the User response: You need further assistance from IBM to
file (for example, a browse can be completed). resolve this problem. See Part 4 of the CICS Problem
System action: The main file control program DFHFCVS Determination Guide for guidance on how to proceed.
detects that an update is being attempted for a file referencing Module: DFHICP
a data set which has failed backout. CICS then writes message
DFHFC0306 to the console, and records an exception trace
entry. AICE
Explanation: An incorrect response was returned from a
DFHFCVS then returns a BACKOUT_FAILED response to the dispatcher (DS) domain request (other than AICG).
calling program, which then terminates the transaction with System action: The task is abnormally terminated with a
abend code AFC9. CICS transaction dump.
User response: The data set will need to be recovered before User response: You need further assistance from IBM to
any further updates may be made to it. Refer to the earlier resolve this problem. See Part 4 of the CICS Problem
backout failure messages for further information. Determination Guide for guidance on how to proceed.
Module: DFHFCEI, DFHDMPCA Module: DFHICP
AGMA AICF
Explanation: An attempt to initiate the good morning Explanation: An incorrect response was returned from a
message transaction was made without specifying a termid for transaction manager (TM) domain request.
it to be displayed. System action: The task is abnormally terminated with a
System action: The transaction is abnormally terminated with CICS transaction dump.
a CICS transaction dump. User response: You need further assistance from IBM to
User response: Use the dump to determine how the attempt resolve this problem. See Part 4 of the CICS Problem
to start the transaction was made. Ensure that no EXEC CICS Determination Guide for guidance on how to proceed.
STARTs are made for the good morning message transaction Module: DFHICP
where no termid is specified.
Module: DFHGMM
AICG
Explanation: A PURGED response was returned from a
AICA dispatcher domain (DS) request, with a reason code of
Explanation: A task has been executing for longer than the TASK_CANCEL. TASK_CANCEL was returned as the
runaway time interval (defined by the ICVR system transaction had been explicitly canceled.
initialization parameter) without giving up control. The System action: The task is abnormally terminated with a
runaway task condition indicates a possible loop in the CICS transaction dump.
application. User response: Notify your system programmer to determine
System action: The task is terminated with an AICA why the task has been purged.
transaction dump. Module: DFHICP
User response: See the CICS Problem Determination Guide for
guidance on dealing with loops.
Module: DFHSRP AICH
Explanation: The task was purged before a request to the
storage manager (SM) domain was able to complete
AICB successfully. The domain that first detected the purged
Explanation: A RETRIEVE WAIT request has been reissued condition will have provided an exception trace.
in system shutdown. System action: The task is abnormally terminated with a
CICS transaction dump. User response: Investigate why the task was purged. This is
User response: None either as a result of a purge from the master terminal operator
Module: DFHICP via the CEMT transaction, or by the task being timed out after
waiting for longer than the DTIMOUT (deadlock timeout)

AICJ • AISC

AICO
Explanation: An unexpected EXCEPTION response was
If the task was timed out automatically as a result of the 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
short-on-storage situations. Another possibility is to increase
has failed.
the value of the DTIMOUT option for the transaction.
Module: DFHICP, DFHEIIC The userid for the intended user of the transaction may not be
correctly defined.
AICJ a CICS transaction dump.
Explanation: An error (INVALID, DISASTER or unexpected User response: Determine why the intended user of the
EXCEPTION response) has occurred on a call to the storage transaction is not correctly defined.
error will have provided an exception trace, a console message Examine messages produced for the CICS job by the external
and, possibly, a system dump (depending on the options security manager (ESM). This may require the assistance of a
specified in the dump table). security administrator.
CICS transaction dump. It may be necessary to examine the transaction dump to
User response: See the related message produced by the determine why the external security manager has informed
domain that detected the original error. CICS that the user is not correctly defined.
Module: DFHICP When the user has been correctly defined, consider rerunning
the transaction.
Module: DFHICXM
AICK
Explanation: Module DFHEIIC has issued a resource level
security check (RSLC) request to module DFHXSRC and AICR
received a response other than OK or EXCEPTION. Explanation: A DFHTC write request has failed for IRC. The
System action: The transaction is abnormally terminated with return codes within TCATPAPR and TCTEIRET should be
a transaction dump. examined to determine the cause of failure.
User response: Examine the trace to find the exception trace System action: The CSNC transaction is abnormally
entry created by DFHXSRC at the time of the error. Use this terminated with a CICS transaction dump.
trace entry to determine the cause of the return code from User response: You need further assistance from IBM to
DFHXSRC. resolve this problem. See Part 4 of the CICS Problem
Module: DFHEIIC Determination Guide for guidance on how to proceed.
Module: DFHCRR
AICL
Explanation: DFHEIIC detected an invalid function code in AISA
the command level parameter list. This is caused either by a Explanation: The mirror transaction (CSMI) has been
storage overwrite or a CICS internal logic error. attached from some facility other than a terminal. This is not
System action: The transaction is abnormally terminated with permitted.
a CICS transaction dump. System action: The task is abnormally terminated with a
User response: If this problem is reproducible, a level 1 trace CICS transaction dump.
of the IC and EI components would aid problem User response: Using the dump, check the field TCAFCAAA
determination. Look in the program storage section of the to identify the invalid attach.
transaction dump and compare argument 0, the exec interface Module: DFHMIRS
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 AISB
program may have occurred. You need further assistance from Explanation: The mirror transaction (CSMI) has detected
IBM to resolve this problem. See Part 4 of the CICS Problem errors in the data passed to it from the attaching transaction.
Determination Guide for guidance on how to proceed. System action: The task is abnormally terminated with a
Module: DFHEIIC CICS transaction dump.
User response: The invalid input will be visible in the
transaction dump. This error is likely to be caused by some
AICN mismatch between the two systems. A typical example might
Explanation: An incorrect response has been returned from a be a DL/I request received on a system generated without
user domain (US) request. DL/I.
System action: The task is abnormally terminated with a Module: DFHMIRS
resolve this problem. See Part 4 of the CICS Problem AISC
Determination Guide for guidance on how to proceed. Explanation: The mirror transaction (CSMI) has not received
Module: DFHICP a TIOA from the terminal.
User response: Use the trace in the dump and the dumped

AISD • AISP
TCTTE to analyze the problem further. information to further analyze the problem.
Module: DFHMIRS Module: DFHISP
AISD AISJ
Explanation: The mirror program executed the request and Explanation: The IRC control task CSNC has abended
received a nonzero return code as a result. The data flow because the attempt to LINK to DFHCRR failed.
control state of the intersystem link being used was such that System action: CSNC is abnormally terminated with a
this information could not be returned normally. system dump. All tasks using MRO links to other systems are
System action: The mirror task is abnormally terminated abnormally terminated. All tasks in other CICS regions
with a CICS transaction dump. (including shared database batch regions) that are currently
User response: The transaction dump provided will provide communicating with this system are also abnormally
information required to analyze the source of the nonzero terminated.
return code at its point of origin. User response: Ensure that program DFHCRR is available.
Module: DFHMIRS Module: DFHCRNP
AISE AISK
Explanation: The mirror program issued a DL/I request, but Explanation: The user transaction has been abnormally
DL/I support is not generated terminated during the execution of a function shipping request
System action: The mirror task is abnormally terminated on an APPC session. This has happened because the mirror
with a CICS transaction dump. transaction on the remote system has abnormally terminated,
User response: The transaction dump provides the and caused a request for syncpoint rollback to be sent across
information required the session. CICS abends the user transaction in these
Module: DFHMIRS circumstances so that function shipping remains transparent to
the transaction.
AISF CICS transaction dump.
Explanation: The CICS mirror program DFHMIRS has been User response: Check the log on the mirror system to
attached in an unsupported manner. The principal facility for determine the reason for the original abend of the mirror task.
the mirror transaction is defined as APPC, however the Module: DFHISP
conversation is unmapped.
System action: CICS abnormally terminates the transaction
with a transaction dump. AISL
User response: There is a problem with the system that Explanation: The LU services manager transaction has been
caused the mirror transaction to be attached. You need further started directly from a user terminal. This is not permitted.
assistance from IBM to resolve this problem. See Part 4 of the System action: The task is abnormally terminated with a
CICS Problem Determination Guide for guidance on how to transaction dump.
proceed. User response: None. The LU services manager transaction
Module: DFHMIRS must be started internally by CICS.
Module: DFHLUP, DFHCLS3, DFHCLS4, DFHZLS1
AISG
Explanation: The mirror program executed the request and AISM
produced the reply. This would not be sent because the data Explanation: A transaction has issued a macro-level request
flow control state of the intersystem link was such that this against a table entry with TYPE=REMOTE. Requests for
could not be done. operations on a remote system are valid only when issued at
System action: The task (CSMI) is abnormally terminated the command level.
with a CICS transaction dump. System action: The transaction is abnormally terminated with
User response: Use the transaction dump provided to a CICS transaction dump.
analyze the problem. User response: The transaction should be rewritten using the
Module: DFHMIRS command level or the CALL level, or should be run using the
table for which it was originally designed.
Module: DFHTDP
AISH
Explanation: The new connection task, CSNC, has been
invoked in an incorrect manner (for example, from a terminal AISP
or via an EXEC CICS START request). Explanation: A mirror transaction (transaction identifiers
System action: The task is abnormally terminated with a CSM1, CSM2, CSM3, CSM5, or CSMI) has been invoked with
CICS transaction dump. an invalid principal facility. The mirror transaction executes
User response: None. with an MRO session, an LU6.1 session or an APPC session as
Module: DFHCRNP its principal facility.
AISI User response: Do not attempt to invoke the mirror
Explanation: A function shipping request was passed by transaction by entering the transaction identifier at a terminal.
DFHEIP to DFHISP. This was found to be invalid by the Module: DFHMIRS
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

AISQ • AISX

AISQ
Explanation: An EXEC CICS command has been issued
against a CPI Communications session. A CPI via the CEMT transaction, or by the task being timed out after
Communications session is one that has a waiting for longer than the DTIMOUT (deadlock timeout)
CPI-Communications Control Block (CPC) associated with it. value specified for the transaction.
System action: The mirror task is abnormally terminated If the master terminal operator purged the task, this may have
with a CICS transaction dump. been in an attempt to clear the system which appeared to be
User response: Do not mix EXEC commands with CPI
Communications calls on the same end of a conversation.
Module: DFHMIRS If the task was timed out automatically as a result of the
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 short-on-storage situations. Another possibility is to increase
insufficient to access the transaction on the connected APPC the value of the DTIMOUT option for the transaction.
system. Depending on the nature of the request and the way Module: DFHMIRS
security has been set up, the requestor with an insufficient
access level can be the local CICS system, the requesting
AISW
transaction, or the terminal user.
Explanation: An INVALID, DISASTER, or EXCEPTION
condition has occurred on a call to the storage manager
Note: DTP programs do not abend with code AISS after a domain (SM) to GETMAIN or FREEMAIN a CRB control
security failure in the remote region. block.
a transaction dump. The domain that detected the original error provides an
User response: First, verify that the access was correctly exception trace, a console message and, possibly, a system
denied. Then, if required, change the access level. dump.
Module: DFHZARM System action: The task is abnormally terminated with a
transaction dump.
AIST detected the original error.
Explanation: An unexpected return code has been returned Module: DFHCRSP
after a DFHTC TYPE=LOCATE command.
system dump. All tasks using MRO links to other systems are AISX
abnormally terminated. All tasks in other CICS regions Explanation: A PURGED condition has occurred on a call to
(including shared database batch regions) that are currently the storage manager domain (SM) to GETMAIN or
communicating with this system are also abended. FREEMAIN a CRB control block.
User response: The trace in the system dump should be used
The domain that detected the original error provides an
to analyze the problem further.
exception trace, a console message and, possibly, a system
Module: DFHCRNP
dump.
AISU transaction dump.
Explanation: An INVALID, DISASTER, or EXCEPTION User response: Investigate why the task was purged. It was
condition has occurred on a call to the storage manager purged either as a result of a purge from the master terminal
domain (SM) to FREEMAIN a FCENT control block. operator via the CEMT transaction, or by the task being timed
out after waiting for longer than the DTIMOUT (deadlock
The domain that detected the original error provides an timeout) value specified for the transaction.
dump. If the master terminal operator purged the task, this may have
System action: The task is abnormally terminated with a been in an attempt to clear the system which appeared to be
transaction dump. deadlocked for some reason.
Module: DFHMIRS
AISV increased, reduce the number of tasks in the system to avoid
Explanation: A PURGED condition has occurred on a call to short-on-storage situations. Another possibility is to increase
the storage manager domain (SM) to FREEMAIN a FCENT the value of the DTIMOUT option for the transaction.
control block. Module: DFHCRSP

dump.
transaction dump.

AISY • AIS7
All tasks in other CICS regions (including shared database

AISY
batch regions) that are currently communicating with this
Explanation: The LU services manager transaction has been
system are also abended.
started, but invalid parameters have been detected.
User response: Repair or enable the system clock.
Module: DFHCRNP
transaction dump.
User response: See message DFHZC4921 for further
guidance. AIS4
Module: DFHLUP Explanation: An unexpected return code has been returned
after a DFHMROQM FUNC=ENQUEUE command. This
command was issued when enqueuing work to the IRC
AISZ
'delayed work' queue.
Explanation: DFHMXP has received an unexpected reply
when committing START PROTECT NOCHECK requests sent
system dump. All tasks using MRO links to other systems are
on a LUTYPE6.2 synclevel 1 conversation.
User response: Determine what happened to transaction All tasks in other CICS regions (including shared database
CVMI in the partner system. If the START PROTECT batch regions) that are currently communicating with this
NOCHECK requests had been committed, no further action is system are also abended.
necessary. If they had not been committed, user-defined action User response: You need further assistance from IBM to
is required to recover from the error. resolve this problem. See Part 4 of the CICS Problem
Module: DFHMXP Determination Guide for guidance on how to proceed.
Module: DFHCRNP
AIS1
Explanation: An unexpected return code has been returned AIS5
after a DFHMROQM FUNC=ENQ command was issued. Explanation: An unexpected return code has been returned
after a DFHMROQM FUNC=ENQUEUE command was
This command was issued when enqueuing work for the IRC
issued.
control task (CSNC) during IRC initialization.
System action: If IRC is being initialized during CICS This command was issued when enqueuing work to the IRC
initialization (as a result of IRCSTRT being specified in the 'immediate work' queue.
DFHSIT or override parameters), then CICS is abnormally System action: CSNC is abnormally terminated with a
terminated. system dump. All tasks using MRO links to other systems are
If IRC is being initialized during the execution of a CEMT SET
IRC OPEN command, then the CEMT transaction is All tasks in other CICS regions (including shared database
abnormally terminated. batch regions) that are currently communicating with this
User response: You need further assistance from IBM to system are also abended.
resolve this problem. See Part 4 of the CICS Problem User response: You need further assistance from IBM to
Determination Guide for guidance on how to proceed. resolve this problem. See Part 4 of the CICS Problem
Module: DFHCRSP Determination Guide for guidance on how to proceed.
Module: DFHCRNP
AIS2
Explanation: An unexpected return code has been returned AIS6
after a DFHMROQM FUNC=WAIT_Q command was issued. Explanation: An INVALID, DISASTER or EXCEPTION
condition has occurred on a call to the storage manager
This command was issued when waiting for more IRC work
domain (SM) to GETMAIN or FREEMAIN a file control read
to process.
set buffer.
system dump. All tasks using MRO links to other systems are The domain that detected the original error provides an
abnormally terminated. exception trace, a console message and, possibly, a system
dump.
All tasks in other CICS regions (including shared database
batch regions) that are currently communicating with this
transaction dump.
system are also abended.
Module: DFHMIRS
Module: DFHCRNP
AIS7
Explanation: A PURGED condition has occurred on a call to
AIS3
the storage manager domain (SM) to FREEMAIN a file control
Explanation: An attempt to issue a STCK (Store Clock)
read set buffer.
instruction failed.
System action: CSNC is abnormally terminated with a The domain that detected the original error provides an
system dump. exception trace, a console message and, possibly, a system
dump.
All tasks using MRO links to other systems are abnormally
terminated.

AIS8 • AJCC
System action: The task is abnormally terminated with a Analysis: If an I/O error is detected on a journal for which
transaction dump. CRUCIAL has been specified in the JCT, message DFHJC4518
User response: Investigate the reason why the task was is issued and you are advised to take a system dump and to
purged. It was purged either by the master terminal operator , terminate CICS. If the journal was specified as being
or as a result of a deadlock timeout. NONCRUCIAL, the journaling task abnormally terminates
Module: DFHMIRS with the AJCA abend code. There is one journaling task for
each journal; each has a task identification of Jnn.
Module: DFHJCIOE
AIS8
module DFHMIRS. AJCB
System action: The transaction is abnormally terminated with Explanation: An error has occurred while switching data sets
a CICS transaction dump. on a NONCRUCIAL journal. The journal's journaling
User response: You need further assistance from IBM to transaction is abnormally terminated with the AJCB abend
resolve this problem. See Part 4 of the CICS Problem code, and message DFHJC4512 is sent to the console and to
Determination Guide for guidance on how to proceed. the CSMT transient data destination.
Module: DFHMIRS
If the error is detected on a journal for which CRUCIAL has
been specified in the JCT (JCTJT has bit JCTJTC (X'02' set),
AIS9 CICS is terminated with a system dump.
Explanation: The mirror program has detected that a DPL System action: If the journal is specified with the CRUCIAL
server program has returned in an invalid state following the option in its journal control table (JCT) entry, CICS execution
completion of the LINK command. The server program or a is terminated with a system dump. Otherwise, execution
program it linked to has initiated a synclevel 2 conversation continues and the journal is unavailable for the duration of the
with another program which in turn has issued a syncpoint. run; the journaling transaction is abnormally terminated with
The server program has not responded to the syncpoint abend code AJCB and a CICS transaction dump.
request which is still outstanding when control returns to the User response: Restart CICS if it has terminated. Inform the
mirror program. person(s) responsible for debugging system errors of this type.
The condition may be due either to an operating system or
The mirror program only issues this abend code if the LINK device open/close failure, or to a CICS error.
request did not specify SYNCONRETURN.
System action: The task is abnormally terminated with a The transaction dump may not contain all the information
transaction dump. necessary to determine the cause of the error. If it does not,
User response: Correct the design of the DTP application or you should take a system dump after message DFHJC4512 is
applications initiated by the server program. If the received.
SYNCONRETURN option is not specified on the LINK
The AJCB transaction dump contains the address of the JCT
request, only the client program should initiate the syncpoint.
entry; this is pointed to by register 11.
If it is necessary to issue syncpoint requests from the DTP
Problem determination: There is one journaling task for each
applications, consider using the SYNCONRETURN option on
journal. Each has a task identification of Jnn.
the LINK request. See the CICS Intercommunication Guide for
further details of the LINK command and its options. The journal status is found in field JCTJS. Bit JCTJSNO (X'20')
Module: DFHMIRS means the journal is not open.
The journaling subtask is alive if the first byte of the field
AJCA JCOCAECB does not have the POST bit set.
Explanation: An unrecoverable I/O error has occurred on
output to a journal data set. The journal's journaling The JCOCAECB field is the first word in the journal control
transaction is abnormally terminated with the abend code open/close list, DFHJCOCL. This storage is addressed by CSA
AJCA, and messages DFHJC4513 and DFHJC4517 are sent to field CSAJCOCL.
the console and to the transient data destination CSMT. Analysis: An AJCB abend may be issued by DFHJCEOV for
System action: See message DFHJC4513, message DFHJC4517 two reasons; the program may fail to close the current data
and message DFHJC4518. set, or it may fail to open the next data set. The trace table
User response: If the affected journal is CRUCIAL, you may will indicate which situation has occurred.
want to shut down CICS for data integrity reasons (see
message DFHJC4518). DFHJCC or DFHJCO may detect that DFHJCOCP is no longer
running if that subtask has terminated prematurely.
Inform those responsible for the integrity of journal data sets.
If the error persists, it may be necessary to allocate an After DFHJCOCP is invoked, errors occur because the OPEN
alternative device or extent. or CLOSE macro issued by DFHJCOCP fails.
Module: DFHJCEOV
The transaction dump probably does not contain all the
information necessary to determine the cause of the I/O error.
Take a system dump by placing an entry for AJCA in the AJCC
transaction dumpcode table, using the system dump option, Explanation: The transaction identifier CSJC (which is
and recreating the error. reserved for use by CICS) has been entered at a terminal.
Problem determination: An I/O error is detected by one of System action: The transaction is abnormally terminated with
the journaling modules. a CICS transaction dump.
User response: None. Do not enter transaction identifier
The JCTTE for the affected journal will have bit JCTJSIOE CSJC at a terminal.
(X'01') in field JCTJS on.

AJCD • AJCL
Module: DFHJCBSP
AJCH
Explanation: The DFHPC link for the journal exit has failed.
AJCD Either message DFHJC4587 or message DFHJC4589 is
Explanation: An error (INVALID, DISASTER, or unexpected produced in response to the detection of this failure.
EXCEPTION response) has occurred on a call to the storage System action: The task which issued the request is abended
manager (SM) domain. The domain that detected the original with a CICS transaction dump.
error provides an exception trace, a console message, and User response: Use the transaction dump and follow the
possibly a system dump (depending on the options in the guidance in message DFHJC4587 or message DFHJC4589 to
dump table). solve the problem.
System action: The task is abnormally terminated with a Module: DFHJCC, DFHJCO
AJCI
Explanation: During initialization, a request was made to the
Module: DFHJCKOJ, DFHJCP, DFHJCPDY
SMAD domain with function ADD_SUBPOOL to create a
system-wide subpool for use by forward recovery. This has
AJCE returned a response of INSUFFICIENT STORAGE.
Explanation: The task was purged before a GETMAIN System action: It is unlikely that initialization will complete
request to the storage manager (SM) domain was able to due to critical storage problems. Other storage-related
complete successfully. The domain that first detected the symptoms may also occur. The task is abnormally terminated
purged condition provides an exception trace. with a CICS transaction dump.
System action: The task is abnormally terminated with a User response: Try increasing the overall size limits of the
CICS transaction dump. DSAs or EDSAs. See the CICS System Definition Guide or the
User response: Investigate why the task was purged. It was CICS Performance Guide for more information on CICS storage.
purged either as a result of a purge from the master terminal Module: DFHJCRP
operator via the CEMT transaction, or by the task being timed
AJCJ
timeout) value specified for the transaction.
Explanation: During initialization, a request was made to the
If the master terminal operator purged the task, this may have SMAD domain with function ADD_SUBPOOL to create a
been in an attempt to clear the system which appeared to be system-wide subpool for use by forward recovery. This has
deadlocked for some reason. returned an unexpected response. The domain that detected
the original error provides an exception trace, a console
If the task was timed out automatically as a result of the message, and possibly a system dump (depending on the
DTIMOUT value being exceeded, this may be due to options in the dump table).
insufficient main storage being available for the number of System action: It is unlikely that initialization will complete
tasks in the system. If the amount of main storage cannot be due to internal problems with the storage manager. The task is
increased, reduce the number of tasks in the system to avoid abnormally terminated with a CICS transaction dump.
short-on-storage situations. Another possibility is to increase User response: See the related message from the domain that
the value of the DTIMOUT option for the transaction. detected the original error.
Module: DFHJCP, DFHJCPDY Module: DFHJCRP
AJCF AJCK
Explanation: An error (INVALID, DISASTER, or unexpected Explanation: DFHJCP has issued a GETMAIN request to the
EXCEPTION response) has occurred on a call to the dispatcher SMGF domain in order to create a new journal thread control
(DS) domain. The domain that detected the original error block but an unexpected response has been received from the
provides an exception trace, a console message, and possibly a request. The domain that detected the original error provides
system dump (depending on the options in the dump table). an exception trace, a console message, and possibly a system
System action: The task is abnormally terminated with a dump (depending on the options in the dump table).
User response: See the related message from the domain that CICS transaction dump.
detected the original error. User response: See related message from the domain that
Module: DFHJCBSP, DFHJCC, DFHJCEOV, DFHJCI, detected the original error.
DFHJCKOJ, DFHJCO, DFHJCP, DFHJCSDJ Module: DFHJCP
AJCG AJCL
Explanation: The task was purged before a WAIT request to Explanation: DFHAKP has issued a GETMAIN request to the
the dispatcher (DS) domain was able to complete successfully. SMGF domain in order to create a new journal minimum list
The domain that first detected the purged condition provides entry for its own internal use. However, an unexpected
an exception trace. response has been received from the request. The domain that
System action: The task is abnormally terminated with a detected the original error provides an exception trace, a
CICS transaction dump. console message, and possibly a system dump (depending on
User response: The task must have been purged as the result the options in the dump table).
of a forced cancel (FORCEPURGE on CEMT SET TASK, CEMT System action: The task is abnormally terminated with a
SET TERMINAL, or CEMT SET CONNECTION). Determine CICS transaction dump. CICS is then terminated abnormally
why this was done. with a dump, with an VSE user abend of 0161.
Module: DFHJCC, DFHJCEOV, DFHJCI, DFHJCKOJ, User response: See the related message from the domain that
DFHJCO, DFHJCP, DFHJCSDJ detected the original error.
Module: DFHAKP

AJCM • AKCC
AJCM AJCR
Explanation: At the commencement of processing the journal Explanation: A task abends with this code if it attempts to
minimum list entries, DFHAKP has attempted to locate the access a CRUCIAL journal that is not available.
first JCT entry in the journal control table, but has failed to do System action: The transaction is abnormally terminated.
so. This is probably due to an internal error. User response: See transaction abend AJCA, and messages
System action: The task is abnormally terminated with a DFHJC4513, DFHJC4517, and DFHJC4518.
CICS transaction dump. CICS is then terminated abnormally Module: DFHJCP
with a dump, with an VSE user abend of 0161.
resolve this problem. See Part 4 of the CICS Problem AKCA
Determination Guide for guidance on how to proceed. Explanation: The CICS transaction manager (DFHKCP)
Module: DFHAKP component has received an invalid request code.
System action: CICS terminates the task with a transaction
dump.
AJCN User response: Use the dump to determine the reason for the
Explanation: DFHAKP has issued a GETMAIN request to the failure. The invalid request code is in field TCATCTR of the
SMGF domain in order to create a new keypoint directory failing task's task control area (TCA). The caller of DFHXCPC
entry. However, this has resulted in an unexpected response is most likely to be in error.
from the domain. The domain that detected the original error Module: DFHXCPC
provides an exception trace, a console message, and possibly a
system dump (depending on the options in the dump table).
System action: The task is abnormally terminated with a AKCB
CICS transaction dump. CICS is then terminated abnormally Explanation: The CICS transaction manager restart task could
with a dump, with an VSE user abend of 0161. not complete because a necessary step failed. The task has
User response: See related message from the domain that done some essential recovery operations and abnormally
detected the original error. terminated itself with code AKCB.
Module: DFHAKP System action: CICS writes a transaction dump for the
transaction manager restart task.
AJCO CICS sends three messages to the console, one to identify the
Explanation: While processing existing keypoint directory error detected by the transaction manager restart task, one to
entries, DFHAKP has issued a request to the SMGF domain to say that the task has failed, and one that gives you the option
FREEMAIN a KPDE. However, this request has returned an of canceling CICS or letting it continue. Depending on the
unexpected response from the domain call. The domain that nature of the original error, you may see messages from some
detected the original error provides an exception trace, a other system component (for example, an access method).
console message, and possibly a system dump (depending on User response: Use the messages and dumps to find out the
the options in the dump table). cause of the failure.
System action: The task is abnormally terminated with a Module: DFHKCRP
CICS transaction dump. CICS is then terminated abnormally
with a dump, with an VSE user abend of 0161. AKCC
User response: See related message from the domain that Explanation: The CICS transaction manager has abended the
detected the original error. transaction because the purge threshold of its TRANCLASS
Module: DFHAKP has been reached. This is specified by the PURGETHRESH
parameter on CEDA DEFINE TRANCLASS. See the CICS
AJCP Resource Definition Guide manual for more details of this
Explanation: An abend has occurred in the journal exit parameter.
program, DFHXJCO, after a link has been executed from System action: The transaction is abended and messages
DFHJCO. DFHAC2036 and DFHAC2004 are issued. The transaction
System action: The task which issued the request is abended dump is suppressed for this abend code.
and a transaction dump is produced. Message DFHJC4588 is User response: Resubmit the transaction. The cause of the
produced in response to the detection of this abend. abend may be a temporary stress condition in the system.
User response: Use the transaction dump and follow the If the problem persists, determine why the TRANCLASS
guidance in message DFHJC4588 to solve the problem. purge threshold has been reached. Ensure that
Module: DFHJCO 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
AJCQ
been reached are immediately queued subject to the
Explanation: An abend has occurred in the journal exit
PURGETHRESH limit.
program, DFHXJCC, after a link has been executed from
DFHJCC. If PURGETHRESH and MAXACTIVE are set correctly, look for
System action: The task which issued the request is abended a more general problem which has caused a decrease in the
with a CICS transaction dump. Message DFHJC4588 is capacity of the system to execute transactions in the
produced. TRANCLASS. The decrease might, for example, be caused by
User response: Use the dump and the guidance in message a connected CICS region which processes requests for
DFHJC4588 to solve this problem. transactions in the TRANCLASS, if this connected region has
Module: DFHJCC. slowed down.
Examine all resources (files, links, storage, and so on) used by
the transactions in the TRANCLASS which is reaching the

AKCE • AKC2
purge threshold and determine why the capacity of the system transaction dump code AKCS indicates that one should be
is reduced. taken.
Module: DFHXMAT, DFHXMCL User response: The transaction should be reexecuted, and the
situation causing the SUSPEND to occur may clear itself.
AKCE The AKCS abend is to be expected occasionally, unless
Explanation: While CICS transaction manager was recording DTIMOUT is set to zero. No special action is necessary.
changes to a transaction or profile definition, a write to the Module: DFHXCP, DFHXCPC
system log failed.
System action: CICS terminates the transaction with a
transaction dump. AKCT
User response: Use the dumps to find out why the write to Explanation: A terminal read-time-out condition has been
the log failed. detected. The transaction has been waiting for a terminal input
Module: DFHKCQ message for an interval longer than specified in the RTIMOUT
value for that transaction.
AKCF If an EXEC CICS HANDLE ABEND has been issued for this
Explanation: While CICS transaction manager was recording task, the read that was timed-out is still outstanding. To cancel
changes to a profile definition, a write to the catalog failed. this read you should issue an EXEC CICS ABEND at the end
System action: CICS terminates the transaction with a of the user exit routine so that CICS can clean up the
transaction dump. terminal's TCTTE.
User response: Use the dumps to find out why the write to System action: The transaction is abnormally terminated. A
the catalog failed. transaction dump is not provided.
Module: DFHKCQ 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
AKCR within the specified time.
Explanation: Transaction manager has received an invalid Module: DFHXCP
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 AKCV
manager request code in the fifth byte of the first section of Explanation: A bad return code was passed as a result of the
the trace. resume of a task suspended by ICP.
System action: The transaction is abnormally terminated with System action: The transaction is terminated with a dump.
a CICS transaction dump. User response: Check the response from the resume in the
User response: Determine the cause of the invalid request trace to determine the cause of the error.
code and correct the problem. Module: DFHALP
Module: DFHXCP, DFHXCPC
AKC0
AKCS Explanation: An attempt has been made to run the CICS
Explanation: A deadlock timeout condition has been internal task CSSY as a user transaction.
detected. This condition may occur within a transaction that System action: CICS terminates the task with a transaction
specifies DTIMOUT to be nonzero on its installed transaction dump.
definition. Deadlock timeout occurs when a transaction was User response: Investigate why the attempt was made to run
been waiting or has been suspended for longer than the time CSSY as a user transaction.
specified in DTIMOUT. Module: DFHAPATT
The abend may be driven by a variety of internal CICS events,

for example: AKC1
v A short on storage condition Explanation: A DFHKC WAIT request was issued when the
v A temporary storage shortage ECB was already marked as waiting.
v ENQUEUE System action: There is a probable user error. The transaction
v An ALLOCATE request is abnormally terminated.
v A RETRIEVE WAIT request. User response: Correct the program that issued the request.
Module: DFHXCP
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 AKC2
CICS is executing. Explanation: A bad response has been received from a
dispatcher (DS) domain call.
Analysis: The transaction receiving the AKCS abend must a transaction dump and a trace entry.
have been suspended or must be waiting for a reason such as User response: Examine the trace entry for further
a short on storage, enqueued on a lock, a short on temporary information.
storage, a suspend after RETRIEVE WAIT, a suspend after Module: DFHXCP, DFHXCPC
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.
System action: The transaction is abnormally terminated. A
dump is not provided unless the dump table entry for

AKC3 • AKEF
AKC3 AKEA
Explanation: The task has been purged, probably due to Explanation: A program check has been detected by the
operator action such as a CEMT TASK PURGE command. kernel (KE) domain.
System action: The transaction is abnormally terminated with System action: If an application is in control, the ASRA
a transaction dump. abend is presented to the application. Otherwise, the
User response: Use the transaction dump to determine why functional recovery routine of the CICS module in control at
the task was purged. In particular, if the purge was operator the time is given control. This recovery routine produces
initiated, the dump should be useful in determining why this suitable diagnostics and may terminate CICS.
task needed to be explicitly purged. User response: Look at the kernel domain section of the
Module: DFHXCP, DFHXCPC, DFHXMAT, DFHXMCL, system dump to determine where the program check has
DFHXMIQ, DFHXMTA occurred.
Module: DFHKESTX
AKC4
Explanation: An attempt to obtain and initialize storage for AKEB
the transaction being attached failed. Explanation: An operating system abend has been detected
System action: A storage GETMAIN failure other than by the kernel (KE) domain.
insufficient storage occurred on transaction attach. The System action: If an application is in control, the ASRB
transaction is abnormally terminated with abend code AKC4. abend is presented to the application. Otherwise, the
User response: Examine the trace entry for further functional recovery routine of the CICS module in control at
information. the time is given control. This recovery routine produces
Module: DFHXCPC suitable diagnostics and may terminate CICS.
User response: Check the console for any VSE messages that
may have caused this abend.
AKC5
Explanation: An invalid response has been received from a Look at the kernel domain section of the system dump to
storage manager (SM) domain call. determine where the abend has occurred.
System action: The transaction is abnormally terminated. Module: DFHKESTX
User response: Examine the trace entry for further
information. Increasing the EDSA storage limit on the CICS
bring-up may help. AKEC
Module: DFHXCPC Explanation: The kernel (KE) domain has detected runaway.
System action: If an application is in control, the AICA abend
is presented to the application. Otherwise, the functional
AKC6 recovery routine of the CICS module in control at the time is
Explanation: DFHKC RESUME should always be preceded given control. This recovery routine produces suitable
by DFHKC SUSPEND. If this protocol is violated then the diagnostics and may terminate CICS.
transaction is abnormally terminated with abend code AKC6. User response: Look at the kernel domain section of the
System action: Transaction is abnormally terminated with system dump to determine where the runaway has occurred.
abend code AKC6. Module: DFHKESTX, DFHKERRU
User response: Examine the trace entry for further
information.
Module: DFHXCP AKED
Explanation: The kernel (KE) domain has been requested to
initiate abend processing as a result of a deferred abend
AKC7 request.
Explanation: A bad response has been received from an System action: Abend processing starts for the task that is
XMSU call during the ATTACH of a transaction. subject to the deferred abend request.
System action: The transaction is abnormally terminated with User response: The task is not abended with AKED but by
abend code AKC7. an abend code specified by the requestor of the deferred
User response: Examine the trace entry for further abend. See the description of this abend for further guidance.
information. Module: DFHKEEDA
Module: DFHXCPC
AKEF
AKC8 Explanation: The kernel (KE) domain has detected an error
Explanation: A bad response has been received from a call to while processing a domain call. The error may have been
the kernel (KE) domain during the processing of a task purge caused by a domain gate that was not yet active during
request. initialization
System action: The transaction is abended with a transaction System action: If an application is in control, the transaction
dump. terminates with a system dump. Otherwise, the functional
User response: Examine the dump and any exception trace recovery routine of the CICS module in control at the time is
entries for further information. given control. This recovery routine produces suitable
Module: DFHXCP diagnostics and may 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

AKEG • AMNZ
active. Check that the caller has NOT specified Manager domain where the original error was detected.
KERNERROR(YES). Module: DFHAPLI
Module: DFHKERKE
ALIF
AKEG Explanation: CICS has issued a GETMAIN request during
Explanation: The kernel (KE) domain issued an VSE the initialization phase for an LE for z/VSE application
GETMAIN for kernel stack storage, but the GETMAIN request program in order to obtain thread storage. However
failed. insufficient storage was available to satisfy the request.
System action: If an application is in control, the transaction System action: CICS abnormally terminates the task. CICS
terminates with a system dump. Otherwise, the functional processing continues.
recovery routine of the CICS module in control at the time is User response: See the related message from the Storage
given control. This recovery routine produces suitable Manager domain where the original error was detected.
diagnostics and may terminate CICS. Module: DFHAPLI
User response: Look at the kernel domain section of the
system dump to determine why sufficient storage was not
available. ALIG
Explanation: CICS has been unable to determine the
Check that the ALLOC statement for the CICS partition language of the user application program about to be
specifies a large enough size. For information about the executed. Either the program was compiled against an old
ALLOC statement, refer to the z/VSE System Control Statements level of compiler that is no longer supported by CICS, or the
manual. language of the program is not supported by CICS.
Module: DFHKESGM System action: CICS abnormally terminates the task and
disables the program. CICS processing continues.
User response: Ensure that the program to be run is written
AKEZ in one of the languages and compiled against a level of
Explanation: A user attach has failed because there are compiler supported by CICS. See the CICS Application
insufficient kernel tasks available. This indicates an internal Programming Guide for details of the languages and compilers
logic error. currently supported.
System action: Message DFHKE0001 is issued and a system Module: DFHAPLI
dump is taken. The attach of the user transaction fails.
resolve this problem. See Part 4 of the CICS Problem AMNA
Determination Guide for guidance on how to proceed. Explanation: An exception response has been received from
Module: DFHKETA 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
ALIA contains an invalid address.
Explanation: CICS has issued a GETMAIN request during System action: The transaction is abnormally terminated with
the initialization phase for an DOS/VS COBOL application a CICS transaction dump.
program in order to get run time storage for the task global User response: Use the transaction dump to determine why
table and working storage areas. However insufficient storage the DATA1 value passed to the monitoring (MN) domain was
was available to satisfy the request. invalid.
System action: CICS abnormally terminates the task. CICS Module: DFHCMP
User response: See the related message from the Storage
Manager domain where the original error was detected. AMNB
Module: DFHAPLI 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
ALIC produced when the 4-byte DATA2 field in the user parameter
Explanation: CICS has issued a GETMAIN request during contains invalid data.
the initialization phase for an LE for z/VSE application System action: The transaction is abnormally terminated with
program in order to obtain run time execution storage above a CICS transaction dump.
the 31-bit line. However insufficient storage was available to User response: Use the transaction dump to determine why
satisfy the request. the DATA2 value passed to the monitoring (MN) domain was
System action: CICS abnormally terminates the task. CICS invalid.
processing continues. Module: DFHCMP
Manager domain where the original error was detected.
Module: DFHAPLI AMNZ
Explanation: An unexpected error response has been received
from the monitoring (MN) domain while processing a user
ALID event monitoring point (EMP) request.
Explanation: CICS has issued a GETMAIN request during System action: The transaction is abnormally terminated with
the initialization phase for an LE for z/VSE application a CICS transaction dump.
program in order to obtain run time execution storage below User response: This indicates a possible error in CICS code.
the 31-bit line. However insufficient storage was available to An earlier CICS message is issued from the monitoring
satisfy the request. domain. Follow the user response for that message.
System action: CICS abnormally terminates the task. CICS Module: DFHCMP

AMSA • APCL
AMSA APCF
Explanation: An input data stream received from a 3270 Explanation: A CICS task has invoked a program which was
begins with a set buffer address (SBA) order but is not defined as PL/I, but either:
followed by two 1-byte address fields. This is probably due to v The program was not compiled with a supported version of
a hardware error. the PL/I for VSE/ESA compiler.
System action: The transaction is abnormally terminated with v The program was compiled using the DOS PL/I compiler
a CICS transaction dump. which is no longer supported.
User response: It may be possible to bypass the problem by System action: CICS terminates the task, and disables the
entering two spaces before the data to be entered. program.
If the problem persists, you need further assistance. See Part 4 User response: Check that the program is PL/I. If the
of the CICS Problem Determination Guide for guidance on how program was compiled with the DOS PL/I compiler,
to proceed. recompile it with the PL/I for VSE/ESA compiler; you may
Module: DFHMSP need to change the source program. If the program is not
PL/I, redefine it correctly.
Module: DFHAPLI
AMSB
module DFHMSP. APCG
System action: The transaction is abnormally terminated with Explanation: The transaction was purged either by master
a CICS transaction dump. terminal actions or due to deadlock timeout actions as part of
User response: Retry the CMSG transaction, specifying a request to the loader for a usable program copy. Deadlock
operands in a different order. If this fails, keep the dump and timeout could be caused by a program whose size exceeds the
contact your IBM Support Center. available space in the DSAs or EDSAs.
Module: DFHMSP System action: CICS terminates the task with a transaction
dump.
User response: Use the dump to investigate why the
AMSC transaction was purged. This may be due to waiting for loader
Explanation: The task was purged before a GETMAIN resources or for program storage. Check the program size. It
request to the storage manager (SM) domain was able to may be necessary to increase the overall size limits of the
complete successfully. The task that first detected the purged DSAs or EDSAs.
condition will have provided an exception trace. Module: DFHACP, DFHCRNP, DFHCRSP, DFHDLRP,
System action: The task is abnormally terminated with a DFHEDFP, DFHEIP, DFHEIPSH, DFHEIQIR, DFHEIQSJ,
CICS transaction dump. DFHFCBP, DFHFEP, DFHICP, DFHJCBSP, DFHJCC,
User response: Investigate why the task was purged. This is DFHJCEOV, DFHJCO, DFHKCQ, DFHMCP, DFHMCPE,
either as a result of a purge from the master terminal operator DFHMCY, DFHMSP, DFHPCPG, DFHPHP, DFHPSIP,
via the CEMT transaction, or by the task being timed out after DFHPUP, DFHRCP, DFHRCRP, DFHRDCAL, DFHRTC,
waiting for longer than the DTIMOUT (deadlock timeout) DFHSII1, DFHSIJ1, DFHSPP, DFHSTP, DFHTACP, DFHTBSGB,
value specified for the transaction. DFHTCBP, DFHTCRP, DFHTDX, DFHTSPA, DFHTSRP,
DFHUSBP, DFHXRCP, DFHXRE, DFHXRSP, DFHZATA,
DFHZATD, DFHZCPLN, DFHZGAI, DFHZQ00, DFHZGAI,
DFHZNCA, DFHZOPA, DFHZXCU
DTIMOUT value being exceeded, this may be due to APCH
insufficient main storage being available for the number of Explanation: A request for a VS COBOL II program could
tasks in the system. If the amount of main storage cannot be not be executed because a problem has occurred during
increased, reduce the number of tasks in the system to avoid system initialization LE for z/VSE This is probably due to the
short-on-storage situations. Another possibility is to increase absence of LE for z/VSE.
the value of the DTIMOUT option for the transaction. System action: The transaction is abnormally terminated and
Module: DFHMSP the program is disabled.
User response: Redefine the program or ensure that the
correct LE for z/VSE support is present.
AMSD Module: DFHAPLI
manager (SM) domain. The domain that detected the original APCL
error provides an exception trace, a console message and, Explanation: An attempt to run the program failed because
possibly, a system dump (depending on the options specified LE for z/VSE was unable to determine its language.
in the dump table). System action: The transaction is abnormally terminated and
System action: The task is abnormally terminated with a the program is disabled.
CICS transaction dump. User response: Ensure that the program is correctly defined
User response: See the related error message produced by to CICS.
the domain that detected the original error. Module: DFHAPLI
Module: DFHMSP

APCN • APC1
DFHMELDE, DFHPCPG, DFHPHP, DFHPUP, DFHRCRP,

APCN
DFHRDCAL, DFHSII1, DFHTBSGB, DFHTSRP, DFHZCPLN,
Explanation: An attempt to release an internal CICS
program, a mapset, or a partitionset has failed because the DFHZQ00, DFHZXCU
program, mapset or partitionset has not been loaded or has
already been deleted. This is probably an internal CICS error. APCW
System action: The transaction is abnormally terminated with Explanation: The program language is defined as COBOL but
a CICS transaction dump. The name of the program for which the level of the compiler under which it was originally
the RELEASE was attempted can be found in the abend dump compiled cannot be determined.
at TCAPCPI. System action: The transaction is abnormally terminated and
User response: This is either an internal CICS error or is due the program is disabled.
to the overwriting of CICS internal control blocks. You need User response: Check that DOS/VS COBOL or LE for z/VSE
further assistance from IBM to resolve this problem. See Part 4 support is present in the system and that the required
of the CICS Problem Determination Guide for guidance on how interface module for LE for z/VSE (CEECCICS) has been
to proceed. correctly loaded during system startup.
Module: DFHAMPEN, DFHFEP, DFHMCP, DFHMCPE, Module: DFHAPLI
DFHMCY, DFHPHP, DFHRCRP, DFHTBSSP, DFHZCPLN
APCY
APCS Explanation: In an VSE/ESA environment, a CICS macro
Explanation: An attempt to run the program failed because request has been issued from a PL/I or COBOL application.
CICS was unable to make a successful connection with LE for Alternatively, it is possible that the application program has
z/VSE to determine the run-time characteristics of the been link edited without the EXEC interface module (for
program. This abend is accompanied by message DFHAP1200 example, DFHECI or DFHELII) which is used by the CICS
which gives the reason code set by LE for z/VSE indicating high-level language programming interface. See the CICS
the nature of the error. System Definition Guide for details of what has to be done to
System action: The transaction is abnormally terminated and include this module.
the program is disabled. System action: The transaction is abnormally terminated and
User response: Refer to the LE for z/VSE Debugging Guide the program is disabled.
and Runtime Messages manual for the meaning of the reason User response: Remove the macro request from the
code, and take whatever action is necessary to correct the application program.
error. Module: DFHAPLI
Module: DFHAPLI
APCZ
APCT Explanation: An attempt has been made to run either an
Explanation: One of the following has occurred: 'old-style' application program (that is, a program with a
1. The program name in the EXEC CICS HANDLE ABEND pre-release 1.6 or a DFHE program stub) or a DOS/VS
program is not usable at the time an abend occurs because: COBOL program, either having been link-edited with the SVA
v The program is not in any sublibrary of the LIBDEF attribute. These types of programs are not reentrant and
SEARCH chain for the CICS job. therefore cannot be loaded into read-only storage.
v The program is disabled. System action: The transaction is abnormally terminated.
v The program cannot be loaded. User response: Relink the program without the RENT and
2. An attempt to load a mapset or partitionset failed because REFR attributes.
although the program is defined to CICS Module: DFHAPLI
v The program is not in any sublibrary of the LIBDEF
SEARCH chain for the CICS job.
v It is disabled, or APC0
v It cannot be autoinstalled. Explanation: A serious error occurred in a call to the
3. An attempt to link to, load, or release an internal CICS program manager domain when trying to link a system
program.
program failed because:
System action: CICS terminates the task with a transaction
v The program is not in any sublibrary of the LIBDEF
dump.
SEARCH chain for the CICS job.
User response: Use the dump to investigate why the error
v The program is disabled.
occurred. Look at the trace records prior to the error for
v The program cannot be loaded. abnormal conditions in processing the PGLK domain call. This
System action: The transaction requiring the program is may be due to a problem with directory manager, loader, or
abnormally terminated with a CICS transaction dump. storage manager. Check the program size. It may be necessary
User response: In cases 1 and 2, define the program, mapset to increase the overall size limits of the DSAs or EDSAs.
partitionset to CICS using CEDA and ensure it is enabled. Module: DFHPCP, DFHMCY
In case 3, the definition of a CICS-provided module is
incorrect. Check for associated messages issued during CICS APC1
start up. Explanation: A request for a TGT exceeding 64KB has been
Problem determination: The trace preceding the abend detected.
indicates the program, mapset, or partitionset that could not System action: CICS abnormally terminates the transaction
be loaded, linked to, or released. The name is also in and disables the installed program definition.
TCAPCEPI. User response: Change the application program to reduce the
Module: DFHACP, DFHAMPEN, DFHCRSP, DFHEDFP, working storage requirement. Perform CEMT NEWCOPY and
DFHEIP, DFHEIPSH, DFHEIQSJ, DFHFEP, DFHICP, ENABLE for the program when it has been corrected.
DFHJCEOV, DFHJCO, DFHMCP, DFHMCPE, DFHMCY, Module: DFHAPLI

APC2 • APP2
APC2 APDD
Explanation: An illegal branch has been attempted by a LE Explanation: An attempt has been made to execute an EXEC
for z/VSE user program following an abend condition with an CICS command from a PL/I program compiled with an
active handle label abend. Usually an Out-Of-Block GOTO unsupported PL/I compiler.
will have resulted, implying that the program tried to branch System action: CICS terminates the task, and disables the
to, for example, an inactive block. This abend is accompanied program.
by message DFHAP1200 which gives the reason code set by User response: Recompile the program with the PL/I for
LE for z/VSE indicating the nature of the error. VSE/ESA compiler; you may need to change the source
System action: The transaction is abnormally terminated and program.
the program is disabled. Module: DFHEIP
User response: Refer to the IBM Language Environment for
z/VSE, Debugging Guide and Run-Time Messages manual for the
meaning of the reason code, and amend the program to avoid APDE
the GOTO in error. Explanation: An attempt has been made to execute an EXEC
Module: CICS command with an invalid PSW key. CICS only supports
Module: DFHAPLI execution of EXEC CICS commands in either CICS key
(partition key) or USER key (key 9).
System action: CICS terminates the task, and disables the
APC3 program.
Explanation: An attempt to run the program failed because User response: Modify the application to ensure all EXEC
the program appeared to be compiled with an LE-conforming CICS commands are issued in either CICS or USER key only.
compiler but no LE for z/VSE support was present in the Module: DFHEIP, DFHEIPA
system and no other language environment was able to run
the program.
System action: The transaction is abnormally terminated and APP1
the program is disabled. Explanation: The DFHIC TYPE=GET response code was not
User response: If the program is compiled with an a normal response.
LE-conforming compiler ensure LE for z/VSE support is System action: The transaction is abnormally terminated with
installed in the system. a CICS transaction dump.
Module: DFHAPLI User response: Analyze the dump. The response code is in
the low-order byte of register 0.
Module: DFHP3270
APDA
Explanation: An attempt has been made to execute a
program in 31-bit addressing mode. However, the level of APP2
compiler used to compile the program produces output that is Explanation: The length of data that has been passed to
executable in 24-bit addressing mode only. DFHP3270 via temporary storage is less than or equal to 5.
a CICS transaction dump and the PPT entry is disabled. a CICS transaction dump.
User response: Ensure that the program is link-edited using User response: Check the user DFHTEP. If it is not at fault,
the AMODE(24) option. submit an APAR.
Module: DFHAPLI If this abend has occurred, the data that DFHP3270 obtained
from temporary storage was probably put there with an
APDB incorrect length. The user may have requested indirectly that
Explanation: A CICS task has invoked a program which was this data be placed in temporary storage either by an
defined as C but the program has been compiled with an application request for printing (for example ISSUE PRINT) or
unsupported compiler. by pressing the Print Request key. However, CICS should
System action: CICS terminates the task, and disables the control the data length for this request. Under normal
program. circumstances, the only way the user could have requested
User response: Check that the program is C. If the program directly that data is to be placed in temporary storage is in the
is C, recompile it with the C for VSE/ESA compiler; you may user's TEP. The user should check any invocations of DFHIC
need to change the source program. If the program is not C, TYPE=PUT in handling print requests, particularly when
redefine it correctly. dealing with the “printer unavailable or busy” condition, and
Module: DFHAPLI ensure that the length field is set correctly.
Problem determination: Register 6 points to the data
retrieved from temporary storage via a DFHIC TYPE=GET
APDC macro invocation. The layout of this data is:
Explanation: A CICS task has invoked a program which has v Terminal data area length (2 bytes)
been compiled with the C/370™ compiler which is no longer v Write control indicator (1 byte)
supported. v Write control or carriage control character (1 byte)
System action: CICS terminates the task, and disables the v Data (variable length)
program.
User response: Recompile the program with the C for Analysis: DFHP3270 has been called to handle a print request
VSE/ESA compiler; you may need to change the source from a 3270 Information Display System terminal. It obtains
program. from temporary storage the data to be printed, via a DFHIC
Module: DFHAPLI
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.

APP3 • APSI
DFHP3270 has found that, because the length of data passed User response: Use a display terminal that is supported by
to it is less than or equal to 5, there is no data to be printed. CEOS or CEMS.
Module: DFHP3270 Module: DFHEMS00
APP3 APSD
Explanation: An attempt to request data has been sent to a Explanation: Error flagged by DFHEMSR1. The start-browse
nonprinter or unsupported device type by either: failed when building a list using CEMS.
v A terminal operator entering CSPP as a transaction code, or System action: The transaction is abnormally terminated with
v A transaction issuing a DFHTEP request. a CICS transaction dump.
System action: The transaction is abnormally terminated. A User response: Either:
CICS transaction dump is not provided. 1. Retry transaction
User response: 2. Notify the system programmer.
1. Ensure that the terminal operator ceases to use CSPP as a Module: DFHEMSR1
transaction code, or
2. Correct the user DFHTEP program.
Module: DFHP3270 APSE
Explanation: Error flagged by DFHEMSP1. The start-browse
command failed when building a list using CEMS.
APR1 System action: The transaction is abnormally terminated with
Explanation: An abnormal DFHIC TYPE=PUT response code a CICS transaction dump.
was received during print key processing. User response: Either:
System action: The transaction is abnormally terminated with 1. Retry transaction
a CICS transaction dump. The keyboard of the terminal on 2. Notify the system programmer.
which the print key was depressed remains locked to indicate Module: DFHEMSP1
the failure of the operation.
User response: Analyze the dump. The response code is in
low-order byte of register 0. APSF
Module: DFHPRK Explanation: Error flagged by DFHEMSJ1. The start-browse
failed when building a list using CEMS.
APSA a CICS transaction dump.
Explanation: Irrecoverable error on the POWER interface. User response: Either:
APSA is produced for certain logic errors when register 0 1. Retry transaction
contains the first word of the reply buffer, register 1 contains 2. Notify the system programmer.
the current return code, and register 15 contains a code Module: DFHEMSJ1
defined as follows:
X’01’ Invalid request type APSG
X’02’ Order response to start command failed Explanation: Error flagged by DFHPSPFX. A printer buffer
address, exceeding the maximum allowed, was encountered
X’03’ Unexpected order response when converting a 3270 data stream.
X’04’ Unexpected setup processed response a CICS transaction dump.
X’05’ Unable to open report. Module: DFHPSPFX
User response: Notify the system programmer. APSH
Module: DFHPSPIO Explanation: Unable to close a report during backout
processing.
APSB a CICS transaction dump.
Explanation: Error flagged by DFHEMS00. An attempt has User response: Notify the system programmer.
been made to use CEOS or CEMS on an unsupported Module: DFHPSBP
terminal.
a CICS transaction dump. APSI
User response: Use a display terminal that is supported by Explanation: Unable to initialize spooler.
CEOS or CEMS. System action: CICS terminates the transaction abnormally.
Module: DFHEMS00 User response: You need further assistance from IBM to
APSC Module: DFHCXPA
Explanation: Error flagged by DFHEMS00. An attempt has
been made to use CEMS or CEOS on a display terminal of
size less than 24x80.

APSK • APS3
APSK APSR
Explanation: DFHPSOP is abending after an error response Explanation: DFHPSOP is abending after an error response
from a DFHPS TYPE=TRANSFER macro. from a DFHPS TYPE=PRINTER,PRACTN=SETUP macro.
User response: Notify the system programmer. User response: Notify the system programmer.
Module: DFHPSOP Module: DFHPSOP
APSL APSS
Explanation: DFHPSOP is abending after an error response Explanation: DFHPSOP is abending after an error response
from a DFHPS TYPE=PRINTER,PRACTN=CONFIRM macro. from a DFHPS TYPE=PRINTER,PRACTN=SETUPCOM macro.
APSM APST
Explanation: DFHPSOP is abending in compliance with Explanation: A task issued a SPOOL command without the
instructions from the NACP or TACP, after a terminal error, mandatory NOHANDLE operand.
and the terminal is being set out of service. System action: CICS terminates the task abnormally with a
System action: The transaction is abnormally terminated with dump.
a CICS transaction dump. User response: Correct the syntax of the command,
User response: Notify the system programmer. specifying NOHANDLE.
Module: DFHPSOP Module: DFHEPS
APSN APS0
Explanation: DFHPSOP is abending in compliance with Explanation: DFHPSOP is abending because the defined
instructions from the NACP or TACP, after a terminal error. printer buffer size in the TCTTE is too small to allow the
The terminal is left in service. transaction to run.
APSO APS1
Explanation: DFHPSOP is abending after an error response Explanation: DFHPSOP is abending after an unrecognizable
from a DFHPS TYPE=OPEN,OPTION=GENIN macro. response from a PRINTER SETUP request.
APSP APS2
Explanation: DFHPSOP failed at initiation because it could Explanation: The writer task is abending after DFHPSOMH
not locate DFHPSWPS from the TCTTE (addressed by was asked to send an unknown message.
TCTTEQAP). System action: The transaction is abnormally terminated with
a CICS transaction dump. User response: Notify the system programmer.
User response: Notify the system programmer. Module: DFHPSOMH
Module: DFHPSOP
APS3
APSQ Explanation: DFHPSOP is abending after an error response
Explanation: The device on which CEPW has been started is from a DFHPS TYPE=CLOSE,OPTION=GENIN macro.
not supported by DFHPSOP. System action: The transaction is abnormally terminated with
a CICS transaction dump. User response: Notify the system programmer.
User response: The device on which CEPW was started has Module: DFHPSOP
one of the characteristics listed below. Fix and retry.
v It is not a terminal
v It is a terminal but without the forms-feed feature
v It is a terminal but without the 3288 Textprint feature.
Module: DFHPSOP

APS4 • APTG
User response: Determine the reason why the write to an

APS4
audit trail failed and correct.
Explanation: DFHPSOP is abending after an error response
Module: DFHEMSR4
from a DFHPS TYPE=READ macro.
a CICS transaction dump. APTB
User response: Notify the system programmer. Explanation: Error flagged by DFHEMSP4. An attempt has
Module: DFHPSOP been made to write to the audit trail CSPA which failed for a
reason other than NOSPACE or QIDERR.
APS5
Explanation: DFHPSOP is abending after being unable to
read a record when it had previously enlarged its INPUT
buffer.
Module: DFHEMSP4
User response: Notify the system programmer. DFHPSOP APTC
Explanation: Error flagged by DFHEMSJ4. An attempt has
been made to write to the audit trail CSPA which failed for a
APS6
reason other than NOSPACE or QIDERR.
from a DFHPS TYPE=PRINTER,PRACTN=DISCON macro.
Module: DFHEMSJ4
Module: DFHPSOP
APTD
APS7
Explanation: DFHPSOP is abending after an error (other than
while retrying a DFHPS TYPE=READ macro.
NOSPACE or QIDERR) when writing to an audit trail (CSPA
or CSPW).
User response: Notify your system programmer.
Module: DFHPSOP
audit trail is failing and correct.
Module: DFHPSOMH APTE
Explanation: CICS has attempted to call a nonexistent
sub-routine in DFHPSOPR.
APS8 System action: Transaction CEPW is abnormally terminated
Explanation: Error flagged by DFHEMS00. An attempt has with a CICS transaction dump.
been made to use XCTL or LINK to DFHEMSP (that is, User response: You need further assistance from IBM to
EIBTRNID is not CEOS or CEMS). resolve this problem. See Part 4 of the CICS Problem
System action: The transaction is abnormally terminated with Determination Guide for guidance on how to proceed.
a CICS transaction dump. Module: DFHPSOP, DFHPSOPR
User response: Correct the program attempting to use XCTL
or LINK to DFHEMSP so that it uses EXEC CICS START
command instead. APTF
Module: DFHEMS00 Explanation: DFHPSOP is abending after an error response
from a DFHPS TYPE=ORDWAIT macro while the RCF printer
sharing facility is enabled.
APS9 System action: Transaction CEPW is abnormally terminated
Explanation: DFHPSOP reserves a stack for its subordinate with a CICS transaction dump.
modules to use as automatic storage. DFHPSOP abends with User response: You need further assistance from IBM to
this abend code if any subordinate module exceeds the size of resolve this problem. See Part 4 of the CICS Problem
this storage. Determination Guide for guidance on how to proceed.
System action: The transaction is abnormally terminated with Module: DFHPSOP
User response: Notify the system programmer. APTG
Module: DFHPSOP Explanation: CICS has attempted to issue a call to print
related sub-routines within a principle facility (printer).
System action: Transaction CEPW is abnormally terminated
APTA
with a CICS transaction dump.
Explanation: Error flagged by DFHEMSR4. An attempt has
been made to write to the audit trail CSPA which failed for a resolve this problem. See Part 4 of the CICS Problem
reason other than NOSPACE or QIDERR. Determination Guide for guidance on how to proceed.
System action: The transaction is abnormally terminated with Module: DFHPSOP, DFHPSOPR

APTH • APTQ
APTH APTN
Explanation: DFHPSOP is abending after an error response Explanation: During initialization, a request was made to the
from a DFHPS TYPE=START macro while the RCF printer SMAD domain with function ADD_SUBPOOL to create a
sharing facility is enabled. system-wide subpool for use by report controller. This has
System action: Transaction CEPW is abnormally terminated returned a response of INSUFFICIENT STORAGE.
with a CICS transaction dump. System action: It is unlikely that initialization will complete
User response: You need further assistance from IBM to due to critical storage problems. Other storage-related
resolve this problem. See Part 4 of the CICS Problem symptoms may also occur. The task is abnormally terminated
Determination Guide for guidance on how to proceed. with a CICS transaction dump.
Module: DFHPSOP User response: Try increasing the value specified for the
system initialization parameter EDSALIM. See the CICS System
Definition Guide or the CICS Performance Guide for more
APTK information.
Explanation: The task was purged before a GETMAIN Module: DFHPSP
purged condition will have provided an exception trace. APTO
System action: The task is abnormally terminated with a Explanation: During initialization, a request was made to the
CICS transaction dump. SMAD domain with function ADD_SUBPOOL to create a
User response: Investigate why the task was purged. It was system-wide subpool for use by report controller. This has
purged either as a result of a purge from the master terminal returned an unexpected response. The domain that detected
operator via the CEMT transaction, or by the task being timed the original error provides an exception trace, a console
out after waiting for longer than the DTIMOUT (deadlock message, and possibly a system dump (depending on the
timeout) value specified for the transaction. options in the dump table).
System action: It is unlikely that initialization will complete
If the master terminal operator purged the task, this may have due to internal problems with the storage manager. The task is
been in an attempt to clear the system which appeared to be abnormally terminated with a CICS transaction dump.
deadlocked for some reason. User response: See the related message from the domain that
If the task was timed out automatically as a result of the detected the original error.
DTIMOUT value being exceeded, this may be due to Module: DFHPSP
APTP
Explanation: Upon return from a DFHPS TYPE=OPEN,ANY
a return code greater than 4 was received, which is considered
to be an error by program DFHCXPB (transaction CXPB). The
Module: DFHPSBP, DFHPSCMD, DFHPSP, DFHPSPCB,
return code passed back is the value in register 15 from the
DFHPSPFX, DFHPSPIO, DFHPSPO, DFHPSPW.
XPCC macro.
System action: Transaction CXPB is terminated with a dump.
APTL This means that you will no longer be able to start Report
Explanation: An error (INVALID, DISASTER or unexpected Controller printers, since the CXPB transaction is the CICS
EXCEPTION response) has occurred on a call to the storage interface to which VSE/POWER passes PSTART requests.
manager (SM) domain. The domain that detected the original User response: Depending on the nature of the error, it may
error will have provided an exception trace, a console message be possible to re-establish the connection between CICS and
and, possibly, a system dump (depending on the options VSE/POWER by issuing a EXEC CICS START
specified in the dump table). TRANSID(CXPB) command (either in a user program, or
System action: The task is abnormally terminated with a using CECI directly). However, if this attempt also fails, you
CICS transaction dump. will have to recycle CICS in order to be able to use Report
User response: See the related message from the domain that Controller printers.
detected the original error. Module: DFHCXPB
Module: DFHPSBP, DFHPSCMD, DFHPSP, DFHPSPCB,
DFHPSPFX, DFHPSPIO, DFHPSPO, DFHPSPW.
APTQ
Explanation: Program DFHCXPB (transaction CXPB) has
APTM detected that an abend has been issued.
Explanation: DFHPSPCB has found an unrecognizable System action: Transaction CXPB is terminated with a dump.
control block id in a spooler control block while trying to This means that you will no longer be able to start Report
determine its storage class prior to a call to the storage Controller printers, since the CXPB transaction is the CICS
manager domain (SM) to FREEMAIN it. This was caused interface to which VSE/POWER passes PSTART requests.
either by a storage overwrite or a CICS internal logic error. User response: Depending on the nature of the error, it may
System action: The task is abnormally terminated with a be possible to re-establish the connection between CICS and
CICS transaction dump. VSE/POWER by issuing a EXEC CICS START
User response: Notify your system programmer. If the TRANSID(CXPB) command (either in a user program, or
problem is re-creatable, a level 1 trace of the RC component using CECI directly). However, if this attempt also fails, you
would aid problem determination. will have to recycle CICS in order to be able to use Report
Module: DFHPSPCB Controller printers.
Module: DFHCXPB

APUA • APUJ
APUA APUF
Explanation: An internal error was detected when module Explanation: Either the RDO language definition table is
DFHPUP was invoked. The GETSTG parameter is missing on invalid or it is missing from the library.
a call to DFHPUP (PUPF). System action:
System action: v In a CICS environment, the CEDA transaction is abnormally
v In a CICS environment, the CEDA transaction is abnormally terminated with a CICS transaction dump.
terminated with a CICS transaction dump. v In a batch environment, processing is abnormally
v In a batch environment, processing is abnormally terminated with an operating system dump.
terminated with an operating system dump. User response: Ensure that module DFHEITSP is in the
User response: You need further assistance from IBM to library and is valid for this release of CICS.
resolve this problem. See Part 4 of the CICS Problem Module: DFHPUP
Module: DFHPUP
APUG
Explanation: An internal error was detected in module
APUB DFHPUP. Storage could not be obtained for the CSD record
Explanation: An internal error was detected when module buffer.
DFHPUP was invoked. The GETSTG parameter is missing on System action:
a call to DFHPUP (PUPU). v In a CICS environment, the CEDA transaction is abnormally
System action: terminated with a CICS transaction dump.
v In a CICS environment, the CEDA transaction is abnormally v In a batch environment, processing is abnormally
terminated with a CICS transaction dump. terminated with an operating system dump.
v In a batch environment, processing is abnormally User response: You need further assistance from IBM to
terminated with an operating system dump. resolve this problem. See Part 4 of the CICS Problem
User response: You need further assistance from IBM to Determination Guide for guidance on how to proceed.
resolve this problem. See Part 4 of the CICS Problem Module: DFHPUP
Module: DFHPUP
APUH
APUC DFHPUP. Storage could not be obtained for the argument list.
Explanation: An internal error was detected when module System action:
DFHPUP was invoked. An invalid function code was supplied v In a CICS environment, the CEDA transaction is abnormally
for a domain call to DFHPUP. terminated with a CICS transaction dump.
System action: v In a batch environment, processing is abnormally
v In a CICS environment, the CEDA transaction is abnormally terminated with an operating system dump.
terminated with a CICS transaction dump. User response: You need further assistance from IBM to
v In a batch environment, processing is abnormally resolve this problem. See Part 4 of the CICS Problem
terminated with an operating system dump. Determination Guide for guidance on how to proceed.
User response: You need further assistance from IBM to Module: DFHPUP
Module: DFHPUP APUI
DFHPUP. Storage cannot be freed for the argument list.
APUD System action:
Explanation: The RDO language definition table (DFHEITSP) v In a CICS environment, the CEDA transaction is abnormally
could not be located in the library. terminated with a CICS transaction dump.
System action: v In a batch environment, processing is abnormally
v In a CICS environment, the CEDA transaction is abnormally terminated with an operating system dump.
terminated with a CICS transaction dump. User response: You need further assistance from IBM to
v In a batch environment, processing is abnormally resolve this problem. See Part 4 of the CICS Problem
terminated with an operating system dump. Determination Guide for guidance on how to proceed.
User response: Ensure that module DFHEITSP is in the Module: DFHPUP
library and is valid for this release of CICS.
Module: DFHPUP
APUJ
APUE DFHPUP. Storage cannot be freed for the CSD record buffer.
Explanation: The RDO language definition table (DFHEITSP) System action:
could not be loaded because of a lack of available storage. v In a CICS environment, the CEDA transaction is abnormally
System action: Processing is abnormally terminated with an terminated with a CICS transaction dump.
operating system dump. v In a batch environment, processing is abnormally
User response: Allocate more storage and resubmit the terminated with an operating system dump.
offline COPY or APPEND command(s) that failed. User response: You need further assistance from IBM to
Module: DFHPUP (Batch environment) resolve this problem. See Part 4 of the CICS Problem
Module: DFHPUP

APUK • APUS
APUK APUO
Explanation: Explanation: Refer to the description of abend APUL.
v In a CICS environment, storage could not be acquired for a
buffer to contain logged RDO commands in the CEDA
transaction. APUP
v In a batch environment, storage could not be acquired for a Explanation: An internal error occurred in DFHPUP
buffer to contain back-translated resource definitions from processing of the language definition table for RDO. There
the CSD. was a stack error building a keyword list for the syntax tree.
System action: System action:
v In a CICS environment, the CEDA transaction is abnormally v In a CICS environment, the CEDA transaction is abnormally
terminated with a CICS transaction dump. terminated with a CICS transaction dump.
v In a batch environment, processing is abnormally v In a batch environment, processing is abnormally
terminated with an operating system dump. terminated with an operating system dump.
Module: DFHPUP Module: DFHPUP
APUL APUQ
Explanation: CICS cannot find a match for a function code in Explanation: An internal error occurred in DFHPUP
the language definition table, because the parameterized processing of the language definition table for RDO. Too many
resource definition contains an unrecognized resource type keywords found in syntax expansion.
code. System action:
v In a CICS environment, the CEDA transaction is abnormally
The abend code issued depends on the DFHPUP operation terminated with a CICS transaction dump.
that was invoked before the error occurred: v In a batch environment, processing is abnormally
Abend DFHPUP operation User response: You need further assistance from IBM to
APUL FLATTEN resolve this problem. See Part 4 of the CICS Problem
APUM TRANCASE Determination Guide for guidance on how to proceed.
Module: DFHPUP
APUN COMPARE
APUO BACKTRANS
APUR
Explanation: An internal error occurred in DFHPUP
The cause of the abend is either: processing of an argument list or a CSD record buffer. The
1. A language definition table (DFHEITSP or DFHEITCU) in data type for a keyword field conflicts with the data type
the library is invalid for the CICS release you are running, specified in the language definition table.
or System action:
2. A CICS logic error has occurred. v In a CICS environment, the CEDA transaction is abnormally
System action: terminated with a CICS transaction dump.
v In a CICS environment, the CEDA transaction is abnormally v In a batch environment, processing is abnormally
terminated with a CICS transaction dump. terminated with an operating system dump.
v In a batch environment, processing is abnormally User response: Ensure that the module DFHEITSP is in the
terminated with an operating system dump. library and is valid for this release of CICS.
User response: Your response depends on which of the two Module: DFHPUP
possible reasons apply:
1. Ensure that the DFHEITSP and DFHEITCU modules in the
library are valid for this release of CICS. APUS
2. You need further assistance from IBM to resolve this Explanation: An internal error occurred in DFHPUP
problem. See Part 4 of the CICS Problem Determination processing of a CSD record buffer. The integer data length for
Guide for guidance on how to proceed. a keyword field is invalid.
Module: DFHPUP System action:
Note: The description of this abend also applies to APUM, v In a CICS environment, the CEDA transaction is abnormally
APUN and APUO. terminated with a CICS transaction dump.
v In a batch environment, processing is abnormally
APUM User response: Ensure that the module DFHEITSP is in the
Explanation: Refer to the description of abend APUL. library and is valid for this release of CICS.
Module: DFHPUP
APUN
Explanation: Refer to the description of abend APUL.

APUT • ARHC
APUT ARCB
Explanation: An internal error occurred in DFHPUP Explanation: CICS has attempted to enable a task-related
processing of an argument list or a CSD record buffer. The user exit, or a global user exit during initialization, but failed
keyword existence bit number, which is the KEP(1) value in because the exit program could not be found.
language definition table DFHEITSP, is not valid. On an emergency restart, CICS enables transaction backout
System action: exit programs as specified by the TBEXITS system
v In a CICS environment, the CEDA transaction is abnormally initialization parameter.
terminated with a CICS transaction dump. System action: CICS issues a message to the console
v In a batch environment, processing is abnormally indicating which exit program is involved. CICS initialization
terminated with an operating system dump. then terminates abnormally with a system dump.
User response: Ensure that the module DFHEITSP is in the User response: Ensure the named program has been defined
library and is valid for this release of CICS. to CICS and is in a sublibrary of the LIBDEF search chain for
Module: DFHPUP the CICS job.
If necessary, use the dump to find out why the exit program
APUZ could not be enabled.
Explanation: CICS has found an unrecognized resource type Module: DFHRCEX
any of the function codes in the language definition table. This
ARHA
abend can occur for one of the following reasons:
Explanation: The SAA resource recovery interface has been
1. You are using a CICS release that does not support a type invoked with an invalid first parameter. The first parameter
of definition that was created on the CSD file by a later should be the code of the function to be performed. This is a
CICS release. CICS internal logic error.
2. The language definition table (DFHEITSP or DFHEITCU) is System action: The transaction is abnormally terminated with
invalid for this CICS release. a CICS transaction dump.
3. The CSD manager (DFHDMP) has passed an invalid CSD User response: A level 2 trace for 'CP' of the transaction
record buffer to DFHPUP. This is a CICS internal logic shows the course of events before this error occurred (such as
error. the modules called and their parameters) plus details of the
System action: error itself. You need further assistance from IBM to resolve
v In a CICS environment, the CEDA transaction is abnormally this problem. See Part 4 of the CICS Problem Determination
terminated with a CICS transaction dump Guide for guidance on how to proceed.
v In a batch environment, processing is abnormally Module: DFHCPIR
ARHB
Explanation: The SAA resource recovery interface has been
invoked with an invalid number of parameters for the call.
Take action corresponding to the reason you have established System action: the transaction is abnormally terminated with
as follows: a CICS transaction dump.
1. Avoid operations on groups containing definition-types User response: The exception trace point produced with this
that are unsupported by the CICS release you are running. abend contains the SAA resource recovery verb name that was
2. Ensure that the library contains versions of DFHEITSP and issued incorrectly. Use this to determine where the application
DFHEITCU that are valid for the CICS release you are program was in error and amend application program
running. accordingly. The SAA Resource Recovery Reference Manual
provides a detailed description of the SAA resource recovery
verbs and how they should be called.
Module: DFHCPIR
Module: DFHPUP
ARHC
Explanation: The SAA resource recovery interface has
ARCA detected an unexpected return code from the syncpoint
Explanation: The CICS recovery control restart task could not program. This is a CICS internal logic error.
complete because a necessary step failed. The task has done System action: The transaction is abnormally terminated with
some essential recovery operations and abnormally terminated a CICS transaction dump.
itself with code ARCA. User response: A level 2 trace for 'CP' of the transaction
System action: CICS writes a transaction dump for the shows the course of events before this error occurred (such as
recovery control restart task. CICS then terminates abnormally the modules called and their parameters) plus details of the
with a system dump. error itself. You need further assistance from IBM to resolve
CICS sends two messages to the console, one to identify the this problem. See Part 4 of the CICS Problem Determination
error detected by the recovery control restart task, and one to Guide for guidance on how to proceed.
say that the task has failed. Depending on the nature of the Module: DFHCPIR
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: DFHRCRP

ARL1 • ASCB
ARL1 ARTE
Explanation: Transaction CSLG was entered to CICS, but was Explanation: An error was encountered when attempting to
not internally initiated by a task attach. read from or write to temporary storage.
System action: The transaction is abnormally terminated with System action: The task is abnormally terminated with a
a CICS transaction dump. CICS transaction dump.
User response: Do not reenter the CSLG transaction User response: Determine the cause of the temporary storage
identification. problem and correct it.
Module: DFHZRLG Module: DFHRTE
ARPA ARTF
Explanation: An unexpected response from DFHSUSN has Explanation: An attempt has been made to use the routing
occurred when trying to sign off a user of the CRTE transaction (CRTE) from a terminal that has a permanent
transaction in the target system when processing a CANCEL transaction code set.
request. System action: The task is abnormally terminated with a
This abend can be caused by incorrect use of the VTAM VARY User response: Inform the system programmer.
INACT command. Otherwise it indicates that there may be an Module: DFHRTE
error in CICS.
System action: The CSSF transaction (CRTE cancel processor
transaction) is terminated with an ARPA abend. ARTG
User response: Ensure that the VTAM VARY inact command Explanation: CICS could not find the profile specified for a
is used correctly. If this is not the cause of the abend, you transaction being routed.
need further assistance from IBM to correct this problem. See System action: CICS terminates the task abnormally with a
Part 4 of the CICS Problem Determination Guide for guidance on dump.
how to proceed. User response: Check your transaction and profile
Module: DFHRTC definitions.
Module: DFHRTE
ARTA
Explanation: The task does not own a terminal as its ARTH
principal facility. Explanation: An error (INVALID, DISASTER or EXCEPTION
System action: The task is abnormally terminated with a response) has occurred on a call to schedule a remote terminal
CICS transaction dump. delete by DFHRTE during signoff for a surrogate terminal
User response: Ensure that DFHRTE has not been specified session running CRTE. The domain that detected the original
as the program for a task other than CRTE. Ensure that CRTE error provides an exception trace, a console message and,
has not been initiated by means other than terminal input. possibly, a system dump depending on the options specified
Module: DFHRTE in the dump table).
dump.
ARTB User response: See the related message produced by the
Explanation: There is no input TIOA or the data length is domain that detected the original error.
zero. Module: DFHRTE
User response: Ensure that DFHRTE has not been specified ASCA
as the program for a task other than CRTE. Ensure that CRTE Explanation: A DFHSC TYPE=GETMAIN request has
has not been initiated by means other than terminal input. resulted in a call to the storage manager (SM) domain which
Module: DFHRTE has returned an INVALID or DISASTER response.
System action: The transaction is terminated with a CICS
transaction dump.
ARTC User response: There has been an earlier failure which led to
Explanation: The link to the required system is not usable for the response from the storage manager domain. Investigate
an unknown reason. the earlier failure (which is accompanied by a console message
System action: The task is abnormally terminated with a and a system dump).
CICS transaction dump. Module: DFHSMSCP
Determination Guide for guidance on how to proceed. ASCB
Module: DFHRTE 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.
ARTD System action: The transaction is terminated with a CICS
Explanation: An internal logic error has been detected. transaction dump.
System action: The task is abnormally terminated with a User response: There has been an earlier failure which led to
CICS transaction dump. the response from the storage manager domain. Investigate
User response: You need further assistance from IBM to the earlier failure (which is accompanied by a console message
resolve this problem. See Part 4 of the CICS Problem and a system dump).
Determination Guide for guidance on how to proceed. Module: DFHSMSCP
Module: DFHRTE

ASCP • ASOA
Module: DFHSFP
ASCP
Explanation: A task which has issued an unconditional
DFHSC TYPE=GETMAIN request has been purged while ASIA
waiting for sufficient contiguous main storage to become free. Explanation: An error has occurred on a call to the storage
System action: The task is abnormally terminated with a manager (SM) domain. The domain that detected the original
CICS transaction dump. error will have provided an exception trace, a console message
User response: Investigate why the task was purged. This and, possibly, a system dump (depending on the options
will either have been as a result of a purge from the master specified in the dump table).
terminal operator via the CEMT transaction, or by the task System action: The task is abnormally terminated with a
being timed out after waiting for longer than the DTIMOUT CICS transaction dump. CICS then terminates abnormally.
(deadlock timeout) value specified for the transaction. User response: See the related message from the domain that
If the task was purged by the master terminal operator then detected the original error.
this may have been in an attempt to clear the system which Module: DFHSII1
If the task was timed out automatically as a result of the ASIB
DTIMOUT value being exceeded then this may be due to Explanation: An attempt has been made to run the CICS
insufficient main storage being available for the number of internal task CPLT as a user transaction.
tasks in the system. If the amount of main storage cannot be System action: CICS terminates the task with a transaction
increased then the number of tasks in the system should be dump.
reduced to avoid short-on-storage situations. Another User response: Investigate why the attempt was made to run
possibility would be to increase the value of the DTIMOUT CPLT as a user transaction.
option for the transaction. Module: DFHSIPLT
Module: DFHSMSCP
ASNA
ASCR Explanation: An internal logic error occurred in DFHSNP
Explanation: A DFHSC macro request has been issued with because of an unexpected response from EXEC CICS.
an invalid request type. System action: CICS terminates the transaction with a dump.
System action: The transaction is terminated with a CICS This abend code is usually accompanied by message
transaction dump. DFHCE3548.
Detection of the invalid request by DFHSMSCP causes a resolve this problem. See Part 4 of the CICS Problem
console message and a system dump to be produced. Determination Guide for guidance on how to proceed.
User response: Use the associated console message and Module: DFHSNP
system dump to investigate the problem.
Module: DFHSMSCP
ASNB
Explanation: An attempt was made execute the CICS sign on
ASFA program without an associated terminal. This abend code is
Explanation: An internal logic error occurred in DFHSFP usually accompanied by message DFHCE3548.
because of an unexpected response from EXEC CICS. This System action: CICS terminates the transaction with a dump.
abend code is usually accompanied by message DFHCE3598 User response: Only use the sign on program when there is a
which contains the associated return codes. related terminal.
System action: The transaction is abnormally terminated with Module: DFHSNP
resolve this problem. See Part 4 of the CICS Problem ASNC
Determination Guide for guidance on how to proceed. Explanation: The signon program attempted to send a
Module: DFHSFP request to the user but failed to do so.
System action: CICS terminates the transaction with a dump.
This abend code is usually accompanied by message
ASFB DFHCE3548.
Explanation: An attempt was made to execute the CICS User response: You need further assistance from IBM to
signoff program without an associated terminal. resolve this problem. See Part 4 of the CICS Problem
System action: CICS terminates the transaction with a dump. Determination Guide for guidance on how to proceed.
This abend code is usually accompanied by message Module: DFHSNP
DFHCE3598.
User response: Only use the signoff program when there is a
related terminal. ASOA
Module: DFHSFP 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
ASFC CEMT SET TCPIP OPEN or the equivalent SPI function.
Explanation: An attempt was made execute the CICS signoff System action: The transaction is abnormally terminated with
program against an APPC session. a transaction dump.
System action: CICS terminates the transaction with a dump. User response: None.
This abend code is usually accompanied by message Module: DFHSOL
DFHCE3598.
User response: Only use the signoff program when there is a
related terminal.

ASPA • ASPH
command cannot handle this abend.

ASPA
User response: Ensure that DFHDBP is available and
correctly specified as a system initialization parameter.
Module: DFHSPP
System action: The task is abnormally terminated with a ASPF
CICS transaction dump. If processing is at a point where data Explanation: A syncpoint has been attempted with an
integrity might not be maintained, CICS is abnormally intersystem session which has returned ROLLEDBACK to
terminated. syncpoint program. As a result, the transaction is abnormally
User response: Investigate why the task was purged. This is terminated because the logical unit of work which was being
either as a result of a purge from the master terminal operator syncpointed has been backed out.
via the CEMT transaction, or by the task being timed out after
waiting for longer than the DTIMOUT (deadlock timeout) This could result from shutting down IRC or from the failure
value specified for the transaction. of a connected CICS region.
If the master terminal operator purged the task, this may have a CICS transaction dump.
been in an attempt to clear the system which appeared to be User response: Determine why the remote intersystem
deadlocked for some reason. session returned a ROLLEDBACK response to the syncpoint
If the task was timed out automatically as a result of the request. Once this has been corrected retry the transaction.
DTIMOUT value being exceeded, this may be due to To avoid ASPF abends in future, ensure that no in-flight units
insufficient main storage being available for the number of of work exist before shutting down IRC.
tasks in the system. If the amount of main storage cannot be Module: DFHSPP
the value of the DTIMOUT option for the transaction. ASPG
Explanation: The local transaction program was about to
If CICS is abnormally terminated, it should be emergency participate in a syncpoint with a partner transaction program
restarted to ensure that data integrity is maintained. connected via APPC synclevel 2. While initializing a URD
Module: DFHSPP, DFHSPZ control block for the partner, the local system detected an
invalid format in the partner's fully qualified LU name. As a
ASPB result, no syncpoint operations could complete with integrity.
Explanation: An error (INVALID, DISASTER or unexpected This error is caused by an invalid LU name in the partner's
EXCEPTION response) has occurred on a call to the storage EXCHANGE LOG NAMES command
manager (SM) domain. The domain that detected the original System action: The transaction program is abnormally
error will have provided an exception trace, a console message terminated with a CICS transaction dump and CICS backs out
and, possibly, a system dump (depending on the options of all recoverable changes.
specified in the dump table). User response: Ask the operator of the partner to help
System action: The task is abnormally terminated with a resolve the problem, and ensure that EXCHANGE LOG
CICS transaction dump. If processing is at a point where data NAMES completes successfully before synclevel 2 activity is
integrity might not be maintained, CICS is abnormally attempted.
terminated. Module: DFHSPZ
detected the original error. If CICS was abnormally
terminated, it should be emergency restarted to ensure that ASPH
data integrity is maintained. Explanation: The local transaction program was about to
Module: DFHSPP, DFHSPZ participate in a syncpoint with a partner transaction program
connected via APPC synclevel 2. At the start of syncpoint
processing, no logname for the partner LU was found,
ASPD indicating that EXCHANGE LOG NAMES has not completed
Explanation: An error has occurred while trying to reset the successfully. As a result, no syncpoint operations can complete
dynamic log. The syncpoint may represent either a user with integrity.
syncpoint or a syncpoint at the end of a logical unit of work
or during restart of a transaction. This error is caused by EXCHANGE LOG NAMES processing
System action: The task is abnormally terminated with a failing to complete successfully.
CICS transaction dump. The EXEC CICS HANDLE ABEND System action: The transaction program is abnormally
command can not handle this abend. terminated with a CICS transaction dump and CICS backs out
User response: Notify the system programmer of the error, of all recoverable changes.
which probably occurred while reading the dynamic log from
Message DFHZN2111, DFHZN2112, or DFHZN2113 may have
temporary storage. The dump can be used to ascertain why
been issued when EXCHANGE LOG NAMES failed.
the log could not be read.
User response: See any related messages for further
Module: DFHSPP
guidance.
Ask the operator of the partner to help resolve the problem,
ASPE and ensure that EXCHANGE LOG NAMES completes
Explanation: A syncpoint rollback command has been issued successfully before synclevel 2 activity is attempted.
but CICS cannot link to DFHDBP (the dynamic backout Module: DFHSPZ
program) from the syncpoint program.
transaction dump. The EXEC CICS HANDLE ABEND

ASPJ • ASP3
User response: The application should have an explicit

ASPJ
syncpoint command coded before the EXEC CICS RETURN. A
Explanation: During CICS synclevel 1 commit, unexpected
syncpoint issued in 'backout required' program state results in
syncpoint message data has been received from the partner
a backout being performed. A subsequent EXEC CICS
system. Local resources and synclevel 2 partners have been
RETURN then completes successfully.
committed, but synclevel 1 function-shipped resource updates
Module: DFHSPP
may have been backed out.
System action: The transaction does not abend. CICS
synclevel 1 commit processing continues, with the aim of ASP1
committing as many synclevel 1 resources as possible. Explanation: An intersystem session failed while a syncpoint
User response: Examine the transaction dump to determine was being taken. In consequence, the transaction is abnormally
why the message data was invalid. It is likely that the error is terminated because the logical unit of work that has updated a
in the remote system. remote database cannot be completed normally.
Module: DFHSPZ System action: The transaction is abnormally terminated with
a CICS transaction dump. The EXEC CICS HANDLE ABEND
command can not handle this abend.
ASPK
User response: None, as a result of this abnormal termination
alone. However, DFHZN2101 may also be produced, which
itself may require some action.
Module: DFHSPZ
be committed. However, an error was detected when the
commit message was sent to a synclevel 1 function shipped ASP2
resource. Explanation: A syncpoint has been attempted with the
System action: A CICS transaction dump is taken, and the intersystem links in an invalid state. This may be because the
local transaction is abended after committing as many syncpoint protocol for transaction to transaction has been
synclevel 1 partners as possible. violated by failing to be in send mode for all sessions for
User response: Examine the CSMT message queue and look which syncpoint has not been received.
for messages DFHZN2131, DFHZN2132 or DFHZN2133. These System action: The task is abnormally terminated with a
provide more information about the error. CICS transaction dump which includes terminal control
Module: DFHSPZ information. In particular, the dump contains state information
for the links used by this transaction. The EXEC CICS
HANDLE ABEND command cannot handle this abend.
ASPL
User response: Ensure that all applications are in the correct
Explanation: An error occurred while CICS was writing
state on all conversations before issuing the syncpoint. If this
syncpoint information to the system log. The syncpoint may
fails, you need further assistance to resolve the problem. See
represent either a user syncpoint or the end of the transaction.
how to proceed.
a CICS transaction dump. The EXEC CICS HANDLE ABEND
Module: DFHSPZ
command can not handle this abend.
User response: Use the dump to ascertain why the log record
could not be written correctly. ASP3
Problem determination: At the time of the abend, the journal Explanation: The abnormal termination occurs because a
error return code is in the JCA, field JCAJCRC. The JCA is remote system on which the unit of work depends fails to take
addressed by TCAJCAAD. a syncpoint. The transaction cannot commit its changes until
Analysis: DFHSPP tests the return code from the journal all coupled systems to which function has been transmitted
control program following a logging operation during also commit. This may be because the syncpoint protocol for
syncpoint processing. If an error has occurred, DFHSPP transaction to transaction has been violated by failing to be in
abends with code ASPL. send mode for all sessions for which syncpoint has not been
Module: DFHSPP received.
CICS transaction dump. The EXEC CICS HANDLE ABEND
ASPM command can not handle this abend.
Explanation: An internal logic error has occurred in DFHSPP User response: Run enquiries to discover whether or not
due to an unexpected response from a resource manager. This remote database changes were successfully backed out. If they
abend code is usually accompanied by DFHRM0101. were, retry the transaction. If they were not, take user-defined
System action: CICS terminates the transaction with a system action to resynchronize the local and remote databases.
dump.
Check why the remote system failed to respond to the request.
User response: Keep the dump. Refer to message
If any database changes on the remote system were
DFHRM0101 for further guidance.
successfully backed out, the transaction may be retried; failing
Module: DFHSPP
which, application-dependent procedures must be taken to
ensure resynchronization of the databases on both systems.
ASPN Problem determination: Register 12 addresses the current
Explanation: A transaction has issued an EXEC CICS TCA. Register 3 addresses the remote system TCTTE. The
RETURN in backout required program state. The backout terminal control operation request byte TCATPOS1 indicates
required program state is set when an application receives or the nature of the request being made to the remote system. Its
issues an abend, or receives a backout request on a protected possible values are:
conversation. TCATPPRP (X’01’) - Prepare request
System action: CICS terminates the transaction with a TCATPSPR (X’02’) - SPR request
transaction dump.

ASP4 • ASRD
The request response code byte TCATPAPR gives the response User response: This abend is caused by a prior problem: for
from the remote system: example, the resource manager cannot flush its buffers
X’00’ - operation successful because of an I/O error, or it cannot communicate with CICS
X’0C’ - session failure because of a TP failure. Correct the earlier problem.
other - remote system error Module: DFHSPP
Analysis: ASP8
Register Label Description Explanation: The transaction requested syncpoint rollback,
but was using a type of processing for which syncpoint
R3=@TCTTE SPIS340 In response to a prepare rollback is not supported.
R12=@TCA request either a remote System action: The task is abnormally terminated with a
system error occurred, CICS transaction dump. The EXEC CICS HANDLE ABEND
or no SPR was received. command cannot handle this abend.
User response: This error is either an application error or a
R3=@TCTTE SPIS453
An SPR request was sent, configuration error. Some communication sessions, (for
R12=@TCA but a remote system error
example, LU6.1) do not support syncpoint rollback, and if
occurred.
CICS detects such a session during rollback processing, the
Module: DFHSPP, DFHSPZ
task is abended. This restriction is described in the CICS
Intercommunication Guide. To resolve the problem, either:
ASP4 v Change the application so that it does not issue syncpoint
Explanation: A resource manager involved in syncpoint rollback commands while the non-supporting sessions are
protocols has replied 'backed out' to a single phase commit allocated, or
request. A non-CICS resource manager communicating v Change the configuration so that either APPC or MRO
through a task related user exit can drive this abend. sessions are used for communication. These are the only
two session types which support syncpoint rollback.
This abend is caused by a prior problem, namely the resource Module: DFHSPZ
manager being forced to back out updates made in this logical
Unit of work (LUW). An example is a loss of communication
between CICS and the resource manager at the time of ASP9
syncpoint. Explanation: An attempt to free a TCTTE owned by this task
System action: CICS terminates the task abnormally with a failed.
CICS transaction dump. The EXEC CICS HANDLE ABEND System action: The task is abnormally terminated with a
command cannot handle this abend. CICS transaction dump. The EXEC CICS HANDLE ABEND
User response: Determine what caused the resource manager command cannot handle this abend.
thread to terminate abnormally and back out. User response: You need further assistance from IBM to
Module: DFHSPP resolve this problem. See Part 4 of the CICS Problem
Module: DFHSPP, DFHSPZ
ASP5
Explanation: The task does not own its principal facility.
System action: The task is abnormally terminated with a ASRA
CICS transaction dump. The EXEC CICS HANDLE ABEND Explanation: The task has terminated abnormally because of
command cannot handle this abend. a program check.
User response: You need further assistance from IBM to System action: The task is abnormally terminated and CICS
resolve this problem. See Part 4 of the CICS Problem issues either message DFHAP0001 or DFHSR0001. Message
Determination Guide for guidance on how to proceed. DFHSR0622 may also be issued.
Module: DFHSPZ User response: Refer to the description of the associated
message or messages to determine and correct the cause of the
program check.
ASP6 Module: DFHSRP
Explanation: An unsuccessful attempt was made to flush out
data that was waiting to be shipped to the system that owns
the terminal that is the principal facility of this task. ASRB
System action: The task is abnormally terminated with a Explanation: An operating system abend has occurred and
CICS transaction dump. The EXEC CICS HANDLE ABEND CICS has been able to abend the current transaction.
command cannot handle this abend. System action: The task is abnormally terminated and CICS
User response: You need further assistance from IBM to issues either message DFHAP0001 or DFHSR0001
resolve this problem. See Part 4 of the CICS Problem User response: Refer to the description of the associated
Determination Guide for guidance on how to proceed. message to determine the cause of the original operating
Module: DFHSPZ system abend, and take the necessary corrective action.
Module: DFHSRP
ASP7
Explanation: A resource manager involved in syncpoint ASRD
protocols has replied 'No' to a request to 'Prepare'. A non-CICS Explanation: The task has been abnormally terminated for
resource manager communicating through a task related user one of these reasons:
exit can drive this abend. v A program contains an assembler macro call which is no
System action: CICS terminates the task abnormally with a longer supported by CICS.
CICS transaction dump. The EXEC CICS HANDLE ABEND
command cannot handle this abend.

ASRK • ATCE
v An invalid attempt has been made to access the CSA or Problem determination: A transaction dump is provided
TCA. This abend could be caused by an attempt to address with this abend. In the dump, register 12 addresses the current
the CSA through DOS/VS COBOL BLL cells. For example: TCA, and register 10 and the field TCAFCAAA address the
TCTTE associated with this task. In TCATPOS2, bit
When an DOS/VS COBOL program is invoked by CICS,
TCATPOWR (X'01') indicates that a write is requested by the
CICS inserts the address of the fetch-protected dummy CSA
DFHTC macro, and bit TCATPORR (X'10') indicates that a
into the first of the application-managed BLL cells. If an
read is requested. In TCTTEOS, bit TCTTEOWR (X'01')
attempt is made to access this storage before the application
indicates that a write is in progress, and bit TCTTEORR (X'10')
has reinitialized the BLL cell, abend ASRD will occur. indicates that a read is in progress.
v A non-assembler program has been wrongly defined to
CICS as an assembler program. Analysis:
This error appears as a program check.
System action: The task is abnormally terminated and CICS R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byte
issues message DFHSR0618, followed by either DFHAP0001 or R12=@TCA (TCZAQ1W) TCATPOS2, and bit TCTTEOWR
DFHSR0001. is on in byte TCTTEOS.
User response: Refer to the description of the associated
messages to determine and correct the error. R10=@TCTTE TCZARQ05 Bit TCATPOWR is on in byte
R12=@TCA (TCZAQ2W) TCATPOS2, and bit TCTTEORR
It is likely that either R12 which usually addresses the TCA or is on in byte TCTTEOS.
R13 which usually addresses the CSA is pointing to an area of
storage that you are not allowed to access. R10=@TCTTE TCZARQ12 Bit TCATPORR is on in byte
R12=@TCA TCATPOS2, and bit TCTTEORR
For more information about DOS/VS COBOL BLL cells and is on in byte TCTTEOS.
associated problems, see the CICS Problem Determination Guide. Module: DFHZARQ
Module: DFHSRP
ATCC
ASRK Explanation: An application program, using a pipeline
Explanation: The AP domain recovery stub, DFHSR1, has session, has either issued more than one write request or
been invoked to deal with a program check, operating system issued a read request.
abend, or another error within a transaction environment. System action: The transaction is abnormally terminated with
However, DFHSR1 has been unable to call the system recovery a CICS transaction dump.
program, DFHSRP, because register 12, which should be User response: Correct the application program so that it will
pointing to the task control area (TCA), is null. This indicates not issue more than one consecutive WRITE to a pipeline
that the caller of DFHSR1, has not set the address of the TCA.. session terminal.
System action: The task is abnormally terminated with a Module: DFHZARQ
resolve this problem. See Part 4 of the CICS Problem ATCD
Determination Guide for guidance on how to proceed. Explanation: This abend code is used whenever a CTYPE
Module: DFHSR1 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
ATCA
when the CICS system is not at a level to support APPC.
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 abnormally
User response: Correct the transaction so that it does not
terminated with a CICS transaction dump.
issue a CTYPE macro instruction if VTAM is not generated
into the system, or include the ZCP function for which the
Module: DFHZARQ
CTYPE or QUEUE request was issued.
Module: DFHZDSP, DFHZERH
ATCB
Explanation: The CICS application program issued two
ATCE
consecutive DFHTC writes or two consecutive DFHTC reads,
Explanation: A CICS application program has issued a
but in either case did not issue an intervening wait.
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.
User response: Take corrective action within the program
being executed.
This is almost certainly an application program error. User response: Correct the error in the user program by
Determine the flow of control through the application and ensuring that a terminal input/output area (TIOA) is provided
determine why an intervening wait is not issued. The trace at write time.
table may be useful to discover where the application is
This is almost certainly an application program error.
issuing the read and write requests. If necessary, start trace or
Determine the flow of control through the application and
auxiliary trace using the master terminal command and rerun
determine why a TIOA has not been specified.
the transaction to obtain a trace. The output of the auxiliary
Problem determination: A transaction dump is provided
trace can be printed using the trace utility program,
with this abend. In the dump, register 12 addresses the current
DFHTU410.
TCA, and register 10 and the field TCAFCAAA addresses the

ATCF • ATCJ
TCTTE associated with this task. Register 8 and TCTTEDA

ATCH
should contain the address of the TIOA to be used in the I/O
Explanation: The task was purged before a domain call was
request, but actually they contain zero. For a 3270 data stream
able to complete successfully. The task that first detected the
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.
purged either as a result of a purge from the master terminal
Analysis: operator via the CEMT transaction, or by the task being timed
R10=@TCTTE TCZARQ41 NIOABAR (register 8) If the master terminal operator purged the task, this may have
contains zero. been in an attempt to clear the system which appeared to be
R8=0 Register 8 has been loaded
field TCTTEDA of the TCTTE
associated with this task. If the task was timed out automatically as a result of the
Module: DFHZARQ DTIMOUT value being exceeded, this may be due to
ATCF
Explanation: A DFHTC CTYPE macro was issued to a short-on-storage situations. Another possibility is to increase
non-VTAM terminal control table terminal entry (TCTTE), or a the value of the DTIMOUT option for the transaction.
DFHTC CTYPE=COMMAND or RESPONSE macro was issued Module: DFHBSM62 DFHBSS DFHBSSZ DFHBSTZ
to a VTAM 3270 TCTTE. DFHBSTZV DFHBSTZ1 DFHBSTZ2 DFHTBSB DFHTBSBP
System action: The transaction is abnormally terminated with DFHTBSD DFHTBSDP DFHTBSL DFHTBSLP DFHTBSQ
a CICS transaction dump. DFHTBSR DFHTBSRP DFHTBSSP DFHTCRP DFHTOASE
User response: Ensure that the program issues CTYPE DFHTOATM DFHTOLCR DFHTOLUI DFHTRZCP DFHTRZIP
macros to VTAM terminals only, and does not issue DFHTRZPP DFHTRZXP DFHTRZYP DFHTRZZP
CTYPE=COMMAND or RESPONSE to a VTAM 3270. DFHZCQCH DFHZCQDL DFHZCQIQ DFHZCQIS
Module: DFHZCRQ DFHZCQRS DFHZCQ00 DFHTCBP DFHDLBP DFHFCBP
DFHUSBP
ATCG
Explanation: A CICS application program has issued a ATCJ
DFHTC request for a terminal that it does not own. The Explanation: This abend is issued by DFHZATA in the
problem of ownership may be because the task previously following circumstances:
issued a WRITE,LAST request (which would have detached v Transaction CATA is issued from a terminal
the terminal from that task) or because the task incorrectly v The address of the AWE (TCAFCAAA) is 0
specified the terminal to which the request is directed. v The AWE is invalid (TCTWETYP should be TCTTEAWE)
System action: The transaction is abnormally terminated with v An abend is issued early in DFHZATA.
a CICS transaction dump. This abend is issued by DFHZATD in the following
User response: This is most probably an application error circumstances:
(unless storage has been completely overwritten). Determine v Transaction CATD is issued from a terminal
the flow from the trace table and when a request to the v The address of the AWE (TCAFCAAA) is 0
DFHZCP detach routine, DFHZDET, or a DFHTC v TCAFCAAA is an AWE and not a terminal
WRITE,LAST was issued. v An abend is issued early in DFHZATD.
TCA and register 10 contains the address of the TCTTE. The This abend is issued by DFHZATR in the following
address of the TCTTE was obtained either from TCAFCAAA circumstances:
in the case of a non-ISC transaction, or from TCATPTA if bit v Transaction CATR is issued from a terminal
TCATPTTA (X'40') is on in byte TCATPOC3 (this indicates that v An abend is issued early in DFHZATD.
TERM=YES was specified on the DFHTC request and that this System action: CICS rejects the request.
is an ISC transaction). In the TCTTE thus located, the field User response: Determine the issuing program and the
TCTTECA does not contain the address of the TCA, indicating reason for the abend and take the appropriate action as
that this TCA is not owned by this task. follows:
Analysis: A DFHTC request has been issued specifying a Do not try to invoke CATA, CATD or CATR from a terminal.
TCTTE in which the field TCTTECA does not contain the
If the address in TCAFCAAA is incorrect, the calling
address of the TCA.
mechanism has failed. This is a CICS logic error.
If an abend has been issued, use the transaction dump to
R10=@TCTTE TCZARQ05 TCTTECA is not equal determine where the abend occurred. This is a CICS logic
to register 12. error.
Module: DFHZARQ Module: DFHZATA DFHZATD DFHZATR

ATCK • ATCO
Possible response codes are:

ATCK
Explanation: An application program has issued a WRITE to X’01’ - IDERROR - Journal identification error
a VTAM terminal specifying CCOMPL=NO without being X’02’ - INVREQ - Invalid request
authorized to do so. X’03’ - STATERR - Status error
System action: The transaction is abnormally terminated with X’05’ - NOTOPEN - Journal not open
User response: Specify CHAINCONTROL in the transaction
profile.
Module: DFHZARQ Analysis:
ATCL For DFHZSYN:
Explanation: An error has occurred either during automatic R4=@JCA TCZSYNS4 JCAJCRC is nonzero
journaling or automatic logging of terminal messages to or indicating that a journal
from this transaction. The message being logged will be one error has occurred.
associated with an explicit READ or WRITE in the application For DFHZDWE:
program. R2=@JCA TCZDWE03 As above
System action: The transaction is abnormally terminated with Module: DFHZDWE, DFHZSYN
User response: Use the dump to ascertain why the journal or
log record could not be written correctly. If a journal record ATCN
length error is indicated, TIOATDL may have been corrupted. Explanation: An error has occurred during the automatic
Problem determination: Register 12 addresses the current journaling or automatic logging of the initial input message of
TCA and field TCAJCAAD and register 4 address the JCA. this transaction. This input message is the message that
The journal control request is contained in JCATR2 and the actually caused the transaction to be invoked.
response code is in JCAJCRC. System action: The transaction is abnormally terminated with
Possible request codes are: User response: Use the dump to ascertain why the log record
X’8001’ - WRITE could not be written correctly. For a guide to analyzing the
X’8003’ - PUT dump, see abend code ATCM.
If a journal record length error is indicated, TIOATDL (X'08')
Possible response codes are: may have been corrupted.
X’01’ - IDERROR - Journal identification error Problem determination: Register 12 addresses the current
X’02’ - INVREQ - Invalid request TCA and field TCAJCAAD and register 4 address the JCA.
X’03’ - STATERR - Status error The journal control request is contained in JCATR2 and the
X’05’ - NOTOPEN - Journal not open response code is in JCAJCRC.
X’07’ - IOERROR - I/O error. Possible request codes are:
X’8001’ - WRITE
The address of the TIOA is contained in register 8 and its data X’8003’ - PUT
length is in TIOATDL.
Analysis: X’01’ - IDERROR - Journal identification error
Register Label Description X’02’ - INVREQ - Invalid request
X’03’ - STATERR - Status error
R4=@JCA TCZARQPJ JCAJCRC is nonzero. X’05’ - NOTOPEN - Journal not open
Module: DFHETL, DFHTCPCM, DFHZARQ
ATCM Analysis:
Explanation: An error has occurred while writing syncpoint Register Label Description
information for the terminal associated with this transaction
on the CICS system log. The syncpoint may represent either a R4=@JCA TCZARQJP JCAJCRC is nonzero.
user syncpoint or the end of the transaction. TCZSUPJW Journal error.
System action: The transaction is abnormally terminated with Module: DFHZSUP
could not be written correctly. This may be a CICS system ATCO
problem. Explanation: An application program has attempted to
Problem determination: Register 12 addresses the current perform a function not supported by a terminal or system.
TCA and field TCAJCAAD and register 4 address the JCA. Possible errors are:
The journal control request is contained in JCATR2 and the 1. SIGNAL not supported.
response code is in JCAJCRC.
A DFHTC TYPE=SIGNAL request with the WAIT=YES
Possible request codes are: option was issued to a VTAM logical unit that CICS does
X’8001’ - WRITE not support for the receipt of the SIGNAL indicator.
X’8003’ - PUT 2. WRITE STRUCTURED FIELD not supported.

ATCP • ATCS
This write may have been attempted as a result of a SEND TCA. TCACCSV1 contains a saved copy of TCATSTR
command with the STRFIELD keyword to a device that containing the temporary storage response code. The
does not support this function. temporary storage response code may be one of:
3. APPC mapped conversation not supported. X’04’ - IOERROR - I/O error
The application has attempted to perform a normal X’08’ - NOSPACE - No temporary storage space
terminal control command on a session that is in use for X’20’ - INVREQ - Invalid request.
an APPC unmapped conversation. (Only EXEC CICS GDS
commands are permitted.) The temporary storage identification is constructed by
System action: The transaction is abnormally terminated with concatenating the character string “DFHQ” with the terminal
a CICS transaction dump. identification from TCTTETI. The temporary storage
User response: Correct the application program. identification is placed in TCATSDI.
Module: DFHZARQ
Register 8 and field TCTTEDA address the TIOA that is being
written to temporary storage. The address passed to
ATCP
temporary storage is that of TIOATDL.
Explanation: DFHJCP detected an error while attempting a
PUT request when a response to a protected message has been
received. This PUT request would log that a positive response Analysis: After the DFHTS TYPE=PUTQ, the temporary
has been received. storage response code was not zero.
System action: The CSLG response-logging transaction is Register Label Description
abnormally terminated with a CICS transaction dump. It is
subsequently reattached and, if possible, the log record is then R12=@TCA ZRAQ60 TCATSTR is nonzero.
written. Module: DFHZRAQ
could not be written correctly.
ATCR
Problem determination: The journal control request is
Explanation: An application program has issued a read
contained in JCATR2 and the response code is in JCAJCRC.
operation, after a previous write operation has caused
Possible request codes are: DFHZCP to read-ahead data from the terminal in order to
avoid a lock-out. DFHZCP has now issued a DFHTS GETQ to
X’8001’ - WRITE
X’8003’ - PUT retrieve the saved data from temporary storage, and an error
has occurred.
X’01’ - IDERROR - Journal identification error User response: Determine the cause of the temporary storage
X’02’ - INVREQ - Invalid request error and correct it.
X’03’ - STATERR - Status error
X’05’ - NOTOPEN - Journal not open If a temporary storage identification error is indicated,
X’06’ - LERROR - Journal record length error examine TCTTETI for a valid terminal identification.
X’07’ - IOERROR - I/O error. Problem determination: Register 12 addresses the current
TCA. TCACCSV1 contains a saved copy of TCATSTR that
Analysis: contains the temporary storage response code. The temporary
Register Label Description storage response code may be one of:
X’01’ - ENERROR - Entry error
R2=@JCA TCZRLG30 JCAJCRC is nonzero indicating X’02’ - IDERROR - Identification error
that a journal error has X’04’ - IOERROR - I/O error
occurred. X’20’ - INVREQ - Invalid request
Module: DFHZRLG
The temporary storage identification is constructed by
ATCQ concatenating the character string “DFHQ” with the terminal
Explanation: The application program issued a write identification from TCTTETI. The temporary storage
operation to a terminal that was in send status. In order to identification is placed in TCATSDI.
allow this write to proceed, a signal command was sent, and
DFHZCP started to read data from the terminal waiting for Analysis: After the DFHTS TYPE=GETQ, the temporary
the change direction indication. As each data record is storage response code was not zero.
received, it is placed on temporary storage and, for one of Register Label Description
these operations, a temporary storage error has occurred.
System action: The transaction is abnormally terminated with R12=@TCA ZRAR90 TCATSTR is not zero.
a CICS transaction dump. Module: DFHZRAR
User response: Check that temporary storage has been
included in the system and that it has sufficient space.
ATCS
If an invalid request is indicated, check that the length of the Explanation: An application program attempted to send data
data being written to temporary storage is not greater than the to a logical unit after a SIGNAL data flow command with an
VSAM control interval size minus 84. The length of the data is RCD (request change direction) has been received. This
in TIOATDL (which is 8 greater than the length of the data condition arises when the application handles the IGREQCD
that is read in by DFHZCP). exceptional condition incorrectly.

ATCT • ATCV
System action: The transaction is abnormally terminated with The application program has attempted an operation on a
a CICS transaction dump. logical unit that is invalid, because the program's current
User response: Handle the IGREQCD exceptional condition status on the session with that logical unit does not permit it.
correctly. An investigation of the TCTTE (that is, Session), status bytes,
Module: DFHZARQ and TCA type of request bytes will reveal which of the above
problems are relevant.
ATCT
When the cause of the problem has been ascertained, the
Explanation: An attempt to build a surrogate TCTTE to
application program should be changed to ensure that the
represent a remotely-owned terminal failed.
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
Module: DFHZSUP
in the order shown, and acted upon, before any further
operations are attempted on the session. In addition, the status
ATCU information bytes themselves are necessarily volatile in that
Explanation: An application program attempted to send data they are reset before the execution of every EXEC CICS
to a logical unit, but was in receive mode (EIBRECV is set), statement. Thus it is good programming practice to save them
and read-ahead queuing was not specified in installed profile into application user storage after a RECEIVE, CONVERSE, or
definition (RAQ=NO). RETRIEVE for later testing. The states are:
System action: The transaction is abnormally terminated with 1. EIBSYNC
a CICS transaction dump. the application must take a syncpoint
User response: Either change the application program to 2. EIBFREE
issue receives until EIBRECV is not set, or specify RAQ=YES the application must free the session (or terminate
in the installed profile definition (If RAQ=YES is specified, when the session will be freed automatically)
ensure that all input messages are read before the transaction 3. EIBRECV
is terminated.) the application must continue receiving data by
Module: DFHZARQ issuing further RECEIVE commands; by definition,
data cannot be sent while in this state.
ATCV Some of these status tests can sometimes be omitted (for

Explanation: An application attempted an operation on a example, testing of the EIBSYNC status is not essential if it is
logical unit, but was not in the correct mode for one of the
known that the application program on the remote system
following reasons:
never issues sync point requests itself). However, the tests
1. When issued by DFHZARQ, CICS cannot perform the
should always be carried out, particularly if the remote
current request because another request is outstanding
application might be amended at a future date, in which event
(EIBSYNC is set). This holds for APPC or non-APPC
the session handling logic may well be altered. Also, it may be
systems
that the remote transaction itself causes an unsuspected flow
2. When issued by DFHETL, the application is
on the session. For example, if the remote program issues
communicating with an APPC system, and is not in the
EXEC CICS SEND..... LAST across the session, followed by
correct state to perform the attempted operation. This
RETURN, a syncpoint request (RQD2) will be added onto the
holds for APPC systems only
transmitted data. (The application programmer is referred to
3. When issued by DFHZISP, a TCTTE free was requested,
the CICS Distributed Transaction Programming Guide for a full
and there is an outstanding sync point request. This holds
discussion of this topic). As a result of this addition, an
for non-APPC systems only
unsuspected syncpoint request is received by the local
4. When issued by DFHZISP, a TCTTE free was requested,
application, which abend if the session is freed without the
the TCTTE is in receive mode, and RAQ=NO was specified
sync point request being honored.
in the installed profile definition. This holds for non-APPC
systems only.
System action: The transaction is abnormally terminated with Note: An ATCV abend is also raised by module DFHETL if a
a CICS transaction dump. state error occurs during processing of an APPC mapped
User response: The response depends on the reason for the application (that is, the program attempts to perform an
error as follows: operation while in the wrong state). The handling of APPC
1. Issue a sync point and then issue the request. mapped applications is described in the CICS Diagnosis
2. Issue the free request and reallocate the session. Reference. Some commands are processed by DFHZARQ, as
3. Either change the application to issue receives until above, and others by various other modules invoked by
EIBRECV is not set, or specify RAQ=YES in the installed DFHETL. Rules for using commands for APPC are given in
profile definition. (If you specify RAQ=YES in the installed the CICS Distributed Transaction Programming Guide, and
profile definition, ensure that all input messages are read reference to this Guide should reveal the programming error.
before the transaction is terminated.) Problem determination: Register 12 addresses the current
4. See the CICS Distributed Transaction Programming Guide, TCA. Register 10 and field TCAFCAAA address TCTTE. The
where rules for the correct use of commands are given. terminal byte TCTTECRE has bit TCTEUCOM (X'02') set if
Then correct the application. 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

ATCW • ATC4
TCTESRAQ (X'80') in byte TCTEIRAQ indicates that If the inbound FMH is from a system with an earlier release of
read-ahead queuing is coded on the installed profile definition CICS then you may need to set USEDFLTUSER. See 'Attach
for this transaction. Time Security and the USEDFLTUSER option' in the CICS
RACF Security Guide for further information.
The type-of-request bits in the TCA are set as follows: Module: DFHZARQ, DFHZSUP
v TCATPOS1 TCATPIS (X'01') Signal requested.
– TCATPFRE (X'03') Free TCTTE.
v TCATPOS2 TCATPORR (X'10') Receive requested. ATCZ
– TCATPOWR (X'01') Send requested. Explanation: An error (INVALID, DISASTER or EXCEPTION
response) has occurred on the SET_NETWORK_IDENTIFIER
call to the security domain as part of opening the CICS VTAM
Analysis:
ACB (for example, EXEC CICS SET VTAM OPEN or CEMT
Number Label Description SET VTAM OPEN). The domain that detected the original
error provides an exception trace, a console message, and
DFHZARQ depending on the options specified in the dump table, a
1. TCZAQW8 Attempting to receive system dump.
when sync point or Free
Session outstanding.
2. TCZAQ2W Attempting to send while CICS transaction dump. The VTAM ACB is closed.
in receive mode. User response: Use the dump, the trace and the console
3. ZARQNOPG Issuing SIGNAL while in message to diagnose and correct the original error. Retry the
send mode. command when the earlier error is resolved.
Module: DFHZSLS
DFHZISP
4. ZISPVTCKAttempting to free session
while sync point request is ATC1
outstanding. Explanation: The CICS terminal control restart task could not
Module: DFHETL, DFHZARQ, DFHZISP complete because a necessary step failed. The task has done
some essential recovery operations and abnormally terminated
itself with code ATC1.
ATCW System action: CICS writes a transaction dump for the
Explanation: The system has been generated without an terminal control restart task.
installed profile definition for an LU6.1 or APPC session.
System action: The transaction is abnormally terminated with CICS sends two messages to the console, one to identify the
a CICS transaction dump. error detected by the terminal control restart task, and one,
User response: Notify the system programmer of the error. DFHTC1001, to say that the task has failed. A third message
Module: DFHZSUP 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
ATCX messages from some other system component (for example, an
Explanation: An error (INVALID, DISASTER, or unexpected access method).
EXCEPTION response) has occurred on a call to the storage User response: First, if CICS has requested a response, you
manager (SM) domain. The domain that detected the original must reply. If you reply ‘GO’, CICS continues processing, but
error provides an exception trace, a console message and, without terminal control. If you reply ‘CANCEL’, CICS
possibly, a system dump (depending on the options specified terminates abnormally with a dump.
in the dump table).
Use the messages and dumps to find out the cause of the
An application program that issues terminal control requests failure.
after an ATCX abend may cause further problems. Module: DFHTCRP
User response: See the related message produced by the ATC2
domain that detected the original error. Explanation: A CICS SET VTAM OPEN command has failed
Module: DFHBSMIR, DFHBSMPP, DFHBSM62, DFHBSS, due to VTAM rejecting a CICS request.
DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ, DFHBSTZB, System action: The explanatory message DFH2302, DFH2304
DFHBSTZO, DFHBSTZR, DFHBSTZV, DFHBSTZ1, or DFH2307 is sent to the console, and CICS terminates the
DFHBSTZ2, DFHBSZZS, DFHAPRT, DFHCRP, DFHQRY, transaction abnormally with a transaction dump.
DFHTCBP, DFHDLBP, DFHFCBP, DFHUSBP, DFHZARL, User response: The RPL with the VTAM request code and
DFHZARQ, DFHZERH, DFHZGET, DFHZFRE, DFHZNAC, return code can be found in the RA pool addressed from
DFHZRVS, DFHZSUP, DFHZTSP, DFHZXST TCTVRVRA. Use section "VTAM codes" in z/VSE Messages and
Codes - Volume 2 to determine the cause of the error and the
actions necessary to correct it. After correcting the error, either
ATCY retry the request or terminate CICS and restart the network in
Explanation: An error has occurred during the processing of your own time.
an inbound function management header (FMH). Either a Module: DFHZSLS
length error has been detected, for example, incomplete FMH
received, or an invalid field has been detected within the
FMH. ATC4
System action: The transaction is abnormally terminated with Explanation: A serious CAVM error has occurred. The XRF
a CICS transaction dump. TCB has abended.
User response: Notify the system programmer of the error. System action: CICS abnormally terminates with a system
The problem is probably in the remote system that has sent dump.
the invalid FMH. User response: Use the dump and the guidance in any

ATC5 • ATDI
messages issued by other system components to diagnose and Module: DFHETL

correct the original error.
See the CICS Problem Determination Guide for further guidance ATC9
on using system dumps. Explanation: A DFHKC RESUME macro call has been issued
Module: DFHTCRP for a task without first issuing DFHKC SUSPEND. DFHKC
RESUME must be preceded by DFHKC SUSPEND.
ATC5 System action: The transaction is abnormally terminated with
Explanation: An internal logic error has been detected during a transaction dump.
APPC mapped processing. The conversation state maintained User response: Examine the trace entry to locate the error.
by DFHZARL does not match the state which is jointly Module: DFHZNCE
maintained by DFHETL and DFHZARM.
This problem could also arise when CICS is receiving ATDD
application data. CICS may receive and end of chain Explanation: The transaction attempted to access a transient
notification before receiving all the data expected. data destination that is disabled. (The master terminal
System action: The task is abnormally terminated with a operator can control the status of the destination.)
CICS transaction dump. CICS processing continues.
User response: You need further assistance from IBM to This abend cannot be issued by this release of CICS. It can
resolve this problem. See Part 4 of the CICS Problem only be issued by a connected CICS system.
Module: DFHETL a CICS transaction dump.
User response: Check with the master terminal operator why
the destination is disabled.
ATC6 Module: DFHTDP
Explanation: DFHETL has a SEND DATA request with a data
length greater than 65 528 bytes which is the maximum that it
can process. ATDI
System action: The transaction is abnormally terminated with Explanation: DFHTDP does not support the type of
a CICS transaction dump. destination that is indicated by the DCT entry for the
User response: This is a CICS internal logic error. You need requested destination. Either DFHTDP has been assembled
further assistance from IBM to resolve this problem. See Part 4 without support for this destination type, or the DCT entry
of the CICS Problem Determination Guide for guidance on how had been overwritten. Valid types are X'10' (remote), X'20'
to proceed. (indirect), X'40' (extrapartition), and X'80' (intrapartition).
Module: DFHETL
Note: This abend cannot be issued by this release of CICS. It
ATC7 can only be issued by a connected CICS system.
Explanation: DFHZSUP has detected a bad response from an System action: The transaction is abnormally terminated with
INITIAL-CALL request to DFHZARL. This response is a CICS transaction dump.
returned to DFHZSUP in the DFHLUC parameter list. User response: Determine the destination type by looking at
System action: The transaction is abnormally terminated with the DCT assembly listing. If the type is indirect, follow the
a CICS transaction dump. destination pointed to until a non-indirect destination is
User response: Examine field LUCCDRCD in the DFHLUC found. Check that DFHTDP has been generated with support
parameter list. This appears in the ENTRY/EXIT trace points for that destination type.
for DFHZARL. If trace is switched off, then it can be found in
DFHZSUP's LIFO entry in the transaction dump. Determine the destination type by looking at the DCT
v LUCCDRCD = 'A0000100' - session failure assembly listing. If the type is indirect, follow the chain of
v LUCCDRCD = 'A0010100' - read timeout indirect destinations until a non-indirect destination is found.
v LUCCDRCD = 'A0010000' - deadlock timeout. Check that DFHTDP has been generated with support for that
destination type.
(The offset for LUCCDRCD can be found in CICS Data Areas).
If it is suspected that the DCT entry has been overwritten,
If LUCCDRCD is X'00000000', the error is the result of a examine the trace table to find a recent execution of a
connection failure. In this case examine the CSMT log for transaction that might have overwritten the DCT entry. If
further diagnostic information. necessary, restart CICS and use trace or auxiliary trace to
Module: DFHZSUP obtain a sufficiently large trace table. The auxiliary trace data
set may be printed using the DFHTU410 trace utility program.
ATC8 Reproduce the error and use the master terminal command to
Explanation: An error has occurred during the processing of take a snap dump (CEMT PERFORM SNAP). Examine the
an inbound function management header (FMH). Either a DCT in the dump and try to identify the code in error from
length error has been detected, for example, incomplete FMH the data overwriting the DCT entry.
received, or an invalid field has been detected within the Problem determination: This abend is issued at only one
FMH. place in DFHTDP, following label TDEATR. A transaction
System action: The transaction is abnormally terminated with dump is provided. In the dump, register 12 addresses the TCA
a CICS transaction dump. and register 13 the CSA. Register 3 addresses the DCT entry
User response: Notify the system programmer of the error. (which is not printed in a transaction dump). The destination
The problem is probably in the remote system that has sent ID is in TCATDDI.
the invalid FMH.

ATDL
is indicated, an irrecoverable I/O error has occurred on output

R3=@DCT entry to the journal data set and this is indicated by message
DFHJC4513 sent to the operator’s console.
TDDCTDT contains the destination type: Problem determination: When this abend is issued, the CSA
TDEXTRBM (X’40’) - extrapartition
is addressed by register 13 and the TCA of the abending
TDINDTBM (X’80’) - intrapartition
TDINDBM (X’20’) - indirect transaction is addressed by register 12.
TDRMTBM (X’10’) - remote The abend occurs in module DFHTDP on encountering an
TDDCTIDI contains the address of the DCT entry abnormal response from DFHJCP for a DFHJC TYPE=PUT
of the indirect destination if bit request. The condition is detected at one place in DFHTDP, in
TDINDBM is set in field TDDCTDT. routine TDPRLR, which issues the journal request and abends
if NORESP is not returned.
Analysis: The destination type is always tested for remote. Relevant fields in the JCA are:
Abend AISM is issued if the type is remote, because remote
JCATR1 Request type byte 1 X’03’ PUT.
requests are permitted only at the command level, which does
not invoke DFHTDP locally. JCAJCRC Response byte (see under Analysis
for abnormal response codes).
The destination type is tested for intrapartition only if
DFHTDP contains support for intrapartition destinations, and JCAJRTID Journal record type ID (2 bytes)
for extrapartition only if DFHTDP contains support for (Copybook DFHFMIDS defines the
codes).
extrapartition destinations. For indirect destinations, the
address at TDDCTIDI is followed and the appropriate tests are Set Byte Value Value Function
performed on the final target destination. If the destination near symbol
type is not one of those for which a test is made, the ATDI label
abend is issued.
TDGLRAF 1 FIDTDPRL X’83’ QZERO detecting
while getting
TDPIEI 1 FIDTDPGT X’82’ GET
R3=@DCT TDIDER TDDCTDT does not contain any of
TDWDBL 1 FIDTDPLP X’81’ first PUT
entry the bits TDEXTRBM
TDPGRAE 1 FIDTDPLG X’84’ PURGE
(extrapartition type), TDINDTBM
TDPRLR 2 MODIDTD X’12’ identifies TDP
(intrapartition type), TDRMTBM
(remote type, or TDINDBM
JCAJFID Journal file ID byte
(indirect type), which this
(system log = X’01’)
version of DFHTDP tests for.
Module: DFHTDP JCAECN Event control number (4 bytes)
JCALDATA Length of DCT entry = X’0054’

ATDL (2 bytes)
Explanation: An error was detected by journaling, which was
called by DFHTDP to log a DCT entry image to support JCAADATA Address of DCT entry
recovery of an intrapartition queue with physical recovery
(DESTRCV=PH on DFHDCT macro). This abend can occur The log routine TDPRLR in DFHTDP will have been called
only when DFHTDP has intrapartition and recovery support, from one of four places in DFHTDP. Register 9 is the link
and the destination in the DFHTD request has physical register to this routine.
recovery specified.
This abend cannot be issued by this release of CICS. It can Information about the original transient data request can be
only be issued by a connected CICS system. found in the trace table. At the time of the abend, register 3 is
System action: The transaction is abnormally terminated with addressing the DCT entry for the associated queue. However,
a CICS transaction dump. the DCT entry is not printed in the transaction dump.
could not be written correctly. Analysis: Determine the abnormal response code from the
journal control request by examining the JCA in the
If the abnormal response code in the JCA indicates a possible
transaction dump.
error in the JCT, for example, IDERROR or LERROR, check
that the JCT entry for the system log is both present and Register Label Description
correct. If NOTOPEN is indicated, this may be for one of
R8=@JCA JCAJCRC = X’01’ IDERROR Journal ID not
several reasons, the most likely being (1) that
in JCT
OPEN=DEFERRED was specified in the JCT entry for the X’02’ INVREQ Invalid request
system log and no attempt has been made by the user to open type
the data set during execution by issuing a DFHJC X’05’ NOTOPEN Journal not
TYPE=OPEN macro, or (2) that OPEN=INITIAL was in effect available
but a DFHJC TYPE=CLOSE macro has been issued X’06’ LERROR Record length
subsequently against the journal. The trace table may help in error
establishing why the journal file has become unavailable. X’07’ IOERROR Output I/O
error
If either INVREQ or LERROR is indicated and the JCT entry Module: DFHTDP
for the journal appears to be correct, suspect either a storage
overwrite or a problem in DFHTDP or DFHJCP. If IOERROR

ATDT • ATMB
ATDT ATD4
Explanation: The transient data program DFHTDP has found Explanation: An error (INVALID, DISASTER or unexpected
an invalid request code in field TCATDTR. EXCEPTION response) has occurred on a call to the storage
error will have provided an exception trace, a console
Note: This abend cannot be issued by this release of CICS. It
message, and possibly, a system dump(depending on the
can only be issued by a connected CICS system.
options specified in the dump table).
User response: Check the application program for a valid User response: See the related message from the domain that
transient data request at the point of request. Also, check detected the original error.
whether DFHTDP was generated with the options required to Module: DFHTDP
support the service requested.
Module: DFHTDP
ATFE
Explanation: A FREEMAIN request to the storage manager
ATDY has failed while CICS was executing a CEDA CHECK or
Explanation: Transient data initialization has failed. A console CEDA INSTALL command.
message, DFH12xx, gives the reason for the failure. System action: CICS abnormally terminates the task with a
System action: Transient data initialization terminates transaction dump.
abnormally. This abend is always followed by an ATDZ abend User response: Use the dump and any associated messages
for the failing function, and by message DFHSI1521 (if CICS issued by the storage manager to investigate the FREEMAIN
abends unconditionally), or message DFHSI1522, which failure.
prompts you to reply GO or CANCEL. Module: DFHTOUT1
User response: See the associated console message for
information regarding the cause of the failure. Then respond
ATGE
to message DFHSI1522, if it has been issued.
Explanation: A GETMAIN request to the storage manager
Module: DFHTDRP
has failed while CICS was executing a CEDA CHECK or
CEDA INSTALL command.
ATDZ System action: CICS abnormally terminates the task with a
Explanation: A CICS function invoked by transient data transaction dump.
initialization has failed. If the failing function is a transient User response: Use the dump and any associated messages
data routine, this abend is preceded by a console message and issued by the storage manager to investigate the GETMAIN
an ATDY abend. failure.
System action: Transient data initialization terminates Module: DFHTOUT1
abnormally. This abend is always followed by message
DFHSI1521 (if CICS abends unconditionally), or message ATMA
DFHSI1522, which asks you to reply GO or CANCEL. Explanation: The task was purged before a GETMAIN
User response: Refer to the associated console message for request to the storage manager (SM) domain was able to
further information regarding the cause of the failure. Then complete successfully. The domain that first detected the
respond to message DFHSI1522, if it has been issued. purged condition will have provided an exception trace.
Module: DFHTDP, DFHTDRP System action: The task is abnormally terminated with a
ATD3 User response: Investigate why the task was purged. It was
Explanation: The task was purged before a GETMAIN purged either as a result of a purge from the master terminal
request to storage manager (SM) domain was able to complete operator via the CEMT transaction, or by the task being timed
successfully. domain that first detected the purged condition out after waiting for longer than the DTIMOUT (deadlock
provides an exception trace. timeout) value specified for the transaction.
System action: The task is abnormally terminated with a If the master terminal operator purged the task, this may have
CICS transaction dump. been in an attempt to clear the system which appeared to be
User response: Investigate why the task was purged. This is deadlocked for some reason.
via the CEMT transaction, or by the task being timed out after If the task was timed out automatically as a result of the
waiting for longer than the DTIMOUT (deadlock timeout) DTIMOUT value being exceeded, this may be due to
value specified for the transaction. insufficient main storage being available for the number of
If the master terminal operator purged the task, this may have increased, reduce the number of tasks in the system to avoid
been in an attempt to clear the system which appeared to be short-on-storage situations. Another possibility is to increase
deadlocked for some reason. the value of the DTIMOUT option for the transaction.
If the task was timed out automatically as a result of the Module: DFHTMP
insufficient main storage being available for the number of ATMB
tasks in the system. If the amount of main storage cannot be Explanation: An error (INVALID, DISASTER or unexpected
increased, reduce the number of tasks in the system to avoid EXCEPTION response) has occurred on a call to the storage
short-on-storage situations. Another possibility is to increase manager (SM) domain. The domain that detected the original
the value of the DTIMOUT option for the transaction. error will have provided an exception trace, a console message
Module: DFHTDP

ATNA • ATOF
and, possibly, a system dump (depending on the options match the attributes of the actual device.
specified in the dump table). Module: DFHZARL, DFHZARM, DFHZARQ, DFHZRAQ,
System action: The task is abnormally terminated with a DFHZSUP
detected the original error. ATOA
Module: DFHTMP Explanation: You have attempted to invoke the CESC
transaction with a terminal as principal facility. This is not
allowed.
ATNA System action: CICS terminates the CESC transaction. No
Explanation: A terminal operator entered the transaction dump is produced.
identification for NACP. User response: Ensure that the CESC transaction is not run
System action: The transaction is abnormally terminated with against a terminal.
a CICS transaction dump. Module: DFHCESC
User response: Do not reenter the NACP transaction
identification (CSNE).
Module: DFHZNAC ATOB
Explanation: CICS has received an abnormal response from
an EXEC CICS START TRANSACTION(CESC) request. This is
ATND caused by an internal error.
Explanation: The node error program (NEP) or NACP System action: CICS terminates the CESC transaction with a
decides that a task should abnormally terminate, but the task dump.
is at a critical point of processing and immediate termination User response: You need further assistance from IBM to
would put the integrity of the system at risk. resolve this problem. See Part 4 of the CICS Problem
CICS transaction dump when the task next requests any action Module: DFHCESC
against the terminal, or issues a sync point request involving
the terminal.
User response: Check destination CSMT for possible further ATOC
information. Use the dump to determine why the task was Explanation: CICS has received an abnormal response from a
abnormally terminated by NEP. request to DFHZCUT to timeout a local userid table (LUIT).
Module: DFHZARQ, DFHZARL, DFHZSUP This is caused by an internal error in DFHZCUT.
System action: CICS terminates the CESC transaction with a
dump.
ATNI User response: You need further assistance from IBM to
Explanation: There are two forms of this abend: resolve this problem. See Part 4 of the CICS Problem
VTAM form Determination Guide for guidance on how to proceed.
The node error program (NEP) or NACP decides the Module: DFHCESC
task should be abnormally terminated. DFHZNAC
informs the request module to abend the transaction
after the TC unit has completed. ATOD
Non-VTAM form Explanation: CICS has received an abnormal response from
The terminal error program (TEP) or terminal an EXEC CICS CANCEL TRANSACTION(CESC) request.
System action: CICS terminates the CESC transaction with a
abnormal condition program (TACP) decides the
dump.
task should be abnormally terminated. DFHTACP
informs DFHZARQ to abend the transaction after
the TC unit has completed.
System action: The task is abnormally terminated with a Module: DFHCESC
User response: This usually occurs when, due to a hardware
failure, a network device rejects the data stream sent to it. The ATOE
device itself may indicate an error code that will give a Explanation: CICS cannot determine the time at which an
specific reason for the rejection. Check the CSMT log for XRF takeover began.
further information. System action: CICS terminates the CESC transaction with a
dump.
This abend can also result from an error in a connected system User response: You need further assistance from IBM to
such as a mirror transaction abend. resolve this problem. See Part 4 of the CICS Problem
Abend ATNI can occur if a user application does not correctly
Module: DFHCESC
handle an error return code from an external resource
manager, such as DB2®.
ATOF
For the NEP (VTAM) form, run a VTAM trace type=BUF for
Explanation: CICS has received an abnormal response from
the logical unit and repeat the error.
an EXEC CICS DELAY TRANSACTION(CESC) request.
For the TEP (non-VTAM) form, run a link trace for the line or System action: CICS terminates the CESC transaction with a
local channel address for the device. dump.
Examine the data stream and error response to determine the resolve this problem. See Part 4 of the CICS Problem
cause of the error. Determination Guide for guidance on how to proceed.
Module: DFHCESC
This type of error occurs if the definitions in the TCT do not

ATOG • ATPE
ATOG ATPA
Explanation: CICS has received an abnormal response from Explanation: An error occurred when trying to estimate the
an EXEC CICS START TRANSACTION(CEGN) request. This length of a CICS message owned by the message domain.
is caused by an internal error. System action: CICS terminates the transaction with a dump.
System action: CICS terminates the CEGN transaction with a User response: You need further assistance from IBM to
dump. resolve this problem. See Part 4 of the CICS Problem
resolve this problem. See Part 4 of the CICS Problem Module: DFHTPR.
Module: DFHCESC
ATPB
Explanation: An error occurred when trying to retrieve a
ATOH CICS message from the message domain.
Explanation: An attempt has been made to invoke the CESC System action: CICS terminates the transaction with a dump.
transaction with an invalid function code. The CESC User response: You need further assistance from IBM to
transaction should only be invoked by CICS. Valid codes are resolve this problem. See Part 4 of the CICS Problem
TERM_TIMEOUT, XRF_TIMEOUT, and ENABLE_TIMEOUT. Determination Guide for guidance on how to proceed.
Module: DFHTPR.
The most likely cause of this error is an invalid attempt by a
user to invoke CESC.
System action: CICS terminates the CESC transaction with a ATPC
transaction dump. Explanation: An error occurred when trying to estimate the
User response: Determine how CESC was invoked. If it was length of a CICS message owned by the message domain.
invoked by CICS, you will need further assistance from IBM System action: CICS terminates the transaction with a dump.
to resolve this problem. See Part 4 of the CICS Problem User response: You need further assistance from IBM to
Determination Guide for guidance on how to proceed. resolve this problem. See Part 4 of the CICS Problem
Module: DFHCESC Determination Guide for guidance on how to proceed.
Module: DFHTPQ.
ATOT
Explanation: An error has occurred in the invocation of the ATPD
CEGN transaction. CEGN has issued an EXEC CICS Explanation: An error occurred when trying to retrieve a
RETRIEVE command to retrieve the CEGN parameter list. CICS message from the message domain.
Either the EXEC CICS RETRIEVE command has failed or it System action: CICS terminates the transaction with a dump.
has succeeded but the retrieved data is invalid. User response: You need further assistance from IBM to
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
Module: DFHTPQ.
EXEC CICS START request).
System action: CICS terminates the CEGN transaction with a
transaction dump. ATPE
User response: Determine how CEGN was invoked. If it was Explanation: The task was purged before a GETMAIN
invoked by CICS, you will need further assistance from IBM request to the storage manager (SM) domain was able to
to resolve this problem. See Part 4 of the CICS Problem complete successfully. The task that first detected the purged
Determination Guide for guidance on how to proceed. condition will have provided an exception trace.
Module: DFHCEGN System action: The task is abnormally terminated with a
ATOU
purged either as a result of a purge from the master terminal
Explanation: The CEGN transaction has attempted to issue
an EXEC CICS RETURN but the command has failed.
System action: CICS terminates the transaction with a dump.
resolve this problem. See Part 4 of the CICS Problem If the master terminal operator purged the task, this may have
Determination Guide for guidance on how to proceed. been in an attempt to clear the system which appeared to be
Module: DFHCEGN deadlocked for some reason.
ATOV DTIMOUT value being exceeded, this may be due to
Explanation: The CEGN transaction has attempted to issue insufficient main storage being available for the number of
an EXEC CICS GETMAIN, ASSIGN, or SEND but the tasks in the system. If the amount of main storage cannot be
command has failed. increased, reduce the number of tasks in the system to avoid
System action: CICS terminates the transaction with a dump. short-on-storage situations. Another possibility is to increase
User response: You need further assistance from IBM to the value of the DTIMOUT option for the transaction.
resolve this problem. See Part 4 of the CICS Problem Module: DFHTPQ, DFHTPR.
Module: DFHCEGN

ATPF • ATSL
ATPF ATSC
Explanation: An error (INVALID, DISASTER, or unexpected Explanation: The task was canceled during execution of a
EXCEPTION response) has occurred on a call to the storage temporary storage command.
manager (SM) domain. The domain that detected the original System action: The transaction is abnormally terminated with
error will have provided an exception trace, a console message a CICS transaction dump.
and, possibly, a system dump (depending on the options User response: Investigate the reason the task was canceled.
specified in the dump table). The task has been canceled by the master terminal operator or
System action: The task is abnormally terminated with a automatically by either the deadlock timeout (DTIMEOUT)
CICS transaction dump. mechanism or the read timeout (RTIMOUT) mechanism.
User response: See the related message produced by the Module: DFHTSP
Module: DFHTPQ, DFHTPR.
ATSD
Explanation: An INVALID or DISASTER response was
ATRA received from a request to the Dispatcher (DS) Domain.
Explanation: The field engineering global trap exit program, System action: The transaction is terminated with a CICS
DFHTRAP, requested task abnormal termination. However, the transaction dump.
currently active task was not a system task (for example, User response: There has been an earlier failure which lead
journal control or task dispatcher) and it was not about to to the response from DS. Investigate the earlier failure (which
abend. is accompanied by a console message and a system dump).
System action: CICS disables the trap exit so that it will not Module: DFHTSP
be reentered, and terminates the currently active task
abnormally.
User response: This is a user-requested task abend. ATSL
Explanation: An error was detected by journaling, which was
If you want to use the trap again, you must reactivate it as called by DFHTSP to log a before-image of updated data to
follows: support recovery of temporary storage data having an
identifier defined as recoverable in the TST with a DFHTST
CSFE DEBUG,TRAP=ON
TYPE=RECOVERY macro.
You should use the global trap exit only in consultation with System action: The transaction is abnormally terminated with
an IBM support representative. a CICS transaction dump.
Module: DFHTRP User response: Notify the system programmer of the error.
The dump can be used to ascertain why the log record could
not be written correctly.
ATSA
Explanation: The CICS temporary storage restart task could If the abnormal response code in the JCA indicates a possible
not complete because a necessary step failed. The task has error in the JCT, for example, IDERROR or LERROR, check
done some essential recovery operations and abnormally that the JCT entry for the system log is both present and
terminates itself with code ATSA. correct. If NOTOPEN is indicated, this may be for one of
System action: CICS writes a transaction dump for the several reasons, the most likely being (1) that
temporary storage restart task. OPEN=DEFERRED was specified in the JCT entry for the
journal file and no attempt has been made by the user to open
CICS sends two messages to the console, one to identify the the data set during execution by issuing a DFHJC
error detected by the temporary storage restart task, and one, TYPE=OPEN macro, or (2) that OPEN=INITIAL was in effect
DFHTS1313, to say that temporary storage restart has failed. A but a DFHJC TYPE=CLOSE macro has been issued
third message follows either to say that CICS has terminated subsequently against the journal. The trace table may help in
abnormally with a dump, or to ask you to reply GO or establishing why the journal file has become unavailable.
CANCEL. Depending on the nature of the original error, you
may see messages from some other system component (for If either INVREQ or LERROR is indicated and the JCT entry
example, VSE). for the journal appears to be correct, suspect a problem in
User response: First, if CICS has requested a response, you DFHTSP or even DFHJCP. If IOERROR is indicated, an
must reply. If you reply 'GO', CICS continues processing, but unrecoverable I/O error has occurred on output to the journal
without support for temporary storage. If you reply data set and this is indicated by message DFHJC4513.
'CANCEL', CICS terminates abnormally with a dump. Problem determination: When this abend is issued, the CSA
is addressed by register 13 and the TCA of the abending
Use the messages and dumps to find out the cause of the transaction is addressed by register 12.
failure.
Module: DFHTSRP The abend occurs in module DFHTSP on encountering an
abnormal response from DFHJCP to a DFHJC TYPE=PUT
request. The condition is detected at one place in DFHTSP,
ATSB after label TSP178, where the journal request is issued, and the
Explanation: An attempt to use temporary storage has failed abend occurs if NORESP is not returned.
because the temporary storage restart task failed.
System action: The transaction trying to use temporary Relevant fields in the JCA are:
storage terminates abnormally with a CICS transaction dump. JCATR1 Request type byte 1 X’03’ PUT
User response: Temporary storage restart has failed with JCAJCRC Response byte (see under Analysis
abend ATSA and associated DFH messages. See the for abnormal response codes)
description of that code for guidance in solving the temporary JCAJRTID Journal record type ID (2 bytes).
storage problem. Copybook DFHMIDS defines the codes.
Module: DFHTSP Expected value is X’C013’
(TSP update log)
JCAJFID Journal file ID byte (X’01’ for

ATSP • AWBA
system log) User response: Identify the failing temporary storage request
JCAECN Event control number (4 bytes) in the application and verify whether the length supplied on
JCALDATA Length of data (2 bytes) the request agrees with the data area size. Correct the
JCAADATA Address of data application as appropriate.
A simple way of finding the point of invocation of journal Note: If the error occurs in DFHTSP and not in DFHETS,
control from DFHTSP is by scanning the CICS trace table for there is probably an internal logic error in temporary storage.
the trace entry corresponding to the last journal control In this case you will need further assistance from IBM. See
request from the current transaction. Part 4 of the CICS Problem Determination Guide for guidance on
how to proceed.
Information about the original temporary storage request can Module: DFHTSP, DFHETS
be found in the TCA at locations TCATSTR and TCACCSV1
or, alternatively, from the trace table.
ATST
Explanation: An unexpected error was returned from a
Analysis: Determine the abnormal response code from the DFHTSUT subroutine call. The DFHTSUT subroutine is used
journal control request by examining the JCA in the to maintain a directory of the temporary storage queues in the
transaction dump. system. The error was detected when adding, deleting, or
Register Label Description locating an entry in the directory.
R1=@JCA TSP178 JCAJCRC=X’01’ IDERROR a transaction dump.
(journal ID not User response: You need further assistance from IBM to
in JCT) resolve this problem. See Part 4 of the CICS Problem
JCAJCRC=X’02’ INVREQ
Module: DFHTSP
(invalid request
type)
ATSU
JCAJCRC=X’05’ NOTOPEN
Explanation: An I/O error occurred while a task was
(journal not
available) attempting to write to the temporary storage data set during
syncpoint processing.
JCAJCRC=X’06’ LERROR System action: The transaction is abnormally terminated with
(record length a transaction dump. Messages DFHTS1301 and DFHME0116
error) may also be written to the console.
User response: This could be a hardware error or a case of
JCAJCRC=X’07’ IOERROR the volume assigned to the temporary storage data set being
(output I/O offline. Either correct the hardware error or put the volume
error) back online.
Module: DFHTSP Module: DFHTSP
ATSP AUEP
Explanation: A task issued a PUT or a PUTQ request to a Explanation: The task has been abnormally terminated
recoverable temporary storage data identification (DATAID) because a return code of UERCPURG has been sent to the
and either: User Exit Handler by a User Exit Program. The value of
1. The DATAID is currently in use as a symbolic reference to UERCPURG is defined by the macro DFHUEXIT TYPE=EP,
a single unit of temporary storage data, or ID=xxxxxxxx, where xxxxxxxx is the exit point by which the
2. The task previously issued a PURGE of the data referenced exit program is enabled. This code does not apply to exit
by this DATAID and has not synchronized. points in domains. The exit program returns this value when
System action: The task is abnormally terminated with a it has made a request for CICS services using the exit
CICS transaction dump. programming Interface (XPI) and when the XPI call has had a
User response: Depending on the cause of the abend (see RESPONSE code of PURGED. Exit programs must not set
Explanation), either: UERCPURG return code under any other circumstance.
1. Correct the application to avoid issuing multiple PUT
requests to the same recoverable DATAID, or
User response: Refer to the CICS Customization Guide for the
2. Correct the application to avoid issuing a PUT(Q) request
use of this return code.
to a recoverable DATAID in a logical unit of work in
Module: DFHUEH
which that DATAID has already been PURGED.
Module: DFHTSP
AWBA
Explanation: CICS Web Receive process has received an
ATSQ exception response from the Web Send Receive function,
Explanation: A move of data to or from temporary storage DFHWBSR, which could be one of the following errors:
has failed. The probable reason is that the size of the area v An error in the Analyzer program
being passed to CICS is inconsistent with the data length v No Analyzer program specified
being used. v Unable to link to Analyzer program
v An Analyzer data length error
a CICS transaction dump. If the abend occurs in DFHTSP, a
v An Analyzer header length error
CICS system dump is taken and message DFHTS1379 is
v A codepage conversion error
issued to the CICS console.

AWBB • AWBQ
v A storage error occurred

AWBH
v An error that the connection has been closed
Explanation: The CICS Web Interface alias detected a logic
v A sockets receive error.
error.
System action: An error message is sent to the client and the
System action: An exception trace entry 454F is written.
CWBO transient data queue.
Message DFHWB0106 is written to the CWBO destination. A
User response: Refer to any error messages accompanying
CICS transaction dump is taken.
this abend to determine why the abend has occurred.
User response: Use related diagnostics to determine the user
Module: DFHWBXN
response.
Module: DFHWBA
AWBB
Explanation: The incoming parameter list to the CICS Web
AWBI
Business Logic Interface program is not in the expected
Explanation: The CICS Web Interface alias received an
format. At present, the structure is assumed to be fixed and
unexpected response from EXEC CICS ASSIGN STARTCODE
only a single version level is recognized.
System action: Message DFHWB0102 is written to the CWBO
System action: The CICS Web Business Logic Interface
destination.
program is not executed.
User response: Ensure that the program receives a parameter
list in the correct format.
Module: DFHWBBLI
Module: DFHWBA
AWBC
AWBK
Explanation: No commarea was passed to a CICS Web
Explanation: The CICS Web Interface alias detected an abend
Interface utility program. One of the utility programs supplied
in the converter or the CICS program servicing the request.
with the CICS Web Interface was executed, but the commarea
System action: An exception trace entry 4550 is written.
that was passed was absent or was too short to contain valid
Message DFHWB0108 is written to the CWBO destination.
information.
User response: Use related diagnostics to determine the user
System action: The CICS Web Interface utility is not
response.
executed.
Module: DFHWBA
User response: Ensure that the program passes a commarea
that is long enough to contain the expected parameters for the
utility you are invoking. AWBL
Module: DFHWBENV, DFHWBTL Explanation: The CICS Web Interface alias detected an error
in an EXEC CICS LINK command for program DFHWBBLI.
System action: An exception trace entry 4543 is written.
AWBE
Message DFHWB0100 is written to the CWBO destination. A
Explanation: The CICS Web Interface detected that a
transaction dump is taken.
Converter program attempted to change the address of the
User response: See the associated message for guidance.
response buffer when it was not allowed to do so.
Module: DFHWBA
System action: The data in the new response buffer is not
returned to the Web browser. A CICS transaction dump is
taken. AWBM
User response: The Converter program is only allowed to Explanation: The CICS Web Interface alias detected an error
replace the response buffer if the converter_volatile flag in the response from the Business Logic Interface program
Converter parameter list is set to '1'. Check that your DFHWBBLI.
Converter program is not trying to return a new response System action: Message DFHWB0101 is written to the CWBO
buffer when this flag is set to '0'. destination. A transaction dump is taken.
Module: DFHWBBLI User response: See the associated message for guidance.
Module: DFHWBA
AWBF
Explanation: The CICS Web Interface alias detected an error AWBQ
in its initialization. The alias was not started by EXEC CICS Explanation: The CICS Web Business Logic Interface program
START, or there was an error in the EXEC CICS RETRIEVE detected an error in its parameter list.
command for the start data. System action: If the abend was issued from the Business
System action: If there is an error in EXEC CICS RETRIEVE, Logic Interface program, DFHWBBLI, an exception trace entry
message DFHWB0103 is written to the CWBO destination. A '4581' is made and message DFHWB0119 is written to the
CICS transaction dump is taken. CWBO transient data destination. If the abend was issued
User response: If the alias was not started by EXEC CICS from the Web Interface program, DFHWBA1, an exception
START, check if it is being started from a terminal. This is not trace entry '4560' is written and message DFHWB0124 is sent
allowed. Otherwise, see the associated message for guidance. to the CWBO destination. A transaction dump is taken.
Module: DFHWBA User response: See the associated message for guidance.
Module: DFHWBA1, DFHWBBLI

AWBR • AWC6
Module: DFHWBGB
AWBR
Explanation: The CICS Web Business Logic Interface program
detected a logic error. AWC1
System action: If the abend was issued from the Business Explanation: The CICS Web Interface 3270 bridge exit
Logic Interface program, DFHWBBLI, an exception trace entry DFHWBLT could not establish a partnership with the Web
'4583' is made and message DFHWB0118 is written to the terminal translation task which started the abended
CWBO transient data destination. If the abend was issued transaction.
from the Web Interface program, DFHWBA1, an exception System action: An exception trace entry 4106 is written, and
trace entry '4558' is written and message DFHWB0123 is sent message DFHWB0131 is issued.
to the CWBO destination. User response: Use related diagnostics to determine the user
User response: Use related diagnostics to determine the user response.
response. Module: DFHWBLT
Module: DFHWBA1, DFHWBBLI
AWC2
AWB2 Explanation: The CICS Web Interface 3270 bridge exit
Explanation: The CICS Web Interface has encountered an DFHWBLT was passed an invalid state token by attach
error while performing a transaction attach call for the alias processing.
task. System action: An exception trace entry 410C is written, and
System action: Message DFHWB0727 describing the error is message DFHWB0130 is issued.
written to the CWBO transient data destination and a trace User response: Use related diagnostics to determine the user
entry code '451C' is made. response. On a busy CICS region, the most likely cause is that
User response: See the associated message for guidance. the bridged transaction started after the state data had been
Module: DFHWBXN discarded by Web 3270 garbage collection process.
Module: DFHWBLT
AWB3
Explanation: CICS Web transaction, CWXN, has been AWC3
illegally started either with data, or by a user at a terminal, Explanation: An application using the CICS Web 3270
with the wrong start code. function issued an unsupported combination of BMS and
System action: The CICS Web Interface is not started. Terminal Control commands.
User response: CICS Web Transaction Execution should only System action: An exception trace entry is written.
ever be started by Sockets Domain using DFHXMAT User response: Use related diagnostics to determine the user
ATTACH, not by a user at a terminal or with data. response.
Module: DFHWBXN Module: DFHWBLT
AWB4 AWC4
Explanation: The CICS Web Transaction Execution has Explanation: The CICS Web Interface 3270 bridge exit
received a bad response from an INQUIRE_TRANSACTION DFHWBLT has been reinvoked after returning an earlier error.
call to determine the start code for the CWXN transaction. System action: An exception trace entry is written.
System action: The CICS Web Interface is not started. User response: Use related diagnostics to determine the user
User response: CICS Web Transaction Execution should only response.
ever be started by Sockets Domain using DFHXMAT Module: DFHWBLT
ATTACH, not by a user at a terminal or with data.
Module: DFHWBXN
AWC5
Explanation: The CICS Web Interface 3270 bridge exit
AWB7 DFHWBLT abended during attach processing because it could
Explanation: The CICS Web Interface environment variables not getmain a brxa user area.
program was invoked, but the invoking transaction does not System action: Message DFHWB0132 is issued, and an
appear to be executing in a valid Web environment. exception trace entry 410D is written.
System action: The transaction is abended. User response: Use related diagnostics to determine the user
User response: Determine how the environment variables response. The most likely cause of this abend is that CICS is
program was invoked. It is only meaningful to execute the having storage problems.
program from a transaction that has been initiated from the Module: DFHWBLT
Web, either through the CICS Web Interface or through the
Business Logic Interface.
Module: DFHWBENV AWC6
Explanation: The CICS Web Interface 3270 bridge exit
DFHWBLT has detected an inconsistency in its request
AWB8 parameters or state data.
Explanation: The CICS Web Interface environment garbage System action: Message DFHWB0133 is issued, and an
collection task CWBG has been started directly from a exception trace entry is written.
terminal. This is not permitted. User response: Use related diagnostics to determine the user
System action: The transaction is abnormally terminated with response. The most likely cause of this abend is a storage
a transaction dump. overwrite.
User response: None. Module: DFHWBLT

AWC7 • AXFH
AWC7 AXFC
Explanation: CICS detected an error during transaction Explanation: The request passed to the data transformation
initialization for a CICS Web alias transaction. program is unknown to CICS. This abend can also occur in an
System action: Message DFHWB0360 is issued. No MRO/IRC system as a result of an invalid EXEC CICS START
transaction dump is taken for this abend. request issued from the user’s node error program
User response: Use related diagnostics to determine the user (DFHZNEP).
response. The most likely cause of this abend is an invalid System action: The task is abnormally terminated with a
userid being passed to CICS by the CICS Web Interface CICS transaction dump.
Analyzer user replaceable module. The userid is invalid if: User response: See the CICS Customization Guide for
restrictions on the use of EXEC CICS commands from within
v It is not defined in the external security manager
an NEP. If this is not the cause of the abend, you will need
v It is revoked
v It is not authorized to access this CICS region.
Module: DFHWBXM
Module: DFHXFP
AWC8 AXFD
Explanation: CICS detected an error during transaction Explanation: The request that is passed to the data
initialization for a CICS Web alias transaction. transformation program cannot be sent to a remote system; for
System action: A transaction dump is taken for this abend. example, a storage control request.
User response: Use related diagnostics to determine the user System action: The task is abnormally terminated with a
response. CICS transaction dump.
Module: DFHWBXM User response: You need further assistance from IBM to
AWKY Module: DFHXFP
Explanation: A request to GET, PURGE, or WRITE a record
using the global catalog during warm keypointing has failed.
System action: The task is abnormally terminated with a AXFE
CICS transaction dump. Explanation: The transformation requested does not exist; for
User response: Check for problems with the global or local example, a DL/I schedule reply is not recognized by the
catalog. See any DFHCCnnnn messages issued by the CICS outbound request processor in the data transformation
catalog domain for further guidance. program.
Module: DFHWKP System action: The task is abnormally terminated with a
AWKZ resolve this problem. See Part 4 of the CICS Problem
Explanation: A request to take a keypoint for the automatic Determination Guide for guidance on how to proceed.
AIDs chain has failed. This is caused by a catalog write error. Module: DFHXFP
CICS system dump.
AXFF
User response: Check for problems with the global or local Explanation: An unacceptable queue organization has been
catalog. See any DFHCCnnnn messages issued by the CICS found in a queue model function management header (FMH).
catalog domain for further guidance. System action: The task is abnormally terminated with a
Module: DFHWKP CICS transaction dump.
AXFA
Explanation: The key length for a file control request that is
Module: DFHXFP
to be sent to a remote system has to be obtained from the file
control table, and has proved to be zero.
System action: The task is abnormally terminated with a AXFG
CICS transaction dump. Explanation: An unacceptable argument number has been
User response: Ensure that the key length has been defined found in the data following a function management header
either in the remote file definition that is being used, or as a (FMH) of type 43.
length option from the application program that is using it. System action: The task is abnormally terminated with a
Module: DFHXFP CICS transaction dump.
AXFB
Explanation: An unacceptable function management header
Module: DFHXFP
(FMH) type has been found. It must be type 05, type 06, or
type 43.
System action: The task is abnormally terminated with a AXFH
CICS transaction dump. Explanation: The argument number in the data following a
User response: You need further assistance from IBM to function management header (FMH) of type 43 is acceptable,
resolve this problem. See Part 4 of the CICS Problem however, the argument itself is not expected.

AXFI • AXFU

AXFQ
Explanation: Either the function management header (FMH)
Module: DFHXFP
just received is too short or too long to be a valid FMH, or an
expected FMH is not present.
AXFI System action: The task is abnormally terminated with a
Explanation: The data length for a WRITEQ TD or READQ CICS transaction dump.
TD, which is determined from the destination control table, is User response: Check that the transaction profile parameter,
zero. The abend can also occur when determining the length INBFMH, is set to ALL. If communicating across a distributed
for file control requests from the file control table. program link, ensure that the requested function is supported
System action: The task is abnormally terminated with a on the partner system.
CICS transaction dump. Module: DFHXFP
Module: DFHXFP
AXFR
Explanation: The CICS command level interface imposes a
AXFJ maximum length of 32 767 for data. The length of the data
Explanation: The error code held in UIBFCTR and UIBDLTR just received exceeds this limit.
cannot be converted to an equivalent SNA error code. System action: The task is abnormally terminated with a
CICS transaction dump. User response: Notify the system programmer.
User response: You need further assistance from IBM to Module: DFHXFP
AXFS
Module: DFHXFP
Explanation: A PSB has been scheduled successfully.
However, the maximum possible length of an I/O area
AXFL exceeded 65 535. This abend is likely to occur if path calls are
Explanation: Transformers 2 and 4 expect to receive a used to retrieve large segments, and/or if FLS causes
function management header (FMH), possibly followed by excessive expansion of segments.
user data. A null chain of data has been received. System action: The task is abnormally terminated with a
CICS transaction dump. User response: Notify the system programmer.
User response: You need further assistance from IBM to Module: DFHXFP
AXFT
Module: DFHXFP
Explanation: An estimate of the size of the output I/O area
has been made, and it exceeds the maximum possible size of
AXFM 65 535.
Explanation: The ISCINVREQ condition has been raised. This
can happen when the resource proves to be on yet another Note: While the estimated size may exceed the actual size, the
remote system, that is, when daisy-chaining is active. difference will only be a few bytes.
System action: The task is abnormally terminated with a This abend is likely to occur if a database calls, inserts, or
CICS transaction dump. replaces multiple segments, and many qualified segment
User response: Check that daisy-chaining of requests is search arguments are specified.
intended and that all relevant intersystem links are in service. System action: The task is abnormally terminated with a
AXFO Module: DFHXFP
Explanation: The check on the DS and DBA parameters in an
attach function management header (FMH) has failed. This
AXFU
abend represents a user error resulting from a mismatch in the
Explanation: A two-level cursor is present in a function
system definitions for both ends of an intersystem link.
management header (FMH) relating to a linear (temporary
storage) queue. However, these cursors are valid only for
User response: Notify the system programmer. hierarchical queues that are not supported by CICS.
Module: DFHXFP System action: The task is abnormally terminated with a
AXFP resolve this problem. See Part 4 of the CICS Problem
Explanation: CICS requires a second function management Determination Guide for guidance on how to proceed.
header (FMH) to follow an attach FMH. No second FMH was Module: DFHXFP
received.
Module: DFHXFP

AXFW • AXMA
If the short-on-storage condition persists, consider increasing

AXFW
the size limit of the CICS DSAs. You can vary the DSAs
Explanation: An invalid length specification has been given
dynamically using the DSALIM and EDSALIM parameters on
in a CICS command-level request corresponding to one of the
the CEMT SET DSAS master terminal command.
data variables.
Module: DFHXFP
The CICS-architected FMH is followed by zero or more
self-describing data variables for each parameter specified.
AXF3
Explanation: The storage manager module DFHSMMC has
returned a condition not expected by DFHXFP.
User response: Check for an invalid or zero length specified
in a CICS command-level request, or for data truncation in a
transaction dump.
user-written node error program (NEP).
User response: Look for any related CICS messages and
Module: DFHXFP
abends to determine if there has been a prior failure in CICS
storage.
AXFX Module: DFHXFP
Explanation: A function shipping request by an APPC link
failed.
AXF4
System action: CICS terminates the task abnormally.
Explanation: The task was purged before a GET_BUFFER
User response: Check that the request was directed to the
request to the EXEC interface service routines module
correct remote system, and that the remote system is set up
(DFHEISR), was able to complete successfully. The domain
correctly.
that first detected the purged condition provides an exception
Module: DFHXFP
trace.
AXFY CICS transaction dump.
Explanation: An APPC conversation failure has occurred User response: Investigate why the task was purged. It was
when an attach between CICS systems was issued. purged either as a result of a purge from the master terminal
System action: The task is abnormally terminated with a operator via the CEMT transaction, or by the task being timed
transaction dump. out after waiting for longer than the DTIMOUT (deadlock
User response: Check the connection to the remote CICS timeout) value specified for the transaction.
system and try to reestablish it.
Module: DFHXFP
AXF0
Explanation: The storage manager module DFHSMGF has
returned a purged response due to lack of storage in a
dynamic storage area (DSA).
transaction dump.
User response: Try the transaction again later.
If the short-on-storage condition persists, consider increasing Module: DFHXFX
the size limit of the CICS DSAs. You can vary the DSAs
dynamically using the DSALIM and EDSALIM parameters on
AXF5
the CEMT SET DSAS master terminal command.
Module: DFHXFP
EXCEPTION response) has occurred on a call to the EXEC
interface service routines module(DFHEISR). The domain that
AXF1 detected the original error provides an exception trace, a
Explanation: The storage manager module, DFHSMGF, has console message, and possibly, a system dump (depending on
returned a condition not expected by DFHXFP. the options specified the dump table).
transaction dump. CICS transaction dump.
User response: Look for any related CICS messages and User response: See the related message from the domain that
abends to determine if there has been a prior failure in CICS detected the original error.
storage. Module: DFHXFX
Module: DFHXFP
AXMA
AXF2 Explanation: An error has occurred obtaining a lock within
Explanation: The storage manager module DFHSMMC has the transaction manager domain.
returned a purged response due to lack of storage in a System action: The recovery routine of the module in control
is invoked which issues message DFHXM0002 with a system
dynamic storage area (DSA).
dump. DFHXM0002 reports the module in control at the time
of the error.
transaction dump.
User response: See the description of message DFHXM0002
User response: Try the transaction again later.
for further guidance.
Module: DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD,

AXMB • AXTA
DFHXMFD, DFHXMLD, DFHXMQD, DFHXMST, DFHXMTA, detected by the security control task, and, if the error occurred
DFHXMXD, DFHXMXE 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
AXMB abnormally with a dump, or to ask you to reply GO or
Explanation: An error has occurred releasing a lock within CANCEL. Depending on the nature of the original error, you
the transaction manager domain. may see messages from some other system component (for
System action: The recovery routine of the module in control example, an access method).
is invoked. This routine issues message DFHXM0002 with a User response: First, if CICS has requested a response, you
system dump. DFHXM0002 reports the module in control at must reply. If you reply ‘GO’, CICS continues processing, but
the time of the error. without support for the external security manager. CICS
User response: See the description of message DFHXM0002 security still operates. If you reply ‘CANCEL’, CICS terminates
for further guidance. abnormally with a dump.
Module: DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD,
DFHXMFD, DFHXMLD, DFHXMQD, DFHXMST, DFHXMTA, Use the messages and dumps to find out the cause of the
DFHXMXD, DFHXMXE failure.
Module: DFHXSMN
AXMC
Explanation: An severe error has occurred allocating a AXSC
unique transaction number to a new transaction. Explanation: The task was purged before a GETMAIN
System action: The recovery routine of the module in control request to the storage manager (SM) domain was able to
is invoked. This routine issues message DFHXM0002 with a complete successfully. The task that first detected the purged
system dump. DFHXM0002 reports the module in control at condition will have provided an exception trace.
the time of the error. System action: The task is abnormally terminated with a
User response: See the description of message DFHXM0002 CICS transaction dump.
for further guidance. User response: Investigate why the task was purged. It was
Module: DFHXMAT, DFHXMXE purged either as a result of a purge from the master terminal
AXMD timeout) value specified for the transaction.
Explanation: An attempt has been made to run the CICS
internal task CSXM as a user transaction. If the master terminal operator purged the task, this may have
System action: CICS terminates the task with a transaction been in an attempt to clear the system which appeared to be
dump. deadlocked for some reason.
User response: Investigate why the attempt was made to run If the task was timed out automatically as a result of the
CSXM as a user transaction. DTIMOUT value being exceeded, this may be due to
Module: DFHXMAB insufficient main storage being available for the number of
AXMY increased, reduce the number of tasks in the system to avoid
Explanation: During transaction attach an unexpected error short-on-storage situations. Another possibility is to increase
occurred obtaining transaction class membership. the value of the DTIMOUT option for the transaction.
System action: The transaction is no longer considered for Module: DFHXSMN
class membership. It is then abnormally terminated with a
AXSD
User response: Use the dump to determine why the
transaction failed to obtain membership of its transaction class.
Module: DFHXMAT
AXMZ possibly, a system dump (depending on the options specified
Explanation: A serious failure in another component has in the dump table).
been detected by the transaction manager domain. System action: The task is abnormally terminated with a
System action: The task in control is abnormally terminated CICS transaction dump.
with a transaction dump. Further diagnostics should have User response: See the related message produced by the
been taken by the failing component. domain that detected the original error.
User response: Look for earlier messages identifying the Module: DFHTCRP
source of the problem. Refer to the descriptions of these
messages for further guidance.
AXTA
Module: DFHXMTA
Explanation: The calculation of the length of data to be
shipped has failed.
AXSA System action: The task is abnormally terminated with a
Explanation: The CICS security control task could not CICS transaction dump.
complete because a necessary step failed. The task has done User response: You need further assistance from IBM to
some essential recovery operations and abnormally terminated resolve this problem. See Part 4 of the CICS Problem
itself with code AXSA. Determination Guide for guidance on how to proceed.
System action: CICS writes a transaction dump for the Module: DFHXTP
security control restart task.
CICS sends messages to the console, one to identify the error

AXTB • AXTL
AXTB AXTH
Explanation: An attempt to obtain a TIOA to ship data has Explanation: An attempt to locate terminal identifier failed.
failed. System action: The task is abnormally terminated with a
CICS transaction dump. User response: You need further assistance from IBM to
Determination Guide for guidance on how to proceed. Module: DFHXTP
Module: DFHXTP
AXTI
AXTC Explanation: The major request byte LUCOPN0 of the
Explanation: An attempt to transform data ready for DFHLUC parameter list specified to the transaction-routing
shipment has failed. transformer is invalid, or corresponds to a request that is not
System action: The task is abnormally terminated with a shipped to a remote system. The parameter list will be found
CICS transaction dump. in the dynamic storage of XTP’s caller and may be located
User response: You need further assistance from IBM to using the output from auxiliary trace.
Determination Guide for guidance on how to proceed. transaction dump.
Module: DFHXTP User response: You need further assistance from IBM to
AXTD Module: DFHXTP
Explanation: No TIOA received message was received from a
remote system.
System action: The task is abnormally terminated with a AXTJ
CICS transaction dump. Explanation: An unexpected combination of bit settings in
User response: You need further assistance from IBM to the fields XTSSTAT and XTSTCOPC in the parameter list of
resolve this problem. See Part 4 of the CICS Problem the transaction-routing transformer was made.
Module: DFHXTP transaction dump.
AXTE Determination Guide for guidance on how to proceed.
Explanation: Incorrect data was received from a remote Module: DFHXTP
system. The data was not long enough.
CICS transaction dump. AXTK
User response: You need further assistance from IBM to Explanation: An APPC conversation failure occurred when
resolve this problem. See Part 4 of the CICS Problem an attach between CICS systems was issued.
Module: DFHXTP CICS transaction dump.
User response: Check the connection to the remote CICS
system and try to reestablish it.
AXTF Module: DFHXTP
Explanation: No relay process function management header
(FMH) was received from the remote system.
System action: The task is abnormally terminated with a AXTL
CICS transaction dump. Explanation: The processing of APPC mapped data requires
User response: You need further assistance from IBM to the generation of an APPC attach FMH with default values. In
resolve this problem. See Part 4 of the CICS Problem particular, the sync level requested is defaulted to 2. However,
Determination Guide for guidance on how to proceed. the session that is to be used has been bound with a sync level
Module: DFHXTP of 1.
AXTG User response: Check that:
Explanation: Transformation of data received from remote v The entry in the TCT for the remote system has been
system failed. defined with parallel sessions
System action: The task is abnormally terminated with a v The remote system is capable of supporting a sync level of
CICS transaction dump. 2.
User response: Check that the reason for failure of the
v Exchange lognames has completed for the connection. You
transformation process was not incorrect definition of the
can use the command CEMT INQUIRE CONNECTION to
remote terminal. In particular check that the user area length
do this. See the CICS Intercommunication Guide for more
specified for the terminal is the same in both local and remote
details of the exchange lognames process.
systems. If the terminal definitions are correct, you need
further assistance to resolve this problem. You need further v The correct sync level has been requested.
assistance from IBM to resolve this problem. See Part 4 of the Module: DFHXTP
proceed.
Module: DFHXTP

AXTM • AZAB
the DFHCCNV commarea DFHC32. The client and server

AXTM
codepages will have already been validated so this may be a
Explanation: An attempt has been made to route a
CICS error. You may need to contact IBM for further
message-protected transaction over an APPC link bound at
assistance.
sync level 1. The attempt has failed because such transactions
Module: DFHXTP
can be routed only over an APPC link that has been bound at
sync level 2.
System action: The task is abnormally terminated with a AXTQ
CICS transaction dump. Explanation: An exception response has been returned to the
User response: If the transaction is to be routed to CICS DFHXTP module from DFHCCNV
OS/2 (which is bound at synclevel 1), remove the message FUNCTION(CONVERT_DS3270_FOR_SBCS). The module was
protection option. If the transaction is to be routed to another called for a CICS client virtual terminal which requested
host system and message protection is required, the link must conversion from EBCDIC to ASCII for data to be sent to the
be redefined so that it can be bound at synclevel 2. client. However the conversion failed.
Module: DFHXTP 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
AXTN
CICS security manager issues a DFHSNxxxx message to the
Explanation: Module DFHXTP detected that the application
transient data queue, CSCS.
buffer chained off a TCTTE at offset TCTERCSA has a
User response: Examine the response and reason returned in
corrupted header. This is caused either by a CICS logic error
the DFHCCNV commarea DFHC32. The client and server
or by a storage overwrite.
codepages will have already been validated so this may be a
CICS error. You may need to contact IBM for further
assistance.
User response: This is a CICS internal logic error. You need
Module: DFHXTP
to proceed. AXTR
Module: DFHETL Explanation: An exception response has been returned to the
DFHXTP module from DFHPGLE FUNCTION(LOAD_EXEC)
whilst trying to load EXEC program DFHCCNV.
AXTO
System action: The transaction routing request is terminated
Explanation: An exception response has been returned to the
DFHXTP module from the CICS security manager. Prior to the
indicate that the transaction routing request has failed. 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
User response: Examine the response and reason returned
perform a preset security signon for the userid sent with the
from DFHPGLE to see why CICS was unable to call
shipped terminal information. It is this preset security signon
DFHCCNV.
attempt which failed.
Module: DFHXTP
System action: The transaction routing request is terminated
indicate that the transaction routing request has failed. The AZAA
CICS security manager issues a DFHSNxxxx message to the Explanation: A CICS logic error has occurred when CICS was
transient data queue, CSCS. attempting to flush application deferred data on an APPC
User response: The most likely cause of this abend is that the mapped conversation. Application deferred data does not
terminal being shipped to the application owning region occur for APPC mapped conversations.
(AOR) has preset security with a userid which is not valid in System action: The transaction is abnormally terminated with
the AOR. To confirm this, check the associated DFHSNxxxx a CICS transaction dump.
message on the CSCS transient data queue in the AOR which User response: You need further assistance from IBM to
gives the precise reason for the failure of the preset security resolve this problem. See Part 4 of the CICS Problem
signon request. This could be the result of an unauthorized Determination Guide for guidance on how to proceed.
transaction routing request. Module: DFHZARM
Module: DFHXTP
AZAB
AXTP Explanation: DFHZARM has a SEND DATA request with a
Explanation: An exception response has been returned to the data length greater than 65 528 bytes which is the maximum
DFHXTP module from DFHCCNV that it can process.
FUNCTION(CONVERT_DS3270_FOR_SBCS). The module was System action: The transaction is abnormally terminated with
called for a CICS client virtual terminal which requested a CICS transaction dump.
conversion from ASCII to EBCDIC for data coming from the User response: This is a CICS internal logic error. You need
client. However, the conversion failed. further assistance from IBM to resolve this problem. See Part 4
System action: The transaction routing request is terminated of the CICS Problem Determination Guide for guidance on how
and a message is sent to the terminal owning region (TOR) to to proceed.
indicate that the transaction routing request has failed. The Module: DFHZARM
User response: Examine the response and reason returned in

AZAD • AZCB
AZAD AZAJ
Explanation: DFHZCN1 has been started from an unexpected Explanation: DFHZCN1 was started for transaction CCIN.
place. The CCIN transaction can only be issued by a client. However, the CCIN transaction is being started on a
System action: The transaction is abnormally terminated. surrogate, which means that it has been defined as a remote
Exception trace point AP3008 is written. Data1 holds the transaction. CCIN must be a local transaction and be run on a
XMIQ start type. CICS region which is directly connected to a client.
User response: Only issue the CCIN transaction from a System action: Exception trace point AP3041 is written. The
client. transaction is abnormally terminated.
Module: DFHZCN1 User response: Either use the default definitions for CCIN or
ensure that it is defined as a local transaction.
Module: DFHZCN1
AZAE
Explanation: DFHZCN1 was started from a terminal facility,
but not an LU6.2 session. The CCIN transaction may only be AZAK
issued by a client. Explanation: DFHZCT1 was started for transaction CTIN.
System action: The transaction is abnormally terminated. However, the CTIN transaction is being started on a surrogate,
User response: Only issue the CCIN transaction from a which means that it has been defined as a remote transaction.
client. CTIN must be a local transaction and be run on a CICS region
Module: DFHZCN1 which is directly connected to a client.
System action: Exception trace point AP3039 is written. The
transaction is abnormally terminated.
AZAF User response: Either use the default definitions for CTIN or
Explanation: DFHZCN1 was started for transaction CCIN. ensure that it is defined as a local transaction.
However either the environment is wrong or the client Module: DFHZCT1
architecture has been violated. This abend will always be
issued in conjunction with a DFHZC32xx message which will
explain the problem in more detail. AZCA
System action: Exception trace point AP30xx is written. The Explanation: An internal logic error has been detected during
transaction is abnormally terminated. APPC mapped processing. The conversation state maintained
User response: Look for a DFHZC32xx message on the by DFHZARL does not match that maintained jointly by
console or CSNE and look for exception trace points AP30xx. DFHETL and DFHZARM.
Use these to diagnose the problem.
The problem may also arise when CICS is assembling
Module: DFHZCN1
application data and receives end of chain before receiving all
of the data that is expected.
AZAG System action: The task is abnormally terminated with a
Explanation: DFHZCT1 has been started from an unexpected CICS transaction dump. CICS processing continues.
place. The CTIN transaction can only be issued by a client. User response: You need further assistance from IBM to
a CICS transaction dump. Exception trace point AP302A is Determination Guide for guidance on how to proceed.
written. Data1 holds the XMIQ start type. Module: DFHZARM
User response: Only issue the CTIN transaction from a client.
Module: DFHZCT1
AZCB
Explanation: CICS has received sense code X'088901xx'
AZAH during APPC mapped processing. This should be followed by
Explanation: DFHZCT1 was started from a terminal facility, an error data GDS (generalized data stream) variable.
but not an LU62 session. The CTIN transaction can only be
CICS has attempted to receive the error data. However this
issued by a client.
attempt has failed because no data has been received or
because the data received is not for an CICS ISSUE ERROR of
a CICS transaction dump. Exception trace point AP3032 is
the correct length.
written. Data1 holds the principal facility address.
User response: Only issue the CTIN transaction from a client. CICS expects the error data to indicate that the other system
Module: DFHZCT1 does not recognize GDS ID X'12F2' (function management
data).
AZAI
Explanation: DFHZCT1 was started for transaction CTIN.
However either the environment is wrong or the client The erroneous GDS ID is returned to the remote system for
architecture has been violated. This abend will always be further analysis there.
issued in conjunction with a DFHZC32xx message which will User response: Check for session failure and for abend by
explain the problem in more detail. the transaction in the other system.
System action: Exception trace point AP30xx is written. The
transaction is abnormally terminated. You need further assistance from IBM to resolve this problem.
User response: Look for a DFHZC32xx message on the See Part 4 of the CICS Problem Determination Guide for
console or CSNE and look for exception trace points AP30xx. guidance on how to proceed.
Use these to diagnose the problem. Module: DFHZARM
Module: DFHZCT1

AZCC • AZCL
AZCC AZCH
Explanation: The failing transaction has sent function Explanation: Sense code X'0889xxxx' has been received
management data to a transaction running in a system that unexpectedly during the processing of APPC mapped data.
does not provide support for application function
This represents a violation of the APPC architecture by the
management data. remote system.
User response: Check that the remote system can support User response: You need further assistance from IBM to
application function management data. resolve this problem. See Part 4 of the CICS Problem
Module: DFHZARM Determination Guide for guidance on how to proceed.
Module: DFHETL, DFHZARM
AZCD
Explanation: An intersystem logic error has been detected AZCI
during APPC mapped processing. The length of application Explanation: The processing of APPC mapped data requires
data that is to be received (as determined from the LL fields generation of an APPC attach function management header
and concatenation flags) does not match the length actually (FMH) with default values. In particular, the sync level
received. CICS determines the length of application data that requested is defaulted to 2. However, the session that is to be
is to be received from the LL fields and concatenation flags. used has been bound with a sync level of 1.
However, CICS has not received all of the data that is System action: The task is abnormally terminated with a
expected. CICS transaction dump.
System action: The task is abnormally terminated with a User response: Check that:
CICS transaction dump. v The entry in the TCT for the remote system has been
User response: You need further assistance from IBM to defined with parallel sessions.
resolve this problem. See Part 4 of the CICS Problem v The remote system is capable of supporting a sync level of
Determination Guide for guidance on how to proceed. 2.
Module: DFHETL, DFHZARM v Exchange lognames has completed for the connection. You
can use the CEMT INQUIRE CONNECTION to do this. See
AZCE the CICS Intercommunication Guide for details of the
Explanation: An intersystem error has been detected during exchange lognames process.
APPC mapped processing. The length of application data that Module: DFHETL, DFHZARM, DFHZARQ
is to be received (as determined from the LL fields and
concatenation flags) exceeds the CICS implementation limit of
AZCJ
32 767, for receive and converse commands, or 65 000 for
Explanation: An APPC structured field with GDS ID X'12F1'
CICS transaction routing or function shipping requests.
(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: Reduce the amount of data that the
transaction in the remote system is transmitting to CICS.
Module: DFHETL, DFHZARM
User response: The problem is in the remote system. You
AZCF Part 4 of the CICS Intercommunication Guide for guidance on
Explanation: An internal logic error has been detected during how to proceed.
APPC mapped processing. An invalid request has been passed Module: DFHZARM
to DFHZARL.
AZCK
Explanation: An internal logic error has been detected during
error recovery for APPC mapped processing. The conversation
was being switched to RECEIVE state by an internal CICS
SEND INVITE, but the conversation had already been FREEd
Module: DFHZARM
by the partner.
AZCG CICS transaction dump. CICS processing continues.
Explanation: An internal logic error has been detected during User response: You need further assistance from IBM to
APPC mapped processing. DFHZARM expects the TCTTE resolve this problem. See Part 4 of the CICS Intercommunication
passed to have been defined as APPC, TCTEILUC (TCTELUC) Guide for guidance on how to proceed.
set on, and TCTECVT set to TCTEMAPD (to indicate a Module: DFHZARM
mapped conversation).
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
Module: DFHZARM
by CICS are:

AZCM • AZCT
X’12F1’ null data Guide for guidance on how to proceed.

X’12F2’ function management data Module: DFHZSUP
X’12FF’ application data.
CICS transaction dump. AZCR
User response: Check for session failure and for an abend by Explanation: A logic or protocol error has been detected
the transaction in the other system. during processing of an APPC SYNCPOINT ROLLBACK
Module: DFHZARM 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
AZCM the partner.
EXCEPTION response) has occurred on a call to the storage The problem arises during rollback in one of the following
manager (SM) domain. The domain that detected the original situations:
error provides an exception trace, a console message and, v The saved state is receive, and the partner sent change
possibly, a system dump (depending on the options specified direction on the last flow, indicating that the partner expects
in the dump table). CICS to be in send state
System action: The task is abnormally terminated with a v The saved state is send, and the partner did not send the
CICS transaction dump. change-direction indicator on the last flow, indicating that
User response: See the related message produced by the the partner expects CICS to be in receive state.
domain that detected the original error. System action: The task is abnormally terminated with a
Module: DFHZARM 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,
AZCN analyze the flows at the last successful syncpoint. Try to
Explanation: The task has been purged before a GETMAIN determine the states the two LUs were in at this point. Look at
request to the storage manager (SM) domain was able to the last syncpoint flow into CICS from the partner, before the
complete successfully. The task that first detected the purged abend. From this flow, calculate whether the change-direction
condition provides an exception trace. indicator on the SPCMOD modifier byte is on. ( See the SNA
System action: The task is abnormally terminated with a Formats manual for further information on the SPCMOD
CICS transaction dump. modifier byte.) The indicator must only be set when the saved
User response: Investigate why the task was purged. It was CICS conversation state is send. If the last CICS state was
purged either as a result of a purge from the master terminal send, and the indicator is on, CICS is at fault. Similarly, if the
operator via the CEMT transaction, or by the task being timed last CICS state was receive, and the indicator is off, CICS is at
out after waiting for longer than the DTIMOUT (deadlock fault.
If the last CICS state was send and the indicator is off, or the
If the master terminal operator purged the task, this may have last CICS state was receive, and the indicator is on, CICS has
been in an attempt to clear the system which appeared to be received a change-direction indicator when it was not
deadlocked for some reason. expecting one. In this case, examine the partner for a logic
error.
Module: DFHZARL
tasks in the system. If the amount of main storage cannot be AZCT
increased, reduce the number of tasks in the system to avoid Explanation: A terminal read-time-out condition has been
short-on-storage situations. Another possibility is to increase detected. The transaction has been waiting for a terminal input
the value of the DTIMOUT option for the transaction. message for an interval longer than specified in the RTIMOUT
Module: DFHZARM value for that transaction.
Coding RTIMOUT in the PROFILE entry causes the task to be

AZCO abnormally terminated if the terminal does not send input
Explanation: The VTAM persistent sessions initialization within the specified time.
transaction CGRP has been started directly from a terminal. System action: The transaction is abnormally terminated. A
This is not permitted. This transaction can only be started dump is not provided unless the dump table entry for
internally by CICS. transaction dump code AZCT indicates that one should be
System action: The transaction is abnormally terminated with taken.
a transaction dump. User response: If a DFHPC TYPE=SETEXIT macro has been
User response: None. issued for this task, the read that was timed-out is still
Module: DFHZCGRP outstanding. In order to cancel this read, issue a DFHPC
TYPE=ABEND at the end of the user exit routine so that CICS
can clean up the terminal's TCTTE.
AZCP
Module: DFHZARQ
Explanation: A logic error has been detected in ZCP. An
allocation request for a starting task cannot be satisfied.
resolve this problem. See Part 4 of the CICS Intercommunication

AZCU • AZI1
User response: Please see the related message from the

AZCU
Explanation: The COVR transaction has been started directly
Module: DFHZIS2
from a terminal, or by a START command. This is not
permitted. This transaction can only be started internally by
CICS. AZID
System action: The transaction is abnormally terminated. No Explanation: A PURGED condition has occurred on a call to
transaction dump is taken. the storage manager domain (DFHSMGFM) to FREEMAIN a
User response: None. CRB control block.
Module: DFHZCOVR
exception trace.
AZCV System action: The task is abnormally terminated with a
Explanation: A logic error has been detected in the COVR transaction dump.
transaction while trying to connect to VTAM. User response: Investigate why the task was purged. It was
System action: The task is abnormally terminated with a purged either as a result of a purge from the master terminal
CICS transaction dump. operator via the CEMT transaction, or by the task being timed
User response: You need further assistance from IBM to out after waiting for longer than the DTIMOUT (deadlock
resolve this problem. See Part 4 of the CICS Intercommunication timeout) value specified for the transaction.
Module: DFHZCOVR If the master terminal operator purged the task, this may have
AZCW
Explanation: An attempt has been made to run the CICS If the task was timed out automatically as a result of the
internal task CSTP as a user transaction. DTIMOUT value being exceeded, this may be due to
System action: CICS terminates the task with a transaction insufficient main storage being available for the number of
dump. tasks in the system. If the amount of main storage cannot be
User response: Investigate why the attempt was made to run increased, reduce the number of tasks in the system to avoid
CSTP as a user transaction. short-on-storage situations. Another possibility is to increase
Module: DFHZCSTP the value of the DTIMOUT option for the transaction.
Module: DFHZIS2
AZIA
Explanation: The transaction attempted to acquire or free AZIE
storage during MRO processing. The response from the CICS Explanation: An interregion communication (IRC)
storage manager (SM) domain indicated that the request was ISSUE-ERROR or ISSUE-ABEND flow has been received in
invalid. violation of IRC protocols. This can be caused by:
System action: The task is abnormally terminated with a v A CICS logic error. IRC protocols are not available to MRO
dump. distributed transaction processing applications. They are for
User response: You need further assistance from IBM to CICS internal use only.
resolve this problem. See Part 4 of the CICS Intercommunication 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.
Module: DFHZIS2
transaction dump.
AZIB User response: Check whether a mixture of mapped and
Explanation: The transaction was purged whilst waiting for unmapped conversations are being used as this can cause this
storage to receive MRO data from a connected subsystem. The abend. Check for any other reasons for transactions to be
purge may have been the result of operator action, such as abending on the attached system.
CEMT SET TASK PURGE, or as the result of the waiting time
If a CICS logic error is involved, you will need further
exceeding the DTIMOUT value for the transaction.
assistance from IBM. See Part 4 of the CICS Intercommunication
dump.
Module: DFHZARQ
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. AZI1
Module: DFHZIS2 Explanation: An IRC data transmission request has been
issued, but cannot be completed because the transmission
protocol has been violated.
AZIC
Explanation: An INVALID, DISASTER, or EXCEPTION If the session is not used for distributed transaction
condition has occurred on a call to the storage manager processing, that is if it is used for function shipping or
domain (DFHSMGFM) to FREEMAIN a CRB control block. transaction routing, then the problem is caused by a CICS
logic error.
exception trace, a console message, and possibly a system If the session is used for distributed transaction processing,
dump. then the following are possible causes of the abend:
transaction dump.

AZI2 • AZRA
v An invalid terminal control command, such as ISSUE

AZI5
SIGNAL, was issued
Explanation: An IRC data transmission request has been
v A send request was issued but the session was not in send
issued, but the data sent by the connected system in response
state, or a read request was issued but the session was not
to the request violated IRC protocols.
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
Module: DFHZARQ
Intercommunication Guide. The EIB describes the state of the
session after a request has been issued.
Module: DFHZARQ AZI6
Explanation: The transaction was connected to another
transaction in another CICS system via an IRC link. This other
AZI2
transaction has abnormally terminated.
issued but cannot be completed. Possible causes of the
problem include:
User response: Correct the cause of the abend in the
v The transaction running in the connected system has been
connected transaction.
purged, or
Module: DFHZARQ
v The transaction running in the connected system has been
timed out, or
v The abending transaction has attempted to SEND while in AZI7
RECEIVE state, or Explanation: The transaction was processing an MRO request
v The abending transaction has attempted to RECEIVE while which involved waiting for a response from a connected
in SEND state. subsystem. The 'wait' request was rejected by the CICS
dispatcher.
If the abend was caused by DFHIRP rejecting the transmission
request, the dump will contain DFHIRP's return code in the
a dump.
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.
Module: DFHZIS2
The meanings of the DFHIRP return codes are given in the
copybook, DFHIRSDS.
System action: The task is abnormally terminated with a AZI8
CICS transaction dump. Explanation: The error log data received with an
User response: If the cause of the error was a purge or a ISSUE-ABEND flow on an IRC connection was not in the
time-out, no further action is required. correct format.
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
Module: DFHZIS1
AZI3
Explanation: A terminal control request issued by an
AZI9
application to a remotely-owned terminal failed because the
Explanation: The transaction was processing an MRO request
conversation with the other system failed.
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.
dump.
Module: DFHZARQ
User response: Investigate the reason the transaction was
purged.
AZI4 Module: DFHZIS2
issued, but cannot be completed because the other system has
AZRA
become unavailable for interregion communication.
Explanation: DFHZARRC detected that the address of an
FMH in the APPC was not in the receive buffer. The cause
could either be a storage overwrite or a CICS internal logic
User response: Rerun the transaction when IRC is available.
error.
Module: DFHZARQ

AZRB • AZRK
User response: If this problem is reproducible, a level 1 and

AZRG
2 trace of the TC component would aid problem
Explanation: The DFHZUSR state machine has returned an
determination. Check the TCTTE in the transaction dump for
invalid state error at a point where it should not be possible.
printable characters or other signs of a storage violation error.
This is a CICS internal logic error.
Module: DFHZARRC
AZRB User response: If this problem is reproducible, then a level 1
Explanation: Module DFHZARR0 was called with an invalid and 2 trace of the TC component would aid problem
first parameter. The first parameter should be the code of the determination. You need further assistance from IBM to
function to be performed. This is a CICS logic error. resolve this problem. See Part 4 of the CICS Problem
a CICS transaction dump. Module: DFHZARR
User response: If this problem is reproducible, then a level 1
and 2 trace of the TC component would aid problem
AZRH
determination. You need further assistance from IBM to
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
Module: DFHZARR0
DFHZARRF. This is a CICS internal logic error.
AZRD a CICS transaction dump.
Explanation: The logical and physical APPC receive buffers User response: If this problem is reproducible, then a level 1
have become out of step. This problem is caused either by a and 2 trace of the TC component would aid problem
storage overwrite or by a CICS internal logic error. determination. You need further assistance from IBM to
a CICS transaction dump. Determination Guide for guidance on how to proceed.
User response: If this problem is reproducible, then a level 1 Module: DFHZARR
AZRI
Explanation: One of the parameters passed to DFHZARR1.
Module: DFHZARR0
was invalid. This is a CICS internal logic error.
AZRE a CICS transaction dump.
Explanation: The logical APPC receive buffer (addressed by User response: If this problem is reproducible, then a level 1
TCTERBLA) starts before or after the physical receive buffer and 2 trace of the TC component would aid problem
(addressed by TCTERBLA). This is not valid as the logical determination. You need further assistance from IBM to
receive buffer is the part of the physical receive buffer that is resolve this problem. See Part 4 of the CICS Problem
yet to be processed. This problem could be caused either by a Determination Guide for guidance on how to proceed.
storage overwrite or by a CICS internal logic error. Module: DFHZARR1
AZRJ
User response: If this problem is reproducible then a level 1
Explanation: The length of a record that DFHZARR0 has
been requested to remove from the APPC receive buffer, is
longer than the buffer itself. This problem could be caused
either by a storage overwrite or by a CICS internal logic error.
Module: DFHZARR0
AZRF User response: If this problem is reproducible, a level 1 and
Explanation: The DFHZUSR state machine has returned an 2 trace of the TC component would aid problem
invalid state error at a point where it should not be possible. determination. Check the TCTTE in the transaction dump for
This is a CICS internal logic error. printable characters or other signs of a storage violation error.
System action: The transaction is abnormally terminated with Module: DFHZARR0
User response: If this problem is reproducible, then a level 1
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.
Module: DFHZARRF

AZRL • AZRT
Module: DFHZARRF Module: DFHZARER
AZRL AZRQ
Explanation: Module DFHZARRF was called with an invalid Explanation: Module DFHZARRA was called with an invalid
first parameter. The first parameter should be the code of the parameter. This is a CICS internal logic error.
function to be performed. This is a CICS internal logic error. System action: The transaction is abnormally terminated with
a CICS transaction dump. User response: If this problem is reproducible, a level 1 and
User response: If this problem is reproducible, a level 1 and 2 trace of the TC component would aid problem
2 trace of the TC component would aid problem determination. You need further assistance from IBM to
determination. 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: DFHZARRA
Module: DFHZARRF
AZRR
AZRM Explanation: Module DFHZARRA detected that the
Explanation: Module DFHZARR called one of its own application buffer chained off of a TCTTE at offset TCTERCSA
internal routines at the wrong time. This is a CICS internal had a corrupted header. This is caused either by a CICS logic
logic error. error or by a storage overwrite. The exception trace point that
System action: The transaction is abnormally terminated with accompanies this abend code gives the TCTTE address.
User response: If this problem is reproducible, a level 1 and a CICS transaction dump.
2 trace of the TC component would aid problem User response: If this problem is reproducible, a level 1 and
determination. You need further assistance from IBM to 2 trace of the TC component would aid problem
resolve this problem. See Part 4 of the CICS Problem determination. Check the TCTTE in the transaction dump for
Determination Guide for guidance on how to proceed. printable characters or other signs of a storage violation error.
Module: DFHZARR Module: DFHZARRA
AZRN AZRS
Explanation: The DFHLUC parameter list passed back from Explanation: Module DFHZARRA is unable to acquire main
DFHZERH to DFHZARRF did not have LUCCIERR set on. memory for a new application buffer into which it is supposed
This is a CICS internal logic error. to copy some data. This is because the DFHLUC receive
System action: The transaction is abnormally terminated with request is SUBTYPE=LLID, SET=YES and DFHZARRA does
a CICS transaction dump. not know the length to acquire on the GETMAIN.
User response: If this problem is reproducible, a level 1 and DFHZARRA requires the length of the record currently being
2 trace of the TC component would aid problem received, but it has been set to 0 in error. This is a CICS logic
determination. You need further assistance from IBM to error. The exception trace point that accompanies this abend
resolve this problem. See Part 4 of the CICS Problem code gives the TCTTE address.
Module: DFHZARRF a CICS transaction dump.
AZRO determination. You need further assistance from IBM to
Explanation: Module DFHZARER was called with an invalid resolve this problem. See Part 4 of the CICS Problem
first parameter. The first parameter should be the code of the Determination Guide for guidance on how to proceed.
function to be performed. This is a CICS internal logic error. Module: DFHZARRA
User response: If this problem is reproducible, a level 1 and AZRT
2 trace of the TC component would aid problem Explanation: Module DFHZARRA has detected that the
determination. You need further assistance from IBM to application buffer, into which it is supposed to copy some
resolve this problem. See Part 4 of the CICS Problem data, is invalid. This is either because the address of the buffer
Determination Guide for guidance on how to proceed. is zero or because its length is less than that of the data to be
Module: DFHZARER 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.
AZRP System action: The transaction is abnormally terminated with
Explanation: Module DFHZARER detected an invalid a CICS transaction dump.
response from DFHZNAC. This is a CICS internal logic error. User response: If this problem is reproducible, a level 1 and
System action: The transaction is abnormally terminated with 2 trace of the TC component would aid problem
a CICS transaction dump. determination. You need further assistance from IBM to
User response: If this problem is reproducible, a level 1 and resolve this problem. See Part 4 of the CICS Problem
2 trace of the TC component would aid problem Determination Guide for guidance on how to proceed.
determination. You need further assistance from IBM to Module: DFHZARRA

AZRU • AZS1

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
Module: DFHZARR
the invalid response code.
a CICS transaction dump. AZR2
User response: If this problem is reproducible, then a level 1 Explanation: Module DFHZARRA is unable to acquire main
and 2 trace of the TC component would aid problem memory for a new application buffer because the storage
determination. You need further assistance from IBM to manager GETMAIN failed.
resolve this problem. See Part 4 of the CICS Problem System action: The transaction is abnormally terminated with
Determination Guide for guidance on how to proceed. a CICS transaction dump.
Module: DFHZARRF User response: Use the trace to identify the failing return
from the storage manager and analyze the reason for failure.
Module: DFHZARRA
AZRV
Explanation: Module DFHZARR1 detected an unexpected
response from DFHZARR0. This is a CICS logic error. The AZR3
exception trace point that accompanies this abend code gives Explanation: During a GETMAIN request, the storage
the invalid response code. domain detected that the task has been purged.
User response: If this problem is reproducible, a level 1 and User response: Use the trace to investigate why the task was
2 trace of the TC component would aid problem purged. Check if the master terminal operator was
determination. You need further assistance from IBM to responsible.
resolve this problem. See Part 4 of the CICS Problem Module: DFHZARRA
Module: DFHZARR1
AZR4
Explanation: An unexpected response has been received from
AZRW a dispatcher domain call.
Explanation: Module DFHZARRA detected a negative record System action: The transaction is abnormally terminated with
length in the TCTTE (field TCTELLC). This is caused either by a transaction dump.
a CICS logic error or by a storage overwrite. The exception User response: You need further assistance from IBM to
trace point that accompanies this abend code gives the TCTTE resolve this problem. See Part 4 of the CICS Problem
address and the value of TCTELLC. Determination Guide for guidance on how to proceed.
System action: The transaction is abnormally terminated with Module: DFHZARER
2 trace of the TC component would aid problem AZR5
determination. Check the TCTTE in the transaction dump for Explanation: An unexpected response has been received from
printable characters or other signs of a storage violation error. a dispatcher domain call.
Module: DFHZARRA System action: The transaction is abnormally terminated with
a transaction dump.
AZRY resolve this problem. See Part 4 of the CICS Problem
Explanation: Module DFHZARR detected an unexpected Determination Guide for guidance on how to proceed.
response from DFHZARRC. This is a CICS logic error. The Module: DFHZARR1
exception trace point that accompanies this abend code gives
the invalid response code.
System action: The transaction is abnormally terminated with AZS0
a CICS transaction dump. Explanation: An invalid request was passed via the
User response: If this problem is reproducible, a level 1 and DFHZSTAM macro to the processing DFHZSTAP program.
2 trace of the TC component would aid problem This is a CICS internal logic error.
determination. You need further assistance from IBM to System action: The transaction is abnormally terminated with
resolve this problem. See Part 4 of the CICS Problem a CICS transaction dump.
Determination Guide for guidance on how to proceed. User response: You need further assistance from IBM to
Module: DFHZARR resolve this problem. See Part 4 of the CICS Problem
Module: DFHZSTAP
AZRZ
Explanation: Module DFHZARR detected an unexpected
response from an internal subroutine. This is a CICS logic AZS1
error. The exception trace point that accompanies this abend Explanation: No TCTTE pointer was passed via the
code gives the invalid response code. DFHZSTAM macro to the processing DFHZSTAP program.
System action: The transaction is abnormally terminated with This is a CICS internal logic error.
User response: If this problem is reproducible, a level 1 and a CICS transaction dump.

AZS2 • AZTG

AZTA
Explanation: The task does not own a terminal as its
principal facility.
Module: DFHZSTAP
AZS2 User response: You need further assistance from IBM to
Explanation: The TCTTE passed via the DFHZSTAM macro resolve this problem. See Part 4 of the CICS Problem
to the processing DFHZSTAP program does not relate to an Determination Guide for guidance on how to proceed.
MRO or an APPC Conversation. This is a CICS internal logic Module: DFHZTSP
error.
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).
Module: DFHZSTAP
System action: DFHZTSP is abnormally terminated with a
AZS3 User response: Verify that the listed transactions exist and
Explanation: The TCTTE passed via the DFHZSTAM macro have been installed. If they have, you need further assistance
to the processing DFHZSTAP program for an APPC to resolve this problem. See Part 4 of the CICS Problem
Conversation, but the LUC Extension Control Block was not Determination Guide for guidance on how to proceed.
located. This is a CICS internal logic error. 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
Module: DFHZSTAP
GETMAIN for the attach of CITS, CDTS, or CFTS.
AZS4 a CICS transaction dump.
Explanation: While processing a DFHZSTAM request in User response: Investigate the reason for the SOS condition.
DFHZSTAP, the DFHZUSRM LUC State Machine was found See the CICS Problem Determination Guide for guidance on
to have an invalid setting. This is a CICS internal logic error. dealing with the SOS condition.
Retry the transaction later.
Module: DFHZTSP
Determination Guide for guidance on how to proceed. AZTF
Module: DFHZSTAP 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
AZS5
storage violation or a CICS internal logic error.
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.
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.
Module: DFHZSTAP
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,
AZS6 you need further assistance to resolve the problem. See Part 4
Explanation: Whilst processing a DFHZSTAM request in of the CICS Problem Determination Guide for guidance on how
DFHZSTAP, the Internal State number was found to have an to proceed.
invalid setting. This is a CICS internal logic error. Module: DFHZTSP
User response: You need further assistance from IBM to AZTG
resolve this problem. See Part 4 of the CICS Problem Explanation: An attempt has been made to attach a task on a
Determination Guide for guidance on how to proceed. remotely-owned terminal without an intersystem TCTTE as its
Module: DFHZSTAP principal facility.

AZTH • AZTV

AZTO
Explanation: The TCTTE ownership chain is in error.
Module: DFHZTSP
AZTH User response: You need further assistance from IBM to
Explanation: An error response was received from the remote resolve this problem. See Part 4 of the CICS Problem
terminal control macro. Determination Guide for guidance on how to proceed.
System action: The task is abnormally terminated with a Module: DFHZTSP
AZTP
Explanation: A BMS TYPE=STORE request issued on behalf
of a remote transaction failed.
Module: DFHZTSP
System action: The task abnormally terminates with a CICS
transaction dump.
AZTI User response: Inform the system programmer. Check that
Explanation: An attempt has been made to attach a task on a the required BMS support has been generated.
remotely-owned terminal, but the terminal is not defined in Module: DFHZTSP
this system as a remotely-owned terminal.
Alternatively, another task holds a lock on this terminal. AZTQ

System action: The task is abnormally terminated with a Explanation: Invalid BMS data received from remote system.
User response: Check the terminal control table definitions in CICS transaction dump.
the systems involved. If the definitions are correct, check that User response: You need further assistance from IBM to
no other tasks have locks held on the terminal (CECI, for resolve this problem. See Part 4 of the CICS Problem
example). Determination Guide for guidance on how to proceed.
Module: DFHZTSP Module: DFHZTSP
AZTL AZTR
Explanation: An attempt has been made to attach a task to a Explanation: A BMS TYPE=PAGEOUT request issued on
remotely-owned terminal that cannot be used to run this behalf of a remote system failed.
transaction. System action: The task is abnormally terminated with a
CICS transaction dump. User response: Ensure that the required BMS support has
User response: Inform the system programmer. Check the been generated.
terminal control table definitions in the systems involved. Module: DFHZTSP
Module: DFHZTSP
AZTS
AZTM Explanation: An attempt to ship data to a remote system
Explanation: The data received from the remote system does failed.
not contain an FMH (function management header). System action: The task is abnormally terminated with a
CICS transaction dump. User response: Investigate why the conversations with the
User response: You need further assistance from IBM to remote system failed. The transaction on the remote system
resolve this problem. See Part 4 of the CICS Problem has probably been abnormally terminated or the session has
Determination Guide for guidance on how to proceed. failed.
AZTN AZTU
Explanation: Conversation with a remote system has been Explanation: The task does not own the link TCTTE after a
unexpectedly terminated. sync point has been taken.
AZTV
Explanation: An invalid function management header (FMH)
has been received from the remote system.

AZTW • AZVE
User response: You need further assistance from IBM to Module: DFHZTSP
Module: DFHZTSP AZVA
Explanation: DFHZTSP has timed out waiting for service
transaction CITS to complete during the creation of a remote
AZTW terminal while attaching a task in the application-owning
Explanation: An attempt was made to attach a task on a region.
remotely-owned terminal that was already running a task.
System action: The task is abnormally terminated with a The probable cause of this is that the application-owning
CICS transaction dump. region is very busy, so the CITS transaction has been waiting
User response: Check the terminal control table definitions in to be dispatched for longer than the timeout value allowed by
the systems involved. DFHZTSP. Lack of storage on the target system is one possible
Module: DFHZTSP reason why CITS has not been dispatched, or has been
dispatched but has not completed.
AZTY CICS transaction dump.
Explanation: A session TCT entry for a remotely owned User response: Retry the transaction when the system
APPC terminal or connection could not be created because to becomes less busy. For more information on improving
do so would exceed the maximum number of APPC sessions transaction throughput on the target system, see the CICS
permitted. Performance Guide.
System action: The task is abnormally terminated with a Module: DFHZATS
User response: Inform the system programmer. Either wait
AZVB
for the system to become less busy, or delete some APPC
Explanation: DFHZCQ has failed to create the remote
sessions.
terminal definition. A previous message or messages should
Module: DFHZTSP
indicate the reason for the failure.
AZTZ CICS transaction dump.
Explanation: The CICS relay program DFHCRT has been User response: See the previous message or messages for
attached in an unsupported manner. further guidance.
System action: CICS abnormally terminates the transaction Module: DFHZATS
User response: The relay transaction executes with an MRO
AZVC
session or an LU type 6.2 conversation as its principal facility.
Explanation: An unexpected error has occurred in DFHZATS.
Ensure that the transaction is being attached by APPC
This is probably caused by DFHZATS being unable to address
terminal sharing logic and not directly by a user transaction.
the CSA, EIB or the TCA. It can also occur if DFHZATS is
If the transaction is being attached by APPC terminal sharing called with an EXEC CICS START command for transactions
logic, you need further assistance to resolve this problem. See CITS, CFTS, CMTS or CDTS. These are internal CICS
Part 4 of the CICS Problem Determination Guide for guidance on transactions and should not be called in this way.
how to proceed. System action: The task is abnormally terminated with a
Module: DFHZTSP CICS transaction dump.
AZT1 Determination Guide for guidance on how to proceed.
Explanation: The task has been attached improperly in the Module: DFHZATS
application-owning region when transaction routing.
with a transaction dump. AZVD
User response: The conversation with the routing system Explanation: An unexpected error has occurred in the install
should be an MRO session or an LU type 6.2 conversation. procedure of DFHZATS.
Ensure that the transaction is being attached by the CICS relay System action: The task is abnormally terminated with a
program in the connected system and not by a user program. CICS transaction dump.
User response: This is a CICS logic error. You need further
If the transaction is being attached by the CICS relay program assistance from IBM to resolve this problem. See Part 4 of the
in the connected system, you need further assistance to resolve CICS Problem Determination Guide for guidance on how to
this problem. See Part 4 of the CICS Problem Determination proceed.
Guide for guidance on how to proceed. Module: DFHZATS
Module: DFHZTSP
AZVE
AZT3
Explanation: DFHZATS is trying to install a remote terminal
Explanation: The task is being routed back to the region from
with the same terminal id as an existing TCT entry.
where it came.
User response: Change the terminal names to ensure that a
User response: Correct the transaction definition.
duplicate does not occur in the same system.

AZVF • AZVQ
Module: DFHZATS
AZVL
Explanation: An error has occurred during the mass flagging
AZVF of remote terminals for deletion.
Explanation: One of the remote install or delete transactions System action: The task is abnormally terminated with a
of DFHZATS (CITS, CFTS, CMTS or CDTS) has been started CICS transaction dump.
directly from a terminal. This is not permitted. These User response: You need further assistance from IBM to
transactions can only be started internally by CICS. resolve this problem. See Part 4 of the CICS Problem
a transaction dump. Module: DFHZATS
Module: DFHZATS
AZVM
Explanation: An error has occurred in DFHZATMF. This is
AZVG probably caused by DFHZATMF being unable to address the
Explanation: An error has occurred in the remote delete CSA, EIB, or the TCA.
routines. System action: The task is abnormally terminated with a
Determination Guide for guidance on how to proceed. Module: DFHZATMF
Module: DFHZATS
AZVN
AZVH Explanation: The remote delete flag transaction of
Explanation: An error has occurred in the remote delete DFHZATMF (CRMF) has been started directly from a
routine during the mass deletion of remote terminals. terminal. This is not permitted. This transaction can only be
System action: The task is abnormally terminated with a started internally by CICS.
CICS transaction dump. System action: The transaction is abnormally terminated with
User response: You need further assistance from IBM to a transaction dump.
resolve this problem. See Part 4 of the CICS Problem User response: None.
Determination Guide for guidance on how to proceed. Module: DFHZATMF
Module: DFHZATS
AZVO
AZVI Explanation: The remote delete transaction of DFHZATMD
Explanation: An error has occurred in the remote delete (CRMD) has been started directly from a terminal. This is not
routine while an attempt was being made to delete a single permitted. This transaction can only be started internally by
remote terminal. CICS.
System action: The task is abnormally terminated with a System action: The transaction is abnormally terminated with
CICS transaction dump. a transaction dump.
User response: You need further assistance from IBM to User response: None.
resolve this problem. See Part 4 of the CICS Problem Module: DFHZATMD
Module: DFHZATS
AZVP
Explanation: An error has occurred in DFHZATMD. This is
AZVJ probably caused by DFHZATMD being unable to address the
Explanation: An error has occurred during the mass deletion CSA, EIB, or the TCA.
of remote terminals. This is caused by a CICS logic error. System action: The task is abnormally terminated with a
Determination Guide for guidance on how to proceed. Module: DFHZATMD
Module: DFHZATS
AZVQ
AZVK Explanation: A request to install a shipped terminal
Explanation: An unexpected return code has been received definition has been rejected by the autoinstall user program.
from the remote delete routine during the deletion of a single System action: The task is abnormally terminated with a
remote terminal. CICS transaction dump.
System action: The task is abnormally terminated with a User response: No action.
CICS transaction dump. Module: DFHZATS
User response: Look for an accompanying DFHZC6911
message indicating the reason for the delete failure, and take
appropriate action.
Module: DFHZATS

AZVR • AZXB
AZVR AZXA
Explanation: An attempt to install a shipped terminal Explanation: An unexpected error, with reason code 5, has
definition has failed because the autoinstall user program has been detected in the catchup program, DFHZXCU. See the
issued an invalid return code. description of message DFHXG6492 for further details.
System action: The task is abnormally terminated with a System action: Console message DFHXG6492 is issued, and
CICS transaction dump. CICS continues after abending the transaction.
User response: Examine the autoinstall user program to User response: Refer to message DFHXG6492.
determine why this return code was issued. Module: DFHZXCU
Module: DFHZATS
AZXB
AZVS Explanation: An unexpected error, with reason code 4, has
Explanation: An attempt to install a shipped terminal been detected in the catchup program, DFHZXCU. See the
definition has failed because an error has occurred in the description of message DFHXG6492 for further details.
autoinstall user program. System action: Console message DFHXG6492 is issued, and
System action: The task is abnormally terminated with a CICS continues after abending the transaction.
CICS transaction dump. User response: Refer to message DFHXG6492.
User response: Examine the autoinstall user program to Module: DFHZXCU
determine the reason for the failure.
Module: DFHZATS
System dump codes

Whenever a CICS system dump is requested, CICS references a system dump code
that corresponds to the event that caused the dump request to be made. This is
done in order to see what further action should be taken. More information about
this can be found in the CICS Problem Determination Guide.
In most cases, system dump codes correspond to a DFH message with the DFH
tag stripped off. For example, system dump code DM0001 corresponds to message
DFHDM0001 with the DFH tag removed. For further information, look up the
relevant message where appropriate.
However, there are some exceptions to this format, as shown in the following list.
System dump code
Corresponding message or exception condition
APUSER
This system dump code is issued through the use of the system dump
macro compatibility interface module (DFHFDP).
APXRFTO
This system dump code has no DFH message associated with it. An error
in the currently active CICS system has occurred. An alternate CICS system
is now taking control and is requesting that the active CICS system
produces a dump of itself.
MT0001
This system dump code has no DFH message associated with it. It
indicates that a dump was requested by a user of CEMT, issuing either a
PERFORM SNAP or a PERFORM DUMP.
DHxx (DL/I DOS/VS) abend codes

If an abend occurs in a DL/I task running in a CICS partition, the transaction
abends without returning control to the application program. CICS issues a
message that includes a DL/I abend code. The following list explains the codes
relating to the main categories of DL/I abends.
Code Explanation
Dnnn See DL/I error message DLZnnn.
DACT A TERM call was issued by a program not defined in the ACT

0100 • 0301
DBPC DLZBPC00 (MPS batch partition controller task) terminated abnormally.

DHxx An application program using the HLPI terminated abnormally. xx is the
DL/I PCB status code associated with the terminating transaction.
You can intercept status code abends with an EXEC CICS HANDLE
ABEND command. The ABEND exit routine can attempt to correct the
error and return control to the transaction.
Note: ABENDs cannot be intercepted in batch or MPS batch environments.

DLPV A system scheduling call was issued with an invalid password.
DMPC
DLZMPC00(MPS master partition controller task) terminated abnormally.
Ennn See DL/I error message DLZnnn in DL/I Messages and Codes manual. (In
this case, the termination cannot be noted on the transient data destination
CSMT.)
01xx (translator) abend codes

Explanation: The translator encountered a program check
0100 LISTING FILE CANNOT BE OPENED
from which it could not recover.
Explanation: The listing data set has not opened successfully.
System action: The CICS command-level translator
System action: The CICS command level translator
terminates abnormally with an VSE DUMP. If the job control
terminates abnormally with an VSE DUMP. If the job control
option SYSDUMP is active, the output of the dump is directed
to the dump sublibrary of the partition. If NOSYSDMP is
active, the output is directed to SYSLST.
User response: Ensure correct JCL or determine what is
causing the open error.
Module: DFHEAP1$ (for assembler language), DFHECP1$
Module: DFHEAP1$ (for assembler language), DFHECP1$
(for COBOL), DFHEDP1$ (for C), DFHEPP1$ (for PL/I)
(for COBOL), DFHEDP1$ (for C), DFHEPP1$ (for PL/I)
0101 UNRECOVERABLE TRANSLATOR ERROR
02xx (DFHPD410) abend codes

0211 RECURSIVE PROGRAM CHECK 0212 TOO MANY PROGRAM CHECKS
Explanation: A program check has occurred while the system Explanation: A sixth program check has occurred during
dump formatting program was handling an earlier program execution of the system dump formatting program.
check. System action: The system dump formatting program
System action: The system dump formatting program terminates abnormally with an VSE DUMP. If the job control
terminates abnormally with an VSE DUMP. If the job control option SYSDUMP is active, the output of the dump is directed
option SYSDUMP is active, the output of the dump is directed to the dump sublibrary of the partition. If NOSYSDMP is
to the dump sublibrary of the partition. If NOSYSDMP is active, the output is directed to SYSLST.
active, the output is directed to SYSLST. User response: This abend is preceded by five DFHPD0123
User response: The program check preceding the abend is messages, one for each of the five earlier program checks. See
accompanied by message DFHPD0123. See the description of the description of this message for more guidance.
this message for more guidance. Module: DFHPD410
Module: DFHPD410
03xx (DFHCSDUP) abend codes

0300 0301
Explanation: The SYSIPT data set has not opened Explanation: The RECFM parameter specified in the SYSIPT
successfully. data set is invalid.
System action: The CSD batch update utility terminates System action: The CSD batch update utility terminates
abnormally with an VSE DUMP. If the job control option abnormally with an VSE DUMP. If the job control option
SYSDUMP is active, the output of the dump is directed to the SYSDUMP is active, the output of the dump is directed to the
dump sublibrary of the partition. If NOSYSDMP is active, the dump sublibrary of the partition. If NOSYSDMP is active, the
output is directed to SYSLST. output is directed to SYSLST.
User response: Ensure that the JCL is correct and that the User response: Ensure that the RECFM parameter in the
SYSIPT data set exists in sequential form. If necessary, SYSIPT data set is either F or V.
examine the SYSIPT DLBL statement to determine the cause of Module: DFHCSDUP
the error.
Module: DFHCSDUP

0302 • 0321

0302
Explanation: The record length specified in the SYSIPT data
set is invalid. User response: You need further assistance from IBM to
System action: The CSD batch update utility terminates resolve this problem. See Part 4 of the CICS Problem
abnormally with an VSE DUMP. If the job control option Determination Guide for guidance on how to proceed.
SYSDUMP is active, the output of the dump is directed to the Module: DFHCSDUP
dump sublibrary of the partition. If NOSYSDMP is active, the
output is directed to SYSLST.
0307
User response: Ensure that the record length specified in the
SYSIPT data set is no greater than 80. Explanation: An attempt to print the input command failed.
Module: DFHCSDUP Since messages cannot be issued, the utility must terminate.
System action: The CSD batch update utility terminates
abnormally and an VSE DUMP is taken. If the job control
0303 option SYSDUMP is active, the output of the dump is directed
Explanation: The SYSLST data set did not open successfully. to the dump sublibrary of the partition. If NOSYSDMP is
System action: The CSD batch update utility terminates active, the output is directed to SYSLST.
abnormally with an VSE DUMP. If the job control option User response: You need further assistance from IBM to
SYSDUMP is active, the output of the dump is directed to the resolve this problem. See Part 4 of the CICS Problem
dump sublibrary of the partition. If NOSYSDMP is active, the Determination Guide for guidance on how to proceed.
output is directed to SYSLST. Module: DFHCSDUP
User response: Ensure that the SYSLST data set exists. If
necessary, examine the SYSLST DLBL statement to determine
the cause of the error. 0308
Module: DFHCSDUP Explanation: During the migration of a TCT table, a bad
command sequence was found. This can occur for one of the
following reasons:
0304
v TYPETERM was not preceded by TERMINAL
Explanation: DFHCSDUP has found an unrecognized
v TERMINAL was not followed by TYPETERM
resource type code in a CSD record. The unrecognized code
does not match any of the function codes in the language System action: The CSD batch update utility terminates
definition table. This can occur for one of the following abnormally and an VSE DUMP is taken. If the job control
reasons: option SYSDUMP is active, the output of the dump is directed
1. You are using a CICS release that does not support a type to the dump sublibrary of the partition. If NOSYSDMP is
of definition that was created on the CSD file by a later active, the output is directed to SYSLST.
CICS release. User response: Correct the TCT table to be migrated and
2. The language definition table (DFHEITSP or DFHEITCU) is rerun the job.
invalid for this CICS release. Module: DFHCSDUP
3. The CSD manager (DFHDMP) has passed an invalid CSD
record buffer to DFHPUP. This is a CICS internal logic
0309
error.
Explanation: DFHCSDUP has found an unrecognized
function code in a command. This is a CICS internal logic
error.
Take action corresponding to the reason you have established resolve this problem. See Part 4 of the CICS Problem
as follows: Determination Guide for guidance on how to proceed.
1. Ignore the message. Module: DFHCSDUP
2. Ensure that the library contains versions of DFHEITSP and
DFHEITCU that are valid for the CICS release you are
0321
running.
Explanation: An internal error has occurred in module
DFHCSDUP when invoked by a CSD utility command.
System action: Message DFHCA5100 is issued and the CSD
batch update utility terminates abnormally with an VSE
Module: DFHCSDUP
DUMP. If the job control option SYSDUMP is active, the
output of the dump is directed to the dump sublibrary of the
0305 partition. If NOSYSDMP is active, the output is directed to
Explanation: An unexpected return code was received either SYSLST.
while trying to close the alternate SYSIPT and SYSLST data User response: You need further assistance from IBM to
sets (CLOSEDCB) or while trying to free the task local storage resolve this problem. See Part 4 of the CICS Problem
(FREETLS). Determination Guide for guidance on how to proceed.
System action: The CSD batch update utility terminates Module: DFHCSDUP

0322 • 0330
0322 0327
Explanation: While processing a MIGRATE command, the Explanation: The language table DFHEITCU could not be
specified table to be migrated could not be loaded. loaded.
System action: Message DFHCA5601 is issued and the CSD System action: The CSD batch update utility terminates
batch update utility terminates abnormally with an VSE abnormally and an VSE DUMP is taken. If the job control
DUMP. If the job control option SYSDUMP is active, the option SYSDUMP is active, the output of the dump is directed
output of the dump is directed to the dump sublibrary of the to the dump sublibrary of the partition. If NOSYSDMP is
partition. If NOSYSDMP is active, the output is directed to active, the output is directed to SYSLST.
SYSLST. User response: Refer to the preceding message which should
User response: You need further assistance from IBM to specify the reason for the failure. You need further assistance
resolve this problem. See Part 4 of the CICS Problem from IBM to resolve this problem. See Part 4 of the CICS
Determination Guide for guidance on how to proceed. Problem Determination Guide for guidance on how to proceed.
Module: DFHCSDUP Module: DFHCSDUP
0323 0328
Explanation: While processing a command, VSAM detected Explanation: The language table DFHEITCU could not be
an error. unloaded.
System action: Message DFHCA5179 is issued preceded by System action: The CSD batch update utility terminates
either DFHCA5177 or DFHCA5178 depending on the error abnormally and an VSE DUMP is taken. If the job control
and the CSD batch update utility terminates abnormally with option SYSDUMP is active, the output of the dump is directed
an VSE DUMP. If the job control option SYSDUMP is active, to the dump sublibrary of the partition. If NOSYSDMP is
the output of the dump is directed to the dump sublibrary of active, the output is directed to SYSLST.
the partition. If NOSYSDMP is active, the output is directed to User response: Refer to the preceding message which should
SYSLST. specify the reason for the failure. You need further assistance
User response: See the description of the issued messages to from IBM to resolve this problem. See Part 4 of the CICS
determine the cause of the error. Problem Determination Guide for guidance on how to proceed.
Module: DFHCSDUP Module: DFHCSDUP
0325 0330
Explanation: When the LIST command invoked DFHDMP to Explanation: The cross reference table size for the table being
scan the objects on the CSD file, an error occurred during migrated is too small.
execution of the DFHDMP function. System action: The CSD batch update utility terminates
System action: Message DFHCA5180 is issued and the CSD abnormally with an VSE DUMP. If the job control option
batch update utility terminates abnormally with an VSE SYSDUMP is active, the output of the dump is directed to the
DUMP. If the job control option SYSDUMP is active, the dump sublibrary of the partition. If NOSYSDMP is active, the
output of the dump is directed to the dump sublibrary of the output is directed to SYSLST.
partition. If NOSYSDMP is active, the output is directed to User response: You need further assistance from IBM to
SYSLST. resolve this problem. See Part 4 of the CICS Problem
resolve this problem. See Part 4 of the CICS Problem Module: DFHCSDUP
Module: DFHCSDUP
0326
Explanation: There has been an internal logic error in the
DFHCSDUP utility program. The data in the back-translated
output buffer is invalid. The length code may be out of range
or the data fields in the wrong sequence. One or more of the
data fields may be invalid.
System action: Message DFHCA5184 is issued and the CSD
batch update utility terminates abnormally with an VSE
DUMP. If the job control option SYSDUMP is active, the
output of the dump is directed to the dump sublibrary of the
partition. If NOSYSDMP is active, the output is directed to
SYSLST.
Module: DFHCSDUP

0401 • 0408
04xx (external CICS interface) abend codes

System action: Module DFHXCPRH issues an VSE abend
0401
with abend code 0404 which invokes its ESTAEX routine from
Explanation: An external CICS interface (EXCI) request was
which a SDUMP is taken.
issued using the CALL API or the EXEC API, and the EXCI
User response: Examine the SDUMP to determine the cause
stub DFHXCSTB link-edited with the application detected that
of the earlier reported problem.
it was running in AMODE 24. The external CICS interface
only supports calls made in AMODE 31. An attempt to format the SDUMP produced with the CICS
System action: The application terminates abnormally. INFOANA dump formatter does not produce any formatted
User response: Change the application so that EXCI calls are output for the job because the error occurred too early in EXCI
made in AMODE 31, or relink-edit the application AMODE 31. initialization for there to be any control blocks.
Module: DFHXCSTB. Module: DFHXCPRH
0402 0406
Explanation: The external CICS interface module Explanation: The external CICS interface module
DFHXCPRH issued an OS/390 ESTAEX macro to establish a DFHXCPRH called the CICS SVC to initialize the EXCI
recovery environment, but a nonzero return code was returned environment. The CICS SVC call failed.
from VSE. System action: Module DFHXCPRH issues an VSE abend
System action: The application terminates abnormally with a with abend code 0406 which invokes its ESTAEX routine to
dump. clear up its environment. A SDUMP is taken before returning
User response: Examine the dump and any associated VSE control to the application. An application using the EXCI
messages produced to determine why the OS/390 ESTAEX CALL API receives RESPONSE(SYSTEM_ERROR)
request failed. REASON(CICS_SVC_CALL_FAILURE) in its return area. The
subreason1 field of the return area contains the R15 return
If the error occurred while processing an INITIALIZE_USER
code from the CICS SVC indicating why it failed. An
request on behalf of the application, an attempt to format the
application using the EXCI EXEC API receives
dump using the CICS INFOANA dump formatter does not
RESP(LINKERR) RESP2(607).
produce any formatted output. This is because the error
User response: Use the R15 return code obtained from the
occurred too early in EXCI initialization for there to be any
application or from the dump to determine why the CICS SVC
control blocks.
call failed.
Module: DFHXCPRH
An attempt to format the SDUMP produced with the CICS
INFOANA dump formatter does not produce any formatted
0403 output for the job because the error occurred too early in EXCI
Explanation: The external CICS interface module initialization for there to be any control blocks.
DFHXCPRH issued an OS/390 GETMAIN request to obtain Module: DFHXCPRH
storage for its XCGLOBAL block, but a nonzero return code
was returned from VSE.
System action: Module DFHXCPRH issues an VSE abend 0407
with abend code 0403 which invokes its ESTAEX routine to Explanation: The external CICS interface module
clear up its environment. A SDUMP is taken before returning DFHXCPRH issued a call to the CICS SVC to check whether
control to the application. An application using the EXCI the SVC in use is at the correct level to be used with the
CALL API receives RESPONSE(SYSTEM_ERROR) external CICS interface. The check failed indicating that the
REASON(XCGLOBAL_GETMAIN_ERROR) in its return area. CICS SVC is not at the correct level.
The subreason1 field of the return area contains the R15 return System action: Message DFHEX0100 is output, and module
code from VSE indicating why the GETMAIN failed. An DFHXCPRH issues an VSE abend with abend code 0407
application using the EXCI EXEC API receives which invokes its ESTAEX routine to clear up its environment.
RESP(LINKERR) RESP2(602). A SDUMP is taken before returning control to the application.
User response: Use the R15 return code obtained from the An application using the EXCI CALL API receives
application or from the dump to determine why the RESPONSE(SYSTEM_ERROR)
GETMAIN request failed. See "OS/390 API Return Codes" in REASON(INCORRECT_SVC_LEVEL) in its return area. An
section "VSE/Advanced Functions Codes & SVC Errors" of application using the EXCI EXEC API receives
z/VSE Messages and Codes - Volume 1 for diagnostic information RESP(LINKERR) RESP2(627).
about the VSE return code. User response: See the explanation of message DFHEX0100
for guidance.
If the reason is insufficient storage, increase the partition size
for the batch application. An attempt to format the SDUMP produced with the CICS
output for the job because the error occurred too early in EXCI
initialization for there to be any control blocks.
output for the job because the error occurred too early in EXCI
Module: DFHXCPRH
Module: DFHXCPRH
0408
Explanation: The external CICS interface module
0404
DFHXCPRH issued an OS/390 GETMAIN request for its
Explanation: The external CICS interface module
working storage but a nonzero return code was returned from
DFHXCPRH needed to take an VSE SDUMP for an earlier
VSE.
reported problem. However the error has occurred too early in
EXCI initialization for EXCI dump services to be available.

0410 • 0416
with abend code 0408 which invokes its ESTAEX routine to

0413
clear up its environment. A SDUMP is taken before returning
Explanation: The external CICS interface dump module
control to the application. An application using the EXCI
DFHXCEIP was processing an EXCI EXEC API request and
CALL API receives RESPONSE(SYSTEM_ERROR)
detected that the EXEC parameter list passed to it did not
REASON(WS_GETMAIN_ERROR) in its return area. The
require the mandatory RETCODE parameter in which return
subreason1 field of the return area contains the R15 return
codes are returned to the application.
code from VSE indicating why the OS/390 GETMAIN failed.
An application using the EXCI EXEC API receives An attempt to format the SDUMP produced with the CICS
RESP(LINKERR) RESP2(601). INFOANA dump formatter may not produce any formatted
User response: Use the R15 return code obtained from the output for the job if this was the first EXCI request for this
application or from the dump to determine why the TCB.
GETMAIN request failed. See "OS/390 API Return Codes" in System action: The application is abnormally terminated
section "VSE/Advanced Functions Codes & SVC Errors" of with a dump.
z/VSE Messages and Codes - Volume 1 for diagnostic information User response: This error indicates the parameter list being
about the VSE return code. passed to the EXCI has not been generated by the CICS
translator. The translator should always be used. Correct the
If the reason is insufficient storage, increase the region size of
application to specify RETCODE.
the batch application.
Module: DFHXCEIP
output for the job because the error occurred too early in EXCI 0414
initialization for there to be any control blocks. Explanation: The external CICS interface module DFHXCEIP
Module: DFHXCPRH issued an VSE ESTAEX macro to establish a recovery
environment but a nonzero return code was returned from
VSE.
0410 System action: The application terminates abnormally with a
Explanation: The external CICS interface module dump.
DFHXCPRH issued an OS/390 GETMAIN request for an User response: Examine the dump and any associated VSE
XCUSER block but a nonzero return code was returned from messages to determine why the VSE ESTAEX request failed.
VSE.
INFOANA dump formatter may not produce any formatted
with abend code 0410 which invokes its ESTAEX routine to
output for the job if this was the first EXCI request for this
clear up its environment. A SDUMP is taken before returning
TCB.
control to the application. An application using the EXCI
Module: DFHXCEIP
CALL API receives RESPONSE(SYSTEM_ERROR)
REASON(XCUSER_GETMAIN_ERROR) in its return area. The
subreason1 field of the return area contains the R15 return 0415
code from MVS™ indicating why the OS/390 GETMAIN Explanation: The external CICS interface module DFHXCEIP
failed. An application using the EXCI EXEC API receives detected an error early in EXCI initialization before EXCI
RESP(LINKERR) RESP2(603). dump services were available. DFHXCEIP issues abend 0415
User response: Use the R15 return code obtained from the so that its ESTAEX routine is invoked from where an SDUMP
application or from the dump to determine why the OS/390 is taken instead to capture the error.
GETMAIN request failed. See "OS/390 API Return Codes" in System action: The application terminates abnormally with a
section "VSE/Advanced Functions Codes & SVC Errors" of dump.
z/VSE Messages and Codes - Volume 1 for diagnostic information User response: Examine the SDUMP to determine the cause
about the VSE return code. of the earlier reported error.
If the reason is insufficient storage, increase the partition size An attempt to format the SDUMP produced with the CICS
of the batch application. INFOANA dump formatter does not produce any formatted
Module: DFHXCPRH output for the job because the error occurred too early in EXCI
Module: DFHXCEIP
0412
Explanation: The external CICS interface dump module
DFHXCEIP was processing an EXCI EXEC API request and 0416
detected that the EXEC parameter list passed to it contained a Explanation: The external CICS interface module
function that is not supported by the external CICS interface. DFHXCPRH issued a VSE SUBSID macro during the
System action: The application is abnormally terminated initialization of the EXCI environment. The SUBSID macro
with a dump. failed.
User response: This error indicates the parameter list being System action: Module DFHXCPRH issues an abend with
passed to the EXCI has not been generated by the CICS abend code 0416 which invokes its ESTAEX routine to clear up
translator. The translator should always be used. Correct the its environment. A SDUMP is taken before returning control to
application to specify the correct EXCI EXEC API command. the application. An application using the EXCI CALL API
An attempt to format the SDUMP produced with the CICS receives RESPONSE(SYSTEM_ERROR)
INFOANA dump formatter may not produce any formatted REASON(CICS_SUBSID_FAILURE) in its return area. The
output for the job if this was the first EXCI request for this subreason1 field of the return area contains the R15 return
TCB. code from the SUBSID macro indicating why it failed. An
Module: DFHXCEIP application using the EXCI EXEC API receives
RESP(LINKERR) RESP2(630).
User response: Use the SUBSID return code obtained from

Dump/abend codes
the application or from the dump to determine why the macro Module: DFHXCPRH
failed.

Readers’ Comments — We'd Like to Hear from You
IBM z/VSE
Messages and Codes
Volume 3
Version 5
Publication No. SC34-2634-02
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, your
IBM business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use
the personal information that you supply to contact you about the issues that you state on this form.
Comments:
Thank you for your support.

Submit your comments using one of these channels:
v Send your comments to the address on the reverse side of this form.
v Send a fax to the following number: +49-7031-163456
v Send your comments via email to: s390id@de.ibm.com
v Send a note from the web page: http://www.ibm.com/systems/z/os/zvse/
If you would like a response from IBM, please fill in the following information:
Name Address
Company or Organization
Phone No. Email address

___________________________________________________________________________________________________
Readers’ Comments — We'd Like to Hear from You Cut or Fold
SC34-2634-02 Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
IBM
Deutschland Research & Development GmbH
Department 3282
71032 Boeblingen
Germany
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
SC34-2634-02 Along Line

Printed in USA
SC34-2634-02

Codigos Cics PDF

Uploaded by

Document Information

Original Title

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

Codigos Cics PDF

Uploaded by

Copyright:

Available Formats

IBM z/VSE

Messages and Codes

Messages and Codes

© Copyright IBM Corp. 1999, 2014 iii

iv z/VSE V5R2 Messages and Codes, Volume 3

Such information may be available, subject to appropriate terms and conditions,

Linux is a registered trademark of Linus Torvalds in the United States, other

© Copyright IBM Corp. 1999, 2014 v

IPv6/VSE is a registered trademark of Barnard Software, Inc.

vi z/VSE V5R2 Messages and Codes, Volume 3

Using Assistive Technologies

One exception is command syntax that is published in railroad track format. If

In the request, be sure to include the publication number and title.

© Copyright IBM Corp. 1999, 2014 vii

Organization of the Manual

Where to Find More Information

z/VSE Home Page

You can find the z/VSE home page at

The Message Format

© Copyright IBM Corp. 1999, 2014 ix

partition + reply message text of the

Type and operator codes

The message code is in the form:

The reply-ID is a number between 000

+ = A reply is required immediately.

The partition-ID (2 alphanumerics):

For example, the message:

is to be interpreted in the following way:

x z/VSE V5R2 Messages and Codes, Volume 3

The Action Indicator

Type/Operator Action Codes

The Message Text Syntax

Read these meta-tags like this:

About This Book xi

For example, the message text:

When You Get a Message

xii z/VSE V5R2 Messages and Codes, Volume 3

Online Message Descriptions

About This Book xiii

© Copyright IBM Corp. 1999, 2014 xv

© Copyright IBM Corp. 1999, 2014 1

EV The sequential I/O component

2 z/VSE V5R2 Messages and Codes, Volume 3

DFHnn-Prefix Messages (CICS Transaction Server for VSE/ESA) 3

CSKL Log for transaction and profile resource definitions

A number of console messages should not be rerouted to a transient data queue.

4 z/VSE V5R2 Messages and Codes, Volume 3

Abend code inserts –

VSE user abend codes

Ordered by abend code

0108 DFHCA5263 0185 DFHJC4530

DFHnn-Prefix Messages (CICS Transaction Server for VSE/ESA) 5

0121 DFHCA5100 0200 DFHXA6540

Ordered by message identifier

6 z/VSE V5R2 Messages and Codes, Volume 3

DFH7xxx (DFHExP) command-level translator diagnostic messages

A diagnostic message can have three components: a message number, a severity

Assembler, C or PL/I Return code COBOL

DFHnn-Prefix Messages (CICS Transaction Server for VSE/ESA) 7

Assembler, C or PL/I Return code COBOL

Messages issued by the command-level translator are usually self-explanatory, and

is active, the output is directed to SYSLIST.

8 z/VSE V5R2 Messages and Codes, Volume 3