Re: E-mail NO SCANNEABLE Re: Log all PF changes?

A coworker of mine developed a nice little command for querying journals
that has made journal querying so much easier. It basically lets us
specify the file, a date range, and an optional time range. It then
creates a file similar to the DSPJRN outfile, but it also appends the
fields from the journaled file in place of the ENTRY_DATA. This file
structure is built with an SQL join of a DSPJRN template file (with the
JOESD field removed) to the journaled file structure.

Once the DSPJRN to outfile is completed, it does a CPYF with FMTOPT(*NOCHK)
to overlay the journal data into the above built file structure, resulting
in a nice log file.






From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/06/2016 05:07 PM
Subject: Re: E-mail NO SCANNEABLE Re: Log all PF changes?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Sure you can read a journal...

But just try getting
ENTRY_DATA, BLOB(2G), The entry specific data returned for this journal
entry.

Broken up into individual values you can read when dealing with a PF's
journal.

Charles

On Wed, Jan 6, 2016 at 4:41 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Reading a journal is no longer hard - there is now an SQL service -
QSYS2.DISPLAY_JOURNAL - a UDTF that you can just use in any SQL

environment

- very cool!


On 1/6/2016 2:27 PM, Raul A Jager W wrote:

The journal is great, but hard to read for regular users. A timestamp
field with "update as row change" helps to follow changes in the same
record. The journal can not be modified.

I often use a trigger and a journal. The file created by the trigger can
be read by a program easy to use.

Also, you can use a trigger and a program that moves it to a file to
read it and show in an easy program.

____________________________________________________________________
On 01/06/2016 03:21 PM, Justin Taylor wrote:

I need to keep a permanent log of all data changes in a particular PF.
I can think of two ways to accomplish this.

1. A DB2 journal with the receivers set to never expire.

2. A trigger that would write the before images to a separate PF.

I expect questions of "who changed what when" to be a weekly

occurrence.

Either of those options sound better than the other? Anyone have a

door

#3?

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --

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

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



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