State of North Carolina

DHHS/DIRM

ENDEVOR Process for Dummy’s

Updated 12/6/2003

 

This document is to assist the DHHS/DIRM Team51 Technical Service Personnel. There are functions described in the following pages that are only applicable to DHHS/DIRM and the PDM developed for its use.

 

 

Installing or Converting to New Version

Create Support files

Create Source and Delta Files

Create Site Information

ENDEVOR Online

Creating System

Creating SubSystem

Create TYPES

Edit Type Information

Create Processor Groups

Edit Processor Groups with Processors

Edit Processor overrides

Create Approver Group

Relate Approver Group

Source Code Promotion

Moving Code from one Stage to another

QuickEdit

Package

Package Functions

Approving

EXECUTING

BATCH

TEC116

Committing

Deleting

Create PDM line

JCL to create a complete PDM line

Library ownership

Processors

Generate

Expand

PreCompile

CICS Translation

Compile step

EXPD

LKED

DB/2 Bind

Store Listing

Print listing

Delete

LOADMODS

Listing

DBRM

Move

LOADMODS

Listing

DBRM

Reconnect

Transferring ELEMENTS from one System to another

Creating a Parallel Development System

COOLGEN and ENDEVOR

Technical Information Bulletin (TIB) Review and Changes

Monitor the ENDEVOR Queue

Test Changes made

ENDEVOR Notification to USERS

DHHS/DIRM ENDEVOR Frequently Asked Questions (FAQ)

DHHS/DIRM ENDEVOR Quick Reference Guide

 

Installing or Converting to New Version

Create Support files

                        MCF File

                        Package File

          Create Source and Delta Files

          Create Site Information

                        Edit C1DFLT51 with Environment Information

 

 

ENDEVOR Online

          Creating System

Each System has a life cycle spanning DEV3STEP and DEV2STEP. The two Environments are connected by a lifecycle Map. A System that is created in DEV3STEP and  Must have a corresponding System in DEV2STEP, Preferable a main repository.

 

          Creating SubSystem

            SubSystems are used to separate the ELEMENTS into Logical Application Systems. Each of the Systems in DEV3STEP will have the SubSystems that are eligible to be worked on within the DEV3STEP System and migrated to the DEV2STEP System. The Code will not be seen by any other DEV3STEP System which does not have the SubSystem defined.

 

          Create TYPES

            Types are defined to separate the source code into Logical categories (i.e. COBOL, COPYBOOK, EZTPLUS, etc) TYPES must be defined in each of the Stages within the Systems lifecycle

 

 

                   Edit Type Information

            The source code is stored using reverse deltaing and non-encrypted format. The default processor group is the most common processor group for this type. *noproc* should never be left as the default processor group. When no processor is needed the name of the TYPE should be used. The source and delta libraries should be specific for the PDM and stage.

 

          Create Processor Groups

 

                   Edit Processor Groups with Processors

 

                   Edit Processor overrides

            The Generate Processor in DEV2USER is the compile step or the assembly step. It must have all of the specific parameters for compile options and special libraries needed to compile and link the code. This will generate an object that will be migrated to the other stages in the life cycle

 

 

          Create Approver Group

            Approver Groups have the TSO IDs that are authorized to approve code to be migrated from one stage to another. The proposed method is to use RACF approver groups and raise the Quorum to 00002. This would eliminate having to maintain TSO IDs in ENDEVOR but would shift the maintenance to RACF.

 

 

                   Relate Approver Group

            Each SubSystem can be defined with a separate approver group, throu the use of the Relate Function.

 

Source Code Promotion

          Moving Code from one Stage to another

                   QuickEdit

                   Package

Package Functions

          Approving

          EXECUTING

                   BATCH

                   TEC116

          Committing

          Deleting

Create PDM line

          JCL to create a complete PDM line

          Library ownership

Processors

          Generate

                   Expand

                   PreCompile

                   CICS Translation

                   Compile step

                                    COBOL

ASM

FORTRAN

                   EXPD

                   LKED

                   DB/2 Bind

                   Store Listing

                   Print listing

          Delete

                   LOADMODS

                   Listing

                   DBRM

          Move

                   LOADMODS

                   Listing

                   DBRM

          Reconnect

Transferring ELEMENTS from one System to another

Creating a Parallel Development System

            Cloning a System and all of it’s components

 

COOLGEN and ENDEVOR

            COOLGEN is not maintained by ENDEVOR Source Management System. However, the process of moving the load modules, DBRM and Bindlib to PROD is done using ENDEVOR. There are 6 MOVE  Processors especially designed to move COOLGEN to the Production Environment. They are:

            COOL3WAY

            COOLXXB

            COOL2XB

            COOLGEND

            COOLGENB

            COOL2XC

            COOLWHOGIVESASHIT

Technical Information Bulletin (TIB) Review and Changes

            Review all TIBs published by ITS and make appropriate changes to the ENDEVOR Systems

Monitor the ENDEVOR Queue

            Monitor the ENDEVOR Queue and respond according to the posted service level

Test Changes made

            Test all changes made in the following areas

            Change System

            Change Processor

            Fix Situation                                        

ENDEVOR Notification to USERS

            When a change is made to any part of the ENDEVOR system that will effect all of the users, a notification must be sent to all DHHS users at the following address: [email protected]

            When a change is made to fix a problem reported by a user, or as a result to a change request for an enhancement. An email must be sent to the individual user and possibly the whole team using that System.

 

DHHS/DIRM ENDEVOR Frequently Asked Questions (FAQ)

            Update the FAQ with frequently asked questions submitted by users with the appropriate answer

                        Document is located at O:/TEAM51/ChangeControl/faq01.htm

                        WebDocument is located on the ENDEVOR WebSite http://dirm.state.nc.us/team51/endevor/faq01.htm

 

DHHS/DIRM ENDEVOR Quick Reference Guide  

            Update the User Guide with changed and new functions

                        Document iis located at O:/TEAM51/ChangeControl/QRG2003.htm

                        WebDocument is located on the ENDEVOR WebSite             http://dirm.state.nc.us/team51/endevor/QRG2003.htm