TS/MP Supplement for Limits Relief (G06.26+)
If the PATHMON process does not have a server process available and the maximum
server processes has not yet been reached, the PATHMON process starts a server
process.
When the process broker acquires the server process from the PATHMON process, it
creates the objects needed to control the link through the redirector process.
4.
The local redirector process checks for security rights and configuration information. If
the requester has the access rights to perform the send operation, the redirector forwards
the request to the server process.
5.
Other process brokers in the system may also be requesting server processes from the
PATHMON process at the same time. Server processes can be shared between process
brokers if the MAXLINKS attribute is set to a value greater than 1.
6.
Parallel requests to a server process are queued on the server's $RECEIVE file until they
are handled by the server process.
7.
Process Management
To manage application server processes created by the TS/MP PATHMON process, use
TS/MP. To manage the ACS subsystem, use the SCF ACS commands. For more information on
the ACS subsystem management interface, see Chapter 7, SCF Command Reference for the
ACS Subsystem.
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 requester
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, you must stop all requestors in the same CPU. Before the
requesters are started again, use the SCF CONTROL ACS command to restart the ACS
subsystem processes in that CPU.
In most cases, a processor has no knowledge of 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 requester can either
abort or retry the operation.
Statistics Collection
You can collect and report statistics using PATHCOM exactly as documented for TS/MP 2.0.
However, the values reported for TS/MP 2.1 may not be identical to the values reported for
TS/MP 2.0 for the same application. The difference is due to different collection mechanisms,
operational dynamics, and changes to management algorithms and some data points.