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

Applications: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
13-5
PATHMON States
PATHCOM responds with output such as:
This output provides information about the number of Pathway processes and
servers that are running, stopped, and so forth.
4. To check the state of the PATHMON process within the Pathway environment and
its status for your application:
= STATUS PATHMON
PATHCOM responds with output such as:
PATHMON States
The status of the PATHMON process can be either STARTING or RUNNING:
•
STARTING indicates that a system load or cool start has not finished.
•
RUNNING indicates that a system load or cool start has finished.
The other elements of the STATUS PATHMON output are:
•
CPUS shows the number of the primary and backup processors in which the
PATHMON process is running. If the backup PATHMON process is not running,
the second number is blank.
•
PATHCTL, LOG1, and LOG2 contain information about the PATHMON control file
and the logging files.
•
The REQNUM column contains the PATHMON internal identifiers of application
requesters that are currently running in this environment.
•
The FILE column identifies the type of requester.
RUNNING
EXTERNALTCPS 0
LINKMONS 0
PATHCOMS 1
SPI 1
FREEZE
RUNNING STOPPED THAWED FROZEN PENDING
SERVERCLASSES 13 5 18 0 0
RUNNING STOPPED PENDING
SERVERPROCESSES 13 40 0
TCPS 1 0 0
RUNNING STOPPED PENDING SUSPENDED
TERMS 1 0 0 0
PATHMON -- STATE=RUNNING CPUS 6:1
PATHCTL (OPEN) $GROG.VIEWPT.PATHCTL
LOG1 SE (OPEN) $0
LOG2 (CLOSED)
REQNUM FILE PID PAID WAIT
1 PATHCOM $Y622 8,001
2 TCP $Y898










