|
Here's an interesting tidbit... I tested using code shown below: C Eval Counter = *Zero C *Loval Setll RPMAST C Dou Counter = 10 C Eval Counter = Counter +1 C Read RPMAST C Enddo The *loval setll fired the *After *Read trigger !!! No one on our staff (5 other programmers) thought this would happen. I always thought (and confirmed by re-reading the SETLL opcode at the infocenter) that setll doesn't actually read the record. My job shows a zero for the I/O count on the file, but in debug, the buffer clearly shows the contents of the first record in the file. As a result of this test using the above code, the trigger fired 11 times.... Also - I'm at V5R2 and my trigger programs are using the trigger template programs provided by Jon Paris & Susan Ganter from an article found at the following link: http://www.eservercomputing.com/iseries/articles/index.asp?id=169 I been using trigger programs (from these templates) for other stuff with no problems. This is my first use of the *READ activity. Query worked as expected. My file has 1001records, and I ran an interactive query and positioned to the bottom and the triggered fired 1001 times. Film at 11:00. 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.