The location from which we load a module is influenced by several things: loadlists, DCUF commands, signon options, profiles, etc. This document outlines how these are prioritized in loading a module.
Loadlists are the overriding factor in determining where modules will be loaded from at run-time, including subschemas, access modules, dialogs, maps, programs, etc. One of the potential entries in a loadlist is a user default dictionary, indicated by the parm USER-DEF in the loadlist entry. If that is included in the loadlist, then the dictionary specified by a DICTNAME parameter will be considered as part of the loadlist evaluation. Loadlists & DCUF commands may also be used to control which version number of a module to load. The location that is used to load a particular load module will not depend on the particular program or tool being executed; it will depend on the environment in which it is run, and various specifications, as follows:
LOADLIST SYSLOAD Type Version Dictnode/Dictname Dict USER-DEF USER-DEF Dict USER-DEF SYST-DEF Loadlib USER-DEF Dict 00001 USER-DEF Dict 00001 SYST-DEF Loadlib 00001
Here is an example of how the above rules apply when using SYSLOAD.
Release: IDADSO00100-18.5-ADS-for CA-IDMS