Plan C.
No longer using QHST and CPF1164.
Created a new work file containing each job that runs in the subsystem.
Then using the HALCYON performance subsystem monitor,
When it triggers, I created a HALCYON substitution variable, JOBNOT.
JOBNOT calls my usrpgm, reading work file, which uses TAATOOL CHKACTJOB cmd.
If the job is not running, CHKACTJOB returns TAA9893.
The logic will find and concatenate the job names.
Resulting alert.
PENCOR05 - Not all 50 jobs running for subsystem Interface, ADRINBOGUS,ELECT not running
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, June 12, 2018 2:29 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V7R3 - Halcyon Subsystem job monitor - determine which job is not running
I found another work around.
I found two control files that contain the job name for all the jobs in the subsystem.
I will create a Halcyon QHST monitor for CPF1164.
Once triggered, I will match the job name from the CPF1164 to the job name in either of the control files.
If I get a match, send the alert.
Working on the SQL for the match.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, June 12, 2018 1:37 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V7R3 - Halcyon Subsystem job monitor - determine which job is not running
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=121160
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, June 12, 2018 1:34 PM
To: Midrange Systems Technical Discussion
Subject: RE: V7R3 - Halcyon Subsystem job monitor - determine which job is not running
Paul,
We're kind of lazy. It helps to get votes if you provide the direct link.
Rob Berendt
midrange.com
