In PDSMAN, the JOURNAL=Y is defined as:
Y Update journaling required. Library update operations are duplicated in the backup library to provide up-to-the-minute recoverability.
The real-time backups of the library are of great value to us with one exception, if the member is deleted from the original library it is deleted from the JOURNAL as well. What we would like to see is the option to keep the backup copies including the +0 generation in the JOURNAL through a user control statement parameter so no information is lost if a member is accidentally deleted from the original library. This would provide us with true "up-to-the-minute recoverability" as implied in the documentation such that we can recover both individual members if they are accidentally deleted or the entire library if it becomes unavailable.
We are using this function for SYS1.PARMLIB as a solution to not having backup members in SYS1.PARMLIB when the members are change, instead using the JOURNAL as a repository for all changes that were made to members in SYS1.PARMLIB. I have also built a REXX/ISPF front end to call PDSM32 and interrogate the JOURNAL for specific members/versions across any of our LPARs, perform SUPERCE compares of different versions in the JOURNAL and perform RECOVER functions from the JOURNAL back into SYS1.PARMLIB should a member need overlayed with the backup in the JOURNAL.
Something as follows:
USER PARAMETER: DELJRNL = Y or N
IF MEMBER-DELETED & DELJRNL = Y
DO NOT UPDATE JOURNAL