TS/MP 2.5 Release Supplement

4 Migrating Applications to TS/MP 2.5
This section includes these topics:
• “Environment Similarities” (page 50)
• “Environment Differences” (page 50)
All TS/MP 2.0 applications that use Pathsend requestors and TS/MP configuration scripts (also
called OBEY files) can run in a TS/MP 2.5 environment. However, to take advantage of the new
features and to understand slight differences in behavior, it is important to understand the similarities
and differences between the two versions of TS/MP.
Environment Similarities
TS/MP 2.5 is similar to TS/MP 2.0 in the following ways:
• You do not need to recompile the TS/MP 2.0 applications. However, applications that manage
configuration and operation of environments are an exception; you might need to make
changes as described in “Environment Differences” (page 50).
• You do not need to recompile even if you want to use the new Pathway domain feature.
Although the Pathway domain name syntax is different from a regular PATHMON process
name syntax, the applications need not be recompiled even if an application wants to send
a request to a Pathway domain.
If the send is being targeted to a specific PATHMON process that is made part of a domain
as mentioned in the ACSCTL file, then the default behavior of TS/MP 2.5 is that the send is
targeted to the entire domain. However, you may want to suppress this behavior and continue
to send requests to the specific PATHMON process by setting the flags parameter as
described in the TS/MP 2.5 Pathsend and Server Programming Manual.
• The program filename and the process name remain unchanged. To provide transparent
migration for TS/MP 2.0 applications, the ACS subsystem link management functions use the
same system filename ($SYSTEM.SYSnn.ROUT) and process name ($ZLnn) used by the
TS/MP 2.0 LINKMON process. However, because the contents of $SYSTEM.SYSnn.ROUT
are different for each version, the TS/MP 2.5 version cannot be used in a TS/MP 2.0
environment, and vice versa.
Environment Differences
TS/MP 2.5 is different from TS/MP 2.0 in the following ways:
• Process name: For applications using Pathsend requestors, PATHMON processes communicate
with the PB process ($ZPnn); they no longer communicate with the link manager process,
$ZLnn. The $ZLnn process continues to perform link management functions.
• Higher Pathsend limits: To use higher link limits supported by TS/MP 2.5, TS/MP 2.0 users
may want to modify the Pathway configuration file as needed. For more information on using
higher link limits, see the new limits listed in Table 2 (page 20).
• ACS Subsystem start up: Before starting TS/MP Pathsend requestors, you must start the ACS
subsystem using the SCF commands. For more information on starting the subsystem, see
“Installing and Configuring” (page 53).
• Pathsend library: The TS/MP 2.5 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.
• Pathway Domain Syntax and Updated Optional flags Parameter: The PATHMONName
parameter in SERVERCLASS_SEND_ and SERVERCLASS_DIALOG_BEGIN_ calls are updated
to accept a new Pathway domain syntax. Additionally, the flags parameter in the two APIs
50 Migrating Applications to TS/MP 2.5