Guardian Programmer's Guide

Table Of Contents
Writing a Requester Program
Guardian Programmer’s Guide 421922-014
21 - 4
File System I/O Synchronization
The requester establishes communication with the server of its choice by sending it the
message that was formulated during the data-mapping phase. Usually, the requester
expects a reply from the server and therefore sends the message to the server using
the WRITEREAD[X] procedure. If no reply data is expected, you can use the
WRITE[X] procedure. Section 6, Communicating With Processes, provides details on
how to do this.
Selecting a Generic Server
Your requester process may choose from several functionally identical servers. For
example, if a server process is heavily used, your application may share the load by
running several functionally identical servers. In this kind of design, however, the
servers must be context free so that the requester can select any available server.
Figure 21-3 shows the model.
See Section 22, Writing a Server Program, for a discussion of context-free servers.
Transaction Control Using TM/MP
The NonStop Transaction Manager/MP (TM/MP) provides the ability to control
transactions against a database from the requester process. These techniques ensure
data integrity by controlling access to the database from the requester process. See
the Introduction to NonStop Transaction Manager/MP (TM/MP) for an overview or the
NonStop TM/MP Application Programmer’s Guide for programming information.
File System I/O Synchronization
The Guardian file system provides a synchronization mechanism for detecting lost or
duplicate interprocess messages. This mechanism becomes important when dealing
Figure 21-3. Selecting From Functionally Identical Servers
VST105.VSD