TS/MP System Management Manual (G06.24+, H06.03+)

Configuring Objects in a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
3-22
Additional Considerations
•
A variable called DEBUGLOGFORMAT is defined. Its value is TRUE. (ENV
attribute.)
A variable called HANGAROUND is defined. Its values is TRUE. (ENV attribute.)
•
The total number of all server processes in the server class that the PATHMON
process can run simultaneously is four. (MAXSERVERS attribute.)
•
The total number of static server processes allowed is three. (NUMSTATIC
attribute.)
•
The object code for the server class is stored in the OSS file
/centrl/inven/orders/app/bin/ordsrv1. (PROGRAM attribute.)
•
Errors are sent to a file with the absolute pathname
/centrl/inven/orders/process/error. (STDERR attribute.)
•
Input is received from a file with the absolute pathname
/centrl/inven/orders/process/orders/new. (STDIN attribute.)
•
Output is sent to a file with the absolute pathname
/centrl/inven/orders/process/orders/out. (STDOUT attribute.)
Additional Considerations
Following are some configuration considerations that can affect system performance.
Configuring OSS Servers for Effective Space Allocation
When you start the PATHMON environment, the PATHMON process allocates enough
memory and disk space to support most configurations. If your environment uses all
allocated memory and disk space, the PATHMON process attempts to get more.
You will not experience any increase in your memory and disk space requirements if
you configure an environment supporting only Guardian servers; an environment
supporting Guardian servers and a few large OSS servers; or an environment
supporting Guardian servers and many small OSS servers. On the other hand, if you
configure a large number of OSS servers with close to maximum-length attributes, you
will see memory and the PATHCTL file increase accordingly.
In rare instances, the PATHMON process may use up its allocated space and request
more space from the Guardian environment; or all pre-allocated extents for the
PATHCTL file may become full. If the PATHMON process uses all its allocated space,
it cannot perform any system functions while it attempts to allocate more space. When
the PATHMON process completes its attempt, a message is logged explaining that the
PATHMON process was trying to resize its segment.
If all preallocated extents for the PATHCTL file become full, the PATHMON process
attempts to allocate another extent. If additional space is not available and a
command is issued, the command fails and you get an allocation error.