Endevor Basics: Environment Type Level

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 42

ENDEVOR BASICS

ENVIRONMENT

LEVEL TYPE

STAGE
OBJECTIVES

• Define ENDEVOR terminology


• Explain the ENDEVOR inventory
structure
ENVIRONMENT

Environment

An ENDEVOR Environment is a


phase of the life cycle through
which a software change
migrates.
Examples:
 Test
 Production
STAGES

Environment
Stage 1 Stage 2
STAGES

Test
Test Hold
MAP

A map defines the life cycle routes


which software can take. Maps are
pre-defined as routes between Stages.
MAP

Test Prod
Unit Model Fix Prod
Test Office
MAP

Test Prod
Test Hold Fix Prod
MAP

Test Prod
Test Hold Fix Prod
WORK IN PROGRESS
(WIP)
WIP

• Edits are performed in the


WIP
• Partitioned Data Set (PDS)
• Tracks library and member
name
WORK IN PROGRESS
(WIP)
ENDEVOR
Environment

Stage 1 Stage 2
WIP
LOGICAL INVENTORY
STRUCTURE

Made up of Environments, Stages, and


the following:

• System Name
• Subsystem Name
• Type of Inventory
• Element Name
ENDEVOR DIAMOND
STAGE

SYSTEM

TYPE SUBSYSTEM

ELEMENT
SYSTEM
STAGE

SYSTEM
SYSTEM

A System often represents an


application that the account
maintains.

Examples:
 Banking
 GMVMVOM
SUBSYSTEM
STAGE

SYSTEM

SUBSYSTEM
SUBSYSTEM

A Subsystem provides for a


further breakdown of the
logical groupings of inventory
that make up a System.

Examples:
 Accounts
Receivable
 DBA
TYPE
STAGE

SYSTEM

TYPE SUBSYSTEM
TYPE

A Type describes characteristics of


the inventory.

Examples:
 COBOL
 C2YL
 C2PTD2
 P2PID2
 JCL
ELEMENT

SYSTEM

TYPE SUBSYSTEM

ELEMENT
ELEMENT

An Element is the actual name of the


inventory item.

Examples:
 COBPRG1
 PL1DB2P3
ELEMENT LEVELS

Level 4
Level 3
Level 2
Level 1
Level 0
FORWARD DELTAS

Level 4
Level 3
Level 2
Level 1 Deltas
(Changes Only)
PGMX
Level 0
Full Copy
REVERSE DELTAS

PGMX
Level 4
Level 3
Level 2 Full Copy

Level 1 Deltas
Level 0 (Changes Only)

Level 0
Automatic Consolidation

PGMX LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
Automatic Consolidation

PGMX LEVEL 0
LEVEL 1 PGMX LEVEL 0
LEVEL 2
LEVEL 3 LEVEL 1
LEVEL 4 LEVEL 2
LEVEL 5 LEVEL 3
CHANGE CONTROL IDENTIFIER
(CCID)
CCID
Copybook
Program ABC
A

Change
Request #1

• Groups inventory
• Account specific
MASTER CONTROL FILE
(MCF)
ENDEVOR
Environment Stage 1
Stage 1 Stage 2 MCF
WIP

Stage 2
MCF
C1DEFLTS TABLE

• Client Specific
• Updated outside ENDEVOR
• Defines Software Life Cycle
Map
SOFTWARE CONTROL
LANGUAGE (SCL)
SCL

• Specific to Endevor
• Ability to perform multiple
requests with 1 submission
• Standard format
• Easy to learn
SOFTWARE CONTROL
LANGUAGE (SCL)
MOVE ELEMENT ‘COBPGM01’
FROM ENVIRONMENT ‘DEMOTEST’
SYSTEM ‘FINANCE’
SUBSYSTEM ‘ ACCTREC’
TYPE ‘ COBOL’
STAGE H
OPTIONS
CCID ‘001’
COMMENTS ‘Move to Production’
.
SUMMARY

ENDEVOR
B
D
C
A
SUMMARY

ENDEVOR
B Environment

C
SUMMARY

ENDEVOR
B Environment D

Stage 1 Stage 2
C
SUMMARY

ENDEVOR
Environment D
Stage 1
Stage 1 Stage 2 MCF
A

Stage 2
MCF
SUMMARY

ENDEVOR
Environment Stage 1
Stage 1 Stage 2 MCF
WIP
A

Stage 2
MCF
SUMMARY
What is the logical inventory structure?
SUMMARY

SYSTEM
SUMMARY

SYSTEM

SUBSYSTEM
SUMMARY

SYSTEM

TYPE SUBSYSTEM
SUMMARY

SYSTEM

TYPE SUBSYSTEM

ELEMENT
The END

ENVIRONMENT

LEVEL TYPE

STAGE

You might also like