Guardian Programmer's Guide

Table Of Contents
Guardian Programmer’s Guide 421922-014
1 - 1
1
Introduction to Guardian
Programming
Writing an application program requires an understanding of the environment and
services provided by the operating system. This guide describes how to use Guardian
procedures in your application program to obtain services from the HP NonStop
operating system and the file system (that is, from the operating system).
This section introduces some of the key topics covered in this guide and provides
references to other sections that contain more detailed information. This section
provides an overview of:
The role of the operating system in providing fault tolerance
The operating-system services available to the application programmer
The requester/server application design that much of this guide supports
How to call Guardian procedures from an application program
The program execution modes that are available on TNS/R systems
How to use the parameter declarations files
How to synchronize processes
Providing Fault Tolerance
The basic design philosophy of fault tolerance is that no single module failure will stop
or contaminate the operating system. This capability is called fault-tolerant operation.
Redundant hardware, backup power supplies, alternate data paths and bus paths,
redundant controllers, and mirrored disks all contribute to the fault tolerance of the
operating system. The Introduction to Tandem NonStop Systems describes these
features.
There is more to fault tolerance than hardware. Fault tolerance requires that all
programs, the operating system as well as individual application programs, contribute
to the reliability and recoverability of a process if a failure occurs. Therefore, fault
tolerance should be considered from both the hardware and software perspectives.
For information about options for achieving fault tolerance in software applications,
refer to the Availability Guide for Application Design.