Tuxedo 8.0 Supplement for H-Series RVUs

produce the server executable. In order to allow for the specification of an alternate compiler, buildserver
checks for the existence of an environment variable named ALTCC. If ALTCC does not exist in
buildserver's environment, or if it is the string " ", buildserver will use "ecobol". If ALTCC does
exist in the environment, its value is taken to be the name of the compiler command to be executed.
ALTCFLAGS
The environment variable ALTCFLAGS is taken to contain a set of additional arguments to be passed as part
of the COBOL85 compiler command line when the -C option is specified. This is in addition to the command
line option "-I $TUXDIR/include" passed automatically by buildserver. When the -C option is
used, putting compiler options and their arguments in the buildserver -f option will generate errors;
they must be put in ALTCFLAGS. If not set, then the value is set to the same value used for CFLAGS, as
specified above.
_RLD_LIB_PATH
The environment variable _RLD_LIB_PATH indicates what directories contain shared object (*.so files,
also known as DLLs) used by buildserver, in addition to the NonStop Tuxedo DLLs. By default, all
NonStop Tuxedo executables use the lib directory in the default install location, that is,
/tuxedo8.0/lib. If NonStop Tuxedo is not installed in the default location, /tuxedo8.0,
_RLD_LIB_PATH must be exported to buildserver and must contain the installed location of the
NonStop Tuxedo DLLs.
Portability
buildserver is supported as a compilation tool supplied by the NonStop Tuxedo system in the Open System
Services environment.
If you compile object files separately from buildserver, and use buildserver to link them into the client,
those object files should be compiled with the -WTandem_float option.
Examples
The following example shows how buildserver can be supplied CC and CFLAGS variables and how -f can be
used to supply a -lrld option to the c89 compiler to link to the runtime loader library:
CFLAGS= -g CC=/usr/bin/c89 \
buildserver -s DEPOSIT -s WITHDRAWAL -s INQUIRY \
-o TLR -f TLR.o -f util.o -f -lrld
The following example shows use of the buildserver command with no resource manager specified:
buildserver -s PRINTER -o PRINTER -f PRINTER.o
The following example shows how buildserver can be supplied with the CFLAGS variable and how -W can be
used to invoke the SQL compiler and have the program registered in the specified catalog:
export CFLAGS="$(CFLAGS) -Wsql=/"catalog =bankapp/""
buildserver -s OPEN_ACCT -s CLOSE_ACCT -o ACCT \
-f ACCT.o -f appinit.o -f util.o
The following example shows how to compile a COBOL program with debugging symbols so INSPECT can be
used:
export ALTCFLAGS=-g
buildserver -C -o SIMPLE -f SIMPLE.cbl
The following example shows how to suppress some compiler warnings and how to control and observe the linker's
options for using DLLs:
CFLAGS="-DNOWHAT $APPDIR/include \
-Weld='-rld_first_L /tux_first/lib:/tux_second/lib -rld_L /tux_middle/lib