Contents

Use the VMALLOC command to allocate system resources for a product user ID or a server machine user ID. The operation of the VMALLOC command can be controlled by the records found in the VMALLOC CONFIG file.

VMALLOC can use CA VM:Secure or CA VM:Director to automatically update the CP directory, or can produce a DIRECT file for use by another directory manager product.

The VMALLOC command has the following syntax:

VMALLOC "Parms" [( "Options"]

Parms:

  PRODUCT ppfname component
| [SERVER] name [tagname]

Options:

DIRECT

Authorizations

VMALLOC is intended to be run from user ID VMANAGER, with all the authorizations of a system administrator and a directory manager.

Definitions

  • ppfname
    Specifies the CMS file name for the Product Parameter File for a version of the product you are allocating. If you created a PPF override file, use its file name here.
  • component
    Specifies the name of the component you are allocating.
  • name
    Specifies the user ID of the product main server virtual machine. For a product that does not run in a server, specifies the name of the deployment.
  • tagname
    Specifies the name of a tag in the VMSERVER NAMES file entry for name. The tag value is either the name of a secondary virtual machine within the deployment or the owner name and device address of a single virtual disk.
  • DIRECT
    Specifies that you are creating a DIRECT file only. If a USE statement is present in the VMALLOC CONFIG file, it is ignored. This option is intended for use in an upgrade, where you already have the server user ID in the directory, and need to determine any minidisk size changes for a new release.

Description

The operation of the VMALLOC command depends on the records contained in the VMALLOC CONFIG file. Create the VMALLOC CONFIG file on the VMANAGER 1FF configuration file minidisk. The VMANAGER 1FF minidisk is accessed at file mode V on user ID VMANAGER.

To allocate only a specific virtual machine or minidisk, specify the tagname parameter. When VMALLOC is configured to allocate new virtual machines and disk space automatically, it normally allocates all of the deployment virtual machines and disk space that you defined in the VMSERVER NAMES file entry. Certain virtual machines or minidisks are optional, and you may have chosen to omit allocating them at the initial deployment. If you subsequently chose to add the optional parts of the deployment, add the parts to the VMSERVER NAMES file entry by uncommenting the tag values, then issue the VMALLOC command with a tagname parameter to generate the new virtual machine or minidisk.