hmmmm. If I were you , I would try to check the stack of the pending job
by WRKACTJOB, option 5(work with job) -> 20( show threads) -->10( show
stack of each thread if multiple). Of course , this is a bit technical,
but could help to find which routine is pending there without ending
Gavin, Zhang Gan --
IBM i J9 Team Lead,
Address: 1/F, 28, ZhongGuanCun Software Park, No.8 Dong Bei Wang West
Road, Haidian District, Beijing P.R.China 100193
J9 on i: http://www.ibm.com/developerworks/ibmi/techupdates/java
----- Original message -----
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Sent by: "JAVA400-L" <java400-l-bounces@xxxxxxxxxxxx>
To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>
Subject: RE: ENDJOB for 5250 job which includes a JVM job taking 2 to 3
minutes to end.
Date: Mon, Nov 7, 2016 12:05 AM
Not JVM specific, but:
FWIW, in some cases I've found a *IMMED end takes longer, particularly
with my CGI jobs. I can't say whether the JVM was active or not. I do
make liberal use of JDBC.
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Friday, November 04, 2016 3:21 PM
To: Java400 <java400-l@xxxxxxxxxxxx>
Subject: Re: ENDJOB for 5250 job which includes a JVM job taking 2 to 3
minutes to end.
ENDJOB *IMMED ?
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.