BSTCOPY does not create backout records

Document ID : KB000125389
Last Modified Date : 28/01/2019
Show Technical Document Details
Issue:
Customer has a processor that has an output dataset allocated twice, once with backout=N and the other without. Since upgrading from V18.0.4 to V18.0.12 the step is not producing backout records.  Step from the Processor that is failing: 

//COPYELT EXEC PGM=BSTCOPY,MAXRC=0 
//SYSPRINT DD SYSOUT=*,FREE=CLOSE,SPIN=NO **VALID** 
//SYSUT3 DD SPACE=(TRK,(1,1)) 
//SYSUT4 DD SPACE=(TRK,(1,1)) 
//INDD DD DISP=SHR,DSN=&&SOURCE(&C1ELEMENT) 
//OUTDDN DD DISP=SHR,DSN=PREV.&C1SI&C1SU..&C1TY, 
// BACKOUT=N * ENSURE THE MEMBER IS NOT DELETED ON BACKOUT 
//OUTDD DD DISP=SHR,DSN=PREV.&C1SI&C1SU..&C1TY 
//@100I IF '&C1ELEMENT(1,1)' = 'B' THEN 
//SYSIN DD * 
COPY O=OUTDDN,I=INDD 
SELECT MEMBER=((&C1ELEMENT,,R)) 
COPY O=OUTDD,I=INDD 
SELECT MEMBER=((&C1ELEMENT,,R)) 
/* 
//@100E ELSE 
//SYSIN DD * 
COPY O=OUTDD,I=INDD 
SELECT MEMBER=((&C1ELEMENT,,R)) 
/* 

 
Resolution:
 This is a known problem and is a result of the Dynamic monitoring of data sets.  It may cause an issue with BSTCOPY     
 if the same data set with different DDNAMES and different MONITOR or BACKOUT parameters are used in the same step.                    
                                                                     
 SYMPTOMS:                                                           
 In a BSTCOPY step the where different DDNAMES specify the same      
 data set name and the MONITOR/BACKOUT parameters are different,     
 the wrong parameters may be used.                                   
                                                                     
 IMPACT:                                                             
 The member is copied with the wrong MONITOR/BACKOUT parameters.     
                                                                     
 CIRCUMVENTION:                                                      
 Run BSTCOPY in different steps so that there are not multiple DDNAMES specifying the same data set name.      

Endevor Development/SE is currently working to resolve this problem.