|
More tidbits... I did more testing and found out the following things are happening... Regardless of whether I use *LOVAL or a key to SETLL, the setll does cause the trigger to fire. Under this circumstance, a do loop of 10 reads results in the trigger firing 11 times. If I don't setll and just do the read, the trigger fires multiple times even though only one read operation occurred. I think the DB manager is doing some blocking type stuff that is causing the 'read' type activity. One read caused the trigger to fire 36 times. The subsequent nine reads (in the do loop) didn't fire the trigger. I did one other test, not doing the setll, and I took the K off of the f spec so that it would read in arrival sequence and the trigger fired 39 times... Regards, Jerry Gerald Kern IBM Certified AS/400 RPG IV Developer & RPG IV Programmer MIS Project Leader, Lotus Notes/Domino Administrator The Toledo Clinic, Inc. 4235 Secor Road Toledo, OH 43623-4299 Phone 419-479-5535 gkern@xxxxxxxxxxxxxxxx ***** This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
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.
midrange.com
