Using DOM Information - ironstream_for_micro_focus_omi - 7.2

Ironstream for Micro Focus® OMi for IBM Z® Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® OMi
Version
7.2
Language
English
Product name
Ironstream for Micro Focus OMi for IBM Z
Title
Ironstream for Micro Focus® OMi for IBM Z® Administration
Copyright
2021
First publish date
2007
ft:lastEdition
2023-08-23
ft:lastPublication
2023-08-23T16:21:59.136387

Mainframe z/OS messages which require an action or are otherwise highlighted for severity will have their intensity removed when the appropriate action is taken (such as mounting a tape on a drive) or the severe condition is relieved (such as a disk space shortage). z/OS signals the removal of the message highlighting by issuing a Delete Operator Message (DOM). Ironstream can optionally pick up these DOMs and forward them to the OMi server, where they can be used to automatically close alerts that may outstanding.

To get DOMs delivered to the OMi service, either add the DOM parameter to the MVS startup initialization card in the SYSIN for the mainframe agent’s job (see the description of the MVS card in the Installation Guide), or activate it using the DOM console command (see the section “About DOM Commands”).

DOM information will arrive in the OM browser in the form of an EVO211 message event with the following format:

EVO211 source key

where the message parameters are:

Message Parameter

Description

source

Either “MSGKEY” or “MSGTOKEN” depending on whether the DOM is for a specific

message or a set of messages grouped together with a token.

key

An integer value which will match either the msg_key or msg_token information that was delivered with the original message event

The EVO211 message can therefore be set up in the event rules with correlation to auto-acknowledge a previous message with the message key that matches the key. The EV390 MVS Messages policy has conditions for action messages (see condition for $HASP050) that create a message key for acknowledgement by the EVO211 message. See the conditions for the EVO211 message for the creation of the acknowledgement key.