RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

• Chapter 7 (page 158)describes how to synchronize entire databases or selected database
volumes online.
• Chapter 8 (page 176) and Chapter 9 (page 250) present the syntax of all RDFCOM and
RDFSCAN commands, respectively, and give examples of these commands.
• Chapter 10 (page 260) describes the triple contingency feature.
• Chapter 11 (page 266) describes subvolume-level and file-level replication.
• Chapter 12 (page 271) describes how to use the mapfile, maplog, and updater configuration
record to support mapping between primary system and backup system subvolumes.
• Chapter 13 (page 276) describes support for auxiliary audit trails.
• Chapter 14 (page 279) describes support for network transactions.
• Chapter 15 (page 292) describes lockstep operation.
• Chapter 16 (page 307) describes SQL/MX database setup for RDF.
• Chapter 17 (page 320) describes the Zero Lost Transactions (ZLT) functional capability.
• Appendix A (page 330) summarizes the syntax of all RDFCOM and RDFSCAN commands.
• Appendix B (page 340) provides additional information about RDF, including reserved words,
default values for configuration parameters, and system file descriptions.
• Appendix C (page 346) lists all messages that can be generated by the lockstep gateway, RDF
processes, RDFCOM, and RDFSCAN, and their probable causes, effects, and recovery actions.
• Appendix D (page 479) lists all the operational limits that apply to the RDF/IMP, IMPX, and
ZLT products.
• Appendix E (page 480) describes how to monitor RDF entities using ASAP.
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in
brackets are required. For example:
filename
Computer Type
Computer type letters indicate:
• C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:
Use the cextdecs.h header file.
• Text displayed by the computer. For example:
Last Logon: 14 May 2006, 08:02:23
• A listing of computer code. For example
if (listen(sock, 1) < 0)
{
perror("Listen Error");
Notation Conventions 21