No Subject

> John Carr <74711.77@CompuServe.COM> 05/21/97 07:27pm >>>

>RE:    Re: Trigger programs.

>Wouldn't that defeat the whole security thing?   (I think I'll run this 
>DFU, SQL, RPG function with MY trigger program.   Monitoring, We
don't
>need no stinking Monitoring.  )

Security is optional anyway.  I doubt this is the straw that breaks the
camels back.  Qualifying a trigger is a small part of securing you data. 
To change data in a file you need data rights.  To add a trigger you
need object management or object alter.

>Chris Rehm         
>Mr.AS400@ibm.net   
>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.

We do not use triggers at this point so the following may be way off,
however, we intend to start using them now that they have been
made functional in the last release.  Couldn't you still qualify your
library if you are concerned?  If *joblibl was made an option, and a
qualified name could still be specified, how could you beat the trigger
unless you specifically allow *joblibl?  If the trigger calls a program and
the call is not qualified wouldn't it will use *libl anyway?  Could *joblibl
be implemented by having a single trigger program that called the
appropriate trigger.*libl?

David Morris



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