Disk space in an SSI complex is usually shared and accessible from every member system, but you may have configured certain volumes to be accessible only from one member. Any minidisk defined in a SUBCONFIG entry may only be accessed from within the member system where that SUBCONFIG is active.
We recommend that you separate shared volumes and unshared volumes for minidisk allocation. One method to accomplish that separation is to use separate allocation POOLs. For example, you could configure one or more pools for shared volumes, and one pool per member system for the volumes which are dedicated for use by that member.
We recommend that you configure the product Servant Facility feature to simplify SSI operation. The product server is able to launch a servant virtual machine in any member node, so that it may format or copy these minidisks defined within SUBCONFIG entries. For more information, see “Servant Facility in an SSI Complex.”
When the servant facility is not in use, commands that include long running operations such as FORMAT, COPYFILE, or DDR processes, and that operate on non-shared minidisks, must be issued from the member node which has access to the minidisk.
The SSI environment does not allow any operation which involves the parallel use of two minidisks defined in SUBCONFIG directory entries for different member systems. For example, you may not use a command like DUPMDISK to duplicate a minidisk in one SUBCONFIG to another SUBCONFIG on a different member. To work around this restriction, you might duplicate a non-shared minidisk to a shared minidisk, and duplicate the shared minidisk to a new unshared minidisk, and then remove the intermediate shared minidisk.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |