March 30, 1979
19 maclib add dosmac eoj R" , maclib MACRO OPEN CLOSE GET PUT DIMOD DTFDI EOJ R;
map dosmac (term INDEX SIZE 2 43
46 43 90 56
147 93
241 647
889 284
1174 6 20 erase eoj *
R;
assemble dostest
*
*
*
21 ASSEMBLER DONE 22 NO STATEMENTS FLAGGED IN THIS ASSEMBLY R" , list file DOSTEST DOSTEST DOSTEST R;
dostest * ASSEMBLE A1 LISTING A1 TEXT A1
print dostest listing
R;
23 doslked dostest
24
R;
listfile DOSTEST DOSTEST DOSTEST DOSTEST DOSTEST R;
dostest * ASSEMBLE A1 DOSLIB A1 TEXT A1 LISTING A1 MAP AS
19 Use the ADD function of the MACLIB command to add the macro EOJ to DOSMIC MACLIE. Then, issue the MACLIB command again, using the MAP function and the TERM option to
display a list of the macros in the library. 20 Erase the EOJ files. You should always remember to erase files that you do not need
any longer. Reassemble the program.
21 This time, the assembler completes without encountering any errors. If your ASSEMBLE file still has errors, you should use the editor to correct them. 22 Use the LISTFILE command to check for DOSTEST files. The assembler created the files, DOSTEST LISTING and DOSTEST TEXT. The TEXT file contains the object module. You can print the program listing, if you want a printed copy. Then, you may want to
erase it.
23 Use the DOSLKED command to link-edit the TEXT file into an executable phase and
write it into a DOSLIB. Since this program has no external references, you do not
need to add any linkage editor control statements.
24 Now, you have a DOSTEST DOSLIB, containing the link-edited phase, and a MAP file,
containing the linkage editor map. You can display the linkage editor map with the TYPE command, or use the PRINT command if you want a printed copy.
372 IBM VM/370 CMS User's Guide

25
26
27 Pg. of GC20-1819-2 Rev Karch 30, 1979 by Supp. SD23-9024-1 for 5748-XX8 icp spool punch to *
punch test data a PUN FILE 0100 TO BILBO R; tcp query reader all COpy 01 NOHOLD ORIGINID FILE CLASS RECDS CPY HOLD DATE TIME NAME PATTI 5840 A PUN 000097 01 NONE 09/29 15:00:39 TEST
assgn sysipt reader
R;
assgn syspch a
R;
dlbl outfile a ems punch output (syspch
R;
state punch output a DMSSTT002E FILE NOT FOUND. R (00028) ; TYFE DATA
DIST
BIN211
28 global doslib dostest
R;
fetch dostest DMSFET710I PHASE 'DOSTEST' ENTRY POINT AT LOCATION 020000. R;
29 start
25 DMSLI0740I EXECUTION BEGINS ••• R;
listfile punch output a (label
FILENAME FILETYPE FM FORMAT LRECL RECS fLOCKS TIME PUNCH OUTPUT A 1 F 80 97 1n I V
DATE
9/29/75 14:50:55 LABEL
BBB191
R;
#cp query reader all NO RDR FILES To execute this program in
records into your virtual
fixed-length, SO-character CMS editor, or by copying
follows: CMS/DOS, punch
card punch. records, you
your ASSEMBLE a file that has fixed-length 80-character
If you do not have any files that have
can create a file named TEST DATA with the
source file with the CCPYFILE command, as
copy file dostest assemble a test data a Use the CP SPOOL command to spool the punch to your own virtual machine, then use
the PUNCH command to punch the file. The FUN FILE message indicates that the file
is in your card reader. Use the CP QUERY command to check that it is the first, or
only file in your reader.
26 Use the ASSGN command to assign SYSIPT to your card reader and SYSPCH to your
A-disk.
27 When you assign a logical unit to a disk mode, you must issue the DLBL command to
identify the disk file to CMS. For this program execution, you are creating a CMS file named PUNCH OUTPUT. The STATE command ensures that the file does not already
exist. If it does exist, rename it, or else use another filename or filetype on the
DLBL t:ommand. 28 Use the GLOBAL command to identify the tOSLIB, DOSTEST, you want to search for
executable phases, then issue the FETCH command specifying the phase name. The
FETCH command loads the executable phase into storage. When the FETCH command is
executed without the START option, a message is displayed indicating the entry point
location of the program loaded.
29 The START command begins program execution. The CMS ready message indicates that
your program completed successfully. You can check the input and output activity by
using the LISTFILE command to list the file PUNCH OUTPUT. If you use the CP QUERY command, you can see that the file is no longer in your virtual card reader.
Sample Terminal Session for DOS Programmers 373