Availability Guide for Application Design

Contents
Availability Guide for Application Design—525637-004
vi
9. Minimizing Programming Errors
8. Availability Through Process-Pairs and
Monitors (continued)
Receiving and Processing Information in the Active Backup 8-14
Takeover by the Active Backup 8-15
Active Backup With TAL 8-16
Comparing Active Backup With Passive Backup 8-17
Active Backup Is More Efficient Than Passive Backup 8-17
Active Backup Is More Flexible Than Passive Backup 8-17
Passive Backup Is Easier to Design 8-18
Process Pairs and Nowait I/O 8-18
Nowait I/O and Multiple Requests to the Same File 8-19
Language Issues 8-20
pTAL and TAL 8-20
C and C++ 8-21
Native Mode COBOL, COBOL85, and FORTRAN 8-21
NonStop Server for Java 8-22
Using a Process Monitor 8-22
Site-Written Process Monitors 8-22
HP Process Monitors 8-23
The Kernel Subsystem 8-23
9. Minimizing Programming Errors
Using Reusable Program Modules 9-1
Shared Run-Time Libraries 9-2
Reusable Objects 9-2
Design Methodology for Eliminating Software Faults 9-3
Common Causes of Software Faults
9-3
Checklist for Common Errors
9-4
Checklist for Detecting Errors 9-5
Development Methodology 9-7
Specify and Review the Requirements 9-9
Specify and Review the Design 9-9
Incremental Implementation and Unit Testing 9-9
High-Level Testing 9-10
10. Designing Applications for Change
Preparing for Future Changes 10-1
Considering Portability Requirements 10-2
Isolating Data From the Application 10-15