Pathway/XM System Management Manual

Configuring Clients and Requesters

Compaq NonStop™ Pathway/XM System Management Manual—426761-001

5-5

Configuring High or Low PINs

The setting of the HIGHPIN attribute for the TCP template affects whether the TCP

processes can run at high process identification numbers (PINs). TCPs can be created at

high PINs if the following conditions are met:

•

The HIGHPIN option is set to ON for the TCP template. (The default value is OFF.)

•

There is a high PIN available.

To ensure that Pathway/XM can create as many processes as needed, you should set the

HIGHPIN attribute to ON for all TCP templates in your configuration.

For more information about running processes in your Pathway/XM environment at

high versus low PINs, refer to the manuals that describe system management for your

version of the NonStop

TS/MP and Pathway/iTS products.

Specifying Maximum Total Terminal Weights

The MAXWEIGHTS attribute specifies the maximum value allowed for the sum of the

WEIGHT attribute values for all TERM objects assigned to any TCP process based on

this TCP template. PXMCFG uses this value, along with other TCP constraints, in

calculating the number of TERM objects that can be assigned to a TCP process. For

example, if you specify a value of 100 and SET TERM WEIGHT is 10, then the

maximum number of TERM objects that can be assigned to the TCP is 10. During the

configuration calculation process, the higher the value set for MAXWEIGHTS, the more

TCP processes the PXMCFG process adds to the configuration.

For more information about terminal weights, see Setting Terminal Weights

page 5-11.

Specifying Maximum Unsolicited Messages per Terminal

In the Pathway/XM environment, the MAXINPUTMSGS attribute specifies the

maximum number of unsolicited messages that each TCP using that TCP template

queues at any one time for any TERM object under its control. The meaning of this

attribute in PXMCFG thus differs from its meaning in a PATHMON environment that

uses Pathway/iTS without Pathway/XM: in the latter case, MAXINPUTMSGS defines

the maximum number of unsolicited messages a TCP queues for all terminal requesters.

When this maximum is exceeded for a TERM object, the TCP rejects all new

unsolicited messages until a terminal issues a REPLY to process messages already in the

queue.

During the configuration calculation process, PXMCFG takes into account the value of

MAXINPUTMSGS in determining the number of terminals to assign to a TCP, because

a TCP can queue at most 2045 unsolicited messages at a time for all its requesters. If

the MAXINPUTMSGS value is set to a high number, PXMCFG configures additional

TCP processes to handle the message workload.

If MAXINPUTMSGS is set to 0, terminals associated with the TCP are not able to

accept unsolicited messages. A value of 0 causes the PXMCFG process to disregard any

of the above constraints when determining the number of TCP processes.