Re: Trigger programs.

Pete,

In a message dated 97-05-19 08:23:15 EDT, you write:

> You are correct about both methods. That is, however, precisely the
>  behavior that is required. If a program is doing something that
>  compromises database integrity, it deserves to crash. You need to track
>  down the culprits (at least the critical ones) beforehand and make sure
>  that they follow the rules. Each program that updates or inserts records
>  into the physical file should be identified and examined, especially the
>  ones that run in jobs which may not be easily recovered if an unexpected
>  error message is received. Suspect code can be modified either to force
>  compliance, or allow a graceful recovery. In a large system, this may
>  not be a trivial job, but a system that generates invalid data has
>  little value.

Well done!  I might also note that triggers CANNOT be removed if the file is
open by anybody, and that *LIBL is NOT supported as a location for said
trigger program...

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"People who snore always fall asleep first." -- Anonymous
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *