Re: CL command to end the current job immediately?

As I recall, *JOBCTL is only needed to do something to somebody else's job.

You always have full control over your own jobs...

Unless somebody specifically removes *PUBLIC *USE from the ENDJOB *CMD...

Charles


On Thu, Mar 1, 2018 at 9:59 AM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

On 2/28/18, 8:02 PM, Roger Harman wrote:

Uh... ENDJOB comes to mind.

Yes, and Larry brought it to my attention off-List. And as I told him, I
can't recall ever using it that way. I think I've occasionally used it as a
fallback for jobs that failed to terminate when asked politely to do so
(e.g., a Tomcat server that ignored a shutdown signal).

It works, and if the job is ending itself, it apparently doesn't need
JOBCTL authority to do so, because I was able to run my test CL program
suite (test1 calling test2 calling test3, which does an ENDJOB *IMMED) just
fine from an account that had a class of PGMR, but no special authorities,
and so presumably no JOBCTL, at least according to
<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72
/rzarl/rzarlusrcls.htm>

Funny thing: last night, I could have sworn that it was leaving an abend
message in the QSYSOPR message queue, but this morning, it definitely is
not.


--
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