Availability Guide for Application Design

Index
Availability Guide for Application Design525637-004
Index-14
O
NonStop Tuxedo applications
asynchronous communication 5-6
availability concepts 5-2/5-3, 5-6/5-14
BBL process 5-7, 5-10
client process
ATMI API 5-12
error handling 5-12
failure of 5-7, 5-10/5-11
recovery from failure of 5-10/5-11
recovery logic 5-12
saving context 5-12
TX API 5-12
communications failure 5-7, 5-11/5-12
configuration file 5-13
configuring links 5-13
DBBL process 5-7, 5-10
design implications 5-12/5-14
development concerns 5-12/5-13
Expand network 5-4
limits, configuring 5-13
machine failure 5-7, 5-11
multiple servers 5-4
native System/T client 5-14
NonStop TCP/IP process
configuring 5-13
failure of 5-7, 5-9/5-10
recovery from failure of 5-9/5-10
operational concerns 5-13/5-14
PATHMON process 5-7, 5-10
processor, failure of 5-7
server class, configuring 5-13
server process
configuring 5-13
error handling 5-13
failure of 5-7, 5-7/5-8
long running transaction 5-13, 6-7
recovery from failure of 5-7/5-8
service 5-12
services 5-13, 10-25
WSH process 5-7, 5-8
WSL process 5-7, 5-8/5-9, 5-13
NonStop Tuxedo servers, in the open
environment 5-1
NonStop Tuxedo System/T
availability features 1-29
open environment, in the 5-1
purpose of 1-14
transaction support in 1-14
Nowait depth 7-19
Nowait I/O, with process pairs 7-18/7-20
NSAA
See NonStop Advanced Architecture
NSX 1-32, 8-41
O
Object Linking and Embedding for
Transaction Processing (OLE/TP) 1-33
Objects
controlling 8-23
down state 8-12
identifying 8-10/8-11
odd state 8-12
offline, reporting 2-16
state change 8-12/8-13, 8-21
status, obtaining 2-16
unknown state 8-12
up state 8-12
valid states 8-12/8-13
Object-oriented programming 9-1/9-3
OMF 1-32, 8-41
Online dump 4-6, 4-9
Online recovery, support for 8-37/8-38
Open applications
availability of 1-16/1-17, 5-1/5-14
products for availability 1-27
Operational costs of downtime 1-4
Operational outage 1-9
Outage classes 1-8/1-10
Outages