I am writing an ILE trigger program. I've looked at the samples. However, what I'm trying to do is add an insert trigger to a PF, then have the program take the record that was written, write it to a message queue, write it to an archive PF, and delete the record from the PF that the trigger is over. Is that possible?
No, database locking would prevent the record that "triggered" the trigger to be deleted. The insert trigger, if it was a before trigger, could alter the field values being inserted to a different value like defaults or nulls, so you could make the row look logically deleted. Another idea would be to have the trigger put an entry on a data queue and then have a background job that's responsible for checking the queue and then deleting that new record in the file.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this online event, Getting the Most out of SQL & DB2 UDB for the iSeries.
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.