Re: Trigger programs.

DAsmussen@aol.com said:

> I would hope the LIBL of the job invoking the trigger (since the trigger
> becomes part of that job anyhow).  I work in a large system environment,
> and we test the STEW out of everything before it goes to production --
> with the exception of triggers.  We have been burned more than once by
> trigger programs that either filled the triggering program's job log
> with SEQONLY messages or just plain didn't work right against production
> data.  For obvious security reasons, developers don't have authorization
> to add or remove triggers.

I think it would be a mistake to pull triggers from the "invoking" job's 
libl since that would be a way to beat triggers.

Since the trigger program is supposed to enforce rules having to do with 
the file, there should be only one (per function). That being the case, 
requiring the location be specified seems appropriate. 

Just my two cents.

> Dean Asmussen
Chris Rehm         
Mr.AS400@ibm.net   
You have to ask yourself, "How often can I afford to be 
unexpectedly out of business?" Get an AS/400.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *