Contents
CA VM products managed by CA Mainframe VM Product Manager are delivered in VMSES/E format. Both new product versions and any subsequent corrective or preventive service are available in a downloadable electronic envelope file. A series of standard VMSES/E commands populate a set of minidisks or Shared File System directories with product materials from a tape image. This set of disk space is unique to one product and only one version of that product.
Installation Process Overview
An Installation Guide is available for each product installation. The guide provides the detailed steps you follow to load the product materials. Here is an overview of the standard installation steps common to all products:
- Issue the VMFINS INSTALL command with the INFO operand to create a list of the products on the installation tape. Use this VMFINS PRODLIST file to verify the contents and identify the Product Parameter Files which were loaded.
- Issue the VMFINS INSTALL command with the PLAN option to produce a PLANINFO file documenting the product resource requirements for needed user IDs and disk space.
- Allocate the user IDs and disk space to hold the product materials. A separate user ID is allocated for each version of a specific product. That ID owns disk space which will be loaded from the tape image file. The process for allocating VM resources is described in the section "Product Resource Allocation".
- Issue the VMFINS INSTALL command with the ADD option to populate the product materials disk space.
At the end of these steps, disk space owned by a newly defined user ID is populated with the product materials from the distribution media. The individual minidisks or Shared File System directories in this collection are identified by a definition character string from the VMSES/E Product Parameter File. The various types of disk space are defined in the following sections.
SERVICE Disk Space
The service minidisks are identified by the DELTA and APPLY minidisk definition strings. These minidisks are used during the service process to contain replacement parts and various service control files.
BASE Disk Space
The BASE minidisks are identified by the BASE prefix on the minidisk definition string. CA VM products generally provide two BASE disk areas. The BASE1 minidisk contains the original version of serviceable parts for a specific release. It also includes source code files for parts of the product written in the REXX language. Because parts of CMS are used to build product executable files, a BASE2 minidisk is defined as the MAINT 190 CMS minidisk. BASE disk space is never updated by the service process.
BUILD Disk Space
The build minidisks or directories are identified by a minidisk string beginning with BUILD. These minidisks contain the code that will be copied for use by a running server machine user ID, or by end users on a publicly accessed minidisk or directory. This list illustrates some of the possible BUILD strings used by CA VM products:
- BUILDSRV -- Server Code Minidisk
- BUILDADM -- Server Administration Minidisk
- BUILDPUB -- Public File Minidisk
- BUILDHLP -- Product Help Files Minidisk
LOCAL Disk Space
CA VM products identify LOCAL disk space by a string name starting with LOCAL. The string is of two types, listed as follows:
- LOCALSAM
The LOCALSAM string name identifies sample disk space. This space contains sample code in the form of User Exit programming files, sample product configuration files, and other control files used by the CA Mainframe VM Product Manager utility commands. - LOCALMOD
The LOCALMOD string identifies an empty minidisk directory, which holds any local modifications of the product code.