TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

Figure 3 Example Application Using a Pathsend Requester
In this scenario, clerks at an order entry office enter their transactions into terminals attached to
an IBM system. Processing of the transactions, however, requires access to a database that is
linked to a NonStop system.
1. The clerks enter transactions into their terminals and initiate processing by pressing function
keys. Any preliminary checking or editing is performed by the application on the IBM system.
2. The IBM system collects the transactions and sends them to a Pathsend requester located on
the NonStop system. The transactions are sent by using a high-speed networking product; for
example, SNAX Advanced Peer Networking (SNAX/APN) product.
3. The Pathsend requester accepts the transactions for the NonStop system and formats a request
message containing the name of the server class and the data needed by the server to complete
its work. The TMF transaction begins.
4. The Pathsend requester forwards the request message to the LINKMON process or the ACS
subsystem processes by calling the Pathsend SERVERCLASS_SEND_ procedure. (This is a
context-free message.)
5. If the LINKMON process or the ACS subsystem processes do not have a link to the specified
server class, the LINKMON process or the ACS subsystem processes ask the PATHMON
process for a link to a server process in the server class. The PATHMON process replies that
a server process is available. If the LINKMON process or the ACS subsystem processes already
have a link to the server class, this step is not performed.
6. The LINKMON process or the ACS subsystem processes forward the request to the server
process by using NonStop Kernel interprocess communication.
7. The server process receives and reads the request message.
Transaction Processing Scenario 27