Re: Integrity help?

[DAsmussen <DAsmussen@xxxxxxx>]

Walden,

In a message dated 98-01-08 17:20:03 EST, you write (in part):

<<snip>>
> Having said that, I would create a trigger program that checked for the
>  change in the field, and when the change occurs I would record everything I
>  can. At a minimum I would do a dspjoblog output(*print) and a dspjob
>  output(*print). You may even want to consider checking if the current job
is
>  an interactive job and if so, pop up a window and ask the user to enter a
>  brief (unlike this email) description of what they are doing. The dspjob
>  will show you the entire call stack, and the dspjoblog is always nice to
>  have.
<<snip>>

Well bud, you "missed it by _that_ much" ;-).  I was about to ask you to
explain how triggering was superior to journaling based on your first
(snipped) paragraph, but agree that, if you are using API's to update the
database, being able to dump job information would be very helpful.  If you're
_NOT_ using an API, journaling is still superior, IMHO.

Regards!

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

"Everywhere is walking distance if you have the time." -- Steven Wright
+---
| 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
+---