RE: Trigger program performance

["Alex Moore" <alexm@xxxxxxxxxxxxxxxx>]

Make your trigger program do NOTHING but pass the after update/insert (and
before if necessary) to a data queue.  Use a never ending program to monitor
the data queue, keeping files open as necessary.  Use a unique data queue
entry ( like *SHUTDOWN* ) to shut down the data queue program as necessary.
You could also use a timed wait for data queue entries, monitoring for the
subsystem ending.

>Hi everybody!

>Trigger is calling after update or insert record to transaction file then
it is checking in file A and B for existence, if >>it is ok I retrive info
form file C, D, and if needed E. Current date form F and write out to G and
H. So I have 8 files to >open and close each time the triger is called (less
if I would use UsrOpn of course). I supouse this have strong impact for
>performance of this triger.

>It is beter
>1 to allow the trigger to open and close this files
>2 end trigger with Return instead *InLR ald leave files open to end of job
(there is about 50 jobs posting transactions)
>3 oters ???

>Thanks in advice
>Marcin Sagan

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