OK, today I have a question about an SQL trigger on a DB2 file.
Customer has a table they want to put a trigger on. That all works.
And the trigger simply does an insert to another table.
However as soon as they added his trigger, the end-user programs (Old RPGII interactive rpg programs) that use the table in question experienced lock-wait conditions.
They are potentially still in the same order doing work once the trigger goes off.
When a trigger goes off I thought it just received an image of the record (similar to a journal entry).
This RPGII program does multiple reads, but it also appears to release the records after each read.
Anyone have thoughts on why a trigger could cause the downstream programs to suddenly lock up waiting on records once a trigger is added.
Input appreciated.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
This mailing list archive is Copyright 1997-2026 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.
midrange.com
