TS/MP 2.5 Release Supplement

processes while maintaining the same transactional throughput. Therefore, to achieve optimum
performance, modify the PATHMON process configuration. To tune the PATHMON configuration,
follow the steps outlined in Section 3, Steps to Optimum Link Configuration in the TS/MP 2.5
System Management Manual.
NOTE: Context-free and context-sensitive links from a requestor to the same server class are not
shared, but separate links are used for each.
System Management Interface
There are no operational changes to the Subsystem Programmatic Interface (SPI) for system
management or to the SPI message format. The system management interface in TS/MP 2.5 is the
same as that in TS/MP 2.0. However, there are data changes. Some token values might contain
different process names, as follows:
• TS/MP 2.0: The SPI interface returns the TS/MP link manager process name $ZLnn.
• TS/MP 2.5: Link management is handled by both the ACS subsystem PB ($ZPnn) and the
redirector process ($ZLnn). Therefore, the SPI interface returns either of these process names,
depending upon which process encounters the error. This is particularly evident in the STATUS
command.
On servers running TS/MP 2.5, the shut down time for large Pathway environments with many
Pathsend requestors are slightly longer than that of TS/MP 2.0.
Pathsend API
Pathsend APIs allow Pathway domain name syntax in place of the PATHMON process name.
NOTE: SCOBOL Dialog and Send APIs also allow Pathway domain name syntax in place of the
PATHMON process name. For more information on SCOBOL APIs, see the HP NonStop Pathway/iTS
SCREEN COBOL Reference Manual.
Figure 4 (page 22) shows how Pathsend requests are processed by the ACS subsystem.
Figure 4 How Pathsend Requests are Processed by the ACS Subsystem
22 Application Cluster Services (ACS) Subsystem