It could be possible other jobs were slowing down the systems so therefore the java would also run slow.
If your team wrote the java code, possibly add some logging logic to the app perhaps and viola - joblog ?
All things being equal it was probably some other job or jobs slowing things down if this job has been consistent.
Also on the scheduling front you may want to put something in place to flag completion of the java job before other jobs kick off.
Of course HelpSystems has options for scheduling and system monitoring, but minimally I would re-consider simply time based kickoffs.
Regards,
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn
------------------------------
message: 6
date: Fri, 19 Feb 2016 21:32:13 +0000
from: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
subject: Java 1.6 batch performance issue
We have a batch job that uses Java 1.6 get info from a remote server.
Normally the process takes 1 1/2 hours.
This morning it took 2 hours 15 minutes, 45 minutes longer.
Other processes were dependent on the timely completion of this info.
Because its Java, joblog does not help.
What tools can be used to troubleshoot/isolate this issue?
Anything in MPG?
8205-E6C 740
1.5 CPU
155gb mem
100% SSD
V7R1 Latest CUM, TR11, most latest groups
Java Group 23
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
