|
|
|
Fixed minidisk addresses
Every product service virtual machine must have a 191 minidisk to hold the product configuration file, the product PROFILE EXEC, and all locally modified files. The product can also use the 191 minidisk to hold temporary files or to provide work space. The VMDEPLOY command processor only updates this minidisk if the INIT option is specified. CMS accesses the 191 minidisk as filemode A. Do not use this filemode for any other minidisk.
Every product service virtual machine must have a 192 minidisk to hold the program material populated by the CA Mainframe VM Product Manager. Subsequent upgrades will replace the contents of this minidisk with new program material, so the 192 minidisk must not contain any locally modified files. To protect the program material from being inadvertently erased or modified, the 192 minidisk is linked read-only by the product service virtual machines. CMS accesses the 192 minidisk as filemode D. Do not use this filemode for any other minidisk.
The CP directory entry for each product service virtual machine must define a link to the VMANAGER 1FF minidisk at virtual address 1FF. This disk contains control files for license checks and product startup processing. The startup procedure accesses this disk at filemode Z.
The CP directory entry for each product must define a link to the VMANAGER 195 disk at 1FE. This disk contains programming for the CA Mainframe VM Product Manager interfaces. The startup procedure accesses this disk at filemode X.
Variable minidisk addresses
Product databases or control files. Some specific examples:
Contains the product primary database files
The 1C0 minidisk for CA VM:Backup contains resource pools
The 1D0 minidisk for CA VM:Batch, CA VM:Secure or CA VM:Director, and CA VM:Tape contains audit data.
The 1E0 minidisk for CA VM:Backup contains compiled jobs.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |