How to Install CA CSM › Install CA CSM › Install and Set Up CA CSM

Install and Set Up CA CSM

The directory (.../MSMSetup) where you extract the CA CSM files contains the MSMSetup.sh setup utility that installs and sets up CA CSM.

Note: CA CSM is an SMP/E-installed and serviceable product.

The utility uses the contents of the options file to tailor the overall process. The utility sets up an Apache Tomcat application server, the CA Datacom/MSM database, the CA CSM service components, and the web-based interface. The utility creates and sets up a runtime environment for CA CSM.

The utility has a restart mechanism to continue installation when reinvoked after addressing an earlier failed run. The utility also lets you select installation from scratch on earlier failed runs. If any of the options file parameters affect the completed stages during restart mode, the utility forces a start from scratch installation.

At the start, the utility checks if data sets and USS folders with the values set in option parameters exist. If they exist, the utility prompts you to overwrite the previous installation files or continue the process without overwriting.

The utility verifies availability of port numbers that are passed through the options file. If they are reserved, already in use or unavailable for other reasons, the utility prompts you to use the provided values and continue the installation.

Consider the following information:

• Before you start installing CA CSM, verify that your TSO region size is at least 143360 KB.
• Invoke the MSMSetup.sh script directly from the TSO OMVS environment (native USS command prompt).
• You cannot invoke the MSMSetup.sh utility from a z/OS Telnet session or an ISHELL command shell.
• MSMSetup.sh requires a userid with UID(0) or SUPERUSER authority.
• If your site has SMS ACS rules to force POU to PDSE, these settings cause the installation job CSMN5102 to fail. The MSMSetup.sh requires POU data sets to be created as PDS data sets.
• If you want to adjust JCL space allocation, run the CA CSM installer in Manual or Review installation mode.

Follow these steps:

1. Verify that you extracted the files from the downloaded CA CSM package.

   The MSMSetup and MSMProduct directories exist, and CA CSM files are extracted to the directories.

2. Verify that the required USS paths are available.
3. Verify that you are using a userid with UID(0). If you are not, issue the su command to switch to UID(0).
4. Go to the directory where the MSMSetup.sh setup utility resides, and execute the utility, for example, from OMVS:

   sh MSMSetup.sh
   

   This utility verifies the existence of the following:

   • MSMSetupOptionsFile.properties file in the current path.
   • Valid JAVAPATH parameter field in the Options file.
   • Supported Java SDK version is installed.

   Note: The setup utility is interactive, requiring user responses until completion. The output is written to a log file, MsminstallerLogyyyy-mm-dd,hh-mm-ss,ttt.log, in the MSMSetup directory. If you rerun the utility after a failure, the utility will perform the necessary cleanup steps for the previous execution.

   A panel appears that provides information about the utility. Then, the license agreement appears.

   This license agreement covers an agreement to allow CA Technologies to accumulate minimal information pertaining to the product acquisition activity. This information includes the site ID, the product, and the user ID for the CA Support Online website. Sometimes site access rules deny an FTP connection that is established for this purpose or the connection cannot be established for any other reason. Then CA CSM still continues to function.

5. Review the license agreement, and press PF3.

   You are prompted to accept the agreement.

   Note: If the license agreement is not displayed, verify that the TSO OMVS libraries are allocated in your TSO environment.

6. Enter Y to accept the agreement.

   (Non-UID(0) installation only) If you are executing the installation utility with a userid that is not assigned UID(0), you are asked whether the installer should immediately stop to switch to a userid that is assigned UID(0).

   Note: A userid with UID other than 0 may encounter errors while files are copied and their attributes and permissions are modified. These errors typically indicate that the Operation is not permitted. Usually, the installation utility catches this type of errors and results in a premature, unsuccessful termination. In most cases, restarting the installation utility with a userid that has UID(0) assigned successfully restarts and completes the installation.

   However, this type of errors may go undetected. In such cases, a successful restart of the installation utility may be very difficult. You are required to delete all unpaxed files, installed files, and restart the installation from the beginning.

7. (Non-UID(0) installation only) Enter Y (Yes) or N (No) in response to the prompt. We highly recommend that you reply N (No) to the installation utility, stop the installation, and switch to a userid that is assigned UID(0). You do so by running in superuser mode. To run in superuser mode, issue the su command at the OMVS command prompt, and then rerun the installation utility.

   If you reply Y (Yes), the installation continues.

8. Monitor the utility as it verifies that system and software prerequisites are satisfied, and validates the contents of the options file.

   (Optional) If the IP address taken from the system fails to connect, provide a host name or IP address that supports FTP for processing batch jobs.

9. Specify one of the following installation modes for processing the CA CSM installation jobs:

   A

   In Automatic mode, installation jobs are submitted automatically in non-stop mode (the submitted jobs are not shown before submission).

   R

   In Review mode, you are prompted to review each installation job before submission.

   M

   In Manual mode, submit each installation job manually after the setup process.

   Note:

   • If you submit your installation job using TSO, the installer only runs in Manual mode.
   • The installer can require more memory than 17200 KB.
   • If you restarted after an earlier failed point, you are prompted to select a start from an earlier failed point or scratch.
   • If you have selected FTP mode for installation job submission, you are prompted to enter your z/OS credentials.
10. (FTP mode only) Enter your user ID and then your password.

    If you make a mistake entering the user ID or password, you have two more attempts to reenter your credentials. A Yes/No prompt precedes the second and third attempts.

    Yes

    Allows you to reenter your credentials.

    No

    Terminates the installation procedure.

    The installation procedure terminates after the third failed attempt to validate your FTP credentials. Once you resolve this issue, restart the installation script.

    The utility displays the JOB statement, and the JOBPARM statement (for JES2 environment) or the MAIN statement (for JES3 environment) for review and modification (if necessary).

11. Take one of the following steps in response to the Edit Job Card question:
    • If your site does not require additional parameters, enter N. The installation process continues.
    • If your site requires additional parameters, enter Y. The job card opens in edit mode. Modify the job card, and press PF3 to save the changes and continue the installation process.

      Note: If CA View is running on the host system, uncomment the following statements. Then, fill them in based on the initialization parameters used in SARINIT upon setting up CA View:

      • The OUTPUT statements SARPRT and JESPRT in the JOBCARD
      • The CLASS option in both SARPRT and JESPRT statements
12. Monitor the utility as it customizes all the required installation jobs.

    (Optional) If you selected Review installation mode, you are prompted to review installation jobs one by one. Modify a job and press PF3 to save your changes and submit the job.

13. Monitor the utility as it creates the SMP/E environment for CA CSM, and sets up the CA CSM components.

    The utility performs the following steps:

    • Submits the previously modified jobs one by one and copies the customized JCL into the runtime JCL PDS.

      Note: If executing a job takes longer than the JobCompletionWaitMaxTime options file keyword specifies, the utility asks if you want to continue waiting. Enter N to terminate the whole installation process.

    • Customizes the CA Datacom/MSM environment including CA Datacom/MSM address spaces and connection pools.
    • Customizes the Apache Tomcat environment including the server.xml and context.xml files, port numbers, the connection pool, and the user XML configuration.
    • Customizes and copies JCL for the runtime PROCLIB PDS.
    • Customizes and copies JCL for the runtime JCL PDS.
    • Prepares CA CSM for the CAICCI interface and copies the LIBCCI and LIBCCI6E modules and the customized job COPYCCI to the run-time JCL PDS member COPYCCI. The COPYCCI job does not need to be run as part of the installation process. This job is provided as a convenience to reload these modules, if needed. For example, if these modules are updated through maintenance procedures, you can copy the updates into the CA CSM run time.

    After the last step completes, the utility displays an installation summary report (MSMSummaryReport.txt). The report is stored in the MSMSetup directory. This report provides the URL required to access CA CSM from a web browser.

    The setup utility completes its process.

14. Review the summary report, MSMSummaryReport.txt, for specific post-installation job submission required to complete the overall CA CSM installation.

    Submit the installation jobs CSMN51yy, as specified in the summary report. yy indicates the sequence number of the job.

    Note: Submit the installation jobs manually after MSMSetup.sh finishes, regardless of the installation mode that the CA CSM installer is running in.

15. Verify that the following libraries in the STEPLIB of the JCL(MSMMUF) job are APF-authorized:
    • CAAXLOAD and CUSLIB CA Datacom/MSM libraries
    • The CA Common Services for z/OS library that the CCSdsn keyword in the options file specifies

    For the libraries to remain APF-authorized after the next IPL, add the libraries to your permanent APF list.

    Note: If the value of the AddAPFauthDSdyn keyword in the options file is N, try to APF-authorize these libraries manually.

16. Verify that the user ID associated with the CA CSM application server (MSMTC job or started task) has the required USS access authority.

    CA CSM can create and mount file systems.

17. Verify that your network configuration permits CA CSM to access the following websites:
    • supportservices.ca.com (using HTTPS Port Number 443)
    • ftp.ca.com (using FTP Port Number 21)
    • ftpca.ca.com (using FTP Port Number 21)

      Note: CA CSM uses this FTP server to accumulate minimal information. This information includes the site ID, the product, and the user ID for the CA Support Online website. Sometimes site access rules deny an FTP connection that is established for this purpose or the connection cannot be established for any other reason. Then CA CSM still continues to function.

    • scftpd.ca.com (using FTP Port Number 21)
    • ftpdownloads.ca.com (using FTP Port Number 21)
    • supportftp.ca.com (using FTP Port Number 21)
    • sdownloads.ca.com (using HTTPS Port Number 443)

      Note: sdownloads.ca.com is only required if you use the Use HTTPS for Downloads acquisition option under System Settings, Software Acquisition on the Settings page. If you authorize the ca.com domain for both ports 80 and 443, you do not need to authorize sdownloads.ca.com.

    In addition, your network administrator must define a Domain Name System (DNS) entry for localhost.

18. Start CA CSM (Start CA CSM, Start CA CSM).

    CA CSM becomes operational.