RE: Web application and a trigger

["Judy Osell" <judyosell@xxxxxxxxxxxxx>]

There can be some updates initiated by the web application during the day
but the majority of the processing occurs during the nightly feed where
approximately 1,000 get processed.

Judy Osell
763-425-4310

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, March 15, 2007 9:36 PM
To: Midrange Systems Technical Discussion
Subject: RE: Web application and a trigger

Judy,
 
The fact that it's a web app has no real bearing on how the commitment
control will work. Provided the trigger is coded to update the file(s) using
commitment control, it will be in the same commitment boundary, so a commit
or rollback will effect the initial update and the updates from the trigger.
HOWEVER, if the trigger submits a program to batch then that job will have
it's own commitment boundary and will be uneffected by the commit/rollback
of the original (submitting) job. 
 
As for how common it is to use commitment control this way, it's relatively
common if you're talking about validation that occurs between screen
updates. I have seen it used across screen updates (that is, a commitment
boundary that holds uncommitted updates while the user enters data) but I
don't like that approach at all. However, if you're talking about updates
that occur and complete before the control is returned to the user, that's
kind of what commitment control is for. You just do your updates as you see
fit and if something goes wrong it's all undone for you. It's all part of
ACID (http://en.wikipedia.org/wiki/ACID)
 
-Walden
 
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx <mailto:WaldenL@xxxxxxxxxxxxxxx> 
http://www.TechSoftInc.com <http://www.TechSoftInc.com> 
Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems
profound.)