IBM DB2 - Message Reference Vol 1 |
|||
|
ISBN : - |
Order a printed copy of this book from Amazon --UNAVAILABLE-- |
||
![]() Cover Design - IBM DB2 - Message Reference Vol 1 |
For your free electronic copy of this book please verify the numbers below. (We need to do this to make sure you're a person and not a malicious script) | ||
|
Sample Chapter From IBM DB2 - Message Reference Vol 1 Copyright © IBM Corp. |
|||
Chapter 1. Introduction to MessagesIt is assumed that you are familiar with the functions of the operating system where DB2 is installed. You can use the information contained in the following chapters to identify an error or problem and resolve the problem by using the appropriate recovery action. This information can also be used to understand where messages are generated and logged. Message StructureMessage help describes the cause of a message and describes any action youshould take in response to the message. Message identifiers consist of a three character message prefix, followed by a four or five digit message number, followed by a single letter suffix. For example, SQL1042C. For a list of message prefixes, see 'Invoking message help' and 'Other DB2 Messages' on page 2. The single letter suffix describes the severity of the error message. In general, message identifiers ending with a C are severe messages. Those ending with an E are urgent messages. Message identifiers ending with an N are error messages, those ending with a W are warning messages and an I indicates an informational message. For ADM messages, message identifiers ending with a C are severe messages. Those ending with an E are urgent messages. Message identifiers ending with a W are important messages and an I are indicates an informational messages. For SQL messages, message identifiers ending with an N are error messages. Those ending with a W indicate warning or informational messages. Message identifiers ending with a C indicate critical system errors. Invoking message help The following DB2 messages are accessible from the command line processor: Prefix Description AMI messages generated by MQ Application Messaging Interface ASN messages generated by DB2 Replication CCA messages generated by the Client Configuration Assistant CLI messages generated by Call Level Interface DBA messages generated by the Database Administration tools DBI messages generated by installation and configuration DBT messages generated by the Database tools DWC messages generated by the Data Warehouse Center DB2 messages generated by the command line processor DLFM messages generated by Data Links File Manager
|
|||