RSC/MP 7.2 Programming Manual

Introduction to Remote Server Call (RSC/MP)
HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004
1-6
TDP TERM Object
The TDP consists of these configurable objects:
•
The TERM object corresponds to a workstation.
•
The ACS object defines a user-written access control server that provides security
for processes on the NonStop system.
•
The PIPE object provides an interface to a Pipeman process.
TDP TERM Object
All RSC/MP connections and sessions terminate with a TERM object. While generally,
a TERM corresponds with a workstation, it is possible for a workstation to be
configured to access multiple TERM objects. The TERM object sets defaults for the
sessions associated with it. For example, a TERM object can enforce access through
an ACS process, regardless of how individual workstations are configured.
RSC/MP Sessions
All communication between applications on workstations and servers on the host
system takes place within the context of an RSC/MP session. Each workstation can
have multiple sessions within an RSC/MP connection. An RSC/MP session supplies
the follow capabilities:
•
identifies the security context for subsequent I/Os
•
provides communication with Guardian named processes
•
provides communication with Pathway server classes through either a LINKMON
process or a user-provided IDS requester
•
accommodates multiple concurrent I/Os to one or more application servers.
RSC/MP limits and sessions are further described in the Remote Server Call
(RSC/MP) Installation and Configuration Guide.
Transaction Management Facility
RSC/MP provides programmatic functions on the workstation to help you recover from
failures and to ensure database consistency. When you use these functions with the
Transaction Management Facility (TMF) on the host system, workstations can recover
from failures with little or no interruption to the programs that the workstation is
running.
If data communications fail, the transport layer attempts to connect through any
alternate path that is configured. If this is successful, no error is returned. If all retries
and alternate paths fail, an error is returned to the application by the API. Upon an
unrecoverable failure, the TDP on the NonStop system aborts the connection to the
workstation and aborts any active transactions. The workstation application can try to
connect to a different TDP.