Installation Guide › Migrating CA VM:Director from AIM to CA Mainframe VM Product Manager › Update the Product Virtual Machine Definition

Update the Product Virtual Machine Definition

The CA VM:Director Server Virtual Machine (SVM) requires minor changes in the virtual machine configuration to operate with the CA Mainframe VM Product Manager.

Note: The changes in this section may be performed without an outage of your VMDIRECT server.

The server is first defined in the VMSERVER NAMES file, which serves as the main software manager database. Issue the following command to define the server:

VMDEFINE name ppfname component

name

Specifies the user ID of the product server machine you are upgrading. In most cases, the name is VMDIRECT.

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 ZVME031A.

component

Specifies the name of the component. Use the name VMDIRECT for installing on minidisks. Use the name VMDIRECTSFS for installing on SFS.

The VMDEFINE command creates the entry and then enters a NAMES panel for you to view or modify the definitions. You can tailor the characteristics of the CA VM:Director product server machine on the VMSERVER NAMES panel.

Note: For more information about NAMES panel usage, see the IBM NAMES command documentation and HELP file.

To change the definitions, overtype the values and press PF6. Press PF3 to exit the panel.

Retrieve the needed directory statements and minidisk definitions for the new release of CA VM:Director 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 product server machine you are migrating.

Match the retrieved directory entry with your existing directory entry for the CA VM:Director server, and upgrade your current definition to match the requirements for the new release of CA VM:Director. The following additional changes may be required, depending on what you have defined already:

• Add a system administration disk at address 0176.
• Add an alternate runtime, alternate administrator disk, and an alternate public disk at addresses 0292, 0276, and 0293 respectively. These disks are populated when you deploy your new release.
• If the old directory entry had the statement “LINK MAINT 193 293”, change it to “LINK MAINT 193 393” to avoid a virtual device collision. If you made this change, also change any ACCESS statement for the 0293 minidisk in the VMSECURE PROFILE EXEC to instead ACCESS the 0393 minidisk.
• Increase the size of existing disks following the size requirements from the DIRECT file created by VMALLOC.

Use the AIM system administration user ID, VMRMAINT, to add authorizations for your CA Mainframe VM Product Manager, VMANAGER, to the CA VM:Director authorization files.

Note: For specific information about using the commands you need, see the CA VM:Director Reference Guide.

• Add this authorization using the VMDIRECT CONFIG AUTHORIZ command:

  GRANT *ALL TO VMANAGER
  

• Add this authorization using the VMDIRECT CONFIG PRODUCT command:

  PRODUCT VMSISERV VMANAGER
  

• Add VMANAGER as a Directory Manager User using the VMDIRECT ADMIN MANAGERS command.