Coding Each AOF Rule Type › Delete-Operator-Message Rules › Example: DOM Rule

Example: DOM Rule

The following is an example of a rule that responds to a DOM event. The example assumes that you have an associating MSG rule that is sending messages to some focal system. This DOM rule would allow those remotely sent action messages to be low-lighted. This might be a desired application in a non-sysplex CA OPS/MVS MSF connected environment, or a normal sysplex.

)DOM *
)PROC
/* SYSTEM A is our focal system, as to which we are currently */
/* shipping all message traffic. This DOM rule will use       */
/* the OPS/REXX OPSSEND function to ship over this DOM event  */
/* We also need to exclude shipping sysplex generated DOMS    */
/* to avoid a possible rule loop.                             */

 if DOM.SYSPLEX = 0 then             /* locally generated DOM */
   sendrc = OPSSEND(“SYSA”,”D”)

 return

Note: The AOFMESSAGES parameter controls whether reissued messages and DOMs are processed by AOF rules. This includes messages and DOMs that originated on another system and were transported and reissued on this system by MSF, CA MIC, or sysplex services.

See examples TAPEMNT1, TAPEMNT2, and TAPEMNT3 of your CA OPS/MVS data set that contains the downloaded OPS.SAMPLES file. These examples demonstrate how to use a DOM rule in conjunction with an MSG and TOD rule to control outstanding tape mounts.