Re: How to tell whether the access path of a physical file is being journaled?

For archive reference in case anyone else has this same issue:

Someone on my team found that the WRKJRNA command has an outfile option, which caught me completely by surprise. I don't know that I've ever seen any WRK* command with an outfile option, but here we are. As well, WRK* commands are normally not valid to run in batch, but WRKJRNA is. The command has a DETAIL(*JRNAP) parameter available, so my needs are met.

IBM gives us the DSPJRNRCVA command, but there's no WRKJRNRCVA command.
IBM gives us the WRKJRNA command, but there's no DSPJRNA command.

Weird.

- Dan

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dan Bale
Sent: Sunday, October 27, 2024 2:10 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: How to tell whether the access path of a physical file is being journaled?

Start Journal Access Path (STRJRNAP) help:
If a physical file is specified, journaling can be started for its access paths. When access path journaling is started for a physical file, only the access paths for the physical file members are journaled. Journaling for any logical file access paths is started only when access path journaling is started for the logical file.
*** Also ***
Before journaling an access path, all physical files over which the access path is built must first be journaled to the same journal that is used to journal the access path.
-------------------------
It would seem a PF object can be journaled for both the data (STRJRNPF) and the access path (STRJRNAP). When querying qsys2.journaled_objects, there is no apparent distinction of what is journaled for a PF object. Based on the help text above, if a PF object is found in qsys2.journaled_objects, we are at least assured that the data is being journaled. How does one determine whether a PF object's access path is being journaled?
*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***