Re: trigger program question

[CRPence <CRPbottle@xxxxxxxxx>]

  If the files are important enough to enable logging via triggers for 
later review, they are probably important enough to have journaling 
enabled.  And journaling enables transaction isolation which is another 
step forward which is good for important files.

  Look at the output from using the CMPJRNIMG command to see if that 
produces acceptable output for the requirements.  And of course if the 
input to the command for requesting that output is usable.

  There is also the option to copy records from the journal into a 
[likeness of a] temporary version of the file against which a query 
report can be run to provide a report; e.g. STRQMQRY, where each *QMQRY 
could be the query defined against the DSPJRN output file, and accept 
variables to vary the results.

Regards, Chuck

tim wrote:
> <<SNIP>> But the journaling suggestion looks intriguing. I have
> never worked with triggers before. It looks like the journal
> store the entire record and not just the changed field(s).
> So, with that, it looks like I still have to find out what
> changed and be able to display it to the users.
>
> So, trigger or journal, or ???....
>
> Feedback always appreciated...