Re: Track all records read from a table

Getting human-readable data out of a journal isn't hard-- and it's the
ONLY place on the system where you can guarantee that some human can't
change things! Once our auditors understood that, they were content with
our using DBU to fix data base issues (with proper permission to use the
utility).

The big 'issue' with reading journals is that they have to be translated
back to human form. You DSPJRN to an outfile, then CPYF th a specially
formatted DB file FMTOPT(*NOCHK) et voila! Data in human readable form,
with the date, time, and user of the journalled transaction.

The formatted file consists of: (a) the journal fields as defined in one
of IBM's manuals (timestamp/user/etc.) plus (b) all of the fields that
define the normal PF on the system, in the same order. Then that CPYF
FMTOPT(*NOCHK) moves all the data into the right places (ignore the 'error'
that the end-of-record doesn't line up). Then read that file to find out
who did what to whom.

And the evidence is as irrefutable as you can get on the iSeries. Just
train your auditors!

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.