Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Reference   |   Topic List   |   Previous   |   Next   |   Contents

   BEA Tuxedo Command Reference

buildclt - construct a BEA Tuxedo Workstation client program for MS-DOS, Windows 3.x, and OS/2 16-bit.

buildclt [ -C ] [ -v ] [ -m {m | l} ] [ -c {m | b | i} ] 
[ -o name ] [ -f firstfiles ] [ -F Firstlibs ] [ -l libfiles ] 
[ -W ] [ -O ] [ -P ] [ -d deffile ]

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:

-v

specifies that buildclt should work in verbose mode. In particular, it writes the compilation command to its standard output.

-o name

specifies the filename of the output program. If not supplied, the program is named client.exe.

-f firstfiles

specifies one or more user files (or options to the compiler or linker) to be included on the command line first, before the BEA Tuxedo libraries. If more than one file is specified, filenames must be separated by white space and the entire list must be enclosed in double quotation marks. This option may be specified multiple times.

-F Firstlibs

specifies one or more standard or import (not dynamic-link) libraries to be included before the BEA Tuxedo libraries. If more than one file is specified, filenames must be separated by white space and the entire list must be enclosed in double quotation marks. This option may be specified multiple times.

-l libfiles

specifies one or more standard or import (not dynamic-link) libraries to be included after the BEA Tuxedo libraries. If more than one file is specified, filenames must be separated by white space and the entire list must be enclosed in double quotation marks. This option may be specified multiple times.

-d deffile

specifies a module definition file used for linking an MS Windows 3.x or OS/2 16-bit program.

-m {m | l}

specifies the memory model to be used for compilation and linking of a client. The values for this option are m and l for the medium and large memory models, respectively. The large memory model is the default value for this option. The medium memory model is no longer supported for DOS. The memory model needs only to be specified for Windows 3.x and OS/2 16-bit compilation.

-c {m | i}

specifies the compilation system to be used. The supported values for this option are m or i for the Microsoft C/C++ compiler, or the IBM CSET2 compiler, respectively. The Microsoft C compiler is the default value for this option. The IBM CSET2 compiler can be used only for OS/2 32-bit compilation.

-W

compiles and links an MS Windows 3.x client.

-O

compiles and links an OS/2 character-mode client.

-P

compiles and links an OS/2 Presentation Manager client.

-C

specifies COBOL compilation.

COBCPY

The environment variable COBCPY indicates which directories contain a set of COBOL copy files to be used by the COBOL compiler.

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.

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"

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.