TS/MP 2.5 Release Supplement

Table 5 Architecture Comparison of TS/MP Versions
TS/MP with NonStop
TuxedoTS/MP 2.0TS/MP 2.1
TS/MP 2.3, 2.4, and
2.5
TS/MP Application
Environment
TS/MP Application
Environment
TS/MP Application
Environment
TS/MP Application
Environment
Application
TS/MP Tuxedo
(Supervisor and
TSMPCOM Processes)
TS/MP 2.0 (Existing
PATHMON and
PATHCOM Processes)
TS/MP 2.1 (Existing
PATHMON and
PATHCOM Processes)
TS/MP 2.3, 2.4, and
2.5 (Updated
PATHMON,
Management and
Control
PATHCOM, and new
PDMI Processes)
Router ProcessLINKMON ProcessApplication Cluster
Services (ACS)
Application Cluster
Services (ACS)
Link Management
HP NonStop J, G, or
H-Series Operating
System
HP NonStop J, G, or
H-Series Operating
System
HP NonStop G-Series
Operating System
HP NonStop J or
H-Series Operating
System
Operating System
NOTE: TS/MP for NonStop Tuxedo users is included in the table solely for comparative purposes.
TS/MP 2.5 does not apply to NonStop Tuxedo users.
TS/MP Features
TS/MP 2.5 contains the following new or changed features.
Large Message Support for Context-Sensitive Pathsends
The following Pathsend APIs are introduced in this release:
• SERVERCLASS_DIALOG_BEGINL_
• SERVERCLASS_DIALOG_SENDL_
• SERVERCLASS_DIALOG_BEGINL64_
• SERVERCLASS_DIALOG_SENDL64_
These APIs allow you to send and receive messages up to 2 MB size in a context-sensitive Pathsend.
For more information on these APIs, see the TS/MP 2.5 Pathsend and Server Programming Manual.
Support for Pathway Domains across Nodes
A Pathway domain is a logical entity. The earlier versions of TS/MP had a limitation where all the
PATHMONs configured under the Pathway domain must be running on the local system. This
limitation is overcome in TS/MP 2.5.
TS/MP 2.5 allows users to configure a Pathway domain with PATHMON processes running on
different nodes. The Pathway domain is local to the system on which it is configured. Users can
have a combination of remote and local PATHMON processes in a domain and no changes are
required to the application to use this feature. Users can continue to use the Pathsend APIs with
either the domain name, local or remote PATHMON process name. Based on the other parameters
like PATHMON process weights, available server processes, and existing links, a Pathsend request
gets processed by any PATHMON process configured in that domain, local or remote. Users can
control the remote PATHMON processes using PDMCOM on the system to which the Pathway
domain belongs.
The remote PATHMON process acts as a standalone PATHMON process for the Pathsend requestors
running on other nodes where it is not configured as a member of a local Pathway domain.
The ACS subsystem remains local to the node in which it is running. ACS subsystems do not share
configuration information with each other. However, users can configure identical Pathway domains
on multiple nodes. This creates the same Pathway domain virtually on multiple nodes.
TS/MP Features 29