The DB2 Messages workspace displays messages that can help
you identify problems with your DB2 system.
This workspace is comprised of the following views:
- Critical DB2 Messages (table view), which
displays all critical DB2 messages and warning DB2 messages. Critical
messages are highlighted in red and warning messages are highlighted
in yellow.
- Last 10 DB2 Messages (table view), which
displays the ten most recent DB2 messages. Critical messages are highlighted
in red and warning messages are highlighted in yellow.
Note: Not all messages are written to the message log. DISPLAY commands,
for example, are filtered out and are not shown in the log.
Based on the information that this workspace provides,
you can recommend changes, set up situations, and verify that your
recommended changes improve system performance.
Note: By default DB2 messages are not collected. If you want to collect
DB2 messages, use the Configuration Tool and select:
Monitoring
Profile configuration –> Additional configuration settings. If
you configure it to YES, the DB2 message subtask is started during
DB2 instance initialization.
To start or stop DB2 message collection
manually, specify the following:
F <cccccccc>,F PESERVER,F<db2>,DB2MSGMON=<p>
where:
- cccccccc
- Identifies the OMEGAMON Collector started task name.
- db2
- Identifies the DB2 name.
- p
- Enter Y to start or N to stop the message subtask.
If you do not see any DB2 messages, check if the DB2
message subtask is started from the OMEGAMON Collector started task.
You can link to the following workspaces from the DB2 Messages
workspace: