![]() |
![]() |
|
|
Building Servers
To build an executable ATMI server, compile your application service subroutines with the BEA Tuxedo system server adaptor and all other referenced files using the buildserver(1) command with the -C option.
Note: The BEA Tuxedo server adaptor accepts messages, dispatches work, and manages transactions (if transactions are enabled).
Use the following syntax for the buildserver command:
buildserver -C -o filename -f filenames -l filenames -s -v
The following table describes the buildserver command-line options:
Note: The BEA Tuxedo libraries are linked in automatically. You do not need to specify the BEA Tuxedo library names on the command line.
The order in which you specify the library files to be link edited is significant: it depends on the order in which routines are called and which libraries contain references to those functions.
By default, the buildserver command invokes the UNIX cobcc command. You can specify an alternative compile command and set your own flags for the compile and link-edit phases, however, by setting the ALTCC and ALTCFLAGS environment variables, respectively. For more information, refer to Setting Environment Variables.
Note: On a Windows 2000 system, the ALTCC and ALTCFLAGS environment variables are not applicable and setting them will produce unexpected results. You must compile your application first using a COBOL compiler and then pass the resulting object file to the buildserver command.
The following command processes the acct.o application file and creates a server called ACCT that contains two services: NEW_ACCT, which calls the OPEN_ACCT routine, and CLOSE_ACCT, which calls a routine of the same name.
buildserver -C -o ACCT -f acct.o -s NEW_ACCT:OPEN_ACCT -s CLOSE_ACCT
See Also
![]() |
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|