Implementing the
CA Endevor
Integration for the Natural Environment

The
CA Endevor
Integration for the Natural Environment lets the Natural developer perform most of their
CA Endevor
tasks from the Natural development environment.
ce18
The
CA Endevor
Integration for the Natural Environment lets the Natural developer perform most of their
CA Endevor
tasks from the Natural development environment.
For information about the use of the
CA Endevor
Integration for the Natural Environment, see Using the
CA Endevor
Integration for the Natural Environment
.
 
 
Use
CA Endevor
as a back-end repository for Natural to allow developers to control updates, migrations, and even the creation of change packages from the Natural environment.
The integration software enables application developers working in the Natural environment to perform
CA Endevor
actions on Natural and Predict objects (known as elements).
This option runs under z/OS, within the CICS, TSO/ISPF, or Com-plete environments and in batch. The option accesses
CA Endevor
through the
CA Endevor
API.
To deploy 
CA Endevor
 Integration for the Natural Environment, install the delivered data sets  in the Natural and ADABAS environments and configure Natural and 
CA Endevor
. These tasks are performed by the following personnel:
  • The Natural administrator installs the Natural objects in the Natural environment.
  • The ADABAS administrator installs the ADABAS files in ADABAS.
  • The 
    CA Endevor
     administrator configures the 
    CA Endevor
     environment.
  • The Natural administrator and the 
    CA Endevor
     administrator work together to configure the Natural software lifecycle and set up the software inventory requirements.
 For more information about the files delivered with the product, see Components.
Hardware Requirements
The following environments are supported:
  • IBM-supported releases of z/OS through V2.4.
Software Requirements
The following mainframe software is required:
  • ADABAS v8.1 or v8.2 with Natural v8.2
  • (Optional) Predict v4.x or v8.2
  • CA Endevor
    Version 16 or Version 17, or 
    CA Endevor
     Version 18
Concurrent Releases
Concurrent releases of 
CA Endevor
 Integration for the Natural Environment can be run when installed into different Natural libraries. Each instance of the application should use their own ADABAS files.
Components
The following components are delivered with 
CA Endevor
 Integration for the Natural Environment:
  •  
    CA Endevor
     Integration for the Natural Environment executable files
    The following executables are supplied:
    • The integration software online interface in the Natural environment.
    • The integration software server, which usually runs as a z/OS started task. This integration software server acts as an interface between the integration software online sessions and the 
      CA Endevor
       API.
  • Natural
    The Natural EINE program initiates 
    CA Endevor
     Integration for the Natural Environment sessions. The Natural EINE module should be placed in the SYSTEM library. This placement allows users to initiate sessions without the need to first log in to the integration software main library. The source for this program is delivered to allow you to run concurrent versions of the integration software.
  • ADABAS files
    The following ADABAS files are supplied:
    • message queue file
      This file serves as the message queue between the integration software online sessions and integration software servers. The online sessions write requests to and read responses from the message queue file. The integration software servers read requests from and write responses to the message queue file. The message queue file also provides the means for an administrator to issue a shutdown command to a 
      CA Endevor
       Integration for the Natural Environment server.
    • system profile file
      This file serves as a repository for all non-message system data, including user profile data.
  •  
    CA Endevor
     processor templates
    The following processor templates are supplied:
    • One set (generate, move, and delete) providing for Natural objects
    • One set (generate, move, and delete) providing for Predict objects
  • SCL
    The supplied SCL must be customized and run in order to:
    • Define Natural and Predict element types to 
      CA Endevor
    • Define processor groups and symbolic variables to those element types.
  • Type Sequencing Type Statements
    Type statements are supplied for inclusion into your Type sequencing scheme. This scheme provides for Predict files, Natural DDMs, and Natural programming objects to be processed in the correct order by 
    CA Endevor
     packages and batch processes.
  • $ESYMBOL samples and template
    The $ESYMBOL samples and templates are used to configure your integration software Site Symbolics. The Site Symbolics are used in Natural and Predict processors, and which are also used by the integration software in the generation of JCL (for batch submission of 
    CA Endevor
     requests).
  • Sample JCL
    The sample JCL is used to install the integration software and configure and run instances of the integration software server (as started tasks).