3. If these characters are not included, and there is only one loader option, neither quotes nor parentheses are required.
For example:
PARM=MAP
To override the PARM parameter options specified in a cataloged procedure, you must refer to the PARM parameter by the qualified name PARM.procstepname. For example: PARM.GO
The loader options are of two types:
1. Simple pairs of keywords: a positive form (for example, CALL) that requests a facility, and an alternative negative form (for example, NOCALL) that rejects that facility.
CALL, LET, MAP, PRINT, and RES are of this type.
2. Keywords that permit you to assign a value to a function (for example, SIZE=lOK). EP and SIZE are of this type.
The loader options are described in the following sections, in alphabetic order.
The CALL option specifies that the loader will attempt to resolve external references by automatic library call. To preserve compatibility with the linkage editor, the negative form of this option can be specified as NCAL as well as by NOCALL.
The EP option specifies the entry point name of the program that is to be executed. The syntax of the EP option is:
EP=name
where "name" is an external name. If all input modules are load modules you must specify EP=PLISTART.
The LET option specifies that the loader will try to execute the problem program even if a severity 2 error has been found.
The MAP option specifies that the loader is to print a map of the load module giving the relative locations and lengths of control sections in the module. You must specify the data set defined by the DD statement with the name SYSLOUT to have this map printed. The module map is described in "Listing Produced by the Loader" on page 98.
The PRINT option specifies that the data set defined by the DD statement with the name SYSLOUT is to be used for messages, the module map, and other loader information.
RES OPTION
SIZE OPTION
The RES option specifies that the loade~ will attempt to ~esolve exte~nal ~efe~ences by a search of the link-pack area of main storage. This search will be made after the p~imary input to the loader has been processed but befo~e the data set defined by the DD statement with the name SYSLIB is opened.
The SIZE option specifies the amount of main storage, in bytes, to be allocated to the loader. The syntax of the SIZE option is:
SIZE=yyyyyy
SIZE=yyyK
specifies that yyyyyy bytes of main storage a~e to be allocated to the loader.
specifies that yyyK bytes of main storage are to be allocated to the loade~ (lK=1024).
The values can be enclosed, optionally, in pa~entheses.
LISTING PRODUCED BY THE LOADER
MODULE MAP
The loade~ can provide a listing on the SYSLOUT data set; the SYSPRINT data set is used by the problem program. The contents of each is given in Figure 38.
Data set Contents
SYSLOUT Loader explanatory messages and diagnostic messages, and optionally, a module map.
SYSPRINT PL/I execution-time messages, and problem program output.
Figure 38. Contents of SYSlOUT and SYSPRINT Data Sets
The SYSLOUT listing is described here; the SYSPRINT listing is described under "Listing (SYSPRINT)" on page 10.
The items in the SYSlOUT listing appear in the following sequence:
1. Statement identifying the loader.
2. Module map (if specified).
3. Explanatory, erro~, or warning messages.
4. Diagnostic messages.
If the MAP option is specified, a module map is printed in the SYSlOUT listing. The map lists all the control sections in the load module and all the entry point names (other than the fi~st)
in each cont~ol section. The information for each reference isz
• The cont~ol section or entry point name.
• An aste~isk, if the control section is included by library call.
98 OS PL/I Optimizing Compiler: Programmer's Guide
• An identifier, as followss
SD Section definition: the name of the control section.
LR Label reference: identifying an entry point in the control section other than the primary entry point.
CM Common areas an external file, or a non-string element variable declared STATIC EXTERNAL.
• Absolute address of the control section or entry point.
Each reference is printed left to right across the page and starts at a preset position. This gives the impression that the references are arranged in columns, but the correct way to read the map is line by line, across the page, not down each column.
The module map is followed by a similar listing of the pseudoregisters. The identifier used here is PR, and the address is the offset from the beginning of the pseudo register vector (PRV). The total length of the PRY is given at the end.
The total length of the module to be executed, and the absolute address of its primary entry point, are given after the
explanatory messages and before the diagnostic messages.
EXPLANATORY AND DIAGNOSTIC MESSAGES
The loader generates messages describing errors or conditions, detected during processing by the loader, that may lead to error. The format of these messages is given under "Diagnostic Message Directory" on page 77.
When the module to be executed has been processed, the loader prints out in full all the messages referred to above. The text of each message, an explanation, and any recommended programmer response, are given in OS/VS Message Library: linkage Editor and Loader Messages.