Availability Guide for Application Design

Availability in the Pathway Transaction-Processing
Environment
Availability Guide for Application Design—525637-004
6-29
Summary and Comparison of Application
Components
The application development team must design and code the feature into the
application.
•
Not applicable
The technique cannot be used with the application entity.
•
Depends on function of workstation
The technique can be used if the workstation software is coded to support the
feature
Table 6-1 shows which of the three levels of process persistence are used for each
process in a Pathway application.
Table 6-2 shows recovery techniques other than the levels of process persistence and
how they are used with each type of process in a Pathway application.
Table 6-1. Process Persistence Techniques Used in Pathway Applications
Application
Process
Process Pairs With
Continual
Checkpointing
Initialized
Persistence
Immediate
Persistence
TCP Configurable Configurable Configurable
PATHMON Automatic Not Applicable Not Applicable
Pathsend Requester Development
Responsibility
Development
Responsibility
Development
Responsibility
TDP Not Applicable Configurable Not Applicable
RSC/MP Client Depends on
Function of
Workstation
Depends on
Function of
Workstation
Depends on
Function of
Workstation
TCP Requester Not Applicable Not Applicable Not Applicable
Server Process Development
Responsibility
Development
Responsibility
Configurable
Server Class Not Applicable Not Applicable Not Applicable
Table 6-2. Other Recovery Techniques Used in Pathway
Applications (page 1 of 2)
Application
Process
TMF
Transactions
Client or
Requester
Context
File system
retries
Process
Replication
TCP Automatic Automatic Automatic Not Applicable
PATHMON Not Applicable Not Applicable Automatic Not Applicable
Pathsend
Requester
Development
Responsibility
Development
Responsibility
Not Applicable Not Applicable