The following steps are required to link and load a module onto the target:

These steps are apportioned between two internal parts of the loader: symbols are relocated by the relocation unit (RU - the portion of the loader that performs relocations) and all other steps are performed by the object-module-format manager (OMF manager).

In addition loading modules to the target, the loader plays an additional role when the target server establishes a connection with a target agent. The loader attempts to obtain the pathname to the core file from the agent. The core file is the executable file on the host that corresponds to the runtime system initially executing on the target. This file is not downloaded to the target system because the core image is already present there (typically in PROM). If the core file is found, the loader reads this file in order to bootstrap the target server symbol table. If the checksums of the text regions do not agree, the loader prints an error message, because a symbol table built from this core file might not contain the correct addresses on the target.

If the core file is not known, the target server exits with an error message. Try connecting the target server again using the -c option to specify the core file path and name.