CPU Directory Statement
Purpose
The CPU statement specifies a virtual processor that is to be defined automatically for the virtual machine at LOGON time.
How to Specify
The CPU statement is allowed in profile, user, and identity entries. If specified, the CPU statement must appear before any device statements. (For a list of device statements, see Table 1.) The maximum number of CPU statements allowed in the virtual machine definition is controlled by the mcpu operand of the user's MACHINE statement, if specified.
The DEFINE CPU command provides additional parameters not supported on the CPU directory statement. The COMMAND directory statement can be used to specify the DEFINE CPU command and access these additional parameters.
Multiple CPU statements are allowed within an entry. If you specify CPU statements with the same processor address (cpuaddr) in a user or identity entry and in a profile entry, the statement in the user or identity entry overrides the one in the profile entry. Otherwise, the CPU statements in the user or identity entry and profile entry are additive.
If a BASE CPU is defined in both a profile and user or identity entry, the CPU statement in the user or identity entry overrides the CPU statement in the profile.
If you do not specify a CPU statement in a virtual machine definition, the address of the base virtual processor is X'00' by default.
Operands
- cpuaddr
- defines a virtual processor at the specified address. The address can be any 2-digit hexadecimal number from X'00' to X'3F'.
- BASE
- tells CP that this CPU statement defines the base virtual processor. You can only specify BASE on one CPU statement. If you do not specify BASE on any CPU statement, CP defines the base virtual processor as the CPU statement with the lowest virtual processor address (cpuaddr).
- CPUID bbbbbb
- provides the processor identification number to be stored in bits 8 through 31 of the CPU ID
that is returned in response to the store processor ID (STIDP) instruction. If the guest is
relocated, these bits do not change as a result of the relocation, even if the FORCE ARCHITECTURE or
FORCE DOMAIN options were used on the VMRELOCATE command.
The variable bbbbbb is a 6-digit hexadecimal number. (No checking is done to ensure that this number is unique in the virtual configuration.) For base processors, this option overrides the CPUID operand on the OPTION statement. For nonbase processors, it overrides the CPU ID of the base CPU. For more information about the CPUID operand, see OPTION Directory Statement.
Usage Notes
- The CPU directory statement cannot be used to define virtual CPUs of different processor types. To create these virtual CPUs, use the CP DEFINE CPU command in a COMMAND directory statement. For more information, see Specialty Engine Support.
- The protected application environment is supported only for virtual machines running a single processor. If this virtual machine is running a multiprocessor configuration, the SET CONCEAL ON command is rejected.
- Although the CRYPTO operand is not shown in the syntax for this statement, it is accepted for compatibility, but it provides no function.
- Dedication of a real processor to a guest is no longer supported, but the DEDICATE and NODEDICATE operands (which are not shown in the syntax for this statement) will still be accepted for compatibility reasons.
Examples
CPU 3E base CPUid 0000de
