TS/MP Release Supplement
ACS Subsystem
HP NonStop TS/MP Release Supplement—546055-006
1-22
PATHTCP4
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.3 (or later version) 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 dynamics, and changes to
management algorithms and some data points. The differences in statistical results
must be minimal.
Error Handling
The ACS subsystem provides the following error handling components.
ACS Auto-Restart
The ACS subsystem detects any failure of its core processes. All the core processes
on the processor are automatically restarted when any core process fails on that
processor. No manual intervention is required from the operators. Also, the Pathsend
requesters can continue to run without being restarted. To use the ACS
auto-restart feature, the Pathsend requesters must follow the guidelines described in
the Programming for Failure Recovery section of the
HP NonStop TS/MP Pathsend
and Server Programming Manual.
Pathsend Errors
Some TS/MP 2.0 errors are no longer generated but that does not cause compatibility
problems. New errors generated by the ACS subsystem can easily be handled by
applications and are highly unlikely to occur. The new errors always indicate that the
transaction has not been processed and that the transaction can be aborted, which is
the standard action for unhandled errors.










