Deleting Messages Already Written

The DOM macro deletes the messages that were created using the WTO or WTOR macros. Depending on the timing of a DOM macro relative to the WTO or WTOR, the message may or may not have already appeared on the operator's console.

When a message already exists on the operator screen, it has a format that indicates to the operator whether the message still requires that some action be taken. When the operator responds to a message, the message format changes to remind the operator that a response was already given. When DOM deletes a message, it does not actually erase the message. It only changes the message‘s format, displaying it like a non-action message.
If the message is not yet on the screen, DOM deletes the message before it appears. The DOM processing does not affect the logging action. That is, if the message is supposed to be logged, it will be, regardless of when or if a DOM is issued. The message is logged in the format of a message that is waiting for operator action.

The program that generates an action message is responsible for deleting that message.

To delete a message, identify the message by using the MSG, MSGLIST, or TOKEN parameters on the DOM macro, and issue DOM.

When you issued WTO or WTOR to write the message, the system returned a message ID in general purpose register 1. Use the ID as input on the MSG or MSGLIST parameters. MSGLIST (message list) associates several message IDs with the delete request. You define the number of message IDs in the message list by the COUNT parameter or by specifying a 1 in the high-order bit position of the last message ID in the list. The count parameter cannot exceed 60. If you specified the TOKEN parameter on one or more WTOs or WTORs, use the same value on the TOKEN parameter of DOM to delete all of those messages.