CA Endevor BSTCOPY gives an erroneous message that return code 0 is greater than the max rc

Products

• Endevor Software Change Manager (SCM)
• Endevor Software Change Manager - Natural Integration (SCM)
• Endevor Software Change Manager - ECLIPSE Plugin (SCM)
• Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

After upgrading our Endevor software to V18.0.11, a processor that has worked for years now abends with the following message on the listlib:

   PROCESSOR STEP INFORMATION                                                 **         **                            ALLOCDS .......RC=0000                                                   **         **                            LNKINC  .......RC=0004                                                   **         **                            LNKINC  .......RC=0004                                                   **         **                            CONWRITE.......RC=0000                                                   **         **                            EXPANCPY.......RC=0000                                                   **         **                            COMPILE .......RC=0000                                                   **         **                            XPDITOR .......RC=0000                                                   **         **                            LINK    .......RC=0000                                                   **         **                          **DVL8COPY.......RC=0000  > MAXRC                                          **         **                          **DVL8COPA.......RC=0000  > MAXRC                                          **         **                            STORE   .......RC=0000                                                   **         **                                                     

What is causing the problem and how do we fix it?              

Environment

Release:
Component: ENDBAS

Resolution

The problem was caused by the FOOTPRNT=CREATE in the BSTCOPY steps was specified on the INDD DD statement:

The following two DD's the jcl was defined as:

//INDD    DD  DSN=&LOADSRC,DISP=SHR,MONITOR=&MONITOR,
//            FOOTPRNT=CREATE
//OUTDD   DD  DSN=&LOADTGT,DISP=SHR,MONITOR=&MONITOR

 

When the FOOTPRNT=CREATE was moved to the OUTDD, everything worked correctly.

//INDD    DD  DSN=&LOADSRC,DISP=SHR,MONITOR=&MONITOR
//OUTDD   DD  DSN=&LOADTGT,DISP=SHR,MONITOR=&MONITOR,
//            FOOTPRNT=CREATE