SET RDEVICE

Authorization

Privilege Class: B

Purpose

Use SET RDEVICE to add, change, or clear the system's definition of a set of real devices.

The following sections describe the syntax of SET RDEVICE commands for clearing real devices and for adding and changing these real devices:

  • Advanced function printers
  • Card punches
  • Card readers
  • Communication controllers
  • DASDs
  • Graphic display devices
  • Impact printers
  • Integrated communication adapters
  • Special devices
  • Tape units
  • Unsupported devices
  • 3270 displays
  • 3800 printers.

Usage Notes

  1. Once you have defined a device at a certain address, you can replace that device with another device of a different class. The following are considered to be discrete device classes:
    • DASDs
    • Graphic display devices
    • Special devices (3088s, CTCAs, 37x5)
    • Special switching devices
    • Tape drives
    • Terminals
    • Unit record devices.
  2. If you change the type of device for a given device address, the features previously defined for that device are returned to their defaults. When you change any feature other than device type for the device at a certain address, however, the other features remain the same. For example, assume you have an IBM® 3800 Model 1 printer defined at address 0500 and CHARS GF10 and AFP YES specified and you want to replace it with an impact printer. When you use the SET RDEVICE TYPE IMPACT_PRINTER command to tell CP the new printer is in place, CP resets all the other features to their defaults. If you leave the 3800 printer in place, however, and use SET RDEVICE to specify a flash overlay (SET RDEVICE … FLASH flashlib), CP leaves all the other features unchanged.
  3. You must use the VARY command to take a device offline before you can redefine it.
  4. By default, CP issues a sense ID request to gather information about the device that you are defining or changing. If you prefer to explicitly define or change the device, you can stop CP from issuing the sense ID request by specifying the NOTSENSED operand. The only exception is the SET RDEVICE Unsupported Devices command. Because the device is unsupported, you must explicitly define that device. For information about the DEVICES Statement, see z/VM: CP Planning and Administration.
  5. The SET RDEVICE command cannot be used to change the device definition of any device that has a static device definition on an RDEVICE macro in the HCPRIO ASSEMBLE file.

Responses

After CP has issued one of the following messages for each device address, the following summary response is displayed:
xxx RDEV(s) specified; yyy RDEV(s) changed; zzz RDEV(s) created

Messages

CP issues one of the following messages for each device address affected by a SET RDEVICE command. These two messages indicate that the SET RDEVICE command succeeded:

Messages:

  • HCP6722I Characteristics of device rdev were set as requested.
  • HCP6722I Created RDEV for device rdev.

The following messages indicate that the SET RDEVICE command failed:

  • HCP1550E Device rdev device class does not match requested device class.
  • HCP1550E Device rdev is not offline.
  • HCP6580E Device rdev is active
  • HCP6760E Device rdev is boxed.
  • HCP6760E Device rdev is not offline.
  • HCP6765E Device rdev cannot be changed because of an old HCPRIO definition.
  • HCP6862E Device rdev cannot be changed or deleted because it is a base Parallel Access Volume for which an alias exists.
  • HCP6870E Device rdev is attached to a guest
  • HCP6895E RDEV rdev cannot be changed or deleted because it is static device definition from HCPRIO