Sounds like a Halcyon enhancement request to me.
Can you create list of jobs that should be running in a table, then have a
CLP use SQL to compare the running jobs (QSYS2 stuff) to the table and send
messages if there is a conflict? To avoid having a program constantly in
delay wait, you could have it self-submit to run again in two hours or
whatever time you want.
As I think it through, that would be a simple CL program or Python task.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Thursday, June 07, 2018 9:46 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: V7R3 - Halcyon Subystem job monitor - determine which job is not
running
V7R3.
I have a Halcyon subsystem job monitor, which triggers if all of the jobs in
the subsystem are not running.
The trigger is determined if the number of jobs falls below X. (X is
currently 50)
I would like to add the alert sent the job name of the job which job is NOT
running, Is there way to determine which job is not running?
One offered solution was to create a separate monitor for every job, doable,
but overkill.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
