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
Planning Considerations for CMS The system macro libraries, located on the CMS system disk, are: 1ibIllY CMSLTB M ACLIB OSMACRO MACLTB OSMACROl MACLTB TSOMAC M ACLIB DOSMACRO MACLTB All of the CMS macros
The selected OS macros from SYS1.MACLIB that are
supported under CMS The remaining distributed SYS1. MACLIB OS macros
The OS macros distributed in SYS1.TSOMAC from
The DOS/VS macros and CMS macros that provide DOS/VS function
If you have previously created a CMS macro library and called it DOS MACRO MACLIB, you should rename it so that it does not conflict with
the DOS MACRO MACLIB supplied with the system.
If you plan to assemble DOS programs containing DOS macros in CMS/DOS, you must first create a CMS macro library that contains all the DOS macros you need. "Appendix G: A Sample EXEC Procedure for Copying DOS/VS Macros into a CMS MlCLIB" shows the procedure for copying an
entire macro library. The procedure for copying individual macros is
described in the The system text libraries, also located on the CMS system disk, are: LiQrary CMSLIB TXTLIB TSOLIB TXTLIB EREPLIB TXTLIB ERPTFLIB TXTLIB Content§ The CMS system text library Selected certain
products TSO routines
features of
necessary to
the language
Base text library for CPEREP Updates to CPEREP text library
support
program
Execution-time libraries are available with the program product
language processors and execute under eMS. You can generate your own libraries and add, delete, or list entries
in them via the MACLIB and TXTLIB commands. You can also specify which
libraries (system and user) to use for program compilation and execution
via the GLOBAL command. Up to eight libraries may be specified.
Although CMS library files are similar in function to OS partitioned
data sets, OS macros should not be used to update them. eMS Command language
The CMS command language lets you converse with CMS. With this command
language, you can use: Language compilers An assembler CMS file management system Context editing and line editing Execution control Debugging capability
22 IBM VM/370 Planning and System Generation Guide
Previous Page Next Page