March 3, 1980 Directory Program MDISK 191 2314 50 15 CPDSK4 W RDPASS WRX2* is an MDISK statement for a minidisk with read/write access to 15
cylinders located on a real 2314 labeled CPDSK4 starting at cylinder 50. A read password of RDPASS and a write password of WRX2* are
provided. This allows the other users to access the minidisk through
the directory LINK statement (see the description of the LINK
statement in this section) or the LINK command.
The SPOOL control statement specifies the unit record device that is to
be spooled. Multiple readers, punches, and printers may be specified,
each on a separate SPOOL card. The format of the SPOOL control
st atellent is: .-- , I Spool cuu devtype (class] L- I J
cuu is
de vtype
class
the virtual device
note that follows
control statement
channel. For CMS, used:
PRINTER OOE PUNCH 000 READER OOC is the device type: 1403 2501 1443 3203 3211 2540 R(EADER] 2540 P( UNCH] 3525 3505 address (1-to 3-hexadecimal digits). The
the description of ECMODE in the OPTION describes a restriction on specifying the
the followin9 unit record addresses must be
is a 1-character spooling class. The characters A through Z,
o through 9, and * are valid. For spool output devices, the
class governs the punching or printing of the real spooled
output. If this operand is omitted, the default class A is
used. This operand is required for all output devices defined
on the spool record. For spool input devices, the class
controls access to spool files by virtual card readers. The
default class for readers is an asterisk (*), which means the
reader can process any class of spool file.
For example: SPOOL ODE 1403 A
specifies a SPOOL record for a virtual 1403 at address ODE. The output class is A. 210 IBM VM/370 Planning and System Generation Guide

Directory Program
The DEDICATE control statement specifies that a real device is to be
dedicated to this user. 3330V (virtual 3330) volumes may be
specified via the DEDICATE statement. If the device is a unit record
device, input and output are not spooled by A real device may be
dedicated to only one user at a time. Should a device be specified as
aedicated in more than one directory entry, only the first user to log
on gains access to it. The format of the DEDICATE control statement is: , Dedicate cuu { rdev I[VOLID] volser} [R/O] [3330V] L-- ________________________________ . ________________________________________ cuu is the virtual device address (1-to 3-hexadecimal digits).
rdev is the real device address (1-to 3-hexadecimal digits). VOLID is the required keyword used if the volser is less than four
characters long. It is optional if volser is four, five, or
six characters long.
If the VOLID operand is used, the volume must be attached to
the system when the user logs on. When he logs off, the
operator can then detach the volume from the system.
volser is the volume serial number of a disk pack mounted on some
real disk storage device (1-to 6-alphameric characters) or of
an volume to be dedicated to the virtual machine. R/O 3330V specifies that the virtual
status. If this operand is
read/write.
device is to be in read-only
omitted, the status defaults to
specifies that
and attentions
all interruptions, including cylinder
received on the rdev are to be passed
faults
to the virtual machine in its cuu.
1. When you dedicate a 2305 device, both the real and virtual device
addresses must specify the first exposure on the 2305 (that- is,
device address 0 or 8). When you dedicate a 2305 or detach a
dedicated 2305 from a user, all 8 exposures are processed.
2. Use caution in defining the hexadecimal addresses of virtual
devices (cuu) in DEDICATE statements, in order to avoid a usage
conflict caused by control unit I/O interface protocol. The
following is an example of a virtual machine's DEDICATE statements
that can cause operational conflict.
DEDICATE 10E 30E (30R is a real 3211)
DEDICATE 10F 30B (30B is a 2400 tape device)
The virtual addresses of both the 3211 and the _tape device indicate
the use of the same channel and control unit. By definition the
devices are virtual and therefore will share one virtual control
unit (VCUBLOK) in CP. A real 3211 printer operates on a nonshared
subchannel, and the real 2400 device is designed for shared
subchannel operations. Both of these real devices are mapped to
the same VCUBLOK. Thus, the subsequent processing of a channel Part 2. Defining Your System 211