CA Endevor Integration for the Natural Environment › Introduction › Components

Components

The following components are delivered with CA Endevor SCM Integration for the Natural Environment:

• CA Endevor SCM Integration for the Natural Environment executable files

  The following executables are supplied:

  • The integration software's online interface in the Natural environment.
  • The integration software's server, which usually runs as a z/OS started task, serving as an interface between the integration software's online sessions and the CA Endevor SCM API.
• Natural

  The Natural EINE program initiates CA Endevor SCM Integration for the Natural Environment sessions. The Natural EINE module should be placed in the SYSTEM library to allow users to initiate sessions without needing to first log on to the integration software's 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's online sessions (which write requests to and read responses from the message queue file) and integration software's servers (which 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 SCM 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 SCM 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 to define Natural and Predict element types to CA Endevor SCM, and to define processor groups and symbolic variables to those element types.

• Global Type Sequencing Type Statements

  Type statements are supplied for inclusion into your site’s global type sequencing scheme, providing for Predict files, Natural DDMs, and Natural programming objects to be processed in the correct order by CA Endevor SCM packages and batch processes.

• $ESYMBOL samples and template

  The $ESYMBOL samples and templates are used to configure the integration software's Site Symbolics, which 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 SCM requests).

• Sample JCL

  The sample JCL is used to install the integration software and configure and run instances of the integration software's server (as started tasks).