Re: V7R3 - Halcyon Subsystem job monitor - determine which job is not running

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Paul

There is a ton of message data information from CPF1164 that is not 
visible when looking at the message itself. It is in the WHST* physical 
files, however, and I think the Work Management documentation tells you 
the layout - might have the subsystem info in it.

Cheers
Vern

On 6/7/2018 10:53 AM, Steinmetz, Paul wrote:
> Brainstorming, I thought of another method.
>
> Check QHST for CPF1164, then if the job that ended matches one of the jobs from the susbsystem, send the alert.
> What would really be nice if IBM included the subsystem name as an additional variable on the CPF1164.
> Then you would only have to check CPF1164 ending from subsystem X.
>
> Any chance IBM could add the subsystem name to the CPF1164?
>
> Thanks
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Musselman, Paul
> Sent: Thursday, June 07, 2018 11:30 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: V7R3 - Halcyon Subsystem job monitor - determine which job is not running
>
> Paul--
>
> We wrote our own monitor, but we just check min/ideal/max jobs in the subsystem.  The subsystem only runs jobs from 1 application, so any deviation is an issue to be dealt with.  If the number of jobs isn't perfect, we want to know.
>
> Our process uses 2 programs-- first is our 'RTVSBSINF' command, which is a wrapper for the QWDRSBSD API.  This is a 'nice' API, and doesn't require a User Space.  The second program we call SBSRUNCHK.  It uses the RTVSBSINF command and sends a lot of messages if the number of jobs running isn't correct.  It also checks to make sure the SBS is running in the first place!
>
> Paul E Musselman
> PaulMmn@xxxxxxxxxxxxx
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
> Sent: Thursday, June 07, 2018 10: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/