Although the CMS in VM/370 is built upon CMS Version 3.1 in CP-67/CMS, there are five types of modifications that were made to 3.1 that affect
the relationship between versions:
1. Some commands and system functions remain unchanged;
therefore, complete compatibility exists.
2. iYD£!ionA! Capability: Functional
enhancements are effected; but, in some cases,
functions are supported.
and
old
syntactical
keywords and
3. Commands have name changes, but a SYNONYM file may be included during nucleus system generation.
4. Some keywords within a command are modified,
deleted or added.
5. MajQr Improvements to commands and system functions
caused complete incompatibilities in the following areas: • Because the CMS nucleus
must be recreated from GENMOD command.
is significantly larger, all MODULES their object (TEXT) files using the • Because you may now have up to 10 disks, the logical directory
identifications (filemode letters) are changed to reflect a more
natural, easy-to-remember, search order: P, T, A, B, S, C
becomes A, B, C, D, E, F, G, S, Y, Z --with the system disk
being the S-disk, and the primary disk becoming the A-disk. • The following global changes of filetypes must be made: SYSIN to ASSEMBLE ASP360 to MACRO • For language processors, the DECK and NODECK options have a new
meaning, they route the object (TEXT) file to the spooled card
punch; the LOAD and NOLOAD options now invoke the function
formerly performed by DECK and NODECK, and the writing of the TEXT file onto a CMS disk. • No 2311 disk support is provided for CP or CMS files. • In Version 1.0 the tape designations are as follows: TAP1 is for 181 TAP2 is for 182
The default for tape commands is TAP1. 420 IBM VM/310 Planning and System Generation Guide

• CMS does not function on a real CPU without the control program. • TXTlIB files must be recreated. • Because many fields are changed in the CMS nucleus or
rearranged, many of your programs that refer to these fields
have to be reassembled with the new CMS macro libraries. • Modules that refer to fields containing sizes, limits, and
quantities within the CMS nucleus may have to be reassembled and
then regenerated. • SYSlIB MACLIB is renamed to CMSLIB MACLIB. • All EXEC files should be checked for command name
changes, filemode usage, and so on, and changed to VM/370 CMS. Major changes are: &TYPEOUT to &CONTROL &PRINT to &TYPE &INDEXO to &RETCODE and operand
conform to • The options specified for a LOAD command do not remain in effect
for subsequent INCLUDE commands; options are reset to default
settings unless the SAME option is specified. • Filenames and filetypes must be composed entirely of alphameric
characters. • If the CMS Version 1.0 system does not recognize
the command line is automatically passed to CP. and QUERY commands do not recognize an operand
command line is passed to CP. This is not true
the CP command must be explicitly stated. The
negated by entering the command:
SET IMPCP OFF a command name,
If the CMS SET
or option, th e
for EXEC files;
feature may be VM/370 CMS Support of CP-67/CMS Commands
Command name changed to RENAME.
Components of the new file identifier may not be specified
as asterisk An equal sign (=) performs the same
function. NOUP option keyword changed to NOUPDIRT; NOUP is the
abbreviation.
Default options added: NOTYPE, UPDIRT. Only one file may be assembled per ASSEMBLE command. NODECK is the default ]IAgINODIAG changed to LTAPn not supported
LDISK option name changed to DISK 1QADINOLOAD, !LG!INOALGN LINECT nn122, Appendix E: Compatibility of VM/370 with CP-61/CMS 421