CA PDSMAN $DEMO batch job abends on S0C1 in step FCOIEXT.

Products

• PDSMAN

Issue/Introduction

CA PDSMAN $DEMO batch job abends on S0C1 in step FCOIEXT and you are running the current maintenance level of CA PDSMAN.

Environment

z/OS

Cause

The $DEMO job runs properly when executing with the active load library being used in the LNKLST.  The SOC1 on the FCOIEXT step occurs when using a STEPLIB to another load library that is not in the LNKLST. Typically, the STEPLIB has some newly applied maintenance and is being used for testing only.  

You cannot add a STEPLIB for the new load library to the $DEMO job and execute the job without the S0C1 occurring. In order to run with a STEPLIB to different modules, you need to start a test CA PDSMAN address space that has the same STEPLIB DD statement. Then you can submit the $DEMO job and it will complete normally.

Note: You will see the following messages in the PDSM19 report: 

WARNING - PDSMCM1 LIBRARY/RESIDENT MODULE MAINTENANCE INCONSISTENT 

 

Resolution

1. In order to run with STEPLIB to different modules, you need to start a test CA PDSMAN address space that has the same STEPLIB DD statement. 

2. The other option you have would be to STOP PDSMAN, copy the load library that has the newly applied maintenance to the LINKLST ahead of the other active load library and refresh LINKLIST, and then start CA PDSMAN. Using this method does not require a STEPLIB for $DEMO.