Overview › How the Installation Process Works

How the Installation Process Works

CA Technologies has standardized product installations across all mainframe products. Installation uses the following process:

• Acquisition—Transports the software to your z/OS system.
• Installation using SMP/E—Optionally creates a CSI environment and runs the RECEIVE, APPLY and ACCEPT steps. The software is untailored.
• Deployment—Copies the target libraries to another system or LPAR.
• Configuration—Creates customized load modules, bringing the software to an executable state.

CA MSM provides a web-based interface to make the standardized installation process easier. Using CA MSM, someone with limited knowledge of JCL and SMP/E can install a product.

Note: If you do not have CA MSM, you can download it from the Download Center at the CA Support Online website. Follow the installation instructions in the CA Mainframe Software Manager documentation bookshelf on the CA Mainframe Software Manager product page. The standardized installation process can also be completed manually.

To install your product, do the following tasks:

1. Prepare for the installation by confirming that your site meets all installation requirements.
2. Use one of the following methods to acquire the product:
   • Download the software from CSO using CA MSM.
   • Download the software from CSO using Pax-Enhanced Electronic Software Delivery (ESD).
   • Order a tape.
3. Perform an SMP/E installation using one of the following methods:
   • If you used CA MSM to acquire the product, start the SMP/E step from the SMP/E Environments tab in CA MSM.
   • If you used ESD to acquire the product, you can install the product in the following ways:
     • Install the product manually.
     • Use the Insert New Product option in CA MSM to complete the SMP/E installation.
   • If you used a tape, install the product manually.

   Note: If a CA Recommended Service (CA RS) package is published for your product, install it before continuing with deployment.

4. Deploy the target libraries using one of the following methods:
   • If you are using CA MSM, deployment is required; it is a prerequisite for configuration.
   • If you are using a manual process, deployment is an optional step.

   Note: Deployment is considered part of starting your product.

5. Configure your product using CA MSM or manually.

   Note: Configuration is considered part of starting your product.