Re: Integrity help?

[John & Barb Brooker <brookerj_b@xxxxxxxxxx>]

If you use a trigger, think about what you are going to capture to track
down the bad program--maybe the user?  Getting to the program name is
not easy.  

One thing we did to the inventory transaction file, is attach a trigger
to catch bad dates.  If the date was bad, the trigger pgm wrote a record
to an error log file-same layout as the original file with a user and
date-time stamp fields added.  This may be enough info in your case to
track down the program (based on the user), and you would just write out
your 'E' records to the error log.

One trick my boss has done (but you need to add code to each pgm) is
find a place for one char, like an empty field, or at the end of a not
used for much field (lots of legacy files have unused space).  Then id
each pgm by a character & add it as records are updated or added.

just my ideas...and 1st post in the midrange-l

barb 

Tim Truax wrote:
> 
> Hello all,
> 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
> --
> :-) Tim & Dana Truax (-:
> 
> +---
> | 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
> +---
+---
| 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
+---