|
|
buildclt(1)
Name
buildclt - construct a BEA Tuxedo Workstation client program for MS-DOS, Windows 3.x, and OS/2 16-bit.
Synopsis
buildclt [ -C ] [ -v ] [ -m {m | l} ] [ -c {m | b | i} ]
[ -o name ] [ -f firstfiles ] [ -F Firstlibs ] [ -l libfiles ]
[ -W ] [ -O ] [ -P ] [ -d deffile ]
Description
buildclt is used to construct a BEA Tuxedo workstation client program for MS-DOS, Windows 3.x, and OS/2 16-bit. The command combines the files supplied by the -f and -l options with the standard BEA Tuxedo libraries to form an executable program. The load module is built by buildclt using the C and COBOL language compilation commands defined for the operating system in use. The options to buildclt have the following meaning:
The following environment variables must be set for the COBOL environment.
Microsoft C Compilation
The buildclt command assumes that directories for needed libraries are specified in the environment variables INCLUDE and LIB. They might look like the following:
INCLUDE=C:\TUXEDO\INCLUDE;C:\NET\TOOLKIT\INCLUDE;C:MSVC\INCLUDE
LIB=C:\NET\TOOLKIT\LIB;C:\WINDEV\LIB;C:\MSVC\LIB;C:\TUXEDO\LIB;
Note that in the above example, C:MSVC is the directory where MS Visual C++ resides; earlier versions such as C600 or C700 can be used. Note that in the above example, C:NET is the directory where Novell Lan Workplace resides; earlier versions resided in C:XLN and can be used.
Note that COBOL source files that reference ATMI calls must be compiled with the LITLINK option.
The names of all libraries used for linking the client followed by the files specified in the -l option are put into a temporary response file and linking is done using the command line:
LINK firstfiles, outname @tmpfile
are the filenames specified with the -f option, outname is the output filename (default client.exe), and tmpfile is the temporary response filename. The -f option should be used to include any necessary options to be passed to LINK (for example, /ST:10000 to set the default stack size to 10000 bytes). The -l option should be used to include any necessary network provider libraries (for example, mlibsock.lib). To create an executable that can be debugged using Codeview (assuming that the object files have been compiled with the -Zi option), use -f /CO.
Examples
MS-DOS C Compilation:
buildclt -cm -ml -o emp.exe -f "/CO/ST:10000/SE:200" -f emp.obj -l llibsock.lib
WINDOWS C Compilation:
buildclt -W -cm -mm -o emp.exe -f "/CO emp.obj" -d emp.def rc -k emp.res emp.exe
OS2 16-bit:
buildclt -O -cm -ml -o emp.exe -f "/NOI/ST:15000/CO emp.obj" -d emp.def
DOS/WINDOWS/OS2 COBOL Compilation:
COBCPY=C:\TUXEDO\COBINC
COBDIR=C:\COBOL\LBR;C:\COBOL\EXEDLL
PATH=C:\C700BIN\;C:COBOLEXEDLL;...
TUXDIR=C:\TUXEDO
INCLUDE=C:\TUXEDO\INCLUDE;C:\XLN\TOOLKIT\INCLUDE;C:\C700\INCLUDE
LIB=C:\XLN\TOOLKIT\LIB;C:\C700\LIB;C:\TUXEDO\LIB;C:\COBOL\LIB
COBOL EMP.CBL OMF"OBJ" LITLINK
DOS:
BUILDCLT -C -o EMP.EXE -f EMP+MFC7INTF+C7DOSIF+C7DOSLB \
-f "/NOD/NOE/SE:300/CO/ST:10000" -l LLIBSOCK
WINDOWS:
BUILDCLT -C -W -o EMP.EXE -f EMP -d EMP.DEF -f "/NOD/NOE/CO/SE:300"
OS2:
BUILDCLT -C -P -o EMP.EXE -f EMP+MFC6INTF+C6OS2IF+C6OS2LB -d
EMP.DEF \ -f "/NOD/NOE/SE:300/CO"
See Also
Microsoft C/C++ Programming Techniques, Microsoft Corporation
Micro Focus COBOL/2 Operating Guide, Micro Focus Ltd.
Micro Focus COBOL/2 Workbench for DOS and OS2, Micro Focus Ltd.
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|