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. Use this process to deploy to a target user ID that is running a previous release of the same product. The procedure allows an easy transition to a new product release while preserving the ability to go back to the older release, if necessary.
- Redefine the Product Deployment
Use the VMSERVER command to update a set of parameters for the deployment. These parameters include the Product Parameter File (PPF) name, and possibly the target disks to contain the product files used by the server or end user. - Allocate Resources for Production Use
Use the VMALLOC command to update any user IDs and possibly modify the disk space needed for the product deployment. Some product minidisks may need to be enlarged for a new release. - Deploy the Product Materials
Use the VMDEPLOY command to populate the product disk space from the installed product materials. - Back Out the Upgrade
Follow the steps in this section to restore the previous release of the product, if necessary. - Discard the Product Materials from the Older Release
Follow the steps in this section to discard the previous release of the product and release the disk space it occupied. - Complete the Deployment
Upgrade the Directory Reader and make the product available to users.
Step 1. Redefine the Product Deployment
The VMSERVER command displays the CA Mainframe VM Product Manager administrator ID entry in the VMSERVER NAMES file. Attributes for the deployment are defined as tags in this standard NAMES file. A set of previously defined attributes for a deployment is presented and may be updated during the redefinition phase. In this step you will update the entry for a deployment to reflect attributes of the new product release.
To display the NAMES file modification screen, enter the VMSERVER command. The format is:
VMSERVER name
- name
Specifies the user ID of the CA Mainframe VM Product Manager administrator.
A new product release is installed with a new Product Parameter File. You will update the PPF Name field on the screen by overtyping it.
For the first token, specify 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.
For the second token, specify the component name MANAGER for a minidisk installation or MANAGERSFS for a Shared File System installation.
After updates are made, press PF6 to change the entry. Press PF3 to exit the panel.
Step 2. Allocate Resources for Production Use
Retrieve the needed directory statements and minidisk definitions for the new release of CA Mainframe VM Product Manager from the product materials you previously loaded from the distribution media. The VMALLOC command must be setup first as described in the appendix Allocating User ID Entries and Disk Space. In the simplest form, create or update a VMALLOC CONFIG file to add a device or volume record. Issue the following command to produce a directory entry:
VMALLOC SERVER name ( DIRECT
- name
Specifies the user ID of the CA Mainframe VM Product Manager administration user ID you are upgrading.
Match the retrieved directory entry with your existing directory entry for the administration user ID, and upgrade your current definition to match the requirements for the new release of the CA Mainframe VM Product Manager.
Step 3. Deploy the Product Materials
To deploy the product materials, copy them to the runtime area. Enter the VMDEPLOY command to copy product materials to the runtime disk space.
VMDEPLOY name PRIMARY
- name
Specifies the user ID of the product server machine being deployed. - PRIMARY
Copies product files to the administrator primary disk space. This value results in overwriting the deployed Product Materials from the older product release or version with the new release materials.
We recommend that you back up the VMANAGER runtime minidisk before using this command. Restoring the backup can be used to revert to the older release, if needed.
Step 4. (Optional) Back Out the Upgrade
The steps in this section restore the previous release of the CA Mainframe VM Product Manager if that step becomes necessary.
To display the NAMES file modification screen, enter the VMSERVER command. The format is:
VMSERVER name
- name
Specifies the user ID of the CA Mainframe VM Product Manager administrator.
The first step in this procedure documented how to update the entry in the VMSERVER NAMES file to define a new Product Parameter File. You updated the PPF Name field on the screen by overtyping it. Reverse that step to restore the field to its original contents.
Use the following format to enter the VMDEPLOY command to copy product materials to the runtime disk space.
VMDEPLOY name PRIMARY
- name
Specifies the user ID of the product server machine being deployed. - PRIMARY
Copies product files to the administrator primary disk space. This value results in overwriting the upgraded Product Materials from the newer product release or version with the older release materials.
After the situation that required you to back out the upgrade is resolved, you can repeat the upgrade procedure from the beginning to reinstall the upgrade.
Step 5. Discard the Product Materials from the Older Release
When you have no further use for the the previous release of CA Mainframe VM Product Manager, follow the steps in this section to discard the previous release and free the disk space that it occupied.
Each release of a product is installed and maintained on minidisks or SFS directories owned by a unique user ID. For this release, that ID is ZVMN012A. Using your Directory Manager product or procedures, simply remove the product specific user ID which was used by the older release. Use the VMSERVER command to ensure that no entry in the VMSERVER NAMES file still references the old product materials ID.
Step 6. Complete the Deployment
For more information about making the product available to your users, see Releasing Products to Users.
Proceed to the section Implementing the Directory Reader Diagnose Code and follow the steps there. After upgrading to a new release of the CA Mainframe VM Product Manager, you must upgrade to the newer version of the Directory Reader.