Microsoft Windows Bindings


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Programming BEA Tuxedo ATMI Applications Using COBOL \| Local Topics \| Previous Topic \| Next Topic \| Contents

The following sections describe how to write and build client programs, build ACCEPT/DISPLAY clients, block network behavior, and restore the network environment when developing, in COBOL, a BEA Tuxedo application for the Microsoft Windows platform.

Writing Client Programs

All program-specific ATMI calls are available.

Building Client Programs

To compile the COBOL source files that call the ATMI, you must use the COBOL compiler with the LITLINK option. To linkedit the Workstation client object files, use the buildclient(1) command. While the syntax of the command is straightforward, the usage varies according to the compilation system used.

The following example shows how to use the buildclient command.

Example of Running buildclient on a Windows Platform

COBCPY=C:\TUXEDO\COBINC
COBDIR=C:\COBOL\LBR;C:\COBOL\EXEDLL
PATH=C:\COBOL\EXEDLL;...
TUXDIR=C:\tuxedo
LIB=C:\NET\TOOLKIT\LIB;C:\MSVC\LIB;C:\TUXEDO\LIB;C:\COBOL\LIB
buildclient -C -o EMP.EXE -f EMP -f "/NOD/NOI/NOE/CO/SE:300" -l WLIBSOCK

For Windows NT:

buildclient -C -o EMP.EXE  -f empobj

The following table describes the buildclient command options used in the preceding example.

buildclient Command Options for Windows Platform

Option

Description

-o name

Name of the executable file being created. The default is client.exe.

-f firstfiles

One or more object files to be included before the BEA Tuxedo libraries. You can use the -f option to pass options to the compiler or linker. To specify more than one filename, enter a list of files after -f, using white space to separate filenames and double quotation marks around the list. You can also specify multiple filenames using multiple occurrences of the -f option on the command line.

-l libfiles

Libraries to be included after the BEA Tuxedo libraries. To specify more than one filename, you must separate the names by white space and enclose the list in quotation marks. You can also specify multiple filenames using multiple occurrences of the -l option on the command line.

Option	Description
-o name	Name of the executable file being created. The default is client.exe.
-f firstfiles	One or more object files to be included before the BEA Tuxedo libraries. You can use the -f option to pass options to the compiler or linker. To specify more than one filename, enter a list of files after -f, using white space to separate filenames and double quotation marks around the list. You can also specify multiple filenames using multiple occurrences of the -f option on the command line.
-l libfiles	Libraries to be included after the BEA Tuxedo libraries. To specify more than one filename, you must separate the names by white space and enclose the list in quotation marks. You can also specify multiple filenames using multiple occurrences of the -l option on the command line.

Building ACCEPT/DISPLAY Clients

The following example shows how to build an executable client for an ACCEPT/DISPLAY application, such as CSIMPAPP.

Building ACCEPT/DISPLAY clients

a) compile the COBOL module and create a file.obj
         cobol file.cbl omf(obj) litlink;
b) use the following link statement
         link FILE+cblwinaf,,,\
         wcobatmi+cobws+wtuxws+ \
         lcobol+lcoboldw+cobw+cobfp87w+  \
         wlibsock,FILE.def  /nod/noe;
   For Windows NT the link statement is:
         cbllink -oEMP.exe EMP.obj  \
         cobws.lib ncobatmi.lib wtuxws32.lib  \
         libcmt.lib user32.lib