CP directory entry for service virtual machine

In order to enable an HCM client program to communicate with z/VM HCD, you need one CP directory entry for each SVM introduced in Setting up the service virtual machine. The following example shows parts of a default CP directory entry as shipped with the product. If you want to use different settings, change according to your needs. CP directory entries can only be updated by a z/VM system administrator with the required authority.

 1  USER CBDIODSP <password> 256M 999M BCEFG
 2  INCLUDE IBMDFLT
 3  MACH XC
 4  OPTION MAXCONN 64 QUICKDSP SVM APPLMON DIAG88
 5  XCONFIG ADDR MAXNUMBER 5 TOTSIZE 5G NOSHARE
 6  MDISK 0191 … adapt to your needs

The values specified in this example are recommended.

The statements are explained in more detail:

 1 
In our example, the user on the service virtual machine has the user ID CBDIODSP. When creating a new user ID, the second parameter (password) defines the password to be used.

256M means that the virtual machine has 256M of primary address space available after logging in. This value is recommended if large IODFs have to be processed.

999M means that the user on the virtual machine is allowed to enlarge the primary address space size up to 999M (using the CP command DEFINE STORAGE).

BCEFG means that the user ID CBDIODSP is allowed to enter CP commands of privilege classes B, C, E, F and G.

You can find a list of privilege classes in z/VM CP Command and Utility Reference. How privilege classes are used in z/VM HCD, is described in z/VM: I/O Configuration.

 2 
Includes the profile IBMDFLT.
 3 
The dispatcher virtual machine is restricted to run in an XC virtual machine which simulates ESA/XC architecture. This is why the 'MACH XC' entry is required.
 4 
MAXCONN 64 specifies the maximum number of IUCV and APPC/VM connections allowed for this virtual machine. The TCP/IP line driver of the Reusable Server Kernel (RSK) needs this value to be set high enough. See z/VM Reusable Server Kernel - Programmer's Guide and Reference for details.

QUICKDSP causes a virtual machine to be added to the dispatch list immediately when it has work to do, without waiting in the eligible list.

SVM specifies that the virtual machine is a service virtual machine. The monitor data records associated with this virtual machine include the SVMSTAT setting. The only purpose is to allow products that process monitor data to report on service virtual machines separate from end-user virtual machines. No other operations, such as transaction or wait state classification, are affected by this operand.

APPLMON: The RSK uses application monitoring. Option APPLMON is only needed if application monitoring is desired. APPLMON authorizes the virtual machine to issue DIAGNOSE code X'DC' by which an application may declare or delete a buffer for CP monitoring. After the buffer has been declared for monitoring, all data in it is collected by CP into monitor records at each sample interval. For more information about DIAGNOSE code X'DC', see z/VM: CP Programming Services. You can find further useful information in z/VM Reusable Server Kernel - Programmer's Guide and Reference, chapter Monitor Data and chapter Command Description.

DIAG88 specifies that the virtual machine is authorized to use DIAGNOSE code X‘88’ to validate user authorizations. For information about diagnose code X‘88’, see Setting up Security and refer to z/VM: CP Programming Services.

 5 
The XCONFIG statement specifies control parameters for the extended configuration facilities provided in the XC virtual machine architecture. The XCONFIG ADDRSPACE operand specifies the maximum number of nonprimary address spaces (sometimes known as data spaces) and the total size in bytes of all nonprimary address spaces that the virtual machine can own simultaneously.

MAXNUMBER 5 specifies the maximum number of nonprimary address spaces that this virtual machine can create and have existing concurrently.

TOTSIZE 5G specifies the maximum total size of all address spaces that this virtual machine can create and have existing concurrently, in our example, 5 gigabytes.

NOSHARE tells CP that the virtual machine is not allowed to make its address spaces available for access by other virtual machines.

 6 
MDISK 0191 … defines an A disk. IODFs in VM must reside on a minidisk that is formatted with 4 K blocksize.