|
No that's not the problem. The trigger i have, is activated after
a write or update. If the program which made the write or update
operation is closed, or the job has finished, my trigger program
have to do some end-program actions.
The trigger must know "his status".
You have the point ?
I lost a little in the translation of your email. Let me attempt to
rephrase it.
Are you saying you have an SQL write, and if it fails, what effect does it
have on the trigger program?
If this is what you are saying then it becomes important to consider when a
trigger program is called. You can set up a trigger program to be called
before, or after, a write.
I have a trigger which is activated before a write. The reason I have this
is to do some basic referential integrity against some BPCS files. BPCS
uses multiple members (yuck) therefore you cannot use the built in
referential integrity of the 400. I can actually cause the sql write to
fail if I don't feel it has my definition of referential integrity.
If you set up a trigger to be performed after a write then it will never be
called if the write has failed.
Clear? Is this what you asked?
Rob Berendt
==================
Remember the Cole!
"Simmerlein,
Stefan" To: RPG400-L@midrange.com
<S.Simmerlein@gue cc:
nther.de> Subject: Trigger must know his status
Sent by:
owner-rpg400-l@mi
drange.com
03/07/01 02:06 AM
Please respond to
RPG400-L
Hi guys,
a trigger program must do some actions before
it ends.
Example:
SQL-Operation or WRITE/UPDATE Operation on a file
--> TRIGGER
If the SQL, the WRITE/UPDATE Oper. ends the trigger
must do some operations
Is this possible ?
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.