z/VM: CP Planning and Administration - z/VM - IBM

Overviewspool files for users across multiple z/VM systems. For additional informationabout CSE, refer to Chapter 10, “Setting Up Cross System Extensions (CSE),” onpage 333.v Plan for security facilities. Facilities are available in z/VM to help protect thesystem from security and integrity exposures. For descriptions and use of thesefacilities, see Chapter 12, “Security and Integrity in z/VM,” on page 379.v Improve system availability by defining and saving multiple copies of theCP module. For more information, see Chapter 4, “Using the Stand-AloneProgram Loader,” on page 37.v Create the stand-alone dump utility program and place it on tape or DASD.For additional information on the stand-alone dump utility provided by z/VM ,refer to Chapter 13, “Using the Stand-Alone Dump Utility,” on page 403.User Planning and AdministrationThe following list describes user planning and administration tasks and where tofind information on each task:v Plan for any changes to command privilege classes. The user classrestructure feature lets you extend the privilege class structure of CP commands,DIAGNOSE codes, and certain CP system functions from eight classes to asmany as 32 classes. For detailed information on how to extend the privilegeclass structure, refer to Chapter 16, “Redefining Command Privilege Classes,” onpage 433.v Create a z/VM user directory. As mentioned under “Major z/VM Files” on page3, each user who can log on to z/VM must have an entry in the z/VM userdirectory. You can create your own directory or update the sample that z/VMprovides. See Chapter 17, “Creating and Updating a User Directory,” on page447 which contains detailed descriptions of the control statements you can codein the directory.v Define virtual machine modes and processor configurations. Coding theMACHINE statement in a user’s directory entry allows you to specify:1. The virtual machine mode (ESA, XA, or XC), which indicates the architecturethe virtual machine simulates (ESA/390 or ESA/XC).Note: XA mode is supported for compatibility and is functionally equivalent toESA mode. Some CMS applications may require the virtual machine tobe in XA mode.2. The maximum number of virtual processors the virtual machine can define.To define virtual processors, the virtual machine user must enter the DEFINECPU command.For information on the MACHINE directory control statement, see “MACHINEDirectory Control Statement (General)” on page 510.As an alternative to including a MACHINE statement in each user’s directoryentry, you can define the virtual machine mode and virtual processor capabilitiesfor a group of virtual machines by including the MACHINE directory statement ina directory profile. See “Creating Directory Profiles” on page 455.If the MACHINE statement is not included in the user’s directory entry or includedin a profile, the default virtual machine mode is XA and the maximum number ofvirtual processors the virtual machine can define is determined by the number ofCPU statements included in the user’s directory entry or in a profile. If no CPUstatements are included in the directory entry or a profile, the virtual machine hasno virtual multiprocessor capabilities.Chapter 1. Planning and Administration Overview 5