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

ecobol(1) OSS Shell and Utilities Reference Manual
is used and annotated source files that contain embedded module definitions are
produced instead of MDF files, while restrictions associated with release 1.8 or
earlier are ignored.
TMPDIR Determines the pathname that overrides the default directory for temporary files
created by ecobol and components it invokes. By default, temporary files are
stored in the /tmp directory. If TMPDIR is set to a directory that does not exist
or is not writable, ecobol uses the default directory as described on the temp-
nam(3) reference page.
Processes
With the exception of the ECOBFE and SQLCOMP processes, which is invoked as a Guardian
process, all components are invoked as OSS processes.
Standard Libraries
The following libraries are available for COBOL85 programs that call OSS functions.
-l c Contains all library functions specified in the POSIX.1 specification, except for
those functions listed as residing in the math.h header file. You can omit this
operand because the ecobol compiler automatically passes it.
-l C Contains the C++ version 2 run-time library. This library is included before the
standard C run-time library.
-l l Contains all functions required by the C language output of the lex utility that are
not made available through the -l c operand.
-l m Contains all functions referenced in the math.h header file.
-l y Contains all functions required by the C language output of the yacc utility that
are not made available through the -l c operand.
In the absence of flags that inhibit invocation of a linker utility, such as -c or -Wnolink, ecobol
passes an -l c operand to the linker utility as the last -l operand, causing the standard C library to
be searched after all other object files and libraries are loaded.
If you want the libraries to be searched in a specific order or you want linking options to be pro-
cessed in a specific order, you should invoke the linker using the eld command from the OSS shell
and not use ecobol to do the linking.
Differences Between Static and Dynamic Linking
The -WBdllsonly and -WBdynamic operands specify dynamic linking. The -WBstatic operand
specifies static linking.
In dynamic linking, the eld utility first searches for a dynamic-link library (DLL). If a DLL cannot
be found, the linker utility searches for an archive file. If no archive file can be found, an error is
issued.
In static linking, the linker utility searches for an archive file but does not search for a DLL. If the
archive file cannot be found, an error is issued.
Dynamic and static linking are not exact opposites. Dynamic linking accepts either a DDL or an
archive file, but static linking accepts only an archive file.
Unlike ecobol flags, multiple -WBdllsonly, -WBdynamic, and -WBstatic operands can be
specified in a single ecobol invocation; thus, it is possible to perform dynamic linking for some -l
operands and static linking for others.
-WBdllsonly, -WBdynamic and -WBstatic operands specified to ecobol are temporarily overrid-
den by linking arguments specified in the -Weld or-Weld_obey flags.
3−38 Hewlett-Packard Company 527188-004