CA Endevor Integration for the Natural Environment › The Natural Development Lifecycle › How to Configure a Natural Lifecycle in CA Endevor SCM

How to Configure a Natural Lifecycle in CA Endevor SCM

You must configure CA Endevor SCM to enable it to control the Natural development process. The Natural administrator and the CA Endevor SCM administrator need to work together to complete this task. To configure CA Endevor SCM to control Natural development, complete the following steps. These steps assume that CA Endevor SCM is already set up at your site. If this is not the case, see additional configuration requirements described in the CA Endevor Software Change Manager Implementation Guide and the CA Endevor Software Change Manager Administration Guide.

1. Identify the stages in the development lifecycle of your Natural code that you want to put under control of CA Endevor SCM.
2. Group the stages into environments, with two stages in each environment and one VSAM master control file for each stage.
3. Define the promotion route that inventory travels through the lifecycle, by mapping the stages in the C1DEFLTS table.
4. Create CA Endevor SCM libraries. See How to Create CA Endevor SCM Base, Delta, and List Libraries.
5. Update the Optional Features table (ENCOPTBL) to activate the CA Endevor Integration for the Natural Environment option. For more information, see Edit, Reassemble, and Relink ENCOPTBL.
6. Define site symbolics.
   1. Define site symbolics to associate each CA Endevor SCM stage to a specific FUSER/FDIC combination. You can use either the supplied sample JCL SITESYME, which provides a sample set of definitions, or SITESYMT, which is a template for definitions. For more information, see Associate Each CA Endevor SCM Stage to a Specific Natural FUSER/FDIC Combination.
   2. Define site symbolics to associate your Natural libraries to CA Endevor SCM locations. For more information, see Methods of Associating Natural Libraries to CA Endevor SCM Inventory Locations.
7. Set up the environments: assemble and link C1DEFLTS; assemble and link the Symbols table; and allocate the CA Endevor SCM VSAM master control files.
8. Define your systems. Identify functional groupings for your Natural applications, such as Finance applications, Tax applications, and so on. Define a system for each functional group and define each system to each environment in which you plan to use it. Define processor load and listing libraries for each system at both stages in an environment. These libraries can be shared across systems and environments.
9. Allocate the processor load and listing libraries, with one load and one listing library for each stage. For more information about allocating processor load and listing libraries, see the CA Endevor Software Change Manager Administration Guide.
10. Define your subsystems. Decide which Natural libraries and Predict files you want to manage in CA Endevor SCM. Define a subsystem for each Natural library, with at least one subsystem for each system. For example, your Finance system could have a subsystem for accounts payable (ACTTPAY) and one for accounts receivables (ACTTREC).
11. Create the CA Endevor SCM inventory and the Type PROCESS. Create a batch job that defines the systems, subsystems, and the Type PROCESS.
12. Edit the sample processors provided in the Processor Template data set. Add the processors to CA Endevor SCM using the sample JCL DEFPROC. For more information about installing processors, see Install the Processors.
13. Edit your type and processor group definitions and create them in CA Endevor SCM using the sample JCL DEFTYPE. For more information, see Define the Natural and Predict Types.
14. Enable Global Type Sequencing to define the sequence in which types are processed. You must use the supplied JCL member ETYPESEQ to order the Natural types. For more information, see Enable Global Type Processing.