The Natural Development Lifecycle

The Natural administrator and the 
CA Endevor
® SCM administrator must work together to design and implement a Natural lifecycle. This task includes the following steps:
ce18
The Natural administrator and the 
CA Endevor
 administrator must work together to design and implement a Natural lifecycle. This task includes the following steps:
  • Implementation of a Natural development lifecycle.
  • An element classification scheme.
  • The definition of the physical data sets in
    CA Endevor
    to enable
    CA Endevor
    to manage the Natural development process. 
 
CA Endevor
 identifies Natural objects (also known as elements) according to the logical structure implemented at your site. All elements have a fully qualified name which consists of environment, stage, system, subsystem, type, and element name. Each element is defined by the following classifications:
  • Location in the software lifecycle. Location is determined by the environment and stage where the element resides. When you modify an application, elements move through the software development lifecycle. The elements reside in different functional locations at different times. The functional areas such as Test, QA, Production, and Backup are defined as an environment and stage combination. The location of an element is part of the identification of that element.
  • Inventory classification. The inventory is determined by the system, subsystem, and type with which the element is associated.
A physical data set structure must be set up at your site to support your logical structure. 
 
 
2
 
 
How to Configure a Natural Lifecycle in 
CA Endevor
 
You must configure
CA Endevor
to enable it to control the Natural development process. The Natural administrator and the
CA Endevor
administrator work together to complete this task. To configure
CA Endevor
to control Natural development, complete the following steps. These steps assume that
CA Endevor
is set up at your site. If not, see the configuration requirements that are described in the
CA Endevor
Implementation Guide and Administrating.
 
Follow these steps:
 
  1. Identify the stages in the development lifecycle of your Natural code that you want to put under control of 
    CA Endevor
    .
  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. 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.
  5. Define site symbolics.
    1. Define site symbolics to associate each
      CA Endevor
      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
      Stage to a Specific Natural FUSER/FDIC Combination
      .
    2. Define site symbolics to associate your Natural libraries to
      CA Endevor
      locations. For more information, see Methods of Associating Natural Libraries to
      CA Endevor
      Inventory Locations
      .
  6. Set up the environments:
    1. Assemble and link C1DEFLTS. 
    2. Assemble and link the Symbols table.
    3. Allocate the
      CA Endevor
      VSAM master control files.
  7. Define your systems. Identify functional groupings for your Natural applications, such as Finance and 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.
  8. 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 Administrating.
  9. Define your subsystems. Decide which Natural libraries and Predict files you want to manage in
    CA Endevor
    . 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).
  10. Create the
    CA Endevor
    inventory and the Type PROCESS. Create a batch job that defines the systems, subsystems, and the Type PROCESS.
  11. Edit the sample processors that are provided in the Processor Template data set. Add the processors to
    CA Endevor
    using the sample JCL DEFPROC. For more information about processor installation, see Install the Processors.
  12. Edit your type and processor group definitions and create them in
    CA Endevor
    using the sample JCL DEFTYPE. For more information, see Define the Natural and Predict Types.
  13. 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.
How to Create 
CA Endevor
 Base, Delta, and List Libraries
To implement an inventory structure for
CA Endevor
Integration for the Natural Environment, you must define and allocate base, delta, and list libraries. The base, delta, and processor load and listing libraries are used during
CA Endevor
execution. Base libraries store the original or current source version of an element. Delta libraries track the differences between the numerous source levels of an element. The processor load and listing libraries of a System hold the executable form of the processor (load) and a listing of the compile that is run for each processor. You can have multiple occurrences of the libraries, usually one set of libraries for each stage. For more information about base, delta and list libraries, see Administrating. The following steps are required to create the
CA Endevor
base, delta, and list libraries.
  1. Allocate data sets for the
    CA Endevor
    base and delta libraries for your Natural element types. Define the PDS data sets with an RECFM value of VB and an LRECL value of at least 256. Ensure that you use your site naming conventions. All Natural element types can share a single pair of base and delta libraries.
  2. Allocate data sets for
    CA Endevor
    base and delta libraries for your Predict element types, if you are using
    CA Endevor
    Integration for the Natural Environment to manage Predict types. Ensure that you use your site naming conventions. Define the PDS data sets with a RECFM value of VB and an LRECL value of at least 1796. All Predict element types can share a single pair of base and delta libraries.
  3. Allocate list libraries. Ensure that you use your site naming conventions. Natural and Predict elements can use list libraries that are defined for other element types, but you can define separate list libraries. We recommend that within any given
    CA Endevor
    stage, all Natural elements, and Predict elements use the same list library.
Edit, Reassemble, and Relink ENCOPTBL
To activate
CA Endevor
Integration for the Natural Environment, you must edit the Optional Features table (ENCOPTBL). As delivered, this option is turned off.
 
Follow these steps:
 
  1. Find the ENCOPTBL in use at your site. This table is delivered in the 
    iprfx.iqual.
    CSIQSRC library. To verify the table in use at your site, look in your site C1DEFLTS table. The table should be defined using the OPTTBL=parameter.
  2. Find the following line in ENCOPTBL: ENHOPT EINE_ACTIVE=ON and uncomment the line. To find this option in the table, you can go to the command line and type F 'EINE_ACTIVE' and press Enter.
  3. Use the JCL member BC1JTABL in the 
    iprfx.iqual
    .CSIQJCL library that is delivered with the product to reassemble and relink ENCOPTBL.
    The ENHOPT_EINE ACTIVE parameter is now active in your ENCOPTBL. This is a requirement to enable the
    CA Endevor
    Integration for the Natural Environment option.
How to Add Site Symbolics to Associate Natural with
CA Endevor
The
CA Endevor
site symbolics facility enables you to define global symbols. You can use these global symbols in type and processor definitions to reference data set name specifications for base, delta, source output, include libraries, and processors. Symbolics simplify maintenance, because these commonly referenced data sets can be defined in a single location.
 
Follow these steps:
 
  1. Define site symbolics.
    1. Define site symbolics to associate each
      CA Endevor
      stage and Natural development system to a specific FUSER and FDIC combination. You can define a maximum of 99 sets of these site symbolics. For more information, see Associate Each
      CA Endevor
      Stage to a Specific Natural FUSER/FDIC Combination
      .
    2. Define site symbolics to associate your Natural libraries to
      CA Endevor
      locations. For more information, see Methods of Associating Natural Libraries to
      CA Endevor
      Inventory Locations
      .
  2. Use the JCL member BC1JSYMT to create the site symbolics table.
  3. Define the site symbolics table in C1DEFLTS using the SYMBOLTBL= parameter to define the table name.
Associate Each
CA Endevor
Stage to a Specific Natural FUSER/FDIC Combination
You must add a set of
CA Endevor
Integration for the Natural Environment site symbolics to
CA Endevor
for each distinct Natural FUSER/FNAT/FDIC set that is to be accessed by
CA Endevor
. The
CA Endevor
Integration for the Natural Environment site symbolics are used by the Natural and Predict processors. The symbolics are also used by the
CA Endevor
Integration for the Natural Environment batch job submission facility. Because a stage is directly associated with a specific Natural FUSER/FNAT/FDIC set, each stage must have a corresponding set of
CA Endevor
Integration for the Natural Environment site symbolics. Also, you must add a set of
CA Endevor
Integration for the Natural Environment site symbolics for each specific Natural FUSER/FNAT/FDIC set associated with any development environment that needs to be accessed by
CA Endevor
Integration for the Natural Environment for add or retrieve actions. These development Natural FUSER/FNAT/FDIC sets are not necessarily associated with a stage.
To associate each
CA Endevor
stage to a specific Natural FUSER/FDIC combination, define the following set of site symbolics for each distinct Natural FUSER/FNAT/FDIC set that is to be accessed by
CA Endevor
. You can edit the template for $ESYMBOL definitions that are provided as JCL member SITESYMT and the sample set of $ESYMBOL definitions that are provided as JCL member SITESYME.
Each set of
CA Endevor
Integration for the Natural Environment site symbolics must contain the following symbol names with all symbols in the set sharing a common symbol-set suffix:
 
SYMNAME=#FUSER#X,
 
 
SYMDATA=(
xxx
,
yyy
)
 
Where 
xxx
 is FUSER DBID and 
yyy
 is FUSER File number, for example, (002,029).
 
SYMNAME=#FDIC#X,
 
 
SYMDATA=(
xxx
,
yyy
)
 
Where 
xxx
 is FDIC DBID and 
yyy
 is FDIC File number, for example, (002,032).
 
SYMNAME=#ADALOAD#X,
 
 
SYMDATA=
Adabas_load_library
 
 
Name of the ADABAS load library that is used in batch access to the site symbolic set FUSER and FDIC combination, for example, ADAvrs.LOAD.
 
SYMNAME=#NATLOAD#X,
 
 
SYMDATA=
Natural_load_library
 
 
Name of the Natural load library that is used in batch access to the site symbolic set FUSER and FDIC combination, for example, NATnnn.LOAD.
 
SYMNAME=#NATNUC#X,
 
 
SYMDATA=
Natural_batch_nucleus
 
 
Name of the Natural batch nucleus that is used in batch access to the site symbolic set FUSER and FDIC combination, for example, NATnnnBA.
 
SYMNAME=#NATPARM#X,
 
 
SYMDATA='
NATPARM
 
 values
'
 
Any site-specific NATPARM values that are used in batch access to the site symbolic set FUSER and FDIC combination, for example: PARM=PRM002BA,IM=D,INTENS=1,MAXCL=0,MADIO=0,MT=0
 
SYMNAME=#DDCARD#X,
 
 
SYMDATA='
DDCARD
'
 
A literal string of valid ADARUN parameters that are used in batch access to the site symbolic set FUSER and FDIC combination, for example: ADARUN MODE=MULTI,SVC=221,DEVICE=8390,DBID=002.
This symbol name is optional if a value is defined for #DDCARDD#X.
For more information, see ADABAS DDCARD Format.
 
SYMNAME=#DDCARDD#X,
 
 
SYMDATA='
DDCARDD
'
 
The name of the data set used for either a PDS member or a PS file. The SYMDATA must be set to a null value if #DDCARD#X is specified.
 
SYMNAME=#DDCARDM#X,
 
 
SYMDATA='
DDCARDM
'
 
The name of the PDS member. The SYMDATA must be set to a null value if #DDCARD#X is specified or a PS file is specified in the #DDCARDD#X.
 
SYMNAME=#LISTLIB#X,
 
 
SYMDATA='
list_library
'
 
Name of the List library that is defined for elements in the stage that is associated with the above FDIC, FUSER combination, for example, CA.NDV.CASCM.TEST.NAT.LISTLIB. This symbol can be omitted if the
CA Endevor
Integration for the Natural Environment Site Symbolic set is not related to a stage.
ADABAS DDCARD Format
Specify the ADABAS DDCARD information in one of three ways:
  • An inline literal string such as ADARUN MODE=MULTI,…. If this format is used, then you must code #DDCARD#X and null values in SYMDATA for #DDCARDD#X and DDCARDM#X.
  • A sequential dataset (PS). If this format is used, then you must code the data set name in #DDCARDD#X and null values in SYMDATA for #DDCARD#X and #DDCARDM#X.
  • A member in a PDS. If this format is used, then you must specify the name of the PDS in #DDCARDD#X and the member name in #DDCARDM#X and set #DDCARD#X SYMDATA to null values.
 
Example: Site Symbolics Defined in BC1JSYMT
 
This example shows part of a BC1JSYMT JCL member that has been edited to include a typical
CA Endevor
Integration for the Natural Environment site symbolics set.
$ESYMBOL SYMNAME=#FUSER#T,SYMDATA=(002,029) $ESYMBOL SYMNAME=#FDIC#T,SYMDATA=(002,032) $ESYMBOL SYMNAME=#ADALOAD#T,SYMDATA=ADAvrs.LOAD $ESYMBOL SYMNAME=#NATLOAD#T,SYMDATA=NATnnn.LOAD $ESYMBOL SYMNAME=#NATNUC#T,SYMDATA=NAT316BA $ESYMBOL SYMNAME=#NATPARM#T, SYMDATA='PARM=PRM002BA,IM=D,INTENSX=1,MAXCL=0,MADIO=0,MT=0' $ESYMBOL SYMNAME=#DDCARD#T,SYMDATA='' $ESYMBOL SYMNAME=#DDCARDD#T,SYMDATA=Adabas.SOURCE $ESYMBOL SYMNAME=#DDCARDM#T,SYMDATA=DDCARD $ESYMBOL SYMNAME=#LISTLIB#T, SYMDATA='CA.NDV.CASCM.TEST.NAT.LISTXLIB'
Methods of Associating Natural Libraries to
CA Endevor
Inventory Locations
Your Natural libraries must be mapped to
CA Endevor
inventory locations using site symbols. Select one of the following methods depending on whether your Natural library names follow a naming convention:
Both methods require the following symbols:
 
SYMNAME=#NSRCLIB,
 
 
SYMDATA='
source_Natural_library
'
 
Name of the source Natural library from which Natural objects are moved. The symbolic uses the following
CA Endevor
symbolics to identify the source Natural library.
  • &C1SENVMNT(1,1) – first character of the environment name
  • &C1SSTGNUM – stage number (1 or 2)
  • &C1SSUBSYS – subsystem name
 
SYMNAME=#NTGTLIB,
 
 
SYMDATA='
target_Natural_library
'
 
Name of the target Natural library when the following actions are performed: delete, generate, or move. The symbolic uses the following
CA Endevor
symbolics to identify the target Natural library.
  • &C1EN(1,1) – first character of the environment name
  • &C1S# – stage number (1 or 2)
  • &C1SU – subsystem name
Associate Natural Libraries that Conform to a Naming Standard to
CA Endevor
Inventory Locations
Map your Natural libraries to
CA Endevor
subsystems with a direct method of symbolic substitution, provided you use a standard naming convention for your Natural libraries. The following method lets you define your Natural libraries to
CA Endevor
locations, using standard
CA Endevor
location symbolics.
 
To associate Natural libraries that conform to a naming standard to
CA Endevor
Inventory Locations
 
Define the symbolics #NTGTLIB and #NSRCLIB, to assign Natural libraries that conform to a standard naming convention. Use one of the formats shown next--either the environment, stage number and subsystem, or the subsystem only.
  • Define the symbolics using the environment, stage number, and subsystem:
    $ESYMBOL SYMNAME=#NTGTLIB, SYMDATA='&&C1EN(1,1)&&C1S#&&C1SU' $ESYMBOL SYMNAME=#NSRCLIB, SYMDATA='&&C1SENVMNT(1,1)&&C1SSTGNUM&&C1SSUBSYS'
  • Define the symbolics using the subsystem only:
    $ESYMBOL SYMNAME=#NTGTLIB, SYMDATA='&&C1SU' $ESYMBOL SYMNAME=#NSRCLIB, SYMDATA='&&C1SSUBSYS'
The names of the Natural libraries depend on the code format you use. The names are assigned directly by the symbol values which use:
  • Either the first character of environment name with the stage number and subsystem name 
  • The subsystem name alone. 
No additional site symbols are required.
 
Example: Associate Natural Libraries to
CA Endevor
Inventory Locations Using Direct Symbolic Substitution
 
This example uses a direct method of symbolic substitution to associate Natural library names to
CA Endevor
locations. Direct Symbolic Substitution assumes that the site lifecycle is configured as follows:
  • It has two environments (QA and PRD) and four stages (two stages in each environment) in the following order:
    QA/1 -> QA/2 -> PRD/1 -> PRD/2
  • The subsystem name is NSUB for all stages.
Define the following site symbolics in your site symbol table (double ampersands are required in the site symbol table):
$ESYMBOL SYMNAME=#NTGTLIB, SYMDATA='&&C1EN(1,1)&&C1S#&&C1SU' $ESYMBOL SYMNAME=#NSRCLIB, SYMDATA='&&C1SENVMNT(1,1)&&C1SSTGNUM&&C1SSUBSYS'
Therefore, the symbolics resolve to the following libraries:
  • At QA stage 1, &#NTGTLIB and &#NSRCLIB resolve to Q1NSUB as your Natural library name.
  • At QA stage 2, &#NTGTLIB and &#NSRCLIB resolve to Q2NSUB as your Natural library name.
  • At PRD stage 1, &#NTGTLIB and &#NSRCLIB resolve to P1NSUB as your Natural library name.
  • At PRD stage 2, &#NTGTLIB and &#NSRCLIB resolve to P2NSUB as your Natural library name.
Associate Any Natural Libraries to
CA Endevor
Inventory Locations
You can map your Natural libraries to
CA Endevor
inventory locations using an indirect method of symbolic substitution, if your Natural library names do not follow a standard naming convention. The following method lets you define your Natural libraries to
CA Endevor
locations, using standard
CA Endevor
location symbolics and recursive symbol substitution.
 
Follow these steps:
 
  1. Define the symbolics #NTGTLIB and #NSRCLIB using recursive symbol substitution. You can use the following $ESYMBOL definitions that are provided as JCL member SITESYME to associate any Natural library name to a
    CA Endevor
    location.
    $ESYMBOL SYMNAME=#NTGTLIB, SYMDATA='&&#N&&C1EN(1,1)&&C1S#&&C1SU' $ESYMBOL SYMNAME=#NSRCLIB, SYMDATA='&&#N&&C1SENVMNT(1,1)&&C1SSTGNUM&&C1SSUBSYS'
    The #NSRCLIB symbolic indirectly defines the source Natural library from which Natural objects are moved. The #NTGTLIB symbolic indirectly defines the target Natural library when the following actions are performed: delete, generate, or move. The symbols resolve to a series of other symbols, defined using the #N
    xysubsys
     symbolic, which you must also code in your site symbol table.
  2. Define one #N
    xysubsys
     symbolic for each stage and subsystem combination that you want to control using
    CA Endevor
    .
    $ESYMBOL SYMNAME=#N
    xy
    subsys, SYMDATA='Natural_library_name'
    •  
      #N
      xysubsys
       
      x - first character of the environment
      y - stage number (1 or 2)
      subsys - subsystem name
    The symbolics #NSRCLIB and #NTGTLIB, when set using recursive symbol substitution, resolve to the series of symbols you define using the #N
    xysubsys
     symbolic. The
     #Nxysubsys
     symbolic defines your Natural libraries. These libraries can reside in any combination of one to 
    FUSER files, where 
    n
     is the number of stages in your lifecycle. For more information, see Associate Each
    CA Endevor
    Stage to a Specific Natural FUSER/FDIC Combination
    .
 
Example: Associate Natural Libraries to
CA Endevor
Inventory Locations Using Indirect Symbolic Substitution
 
This example uses an indirect method of symbolic substitution to associate Natural library names to
CA Endevor
locations, assuming that your lifecycle is configured as follows:
  • It has two environments (QA and PRD) and four stages (two stages in each environment) in the following order:
    QA/1 -> QA/2 -> PRD/1 -> PRD/2
  • The subsystem name is NSUB for all stages.
  • The library names are 
    not
     the same.
Define the following site symbolics in your site symbol table (double ampersands are required in the site symbol table):
$ESYMBOL SYMNAME=#NTGTLIB, SYMDATA='&&#N&&C1EN(1,1)&&C1S#&&C1SU' $ESYMBOL SYMNAME=#NSRCLIB, SYMDATA='&&#N&&C1SENVMNT(1,1)&&C1SSTGNUM&&C1SSUBSYS' $ESYMBOL SYMNAME=#NQ1NSUB, SYMDATA='NATLIB1' $ESYMBOL SYMNAME=#NQ2NSUB, SYMDATA='NATLIB2' $ESYMBOL SYMNAME=#NP1NSUB, SYMDATA='NATLIB3' $ESYMBOL SYMNAME=#NP2NSUB, SYMDATA='NATLIB4'
Coding these symbolics, has the following effects:
  • The target and source library symbolics #NTGTLIB and #NSRCLIB resolve to the following stage symbols:
     #N is not defined as a site symbol so no substitution takes place.
  • The value of the secondary symbols resolves to the assigned Natural library name:
    • #NQ1NSUB=NATLIB1
    • #NQ2NSUB=NATLIB2
    • #NP1NSUB=NATLIB3
    • #NP2NSUB=NATLIB4
  • Therefore, the symbolics resolve to the following libraries:
    • At QA/1, &#NTGTLIB and &#NSRCLIB resolve to NATLIB1 as your Natural library name.
    • At QA/2, &#NTGTLIB and &#NSRCLIB resolve to NATLIB2 as your Natural library name.
    • At PRD/1, &#NTGTLIB and &#NSRCLIB resolve to NATLIB3 as your Natural library name.
    • At PRD/2, &#NTGTLIB and &#NSRCLIB resolve to NATLIB4 as your Natural library name.
Install the Processors
CA Endevor
 uses JCL streams that are called processors to automate the creation of executables such as program load modules. Associate one or more processor groups with each type of source code. Each processor group identifies the processors that are needed for a particular type of source. User and site symbolics make it possible to share processors across groups. Install the Natural and Predict Generate, Delete, and Move processors.
As delivered, the software uses the Natural SYSOBJH utility Internal format for storing objects in
CA Endevor
. However, you can configure the software to use one of the SYSOBJH utility Transfer formats. The Natural Generate processor must be configured to match the Natural SYSOBJH utility format and options that are used to store the Natural objects in
CA Endevor
.   
 
Follow these steps:
 
  1. Determine the Natural Generate processor with the appropriate Natural SYSOBJH LOAD options in the EINE JCL library to use when generating Natural objects.
    Select the Natural Generate processor based on what the +EINE-SYSTRAN-SYSOBJH parameter in the initialization exit, UEXIT00, is set to. For more information, see the step Modify the Initialization Exit in Install User Exits.
    If +EINE-SYSTRAN-SYSOBJH is set to O, then use the default PNATGEN processor.
    If +EINE-SYSTRAN-SYSOBJH is set to F, I, IS, or S, then delete or rename PNATGEN and rename PNATG#F to PNATGEN.
    If +EINE-SYSTRAN-SYSOBJH is set to L or LS, then delete or rename PNATGEN and rename PNATG#L to PNATGEN
    This eliminates the need to edit the
    CA Endevor
    setup member DEFPROC to change the Generate processor name.
  2. Edit the sample JCL member DEFPROC to conform to your site's standards. Edit the job card and data set names. You may also need to edit the ENVIRONMENT and SYSTEM parameters within each ADD ELEMENT SCL statement.
  3. (Optional) Modify the processors replacing the AUTO=ON parameter with the appropriate Processor Natural Security login and password, if you use Natural Security.
  •  If you use Natural Security, two different Natural Security logon IDs are required: one for the processors that uses a default ETID of *INIT-US, so the job name is used as the ETID, and a second for the CASCMMNI server that uses a default ETID of *INIT-ID, so the server uses the step name as the ETID. It is critical that the processors use a different ETID from the server, because they are accessing Natural libraries from the server job at the same time.
  1. Submit the DEFPROC JCL.
    All the integration software Natural and Predict processors are loaded to
    CA Endevor
    .
Define the Natural and Predict Types
Define your Natural and Predict Element types, processor groups, and processor group symbolics for each stage and system that is being configured for management of Natural and Predict elements. All subsystems that are defined to a system can use the types that are defined to that system.
 
Follow these steps:
 
  1. Modify sample JCL member DEFTYPE, and ensure that the job card, STEPLIB, and CONLIB definitions adhere to site standards.
  2. Make a copy of DEFTYPE for each stage and system combination that is being configured for management of Natural elements. For example, if you have six stages in your Natural lifecycle, you need six copies of DEFTYPE.
    Copies of DEFTYPE are now available so you can edit them separately with stage-specific information.
  3. Modify each copy of member DEFTYPE with the appropriate environment, stage, and system parameters; the base and delta libraries; and the symbol definitions. There are many definition sets within DEFTYPE (one for each Natural element type and Predict element type), and each needs to be assigned identical values for all of the following parameters and symbol definitions; therefore, we recommend that you use the CHANGE ALL edit to speed and simplify this edit procedure. Modify the italicized values in the following lines of DEFTYPE.
    • Environment, stage, and system parameters
      •  
        TO ENV 
        'ENVNAME'
         
         
      •  
        STAGE ID 
        'Z'
         
        CA Endevor
        environment and stage
      •  
        SYSTEM 
        'SYSNAME'
         
        CA Endevor
        system for which the types, processor groups, and Symbolics are being defined.
    • Base and delta libraries
      All Natural element types can share the same base and delta libraries. All Predict element types can also share the same base and delta libraries.
      •  
        BASE LIBRARY 
        'NAT.SRCLIB'
         
        CA Endevor
        base Library for Natural element types
      •  
        DELTA LIBRARY 
        'NAT.DELTA'
         
        CA Endevor
        delta Library for Natural element types
      •  
        BASE LIBRARY 
        'PRED.SRCLIB'
         
        CA Endevor
        base Library for Predict element types
      •  
        DELTA LIBRARY 
        'PRED.DELTA'
         
        CA Endevor
        delta Library for Predict element types
    • Symbol definitions
      All symbol definitions reference the
      CA Endevor
      Integration for the Natural Environment site symbolic sets.
      • All processor groups (generate, delete, and move) share the same set of symbols, as follows.
      SYMBOL ADALOAD=&#ADALOAD#X SYMBOL NATLOAD=&#NATLOAD#X SYMBOL NATNUC=&#NATNUC#X SYMBOL NATPARM=&#NATPARM#X SYMBOL DDCARD=&#DDCARD#X SYMBOL DDCARDD=&#DDCARDD#X SYMBOL DDCARDM=&#DDCARDM#X SYMBOL LISTLIB=&#LISTLIB#X SYMBOL ADALOAD2=&#ADALOAD#Y SYMBOL NATLOAD2=&#NATLOAD#Y SYMBOL NATNUC2=&#NATNUC#Y SYMBOL NATPARM2=&#NATPARM#Y SYMBOL DDCARD2=&#DDCARD#Y SYMBOL DDCARDD2=&#DDCARDD#Y SYMBOL DDCARDM2=&#DDCARDM#Y SYMBOL LISTLIB2=&#LISTLIB#Y
      Use the CHANGE ALL command to replace the #X in the symbol definitions to the value used in the
      CA Endevor
      Integration for the Natural Environment site symbolic set that corresponds to the stage for which the current copy of DEFTYPE is being configured. For example, if you set the stage ID parameter to STAGE ID = T, then you would change the #X in the symbol definitions to #T, assuming that this is the suffix used in the
      CA Endevor
      Integration for the Natural Environment site symbolic set that corresponds to stage T.
    • In addition, all move processor groups also share the following additional set of symbols.
      Use the CHANGE ALL command to change the #Y in the symbol definitions to the value used in the
      CA Endevor
      Integration for the Natural Environment site symbolic set that corresponds to the stage to which elements are moved.
      For example, if elements are moved from stage T (test) to stage Q (QA), then you would change the #Y suffix to #Q (assuming that this is the suffix that is used in the
      CA Endevor
      Integration for the Natural Environment Site Symbolic set that corresponds to stage Q).
  4. Submit the JCL for each copy of DEFTYPE (once for each stage and system combination) created and edited in the previous step.
Enable Global Type Sequencing
 
Global Type Sequencing
 is an optional method of defining the order in which element actions are processed. When global type sequencing is enabled, element actions are processed by type sequence regardless of the inventory location of each action. API element actions (if wildcarded) and SCL element actions are executed in the type sequence order that is defined at the site level in the Type Sequence member that is created by the
CA Endevor
administrator. The Global Type Sequencing option is required to specify the order in which your Natural types are processed in batch requests. To use the
CA Endevor
Global Type Sequencing option to process Natural types, you must enable this option for the Natural types.
 
Follow these steps:
 
  1. Enable Global Type Sequencing, if it is not in use at your site.
     For more information on enabling Global Type Sequencing, see How to Enable Global Type Sequencing.
  2. Edit your Global Type Sequencing Type Processing Member to add the Natural types. You must use the following list of Natural types.
     Do not change the order in which the types are listed in the supplied list of Natural types.
    The following list of Natural types is supplied as JCL member ETYPESEQ.
    TYPE 'NATGDA' DESC 'Natural TYPE DEF FOR GLOBALS DATA AREAS'. TYPE 'NATPDA' DESC 'Natural TYPE DEF FOR PARAMETER DATA AREAS'. TYPE 'NATLDA' DESC 'Natural TYPE DEF FOR LOCAL DATA AREAS'. TYPE 'NATCOPY' DESC 'Natural TYPE DEF FOR COPYCODE'. TYPE 'NATTEXT' DESC 'Natural TYPE DEF FOR TEXT'. TYPE 'NATFUNC' DESC 'NATURAL TYPE DEF FOR FUNCTIONS'. TYPE 'NATSUBR' DESC 'Natural TYPE DEF FOR SUBROUTINES'. TYPE 'NATSUBP' DESC 'Natural TYPE DEF FOR SUBPROGRAMS'. TYPE 'NATHELP' DESC 'Natural TYPE DEF FOR HELPROUTINES'. TYPE 'NATMAP' DESC 'Natural TYPE DEF FOR MAP'. TYPE 'NATADAP' DESC 'NATURAL TYPE DEF FOR ADAPTERS'. TYPE 'NATPROG' DESC 'Natural TYPE DEF FOR PROGRAMS'. TYPE 'NATCLASS' DESC 'Natural TYPE DEF FOR CLASSES'.
    Your Natural types are processed in the order in which the types are listed in the Type Processing Member.