Set Db2/IRLM Messages that MSGE Exception Monitors
Use this panel to add or delete the Db2 and IRLM messages that you want the MSGE exception to monitor.
________________ ZXMSG VTM O2 V550.#P DA41 11/06/13 11:36:53 2
> Help PF1 Back PF3
> P.J
===============================================================================
> SET Db2/IRLM MESSAGES THAT MSGE EXCEPTION MONITORS
> To add a Db2 or IRLM message to the list shown below, type its message
> identifier, which can be up to 8 characters, on the broken line next
> to Add =. To delete a message, type its identifier next to Delete=. Press
> ENTER to record the change.
XMSG
+ DSN000I DSN010E DSN011E DSN025W DSX030W DSX050N DSX051N
+ DSX052N DSX053N
: Add = ________
: Delete = ________
===============================================================================
Navigation
For additional information about other topics, use the PF keys.
Fields
- XMSG
- The lines below XMSG define the IDs of the DB2® and Internal Resource Lock Manager (IRLM) messages that OMEGAMON® for Db2 PE exception analysis is tracking.
- Add
- Type the ID of an additional Db2 or IRLM
message that you want OMEGAMON
for Db2 PE exception analysis to
track, and press Enter. You can add more than one ID at a time by typing the
IDs on the Add line with a space between them.Note: If you want to add a group of messages that have the same initial characters, you can save time by entering only those characters. For example, if you enter DSN, XMSG will monitor all messages that begin with DSN.
- Delete
- Type the ID of a Db2 or IRLM message that
you no longer want OMEGAMON for
Db2 PE exception analysis to track and
press Enter. You can delete more than one ID at a time by typing the IDs on
the Delete line with a space between them. Note: If you want to delete a group of messages that have the same initial characters, you can save time by entering only those characters. For example, if you enter DSN, XMSG will no longer monitor messages that begin with DSN.