z/TPF Geographically Dispersed Processing for High Availability

Multiple z/TPF Customers; Citibank, SABRE, Marriott, Amex, and TVPT, desire an implementation of z/TPF where at least two geographically dispersed z/TPF Loosely Coupled Computing Cluster (LCCC) Systems may cooperatively process against the same database.
Contact: john.prictoe@citi.com; ron.carlson@sabre.com
Description:
a. Multiple z/TPF Customers; Citibank, SABRE, Marriott, Amex and TVPT, desire an implementation of z/TPF where at least two geographically dispersed z/TPF Loosely Coupled Computing Cluster (LCCC) Systems may cooperatively process against the same database.
<Comment by z/TPF's Mark Gambino> The z/TPF systems do not have to be loosely-coupled (L/C). For example, the US site could be L/C while another site in country with small local transaction rates could be single image z/TPF.
b. Ideally this would be an Active/Active Failover Configuration where message traffic can be split between the two sites but with both sites being able to process all of the traffic when the other system is not available
c. This RFE acknowledges that there are at least three distinct patterns z/TPF Customer Processing patterns that must be satisfied:
i. Reservation Booking Pattern
ii. Credit Card Authorization Pattern
iii. ATM Banking Transaction Pattern
d. The three above patterns may require different approaches to solving this need recognizing that the Active/Active may need to be relaxed to Active/Passive failover model.