Availability Guide for Application Design

Availability Guide for Application Design—525637-004
Index-1
Index
Numbers
27515
N1 num list
3. The client process makes a
request for a service. The link
manager process uses the 5-6
A
ABORTTRANSACTION Guardian
procedure 4-12
ABORT-TRANSACTION COBOL
statement 4-12
Acceptance testing 9-12
ACF 8-26
Action events 8-20
Active backup process-pair model 7-1,
7-12/7-18, 10-40
C 7-21
COBOL85 7-21
comparison with passive
backup 7-17/7-18
control-state information 7-14, 7-15
critical data 7-13, 7-15
data state on takeover 7-16
detecting primary failure 7-15
file-open information 7-13, 7-15
file-state information 7-14, 7-15
FORTRAN 7-21
multithreaded process
considerations 7-19/7-20
opening files in the backup 7-15
process-state information 7-13/7-15
receiving operating system
messages 7-15
restart point on takeover 7-16
saving file-state information in the
backup 7-15
starting the backup 7-12/7-13
takeover by backup 7-15/7-16
TAL 7-20
TAL procedures, using 7-16/7-17
Active Transaction Pages (ATP) 3-16
Administration Server 3-17
After-image record 1-16, 4-6/4-8
Alarms, purpose of 1-19, 2-16
Application configuration file 8-26
Application design methodology 9-3/9-7
Application development
methodology 9-7/9-12
Application environment 1-10/1-15
Application upgrade, online
See Dynamic upgrade
Asynchronous communication
NonStop Tuxedo application 5-6
RSC/MP application 6-15
ATMI API 4-10, 5-12
ATMI functions 4-10
Audit dump 4-6, 4-9
Audit trail 4-9, 8-7
Automated operations
EMS messages, importance of 8-21
operational outage, preventing 1-9
recovering from failures 8-10
reducing costs 1-5
AUTORESTART TCP parameter 6-26
B
Babbling node, effect on client/server
network 2-18
Backup power supplies 2-9
Backup process
checkpoint information, receiving 7-9
control-state information 7-9, 7-15
critical data 7-9, 7-15
detecting primary failure 7-9/7-10, 7-15
file-open information 7-9, 7-15