TS/MP Supplement for Limits Relief (H06.05+, J06.03+)

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.
New ACS Subsystem
The ACS subsystem provides link management functions for applications using Pathsend
requesters. For information about the ACS subsystem, see Chapter 4, Introduction to the ACS
Subsystem.
Changes to LINKMON (ROUT) Process
In TS/MP 2.1, the functions performed by the TS/MP 2.0 LINKMON (or ROUT) process are
performed by the ACS subsystem components. Messages formerly returned by the LINKMON
(or ROUT) process are replaced by similar messages returned by the ACS subsystem
components. For more information on link management, see Link Management in Chapter 2.
Compatibility With TS/MP 2.0
TS/MP 2.1 cannot be installed on the same system with either TS/MP 2.0 or TS/MP for Tuxedo
users. However, the TS/MP 2.1 environment supports the following TS/MP 2.0 environment
features and functions:
Requesters and Servers. Server classes defined in TS/MP 2.1 are fully accessible to
requesters from TS/MP 2.0 environments in other systems. Similarly, requesters from a
TS/MP 2.1 environment can fully access server classes in TS/MP 2.0 environments in
other systems.
●
LINKMON (ROUT) name. The ACS subsystem redirector process uses the same file
name ($SYSTEM.SYSnn.ROUT) and process name ($ZLnn) that are used by the
LINKMON process in TS/MP 2.0 (although the contents of the file and the functionality
of the process are different). For a description of the ACS subsystem components, see
ACS Subsystem Components in Chapter 4.
●