Contents
Overview
The following is a brief description of the main steps in deploying an instance of this product by issuing CA Mainframe VM Product Manager commands. One installation of the product materials for a specific product version can be used to deploy multiple instances of the product. These instances might run on the same VM system, or on different VM systems at your installation.
- Define the Product Deployment
Use the VMDEFINE command to establish a set of parameters for the deployment. These parameters include the server machine user ID and the target disks or directories to contain the product files used by the server or end user. - Deploy the Product Materials
Use the VMDEPLOY command to populate the product disk space from the installed product materials. Initial configuration files are created and the deployment is readied for its first use. - Complete the Deployment
Step 1. Define the Product Deployment
The VMDEFINE command creates an entry in the VMSERVER NAMES file. Attributes for the deployment are defined as tags in this standard NAMES file. A set of initial attributes for a deployment is presented and may be updated during the definition phase.
To bring up the initial NAMES file modification screen, enter the VMDEFINE command. The format is:
VMDEFINE name ppfname component
- name
Specifies the user ID of the product server machine to be created. - ppfname
Specifies the CMS file name for the Product Parameter File for this specific version of the product. If you created a PPF override file, use its file name here. If you use the supplied PPF, its name is ZVMN012A. - component
Specifies the name of the component. Use the name MANAGER for installing on minidisks. Use the name MANAGERSFS for installing on SFS.
Step 2. Tailor the Product Deployment
The VMDEFINE command creates the entry and then enters a NAMES panel for you to view or modify the definitions. You may tailor the characteristics of the CA Mainframe VM Product Manager product server machine on the VMSERVER NAMES panel. Name panel usage is described in the IBM NAMES command documentation and HELP file. To change entries just overtype the values and press PF6 to change the entry. Press PF3 to exit the panel.
Step 3. Deploy the Product Materials
The step in this section creates a usable product instance by copying the installed product build materials to the disk areas you allocated in the previous step.
Enter the VMDEPLOY command to copy product materials to the runtime disk space.
VMDEPLOY name PRIMARY
- name
Specifies the user ID of the CA Mainframe VM Product Manager administrator being deployed. We strongly recommend that you use the ID VMANAGER. - PRIMARY
Specifies that code is being deployed to VMANAGER disks 193 and 195. These are the ADMIN and PUBLIC disks as defined in the VMSERVER NAMES file.
Step 4. Complete the Deployment
For more information about making the product available to your users, see Releasing Products to Users in the Reference.
Proceed to the section Implementing the Directory Reader Diagnose Code and follow the steps there.