Format of information

Information about each message is presented in the following format:

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 DFHMEXMnnnn 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 MVS™ 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 MVS log

Unless otherwise stated, console messages have the route codes ‘2’ and ‘11’.

Start of change

Message editing -

You can use the message editing utility to change the text or language of those CICS messages that are issued via the message domain. Messages that cannot be changed using the utility include a note to this effect before the message destination. See the CICS Operations and Utilities Guide for more information about the message editing utility.

End of changeStart of change

Console message reformatting -

The "console message handling facility" is an optional feature of the CICS subsystem that can affect the appearance of CICS messages displayed on an MVS console. It is effective when you specify FORMATMSG=YES as an initialization parameter for the CICS subsystem, as described in the CICS Transaction Server for z/OS® Installation Guide. When this facility is used, it affects messages displayed on MVS system consoles in the following ways:

End of change

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:

[[ Contents Previous Page | Next Page Index ]]