Tuxedo 8.0 Supplement for H-Series RVUs

command to its standard output.
-o outfile
Specifies the name of the file the output load module is to have. If not supplied, the load module is named
SERVER.
-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. 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 buildserver first, before the
System/T library. 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. The CFLAGS and
ALTCFLAGS environment variables, described below, should be used to include any compiler options and
their arguments.
-l lastfiles
Specifies one or more user files to be included in the link edit phase of buildserver last, after the
System/T library. 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.
-r rmname
Specifies the resource manager associated with this server. (Use -r; -g is an historic synonym). The value
rmname must appear in the resource manager table located in TUXDIR/udataobj/RM. Each line in this
file is of the form:
rmname:rmstructure_name:library_names
Using the rmname value, the entry in $TUXDIR/udataobj/RM is used to include the associated libraries
for the resource manager automatically and to set up the interface between the transaction manager and
resource manager properly. If the -r option is not specified, the default is that the server can use the NonStop
SQL database available for the host platform. See ubbconfig.
-s {@filename|service[,service...][:func]|:func}]
Specifies the names of services that can be advertised when the server is booted. (See servopts). All
functions that can be associated with a service must be specified with this option. In the most common case, a
service is performed 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
builds 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:abc
builds the associated server with services x, y, and z, each to be processed by the function abc. Spaces are
not allowed between commas. Function name is preceded by a colon.
In another case, the service name may not be known until runtime. Any function that can have a service
associated with it must be specified to buildserver. To specify a function that can have a service name
mapped to it, put a colon in front of the function name. For example, the specification:
-s :pqr