Re: Aborting write with a trigger program

Hello Jim,

Monday, October 09, 2000, 11:02:16 AM, you wrote:

> V3R7M0

> There is a situation where if a blank record is inserted into out of our 
>physical files it totally throws our entire system out of whack.  This should 
>never happen as there is supposed to be
> validation against the data in the entry programs, but it has happened (3 
>times in the last 6 years).  It just happened a week ago and I had to fix it 
>(by deleting the blank record).

> What I am going to do is to add a trigger program on *INSERT *BEFORE and if 
>the key information is *BLANK I want to abort the write.  Also if possible I 
>want to generate a program error so that the
> program attempting to write or update the data to blank bombs out.

> I am looking in the online book OS/400 DB2 for OS/400 Database Programming 
>V3R2 and read the entire section dedicated to triggers, but really didn't see 
>how to abort the write.

Well as I write this there are no replies to your message so...

What you need to do is send an *ESCAPE message back one invocation
level and whaa laa you have both the insert being aborted and your RPG
program gets an error on the write which if you are not monitoring for
will stop you dead in your tracks!

Hope that helps
Eric


+---
| 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
+---