Re: Subsystem monitor job

[Rich Duzenbury <rduz@xxxxxxxxxxxxxxxxxxx>]

I code all my never ending batch jobs to check to see if they have been
ended by someone each time they wake up.  If in a CL, I use RTVJOBA.  If in
an RPG, I use the SHTDN opcode.

If the job finds that it is in an end status, it cleans up as quickly as
possible and ends.  I can't remember ever having a problem caused by any
type of ENDJOB or ENDSBS command over the past fifteen years or so.

At 04:46 PM 1/9/02, you wrote:
>Hi,
>
>I have some server jobs running in their own subsystem and a 'control panel'
>SFL program where you can start, stop, or end each individual server.
>Everything's peachy until someone issues an ENDSBS *IMMED.
>
>Is there a way to capture this and then notify each job to end itself in an
>orderly fashion?  I was reading the manuals and see that a subsystem has a
>monitor job that is in DEQW awaiting incoming commands, presumably on a data
>queue or user queue.  Can I have my own sbs monitor?  What's the name of the
>queue?
>
>Any ideas on how to capture the ENDSBS *IMMED appreciated!