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

Planning Considerations for CMS Additionally, you can invoke the CP commands available to all virtual
machines under VM/370 directly from CMS. Using these CP commands, you
can send messages to the operator or to other users, dynamically change
your virtual machine's configuration, and invoke spooling facilities.
In CMS, the facilities of CP and CMS together appear as those of a
single integrated system.
To use CMS, you must first gain access to a virtual machine via the CP LOGON command, and IPL CMS. Then you can enter commands or data from
the remote terminal (virtual operator's console). Each command, upon
completion, returns control to you. For information about how to use CMS and for a description of all CMS commands, see the ang and the VM/37Q. eMS Program language Facilities The languages available under CMS include: S/370 Assembler VS BASIC PL/T as FORTRAN IV OS/VS COBOL DOS PL/I Optimizer DOS/VS COBOL VS APL The assembler is distributed with VM/370. The language compilers
that are program products must be ordered separately. For a complete
list of language processors that can be executed under CMS, see
"Appendix A: Program Products, Installed User Programs, Field Developed
Programs and Emulators." CMS executes the
provided to invoke
of CMS. compilers via interface modules. CMS commands are
the compilers within the conversational environment OS/VS COBOL programs, using the following facilities, can be compiled
under CMS, but must be transferred to a machine (virtual or real)
running as for execution. QSAM & BDAM spanned records ISAM RERUN statement
label-handling options OPEN REV ERSED Sort feature
Segmentation feature ASCII code feature
Forced end of volume TCAM feature
as PL/I programs, using the following
under CMS, but must be transferred to a
running 05 for execution. Mul ti tas king
Teleprocessing file support ISAM Backwards attribute
facilities, can be compiled
machine (virtual or real) Part 1. Planning for System Generation 23