Re: Journaling?

The positive benefit of things like a UDTF is that it is directly usable in SQL - so whether there is misuse with DSPJRN (there has probably always been an issue the first time someone has tried to work with journals, I know it was for me) - it is what we have, and it is a general-purpose tool - not tied to audit journal info.

So maybe one should submit a request for a service over the audit journal specifically.

As t where the documentation is, yes, good information on Knowledge Center - I see you dropped my suggestion of how to find that same information, cést la vie.

Cheers
Vern

On 10/6/2016 11:25 AM, CRPence wrote:

On 06-Oct-2016 10:23 -0500, Vernon Hamberg wrote:

On 10/6/2016 8:13 AM, CRPence wrote:

On 05-Oct-2016 10:04 -0500, Boyle, Doreen wrote:

I'm running dspjrn on QAUDJRN with entry type CA. I don't know
a time frame. I'm a little rusty on using DSPJRN.

The Display Journal (DSPJRN) is not the easiest way to search;
because that feature is so generic, many people will lack the full
understanding. As such, the OS provided the [since deprecated]
command Display Audit Journal Entries (DSPAUDJRNE) later supplanted
by the Copy Audit Journal Entries (CPYAUDJRNE) as a feature for
more directly extracting the /auditing/ details directly from the
QAUDJRN *JRN in QSYS. In the latter, after the output file is
produced with the data, then query [or browse] the data for
relevant records.

For the Journaled file parms I put *ALL for the file and for
Library I put the name of the library I'm interested in knowing
who changed. It's been running awhile, I'm keeping an eye on
disk.

That would be an example of a /misuse/ of the DSPJRN, as an
attempt to get the details of interest :-( Use the CPYAUDJRNE. […]

[…] there is an SQL service that can list journal entries nicely
QSYS2.DISPLAY_JOURNAL is a user-defined table function, and one can
use a WHERE clause to get just what you want. […]

Sure. But coding the inputs to DISPLAY_JOURNAL is much like coding the inputs to DSPJRN. And just repeating the same misuse would be equally frustrating for the same inability to get what is wanted from the journal ;-)

Also, while the docs for those DB2 for IBM i /services/ will originally appear on DeveloperWorks, and feature updates will appear there as well, a particular release should have the /shipped-level/ of that feature documented in the IBM Knowledge Center; e.g.:
[IBM i 7.2->Database->Performance and query optimization->IBM i Services->Journal Services->DISPLAY_JOURNAL table function] (http://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/rzajq/rzajqudfdisplayjournal.htm)