RE: Changing triggers

[Chris Bipes <rpg@xxxxxxxxxxxxxxx>]

Front end your triggers with a generic CLP.  Have the CL call the intended
RPG where the real work is done.  You should never have to change the CL and
you can bind to a service program to reduce overhead.  The data base manager
will never lock the service program, only the cl.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


-----Original Message-----
From: Nelson, Jim (RCIS) [mailto:Jim.Nelson@RCIS-NET.COM]
Sent: Monday, March 27, 2000 7: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.

Before we get too deep into this, it would be nice to know if there are any
'gotchas'.  

Has anybody else gone down this road?  Has it worked?  Anything we should
keep in mind?

Thanks, 
JN

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