On 28-Oct-2015 13:58 -0500, rob wrote:
<<SNIP>>
Date sent . . . : 10/28/15 Time sent . . . : 14:48:13
Message . : addlible robdelme


Output from Display Journal (DSPJRN) to reveal that the Library object named ROBDELME was accessed for a Read, per that object having been audited [not per that library having been journaled]:

Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : ZR - Object read access
Object . . . . . . . :
Type . . . . . . . :
Date . . . . . . . . : 10/28/15
Time . . . . . . . . : 14:48:13.432880
...
Job . . . . . . . . : 756649/ROB/ROBS1
F15=Display only entry specific data
*...+....1....+....2....+....3..
'RROBDELME QSYS *LIB ¬

Yes, it does rather grind me that IBM fails to put the object in the
"Object" and "Type" and makes you look in the "Entry specific data".

The "Object" and "Type" are there for another purpose, so to include the data from the T-ZR would be incorrect output.

Those elements of output are there to identify the Object and Type of the /object that is journaled/ to the journal being displayed; i.e. they identify the Object and Type, to which a prior Start Journal Object (STRJRNOBJ) [or STRJRNPF, et al] request had been performed in order to associate that Object to the Journal [being displayed].


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