TS/MP Supplement for Limits Relief (G06.26+)

The major new and changed features are as follows:
Applications
No syntax changes to application configurations are required in PATHMON environments.
However, you may want to make some configuration modifications for performance tuning.
❍
The TS/MP 2.1 Pathsend library replaces the TS/MP 2.0 Pathsend library. Although the two
Pathsend libraries function similarly, they are internally different and cannot be used
interchangeably. For information on migrating applications, see Chapter 3, Migrating
Applications to TS/MP 2.1.
❍
●
Management and Control
There are no changes to the PATHMON process and the PATHCOM interface.❍
The TS/MP installation automatically installs the ACS subsystem components. For
information on installing and configuring, see Chapter 5, Installing and Configuring.
❍
Before running TS/MP Pathsend applications you must start the ACS subsystem. HP
recommends that you start PATHMON processes after the ACS subsystem is started. For
information on configuring and starting, see Chapter 5, Installing and Configuring and
Chapter 6, Managing the ACS Subsystem.
❍
●
Link Management
The ACS subsystem replaces all the link management functions formerly handled by the
LINKMON (ROUT) process.
❍
The ACS subsystem returns a new set of EMS messages that functionally replace the
messages formerly returned by the LINKMON process. Similarly, the ACS subsystem
Pathsend API returns a new set of errors. Messages returned by TS/MP PATHMON
processes are unchanged.
For information on EMS messages, see the Operator Messages Manual. For information on
the ACS subsystem EMS event tokens, see Chapter 10, ACS EMS Event Tokens. For
information on the ACS SCF errors, see Chapter 9, SCF Error Messages. For information on
the ACS API errors, see Chapter 8, Pathsend Errors.
❍
●
New Pathsend Limits
TS/MP 2.1 contains a link-management architecture designed for the more powerful processors typically
installed in today's NonStop systems. It provides higher configuration and processing limits to support
higher link capacity for client processes and more efficient acquisition and usage of server processes.
TS.MP 2.1 is designed with no architectural limits, which allows TS/MP applications to run without
encountering limit errors. However, the practical limits may be lower depending upon on the physical
hardware available on the system (for example, memory) or on file system constraints. For a list of the
configuration and processing limits, see Configuration and Environment Limits in Chapter 2.