LOAD

Loads the target program and associated symbol information into memory.

Read syntax diagramSkip visual syntax diagramLOAdMODuleSYMbolsFile Info
File Info
Read syntax diagramSkip visual syntax diagramcms-fnMAPftfmpds-memberdd-namephasename(MODUlemodule-name
MODULE
Keyword indicating module-only load.

Only the target module is loaded into storage.

This option may only be used in the PROFILE macro. For more details see Command restrictions related to PROFILE execution.

SYMBOLS
Keyword indicating symbols-only load. Does not apply to z/OS®.

Only the module symbols are loaded into storage. The following parameters provide more information.

cms-fn
CMS file name
MAP
Default CMS file type
ft
CMS file type
fm
CMS file mode
pds-member
z/OS PDS member name.
dd-name
z/OS DD name. If omitted, IDF looks in the ISPLLIB or STEPLIB if present. If the LIBE option was used, then that DD name is used as the default. IDF does not look in LPALIB or the z/OS link list.
phasename
The z/VSE® phase map, as generated by ASMLKEDT.
MODULE
Keyword to indicate that a module name is supplied. If not supplied, then symbols are loaded for the qualified module.
module-name
Module for which symbols are loaded.

If LOAD MODULE or LOAD SYMBOLS is issued by the PROFILE macro, but not both, IDF makes sure that both functions are performed after the profile completes.

For example, if the PROFILE issues LOAD SYMBOLS but does not issue LOAD MODULE, IDF loads the module anyway after the profile is completed.

You can stop IDF from loading the module with the MODULE command.

If no parameters are supplied with this command (the command is just LOAD) then both the target module and its associated symbols are loaded into storage. This may only be used in PROFILE macro. For more details see Command restrictions related to PROFILE execution.

Return codes

0
Target program loaded successfully
Other
An error occurred, see Message numbers and severity levels for return codes.

Notes for LOAD SYMBOLS for CMS

The underlying assumption for the IDF processing which loads symbols is that the symbol information is found as INVALID CARD images in the LOAD MAP file, interspersed with entrypoint addresses. You can use the LOAD SYMBOLS command to load symbol information from a TEXT file rather than a renamed LOAD MAP if you wish, but you have to perform some more setup for this case.

When loading symbol information directly from a TEXT file, you must first load all of the applicable TEXT files by means of the LOAD SYMBOLS command, then you must issue a SYMBOL command to define the offset-within-module for each CSECT.

An example profile to perform this kind of operation follows, but you probably want something more elaborate to prevent retyping the addresses within the profile each time you rebuild the program:
Figure 1. Loading symbols directly from TEXT files
/* load symbols directly from TEXT files */
'LOAD SYMBOLS ASMPARM TEXT'
'LOAD SYMBOLS ASMSCAF TEXT'
'SET SYMBOL (ASMPARM) ASMPARM  00000000 00000000 00000060 E F 01'
'SET SYMBOL (ASMSCAF) ASMSCAF  00000000 00000060 00000400 E F 01'
'SET SYMBOL (ASMSCAF) ASMSUBCM 0000028E 000002EE 00000000 E F 24'
The records in the LOAD MAP file which IDF uses to determine the start addresses of various CSECTs have the following format (in some cases you may want or need to build the map manually):
Col 1
Blank
Col 2-9
Symbol name (upper case)
Col 10
Blank
Col 11-12
If the symbol marks the start of a CSECT, these columns should contain the characters SD, otherwise they should be blank.
Col 13
Blank
Col 14-19
The hexadecimal address associated with this symbol.
Col 20-*
Blank