When an Endevor element is Moved to the next stage, the load module is not getting deleted from the Source library

Products

• Endevor

Issue/Introduction

Normally, when an Endevor element is promoted to the next stage, the member is deleted from all the libraries in the From location. 

The Delete processor is being executed after the Move was done but one of the load modules are not being deleted. 

What can be the problem?

Environment

All supported versions of Endevor

Resolution

The Delete processor contained an IF statement checking &C1ACTION:

//       IF  (&C1ACTION = 'DELETE')  THEN          
//*                                                
//DELTIT EXEC PGM=CONDELE,                       
//       MAXRC=&RCODE,                             
//       PARM='&C1ELEMENT'                         
//*                                                

 

For Move actions, the Delete processor is being executed as part of the Move action so &C1ACTION will resolve to MOVE  - not DELETE. 

With this IF statement coded, the IF condition is False for Move actions and the DELTIT step is not executed. 

The DELTIT step will only be executed for DELETE actions. 

If this step is to be executed when elements are Moved, remove the IF  (&C1ACTION = 'DELETE')  THEN   statement and corresponding ENDIF statement and regenerate the Delete processor.