If the CGI programs are compiled into activation group *NEW, I think
this will take care of the problem and also perform slightly better than
ending the CGI jobs. Also, if they are using SQL, you can specify "WITH
NC" on the queries which will not lock files (it also performs better
since there's no commitment control overhead). If SQL is not being used,
the programs will need changed so locks aren't done on I/O operations.
If Net.Data is involved, there's a setting you can put in the INI file
to default commitment control to *NONE.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of albartell
Sent: Thursday, August 16, 2007 7:36 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: [WEB400] Ending job immediately after RPG is done
Hi all,
Does anybody know if there is a way to end an Apache job immediately
after
the RPG CGI program is done running? I am working with somebody where
this
would be a hack for sure, but would solve the problem they have of not
being
able to get locks on files during the night. I don't know the full
breadth
of the situation, just that nightlies are hanging and it is because of
the
CGI jobs.
I told them that even if Apache could do this (because I am still not
sure
if it can) that there would be some performance lost because of new jobs
constantly needing to be created. That was an ok tradeoff vs. having to
get
a call at 3am because a file lock is holding up nightlies.
Thanks in advance for any replies,
Aaron Bartell
http://mowyourlawn.com
midrange.com
