+PDSM03-5 PROGRAM OBJECT LIBRARY BYPASSED, DSN=dsname

book

Article ID: 206498

calendar_today

Updated On:

Products

CA PDSMAN

Issue/Introduction

Sometimes when running PGM=PDSM03. We have to reallocate the PDSE before rerunning the job to get the job to run. Note : that the allocated file is empty. Earlier in the day we saw a job that issued the following during an IEBCOPY ;-

+IEW2606S 4B39 MODULE INCORPORATES VERSION 3 PROGRAM OBJECT FEATURES AND CANNOT     
+         BE SAVED IN LOAD MODULE FORMAT.                                           
PDSM021-6  UPDATE JOURNALLING FAILED FOR MEMBER SQ01     OF dsname      
PDSM021-7  BINDER ERROR DURING COPY TO JOURNAL LIBRARY                              
PDSM021-22  BINDER SAVEW    ERROR. RETCODE=00000012 REASON=83000422 MEMBER=SQ01     

How do we stop this from happening? 

 

 

Environment

Release : 7.7

Component : CA-PDSMAN for z/OS

Resolution

The PDSM03 program does not support PDSEs. You will have to remove the PDSEs from the archive. This link to documentation on how to use the archive and restore facility to clean out the entries that need removed.

Link: https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-pdsman-pds-library-management/7-7/using/member-archiving-and-recovery-facilities/archiving-and-recovery-system-examples.html

Once you remove the Object library you will stop seeing the errors.

Also, the error on the Journaling:

If you are working with a PDSE then the Journal file must be a PDSE as well.

In addition;  you do not need to remove the libraries from the PDSMINIT if you do not want to. The $ACCESS and $UPDATE rules still work for PDSEs.