of GC20-1819-2 Rev March 30, 1979 by Supp. SD23-9024-1 for 5748-XX8 CALL
CANCEL CDLOAD CHECK CLOSE/ CLOSER CNTRL COMRG DEQ
DEQB
DTFxXl DUMP ENQ
ENQB EOJ ERET EXCP EXIT PC EXIT AB FCEPGOUT FETCH FREEVIS GENL
GET GETVIS GETIME JDUMP LOAD MVCOM NOTE OPEN/ OPENR PAGEIN PDUMP PFIX PFREE POINTR POINTS POINTW POST PRTOV PUT PUTR READ RELEASE RELPAG RELSE RETURN RUNMODE SECTVAL SEiZE SETIME SETPFA 06 65
33
41
9
42
2
14 00 17
95
86 01 02 62
61
34 04 05 87
67
68 40 64
85
66
75
22 10/24 71 Pass control to another program
Terminate processing
Load a VSAM phase Verify completion of a read or write operation
Deactivate a data file
Control a physical device
Return address of background partition communication region
no-op
Release a resource
Establish file definitions
Dump storage and registers and terminate processing
no-op Protect a resource
Terminate processing normally Provide an error routine
Execute a channel program
Return from program check routine
Return from abnormal termination routine
no-op
Load and pass control to a phase
Load and pass control to a logical transient
Release user free storage
Generate a phase directory list
Access a sequential file Obtain user free storage
Get the time of day
Dump storage and registers and terminate processing
Read a phase into storage
Modify bytes in the partition communication region Manage data set access
Activate a data file
no-op
Dump storage and registers and continue processing
no-op
no-op Position a file for reading
Reposition a file to its beginning Position a file for writing Post the event control block
Control printer overflow Write to a sequential file
Communicate with the system operator Access a sequential file
Release a system resource
no-op Skip to begin reading next blcck
Return control to calling program
Check if program is running real or virtual Obtain a sector number
no-op
no-op
no-op IThe declarative macros supported are:
DTFCN, DTFCD, DTFPR, DTFDI, DTFMT, DTFSD, DTFCP, and DTFSL Figure 16. DOS/VSE Macros Supported by eMS (Part 1 of 2) 170 IBM VM/370 CMS User's Guide

Pg. of GC20-1819-2 Rev March 30, 1979 by Supp. SD23-9024-1 for 5748-XX8 Maf!:.Q STXIT AB PC IT OC TRACK FREE
TRACK HOLD TRUNC TTIMER USE WAIT WRITE xxMODl SVC 37- 16 20 18
36
35
52
63 07 Function provIde-or terminate linkage to abnormal ending
routine
no-op
no-op
no-op
no-op Skip to begin writing next blcck
Return a 0 in Register 0 (effectively a noop)
Reserve a system resource Wait for the completion of IIC Write to a sequential file
Create Logical IOCS routine inline IThe DOS logic modules supported are: CDMOD, PRMOD, DIMOD, MTMOD, SDMODxx, and CPMOD Figure 16. DOS/VSE Macros Supported by CMS (Part 2 of 2) Assembling Source Programs
If you are a DOSjVSE assembler language programmer using CMS/DOS, you
should be aware that the assembler used is the VM/370 assembler; not the DOS/VSE assembler. The major difference is that the VM/370 assembler,
invoked by the ASSEMBLE command, is designed for interactive use, so
that when you assemble a program, error messages are displayed at your
terminal when compilation is comFleted, and you do not have to wait for
a printed listing to see the results. You can correct your source file
and reassemble it immediately. When your program assembles without
errors, you can print the listing.
To specify options to be used during the assembly, you enter them cn
the ASSEMBLE command line. So, for example, if you do not want the
output LISTING file placed on disk, you can direct it to the printer:
assemble myfile (print All of the ASSEMBLE command options are listed in When you invoke the ASSEMBLE command specifying a file with a
filetype of ASSEMBLE, CMS searches all of your accessed disks, using the
standard search order, until it locates the file. When the assembler
creates the output LISTING and TEXT files, it writes them onto 1isk according to the following priorities:
1. If the source file is on a read/write disk, the TEXT and LISTING files are written onto the same disk. 2. If the source file is on a read-only disk that is an extension of a
read/write disk, the TEXT and LISTING files are written onto the
parent disk.
3. If the source is on any other read-only disk, the TEXT and LISTING files are written onto the A-disk.
In all of the above cases, the filenames assigned to the TEXT and LISTING files are the same as the filename of the input file.
The output files used by the assembler are defined via FILEDEF
commands issued by CMS when it calls the assembler. If you issue a
Section 9. Developing DOS Programs Under CMS 171