|
The job monitor policy may be used to monitor for critical jobs that should be active on a mainframe node. The job monitor script ev390jobmon.pl uses a configuration file to determine which jobs to monitor and when to monitor for the jobs. If a specified job is not running, an event will be sent to the ServiceNow instance.
The default configuration file for the job monitor script is ev390jobmon.conf in the Ironstream configuration directory on the Windows MID server. This file must be customized for each installation.
Each record (line) in the file must begin in column 1 and have the following syntax:
<jobname> <host> [<starttime> <duration> [<dayofweek>]]
where:
<jobname>
|
The name of the job/address space that the monitor is to check |
<host>
|
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".
|
|
Examples:
To monitor JOBA on mainframe bluebox1.mycom.com during the hours 0800-1600 on Mondays, Wednesdays, and Fridays, enter the line in the ev390jobmon.conf file:
JOBA bluebox1.mycom.com 08:00:00 8h 1,3,5
To monitor JOBB on mainframe bluebox2.mycom.com every day during the house 2200-1000 (crossing midnight to the next day), enter the line:
JOBB bluebox2.mycom.com 22:00:00 12h
|