Open System Services Shell and Utilities Reference Manual (G06.27+, H06.04+)

eld(1) OSS Shell and Utilities Reference Manual
6. The following example:
eld -change highpin off exeobj
changes the value of the HIGHPIN attribute in the loadfile exeobj to OFF.
7. The following is an example of a valid private DLL registry file:
-- Specify the overall domain area that DLLs
-- can reside in (high to low)
-dllarea 0x68000000 0x60000000
-- Set up two DLLs that overlap each other
-- (one entry manually inserted)
-range $SYSTEM.ZDLL.ABC 0x67D00000 0x100000
-range /bin/usr/don/libmy.lib 0x67D00000 0x300000
FILES
/usr/bin/zimpimp
First default for the import library that represents the implicit DLLs
/usr/lib/zimpimp
Alternate default for the import library that represents the implicit DLLs
/usr/bin/zreg First default for the public DLL registry file
/usr/lib/zreg Alternate default for the public DLL registry file
NOTES
In the Guardian version of eld, MAP DEFINE names can be used to identify Guardian files wher-
ever the ELD command allows entry of a filename. The OSS version of eld does not support the
use of MAP DEFINEs. However, OSS filenames used with eld cannot begin with = because eld
uses the = character to identify MAP DEFINEs for expansion into Guardian filenames.
EXIT VALUES
The eld command returns one of the following values:
0 (zero) No errors or warning conditions were detected.
1 One or more error or warning conditions were detected.
RELATED INFORMATION
Commands: c89(1), enoft(1), ld(1), nld(1), noft(1).
Files: float(4).
STANDARDS CONFORMANCE
The eld command is an HP extension to the Single UNIX specification and performs functions
comparable to the UNIX ld command.
3−78 Hewlett-Packard Company 527188-004