TS/MP 2.5 System Management Manual

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 might use up its allocated space and request more space
from the Guardian environment; or all pre-allocated extents for the PATHCTL file might become
full. If the PATHMON process uses all the allocated space, it cannot perform any system functions
while it attempts to allocate more space. When the PATHMON process completes the attempt, a
message is logged explaining that the PATHMON process was trying to resize the 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.
Configuring for the Use of High PINs
If you have configured your system to the use of high PINs, you can define additional server classes
without exhausting PINs that you might need for other processes. Additionally, you have more
freedom to define server classes as static, thus reducing the overhead associated with process
startup.
Configuring Server Processes in Multiple CPUs
Running server processes in different CPUs often increases application throughput, because
concurrent copies of the server code can run in parallel.
In assigning CPUs for your server processes, try to balance these processes evenly across the CPUs
to avoid overloading any particular processor. Using HP performance tools can simplify this process.
For a discussion of these tools, see “Other System Management Tools” (page 32).
Setting Process Priority
You can specify the priority at which the PATHMON process, server classes, and TCPs run. To
specify the priority at which the PATHMON process runs, include the PRI run option in your
TACL command to start the PATHMON process. In general, the PATHMON process must run at
a higher priority than the rest of the PATHMON environment. To specify the priority at which a
server class or TCP runs, include the PRI option with the SET TCP or SET SERVER command,
respectively.
NOTE: Your environment includes TCPs only if you have the Pathway/iTS product.
For server classes and TCPs, priorities must facilitate the completion of work over the arrival of
work. Usually, this means that server classes must have a higher priority than TCP objects.
Configuring Links for Optimum Performance
Arriving at an optimum system configuration can be challenging because so many variables are
involved. The values defined for these variables play an important role in determining whether an
application provides optimum, average, or unacceptable performance. This subsection outlines
an approach to configuring key variables in your application environment. The approach, which
emphasizes the importance of link management, is presented in a series of steps that you to calculate
appropriate values for key variables affecting a given server class. You must repeat most of the
66 Configuring Objects in a PATHMON Environment