Complete Configuration without CA CSM

The tasks in this section must be completed whether you installed the product files using CA CSM or ESD. If you used CA CSM, these tasks are required regardless of whether you are using SCS. The configuration tasks that are described in this section are listed and described in the online SCS steps. However, these tasks are not automated in SCS. You must perform them manually outside of SCS.
ce18
The tasks in this section must be completed whether you installed the product files using CA CSM or ESD. If you used CA CSM, these tasks are required regardless of whether you are using SCS. The configuration tasks that are described in this section are listed and described in the online SCS steps. However, these tasks are not automated in SCS. You must perform them manually outside of SCS.
To configure the installed files to enable
CA Endevor
to be started and customized:
  1. Configure the deployed product data sets.
    1. Modify deployed file names to your user-defined values using job BC1JJB03. For more information, see Edit the CSIQJCL Data Set.
    2. APF-authorize the CSIQAUTU or CSIQAUTH libraries, or copy the content to an existing APF-authorized library.
    A client with an existing installation may want to run their current release and the new release on the same system/LPAR. In this case, the client must verify that the libraries for the new release cannot be used by accident. For more information, see Concurrent Releases.
  2. Existing clients could have completed these steps for an earlier release of
    CA Endevor
    .
    1. If your site is using CA ACF2 security, modify the TSO Command Limiting Facility to allow ISPTLIB commands. These commands include ACMQ, BC1PACMI, ESORT, EONLY, EM, QM, and so on.
    2. Create a
      CA Endevor
      environment for the new release under TSO. For more information, see How to Define
      CA Endevor
      to the ISPF Environment
      .
    3. Set up security as follows: