RE: Exit Point for COMMIT?

I don' think there is a where to do this at the trigger level.  However, below 
is one solution that one of our application used (not a perfect solution 
though).

1)Trigger program write to a temporary file.
2)Create a never ending job that read the temporary file and chain (with lock) 
back to the original file and do the following:
  If not found, delete the record.
  If record lock, try to chain again.
  If chain successful, do what ever that you need to do.
  Note: Make sure you start the commitment control at *CHG level when running 
this job.
 




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Squires
Sent: Friday, February 11, 2005 1:13 PM
To: 'rpg400-l@xxxxxxxxxxxx'
Subject: RE: Exit Point for COMMIT?


I wish to call a new (trigger) program when journalled file changes are
committed rather than at the point of update.  Does anyone know of an exit
point at which this could be done?
 
Many thanks in advance, 
 
Anthony 



 


-- 
Internal Virus Database is out-of-date.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.5 - Release Date: 26/12/2004
 
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.