×
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.
I think you're grabbing at straws. The fact is that your job said:
CPC1165 - SIGTERM signal sent to job 472732/DEVD1/OBNORM01D.
and it said this at 16:55:07.
Then two minutes later (plus 1 second for overhead), at 16:57:08, you got
CPC1166 - Time limit reached for SIGTERM signal handler.
and that points to QENDJOBLMT.
So whether or not this is a JVM job and whether or not they just
'generally take longer' is irrelevant.
Maybe they just generally take longer because no one properly configures
the SIGTERM?
You could try asking the java400 list about these messages.
Or, if this software was provided by some vendor you could ask that vendor
on how to set the SIGTERM settings.
I did some cursory searching for SIGTERM, java on IBM i and so forth. No
java environment variables just screamed out at me but I really don't know
jack about java, let alone java on IBM i, so maybe I just didn't try the
right search terms.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Job taking long time to end - CPC1165, (continued)
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.
midrange.com
