Interesting. I did not recall that F19 had changed to add that summary feature. Nice. I had gotten frustrated with the changes to the interactive displays and moved to spooled output almost exclusively.

I would still recommend getting WRKJRNA OUTPUT(*PRINT) and DMPOBJ. If nothing obvious in either, then perhaps use the WRKJRN utility to run the diagnostic\cleanup features; sorry, I do not recall what they are, just that some exist.

Regards, Chuck

On 21-Jun-2011 11:25 , Chris Bipes wrote:
WRKJRNA:
Work with Journal Attributes

Journal . . . . : AUTHSYSJ Library . . . . . . : AUTHSYSF

Attached receiver: AUTHSY0022 Library . . . . . . : AUTHSYSF

Text . . . . . . : Journal For Authorizations Base Data

ASP . . . . . . : 1 Journaled objects:
Message queue . : QSYSOPR Current . . . . . : 33
Library . . . : QSYS Maximum . . . . . : 250000
Manage receivers : *SYSTEM Recovery count . . . : *SYSDFT
Delete receivers : *NO Receiver size options: *RMVINTENT
Journal cache . : *NO *MAXOPT3
Manage delay . . : 10 Fixed length data . : *JOB
Delete delay . . : 10 *USR
Journal type . . : *LOCAL *PGM
Journal state . : *ACTIVE
Minimize entry data: *NONE

F19

40. Summary by object type

Summary by Object Type

Journal . . . . : AUTHSYSJ Library . . . . . . : AUTHSYSF

Number of journaled files . . . . . . . . . . . . . . . . . : 16
Number of journaled members . . . . . . . . . . . . . . . . : 16
Number of journaled access paths . . . . . . . . . . . . . . : 0
Number of journaled data areas . . . . . . . . . . . . . . . : 0
Number of journaled data queues . . . . . . . . . . . . . . : 0
Number of journaled integrated file system objects . . . . . : 0
Number of journaled commit definitions . . . . . . . . . . . : 0


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