Messages
The messages library consolidates all BMC messages from the following product lines:
| Enter message ID or message text to locate your message: | ||
Intended Audience
This space is intended for use by Abend-AID installers and systems programmers.
Messages overview
This section lists in alphanumeric order the messages that Abend-AID for CICS, the Abend-AID Viewer, and the batch dump capture address space (BDCAS) generate. Included with each message is an indication of its severity, the reason Abend-AID for CICS, the Abend-AID Viewer, or the BDCAS generated the message, and any resultant actions performed by the system or required of the user. In addition, messages starting with prefix DB2 include a Module entry. This entry names the application module from which the message originated.
Message IDs
Most Abend-AID for CICS, Abend-AID Viewer, and BDCAS messages include a 10-character message ID that has the following format:
WWWXXYYYYZ
As following figure illustrates, the message ID has four distinct parts:
•A three-character message prefix
•A two-character Abend-AID Viewer component ID
•A four-character sequence number
•A one-character message severity code.
Abend-AID for CICS, Abend-AID Viewer, and BDCAS Message ID Syntax
Each part of a message ID conveys specific information:
Message Prefix
The three-character message prefix identifies the major area from which a message originated. Valid message prefix values are as follows:
CCA | CICS transaction-related services |
CTC | CICS transaction dump capture services |
DB2 | DB2 |
ERW | SVC dump processing |
FDB | SVC dump-related services |
HCI | Communication services |
KAZ | Batch dump processing |
MBC | Batch dump capture address (BDCAS) processing |
MCC | CICS common; that is, areas in CICS that are common to both transaction and region dumps |
MFD | Fault Diagnosis for batch, transaction, and SVC dumps |
MRD | WebSphere MQ-related region dump services |
MSD | Dump access for batch, transaction, and SVC dumps |
MTC | WebSphere MQ-related transaction dump services |
QMD | WebSphere MQ queue manager-related services |
ZSD | z/OS-related SVC dump processing |
Component ID
The two-character component ID specifies the Abend-AID Viewer component that generated the message. Each message prefix has its own set of applicable component IDs.
For the CCA message prefix, the following component IDs are valid:
CI | CICS transaction initialization |
CT | CICS transaction termination |
ME | Message errors |
SD | Dump access services |
VT | Server view time |
For the CTC message prefix, the following component IDs are valid:
FD | Fault diagnosis |
TC | Transaction dump capture |
For the DB2 message prefix, the following component IDs are valid:
DC | Dump capture |
VP | View processing |
For the ERW message prefix, the following component IDs are valid:
AN | Symptom analysis |
AP | Application domain |
BR | 3270 bridge processing |
CD | Core (memory) display/access |
CI | Communication interface |
CR | Dump processing |
CS | Change summary |
DA | Dump analysis |
DD | Dump directory maintenance/display |
DH | Document handler domain |
DL | DL/I |
DS | Dispatcher domain |
DU | Dump domain |
FC | File control |
GM | General (common) |
IC | Interval control |
JC | Journal control |
KC | Task control |
KE | Kernel domain |
LD | Loader domain |
LG | Log manager |
LM | Lock manager |
LN | Link command |
MN | Monitoring domain |
NQ | Enqueue manager |
PC | Program control |
PD | Problem directory |
PG | Directory manager PPT |
RM | Resource manager |
RS | Task control area |
SM | Storage manager |
SO | Sockets domain |
SY | Storage retrieval |
TA | Task analysis |
TC | Terminal control |
TD | Transient data |
TI | Timer domain |
TM | Table manager |
TS | Temporary storage |
UE | User exit |
WB | Web domain |
WH | WHO and WHERE command |
XI | Server main task/VTAM or tasks started by the post dump exit |
XM | Transaction manager or system dump interface |
For the FDB message prefix, the following component IDs are valid:
DS | Dataset |
FO | File owning subtasks |
HP | HTML viewing support |
IN | Installation |
PO | Profile options |
RC | Region control |
SI | Presentation environment |
SS | Subsystem processing |
VP | VTAM processing |
For the HCI message prefix, the only valid component ID is:
HC | Communication services |
For the KAZ message prefix, the only valid component ID is:
KA | Batch dump processing |
For the MBC message prefix, the only valid component ID is:
BC | Batch dump capture address (BDCAS) processing |
For the MCC message prefix, the only valid component ID is:
CC | Common components (Common Shared Services) |
TR | Trace |
For the MFD message prefix, the following component IDs are valid:
AA | AADF |
CR | Region configuration |
DB | DB2 |
FD | Fault Diagnosis |
FE | Dump capture options |
IN | Installation |
PO | Profile options |
SI | Screen interface |
SL | Source support |
TR | Trace |
For the MRD message prefix, the only valid component ID is:
MR | Region dump analysis and viewing |
For the MSD message prefix, the following components IDs are valid:
CB | Control blocks |
CD | Core display |
DE | Code Coverage/DevEnterprise |
FM | Fault Manager |
GM | General |
HX | Hexadecimal storage |
IN | Installation |
PL | Program log |
SD | Dump access services |
VS | Virtual storage |
VT | View time |
For the MTC message prefix, the only valid component ID is:
MC | WebSphere MQ-related transaction dump services |
For the QMD message prefix, the only valid component ID is:
QR | WebSphere MQ queue manager-related services |
For the ZSD message prefix, the following component ID is valid:
ZO | z/OS-related region and transaction dump processing |
Sequence Number
The four-character sequence number uniquely identifies each message within each Abend-AID Viewer component.
Severity Code
The one-character severity code specifies the severity of the message. Valid values are as follows:
I | Informational — Requested processing was successful. |
W | Warning — Requested processing was successful, with some qualification. |
E | Error — Requested processing was not successful, but the error does not affect the continuation of the user’s Abend-AID Viewer session. |
S | Severe error — User’s Abend-AID Viewer session may not be able to continue. |
C | Critical error — Error may have affected the entire Abend-AID Viewer server region. |
User Abends
User Abend Codes describes user abend codes that you may receive early in the Abend-AID startup processing in the viewing server, batch dump capture address space (BDCAS), transaction dump capture address space (TDCAS), or the CICS region and that are not preceded by a message.
Online Help
To display online help for any message, execute one of the following procedures:
•Position the cursor on the message ID and press the HELP key (PF1).
•Type MSGHELP messageid in the COMMAND (or OPTION) field on any screen and press Enter. For example, typing MSGHELP AN0001 displays the online help for message ERWAN0001I.
Batch Abend-AID messages
This section lists the Batch Abend-AID messages you may encounter while installing and using Abend-AID. Along with each messages, explanations may provide the following information:
- The message number. The entry (None) indicates that the message has no number.
- The message text.
- The program module that issued the message.
- An analysis of the message, including the reason why the message was issued and the action Abend-AID takes.
- Instruction for the user or troubleshooting staff.
Customized User Messages
A function introduced in Abend-AID Release 9.4 with Common Shared Services (CSS) 7.9 and later allows you to hot key from your job log to the report in the Abend-AID report data set. This function uses the same CLIST as for the Abend-AID Viewer that you set up during the installation process. The function is context-independent and works from any ISPF screen display. It depends on the AB400A message which is written at dump capture to the job log. This message (and function) is unique in these ways:
- You can add up to four user-defined lines of message text to the AB400A message that display, sequentially, with each instance of the AB400A message. Use this message to provide instructions for using the hotkey to access Abend-AID reports. The message is configured in global options, in the HotKey WTO fields.
- There are several ways to access the report while viewing the AB400A message:
- Type the TSO command TSO EXEC ‘CX.SLCXCNTL(CWVFREXE)’ ‘HOTKEY’ and press Enter.
- Equate the TSO command to a PF key and thus provide hot key access to the report.
- Define the TSO command as an ISPF system command.