buildclient-construct a BEA TUXEDO client module
buildclient[-C] [-v] [ {-rrmname| -w} ] [-oname]
[-ffirstfiles] [-llastfiles]
buildclient is used to construct a BEA TUXEDO client module. The command combines the files supplied by the -f and -l options with the standard BEA TUXEDO libraries to form a load module. The load module is built by buildclient using the default C language compilation command defined for the operating system in use. The default C language compilation command for the UNIX System is the cc(1) command described in UNIX System reference manuals.
-v
buildclient should work in verbose mode. In particular, it writes the compilation command to its standard output.
-w
-r option.
-r rmname
rmname must appear in the resource manager table located in $TUXDIR/udataobj/RM. Each line in this file is of the form:
rmname:rmstructure_name:library_names
(See buildtms(1) for further details.) Using the rmname value, the entry in $TUXDIR/udataobj/RM is used to include the associated libraries for the resource manager automatically and to set up the interface between the transaction manager and resource manager properly. The value TUXEDO/D includes the libraries for the TUXEDO System/D resource manager. The value TUXEDO/SQL includes the libraries for the TUXEDO System/SQL resource manager. Other values can be specified as they are added to the resource manager table. If the -r option is not specified, the default is that the client is not associated with a resource manager. Refer to the ubbconfig(5) reference page.
-o
a.out.
-f
buildclient first, before the BEA TUXEDO libraries. If more than one file is specified, file names must be separated by white space and the entire list must be enclosed in quotation marks. This option may be specified multiple times. The CFLAGS and ALTCFLAGS environment variables, described below, should be used to include any compiler options and their arguments.
-l
buildclient last, after the BEA TUXEDO libraries. If more than one file is specified, file names must be separated by white space and the entire list must be enclosed in quotation marks. This option may be specified multiple times.
-C
TUXDIR
buildclient uses the environment variable TUXDIR to find the System/T libraries and include files to use during compilation of the client process.
CC
buildclient normally uses the default C language compilation command to produce the client executable. The default C language compilation command is defined for each supported operating system platform and is defined as cc(1) for UNIX System. In order to allow for the specification of an alternate compiler, buildclient checks for the existence of an environment variable named CC. If CC does not exist in buildclient's environment, or if it is the string "", buildclient will use the default C language compiler. If CC does exist in the environment, its value is taken to be the name of the compiler to be executed.
CFLAGS
CFLAGS is taken to contain a set of arguments to be passed as part of the compiler command line. This is in addition to the command line option "-I${TUXDIR}/include" passed automatically by buildclient. If CFLAGS does not exist in buildclient's environment, or if it is the string "", no compiler command line arguments are added by buildclient.
ALTCC
-C option is specified for COBOL compilation, buildclient normally uses the BEA TUXEDO shell cobcc which in turn calls cob to produce the client executable. In order to allow for the specification of an alternate compiler, buildclient checks for the existence of an environment variable named ALTCC. If ALTCC does not exist in buildclient's environment, or if it is the string "", buildclient will use cobcc. If ALTCC does exist in the environment, its value is taken to be the name of the compiler command to be executed.
ALTCFLAGS
ALTCFLAGS is taken to contain a set of additional arguments to be passed as part of the COBOL compiler command line when the -C option is specified. This is in addition to the command line option
"-I${TUXDIR}/include"
passed automatically by buildclient. When the -C option is used, putting compiler options and their arguments in the buildclient -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.
COBOPT
COBOPT is taken to contain a set of additional arguments to be used by the COBOL compiler, when the -C option is specified.
COBCPY
COBCPY indicates which directories contain a set of COBOL copy files to be used by the COBOL compiler, when the -C option is specified.
LD_LIBRARY_PATH
LD_LIBRARY_PATH indicates which directories contain shared objects to be used by the COBOL compiler, in addition to the BEA TUXEDO system shared objects.
buildclient is supported as a BEA TUXEDO-supplied compilation tool on UNIX and MS-DOS operating systems. However, due to file naming restrictions, only the buildclt alias is supported on MS-DOS. Note that file names supplied as part of the buildclient command line must conform to the syntax and semantics of the resident operating system.
The MS-DOS version of buildclt has significant differences from the UNIX System version. These differences warrant a separate man page for the MS-DOS version of the command. Therefore, a separate buildclt(1) reference page is also included to describe the command for the MS-DOS environment.
CC=ncc CFLAGS="-I /APPDIR/include"; export CC CFLAGS
buildclient -o empclient -f emp.c -f "userlib1.a userlib2.a"
COBCPY=$TUXDIR/cobinclude
COBOPT="-C ANS85 -C ALIGN=8 -C NOIBMCOMP -C TRUNC=ANSI -C OSEXT=cbl"
COBDIR=/usr/lib/cobol LD_LIBRARY_PATH=$COBDIR/coblib:$TUXDIR/lib
export COBOPT COBCPY COBDIR LD_LIBRARY_PATH
buildclient -C -o empclient -f name.cbl -f "userlib1.a userlib2.a"
buildclt(1), buildserver(1), buildtms(1), compilation(5), cc(1), ld(1) in a UNIX System reference manual.