CPU

Read syntax diagramSkip visual syntax diagramDIRMaintPrefix Keywords1 CPU cpuaddr ?DELETEBASECPUIDxxxxxx
Notes:
  • 1 For more information on prefix keywords, see the DIRMAINT EXEC.

Purpose

Use the CPU operand of the DIRMAINT command to allow the general user to add, change, delete, or query the central processing unit (CPU) statement in a profile, user, or identity entry.

Operands

cpuaddr
specifies the address of the virtual processor being defined, changed, or deleted. The processor address can be any hexadecimal value from 0 to 3F.
?
issues a query against the specified CPU statement.
DELETE
deletes the specified CPU statement from the directory entry.
BASE
specifies that the CPU identified on this statement is defined as the base CPU.
CPUID xxxxxx
specifies the processor ID number that is stored in bits 8 to 31 of the CPU ID and is returned in response to the STIDP instruction.

Usage Notes

  1. You can use one or more of the prefix keywords (REQuest, TOsys, ASuser, BYuser, PRESET, FORuser, ATnode, NODIRectxa) with this command. These prefix keywords may be specified in any order, but each keyword may only be specified once.
  2. For more information on the CPU directory statement, see z/VM: CP Planning and Administration.
  3. The CPU operand is equivalent to the SETCPU operand.
  4. Successful execution of the DIRMAINT CPU operand depends on the MACHINE directory statement setting defining the maximum number of virtual processors allowed to be defined (indicated by the mcpu value). These rules apply:
    • Modification of an existing CPU statement is always valid. However, only one CPU statement can be given the BASE attribute.
    • Deletion of an existing CPU statement is always valid.
    • If a MACHINE statement does exist and the mcpu field contains a value, this value is the maximum number of allowable CPU statements.
    • If a MACHINE statement does not exist, or does not specify an MCPU value, only one CPU may be defined.

    If any of these rules are violated, CPU operand processing will terminate and an appropriate error message is issued.

  5. A new CPU statement is always added after all existing CPU statements in your directory entry unless your installation has chosen to sort by device addresses. The order of CPU statements determines the assignment of real processors to virtual CPUs.
  6. The CRYPTO operand is still accepted for compatibility purposes, but provides no function.