Then, you can use the PUNCH command to punch virtual card images:
punch acct records
The file ACCT RECORDS is spooled to the userid MICKEY's virtual card
reader. If the CMS file you are transferring does not have fixed­
length, 80-character (card image) records, you can use the command:
disk dump acct records
The CMS TAPE command allows you to dump CMS files onto tape, or to
restore previously dumped files:
tape dump archive file
tape load archive file VM/370 also provides a special utility program, DASD Dump Restore,
that allows you to dump the entire contents of your virtual disk onto a
tape and then later restore it to a disk. You might use this program,
invoked by the DDR command in CMS, to back up your data files before
using them to test a new program. COMMANDS TO PRINT AND PUNCH FILES
The commands that you use most often to print and punch CMS files are
the commands PRINT and PUNCH. For example:
print myprog listing
prints the contents of the LISTING file on the system printer, and:
punch myprog assemble
punches the assembler language source statement file onto cards. You can also punch members of MACLIBs and TXTLIBs: punch cmslib maclib (member fscb
Some CMS commands have a PRINT option, so that instead of having some
kinds of output displayed at your terminal or placed in a disk file, you
can request to have it printed on the real system printer. For example,
if you want a list of the contents of a macro library to print, you
could issue the command:
maclib map mylib (print You can see the contents of a file displayed at your terminal by
using the TYPE command:
type week3 report You can specify, on the TYPE command, that you want to see only some
specific records in this file:
type week3 report a 1 20 34 IBM VM/370 eMS User's Guide

March 30, 1979
Commands to Develop and Test OS and CMS Programs Use CMS to prepare programs: you can create them with the CMS editor
l or
write them cnto your CMS disks using any of the methods discussed above. You can also assemble or compile source programs directly from cards,
tapes, or OS data sets. If your source program is in a CMS disk file,
then during the development process you can use the editor to make corrections and updates.
To compile your programs, use the assembler or any of the language
processors available at your installation. If your program uses macros
that are contained in either system or private program libraries, you must make these libraries known to CMS by using the GLOBAL command:
global maclib cmslib asmlib
In this example, you are using two libraries: the CMS macro library, CMSLIB MACLIB, and a private library, named ASMLIB MACLIB. The output from the compilers, in relocatable object fora, is stored
on a CMS disk as a file with the filetype of TEXT. To load TEXT files
into virtual storage to execute them, use the LOAD command:
load myprog
The LOAD command performs the linkage editer function in C!S. If MYPROG contains references to external routines, and these routines are
the names of CMS TEXT files, those TEXT files are automatically included
in the load. If you receive a message telling you that there is an
undefined name (which might happen if you have a CSECT name or entry
point that is not the sa.e as the name of the TEXT file that contains
it), you can then use the INCLUDE command to load this TEXT file:
include scanrtn When you have loaded the object modules into storage, you can begin
program execution with the START command:
start
If you want to begin execution at a specified entry point, enter:
start scan1
where SCAN1 is the name of a control section, entry point, or procedure.
If you are testing a program that either reads or writes files or
data sets using OS macros, you must use the FILEDEF command to supply a
file definition to correspond to the ddname you specify in your program. The command:
filedef indd reader
indicates that the input file is to be read from your virtual card
reader. A disk file might be defined:
filedef outdd disk out file a1
The FILEDEF command in CMS performs the same function as a data
definition (DD) card in OS. The commands to load and execute OS programs are discussed in "Section 8. Developing OS programs Under CMS." Section 3. What You Can Do With VM/370-CMS Commands 35