Pg. of GC20-1819-2 Rev March 30, 1919 by Supp_ SD23-9024-1 for 5148-XX8 The RUN command, which is actually an EXEC procedure, combines many
of these commands for you, so that if you want to compile, load, and
execute a single source file, or load and execute a TEXT or MODULE file,
you can use the RUN command instead of issuing a series of commands. See the discussicn of the RUN command in for a list of the OS language processors available.
Commands to Develop and Test DOS Programs CMS simulates many functions of DOS/VSE in the CMS/DOS environment. eMS/DOS is not a separate system, but is part of CMS. When you enter the
command:
set dos on
you are in the CMS/DOS environment. If you want to use the libraries on
the DOS/VSE system residence volume, you should access the disk on which
it resides and specify the mode letter on the SET DOS ON command line:
access 132 c
set dos on c Using commands that are available only in the eMS/DOS environment,
you can assign system and programmer logical units with the ASSGN command:
assgn sys200 reader
If the device is a disk device, you can set up a data definition with
the DLBL command:
assgn sys100 b
dlbl infile b dsn .yinput file {sys100 You can find out the current logical unit assignments and active file
definitions with the LISTIO and QUERY DLBL commands, respectively:
listio a
query dlbl
If you are an assembler language programmer, you can assemble a
source file with the ASSEMBLE command:
assemble myprog
A eMS file with a filetype of DOSLIB simulates a DOS core image
library; you can link-edit TEXT files or relocatable modules from a DOS relocatable library and place the link-edited phase in a DOSLIB using
the DOSLKED ccmmand:
doslked myprog new lib
Then, use the GLOBAL command to identify the phase library and issue the
FETCH command to bring the phase into virtual storage:
global doslib newlib
fetch myprog
The START command begins program execution:
start
36 IBM VM/310 CMS User's Guide

During program development with CMS, you can use DOS/VS system or
private libraries. You can use files on these libraries or you can copy
them into eMS files. The DSERV command displays the directories of DOS/VS libraries. The command:
dserv cd
produces a copy of the directory for the core image library. To copy
phases from relocatable libraries into CMS TEXT files, you could use the RSERV command:
rserv oldprog
The SSERV and ESERV commands are available for you to copy files from
source statement libraries, or copy and de-edit macros from E
sublibraries. Also, the PSERV command copies procedures from the
procedure library.
The CMS/DOS commands are described
Developing DOS programs Under CMS." in detail in "section 9. Commands Used In Debugging Programs When you execute your programs under eMS, you can debug them as they
execute, by forcing execution to halt at specific instruction addresses. You do this by entering the debug environment before you issue the START command. You enter the debug environment with the DEBUG command:
debug
To specify that execution be stopped at a particular virtual address,
you can use the BREAK subcommand to set a breakpoint. For example:
break 1 20adO Then, when this virtual address is encountered during the execution of
the program, the debug environment is entered and you can examine
registers or specific storage locations, or print a dump of your virtual
storage. Subcommands that do these things might look like the
following:
gpr 0 15
x 20c12 8
dump 20000 *
Instead of using the CMS DEBUG subcommands, you can use the CP ADSTOP command to set address stops. For example:
cp adstop 20adO Then, in the CP environment, you can use CP commands to do the same
things. For example:
cp display g
cp display 20c12.8 cp dump 20000 Both sets of commands shown in these examples result in displays of (1)
the contents of your virtual machine's general purpose registers, (2) a
display of eight bytes of storage beginning at lccation X'20C12' and (3)
a dump of virtual storage from location X'20000' to the end. Section 3. What You Can Do With VM/370-CMS Commands 37