TS/MP 2.5 Release Supplement

Consider that the ACSCTL file on system \A has the following weights defined for domain %DOM.
%DOM = \A.$PM1:80, \A.$PM2:20
The PATHMONs $PM1 and $PM2 have server DEMO-SERVER configured. The LINKDEPTH and
MAXLINKS parameter values are set to 1. The MAXSERVERS and NUMSTATIC parameter value
is:
$PM2$PM1PATHMON Names
Parameters
416MAXSERVERS
14NUMSTATIC
Under heavy load conditions, all the server processes (links) are active. This means PATHMON
$PM1 has 4 static and 12 dynamic links active, whereas PATHMON $PM2 has 1 static and 3
dynamic links active. It might be possible that the links from PATHMON $PM2 are more responsive
than PATHMON $PM1. Because the ACS subsystem favors efficient links, the dynamic links from
PATHMON $PM1 will be returned before PATHMON $PM2, thereby leading to a distorted link
distribution until the load condition subsides.
If a PATHMON returns a link error, and more than one PATHMON is associated with the Pathway
environment, the request is retried to the next PATHMON in the domain until the link request is
processed or all the PATHMONs return an error. Only the last error is returned to the requestor in
this case, but all errors are logged through the normal PATHMON error logging process.
Process Management
To manage the ACS subsystem, use the SCF ACS commands. For more information on the ACS
subsystem management interface, see “SCF Command Reference for the ACS Subsystem” (page 62).
PATHMON processes associated with each TS/MP environment in the system monitor the server
processes; the ACS subsystem redirector process in each CPU handles the requestor processes. If
any ACS subsystem processes fail, the other ACS subsystem processes in the same CPU typically
fail soon thereafter because of the tight bond between them.
If any ACS subsystem process fails in a processor, the ACS subsystem restarts all the core processes
on that processor automatically.
In most cases, a processor cannot ascertain ACS subsystem process failures in other processors.
The exception is when a process fails during a communication on an assigned server link. When
this occurs, the link is terminated and an error is reported. The requestor can either abort or retry
the operation.
PATHTCP4
The PATHTCP4 and the Java library components of Pathway/iTS 1.1 support the Pathway domain
name syntax in place of PATHMON name for SCOBOL SEND and DIALOG APIs. For compatibility
purposes, the current name forms and their default values have been maintained.
You are not required to make any changes to your SCOBOL application programs to do sends to
Pathway domain. If the PATHMON process name specified in the SCOBOL SEND verb is part of
a Pathway domain, the send will be processed by a server in any PATHMON in the domain. If
the specified PATHMON is not part of any domain, the send will be processed by that PATHMON.
You can also replace the PATHMON process name with the domain name in the SEND verbs.
Statistics Collection
You can collect and report statistics using PATHCOM exactly as done for TS/MP 2.0. However,
the values reported for TS/MP 2.5 might not be identical to the values reported for TS/MP 2.0 for
the same application. The difference is because of different collection mechanisms, operational
26 Application Cluster Services (ACS) Subsystem