TS/MP 2.5 System Management Manual

CAUTION: Neither PATHCOM nor the PATHMON process checks for escape sequences in an
environment list. If escape sequences or other nonprintable characters are included in an environment
list, they are passed as input to PATHCOM, and unexpected results might occur. HP recommends
that all characters specified for the ENV attribute be ASCII printable. To specify escape sequences
in an environment list, HP recommends that you use the SPI management programming interface;
see the TS/MP 2.5 Management Programming Manual.
If a name or value includes blanks, quotes, commas, or semicolons, use the same rules as those for
presenting names and values in PATHCOM (the entire list must be enclosed in quotes.) However,
PATHCOM does not use blanks directly before or after the equal sign (=) if they are not enclosed
in quotes. For examples, see the description of the ARGLIST attribute.
In addition, environment variable names (name) cannot contain an equal sign (=). (The first equal
sign PATHCOM encounters is used as the delimiter for the environment variable name.) However,
an equal sign can be included in the value. For example, to specify an environment variable named
env1 having a value of abc=cba, enter the command as follows:
SET SERVER ENV env1=abc=cba
For a discussion of when to use parentheses, see the subsection “Command Format” (page 129).
This attribute is valid for OSS server processes only.
NOTE: Due to the extra characters required by PATHCOM to embed blanks, quotes, commas,
and semicolons, it is possible for the input buffer to be larger than the 24,000-character maximum.
In such cases, PATHCOM allows 500 additional bytes in the input buffer.
GUARDIAN-LIB file-name
specifies the name of the user library object file that contains additional server code space and
procedures that can be shared among servers. If you supply a value for this attribute, the operating
system uses this file name and the file named in the PROGRAM attribute to access the server code.
For example:
SET SERVER PROGRAM $DATA.WORK.SRVOBJ
SET SERVER GUARDIAN-LIB $DATA.WORK.SRVLIB
In this example, whoever starts the PATHMON process must have WRITE and EXECUTE access to
the server object file.
If you omit this attribute, the operating system accesses all of the server code, including the user
library object file, through the file that you define with the PROGRAM attribute.
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).
After starting a server process, the operating system modifies the server object file to point to the
user library object file.
You can set the server user library file using the TACL RUN command or using the Binder program
development tool. For more information, see the Binder Manual.
This attribute is valid for Guardian and OSS server processes.
HIGHPIN { ON | OFF }
specifies whether the server process runs at a high PIN or a low PIN:
The server process runs at a high PIN.ON
The server process runs at a low PIN.OFF
If you omit this attribute, the default is OFF
To run a server at a high PIN, you must also set the ?HIGHPIN compiler directive in your server
source code file. For more information about the ?HIGHPIN compiler directive, see the appropriate
programming language reference manual.
This attribute is valid for Guardian and OSS server processes.
HOMETERM file-name
specifies the name of the home terminal for servers in the server class.
If you omit this attribute, the default is the home terminal of the PATHMON process.
SET SERVER Command 191