CA Mainframe VM Product Manager - 1.2 : Configuring the VMALLOC command processor

You issue the VMALLOC command to either generate the data you need to allocate these resources, or to actually perform the resource allocation task automatically.

The actions performed by the VMALLOC command depend on parameters you specify in an optional configuration file. To specify these parameters, create a VMALLOC CONFIG file on the CA Mainframe VM Product Manager configuration file disk, which is accessed as file mode V.

The following configuration file statements are supported:

DEVTYPE [3390 | 3380 | 9336 | FB-512]

This statement specifies MDISK Directory statements will be produced that define space in units of cylinders for Count Key Data (CKD) devices or 512-byte blocks for Fixed Block Architecture (FBA) devices.

VOLUME volser

This statement specifies MDISK Directory statements will be produced that define space to be allocated on a specific disk volume.

USE [VMSECURE | VMDIRECT]

This statement specifies that an already installed and operational CA VM:Secure or CA VM:Director product is available, and that it will be used to automatically allocate user ID entries and minidisk space. When this statement is specified, make sure that the following conditions are met:

  1. The CA Mainframe VM Product Manager must have a copy of the appropriate VMSECURE or VMDIRECT MODULE file on an accessed minidisk or SFS directory. If your CA VM:Secure or CA VM:Director has another name, specify that name on the USE statement.
  2. The CA VM:Secure or CA VM:Director server PRODUCT CONFIG file must contain a “PRODUCT VMSISERV VMANAGER” record to authorize the VMANAGER ID for automatic allocation.
  3. An entry for VMANAGER must exist in the VMSECURE MANAGERS or VMDIRECT MANAGERS file
POOL poolname

This statement specifies that automatic allocation will use a specific disk sub-pool defined in the DASD CONFIG file of your CA VM:Secure or CA VM:Director server. The statement is ignored if the USE statement is not present.