Alternatives for OMEGAMON placing messages on the z/OS console

This is a question that comes up fairly often. If OMEGAMON detects an alert or an issue, how can I have OMEGAMON put a message on the z/OS console?

The first thing to be aware of is that the OMEGAMON classic interface task by itself does not have a syslog message command option for when an exception is detected. You will be able to see your desired exception in the the exception analysis screens in classic interface, but you will need to explore additional options to get that exception message on the z/OS console.

There are three primary options to accomplish this:

1- The first is to use the Tivoli portal interface, create a situation alert for the desired exception, and have that situation execute an action command to place a message with the desired information on the console. Any command string entered into the command field will be executed directly to the console. For example, to log a message you could enter LOG 'test message', and 'test message' will appear on the console. Also, be aware that you can use attribute substitution to enter additional information in the command field.

2- If you do not want to use the Tivoli Portal, the next option is classic interface and connect classic to IBM automation. IBM SA automation is able to detect any of the OMEGAMON classic interface exceptions, and can then issue any desired message or command to the z/OS console.

3- If you do not have IBM automation, you can still interface OMEGAMON to non-IBM automation through the XLFOUT mechanism of OMEGAMON. On an earlier post I mentioned a technote that describes the setup and usage of the XLFOUT DD, and how to direct exceptions to XLFOUT.

In a nutshell, those are the 3 alternatives. In general, I think that the Tivoli Portal is the easiest way to go. You can use visual GUI interface, and you can set up actions without having to code any REXX, etc. However, options 2 and 3 are still there, if you desire to go that direction.