Things to consider about Endevor life cycle mapping:
- The entry point into an Environment can be either Stage 1 or Stage 2.
- The exit stage for an Environment must always be Stage 2.
This means that if a stage is eliminated from an Endevor life cycle map, it must be Stage 1 of the Environment.
- First move all the elements out of the stage to be deleted.
- ⇒ In this example, move all elements out of TEST stage 1.
- After the stage is empty, change the C1DEFLTS table to:
-
- In the ENVRNMNT macro of the Environment before the Environment the stage is being deleted from, update the NEXTENV keyword to point to stage 2.
- ⇒ In this example, change the NEXTENV keyword in the DEV ENVRNMNT to (TEST,2).
- In the ENVRNMNT macro of the Environment the stage is being deleted from, update the ENTRYSTG# keyword changing it from 1 to 2
- The Stage 1 keywords: STG1ID= , STG1NME= , STG1TTL= , and STG1VSM= , even though not used, must be defined in the ENVRNMNT macro of the Environment the stage is being deleted from. They can be dummy entries.
NOTE: The MCF data set specified in STG1VSM must be allocated. It can be defined as a one track file.
-
- If necessary, change the STG2NME and STG2ID keywords in the ENVRNMNT macro of the Environment the stage is being deleted from so any Processor logic depending on &C1STAGE or &C1STGID does not have to be updated.
- Assemble and link the updated C1DEFLTS table