|
Pending Replies and Job Run Time
JobRescue was given two new features in version 6.1F. These features allow monitoring
of:
Monitoring Pending Console Replies
JobRescue can monitor for console replies that are pending, and if not responded
to after a configured time period execute a command file. The command file can perform
most any function, such as emailing, sending tell messages, etc. The command file
executes as part of the JobPak job.
To configure this feature, sign on as MGR.NSD and run the CONFIGIX.JPAK program.
Then navigate to Global Values -> Miscellaneous System Values. You should
see a screen that looks something like this:

At the bottom of the display, the last three fields are used to configure the reply
monitoring feature. In this example you can see that the command file REPLY2.XEQ
is executed every two minutes, after the initial waiting period of one minute. Each
console reply that has not been answered will have REPLY2 executed when the reply
reaches an age of one minute.
There is an example command file named REPLY.EXAMPLE.NSD that is part of
the 6.1F distribution. This file is only an example and should be customized to
fit your purposes. When you do customize it, remember to leave the "parm" line at
the beginning of the command file. Here's what REPLY.EXAMPLE.NSD looks like:
parm replyId=0,replyText=""
TELLOP REPLY !replyID "!replyText" IS WAITING!!!
TELLOP REPLY !replyID "!replyText" IS WAITING!!!
TELLOP REPLY !replyID "!replyText" IS WAITING!!!
TELLOP REPLY !replyID "!replyText" IS WAITING!!!
If you want to do something special with the command file, like use JobRescue's
email program to send an email or text message to your phone, just email or call
us and we'll be happy to help you set it up.
Monitoring Job Run Times
JobRescue can also monitor the run times of running jobs on your system. It can
then execute a command file when the parameters you specify are exceeded. This may
be individualized so that you can have a different command file for each job you
want monitored.
To configure this feature, sign on as MGR.NSD and run the CONFIGIX.JPAK program.
Then navigate to JobSpecific Values and select the Job Specific entry you
wish to configure. If you do not have an entry that matches the job you wish to
monitor, then press F1 to add it.
Open the Job Specific entry and navigate down the menu list to the last item, Job
Timers & Notification.
You should see a screen that looks like this:

The fields, in order are:
- Command file name
- Elapsed minutes
- CPU seconds
- Wait minutes
- Execute period
Command file name is the filename of the command file to be executed when
the job exceeds any of the specified parameter values. The threshold condition that
caused the command file to be executed is passed as a parameter to the command file.
There is an example below.
Elapsed minutes is the number of minutes that when the job runtime exceeds
this value the command file is executed.
CPU seconds is the number of seconds that when the accumulated job CPU time
exceeds this value the command file is executed.
Wait minutes is the number of minutes the job has been in a wait state, or
the unbroken period of time that the job has not consumed any more CPU time. When
this value is exceeded the command file is executed.
Execute period is the number of minutes that JobRescue waits after initially
executing the command file to execute it again.
There is an example command file named TIMERS.EXAMPLE.NSD as part of your
distribution that is shown below. Note the "parm" line and the values passed to
the command file by JobRescue.
PARM jobNum,jobName="",jobUser,jobAcct,logonDate,logonTime,msg=""
TELLOP #J!JobNum !msg !!!!
TELLOP #J!JobNum !msg !!!!
TELLOP #J!JobNum !msg !!!!
TELLOP #J!JobNum !msg !!!!
The parameter msg passes the reason for the execution of the command file.
The reasons may be:
- EXEC MINS x EXCEEDS MAX MINS y
- CPU SECS x EXCEEDS MAX SECS y
- WAIT MINS x EXCEEDS MAX MINS y
Where both x and y are the actual and configured values, respectively.
And again, if you want to do something in particular with a command file and you're
not sure how to go about it, we're here to help, just email or call us.
Thanks for using JobRescue!
|