LOAD contain a name to be used as the entry point for the loaded member. The LOT statement has the format shown in Figure 12. r , Column
2-4
5-16
17-24
25
26-33
34-80 L-- Contents !' 02' (12-2-9 punch).
Identifies this as a loader control statement. LOT - identifies type of statement.
Not used.
Blank or entry name (left-justified and padded with
blanks to eight characters) • Blank. Mav contain information specified on a SETSSI card
processed by the TXTLIB command.
Not used. ---'-' Figure 12. LOT statement Format The ICS statement changes the
length of a specified control section or defines a new control section.
It should be used onlv when REP statements cause a control section to be
increased in length. The format of an ICS statement is shown in Figure
13. An ICS statement must be placed at the front of the file or TEXT file. r- , Column , 2-4
5-16
17-22
23
24
25-28
30-72 , , 73-80 I 1---- -----, contents !' 02' (12-2-9 punch).
Identifies this as a loader control statement.
ICS --identifies the type of load statement.
Blank.
Control section name -- left-justified in these columns.
Blank.
(comma) • Hexadecimal length in bytes of the control section. This
must not be less than the actual length of the previously
specified control section. It must be right-justified in
columns with unused leading columns filled with zeros.
Blank. May be used for comments or left blank. , , , I I I , , , , , , , , , , , I I , , , , , Not used by the loader. You may leave these columns blank , or insert program identification for your own convenience. I ----I Only six characters can be coded for the CSECT names in , ,the ICS statement, but the loader program compares eight characters Ithe CSECT name from the TEXT file. tol I L -----.-1 Figure 13. ICS statement Format
section 2. CMS Commands 125

LOAD §gt The SLC statement sets the
location counter used with the loader. The file loaded after the SLC statement is placed in virtual storage beginning at the address set by
this SLC statement. The SLC statement has the format shown in Figure
14. It sets the location counter in one of three ways:
r I I I I , 1. With the absolute virtual address specified as a hexadecimal number
in columns 7-12.
2. With the symbolic address already defined as a
entry point. This is specified by a symbolic
columns 17-22.
program name or
name punched in
3. If both a hexadecimal address and a symbolic name are specified,
the absolute virtual address is converted to binary and added to
the address assigned to the symbolic name; the resulting sum is
the address to which the loader's location counter is set. For
example, if 0000F8 was specified in columns 7-12 of the SLC card
image and GAMMA was specified in columns 17-22, where GAKMA has an
assigned address of 006100 (hexadecimal), the absolute address in
columns 7-12 is added to the address assigned to GAKKA giving a
total of 0061F8. Thus, the location counter would be set to 0061F8. Column 2-4
5-6
7-12
13-16
17-22
23
24-72 73-RO contents 1C'02' (12-2-9 punch).
Identifies this as a loader control statement. SLC -- identifies the type of load statement.
Blank.
Hexadecimal address to be added to the value of the symbol,
if any, in columns 17-22. It must be right-justified in
these columns, with unused leading columns filled with
zeros.
Blank.
Symbolic name whose assigned location is used by the
loader. Must be left-justified in these columns. If
the address in the absolute field is used.
Blank. May be used for comments or left blank.
Not used by the loader. You may leave these columns
blank or insert program identification for your own
convenience.
blank, , , , I , , , , , L- ,------' Figure 14. SIC Statement Format A REP statement allows instructions and
constants to be changed and additions made. The REP statement must be
punched in hexadecimal code. The format of a REP statement is shown in
Figure 15. The data in columns 17-70 (excluding the commas) replaces
what has already been loaded into virtual storage, beginning at the
address specified in columns 7-12. REP statements are placed in the
file either (1) immediately preceding the last statement (END statement)
if the text deck does not contain relocatable data such as address
constants, or (2) immediately preceding the first RLO (relocatable
126 VM/370 CMS Command and Reference