× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.