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

Configuring Objects in a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
3-4
Configuring a PATHMON Environment
operating environments, see Figure 1-2 on page 1-4. As a system manager for a
PATHMON environment, you can configure and manage OSS server objects.
How you configure a PATHMON environment depends on various management
objectives: the size of your application or applications, the number of users,
response-time requirements, whether the application is distributed over a network, and
so on.
For example, a very large NonStop TS/MP application that includes Pathway/iTS
objects−for example, 100 terminal control processes, 1000 server classes, 40,000 links
and 2000 terminals−might be configured in a single PATHMON environment with
several TCPs to handle the large number of TERM objects required for the application.
If you are running such a system on a single node, you might, for performance
reasons, choose to create a separate PATHMON environment to manage the server
classes and their associated links. By distributing the application among multiple
processes, you improve response time).
If your application generates a large number of Pathsend requests (like the application
shown in Figure 3-2), you should consider distributing the request load by configuring
your TDP processes across a number of CPUs. Such an arrangement avoids
overwhelming any single LINKMON process; each LINKMON can handle only a certain
number of Pathsend requests. (For descriptions of configuration limits, see
Configuration Limits and Defaults on page C-1.)
Configuring a PATHMON Environment
As described in Section 2, Starting and Stopping a PATHMON Environment the SET
PATHWAY command enables you to define the limits for your overall configuration and
to specify owner and security attributes for your PATHMON environment. If you
anticipate ever needing to migrate your application to another node, you should
consider configuring your environment for node independence.
Specifying Limits
You must use the SET PATHWAY command to define this limits before executing a
START PATHWAY command:
MAXASSIGNS
MAXPARAMS
MAXSERVERCLASSES
MAXSERVERPROCESSES
MAXSTARTUPS
The limits that you specify determine the maximum number of SERVER objects you
can define for your system during subsequent configuration:
•
MAXASSIGNS specifies the number of ASSIGN definitions that you can specify for
all server classes.