The steps in this section create a usable product instance. Copy the installed product build materials to the disk areas you allocated in the previous step.
Enter the VMDEPLOY command to verify the product server disks, and copy product materials to the runtime disk space.
VMDEPLOY name [PRIMARY|ALTERNATE]
Specifies the user ID of the product server machine being deployed. For more information about this ID, see Define the Product Deployment.
Copy to the product 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 suggest that you backup all deployed minidisks before using this operand. Restoring the backup could be used to revert to the older release, if needed.
Copy to the alternate disk space location. This value retains your older product material deployment. Setting the Runtime Environment tag value in the VMSERVER NAMES file to PRIMARY or ALTERNATE causes that set of deployed disks to be used when the product server is next started. Testing the new release, or backing out to the old release just requires setting a new value for Runtime Environment and restarting the server.
Note: For more information, see the chapter "Defining a VMSERVER NAMES File Entry" in the CA Mainframe VM Product Manager Reference Guide. For a list of the product tag definitions for the NAMES file entry, see the appendix Product Tags in VMSERVER NAMES File.
Follow the procedure in the CA Mainframe VM Product Manager Reference Guide to define the LMP (License Management Program) key for this product, if necessary.
In order to upgrade an implementation of the CA VM:Secure External Security Manager interface, you must incorporate the upgraded CA VM:Secure Access Control Interface (ACI) CP component from the new release into a new CP nucleus. The complete procedure is documented in the CA VM:Secure Rules Facility Guide in the section “Installing the Rules Facility” under the topic “Configure and Generate the VM:Secure CP Component.” IPL your VM system with the upgraded CP component, before bringing up your CA VM:Secure product server.
When you are running on a Single System Image complex, all member systems must be running the same release of CA VM:Secure. You must incorporate the upgraded CA VM:Secure CP component parts into every member of the complex at the same time. All members of the complex must have the same level of these parts or they will not be allowed to join the complex.
|
Copyright © 2014 CA.
All rights reserved.
|
|