Source and Target environment control block in EXIT2 and EXIT3 at Generate.

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench
• CA 2E

Issue/Introduction

The Source and Target Environment block contents will differ depending on whether the Element exists at the FROM location of the GENERATE SCL.

Resolution

The Source and Target Environment block contents will differ depending on whether the Element exists at the FROM location of the GENERATE SCL.

Whether option NOSOURCE or COPYBACK is used does not influence the behavior.

Two main cases can be distinguished at Generate:

The Element exists at the FROM (target) location ; in this case (in-place) the Source Environment control block ($ENVDS) will reflect the FROM location. The Target environment control block will also reflect this (same) location at Exit Point 3. It will not be populated at Exit Point 2.

The Element does NOT exist at the FROM location; in this case the Source environment block will reflect the inventory location where the element is Fetched from, and the Target environment block will reflect the FROM clause in the Generate SCL statement. This is the case at both the Exit Point 2 and 3.

EXAMPLE:

Given Environments DEV and PROD .

At the EXIT Point 3 (C1UEXT03, after action) these will be the contents presented;

ELM1 exists at PROD/2, and DEV/1; GENERATE ELM1 FROM DEV/1 OPTION COPYBACK.
SRC-ENVIRONMENT-BLOCK will be DEV/1
TGT-ENVIRONMENT-BLOCK will be DEV/1
ELM1 exists at PROD/2 only; GENERATE ELM1 FROM DEV/1 OPTION COPYBACK
SRC-ENVIRONMENT-BLOCK will be PROD/2
TGT-ENVIRONMENT-BLOCK will be DEV/1

At the EXIT Point 2 (C1UEXT02, before action) these will be the contents presented;

ELM1 exists at PROD/2, and DEV/1; GENERATE ELM1 FROM DEV/1 OPTION COPYBACK.
SRC-ENVIRONMENT-BLOCK will be DEV/1
TGT-ENVIRONMENT-BLOCK is not (yet) populated.
ELM1 exists at PROD/2 only; GENERATE ELM1 FROM DEV/1 OPTION COPYBACK
SRC-ENVIRONMENT-BLOCK will be PROD/2
TGT-ENVIRONMENT-BLOCK will be DEV/1