Re: Integrity help?

[DAsmussen <DAsmussen@xxxxxxx>]

Tim,

In a message dated 98-01-06 22:26:43 EST, you write:

> I would like some advice.  I am working with some software that is
>  terrible (alot of atrocious hardcoding) and in this particular instance
>  -- there are many, many jobs that are affecting 1 field in 1 file and I
>  have to identify what program is making a specific change.  (eg)
>  File-CUSTMAST  Field-CSCDE9, one program of many is changing this field
>  from an 'F' to an 'E', I gotta identify the program and maintain my
>  sanity in hardcode village.
>  Should I consider a database trigger program?  Any assistance on doing
>  this appreciated

I prefer using journaling in this instance.  The performance impact is minimal
for a single file (actually, pretty minimal for all files on the new boxes/OS
versions).  Create a journal and receiver, then STRJRNPF (after images only
should be sufficient).  When you've found your culprit, ENDJRN and delete the
journal and receiver.

You can DSPJRN to an outfile, and use a "quickie" RPG program (oh no!  you
_MIGHT_ use the cycle!) that places the data portion of the journal into an
externally defined data structure based on your physical file to locate your
offending program...

HTH,

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

"Governments ruled by people will make war in a fashion that will make wars
waged by kings pale in comparison." -- Sir Winston Churchill
+---
| 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
+---