TS/MP 2.5 Release Supplement

Figure 3 ACS Architecture with Pathway Domain
1. The ACSCTL file, provided in the “ADD Command” (page 66) during startup of the ACS
subsystem, contains information about two Pathway domains. Pathway domain %env1
comprises of PATHMONs $PM1 and $PM2 on NonStop system \A and Pathway domain
%env2 comprises of PATHMONs $PM3 and $PM4 on the same NonStop system.
2. Assumption is that you have configured the Pathway domains with similar Pathway configuration
for the participating PATHMON processes. For example, the server class attributes for SC1
is same for Pathway domain %env1 for PATHMON processes, $PM1 and $PM2.
3. The ACS subsystem recognizes that the send request from requestors (Client1 or Client2) is
sent to a Pathway domain and hence obtains a link (server process) from any one of the
available PATHMON processes, $PM1 or $PM2.
4. When one of the participating PATHMON processes (for example, $PM1 for domain %env1)
is brought down for a Pathway configuration change, the ACS subsystem automatically
redirects the new and queued requests to the other PATHMON process ($PM2) within the
same domain (%env1) to maintain application availability.
Pathway Domain Configuration Management
TS/MP 2.5 provides a management interface called the Pathway Domain Management Interface
(PDMI), with the set of commands to configure and operate multiple PATHMON processes under
a single Pathway domain or to manage Pathway domains. The PDMI interface is a super set of
Pathway Domain Configuration Management 17