Re: Changing triggers

Why can't they have any locks?  What error are you getting?

I don't know what performance implications this might have, 
but perhaps your trigger program could be an opm cl program 
that does a CALL to the real trigger program.





Jim.Nelson@RCIS-NET.COM on 03/27/2000 12:29:53 PM
Please respond to RPG400-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
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
+---