Re: Interesting Situation

At 09:46 28.03.01 -0500, Mike Silvers wrote:
>I should have put this in before... I was trying to avoid using a trigger
>because of the overhead of the trigger ...
>any other ideas?

Do you have the need to avoid writing of, from your program's point of 
view, unwanted data?
Then you can't avoid the trigger lane.

If you mustn't or don't have to, you can examine journal receivers. But 
that's pretty much overhead, too; probably even more...

If you're only interested in new records, then you could wait for records 
in the file. You just code as always, just override the file with 
EOFDLY(nnn). Then the pgm waits nnn seconds when the file end is reached 
and tries to read new records then. That's not much overhead.

But for both latter methods, you have to do that in another job. The 
trigger has the advantage to run in the same job and is able to throw out a 
window (drawback: one has to avoid that in batch processing!) in the 
session of the person which tried to write the record.
Another job could just send a break message if it knows who wrote the record.



Mit freundlichen Grüssen / best regards

Anton Gombkötö

Avenum Technologie GmbH
Wien - Mattsee - Stuttgart
e-mail Office   :       mailto:Anton.Gombkoetoe@avenum.com
Homepage        :       http://www.avenum.com

Lest das Redbook / read the redbook "Who knew you could do that with RPG?":
http://www.redbooks.ibm.com/abstracts/sg245402.html

+---
| 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
+---