Previous Topic: Enable Global Type SequencingNext Topic: Customize the Server Shutdown JCL

CA Endevor Integration for the Natural Environment › How to Customize the Server Start JCL

How to Customize the Server Start JCL

To enable the server to be turned on, you must customize the CA Endevor SCM Integration for the Natural Environment server JCL to your site specifications.

Note: The servers can be executed as a batch job using the provided JCL member or you can modify it to run as a started task and copy it to a z/OS procedure library such as SYS1.PROCLIB.

To customize the server start JCL

  1. Modify the sample JCL member CASCMMN1 as follows:
    1. Make sure that the job card adheres to site standards. The job card in the MSGLEVEL is set to (0,0) to suppress extensive informational output from the CA Endevor SCM API.
    2. Set appropriate values for the PREFIX and SERVER symbolic variables, which serve to establish the names of the data sets allocated and used by the started task.
    3. In the CASCMMN1 step, make the following modifications:

      Important! If this is a Natural batch nucleus which is also defined in any of your CA Endevor SCM Integration for the Natural Environment site symbolics as a #NATNUC value, then this Natural batch nucleus must be linked as reentrant.

      • Modify the single PARM value to a Natural batch nucleus which provides access to the Natural environment (FUSER/FNAT/FDIC) in which the CA Endevor SCM Integration for the Natural Environment online sessions will be running.
      • Make sure that the STEPLIB data sets adhere to site standards. Make sure that the Natural load library you specify contains the Natural batch nucleus.
      • In the Natural/Adabas DATA SET section, make sure that the DDCARD data set is properly defined, either inline or with reference to an external DDCARD data set.
  2. (Optional) Make copies of the JCL member and alter the job name and the SERVER symbolic variable appropriately, if you want to configure and run multiple servers.
  3. (Optional) Modify the server JCL to provide the appropriate server Natural Security login and password, if you use Natural Security.

    Note: 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.

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