Using Monitors - ironstream_for_micro_focus_omi - 7.2

Ironstream for Micro Focus® OMi for IBM Z® Administration

Product type
Product family
Ironstream > Ironstream for Micro Focus® OMi
Product name
Ironstream for Micro Focus OMi for IBM Z
Ironstream for Micro Focus® OMi for IBM Z® Administration
First publish date

Ironstream for Microfocus OMi for IBM Z provides several system monitors in the shipped product that can be modified for your needs. These monitor policies can also be used as samples for creating additional monitors needed in your environment. To implement one or more of these monitors, update the CPU monitor or DASD monitor policy conditions if desired, or add job information to the job monitor configuration file. Then assign the monitor policy(s) to the OM management server agent. Finally, distribute the monitor policies to the OM management server agent. (Do not distribute policies to the S/390 managed node.) The default monitors provided are:

Table 4-2: Default Monitors




CPU Monitor

Monitors the system CPU of all z/OS nodes defined to OMi. The default policy generates warning messages of increasing severity when CPU utilization exceeds 75, 85, 90, and 95 percent.


Job Monitor

The job monitor policy may be used to monitor for critical jobs that should be active on a mainframe node. The job monitor script uses a configuration file to determine which jobs to monitor and when to monitor for the jobs. If a specified job is not running, a message will be sent to the OMi event browser.

The default configuration file for the job monitor script is:

Linux: /etc/opt/OV/share/conf/vp390/vp390jobmon.conf

Windows: ev390jobmon.conf in the Ironstream configuration directory.

This file must be customized for each installation. The file contains default names for standard WebSphere process names as comments.

Each record (line) in the file must begin in column 1 and have the following syntax:

<jobname> <host> [<starttime> <duration> [<dayofweek>]]



The name of the job/address space that the monitor is to check


The fully qualified name of the mainframe where the job should be active

The remaining parameters are optional and may be used to limit the time frame when the job monitor script will check for the specified job to be active.

<starttime> The starting time for the interval that the monitor script will check for the job to be active. The time must be specified in the format HH:MM:SS

<duration> The duration of time that the monitor script will check for the job to be active. The duration must be a number followed by an "h", "m", or "s" to indicate hours, minutes, or seconds. To specify a duration of eight hours, enter "8h".

<dayofweek> A limit of the number of days in the week to check for the active job. The days are designated by number, with 0=Sunday and 6=Saturday. Multiple days must be separated by commas. To specify Monday through Friday inclusive, enter "1,2,3,4,5".


To monitor JOBA on mainframe during the hours 0800- 1600 on Mondays, Wednesdays, and Fridays, enter the line in the vp390jobmon.conf file:

JOBA 08:00:00 8h 1,3,5

To monitor JOBB on mainframe every day during the house 2200-1000 (crossing midnight to the next day), enter the line:

JOBB 22:00:00 12h


SMS Storage Group Monitor

The SMS Storage Group Monitor policy may be used to monitor SMS storage group utilization thresholds. The SMS Storage Monitor script retrieves details of each storage group and calculates the overall utilization of each storage group. (VIO storage groups are omitted.) The storage group data is passed to the monitor to be evaluated by the monitor conditions. The Object field contains the following information, in order, with each item separated by a colon:

  • Mainframe Hostname

  • SMS Pool Name

  • Pool High Threshold

  • Pool Low Threshold

To check for different thresholds based on mainframe hostname or SMS pool name, create new conditions ahead of the default condition and perform pattern matching on data in the Object field.

To use the SMS Storage Group Monitor, the OSINFO card must be present in the Ironstream IBM Z agent's SYSIN parameter card list.


Monitors the availability of WebSphere MQ managers, status of MQ channels and current depth of MQ message queues. The MQ monitor will checks system configuration data to find configured MQ subsystems and then check availability of those subsystems. For active queue managers the monitor will check status of channels and current depth of queues.

The policy contains three separate conditions for queue manager availability, channel status, and queue depth. Each condition checks information passed by the monitor script such as the queue manager name, channel name, queue name. Custom thresholds can be created by copying these conditions and using pattern matching to create unique conditions for queue managers, channels or queues.