|
Rob, In a message dated 10/9/00 7:04:51 PM Eastern Daylight Time, rob@dekko.com writes: > You're not trying to write to the file in the trigger program are you? > > I'll give you an example. I have a trigger which updates two fields in a > file: TIMESTAMP and USER. The trigger program receives as input the file > buffer, updates these two fields, and sends out the file buffer. There are > no F specs, or SQL in my particular trigger program. If you do a WRITE in > your trigger program to the same file it will reinvoke the same trigger > program, until you stop doing writes to the file associated with the > trigger. <<snip>> Actually, if you specify "Allow Repeated Changes (*YES)" (ALWREPCHG?) when adding the trigger, this scenario should not be a problem... JMHO, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-mail: DAsmussen@aol.com "You could be a liar. You could also be a member of congress. But I repeat myself." -- Mark Twain +--- | 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.