TS/MP 2.5 Management Programming Manual

Table 3 Configuration and Manual Correspondences (continued)
To Perform these actions…You Need…If Your Configuration Includes…
See error-handling examplesSection 17
Define and control SERVER objectsSection 9Servers
Architecture and Components
The Pathway subsystem includes a group of related software tools that enable your organization
to develop, install, and manage online transaction processing applications.
Transaction processing applications consist of two types of programs: requester programs (called
clients in other environments) and server programs. Among other benefits, the requester/server
design allows application logic to be distributed near the resources it manages. For example,
presentation services are located in requester programs near the I/O devices; database logic
resides in server programs near the database. Requesters and servers communicate using the
message system provided by the NonStop operating system.
Link managers (such as ACS subsystem processes and Pathway/iTS terminal control processes
(TCPs)) coordinate the sharing of links between requesters and server processes. The PATHMON
process, in addition to creating, configuring, and globally managing server classes, grants links
to link managers that request access to server processes.
Figure 2 (page 19) shows a simple TS/MP application that uses Pathway/iTS. This example shows
the TCP and the PATHMON process managing communications between Guardian requesters
and servers.
NOTE: Although ACS subsystem processes are visible to the PATHMON process and are part
of the Pathway subsystem, they are not controlled or managed by the PATHMON process. They
are, however, treated as external TCPs by the PATHMON process that processes link requests.
For more information about TCPs, see the Pathway/iTS System Management Manual. For more
information about ACS subsystem processes, see the TS/MP Supplement for Limits Relief Manual.
18 Introduction