DB2 Server for VSE: Messages and Codes

Message Format and Associated Text

In this book, the conventions for showing messages are:

• All the letters, numbers, and punctuation marks (periods, commas, underscores, dashes, and so on) following the message identifier in bold show the actual message text. The exceptions to this convention are brackets [ ], braces { }, logical OR symbols |, blank lines, and format numbers.
• Letters, words, and numbers in the text of the message that are not bold represent variables. Hyphenated words that are not bold also represent variables. The database manager substitutes specific values for the variables when it displays the message.

  In the explanation following the message text, the variables are in bold or italics.

• Brackets [ ] enclose optional message text. Depending on the circumstances, an item or group of items in brackets might appear when the message is displayed.
• Braces { } enclose alternative items, which are separated by a logical OR | symbol. Depending on the circumstances, one of the alternative items appears when the message is displayed.

All DB2 Server for VSE messages have a message identifier in the form of XXXnnnnt, where:

XXX

Identifies the major component generating the message:

ARI

shows the message is from the database manager component of the DB2 Server

ASN

shows the message is from the DPROPR component

DSQ

see QMF Messages and Codes manual

XTS

shows the message is from the Data Restore Feature.

nnnn

Identifies the particular message number.

t

Is the action indicator:

A

Action required

D

Decision required

E

Error

I

Information only

W

System wait.

For messages beginning with:

XTS

See the DB2 Server for VSE & VM Data Restore manual

SQM

See the DB2 for VSE Control Center Operations Guide.

ELO

See the DB2 REXX SQL for VM/ESA Installation and Reference manual

Explanation contains information about the message. This includes the following:

• Definitions for variable fields in the message text
• Possible reasons why the message occurred
• Additional descriptive information about the condition that caused the message to occur.

System Action describes the resulting action that was or will be taken by the database manager.

User Response, Operator Response, Programmer Response, Database Administrator Response, and System Programmer Response describe the responses that might be required of those persons.