Processing, DBUTLTY and SQL Messages

All CA Datacom/DB processing and DBUTLTY messages are numbered and have an identifying prefix in the form DBnxxxxc:

Processing and DBUTLTY Messages

DB	Product code indicating CA Datacom/DB
c	Subsystem identifier as follows: 0 - Processing message (Documented in CA Datacom/DB Processing Messages (DB0xxxxc).) 1 - DBUTLTY message (Documented in DBUTLTY Messages (DB1xxxxc).) 2 - SQL Precompiler message (Documented in SQL Preprocessor Messages (DB2xxxxc).) 9 - CA Datacom Transparency message (Documented in CA Datacom/DB Messages for Invocation of CAIRIM (DB9xxxxc).) H - Health Checker message (Documented in CA Datacom/DB Health Checker Messages).)
xxxx	Numeric message identifier
c	Message type indicator as follows is a general guideline because the line between the various types is often a matter of opinion. Once a message is documented with a given type, it is a risk to all users for the type to be changed to another. A - Action C - Critical E - Error I - Information W - Warning

Product code indicating CA Datacom/DB

Subsystem identifier as follows:

0 - Processing message (Documented in CA Datacom/DB Processing Messages (DB0xxxxc).)
1 - DBUTLTY message (Documented in DBUTLTY Messages (DB1xxxxc).)
2 - SQL Precompiler message (Documented in SQL Preprocessor Messages (DB2xxxxc).)
9 - CA Datacom Transparency message (Documented in CA Datacom/DB Messages for Invocation of CAIRIM (DB9xxxxc).)
H - Health Checker message (Documented in CA Datacom/DB Health Checker Messages).)

xxxx

Numeric message identifier

Message type indicator as follows is a general guideline because the line between the various types is often a matter of opinion. Once a message is documented with a given type, it is a risk to all users for the type to be changed to another.

A - Action
C - Critical
E - Error
I - Information
W - Warning

Message Prefix

If you have coded the MUF startup option MUFMSG, certain CA Datacom/DB messages (see MUFMSG in the CA Datacom/DB Database and System Administration Guide) are prefixed by one or more pieces of information in the format a:b:c:d identified as follows:

a	JOBNAME
b	SVC number
c	MUFNAME
d	CA Datacom/DB numbered message

The z/OS default prints all three prefixes. The z/VSE default does not print the SVC number prefix because the SVC number is meaningless in z/VSE.

Message Suffix

Allows the same choices but the suffix occurs after zero or more spaces after a message.