RDF System Management Manual for H-Series RVUs (RDF 1.8)

• Chapter 15 (page 289) describes lockstep operation.
• Chapter 16 (page 295) describes SQL/MX database setup for RDF.
• Chapter 17 (page 309) describes the Zero Lost Transactions (ZLT) functional capability.
• Appendix A (page 319) summarizes the syntax of all RDFCOM and RDFSCAN commands.
• Appendix B (page 329) provides additional information about RDF, including reserved
words, default values for configuration parameters, and system file descriptions.
• Appendix C (page 335) 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 437) lists all the operational limits that apply to the RDF/IMP, IMPX, and
ZLT products.
• Appendix E (page 439) 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");
exit(-1);
}
Bold Text
Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED: 123.00
The user must press the Return key after typing the input.
[ ] Brackets
Brackets enclose optional syntax items. For example:
TERM [\system-name.]$terminal-name
Notation Conventions 29