After IBM APAR OA60462 receiving PDSM018-5 and PDSM018-12 or PDSMDUPD ERROR, FUNC=08,RC=16

Products

• PDSMAN

Issue/Introduction

We have a three member sysplex running PDSMAN 7.7.  We roll maintenance in on one LPAR before bringing it in on the other two.  After applying the maintenance through 8/20/2021 on the first LPAR, we are having an issue where we are getting PDSM018-5 and PDSM018-12 errors on this LPAR. 

PDSM018-5  UNABLE TO RECORD LAST REFERENCE DATE FOR MEMBER SASERVB  OF dsname
PDSM018-12  UNRECOGNIZABLE USER DATA IS PRESENT IN THE DIRECTORY ENTRY
 UNRECOGNIZABLE USER DATA IS PRESENT IN THE DIRECTORY ENTRY
 DDNAME          PERMANENT I/O ERROR WHEN READING DIRECTORY
 SYNADAF DATA - BC36,D,JOBLIB  ,**- OP,OUT OF EXTENT  ,00001465000000,EXCP
 SENSE/CSW/FAILING CCW  0000/00000000000000/XXXXXXXXXXXXXXXX
UNABLE TO RECORD LAST REFERENCE DATE FOR MEMBER SIMESS   OF dsname
PDSMDUPD ERROR, FUNC=08,RC=16 

 

Just updated with IBM APAR OA60462

various applications that
issue ISITMGD macro can fail with RC04 RSN34 indicating a DEBCHK
error.

Environment

Release : 7.7

Component : CA-PDSMAN for OS/390

Resolution

Recommend IBM APAR OA62138 that replaces OA60462

Error description

• After applying the PTFs for OA60462, various applications that issue ISITMGD macro can fail with RC04 RSN34 indicating a DEBCHK error. 

  ANALYSIS:
  DEBCHK LOCK issued by IGWCIMG2 at UJ06105 is receiving RC4 RSN5
  which indicates the DEB table entry does not point to a DEB or
  the access method type is wrong.
  The DEB is not in the DEB table associated with the TCB that is
  currently running.
  
  PE INFORMATION:
  USERS AFFECTED:
  all users with OA60462 applied that run applications that issue
  ISITMGD macro can be affected if the application is checking for
  data sets that are in STEPLIB DD
  
  USER IMPACT:
  APAR OA60462 fixed the problem it reported but introduced a new
  problem.