TS/MP 2.5 System Management Manual

Defaults for file name expansion are based on values you specify for the CMDVOL command and
the SET PATHWAY NODEINDEPENDENT attribute. See the command descriptions in “CMDVOL
Command” (page 138) and “SET PATHWAY Command” (page 159).
This attribute is valid for Guardian and OSS server processes.
IN file-name
specifies the name of the input file passed to the server process in the startup message; this can be
a DEFINE name.
System defaults for file name expansion are based on values you specify for the CMDVOL command
and the SET PATHWAY NODEINDEPENDENT attribute. See the command descriptions in “CMDVOL
Command” (page 138) and “SET PATHWAY Command” (page 159).
If you omit this attribute, spaces are passed to the servers for the file name.
This attribute is valid for Guardian server processes only.
LIKE server-class
sets the attribute values for the server class to those of the named server class. server-class must
be the name of a previously added server class.
This attribute is valid for Guardian and OSS server processes.
LINKDEPTH number
specifies the maximum number of concurrent links that any one link manager that is the ACS subsystem
processes, or a TCP, can have to a given server process before the PATHMON process directs that
link manager's link requests to another server within the server class.
The value of LINKDEPTH must not exceed the value of MAXLINKS and cannot exceed 255. In the
unlikely event that if MAXLINKS is set to 0, set the value of LINKDEPTH to 1. For information about
configuration limits, see “Configuration Limits and Defaults” (page 318).
If you omit this attribute, the default is 1.
Typically, you use the LINKDEPTH attribute to multithreaded servers; for servers that are not
multithreaded, use the default of 1 for LINKDEPTH.
This attribute is valid for Guardian and OSS server processes.
MAXLINKS number
specifies the maximum number of concurrent links permitted between all ACS subsystem processes
and TCPs and a server in a server class.
number must be a value from 0 through 4095. This attribute establishes the maximum number of
concurrent send operations to a single server process. The TCP or ACS subsystem processes do not
check how many links a server has with other TCPs or ACS subsystem processes.
If the value for this attribute is too large, it can cause the requests to the server process to be queued
at the server for an unacceptable length of time. For example, if MAXLINKS is equal to 20, there
can be 20 concurrent requests outstanding to a server. If the transaction service time is 1 second, a
response time of more than 20 seconds can occur.
If you omit this attribute, the default is an unlimited number of links. HP strongly recommends that
you set a value for MAXLINKS.
NOTE: The value of MAXLINKS and the value of the TABLE OCCURS clause in the RECEIVE–
CONTROL paragraph of your COBOL server programs must correspond with each other. The
MAXLINKS value must be equal to or less than the TABLE OCCURS value. When the COBOL
RECEIVE–CONTROL table is full, new requests to the server fail with file-system error 12 (File in use).
This error is most likely to occur during peak transaction load times. For more information about the
RECEIVE–CONTROL paragraph of a COBOL program, see the COBOL Reference Manual.
If this server is an associative server, then you must include links allocated by other PATHMON
environments when calculating the size of the RECEIVE-CONTROL paragraph.
The value of MAXLINKS must always be greater than or equal to the value of LINKDEPTH (unless
MAXLINKS is set to 0).
This attribute is valid for Guardian and OSS server processes.
MAXSERVERS number
specifies the maximum number of server processes in this server class that can run at the same time.
192 SERVER Commands