Re: End a program gracefully even with ENDJOB

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

The challenge is greater when the NEP (never-ending-program) has a 
delay, especially of some length, say, 5 or 10 minutes. We have some 
that check a data area for whether to keep going or to end. That's fine, 
until there's a long wait, as I mentioned.

I'm now checking job status with the active_job_info SQL service - if 
it's other than *DLYW, the job should not be ended. I repeat the check 
every few seconds. Once the job is in *DLYW, I change the data area to 
indicate the job is to be ended and I do an ENDJOB.

I need the data area set, because I don't allow running 2 of the same 
job, so it's used in a startup program.

My issue is that the job is often ended with a 50 severity - not all 
that big a thing, perhaps, but I'd love to have a way for it to end when 
I want it to, and for it to still have a low severity ending.

Cheers
Vern

On 6/3/2021 10:42 AM, Javier Sanchez wrote:
> I'm sure this is an old subject, but I never had the time to implement it.
> I need to have the opportunity to do some graceful updates to a table in a
> looping socket RPG program that will end when it receives an indication to
> terminate.  This updates a flag in a table to report that its status is
> Ended.  So this program does end gracefully.  It also has formal commands
> to start it and to end it.
>
> But when an IPL is needed, the operator simply forgets to issue those
> commands and the ending is abrupt, so the update of the status doesn't take
> place.
>
> I understand that the ENDJOB command for a job running an RPG program would
> send a TERM signal to the program but the default handler (I think) would
> simply force it to end with no chance to run a graceful subroutine that
> does the update.
>
> Can you please give me an example that does this?
>
> Thanks.