NonStop NS-Series Operations Guide (H06.12+)

• “Monitoring EMS Event Messages” (page 69)
• “ Processes: Monitoring and Recovery” (page 71)
• “Communications Subsystems: Monitoring and Recovery” (page 77)
• “ServerNet Resources: Monitoring and Recovery” (page 89)
• “ I/O Adapters and Modules: Monitoring and Recovery” (page 97)
• “Processors and Components: Monitoring and Recovery” (page 103)
• “Disk Drives: Monitoring and Recovery” (page 121)
• “Tape Drives: Monitoring and Recovery” (page 135)
• “Printers and Terminals: Monitoring and Recovery” (page 143)
• “Applications: Monitoring and Recovery” (page 145)
• “Power Failures: Preparation and Recovery” (page 151)
• “Starting and Stopping the System ” (page 155)
• “Creating Startup and Shutdown Files” (page 173)
• “Preventive Maintenance” (page 191)
• “Operational Differences Between Systems Running G-Series and H-Series RVUs” (page 195)
• “Tools and Utilities for Operations” (page 197)
• “Related Reading” (page 201)
• “Converting Numbers” (page 205)
• Safety and Compliance
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:
file-name
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
20