Re: RPG Web Service Architecture

When the database times out, the query ends immediately and control goes back to the calling program.

Basically, the same thing happens with killing the CGI job but it may take a little while to end depending on what was going on when it ended. For example, if you were doing writes or updates and using commitment control, it will roll back uncommitted transactions before ending.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Maurice O'Prey
Sent: Friday, December 12, 2008 2:49 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] RPG Web Service Architecture

Hmmm..

I suppose one could argue that if the database connection is terminated then
it is the hosts responsibility to kill off further processes?. The timeout
exception is thrown immediately once the limit is exceeded but what remains
running via the SQL statement on the iSeries I'm not sure. OK fair point, do
you know the answer?

Maurice


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Haas, Matt (CL Tech Sv)
Sent: 12 December 2008 19:37
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] RPG Web Service Architecture

In the context of using a CGI program, you can set the script time out in
the HTTP server. That will kill the CGI job when it runs longer than the
time you specify.

For general DB access via SQL, you can change some settings in QQAINI (I
know I spelled it wrong) that will put some limits on query execution.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Thorbjørn Ravn Andersen
Sent: Friday, December 12, 2008 2:24 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] RPG Web Service Architecture

Maurice O'Prey skrev den 12-12-2008 17:02:

One nice feature of keeping the responsibility for collecting iSeries
data on the . Net server is the ability to set the command timeout value

So if someone issues an SQL statement that doesn't complete in say 30
milliseconds an exception is thrown and you can inform ( or tell ) the
user to refine their search criteria

Yes. An extra layer is very nice, but you still need to stop the SQL
statement. What is the appropriate way to do that, or must it run to
completion?