Virtual Machine Environment

Local and system resources are known on the system where they reside. Global resources are known throughout the TSAF or CS collection. Local, global, and system resources are identified, using *IDENT, by a server virtual machine (also called the resource manager). The server virtual machine must be logged on and the resource manager program must be running when a user program requests a connection to a local, global, or system resource. The resource manager program can run in a disconnected virtual machine. The Structured Query Language/Data System (SQL/DS) and the Shared File System (SFS) are examples of resource manager programs that run in disconnected server virtual machines. Connections to global resources are routed by the global resource name, which must be unique in the TSAF or CS collection. System resources must be unique on the system they reside, but can share a name with a system resource on another system.

Private resources are not explicitly known in TSAF or CS collections. The private resource server virtual machine does not identify itself to the TSAF or CS collection as a resource manager. It must be enabled to process private resource requests. This virtual machine owner can set up a special file, $SERVER$ NAMES, which lists the private resources known to that virtual machine. When a user program requests a connection to a private resource, the private server virtual machine does not need to be logged on and the private resource manager does not need to be running. If necessary, VM will automatically log on the server virtual machine and cause the resource manager program to start running. Connections to private resources are routed by user ID.

Preparing Virtual Machines to Manage Resources describes how to set up server virtual machines to manage local, global, and private resources.