TS/MP 2.5 Pathsend and Server Programming Manual

Perform application-dependent error logic, which
might include aborting transaction.
IF( ReplyError ) THEN
.
.
.
ELSE
TMFError :=ENDTRANSACTION;
Clients Using RSC/MP and POET
The RSC/MP product facilitates client/server computing, allowing workstation applications to
access Pathway server-classes and Guardian processes. The RSC/MP product supports a number
of different transport protocols and workstation platforms. For detailed information about the
supported platforms and protocols, see the Remote Server Call (RSC) Programming Manual.
Transactions are transmitted from the workstation application (the client) to a Pathway application
running on a NonStop server by means of a supported communications protocol, such as network
basic input/output system (NETBIOS), TCP/IP, or an asynchronous connection.
RSC/MP includes a process called the Transaction Delivery Process (TDP), which resides on the
NonStop system. The TDP is a multithreaded process that can handle multiple workstations. It routes
request messages from workstations to Pathway server-classes by using either the Pathsend API
and the ACS subsystem processes, or the TCP provided in the Pathway/iTS product. If the TCP is
used, it can route a request message to a Pathway server by using either the IDS requestor supplied
as part of RSC/MP or an IDS requestor that you develop yourself. The TDP can also send request
messages from a workstation to a Guardian process.
The POET provides tools for developing RSC/MP clients for the Microsoft Windows environment.
These tools include a simplified programmatic interface, name mapping, and data conversion
mapping.
For information about designing and coding requestors with the RSC/MP product, see the Remote
Server Call (RSC) Programming Manual. For information about using the POET product, see the
Pathway Open Environment Toolkit (POET) Programming Manual.
Requestors Using GDSX
The GDSX communications subsystem product simplifies the development of front-end processes
and back-end processes for communication with I/O devices. These devices can be of any type,
including workstations, terminals, ATMs, point-of-sale (POS) devices, and industrial robots. GDSX
supplies code that provides multitasking and other features useful for developing these front-end
and back-end processes.
A GDSX process can act as a front-end process for ACS subsystem processes or a Pathway/iTS
TCP.
A GDSX process contains two primary parts:
• TSCODE, supplied by HP
• USCODE, supplied by the application programmer
TSCODE provides generic routines and management services that help you build a multithreaded,
fault-tolerant process. TSCODE provides these functions:
• Creates new tasks and stops tasks
• Receives all system messages and I/O requests
• Dispatches (wakes up and executes) the appropriate active task to process messages and
requests
• Handles errors
Designing Requestor Programs 39