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

I'm probably way off base here, but is it possible that the program that
doesn't end right away is something that is sort of locked and isn't "coming
up for air" so to speak? I am guessing here but if a program is kind of in a
lock state or doesn't reach a point where it has to "come up for air", maybe
the endjob *immed can't do it...don't know if this makes sense or not. I'm
sure if that was the reason, well, then you could put something in the
original program that will allow the endjob *immed to sink it's teeth into
it...

Ga

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan
Harris
Sent: Tuesday, July 17, 2018 4:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Is there a way to deliberately block an ENDJOB OPTION(*IMMED)
from functioning?

Logically if the ENDJOB works later then it should work when it is first
issued so it seems to me that either *IMMED is not being specified or the
wrong job is being ended... or some other logical error exists.

I am not aware of anything to block ENDJOB *IMMED requests (that does not
necessarily mean a whole lot) but it seems to me that this would create
some major issues with ENDSBS and PWRDWNSYS processes if this was possible.

For what it is worth, this IBM document describes how to check for *CNTRLD
End requests
http://www-01.ibm.com/support/docview.wss?uid=nas8N1018172

On Wed, Jul 18, 2018 at 9:37 AM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD