Re: Web application and a trigger

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm not sure how common it is, but I do that quite often myself. It's
very handy for rolling back any and all updates. The trigger will
normally run in the same commitment group as the job. I think SQL
triggers do that automatically. With SQLRPGLE trigger programs, you
compile with commit *NONE, and they will automatically do the same
thing. With legacy file IO in RPG trigger programs, you need to open any
RPG files with commitment (there's an F-Spec switch for that). You can
do that conditionally based on a commitment indicator in the trigger buffer.

Pete Hall
pbhall@xxxxxxxxxxxxx
http://pbhall.us


Judy Osell wrote:

I'm working with an application that updates tables via the web.  The web
application is using commitment control to back out any updates/inserts to
the table if an error is found during validation.  I've never seen
commitment control used in this way.  Is this a common use of commitment
control?  

 

To make it more complicated there is a trigger on the file that the web
application is using.  Is there any way the web application and the trigger
can share the same commitment control?  I don't want the trigger to run if
the web application does a roll back.  The trigger is activated when a row
is inserted into the table and a program is submitted to batch to continue
processing.  The batch program also uses commitment control. 

 

 

Judy Osell



 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF+fDnpcZsDl8OX6kRApdSAJwIsBQWlNfOaZYkqSSfdA2UDFV9jgCgm5yE
MqS1HfB2/2zwhMzKS2xmqLo=
=Lewb
-----END PGP SIGNATURE-----