Message identifiers are of two types.
These consist of the prefix "DFH" followed by a four digit message
number. "DFH" is the IBM® assigned identifier for CICS® modules. The
first two digits are the CICS module reference code as follows:
- 01
- DFHSSIN
- 42
- DFHZCNR
- 51
- DFHCSDUP
- 52
- DFHCSDUP
- 55
- DFHCSDUP
- 56
- DFHCSDUP
- 7x
- Command-level translators
The last two digits are assigned by CICS to identify the message or group of messages
within an assembled program.
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
AD
The CICS Development Deployment Tool messages
- AI
- The auto-install terminal model manager (AITM)
- AM
- The RDO allocation manager
- AP
- The application domain
BA
The CICS business transaction services (BTS) domain
BR
Bridging to 3270 transactions
CA
RDO command utility routine
- CC
- The CICS catalog domain (local and global)
- CE
- The sign on program component
CF
CICS coupling facility data tables server
- CP
- The CPI Communications component
- CQ
- The CQ console messages
- CR
- The ISC remote scheduler component
CZ
The CICS class libraries domain
- DB
- The CICS database control component
- DD
- The directory manager
DH
Document handler component
- DM
- The domain manager domain
DP
The debugging profile domain
- DS
- The dispatcher domain
- DU
- The dump domain
- DX
- The CICS database control component
EJ
The Enterprise Java™ domain
EM
The Event Manager domain
- ER
- The user backout program
- EX
- The external CICS interface
- FC
- The file control component
- FE
- The FE terminal test program component
- IC
- The interval control program
IE
The IP ECI domain
II
The CORBA and IIOP domain
IN
The indoubt testing tool
- IR
- The interregion component
- JC
- The online journal control component
- KC
- The transaction/profile manager
- KE
- The kernel domain
- LD
- The loader domain
LG
The logger domain
- LM
- The lock manager domain
- MC
- The BMS message control program component
- ME
- The message domain
- MN
- The monitor domain
- MU
- The message editing utility program
- MV
- The MVS™ RESMGR exit stub
NC
The Named counter sequence number server
NQ
The enqueue manager domain
OT
The Object Transaction Services domain
- PA
- The parameter manager domain
- PC
- The program control program component
- PD
- The print dump exit routine DFHPDX
- PG
- The program manager domain
PI
The pipeline manager domain
- PR
- The partner resource manager
- PS
- The system spooler interface control module component
- RD
- The RDO allocation manager
- RM
- The recovery manager
- RP
- CICS ONC RPC
RS
The communications resynchronization program
- RT
- The ISC transaction routing component
- RU
- The recovery utility program
RX
The RRS-coordinated EXCI domain
RZ
The Request Streams domain
SH
The Sheduler domain
- SI
- The system initialization component
SJ
The Scaleable Java domain
- 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 domain
- UP
- The measured usage license charging support macro
- US
- The user domain
- WB
- The CICS Web Interface
- 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
XQ
The shared temporary storage queue pool server
- XS
- The CICS security component
- ZC
- The terminal control working set component
- ZE
- The TCP error message writer component
- ZN
- The syncpoint component
Thus the CICS message DFHAP0002 is issued from the application domain, identified
by the two-character identifier AP.
Certain messages (for example, DFHDB8208D) 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.)

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
- Alert. 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.
[[ Contents Previous Page | Next Page Index ]]