RE: How could a job escape an ENDJOB?

Depending on what went wrong the job could have been ending-- sometimes our HTTP and EDI jobs take a while to end (and start) because they're ending or firing up additional subtasks.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, June 28, 2018 2:14 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: How could a job escape an ENDJOB?

On 6/28/18, 10:43 AM, Jim Oberholtzer wrote:

Mark: Good point. I think Tomcat/Apache can be configured to do just
exactly that.

If so, that's news to me.

As to ENDJOBABN, run and fast from that command unless it is really needed

Thankfully, it wasn't (see previous), but that raises the question of
why it escaped two ENDJOBs in CLLE programs that have worked just fine
in the past, only to be successfully abended by a third, sent from
WRKACTJOB option 4.

Paul:
Good idea with the history log, but the only thing out of the ordinary
was the lack of a message that the CATALINA job had ended (at a time
when it's abundantly clear that it should have ended, but didn't).

--
JHHL