Contents
Product Resources
Typically, two sets of resources are allocated to bring a product into use.
- The first set is a collection of disks owned by a user ID defined for one specific product and one specific product release. The ID exists just to own the disk space. It is defined as a NOLOG user ID.
- The second set is disk space allocated to house and run the product. A server-based product requires a server user ID which accepts requests and delivers services. It may employ worker virtual machines so it can offload function which can run in parallel. It may employ administration user IDs, like a tape librarian virtual machine, to manage and control the server function. Another type of product is a utility product. It does not have a server virtual machine. The product just supplies function executed directly by an end user. A utility product may just need disk space to hold the utility code.
The first set of resources is allocated during the Product Installation steps. The second set is allocated during each deployment of a product. When VMFINS INSTALL with the PLAN option is executed, a PLANINFO file is generated to document resource requirements for both sets of resources.
You may retrieve the resource requirements for both sets of resources directly from this PLANINFO file, or you may use the VMALLOC command tool to extract the information for you. VMALLOC may be configured to call CA VM:Secure or CA VM:Director if you use either product at your site.
The VMSES/E Planning Resource File (PLANINFO) File Example
The Planning Resource File (PLANINFO) contains the directory entry for the product user ID, the server machine user ID, as well as any worker, servant or other user IDs needed by the product server. Information to build MDISK statements for these user IDs is included as well. For example, if you XEDIT the PLANINFO file for product CA VM:Account, you will see that the file contains the real directory entry for all the user IDs needed.
USER ZVMJ017A NOLOG USER VMACCT VMACCT 64M 256M ABCEG ACCOUNT VMANAGER VMANAGER MACHINE ESA IUCV ALLOW OPTION D84NOPAS ACCT MAXCONN 65535 IPL CMS CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR * CMS system disk LINK MAINT 019D 019D RR * help disk LINK MAINT 019E 019E RR * LP Product disk LINK VMANAGER 0195 01FE RR * VMANAGER code disk LINK VMANAGER 01FF 01FF RR * VMANAGER configuration disk USER VMJDASD VMJDASD 32M 32M G ACCOUNT VMANAGER VMANAGER OPTION ACCT MAXCONN 256 MACHINE ESA IUCV ALLOW IPL CMS PARM AUTOCR NOSPROF CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 0190 0190 RR * CMS system disk LINK MAINT 019D 019D RR * help disk LINK MAINT 019E 019E RR * LP Product disk LINK VMACCT 0192 0192 RR * VMACCT code disk LINK VMACCT 0191 0193 RR * VMACCT local disk
In addition, the owner, virtual address, size, format and block size requirements for each minidisk for each user ID is provided.
The entry for the VMACCT 191 minidisk appears as follows:
OWNER: VMACCT TARGID: 191 SIZE: 3600 BLKSIZE: 4K FORMAT: CMS RECOMPED: NO
VMALLOC Command Tool
The VMALLOC command uses the information contained in the PLANINFO file in one of two ways:
- It can create DIRECT files for use in manually updating the CP Directory with the DIRECTXA command or with your installation Directory Manager product.
- It can automatically create the CP Directory entries for the needed users as well as allocating the disk space. This feature is available if you have the CA VM:Secure or CA VM:Director product installed.
Each product installation guide details the VMALLOC command and its syntax.