Do you have objects that need to be journaled for your recovery plan or high availability system to work correctly? What if all the objects you think are being journaled are really not? If you can easily identify the objects that are not being journaled, you can correct the problem and get your plan back on track.

You can always use the WRKJRNA (Work with Journal Attributes) command to look at the attributes of a journal so you can determine which objects ARE being journaled to a specific journal. But what about when you hope all files are being journaled and you really just need confirmation?

Well, the command you need is PRTJRNRPT (Print Journal Report), which will not only tell you what objects are NOT being journaled, but will also tell you what IS being journaled. The command allows you to specify a library name, (*LIBL, *CURLIB, etc.) and allows you to specify if you want a list of journaled, or non-journaled objects, the object types you are interested in, and the report order, such as Object Order, Library/Object order, or Journal order.

Using the command will submit a batch job that will print the report. The batch job attributes are based upon the Job Description and Output Queue parameters.

                        Print Journal Report (PRTJRNRPT)

 Type choices, press Enter.

 Object library ....... MYLIB     Name, *LIBL, *CURLIB...
 Object type  ......... *ALL      *ALL, *FILE, *DTAQ, *DTAARA
 Report type  ......... *NOTJRN   *JRN, *NOTJRN
 Printing order ....... *LIBOBJ   *LIBOBJ, *OBJ, *JRNLIB...
 Job description ...... *USRPRF   Name, *USRPRF
    Library  .......... ________  Name, *LIBL, *CURLIB
 Output queue ......... *CURRENT  Name, *CURRENT, *JOBD, *USRPRF
    Library  .......... ________  Name, *LIBL, *CURLIB

The following source code included is:

CBX943H     PNLGRP    Print Journal Report
CBX943V     CLP       Print Journal Report - VCP
CBX943X     CMD       Print Journal Report
CBX9431     CLP       Print Journal Report - CPP
CBX9432     RPGLE     Print Journal Report - CPP

See each source member for compile instructions and see the help panel group for additional documentation.

You can download a zip file containing all the source code here [2].

This article is adapted from Carsten's article from 2005.