|
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. Any suggestions? Regards, Jim Langston +--- | 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-2024 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.