The structure of message numbers

Message numbers have fourfold structure that consists of prefix, subcomponent identifier, number, and severity code.

Prefix
A three-character prefix that identifies the product or major component that issues a message.
BPO
The Buffer Pool Analyzer program prefix.
DGO
Prefix that identifies workstation client messages.
FPE
The OMEGAMON for Db2 PE program prefix (components from former IBM® Db2 Performance Expert product).
KDP
The Tivoli® Enterprise Monitoring Agent (TEMA) for Db2 program prefix
KO2
The OMEGAMON for Db2 PE program prefix (components from the former OMEGAMON II product).
Subcomponent identifier
A one-character subcomponent identifier that identifies the subcomponent within a product or major component. For example, in message FPEA1242I, the A identifies the Accounting subcomponent in OMEGAMON for Db2 PE.

BPO messages use a single subcomponent identifier K, which means that all Buffer Pool Analyzer messages start with BPOK.

DGO messages use a single subcomponent identifier K, which means that all workstation client messages start with DGOK.

FPE messages use the following subcomponent identifiers:
A
Accounting
B
User-Tailored Reporting (part of Batch feature)
C
Background control
E
Exception processing
F
Interactive Report Facility (part of Batch feature)
I
I/O activity
J
Installation and customization
L
Locking
M
Online Monitor
R
SQL activity
S
Statistics
T
Utility activity
U
Utility services
V
Data Server
W
System Parameters report set
X
Audit
Y
Explain
Z
Migrate/Convert function

KDP messages do not have explicit subcomponent identifiers.

KO2 messages use the following subcomponent identifiers:
A
Reserved for Application Trace Facility (ATF)
C
Reserved for Interface, Cross-Memory, Display Module
D
Reserved for Data Analysis Module
E
Object Analysis
H
Near-Term History Data Collector
I
Reserved for D5API Framework
M
ISPF
O
VTAM® Display Logic
P
Reserved for D5API Collectors
R
Capture Server
S
Storage Manager
T
Reserved
U
Reserved for Utility I/O and Data Conversion Routines
X
Cross-Memory Module
Z
OMPE Subsystem
Message number
A unique number within the range of messages from a subcomponent.
Severity
An appending single-letter code that indicates the severity of the message.
I
Informational message that does not require any user action.
W
Warning message that should be analyzed to determine whether the condition can effect the results. Usually, a warning message does not prevent the system from execution.
E
Error message that can be corrected by an appropriate user action (for example, by correcting a command syntax error).
S
Severe error message that results from an abnormal condition and in the abandonment of processing for a command. Other commands in a job stream may still be executed.
U
Unrecoverable error message that results from an abnormal condition and in the abandonment of processing for the entire job. Most internal errors fall into this category.