Administrating the Servant Facility
The Servant Facility is a set of special worker virtual machines that help cacc perform long-running CMS tasks such as formatting and copying minidisks, and deleting and renaming SFS file spaces.
The Servant Facility is a set of special worker virtual machines that help
VM:Secureperform long-running CMS tasks such as formatting and copying minidisks, and deleting and renaming SFS file spaces.
These extra worker virtual machines, or servant machines, let directory managers start minidisk management functions and continue to work while the minidisk management functions are processed. They save time and increase productivity.
You can use the Servant Facility whenever your staff has many minidisk management functions to perform. You can turn the Servant Facility off and on at any time.
To use the DELETE and CHANGE commands when you are using
VM:Securefor SFS administration, use the Servant Facility . With the Servant Facility, potentially long-running commands can execute on an
VM:Secureservant instead of tying up the
VM:Secureservice virtual machine.
When the Servant Facility is turned on,
VM:Securedynamically creates and autologs servant user IDs when it needs them. The product creates as many servant virtual machines as it requires, up to the limit you set or up to 9999, whichever is smaller.
Servant user IDs are created in the range VMX$0001 to VMX$9999 by default. (You can change the first four characters of their user IDs.)
VM:Secureuses its own directory entry as a prototype for the directory entries for these servant user IDs. As for all directory entries that are created from prototypes,
VM:Securestrips all minidisk references from each new directory entry and changes the user ID, password, and other statements as necessary.
- The servant user IDs are created with a maximum virtual storage (vstor) size of 24M.
- Because the servant user IDs are modeled after theVMSECUREdirectory entry, you cannot have an IPL 190 statement in theVM:Secureservice virtual machine directory entry.
VM:Securerequires a servant for a process, it places the process in a wait queue and searches for an available servant. If it finds an available servant, it attaches that servant to the process and it places the process in the ready queue. If it cannot find an available servant, it creates a directory entry for a new servant and it adds the entry to the object directory.
VM:Securethen autologs the new servant, attaches the servant to the process, and places the process in the ready queue.
When a process finishes with a servant, it releases the servant.
VM:Securethen removes any links that were made during the processing and it verifies the number of free servant user IDs against the number that must remain standing by. If there are more free servant user IDs than required,
VM:Securelogs off the extra ones.
Define the characteristics of the Servant Facility, including the number of free servants that can remain waiting and the maximum number of servants that can exist, through the SERVANT record. This record exists in the PRODUCT CONFIG file. For more information, see SERVANT Record in the