Availability Guide for Application Design

Contents
Availability Guide for Application Design525637-004
ix
Tables
Figure 10-2. Indirect Addressing Allows Multiple Versions of the Data-Interface
Module to Be Used Simultaneously 10-17
Figure 10-3. Labeled Message Versions 10-20
Figure 10-4. Overlapping Ranges of Labeled Message Versions 10-21
Figure 10-5. Increasing Application Availability Through Dynamic Name
Resolution 10-34
Figure 10-6. Increasing Application Availability During SQL Program
Upgrade 10-36
Figure 10-7. Increasing Application Availability During DDL Changes 10-38
Tables
Table i. Organization and Contents of the Manual xiv
Table 1-1. Server System and Network-Level Products That Help Provide
Availability 1-27
Table 1-2. Data Protection Products That Help Provide Availability 1-28
Table 1-3. Products That Keep Tuxedo Applications Available 1-28
Table 1-4. Products That Help Keep Applications Available in the Pathway
Transaction-Processing Environment 1-29
Table 1-5. HP Communication Products That Help Provide Availability 1-30
Table 1-6. Language Compilers That Help Support Availability 1-31
Table 1-7. Products and Facilities Related to DSM That Help Provide
Availability 1-31
Table 1-8. Products for Client Workstations That Help Provide Availability 1-33
Table 4-1. NonStop Tuxedo Interfaces to Transaction Control Facilities 4-10
Table 4-2. POET Gateway Interface to Transaction Control Facilities 4-11
Table 4-3. Remote Server Call Interface to Transaction Control Facilities 4-11
Table 4-4. Programmatic Interface to Transaction Control Facilities on an HP
System 4-12
Table 6-1.
Process Persistence Techniques Used in Pathway Applications 6-29
Table 6-2.
Other Recovery Techniques Used in Pathway Applications 6-29
Table 7-1. TAL Procedure and NonStop C Function Correspondence 7-16