DB2 Message Attributes

Use the DB2 Message attributes to identify problems with your DB2 system.

DB2ID The name of a DB2 subsystem.

DB2 Version The version of DB2.

Interval Start The date and time, as set on the monitored system, indicating the instance when the agent collects information.

Long Message Action Code The long message action code.

Message ID The system identification number for the message. Valid format is an alphanumeric text string with a maximum of eight characters.

Message Text A description of the message. Valid format is an alphanumeric text string with a maximum of 2500 characters.

MVS System ID The MVS identifier.

Originating System ID Identifies the originating Tivoli Enterprise Monitoring Server. Valid format is alphanumeric, with a maximum of 32 characters; for example, DB2.USCACO01.D412.

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
Select Y to start or N to stop the message subtask.
If you do not see any DB2 messages, check if DB2 message subtask is started from the OMEGAMON Collector started task.