Planning Considerations for CMS Resident disk space for application programs (CMS commands, user
programs, IBM Program products) --the amount of space needed is
program-dependent, and must be assigned by you. Work space for application programs (CMS commands, user programs, IBM Program Products) --the amount of space is program-dependent, and
must be assigned by you.
Device Support eMS supports the virtual machine devices shown in Figure 2. r , Virtual Virtual Symbolic , IBM Device Address
1
Name Device Type 3210,3215,1052 cuu
2 CON1 System console 2314,231Q,3330,3340,3350 190 DSKO System disk
(read-only) 2314,2319,3330,3340,3350 191
3 DSK1 Primary disk
(user files) 2314,2319,3330,3340,3350 cuu DSK2 Disk (user files) 2314,2319,3330,3340,3350 cuu DSK3 Disk (user files) 2314,231
Q
,3330,3340,3350
192 3 DSK4 Disk (user files) 2314,2319,3330,3340,3350 cuu DSK5 Disk (user files) 2314,2319,3330,3340,3350 cuu DSK6 Disk (user files) 2314,2319,3330,3340,3350 cuu DSK7 Disk (user files) 2314,2319,3330,3340,3350 19E3 DSK8 Disk (use r files) 2314,2319,3330,3340,3350 cuu DSK9 Disk (user files) 1403,3203,3211,1443 OOE PRN1 Line printer 2540,2501,3505 OOC RDR1 Card reader 2540,3525 OOD PCRl Card punch 2401,2402,2403,2415, 181- 4 TAP 1-TA P4 Tape dri ves 2420,3410,3411,3420 1The device addresses shown are those that are preassembled into the CMS resident device table. You can change the virtual machine , addresses by using the CP DEFINE command. 12The virtual address of the system console may be any valid I multiplexer address. 1
3
The
virtual device address (cuu) of a disk for user files can be any I valid System/370 device address, and can be specified by the CMS user , when he activates a disk. If the user does not activate a disk , immediately after loading CMS, CMS automatically activates the user's I primary disk (A-disk) at virtual address 191, the D-disk at 192, and , the Y-disk (a read-only extension of the system disk) at 19E.
L
Figure 2. Devices Supported by a CMS Virtual Machine Under CP, unit record devices and the system console are simulated
and mapped to different addresses and different devices. For instance, eMS expects a 3215, 3210, or 1052 type of operator's console, but many
terminals are 2741s or 3270s. Regardless of the real device type, the
virtual system console is a 3215. The control program (CP) of VM/370 handles all channel program modifications necessary for this simulation. eMS virtual disk addresses are mapped by CP to different real device
addresses. 20 IBM VM/370 Planning and System Generation Guide
Planning Considerations for CftS The CftS system disk, normally located at virtual address 190, is
read-only and contains the CftS nucleus functions and disk-resident CftS command modules. The CftS nucleus is loaded into virtual storage when you
issue the CP IPt command. CMS remains resident until another IPL command
is entered or until you log off. The disk-resident modules are loaded
into virtual storage only when their services are needed.
The A-disk is a read/write disk and is the primary or first disk.
Files that you wish to retain for later use are stored on one of your
disks. Information stored on a disk remains there until you erase it.
An exception is the temporary disk; files written on this disk are lost
when you log off. In addition to the system disk and primary
disk (A-disk), each eMS user can have up to eight additional disks. You can enter CftS direct output files,
back to the terminal.
commands and input files
program results, and error
from the terminal and
and prompting messages
The virtual card reader is used as the input medium for files, source
decks, and data to be processed by your programs. The virtual card
punch is used for your output files, language processor object decks,
and various other types of data. The virtual printer is used for
program results, storage dumps and language processor output. Under VM/370, the unit record equipment is normally spooled. CMS supports only spooled unit record devices.
The following is an example of a VM/370 directory entry for a CMS virtual machine. USER USER1 PASSWORD ACCOUNT NUMBER BIN7 IPL CMS CONSOLE 009 3215 SPOOL C 2540 READER A SPOOL D 2540 PUNCH A SPOOL E 1403 A
LINK ftAINT 190 190 RR MDISK 191 2314 71 10 UDISK1 W RPASS WPASS This entry describes the configuration when you log on as USER1. The
Directory program control statements are described in Part 2. Briefly,
this entry describes the USERl virtual machine: it has a console at 009, a class A -reader at OOC, a class A punch at OOD, a class A printer at OOE, a link to the CMS system disk (owned by userid MAINT) at 190, and a
minidisk at 191. Once you are logged on you can change the
configuration and also the spooling classes of the unit record devices. You can add devices to the VM/370 directory or dynamically add to the
configuration as needed. eMS Libraries efts updates simulated partitioned data sets which contain: CftS and OS macros to be used at assembly time (macro Object routines to be referred to at execution-load time (text
libraries)
Part 1. Planning for System Generation 21
Previous Page Next Page