ADJUNCT

Authorization

Privilege Class: G

Purpose

Use the ADJUNCT command to control the operation of an adjunct virtual machine.

An adjunct is a second virtual machine configuration running under your userid, distinct from the configuration created when your userid is logged on or autologged (called the principal configuration). Each configuration has its own virtual CPU(s), virtual storage (memory), and virtual devices, and can IPL a different instance of an operating system. The adjunct is intended to run CMS, to give you access to CMS files and tools, for example, to aid in debugging the operating system in the principal configuration while keeping the principal's operating system intact.

When both principal and adjunct configurations exist for a user, only one is runnable at a time. When the adjunct is started or resumed, the principal is suspended, and vice versa.

Operands

START: The ADJUNCT START operation is analogous to LOGON for the primary configuration. It creates and IPLs an adjunct configuration, suspends execution of the principal configuration, switches the terminal session (if connected) from the virtual console of the principal to that of the adjunct, and transfers control to the adjunct configuration.
END: Logs off the adjunct, leaving the principal configuration active.
Begin
RESume: Suspends execution of the principal configuration, switches the virtual console to the adjunct, and transfers control to the adjunct configuration. The adjunct must already have been started. This operation is the adjunct analog to the CP BEGIN command for the principal configuration.
Stop
SUSpend: Puts the adjunct into a soft-stop state and transfers control back to the principal configuration. This operation is the adjunct analog to the CP STOP command for the principal configuration.
CP command: Permits a user or program in the principal configuration to direct commands to the adjunct configuration. Typical use includes the ability to re-IPL the adjunct when necessary (ADJUNCT CP IPL).

Usage Notes

In order for you to create an adjunct, the feature must be enabled for the z/VM system and authorized for you by the system administrator. The administrator provides the virtual machine definition that specifies how the adjunct configuration is instantiated. Information on how to enable and set up adjuncts appears in z/VM: CP Planning and Administration, in the description of the FEATURE ENABLE ADJUNCTS configuration statement and the ADJUNCT directory statement.
To direct a command from the adjunct configuration to the principal, use the CPU prefix command, for example, CPU * DEFINE STORAGE 4G or CPU ALL DISPLAY PSWG.
Use the QUERY ADJUNCT command to determine the state of your adjunct configuration.

Messages

HCP002E Invalid operand - operand
HCP003E Invalid option - {option|command contains extra option(s) starting with option}
HCP026E Operand missing or invalid
HCP643E Adjunct feature is not enabled on this system
HCP1461E No adjunct configuration defined
HCP5768E userid Adjunct does not exist
HCP5769E userid Adjunct already exists
HCP5770E userid Adjunct is not exploitable