Re: Commitment control and triggers

["HauserBirgitta" <Hauser@xxxxxxxxxxxxxxx>]

Hi,

A trigger is nothing else than a program that is called by the database 
manager, whenever the event (insert, update, delete) specified in the 
trigger definition occurs. This program is implemented in the call stack and 
can be considered as any other program called from the caller program.

If you started commitment control with commitment scope *JOB there is no 
problem to rollback. If you didn't change the default value for commitment 
scope from *ACTGRP to *JOB, a rollback will only performed for the current 
active activation group. If you let SQL start the commitment control it is 
started with commitment scope *ACTGRP. As long as you do not have a real 
ILE-environment, you'll get problems if the caller and the trigger program 
run in different activation groups.

Mit freunlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les 
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)




----- Original Message ----- 
From: "Bob P. Roche" <BRoche@xxxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, November 14, 2006 20:33
Subject: Commitment control and triggers


> I am adding commitment control to a program that updates a file. There is
> a trigger on the file to write tracking records to a different file
> whenever a change is made. Is there a way to get the trigger to rollback
> it's changes when I use the ROLBCK opcode in my program?
> --
> 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.