× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Rob,

It's ugly...you're still dealing with:
ENTRY_DATA, BLOB(2G), The entry specific data returned for this journal
entry.

And SQL doesn't have the easy to use tools that RPG does for data
structures or packed data.

Charles


On Wed, Jan 6, 2016 at 4:43 PM, <rob@xxxxxxxxx> wrote:

See also this:

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqudfdisplayjournal.htm?lang=en

Anyone use that with something to automate the parsing out the
before/after images?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





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



Just a word of advice...

If you don't currently use journalling, and you want to start journally
for
just this one file...

Then sure, it would make for a quick and easy solution.

However, some things to think about
- How do you intend to display the journal entries? DSPJRN in an of
itself
is not very pretty. The table's data is just one big blob. It gets even
more complex when you have nullable fields and/or MINENTDTA() of other
than
*NONE.
- If you ever need journalling for something else such as commitment
control or HA, then you're going to have problems keeping receivers around
forever.

IMHO, planning on keeping journal receivers around forever is not a good
idea.

Consider instead a program that harvests the journal entries and stores
them someplace.
You may be able to start with the CMPJRNIMG command as laid out here:
http://www.securemyi.com/nl/articles/databaseaudit.html

Personally, if I really _HAVE_ to (for legal reasons) have a record of
changes forever; then I'd be looking at a third party compliance tool.
http://www.helpsystems.com/powertech/products/datathread
http://www.cosynsoftware.com/index.asp?CID=product&PID=CAT

http://townsendsecurity.com/products/file-integrity-monitoring-advanced-tools


http://www.razlee.com/products/security/ap-journal/ap-journal_regulation_compliance_o.php


I'm sure there's more...

Charles




On Wed, Jan 6, 2016 at 1:21 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
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?
--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.