Re: Is there a way to deliberately block an ENDJOB OPTION(*IMMED) from functioning?

On 7/17/18, 2:30 PM, Evan Harris wrote:

A dumb question perhaps, but what authority does the job issuing the ENDJOB
have ?
What does the job log of the job issuing the ENDJOB show ? Does the ENDJOB
complete successfully ?
Does the ENDJOB definitely specify *IMMED in the program that is not
working ?

As it happens, the ENDJOB is being issued from a scheduled batch job that runs under the same USRPRF as the job being ended, AND which has JOBCTL authority.

And as it happens, I just noticed something about the customer's "belt-and-suspenders" program that scavenges any "to be terminated immediately" job(s) that our program somehow failed to terminate: it's looking for them in the wrong subsystem.

I've corrected that. Maybe that will solve the problem.

The maddening thing about this is that it's intermittent.

--
JHHL