The following DB2 messages are accessible from the operating system command line:
As well, the message text associated with SQLSTATE values is available online.
Message identifiers consist of a three-character message prefix (see above list), followed by a four- or five-digit message number. The single-digit letter at the end, which describes the severity of the error message, is optional.
To access help on these error messages, enter the following command at the operating system command prompt:
db2 ? XXXnnnnn where XXX represents the message prefix and where nnnnn represents the message number.
| Note: | The message identifier accepted as a parameter of the db2 command is not case-sensitive, and the terminating letter is not required. |
Therefore, the following commands will produce the same result:
If the message text is too long for your screen, use the following command (on UNIX-based systems and others that support 'more'):
db2 ? XXXnnnnn | more
Help can also be invoked in the interactive input mode. To enter the interactive input mode, enter the following command at the operating system command prompt:
db2
Once in the interactive input mode, you can enter commands at the following command prompt:
db2 =>
To get DB2 message help in this mode, type the following command at the command prompt:
? XXXnnnnn
| Note: | If the message text exceeds the length of the screen, users with non-graphical workstations can pipe the output to the 'more' (on UNIX-based systems) program or redirect the output to a file, which you can then browse. |
The message text associated with SQLSTATEs can be retrieved by issuing:
db2 ? nnnnn or db2 ? nn
where nnnnn is a five-digit SQLSTATE (alphanumeric) and nn is the two-digit SQLSTATE class code (first two digits of the SQLSTATE value).
Some DB2 components return messages that are not described in this manual, or online. Some of the message prefixes might include:
In most cases, these messages provide sufficient information to determine the cause of the warning or error. For more information on the command or utility that generated the messages, please refer to the appropriate manual where the command or utility is documented.
When running other programs on your workstation, you might receive messages with prefixes other than those mentioned in this reference.
For information on these messages, see the publications that you received for that program product.