Previous Topic: Create a Default Job Card for Batch RequestsNext Topic: The Natural Development Lifecycle


Create a Default CA Endevor SCM Procedure for Package Execution

This CA Endevor SCM procedure is used to build the JCL required for package execution.

Note: If you are upgrading from Version 15.0 or Release 15.1 and saved your NDVPROCP to a temporary Natural library, you can use it as a model for updating the Version 16.0 NDVPROCP.

To create a default CA Endevor SCM procedure for package execution

  1. Log on to the EINELIB Natural library.
  2. Modify the text module NDVPROCP to make it consistent with your general site standards for a package execution and save the text module.

    The text module NDVPROCP is available to build default JCL for package execution.

Create a CA Endevor SCM Procedure for Action Processing

A CA Endevor SCM procedure is needed for execution of CA Endevor SCM action processing. If your site has not already customized this procedure, use the following steps to create the procedure.

  1. Customize the ENDEVOR procedure. A sample ENDEVOR procedure is located in the CSIQJCL library delivered with the CA Endevor SCM files.
  2. After modification, copy it to a PROCLIB defined to JES.
  3. If you changed the ENDEVOR member name, you must update the text module NDVSTEP in the EINELIB Natural library. To do this, perform the following steps:
    1. Log on to the EINELIB Natural library.
    2. Modify the text module NDVSTEP to update the PROCNAME value in the EXEC statement to reflect the new procedure name.
    3. Save the text module.