Endevor CONDELE utility deletes the unexpected outputs

Products

• Endevor

Issue/Introduction

The issue arises when running the DELETE action for an element at a specific location.

You observe that the CONDELE utility executed by the delete processor unexpectedly removes outputs that are related to the element at a location other than the one where the DELETE action is executed.

The deleted outputs relate to the location from which the element was previously moved or transferred

Cause

This issue is caused by the BC1PMVCL utility in the move processor copying an unchanged component list to the target stage.

The action (MOVE or TRANSFER) that brought the element to its current location executed a MOVE processor which normally runs the BC1PMVCL utility as its last step 

If the MOVE processor fails to capture new output component information, the move processor does not capture new output component information. This may happen if all the steps that produce output components fail or are bypassed.

In this situation, BC1PMVCL copies the outputs logged in the component list from the source element directly to the component list of the target element.

Consequently, if the target element is later deleted, the CONDELE utility executed by the delete processor will delete the outputs related to the source element. 

Resolution

To produce again the deleted outputs, it is enough to GENERATE the element at the source location so this is normally not a problem.

To prevent this in the future, the MOVE processor may set conditions (COND clauses) in the step that runs the BC1PMVCL utility so that it is skipped if the steps that produce outputs have failed or have not been executed.

Note that, if BC1PMVCL is skipped, the element at the target location will show no component information apart from any input component eventually captured by the MOVE processor.