SYNOPSIS

buildgateway [ -v ] [ -o name] [ -n maxdynam] [ -f firstfiles] [ -l lastfiles]
  [ -s services[:func]]

DESCRIPTION

buildgateway is used to construct a TUXEDO System/T gateway server. The command combines the files supplied by the -f and -l options with the standard server main routine (stdmain.o in $TUXDIR/lib/libtux.a), the standard TUXEDO System/T libraries, and the gateway template to form a gateway server. The gateway is built by the cc(1) command, which buildgateway invokes. (See cc(1) in UNIX reference manuals.) The options to buildgateway have the following meaning:

-v

specifies that buildgateway should work in verbose mode. In particular, it writes the executed commands to its standard output.

-o name

specifies the name of the file the output gateway is to have. If not supplied, the gateway is named GATEWAY.

-n maxdynam

specifies the maximum number of dynamic services the user may specify when the server is run. A dynamic service allows the user to specify at run time the function within the server that is to process the service, via either the command line options (see servopts(5)) or through tmadmin(1). If -n is not specified, the maximum number of such services is set to 25.

-f firstfiles

specifies one or more user files to be included in the link edit phase of buildgateway first, before the System/T libraries. If more than one file is specified, file names must be separated by white space and the entire list must be enclosed in quotation marks. This option may be specified multiple times.

-l lastfiles

specifies one or more user files to be included in the link edit phase of buildgateway last, after the System/T libraries. If more than one file is specified, file names must be separated by white space and the entire list must be enclosed in quotation marks. This option may be specified multiple times.

-s service,service[:func]

specifies the default set of service names that will be advertised when the gateway is booted. In some cases, a service is handled by a function that carries the same name; that is, the x service is performed by function x. For example, the specification -s x,y,z will build the associated server with services x, y, and z, each to be processed by a function of the same name. In other cases, a service (or several services) may be performed by a function of a different name. The specification, -s x,y,z:GATE_RPC builds the associated server with services x, y, and z, each to be processed by the gateway template's function GATE_RPC.

Spaces are not allowed between commas. Function name is preceded by a colon. The -s option may appear several times.

The cc command is normally used to produce the a.out. In order to allow for the specification of an alternate compiler, buildgateway checks for the existence of a shell variable named CC. If CC does not exist in buildgateway's environment, or if it is the string "", buildgateway will use cc as the compiler. If CC does exist in the environment, its value is taken to be the name of the compiler to be executed. Likewise, the shell variable CFLAGS is taken to contain a set of parameters to be passed to the compiler.

PORTABILITY

buildgateway is supported as a TUXEDO System/T-supplied compilation tool on UNIX Systems only.

EXAMPLES

The following example links in one object file and an LU 6.2 library, naming the output gateway "CICSGATEWAY". It assumes that users will map their services to the GATE_RPC function via the CLOPT option in the *UBBCONFIG or at run-time.

buildgateway -f gate.o -f cicsconv.o -f tm_cpic.o  
    -l lu62lib.a -o CICSGATEWAY 

buildgateway -f communic.a -o mygate -s MYSVC1,MYSVC2:GATE_RPC

SEE ALSO

servopts(5), and cc(1), ld(1) in UNIX System reference manuals