"Imported modules" page

The "Module" pages appear in the properties notebooks of all executable files to display additional information about an executable module.

This page shows you the submodules imported by the module.

The page only lists the submodule names which are explicitly listed as imports in the module header for load-time linking. These imports are resolved already at the time the module gets loaded, as opposed to run-time linking (see below). The module names are the names of the dynamic link libraries to be imported, usually without the .DLL file name extension, and are expected to be on the LIBPATH (see "System paths" for more information).

If an executable fails to load, the information on this page can be useful to find out what submodule might have failed.

However, as a result of the above, this page does not show:

Run-time imports, when an application calls specific &os2; APIs to import code dynamically after it has been completely loaded. This information is not specified in the executable headers because it is the actual program code that performs the import. See the documentation for DosQueryProcAddr in the Toolkit documentation.*
Indirect imports, that is, sub-imports performed by the modules listed on this page. Those imports depend on the execution context: for example, the currently active LIBPATH, BEGINLIBPATH, and ENDLIBPATH system paths all determine which modules would be actually loaded.

To find out which module is really used by a given program file, you can use the PSTAT /L command from an &os2; command prompt while that specific program is running.