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

Overview of Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
3-16
Automating Routine System Monitoring
Automating Routine System Monitoring
You can automate many of the monitoring procedures. Automation saves you time and
helps you to perform many routine tasks more efficiently.
Your operations environment might be using TACL macros, TACL routines, or
command files to perform routine system monitoring and other tasks. These items
allow you to run many procedures so that you can quickly determine system status,
produce reports, or perform other common tasks. The TACL Reference Manual
contains an example that you can adapt to automate system monitoring.
Example 3-2 contains an example of a command file you can use or adapt to check
many of the system elements:
1. To create a command file named SYSCHK that will automate system monitoring,
type the text shown in Example 3-2 into an EDIT file.
2. After you create this file, at a TACL prompt, type this command to execute the file
and automatically monitor many elements of your system:
> OBEY SYSCHK
For an example of the output that is sent to your home terminal when you execute a
command file such as SYSCHK, refer to Example 3-3. This output shows that all
elements of the system being monitored are up and running normally.
Example 3-2. System Monitoring Command File
COMMENT THIS IS THE FILE SYSCHK
COMMENT THIS CHECKS ALL DISKS:
SCF STATUS DISK $*
COMMENT THIS CHECKS ALL TAPE DRIVES:
SCF STATUS TAPE $*
COMMENT THIS CHECKS THE SPOOLER PRINT DEVICES:
SPOOLCOM DEV
COMMENT THIS CHECKS THE LINE HANDLERS:
SCF STATUS LINE $*
COMMENT THIS CHECKS THE STATUS OF TMF:
TMFCOM;STATUS TMF
COMMENT THIS CHECKS THE STATUS OF PATHWAY:
PATHCOM $ZVPT;STATUS PATHWAY;STATUS PATHMON
COMMENT THIS CHECKS ALL SACS:
SCF STATUS SAC $*
COMMENT THIS CHECKS ALL ADAPTERS
SCF STATUS ADAPTER $*
COMMENT THIS CHECKS ALL LIFS
SCF STATUS LIF $*
COMMENT THIS CHECKS ALL PIFS
SCF STATUS PIF $*










