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

PATHMON and PATHCOM
There are no changes to the PATHCOM command interface. Although there are no operational
changes to the SPI interface to PATHMON processes, there are some data changes, described in
System Management Interface in this chapter.
Link Management
To provide transparent migration for TS/MP 2.0 applications, the ACS subsystem link
management functions use the same program file name ($SYSTEM.SYSnn.ROUT) and
process name ($ZLnn) used by TS/MP 2.0. However, because the contents of
$SYSTEM.SYSnn.ROUT are different for each version, the TS/MP 2.1 version cannot be used
in a TS/MP 2.0 environment, and vice versa.
Due to the changes in server class queuing, it is important that servers conform to the server
packaging guidelines outlined in Section 2 of the TS/MP Pathsend and Server Programming
Manual, in the subsection entitled Packaging Server Functions. These changes are
recommended but not required:
Grouping long-running and short-running requests causes uneven response times and
increases the number of links needed to maintain transaction throughput. If an application
contains server programs that process both long and short-running requests, configure the
server program to use multiple server classes in PATHMON. This separates the long and
short-running requests into different queues. Modify requester programs to call one
server class for long-running requests and another server class for short-running requests.
●
The new algorithm used for link management may require more or fewer links to server
processes while maintaining the same transactional throughput. To achieve optimum
TS/MP 2.1 performance, therefore, modify the PATHMON process configuration. To
tune the PATHMON configuration, follow the steps outlined in the TS/MP Systems
Management Manual, in the Section 3 subsection entitled “Steps to Optimum Link
Configuration”.
●
For more information on how the ACS subsystem handles link management, see Chapter 4,
Introduction to the ACS Subsystem.
System Management Interface
There are no operational changes to the Subsystem Programmatic Interface (SPI) for system
management or to the SPI message format. The TS/MP 2.1 version is the same as provided by
TS/MP 2.0.
However, there are data changes. Some token values may contain different process names, as
follows: