Directory Program by the first available processor from the Vft/370 dispatch
queue. An affinity setting in the Vft/370 directory can be
overridden by the CP SET AFFINITY command. If the system is
running in attached processor mode and an error forces
recovery to uniprocessor mode, the affinity setting of virtual
machines assigned to the attached processor is nullified and
virtual machine processing may be continued on the main
processor.
The IPL control statement contains a one-to eight-character name of the
system (or one-to three-digit I/O device address) to be loaded for the user when he logs on. This statement is optional; if specified, it must
follow the USER statement, and must precede the first device statement (CONSOLE, MDISK, or SPOOL). The IPL statement can be overridden by the
user at logon time by specifying "LOGON userid NOIPL". If the user is the primary system operator, an automatic IPL is n2£ performed when he logs on.
The format of the IPL statement is:
r , Ipl iplsys
L
iplsys is a one-to eight-character system name or the virtual
address of the device containing the system to be loaded.
The CONSOLE control statement specifies the virtual console. The format
of the CONSOLE control statement is: ro- , Console cuu devtype (class]
L
cuu is the virtual device address of one to three hexadecimal
digits.
devtype is the device type: 1052 3210 3215
Note: The system accepts any of the devtypes indicated regardless of the real console or terminal being used. Device
types 3275, 3276, 3277, 3278, 3036, 3066, 3138, 3148, 3158,
2741, and 3767 cannot be specified. Only one console can be
specified. If a different console is sometimes required, use
the CP DEFINE command to change the console address or add an
alternate console. 206 IBM VM/370 Planning and System Generation Guide

class
Directory Program
is a one-character spooling class. A through Z and 0 through q are valid. The class governs the printing of the real
spooled output. If the class operand is omitted, the default
is class T and is for console spooling.
For more information about defining consoles, including a tutorial
discussion, see VM/370 Operating Systems in Virtual The MDISK control statement describes the cylinder extent on a direct
access device to be owned by the user. The DASD area assigned with this
statement becomes the user's minidisk. Neither CP nor the directory checks that minidisks defined with
the MDISK statement do not overlap each other and (for 3330, 3340, and 3350 disks) that they do not overlap the "alternate track" cylinders at
the end of the real disk. If overlap occurs, file damage is inevitable.
The format of the MDISK control statement is:
r--------------------------------- , Kdisk cuu devtype {CYlr cy Is volser [mode [pr [pw [pm J J J J} , __ T-DISK cyls . I cuu
devtype {
CYlr } T-DISK is the virtual device address of 1 to 3 hexadecimal digits. is the device type: 2305 2311 Top
2311 Bottom
2314
2319 3330 3340 3350 (Top half of a 2314 or 2319)
(Bottom half of a 2314 or 2319)
For a 3350 device in native mode, specify 3350 as the device
type. For a 3350 used in 3330 compatibility mode, specify 3330. Specify a 3344 disk as a 3340, and a 3333 as a 3330. For a 3330V system volume, specify 3330 as the device type.
is a three-digit decimal cylinder relocation factor that
specifies the cylinder on a real disk which corresponds to
cylinder 0 of the virtual disk. If T-DISK (temporary disk) is
specified, temporary disk space is obtained at logon time from
preallocated system disk space. This space must be initialized
or formatted by the user when he logs on and is a part of his
virtual configuration until he logs off or detaches the disk,
at time the data area is returned for reallocation for
another T-DISK area. To maintain security this area should be
physically erased before it is returned.
Part 2. Defining Your VK/370 System 207