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

Chapter 3. Migrating Applications to TS/MP 2.1
Prev Next
Chapter 3. Migrating Applications to
TS/MP 2.1
TS/MP 2.1 Environment Similarities
TS/MP 2.1 Environment Differences
In general, all TS/MP2.0 applications that use Pathsend requesters and TS/MP 2.0 scripts (also
called OBEY files) can run in a TS/MP 2.1 environment. However, to take advantage of new
features and to understand slight differences in behavior, see the following topics.
TS/MP 2.1 Environment Similarities
No need to recompile. You do not need to recompile TS/MP 2.0 applications. However,
applications that manage configuration and operation of environments are an exception;
you may need to make changes as described in TS/MP 2.1 Environment Differences.
●
Program file name and process name are unchanged. To provide transparent
migration for TS/MP 2.0 applications, the ACS subsystem link management functions
use the same system file name ($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.1 version cannot
be used in a TS/MP 2.0 environment, and vice versa.
●
TS/MP 2.1 Environment Differences
Process names. For applications using Pathsend requesters, PATHMON processes
communicate with the process broker process ($ZPnn); they no longer communicate with
$ZLnn.
The link manager process, $ZLnn, still performs link management functions. In TS/MP
2.0 this process was the link manager; in TS/MP 2.1 this process is the ACS subsystem
redirector process.
●
Higher configuration limits. You may want to modify your configuration to take
advantage of the higher link limits supported by TS/MP 2.1. See the new limits listed in
the table Pathsend Requester Limits in Chapter 2.
●
ACS Subsystem start up. Before starting TS/MP Pathsend requesters, you must first use●