LOAD dictionary) statement if there is relocatable data in the text deck. If
additions made by REP statements increase the length of a control
section, an rcs statement, which defines the total length of the control
section, must be placed at the front of the deck.
r I Column I I I , I 2-4 I , 5-6 I I 7-12 I I I 13-14
15-16 17-70 71-72 73-80 ----------------------------,
Contents (12-2-9 punch).
Identifies this as a loader control statement.
REP --identifies the type of load statement.
Blank.
Hexadecimal starting address of the area to be replaced as
assigned by the assembler. It must be right-justified
in these columns with unused leading columns filled with
zeros.
Blank. , I , I I , I , I , , I I , , I ESID (External Symbol Identification) --the hexadecimal , number assigned to the control section in which replacementt
is to be made. The LISTING file produced by the compiler , or assembler indicates this number. A maximum of 11 four-digit hexadecimal fields, separated by
commas, each replacing one previously loaded halfword (two
bytes). The last field must not be followed by a comma.
Blank.
Not used by the loader. This field maj be
program identification may be inserted.
blank or
Figure 15. REP Statement Format An SPB statement instructs the loader
to update the location counter to point to the next page boundary. The SPB statement has the format shown in Figure 16.
r , Column contents I I 102 I -(12-2-9 punch). I Identifies this as a loader control statement. I I 2-4 SPB identifies the type of load statement. I I 5-80 May be used for comments or left blank. , L- ----------------- ______________ . __________________________________________ -J Figure 16. SPB Statement Format DMSLI07401 BEGINS ••• START was specified with LOAD and the loaded program starts
execution. Anv further responses are from the program.
Section 2. CMS Commands 127

LOAD INVALID CARD - xxx •.• xxx INV was specified with LOAD and an invalid statement was found.
The message and the contents of the invalid statement (xxx ••• xxx) are listed in the file LOAD MAP. The invalid statement is ignored
and loading continues. DMSLGT002I FILE 'fn NOT FOUND RC=O DMSLI0001E NO FILENAME SPECIFIED RC=24 DMSLI0003E INVALID OPTION 'option' RC=24 DMSLI0005E NO 'option' SPECIFIED RC=24 DMSLI0021E ENTRY POINT 'name' NOT FOUND RC=40 DMSLI0029E INVALID PARAMETER 'parameter' IN THE OPTIJN 'option' FIELD DMSLI0055E NO ENTRY POINT DEFINED RC=40 DMSLI0056E FILE 'fn ft' CONTAINS INVALID [NAMEIALIASIENTRYIESD] RECORD FORMA'TS RC=32 DMSLI0099E CMS/DOS ENVIRONMENT ACTIVE RC=40 DMSLI0104S ERROR Inn' READING FILE 'fn ft fm' FROM DISK RC=100 DMSLI0105S ERROP. Inn' WRITING FILE 'fn ft fm' ON DISK RC=100 DMSLI0109S VIRTUAL STORAGE CAPACITY EXCEEDED RC=104 DMSLI0116S LOADER TABLE OVERFLOW RC=104 DMSLI0168S PSEUDO REGISTER TABLE OVERFLOW RC=104 DMSLI0159S ESDID TABLE OV9RFLOW DMSLI0201W THE FOLLOWING NAMES ARE UNDEFINED: RC=4 DMSLI0202W DUPLICATE IDENTIFIER 'identifier' RC=4 DMSLI0203W "SET LOCATION COUNTER" NAME 'name' UNDEFINED RC=4 DMSLI0206W PSEUDO REGISTER ALIGNMENT ERROR RC=4 DMSLIOQ07T I/O ERROR ON FILE 'fn ft fm' RC=256 DMSSTT062E INVALID * IN FILEID RC=20 128 IBM VM/370 Command and Macro Reference