Previous Topic: How to Customize the Server Start JCLNext Topic: How Processing Works

CA Endevor Integration for the Natural Environment › Customize the Server Shutdown JCL

Customize the Server Shutdown JCL

A CA Endevor SCM Integration for the Natural Environment server is shutdown through submission of a separate started task or batch job that issues a shutdown command to the server task using the message queue. Each server task requires a corresponding shutdown task.

To customize the server shutdown JCL

  1. Modify sample JCL member CASCMSTP as follows:
    1. Make sure that the JOBLIB data sets adhere to site standards. The Natural load library should be that in which the Natural batch nucleus is found.
    2. In the SHUTDOWN step, make the following modifications:
      • Modify the single PGM value to a Natural batch nucleus which provides access to the Natural environment (FUSER/FNAT/FDIC) in which CA Endevor SCM Integration for the Natural Environment online sessions will be running. This is usually the same Natural batch nucleus as that used in the corresponding CASCMMN1 server started task.
      • Make sure that the DDCARD data set is properly defined, either inline or with reference to an external DDCARD data set.
      • In the CMSYNIN section, make sure that the single parameter submitted to the SHUTDOWN program is the name of the server started task that is to be shutdown. For example, to shut down a server started task called CASCMMN1, the command should be: 
        SHUTDOWN CASCMMN1

    If you are configuring and running multiple server instances, a separate copy of this JCL member should be made, with job name and SHUTDOWN command modified appropriately.

  2. Set up each configured member as a started task, by copying it to a z/OS procedure library such as SYS1.PROCLIB.