Availability Guide for Application Design

Availability in the Pathway Transaction-Processing
Environment
Availability Guide for Application Design—525637-004
6-12
How Does RSC/MP Work?
RSC/MP permits workstations to invoke NonStop Transaction Services/MP (TS/MP)
servers on NonStop servers. By providing a client-server environment, RSC/MP can
improve the performance of NonStop TS/MP applications while maintaining the ability
to handle high-transaction volumes.
RSC/MP provides the link between NonStop servers and client workstations over
existing communication networks. Clients may communicate with a NonStop server by
serial asynchronous communication or a LAN using TCP/IP, NetBIOS, or IPX/SPX.
The RSC/MP application program interface (API) lets you develop custom user
interfaces to the NonStop system. Application programs running on the workstation
use RSC/MP’s API to send and receive messages from NonStop processes. These
RSC/MP application programs can be written in a variety of programming languages,
including C, Visual Basic, and PowerBuilder. For an extensive description of the
RSC/MP API, see the RSC/MP Programming Manual.
This subsection introduces the RSC/MP products and their availability features. First,
it establishes how these products normally function and includes a skeletal work
session. It goes on to describe how availability is maintained even if critical
components fail and how a typical work session is affected. Finally, it explains what the
application designer or developer needs to consider to take full advantage of these
features.
How Does RSC/MP Work?
Figure 6-4 shows the major components of a typical RSC/MP application.
Figure 6-4. Components in a Typical RSC/MP Application That Uses Pathsend
Interprocess Sessions
Server
Server Class
LINKMON
PATHMON
Database
NonStop TS/MP
Workstation
RSC/MP
Client
TDP
CSS
HP Server
RSC/MP
COM
VST504.vdd