Re: Integrity help?

[Bob Larkin <blarkin@xxxxxx>]

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 (-:
>

Tim,
Avoid triggers! At least in this instance. Especially since any error in the
trigger program could make CUSTMAST unusable to ANY programs, until the error is
corrected. Triggers can be very useful, but you need a bulletproof trigger
program.

Journalling will find that deviant program in a flash. Create a journal receiver
and a journal. STRJRNPF on CUSTMASST. I would chose the *BOTH option for journal
images. This will give both before and after images for all updates.

At anytime after this, you can use the DSPJRN command to place the journal
entries into an outfile. The Entry Specific Data field will contain the record's
data as a single string. Scan the records by calculating the offset for the
desired field and looking for the "E". It sounds more complicated than it is.

If you have DBU, then there is a command (DBUJRN I think) that will display the
journal data as individual fields using the CUSTMAST field definitions.

Anyway, once you find the offending update, the journal entru will provide you
with the program name, user, job info, date, time, just about anyhing you need.

Two warnings. If there is a lot of update activity, you might want to use the
CHGJRN command with *GEN to create a new journal (It will add 0001, 0002,
0003,...to the journal receiver name). Once this is done, you can analyze the
previous journal and delete it.
Also, don't forget to end journalling once the problem is fixed.

If this rambling is too much, give me a call at (281)931-3100 x225 or a page at
(713)786-6166

HTH,
Bob Larkin



+---
| 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
+---