CA - ENDEVOR Course Mechanics • Course Type: Facilitated • Course Notes: –If training is Facilitated, Notes are located in the Notes View. (Please see View Master/Notes Master to see the Notes View.) –If training is Self Paced, Notes are located in Slide View. • This course is best viewed in Slide Show Mode. You can download this course to your desktop (if desired) for printing and note taking. • Length of Course: 8.0 hours. • Course Audience: Mainframe Resources CA-ENDEVOR ENVIRONMENT LEVEL STAGE TYPE 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 Unit Test Prod Model Office Fix Prod MAP Test Test Prod Hold Fix Prod MAP Test Test Prod 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 WIP Stage 2 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 x 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 PGMX Level 0 (Changes Only) Full Copy REVERSE DELTAS PGMX Level 4 Level 3 Full Copy Level 2 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) • Groups inventory • 15 bytes • Account specific MASTER CONTROL FILE (MCF) ENDEVOR Environment WIP Stage 1 Stage 2 Stage 1 MCF 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 ‘FINARP01’ FROM ENVIRONMENT ‘DEMO’ SYSTEM ‘FINANCE’ SUBSYSTEM ‘ ACCTREC’ TYPE ‘ COBOL’ STAGE Q OPTIONS CCID ‘001’ COMMENTS ‘Move to Production’ . SUMMARY ENDEVOR B D A C SUMMARY ENDEVOR B Environment C SUMMARY ENDEVOR B Environment Stage 1 C Stage 2 D SUMMARY ENDEVOR Environment Stage 1 Stage 2 D Stage 1 MCF A Stage 2 MCF SUMMARY ENDEVOR Environment WIP Stage 1 Stage 2 Stage 1 MCF 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 SUMMARY Look at the handouts and Match the term with the correct definition. C1DEFLTS Map Delta Master Control File WIP Automatic Consolidation Change Control Identifier SCL SUMMARY Look at the handouts and Match the term with the correct definition. F E B H A C D G C1DEFLTS Map Delta Master Control File WIP Automatic Consolidation Change Control Identifier SCL The END ENVIRONMENT LEVEL STAGE TYPE