This topic includes the following sections:
Refer to Using the BEA Tuxedo Workstation Component for more information on the Workstation platform.
The following sections describe how to write and build client programs, and set appropriate environment variables when developing, in COBOL, a BEA Tuxedo application on a UNIX platform.
You can develop COBOL client programs for a UNIX platform in the same way that you develop COBOL clients in the BEA Tuxedo administrative domain. All ATMI calls are available.
To compile and link-edit Workstation client programs, use the buildclient(1) command. If you are building a UNIX Workstation client on the native node, use the -w
option to have the client built using the Workstation libraries.
If you are building a client on a native node, and both native and Workstation libraries are present, the native libraries are used by default. In this case, specifying the -w
option ensures that the correct libraries for a Workstation client are used.
On a workstation, where only the Workstation libraries are present, it is not necessary to specify -w
.
The following example shows how to use the buildclient
command on a native node.
ALTCC=cobcc ALTCFLAGS="-I /APPDIR/include"
COBCPY=$TUXDIR/cobinclude
COBOPT="-C ANS85 -C ALIGN=8 -C NOIBMCOMP -C TRUNC=ANSI -C OSEXT=cbl"
export COBOPT COBCPY ALTCC ALTCFLAGS
buildclient -C -w -o empclient -f name.cbl -f "userlib1.a userlib2.a"
The -o
option enables you to specify a name for your output file. Input files specified with the -f
option are linkedited before system libraries.
As illustrated, the TUXDIR
environment variable must be used to ensure that the buildclient
command can locate system libraries. Be sure that you have defined TUXDIR
. The CC
environment variable defaults to cc
, but can be set to another compiler through ALTCC
.
Workstation clients make use of several environment variables.
The following table lists the environment variables that are checked by TPINITIALIZE
when a Workstation client attempts to join an application.
Other environment variables may be needed by Workstation COBOL clients on a UNIX workstation, depending on which components of the BEA Tuxedo system are being used.
Note: | MicroFocus delivers LIBNSL.a as a shared object, which is required by buildclient when linking a Workstation client. Because MicroFocus COBOL does not support shared objects on UNIX 3.2, Workstation for UNIX 3.2 is not supported. |
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.
All program-specific ATMI calls are available.
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.
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.
The following example shows how to build an executable client for an ACCEPT/DISPLAY
application, such as CSIMPAPP
.
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