Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
DEVICE Initialization Statement z/OS JES3 Initialization and Tuning Guide SA32-1003-00 |
|
The XUNIT parameter of the DEVICE statement specifies the routing information for all JES3 and MVS™ device-related messages. The XUNIT parameter accepts an MVS routing code or a JES3 destination class for messages that pertain to the device being defined. If you want a particular RJP console to receive messages for this device, the message destination must be assigned to the RJP console through the DEST= parameter of the CONSOLE statement. For efficiency, the console should be near the device. Use the ROUTCODE parameter on the CONSOLE statement in the CONSOLxx parmlib member to assign message destinations to MCS consoles. As an example, suppose the following direct access and
tape devices are defined:
In order for RJP work station T0001 to receive messages associated with
these devices, the following CONSOLE statement would have to be specified:
The XTYPE parameter allows the specification of device class and volume
removability. These subparameters, normally defaulted to tape (TA) and removable
(RM), can be used to indicate a JES3-managed device that contains a permanently
resident volume. For example:
would establish the volume on local processor SY2 unit 230 as permanently
resident. If a device has multiple access, it should be specified in the XUNIT parameter
of the DEVICE statement for all processors. For example:
You can also specify that a device is defined to all processors
by using the processor name *ALL. For example:
When using *ALL, the same device number, message destination, and initial
online/offline status apply to every processor. You can define a range of
devices with a single device statement by using the NUMDEV keyword. For example:
indicates that
devices 230, 231, 232, 233, and 234 are defined on all processors. |
Copyright IBM Corporation 1990, 2014
|