Availability Guide for Application Design

Contents
Availability Guide for Application Design—525637-004
vii
Glossary
10. Designing Applications for Change (continued)
Using a Modular Design 10-18
Using Version-Labeled Interfaces for Intermodule Communication 10-19
Supporting Implementation 10-22
Explicit Upgrade Action: Handling Changes in Initialization Information 10-23
Changing a NonStop TS/MP Application 10-24
Using Message Versions and Server Upgrade 10-24
Using the Trickle Catchup Approach 10-25
Upgrading a TCP Requester 10-26
Changing a NonStop SQL/MP Program or Database 10-27
Physically Reconfiguring the Database 10-28
Execution-Time Name Resolution 10-33
Installing a New Program Version 10-34
Recompiling or Execution-Time Name Resolution for Data Definition
Changes 10-36
Changing a NonStop Process Pair 10-38
Replacing the Process 10-39
Replacing a Library 10-42
Glossary
Index
Figures
Figure i. Related Manuals xvii
Figure 1-1. The NonStop Application Environment 1-11
Figure 1-2. Availability and Costs 1-22
Figure 1-3.
Collecting Outage Data 1-24
Figure 2-1.
Fault Tolerance and Availability 2-2
Figure 2-2. NonStop Hardware Architecture, S-Series Server 2-5
Figure 2-3. NonStop Hardware Architecture, K-Series Server 2-6
Figure 2-4. Detecting Processor Failure 2-9
Figure 2-5. A Disk Process: An Example of an I/O Process Pair 2-14
Figure 2-6. S-Series Client/Server Architecture With a Continuously Available
Server 2-20
Figure 2-7. K-Series Client/Server Architecture With a Continuously Available
Server 2-21
Figure 2-8. An S-Series Fault-Tolerant LAN 2-22
Figure 2-9. NS-Series Triplex Server Attached to ServerNet 2-24
Figure 2-10. 4-Node ServerNet Cluster 2-26