NonStop NS-Series Operations Guide (H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Guide
- 1 Introduction to Integrity NonStop NSSeries Operations
- When to Use This Section
- Understanding the Operational Environment
- What Are the Operator Tasks?
- Monitoring the System and Performing Recovery Operations
- Preparing for and Recovering from Power Failures
- Stopping and Powering Off theSystem
- Powering On and Starting the System
- Creating Startup and Shutdown Files
- Performing Preventive Maintenance
- Operating Disk Drives and Tape Drives
- Responding to Spooler Problems
- Updating Firmware
- Determining the Cause of a Problem: A Systematic Approach
- Logging On to an Integrity NonStop Server
- Service Procedures
- 2 Determining Your System Configuration
- 3 Overview of Monitoring and Recovery
- 4 Monitoring EMS Event Messages
- 5 Processes: Monitoring and Recovery
- 6 Communications Subsystems: Monitoring and Recovery
- 7 ServerNet Resources: Monitoring and Recovery
- 8 I/O Adapters and Modules: Monitoring and Recovery
- 9 Processors and Components: Monitoring and Recovery
- When to Use This Section
- Overview of the NonStop Blade Complex
- Monitoring and Maintaining Processors
- Identifying Processor Problems
- Recovery Operations for Processors
- Recovery Operations for a Processor Halt
- Halting One or More Processors
- Reloading a Single Processor on a Running Server
- Recovery Operations for a System Hang
- Enabling/Disabling Processor and System Freeze
- Freezing the System and Freeze-Enabled Processors
- Dumping a Processor to Disk
- Backing Up a Processor Dump to Tape
- Replacing Processor Memory
- Replacing the Processor Board and Processor Entity
- Submitting Information to Your Service Provider
- Related Reading
- 10 Disk Drives: Monitoring and Recovery
- 11 Tape Drives: Monitoring and Recovery
- 12 Printers and Terminals: Monitoring and Recovery
- 13 Applications: Monitoring and Recovery
- 14 Power Failures: Preparation and Recovery
- 15 Starting and Stopping the System
- When to Use This Section
- Powering On a System
- Starting a System
- Minimizing the Frequency of Planned Outages
- Stopping Application, Devices, and Processes
- Stopping the System
- Powering Off a System
- Troubleshooting and Recovery Operations
- Fans Are Not Turning
- System Does Not Appear to Be Powered On
- Green LED Is Not Lit After POSTs Finish
- Amber LED on a Component Remains Lit After the POST Finishes
- Components Fail When Testing the Power
- Recovering From a System Load Failure
- Getting a Corrupt System Configuration File Analyzed
- Recovering From a Reload Failure
- Exiting the OSM Low-Level Link
- Opening Startup Event Stream and Startup TACL Windows
- Related Reading
- 16 Creating Startup and Shutdown Files
- Automating System Startup and Shutdown
- Processes That Represent the System Console
- Example Command Files
- CIIN File
- Writing Efficient Startup and Shutdown Command Files
- How Process Persistence Affects Configuration and Startup
- Tips for Startup Files
- Startup File Examples
- Tips for Shutdown Files
- Shutdown File Examples
- 17 Preventive Maintenance
- A Operational Differences Between Systems Running GSeries and HSeries RVUs
- B Tools and Utilities for Operations
- When to Use This Appendix
- BACKCOPY
- BACKUP
- Disk Compression Program (DCOM)
- Disk Space Analysis Program (DSAP)
- EMSDIST
- Event Management Service Analyzer (EMSA)
- File Utility Program (FUP)
- Measure
- MEDIACOM
- NonStop NET/MASTER
- NSKCOM and the Kernel-Managed Swap Facility (KMSF)
- OSM Package
- PATHCOM
- PEEK
- RESTORE
- SPOOLCOM
- Subsystem Control Facility (SCF)
- HP Tandem Advanced Command Language (TACL)
- TMFCOM
- Web ViewPoint
- ViewPoint
- ViewSys
- C Related Reading
- D Converting Numbers
- Safety and Compliance
- Index
Creating Startup and Shutdown Files
HP Integrity NonStop NS-Series Operations Guide—529869-001
16-4
Processes That Represent the System Console
Processes That Represent the System
Console
On Integrity NonStop NS-series servers, the system console is a pair of windows on a
LAN-connected system console. It is represented by the processes $YMIOP.#CLCI
and $YMIOP.#CNSL, and the home terminal is represented by the $ZHOME process
pair.
$YMIOP.#CLCI
$YMIOP.#CLCI is the primary interactive terminal for the operator interface to the
system.
This process:
•
Runs on the system console
•
Is preconfigured on your system during system generation
TACL processes are started on $YMIOP.#CLCI by commands in the CIIN file. If a read
operation is pending, such as a TACL prompt on $YMIOP.#CLCI, write operations are
blocked, causing the process attempting the write operation to wait indefinitely.
$YMIOP.#CNSL
$YMIOP.#CNSL is a write-only device for logging.
This process:
•
Runs on the system console
•
Is preconfigured on your system during system generation
$ZHOME
The $ZHOME process is a process pair that provides a reliable home terminal to which
processes can perform write operations. The $ZHOME process can be used by
processes that must write to the system console but do not require a response.
$ZHOME is preconfigured on your system by the CONFBASE file. $ZHOME is a
generic process that is part of the SCF Kernel subsystem. Note the following about the
configuration of $ZHOME:
•
The $ZHOME process is configured with $YMIOP.#CLCI as its HOMETERM,
INFILE, and OUTFILE.
•
Because $ZHOME acts as a reliable home terminal designed to interact with the
system console, $YMIOP.#CLCI, HP recommends that you do not change its
configuration. Most important:
°
Do not specify $ZHOME for the INFILE, OUTFILE, or HOMETERM for the
$ZHOME process.










