RE: commitment control scope

[Marco Facchinetti <facchinetti@xxxxxxxxx>]

Take a look in the "Multitherad Application" chapter 3,
database consideration... in the section about "server mode
for SQL" and "committable transaction".
I don't know if it apply to you situation but since the
main program starts with a that commitment controll...

hth
Marco
--- Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxx> wrote:
> Because the driver program is the main program that
> starts the entire suite of applications, changing the
> commit scope for this program is probably out of
> question.  As you mentioned it might have other
> ramifications.  (I probably should have insisted to set
> the commit scope to actgrp when we did the ILE
> conversion.  Oh, well, too late now.)
> 
> The service program will always rolbk after calling PGMA.
>  All this service program interests in is the AR/AP
> amount.
> 
> The service program is creating temp AR/AP file in QTEMP.
>  However, I can delete them without rolbk or commit first
> (Getting some type of pending transaction error).  The
> other problem with this method is that PGMA also update
> quite a few  other production files that I'll have to
> condition it to not updated them.
> 
> 
> Lim
> 



                
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail