ATTACH

Authorization

Privilege Class: B

Purpose

Operands

rdev

rdev1-rdev2

specifies a real device number, a list of real device numbers, or a range of real device numbers to be attached to the specified user or to the CP system. Specify a real device number as 4 hexadecimal digits. You may omit leading zeros. The maximum number of devices allowed in a range is 256.

If you are not specifying a virtual device number or volume label for the real device that you are attaching, the virtual device number defaults to the real device number. You can combine device numbers, lists of device numbers, and ranges of device numbers on a single command line.

If you are specifying a virtual device number for the device, you can specify only one real device number when you enter the ATTACH command.

ldev

ldev1-ldev2

specifies a logical device number, a list of logical device numbers, or a range of logical device numbers to be attached to the specified user. Specify a logical device number as an L followed by up to 4 hexadecimal digits. You may omit leading zeros.

If you are not specifying a virtual device number for the logical device that you are attaching, the virtual device number defaults to the logical device number. You can combine device numbers, lists of device numbers, and ranges of device numbers on a single command line.

If you are specifying a virtual device number or volume label for the device, you can specify only one logical device number when you enter the ATTACH command.

VOLid

indicates that a volume serial number, which must follow this keyword, is used to identify the real device. If the volume serial number is valid as an operand of the command (e.g., is a valid device number), specify VOLID to indicate that the operand is a volume serial.

volid

specifies the 1- through 6-character volume serial number of a real DASD.

EQid

indicates that a device equivalency ID, which must follow this keyword, is used to identify the real device. If the EQID is valid and only one unattached device with this EQID exists, the device will be attached. If more than one unattached device exists with the specified EQID, the first unattached device found will be used.

eqid

specifies a string of 1 - 8 alphanumeric characters for a user-specified EQID or a string of 50 alphanumeric characters plus a dash ("-") for a system-generated EQID.

userid

*

is the virtual machine that is to receive the device or devices. That virtual machine must currently be logged on to the system. If you are attaching a device to your own virtual machine, you can specify your user ID as an asterisk (*).

Use the keyword TO when:

• You specify a user ID with three numbers or fewer in a range of addresses or multiple device addresses
• You specify a user ID that could also be a valid hexadecimal device address (for example, CE)
• You specify a user ID as to or t.

vdev

is the virtual device number you want assigned to the device. The device number is assigned to an available virtual subchannel number, and may be as long as four digits.

PCIFunction

indicates that a PCI function ID, which must follow this keyword, is used to identify the real function.

rpfid

rpfid1-rpfid2

specifies a real PCI function ID or a range of PCI function IDs to be attached to the specified user. Specify a PCI function ID as 8 hexadecimal digits. You may omit leading zeros. The total number of PCI functions specified cannot exceed 256.

TO userid

is the virtual machine that is to receive the function or functions. That virtual machine must currently be logged onto the system. If you are attaching a function to your own virtual machine, you can specify your user ID as an asterisk (*).

AS vpfid

specifies the virtual PCI function ID you want assigned to the function. Specify a PCI function ID as 8 hexadecimal digits. You may omit leading zeros. This option is only valid if a single rpfid is specified. If omitted, the virtual PCI function ID will be the same as the real PCI function ID specified.

SYSTEM

makes the DASD available to CP for access to users' virtual disks, or for paging, spooling, and temporary disk functions. Indicates that crypto resources will be added to the system's shared pool.

volid

is the volume label of the volume on the device being attached. The system verifies the volume label on the device, so the label must be unique when compared with all other volumes attached to the system.

SYSAscii

indicates that the real ASCII console is to be attached to the specified user.

SYSAscii TO userid

is the user ID of the virtual machine that is to receive access to the real ASCII console. The virtual machine must be currently logged on to the system. A user ID of SYSTEM is not valid.

SYSAscii TO *

specifies that the virtual machine issuing the ATTACH command receives access to the real ASCII console.

n

n1-n2

specifies a single crypto adapter number, a list of adapter numbers, a range of adapter numbers or a combination of these, to be attached. If you are specifying a list of numbers, insert at least one blank between the numbers you specify. If you are specifying a range of numbers, insert a hyphen (-) between the numbers you specify. The number is a decimal number between 0 and 255.

p

p1-p2

specifies the crypto domain number, a list of domain numbers, a range of domain numbers or a combination of these, to be attached to the virtual machine or system. If you are specifying a list of domain numbers, insert at least one blank between the numbers you specify. If you are specifying a range of domain numbers, insert a hyphen (-) between the numbers you specify. The domain number is a decimal number between 0 and 255.

Options

R/O

can be used for DASD and tape devices that are attached to a user. This allows the system operator to apply read-only protection to a user's disk or tape.

CP ignores the R/O operand for any device number that does not correspond to a TAPE or DASD device.

SINGLEuser

dedicates a real tape device to a single user. This is the default.

MULTIuser

attaches a real tape device to be serially shared with other users. See Usage Note 16.

WITH ASSIGN

specifies that the tape device you want attached to the user will be assigned to the user system. CP ignores this operand for any tape device that does not support ASSIGN and UNASSIGN CCWs.

WITH NOASSIGN

specifies that the tape device you want attached to the user must not be assigned to the user system. This gives the guest the ability to control the assignment of the tape. CP ignores this operand for any tape device that does not support ASSIGN and UNASSIGN CCWs.

Note: When a tape attached with NOASSIGN is detached:

• The tape is not rewound or unloaded.
• If the tape was attached with SINGLEUSER (the default), CP does not change the ASSIGNED or UNASSIGNED status of the device. It is the responsibility of the guest to enter the ASSIGN CCW when it needs the tape and to enter the UNASSIGN CCW when it is finished using the tape.
• If the tape was attached with MULTIUSER, CP changes the status of the device to UNASSIGNED.

NOCPMS

indicates that attach processing should not issue MODE SET CCWs to a tape device to initialize the Device Control Pages of the device. This option is ignored for any tape device that does not support the X'CB' MODE SET CCW. This option is not available on the DEDICATE User Directory Statement.

MODE SET CCWs are issued only if ASSIGN processing is also done. Thus, NOCPMS performs no function if NOASSIGN is specified.

The KEY option will issue MODE SET CCWs, but will respect the existing device settings if used in conjunction with the NOCPMS option.

CPMS

indicates that CP will issue MODE SET CCW's with either default mode (no CPMS parameter) or with the specified mode parameter. Mode validation is done in respect of the tape hardware capabilities. CPMS and NOCPMS option cannot be issued together.

EFMT1

indicates the 512 track recording format.

EFMT2

indicates the 896 track recording format.

EFMT3

indicates the 1152 track recording format.

EFMT4

indicates the 2176 track recording format.

WITH DEVCTL

means that the device accepts CCWs that have an effect on resources and functions directly related to the device. See Usage Note 6 for default values.

WITH NOCTL

means that the device does not accept any CCWs that can exercise control of subsystem resources or functions, regardless of whether they directly relate to the device.

WITH SYSCTL

means that the device accepts CCWs that have a direct global effect on subsystem resources and functions, not just on those related to the device. See Usage Note 6 for default values.

NOQIOAssist

indicates that the devices are not eligible for Queued-I/O assist.

KEY keyalias

prepares CP to enable a device's hardware encryption on behalf of a guest that is not able to manage the support itself. If a keyalias is specified (up to two are allowed), CP will use the encoding mechanism and key label described by the alias while setting up the encryption environment. If no aliases are supplied, the external key manager's default keys will be used.

USERACCessid userid

to allow a user (guest) the ability to give FCP LUN access to the specified userid. This is a shortcut to redefining entries in the Access Control Table (ACT), and assumes the user has authority to the LUN as defined in the ACT. Please refer to Linux documentation for details on creating and maintaining the ACT for FCP configuration.

Usage Notes

1. If you are attaching a DASD with logical addresses, the real device number you specify must be the base address for the device, and the virtual device number you specify must follow the addressing rules for base addresses.
2. The ATTACH command will not affect the various draining status indicators, so you can set the desired draining status before you attach a DASD to your system.
3. If you mount and ready a device that contains virtual minidisks after you have loaded VM onto the system, you must attach that device to the system if you want to use it. If you log on after the device has been attached, you gain access to the disk as provided by your entry in the system directory. If you were logged on before the volume was attached to the system, you must use the CP LINK command to gain access to the virtual disks.
4. CP processes all the device numbers you specify, even if it encounters errors when attempting to attach the devices. So, if you enter: attach 108-10f user1 r and real devices 10A and 10D were not ready and online, the following devices would be successfully attached: 108, 109, 10B, 10C, 10E, 10F. Messages tell you whether devices are successfully attached.
5. You can use the system directory DEDICATE statement to attach real devices to each virtual machine. Then, when users successfully log on, the devices (if online and available) are automatically attached to their virtual machine. This function saves Class B users the trouble of issuing multiple ATTACH commands for the devices.
6. Levels of control (SYSCTL/DEVCTL/NOCTL)
   1. The default control level value is normally DEVCTL.
   2. The SYSCTL, DEVCTL, and NOCTL operands apply only to DASD on a cached control unit. If one of these operands is specified for a noncached DASD, the device is attached and a response is issued stating that the operand was ignored.
   3. Specifying a level of control (NOCTL, DEVCTL, or SYSCTL) for a DASD attached to a cache storage control unit authorizes CP to accept particular control CCWs.

      Table 1 shows the additional control CCWs CP accepts for a level of control. The DEVCTL column shows the CCWs CP accepts in addition to those it accepts for the NOCTL level of control. The SYSCTL column shows the CCWs CP accepts in addition to those it accepts for the DEVCTL and NOCTL levels of control.

      Table 1. DASD Control Levels

      Additional Control CCWs Accepted for DEVCTL	Additional Control CCWs Accepted for SYSCTL
      Set subsystem mode Activate caching for device Deactivate caching for device Activate DASD fast write Deactivate DASD fast write Force deactivate DASD fast write Perform Subsystem Function Establish duplex pair Terminate duplex pair Suspend duplex pair Direct I/O to one device of the duplex pair	Set subsystem mode Make cache available Make cache unavailable Force cache unavailable Make NVS available Make NVS unavailable Activate cache fast write Deactivate cache fast write Perform Subsystem Function Destage Modified Tracks Set Cache Allocation Parameters Suspend/Resume Function

7. When an authorized user issues the GIVE command to transfer control of a tape drive, the ATTACH command is invoked.
8. The ATTACH command may be used to attach duplex volumes to a guest virtual machine or the system. Only the primary duplex volume may be attached to the system. Either the primary volume, the secondary volume, or both volumes may be attached to a guest virtual machine.

   When a duplexed volume is attached to a virtual machine (or to the system), the responses generated will indicate that the volume was either the primary duplex volume or the secondary duplex volume of a duplex pair.

9. For a guest virtual machine to establish a duplex pair, both of the affected volumes must be physically attached to the same 3990 storage control subsystem, and each volume must be logically attached to that guest with either DEVCTL or SYSCTL. In order for a guest virtual machine to suspend or stop a duplex pair, the guest must have DEVCTL or SYSCTL over the primary volume of the duplex pair.

   Duplexing is only allowed if both volumes are dedicated, or both are DEVNO-defined full-pack minidisks. CP does not allow a guest virtual machine to duplex a full-pack minidisk with a dedicated device.

10. The ATTACH command cannot be used to attach DEVNO-defined minidisks or secondary volumes of duplex pairs to the system.
11. The ATTACH command cannot be used to attach virtual disks in storage.
12. The ATTACH command will verify that the correct allocation map is used by the volume. Only FBA and devices with greater than 4K cylinders will use the extent-based allocation map. All other DASD will use the cylinder-based allocation map.
13. If a device is being throttled, you cannot attach it to the system as a CP-owned device. To display whether a device is being throttled, use the QUERY THROTTLE command (see QUERY THROTTLE). To turn throttling off for a device, use the SET THROTTLE command (see SET THROTTLE).
14. When attaching Parallel Access Volume DASDs:
    • To a guest, the base Parallel Access Volume must be attached first, before any associated alias Parallel Access Volumes. The associated alias Parallel Access Volumes can only be attached to the same guest as the base Parallel Access Volume.
    • To the system, the base Parallel Access Volume must be attached first, before any associated alias Parallel Access Volumes. Alias Parallel Access Volumes can be attached to the system, but are only exploited for VM I/O if they contain minidisk (PERM) or temporary disk (TDSK) allocations. Other CP volume allocations receive no benefit from system-attached alias Parallel Access Volumes.
15. HyperPAV aliases that are attached to the system are exploited by:
    • VM I/O, for minidisk (PERM) and temporary disk (TDSK) allocations
    • The CP paging subsystem, for directory (DRCT), page (PAGE), and spool (SPOL) allocations, when the feature has been enabled through one of the following:
      • In the system configuration file:
        • The PAGING_ALIAS FEATURES statement (the preferred method)
        • The FEATURES ENABLE PAGING ALIAS statement
      • The SET PAGING command.
16. The MULTIUSER function is intended for guest operating systems that manage their own assignment of tape devices. It is not intended for CMS unless some external means of managing assignments or serializing access to the tape device among the sharing users is explicitly implemented. Third party assignment and multiple system assignment (Control Access CCW) are not supported.

    To share a tape device, a user must specify the MULTIUSER option when attaching the device, or the CP directory entry for that user must contain a DEDICATE statement for the device that includes the MULTIUSER operand. If the first user to log on attaches the device without specifying MULTIUSER, or has a DEDICATE statement for the device that does not include MULTIUSER, the device becomes dedicated to that user. The device then cannot be attached as MULTIUSER by any user until it is detached by the user to whom it is dedicated.

    The MULTIUSER function is valid only for 3480, 3490, and 3590 tape devices.

17. The USERACCessid option applies only to first-level and second-level users. If it is attempted on a third-level or higher virtual machine, the request is translated into corresponding first-level and second-level information only.
18. The KEY option (and any supplied keyaliases) are valid only for 3592 tape drives that support hardware encryption. It is to be used only for those guests that do not exploit hardware encryption itself. If used with guests that do exploit hardware encryption, problems may occur such as missing interrupts or mode sense errors.
19. Encryption settings can persist on a device, via an ATTACH with encryption settings followed by a DETACH LEAVE or through an ATTACH MULTIUSER with encryption settings, as two examples. An ATTACH without encryption settings for either case will then pick up those settings on the device, while an ATTACH with encryption settings will fail if the encryption settings differ from what is currently associated with the device.
20. During an ATTACH TO SYSTEM command, a test is performed to determine if any non-PERM space is the Target of a FlashCopy® relationship. If so, the command fails with message HCP2463E.
21. ATTACH fails if the device being attached has CHPID Virtualization on and the device is an unsupported DPS=NO DASD or TAPE. The following message is issued:

    HCP6863E Device ldev has not been attached because it is a DPS=NO device and CHPIDVirtualization option is not specified for the user in the directory.

22. When issuing an ATTACH rdev to SYSTEM command for a CP owned volume, note that for SPOOL and DIRECTORY volume types extents are limited to cylinders 0-65519, and for PAGE volume types extents are limited to cylinders 0-1182005. TEMP and PARM disks can be located anywhere on the volume, but the PARM disk size is limited to 65520 cylinders. PERM space allocation is allowed anywhere on the volume.
23. When a CP-owned DASD volume with SPOOL extents is attached to a member of an SSI cluster, the volume will be automatically attached to the other active members where the device is online and not already attached. Also, if the volume is not in the CP-owned list on another active member where the device is being attached, the attach process will automatically add the volume to the CP-owned list on that member.
24. When ENFORCE_BY_VOLID has been enabled in the system configuration file, ATTACH commands will be rejected and message HCP6419E will be issued unless the ATTACH command specifies targets by VOLID.
25. The z/VM® CP definition of a virtual function is a guest's view of a real function. This should not be confused with a virtual function associated with a PCI function where an adapter, identified by its PCHID, supports more than one PCI function.
26. The maximum value of the virtual function id number may be model dependent and limited by the machine and may also be limited by the guest operating system or application using the function. For example, z/OS® 2.1 Communications Server IP Configuration allows a 2-byte hexadecimal value in the range 0-00FF.
27. When UID uniqueness enforcement is enabled by the SET IO_OPT UID command, the attach of a PCI function will be rejected if another function with an identical UID value is already attached to the target guest.
28. The DEFINE CRYPTO APVIRTUAL command will give a virtual machine access to the system's shared crypto resources for the current logon session. The CRYPTO APVIRTUAL user directory statement will give a virtual machine access to the system's shared crypto resources at each logon.
29. The ATTACH CRYPTO TO SYSTEM command can be used to assign crypto resources to the system for shared use. This assignment can also be made during system IPL using a CRYPTO APVIRTUAL statement in the system configuration file.
30. The ATTACH CRYPTO TO userid command may be used to provide a virtual machine with dedicated access to one or more crypto resources for the duration of a logon session. This is the same authority given to a virtual machine with a CRYPTO APDEDICATED statement in the directory entry. The CRYPTO APDEDICATED directory statement will give the virtual machine access to the specified crypto resources at each logon. The ATTACH CRYPTO command will give the virtual machine access to the specified crypto resources for the current logon session only.
31. Dedicated crypto resources must be assigned to a virtual machine as a rectangular resource set so that the resources available to a virtual machine are a cross-product of all assigned adapters and domains.

    In order for a virtual machine to have dedicated access to a crypto resource, each specified domain number must be available for dedicated use by this virtual machine on all specified adapter numbers. If one or more domains on an adapter are not available for dedicated use by this virtual machine, then none of the domains on the adapter will be assigned. Any requested domains that are not assigned to the LPAR that the z/VM system is running on will be eliminated from the request and will not be reason to deny access to the remaining requested adapters or domains.

    For example, assume that domain 1 on adapters 1, 2, and 3 are resources that are dedicated to virtual machine vmach1. You can then attach domain 2 to vmach1 only if domain 2 is available to vmach1 on all of adapters 1, 2, and 3. If domain 2 is not available on one or more of adapters 1, 2, or 3, then you cannot attach domain 2 to vmach1 on any of adapters 1, 2, or 3.

    For more examples, see Examples.

32. A crypto adapter must be configured in CCA coprocessor mode or accelerator mode in order to be attached to the system for shared use.
33. For information on planning and managing crypto resources on a z/VM system, see Crypto Planning and Management in z/VM: CP Planning and Administration.

Responses

The receiver of the device attached, the user who issued the ATTACH command, and the primary system operator all receive messages indicating that the ATTACH was successful.

Response 1:

{rdev…  } ATTACHED TO userid
{rdev–rdev}
{ldev…  }
{ldev–ldev}

{type rdev} ATTACHED TO userid vdev [R/O] [WITH SYSCTL] [PRIMARY DUPLEX  ]
{type ldev}                               [WITH DEVCTL] [SECONDARY DUPLEX]
                                          [WITH NOCTL ] [PAV BASE        ]
                                                        [PAV ALIAS       ]
                                                        [HYPERPAV BASE   ]
                                                        [HYPERPAV ALIAS  ]

Response 2:

Depending on the command format the Class B user enters, this response indicates the devices attached to a specified user's virtual machine (and, if appropriate, the virtual device number, access mode, the level of control, and the duplex state, the PAV state, or the HyperPAV state for the device) or indicates that the device has been attached to the CP system.

{rdev…  } ATTACHED TO userid
{rdev–rdev}
{ldev…  }
{ldev–ldev}

{type rdev} ATTACHED TO userid vdev [R/O] [WITH SYSCTL] [PRIMARY DUPLEX  ]
{type ldev}                               [WITH DEVCTL] [SECONDARY DUPLEX]
                                          [WITH NOCTL ] [PAV BASE        ]
                                                        [PAV ALIAS       ]
                                                        [HYPERPAV BASE   ]
                                                        [HYPERPAV ALIAS  ]

DASD rdev ATTACHED TO SYSTEM volid [PRIMARY DUPLEX  ]
                                   [PAV BASE        ]
                                   [PAV ALIAS       ]
                                   [HYPERPAV BASE   ]
                                   [HYPERPAV ALIAS  ]

Response 3:

One of the following responses is sent to the primary system operator, if this operator did not issue the command. The response indicates that the device has been attached to either the specified user's machine (at virtual device number vdev) or to the CP system. The originator field designates the user ID of the user who issued the command.

{rdev…  } ATTACHED TO userid BY originator
{rdev–rdev}
{ldev…  }
{ldev–ldev}

{type rdev} ATTACHED TO userid vdev BY...con't
{type ldev}

Continued:

originator [R/O] [WITH SYSCTL] [PRIMARY DUPLEX  ]
                 [WITH DEVCTL] [SECONDARY DUPLEX]
                 [WITH NOCTL ] [PAV BASE        ]
                               [PAV ALIAS       ]
                               [HYPERPAV BASE   ]
                               [HYPERPAV ALIAS  ]

DASD rdev ATTACHED TO SYSTEM volid
BY originator [PRIMARY DUPLEX  ]
              [PAV BASE        ]
              [PAV ALIAS       ]
              [HYPERPAV BASE   ]
              [HYPERPAV ALIAS  ]

Response 4:

ctlevel IGNORED - INVALID FOR rdev

ctlevel

is the level of control: SYSCTL, DEVCTL, or NOCTL.

rdev

is the real device number.

Response 5:

The directory on volume volume at address
rdev has been brought online.

Response 6:

SYSASCII attached by originator

The variable originator designates the user ID of the person who entered the command.

SYSASCII attached to userid

SYSASCII attached to userid by originator

The response indicates that the ASCII console has been attached to the specified user's virtual machine. The variable originator designates the user ID of the person who entered the command.

The receiver of the PCI function attached, the user who issued the ATTACH command, and the primary system operator all receive messages indicating that the ATTACH was successful.

Response 7:

PCI FUNCTION rpfid ATTACHED TO userid vpfid

Response 8:

PCI FUNCTION rpfid ATTACHED TO userid vpfid BY originator

Response 9:

Crypto AP nnn Domain ppp attached to target

Response 10:

Crypto AP nnn Domain ppp attached to target by originator 

Response 11:

Crypto AP nnn Domain ppp attached to SYSTEM

Response 12:

Crypto AP nnn Domain ppp attached to SYSTEM by originator 

nnn

is the adapter number.

ppp

is the domain number.

Messages

• HCP002E Invalid operand - operand
• HCP003E Invalid option - {option| command contains extra option(s) starting with option}
• HCP009E Invalid range - range
• HCP013E Conflicting option - option
• HCP020E Userid missing or invalid
• HCP021E A real PCI function ID was not supplied or it is invalid.
• HCP022E A virtual PCI function ID was not supplied or it was invalid.
• HCP023E VOLID missing or invalid
• HCP026E Operand missing or invalid
• HCP040E Device {rdev|vdev|ldev} does not exist
• HCP040E PCI function rpfid does not exist
• HCP045E userid not logged on
• HCP046E type rdev | rpfid offline
• HCP046E SYSASCII offline
• HCP048E No device with EQID eqid exists.
• HCP049E type vdev in use
• HCP120E type {rdev | ldev | rpfid} not {attached | given}; userid { vdev | vpfid already defined
• HCP122E type {rdev | ldev | rpfid} already attached to userid
• HCP122E SYSASCII already attached to userid
• HCP125E DASD rdev EQID eqid already attached to system
• HCP125E DASD rdev volid volid already attached to system
• HCP126E DASD rdev error reading volid
• HCP127E DASD rdev volid volid does not match
• HCP128E DASD rdev error reading allocation record
• HCP130E No devices with EQID eqid are available to attach with the parameters provided.
• HCP142E type rdev not drained
• HCP153E Device {vdev|range} exceeds maximum number of virtual devices
• HCP155E Device rdev has not been attached to the system because it is not a DASD device.
• HCP263E Too many operands were supplied for this command.
• HCP845E DASD rdev not attached; paging addresses offline
• HCP1014E A required option is missing
• HCP1100E A logical device number was not supplied or it is invalid.
• HCP1101E DASD rdev is not supported as a system-owned device.
• HCP1102E DASD rdev has not been attached because the paging subsystem is already owned by userid.
• HCP1103E DASD rdev has not been attached because a real DASD paging subsystem must map to only one virtual paging subsystem.
• HCP1104E DASD rdev has not been attached because multiple real DASD paging subsystems must not map to the same virtual DASD paging subsystem.
• HCP1105E Tape rdev not attached; tape assigned elsewhere.
• HCP1107E Attach failed; I/O error on tape rdev
• HCP1107E Attach failed; encryption requires tape rdev to be positioned at the beginning-of-tape
• HCP1113I DASD rdev was not ATTACHed to the SYSTEM because this operation would conflict with an MDISK definition for user userid.
• HCP1114I DASD rdev was not ATTACHed to the SYSTEM because it is the secondary in a duplex pair.
• HCP1116E Tape rdev not attached; the tape is being rewound.
• HCP1117I DASD rdev was not ATTACHed to the SYSTEM because it is the secondary in a PPRC pair or a cascading intermediate PPRC volume.
• HCP1124I An allocation map containing invalid data was found on DASD rdev volume volid; the device is not attached.
• HCP1125I The allocation map for DASD rdev, volume volid contains an area that is currently undefined. That area will be ignored.
• HCP1128E Device rdev not attached; MULTIUSER or SINGLEUSER not supported on this device.
• HCP1128E Device rdev not attached; hardware encryption not supported on this device.
• HCP1128E Device rdev not attached; a mismatch in hardware encryption settings was detected.
• HCP1128E Device rdev not attached; user is not authorized.
• HCP1128E Device rdev not attached; unsupported mode specified.
• HCP1129I type rdev has invalid volume label.
• HCP1129I type rdev has invalid volume prefix.
• HCP1150E DASD {rdev|vdev} is not a valid base exposure.
• HCP1168E PCI function rpfid cannot be attached to userid because a function with the same UID is already attached to that guest.
• HCP1280E Device vdev not usable; reserve lost [by userid as vdev]
• HCP1281I Path channel to device rdev now offline; path group ID mismatch.
• HCP1401I Expanded storage is not supported.
• HCP1561I Real device rdev forced R/O; unauthorized for R/W.
• HCP1728E AP Crypto resources are not installed on this system.
• HCP1728E Crypto AP apnum Domain domnum is not assigned to this system.
• HCP1728E Crypto AP apnum is not assigned to this system.
• HCP1728E Crypto Domain domnum is not assigned to this system.
• HCP1737E Crypto AP apnum Domain domnum cannot be attached to SYSTEM because it is attached to a user.
• HCP1737E Crypto Domain domnum cannot be attached to SYSTEM because it is not configured in coprocessor or accelerator mode.
• HCP1737E Crypto AP apnum Domain domnum cannot be attached to SYSTEM because it does not match the currently defined shared type.
• HCP1738E Only APs or Domains can be specified, not both, when attaching AP crypto resources to a user that already has dedicated AP crypto resources assigned.
• HCP1738E Both APs and Domains must be specified when attaching AP crypto resources to a user that does not have dedicated AP crypto resources already assigned.
• HCP1739E Dedicated AP crypto resources cannot be attached to an APVIRTUAL crypto user.
• HCP1747E Crypto AP apnum Domain domnum is already attached to SYSTEM.
• HCP1748E Crypto AP apnum cannot be attached because not all domains assigned to this user are free on this AP.
• HCP1748E Crypto Domain domnum cannot be attached because this domain is not free on all APs assigned to this user.
• HCP1748E Crypto AP apnum Domain domnum cannot be attached.
• HCP1749E AP crypto resources on AP apnum are already attached to this user.
• HCP1749E AP crypto resources on domain domnum are already attached to this user.
• HCP1753E There is no directory online because the directory on volume volid at address rdev is not valid.
• HCP1831E The command could not be completed because of a temporary condition. Try again later.
• HCP2462I extenttype extent on CP-OWNED volume volser, tracks cccc/hh to cccc/hh, is the Source for FlashCopy Relationship sequence.
• HCP2463E extenttype extent on CP-OWNED volume volser, tracks cccc/hh to cccc/hh, is the Target for FlashCopy Relationship sequence.
• HCP2768E Missing user ID
• HCP2768E Missing crypto domain number
• HCP2768E Missing crypto AP number
• HCP2777I Option option has been ignored.
• HCP2826E operand contains invalid UTF-8 data: data.
• HCP2890E CSE I/O error, code cc, volume volid; LINK commands may fail.
• HCP3173E Device device is reserved for system use.
• HCP5780E Adjunct does not support the command subcommand command
• HCP6000E The range of device numbers cannot exceed 256.
• HCP6005E Option option is not supported by z/VM.
• HCP6202E The {spool|temporary disk|directory} cylinders were ignored on system volume volid.
• HCP6275E An error occurred writing to the subchannel for device rdev, code = code.
• HCP6419E DASD rdev has not been attached because the system requires it to be attached with the VOLID parameter.
• HCP6430E ATTACH cannot complete because the associated PAV base is quiesced for Hyperswap.
• HCP6430E ATTACH cannot complete because there is at least one base device in this HyperPAV pool that is quiesced for Hyperswap.
• HCP6643E Device rdev not attached to SYSTEM. Device contains spool extents and is already attached on system system.
• HCP6643E Device rdev not attached to SYSTEM. Device contains spool extents and is in slot slot. System system contains volid volid.
• HCP6643E Device rdev not attached to SYSTEM. Device contains spool extents and is in slot slot. This slot does not exist on system system.
• HCP6643E Device rdev not attached to SYSTEM. Device offline on system system.
• HCP6643E Device rdev not attached to SYSTEM. SSI cluster error, code code.
• HCP6644E Device with EQID eqid not attached to SYSTEM. Device contains spool extents and has been attached on other systems in the SSI cluster and could not be attached to this system.
• HCP6645E SSI cluster is in safe mode; command rejected.
• HCP6706E Invalid user ID
• HCP6706E Invalid Crypto Domain number
• HCP6706E Invalid Crypto AP number
• HCP6790I ATTACH processing halted. The next function that would have been processed is rpfid
• HCP6807E Device rdev is being throttled and cannot be attached to the system as a CP-owned device.
• HCP6860E Device rdev cannot be attached to the system because it is an alias Parallel Access Volume for which the base is attached to a user.
• HCP6860E Device rdev cannot be attached to the system because it is an alias Parallel Access Volume for which the base is free.
• HCP6863E Device rdev has not been attached because it is an alias Parallel Access Volume for which the base is free.
• HCP6863E Device rdev has not been attached because it is an alias Parallel Access Volume for which the base is in use by another user.
• HCP6863E Device rdev has not been attached because it is an alias Parallel Access Volume for which the base is in use by the system.
• HCP6863E userid: Device rdev has not been attached because it is a DPS=NO device and the CHPID Virtualization option is specified for the user in the directory.
• HCP9968E The key alias contains leading or trailing blanks or an empty string.