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 CSM provides a web-based interface to make the standardized installation process easier. Using CA CSM, someone with limited knowledge of JCL and SMP/E can install a product.

Note: If you do not have CA CSM, 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. Acquire the product using one of the following methods:
   • CA CSM
   • Pax-Enhanced Electronic Software Delivery (ESD)
   • Order a tape or a DVD.
3. Install the product based on your acquisition method.
4. Install the CA Common Services using the pax files that contain the CA Common Services you need at your site.

   All sites should install all CA Common Services contained in the Required CA Common Service bundle.

5. Customize the application proc.

   Customize the sample proc located in CCTVJCL and copy to a system proclib.

   The PARMS DD points to a parmlib that contains the members that are essential for CA SYSVIEW to function. Copy these members from the CCTVJCL lib to this parmlib:

   • SAMPVKGP to create VKGPARMS.
   • VDSPROG to create VDSPROG.
   • VDSTORGP to create VDSTORGP.
   • SAMPCONF to create CONFIG

   Other members that reside in this parmlib are:

   • COPYBOOK members that you create and that are used in VDSPROG.
   • QUOTA function members (if licensed).
6. Configure the minimum settings.

   In the VKGPARMS member, add this entry:

   PLSPRGDS - Specify the name of the parmlib that you set up in item 5.

   VDSPROG contains the default entry:

   EXIT CODE(0)

   CA SYSVIEW does not do anything when it is started. This member will be customized after the product is started in a minimal configuration.

   VDSTORGP is customized later. Define storage groups (POOLS) for non-SMS allocations that CA SYSVIEW will redirect.

7. Start your product.

   Issue this command to start CA SYSVIEW:

   S VAM (or the name you specified for the proc)
   

   The action tests if the task locates all members and the task starts cleanly. To stop the task and remove any hooks in the system, issue the following command:

   F VAM,REMOVE
   

   Note: Do not stop the task with the command P VAM.

8. Customize your product.
9. Deploy your product.

   For simple implementation on a single system, you have a unique PDS specified on the PARMS DD in each application proc on each system. A more complex implementation can utilize a single PDS specified on the PARMS DD of multiple procs. Each system utilizes its own ASRs by definitions in the CONFIG member in the Parmlib and the CONFIG statement on each EXEC in the proc.

Notes:

• For more information about customizing the application to perform allocation control requirements, see the CA SYSVIEW User Guide.
• If VAM abends or error messages display at startup indicating that the application or some of its hooks are already installed, you can easily correct the situation. For more information, see the CA SYSVIEW User Guide.