RE: Changing triggers

One of the software vendors I work with has done this.

What they did was to build a generic trigger program, which they reference on 
the ADDPFTRG command. The generic trigger when activiated writes it's data to 
file.  A batch job waiting on the same file with an end of file delay then 
refers to a table to determine which program(s) should be called to re-signal 
the trigger.

Of course, the generic trigger program has to be well thought out, and 
including extra program calls to re-signal the trigger does have a performance 
penalty.  

AFAIK, these triggers are only *AFTER style triggers, just intended to let 
another application or interface know that a record had been 
added/changed/deleted.  

This setup was written in RPG III
Regards,
Rich

-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of Nelson, Jim (RCIS)
Sent: Monday, March 27, 2000 9:20 AM
To: 'MIDRANGE-L@midrange.com'
Subject: Changing triggers


In our development environment, we are changing SOME trigger on SOME file
almost daily.  To make such a change, the file that trigger is based on must
not have any locks.  This has become unworkable with the number of
developers and functional test people involved.

We are talking about creating completely generic triggers to call a stored
procedure which will either run the activity intended or call one or more
other stored procedures.  When a change was needed it would be made to that
front-end stored procedure.

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