Previous Topic: How to Configure for New ClientsNext Topic: Implementing the Sample Application

Starting Your Product › How to Complete Configuration With CA CSM

How to Complete Configuration With CA CSM

Note: The CA CSM configuration process implements a Rapid Implementation configuration for CA Endevor SCM. Instead of using CA CSM to configure CA Endevor SCM, we recommend that you use the Best Practice Implementation. For more information about the Best Practice Implementation, see the Scenario Guide.

If you used CA CSM to install and deploy the product files and you are installing CA Endevor SCM for the first time, you can use the Software Configuration Service (SCS). SCS automates the configuration of CA products after they have been installed and deployed using CA CSM.

The SCS steps include the tasks required to configure the deployed files to enable CA Endevor SCM to be started and customized. Also, the SCS automated configuration for CA Endevor SCM leads you through all the tasks necessary to perform a Rapid Implementation. The Rapid Implementation steps set up a fully scalable software development environment that is complete and includes a lifecycle and inventory structure. If this is the first time CA Endevor SCM is being installed at your site, we recommend that you use SCS to configure a Rapid Implementation.

SCS guides you through the steps necessary to configure CA Endevor SCM. All these steps are listed and described in the online SCS procedure. However, some steps are performed outside of SCS. The steps performed outside of SCS are referred to as the manual steps. These manual steps enable you to perform the following tasks:

A list of the manual steps follows. Cross references are provided to indicate where you can find more information about how to perform each step.

The following manual steps prepare the deployed files or your installation environment:

  1. Availability of the Include Members.

    For more information, see How to Make Include Members SCMM@LIB and SCMM@SYM Available.

  2. Authorize the CSIQAUTU or CSIQAUTH libraries or copy the content to an existing authorized library.

    For more information, see How to Authorize CSIQAUTU and CSIQAUTH Libraries.

  3. LINKLIST/LPA Considerations Part 1.

    For more information, see How to Authorize CSIQAUTU and CSIQAUTH Libraries.

  4. LINKLIST/LPA Considerations Part 2

    For more information, see How to Authorize CSIQAUTU and CSIQAUTH Libraries.

  5. Define CA Endevor SCM to the ISPF environment.

    For more information, see How to Define CA Endevor SCM to the ISPF Environment.

  6. Define CA Endevor SCM to GRS (if not already done).

    For more information, see Global Resource Sharing.

  7. Modify the TSO Command Limiting Facility to allow ISPTLIB commands (ACMQ, BC1PACMI, ESORT, EM, OM, etc) - CA ACF2 for z/OS users only.

    For more information, see ISP Command Table Considerations.

  8. Establish security for CA Endevor SCM data sets.

    For more information, see How to Secure Your Data Sets.

  9. Secure Access to functions.

    For more information, see How to Establish Functional Security.

Note: The following SCS step is executed after you complete the steps previously listed. However, it is not a manual step: Execute the @@UPDJCL SCMUPDTE utility program.

The following manual steps set up a Rapid Implementation.

Note: For more information about steps 1 through 20, see How to Set Up the Standard Environment in the appendix "Using Rapid Implementation."

  1. Define the EA System files.
  2. Process the CA Endevor SCM Tables.
  3. Define the ACMQ files.
  4. Define the Package file.
  5. Define the Element Catalog and Index files.
  6. Define the Master Control files.
  7. Define the DEV, QA, and PRD APPL@SYS files.
  8. Define the DEV, QA, and PRD COMM@SYS files.
  9. Define the EA System.
  10. Add Processors to the EA System.
  11. Define the EA System Types.
  12. Add the CA Endevor SCM Tables to the EA System.
  13. Promote the CA Endevor SCM Tables and Processors.
  14. Copy the Table Load Modules to the CSIQAUTU library.
  15. Define the APPL@SYS System in the PRD Environment.
  16. Define the APPL@SYS System in the QA Environment.
  17. Define the APPL@SYS System in the DEV Environment.
  18. Define the COMM@SYS System in the PRD Environment.
  19. Define the COMM@SYS System in the QA Environment.
  20. Define the COMM@SYS System in the DEV Environment.
  21. Verify the configuration is complete.

    For more information, see How to Verify the Implementation in the appendix "Using Rapid Implementation."

  22. Optional - Jobs to Delete Rapid Implementation files.

    For more information, see Optional Jobs to Delete Rapid Implementation Files in the appendix "Using Rapid Implementation."

After you have completed these manual steps, the lifecycle and inventory structure are set up and verified, you can begin to load your own inventory. For more information, see How to Complete Your Basic Implementation in the appendix "Using Rapid Implementation."

How to 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 described in this section are listed and described in the online SCS steps. However, these tasks are not automated in SCS and must be performed manually outside of SCS.

To configure the installed files to enable CA Endevor SCM to be started and customized, complete the following configuration tasks:

  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. Make SCMM@LIB and SCMM@SYM available to jobs at runtime.
    3. Authorize the CSIQAUTU or CSIQAUTH libraries or copy the content to an existing authorized library.

    Note: 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. Configure the installation environment

    Note: Existing clients could have already completed these steps for an earlier release of CA Endevor SCM.

    1. Define CA Endevor SCM to GRS.
    2. 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.
    3. Create a CA Endevor SCM environment for the new release under TSO. For more information, see How to Define CA Endevor SCM to the ISPF Environment.
    4. Set up security as follows: