|
Dean, 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. -Walden PS. You are journaling your files anyway, right? (Commitment control, disaster recovery, etc.) > -----Original Message----- > From: mcsnet!midrange.com!midrange-l-owner@Mcs.Net > [mailto:mcsnet!midrange.com!midrange-l-owner@Mcs.Net]On Behalf Of > DAsmussen > Sent: Thursday, January 08, 1998 7:31 PM > To: MIDRANGE-L@midrange.com > Subject: Re: Integrity help? > > > 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.