RE: Time limit reached for SIGTERM signal handler.

The only thing I can imagine is that the job was in a section of code
that defers interrupt requests. I've seen this when trying to cancel
certain interactive jobs (like building an index on a new LF).

I guess I wonder why you force option(*immed). If you wrote this
application, is it really very difficult to test the %shutdn flag and
use option(*CNTRLD), so that you end your job at a known exit point?
Forcing jobs to end immed might cause them to terminate in the middle of
a transaction, or right before a commit, or whatever... You can still
make use of CEERTX to clean up resources.

-Eric DeLong

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of hockchai Lim
Sent: Friday, March 25, 2011 10:30 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Time limit reached for SIGTERM signal handler.

hello all,
I've just created a brand new RPG program that will call the CEERTX to
register the Cancel handler at runtime. The main function of this new
RPG
program is to update/add record to a table in a mysql database (using
JDBCR4
by Scott, of course).

Everything has been working fine. When the job is being ended
(option(*IMMED)), the cancel handler is being called to do the cleanup
task.
But, last night, something strange happened. When the job was being
ended
last night (option(*IMMED)), the job did get ended. But in the Operator

Message Queue, I'm getting error below:

Message ID . . . . . . : RNQ0202 Severity . . . . . . . : 99
Message type . . . . . : Inquiry
Date sent . . . . . . : 03/25/11 Time sent . . . . . . :
08:42:44

Message . . . . : The call to PROCESSTHI ended in error (C G D F).


When reviewing the log, I also see this:
CPC1166 Completion 50 03/25/11 08:44:30.105304
QWTMETMR
QSYS 019E *EXT
From user . . . . . . . . . :
QSYS
Message . . . . : Time limit
reached
for SIGTERM signal handler.
Cause . . . . . : Job
009075/PALHC/BLWGINTCMP did not complete during the
time allowed. An immediate end
job
request was issued by the system. The
time limit was 120 seconds.
Recovery
. . . : If the time limit of 120
seconds is not enough time for
the
SIGTERM signal handler to complete,
contact your system administrator
to
increase the time allowed by the
QENDJOBLMT and QPWRDWNLMT system
values.

The reason I'm getting the RNQ0202 appears to be cause by this CPC1166
error.


I've done cancel handler on several production programs before and has
never
enconuter this. Any idea why?

thanks