Re: Integrity help?

Walden,

In a message dated 98-01-10 20:05:16 EST, you write:

> If you know that the program that issues the update is indeed the program
>  that you are interested in, and ALL you want to know is the program name,
>  then I agree, use journaling. BUT, if you need more info, source line # for
>  example, or you are using SQL or common update routines, then you need the
>  trigger. IMHO.

All of our integrity problems have boiled down to knowing the program name.
In structured code, the file is only updated in one place within a given
program.  Agreed on your SQL point, but we (but definitely _NOT_ SSA) try to
avoid using SQL for INSERTS and UPDATES.  I'm not putting triggers down, we
use them extensively.  They're just harder to take off in a 24 hour
environment, and (I feel) they should not be used when a journal will serve
your purpose.

>  PS. You are journaling your files anyway, right? (Commitment control,
>  disaster recovery, etc.)

We are now, after the implementation of Vision's OMS.  Despite my objections,
the client was not using journaling before.  There are still an awful lot of
people out there with the /38 vision of journaling's performance impact on
their minds, and BPCS doesn't use commitment control.  This is sad, as the
main performance impact of commitment control is journaling and many software
packages use journaling already...

IMHO,

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

"Jimi Hendrix was the first rocker on the Internet, his modem was a purple
Hayes."
+---
| 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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---