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

Determining Your System Configuration
HP Integrity NonStop NS-Series Operations Guide—529869-001
2-15
Displaying Configuration Information—SCF
Examples
Displaying Configuration Information—SCF Examples
These examples show SCF commands that display subsystem configuration
information, along with the information that is returned. These commands are not
preceded by an ASSUME command.
To display all the processes running in the Kernel subsystem:
-> INFO PROC $ZZKRN.#*
The system displays a listing similar to that shown in Example 2-3:
To display a list of all SAC names with their associated owners and access lists:
-> info sac $zzlan.*
The system displays a listing similar to that shown in Example 2-4
:
Example 2-3. SCF INFO PROCESS Command Output
32-> INFO PROCESS $ZZKRN.#*
NONSTOP KERNEL - Info PROCESS \DRP09.$ZZKRN
Symbolic Name *Name *Autorestart *Program
CLCI-TACL $CLCI 10 $SYSTEM.SYSTEM.TACL
OSM-APPSRVR $ZOSM 10 $SYSTEM.SYSTEM.APPSRVR
OSM-CIMOM $ZCMOM 5 $SYSTEM.SYSTEM.CIMOM
OSM-CONFLH-RD $ZOLHI 0 $SYSTEM.SYSTEM.TACL
OSM-OEV $ZOEV 10 $SYSTEM.SYSTEM.EVTMGR
QATRAK $TRAK 10 $SYSTEM.SYSTOOLS.QATRACK
QIOMON $ZMnn 10 $SYSTEM.SYSTEM.QIOMON
ROUT $ZLnn 10 $SYSTEM.SYSTEM.ROUT
SCP $ZNET 10 $SYSTEM.SYSTEM.SCP
SP-EVENT $ZSPE 5 $SYSTEM.SYSTEM.ZSPE
TFDSHLP $ZTHnn 10 $SYSTEM.SYSTEM.TFDSHLP
ZEXP $ZEXP 10 $SYSTEM.SYSTEM.OZEXP
ZHOME $ZHOME 10 $SYSTEM.SYSTEM.ZHOME
ZLOG $ZLOG 5 $SYSTEM.SYSTEM.EMSACOLL
ZSLM2 $ZSLM2 10 $SYSTEM.SYSTEM.TZSLM2
ZZKRN $ZZKRN 10 $SYSTEM.SYSTEM.OZKRN
ZZLAN $ZZLAN 10 $SYSTEM.SYSTEM.LANMAN
ZZSTO $ZZSTO 10 $SYSTEM.SYSTEM.TZSTO
ZZWAN $ZZWAN 10 $SYSTEM.SYSTEM.WANMGR
Example 2-4. SCF INFO SAC Command Output
-> INFO SAC $ZZLAN.*
SLSA Info SAC
Name Owner *Access List
$ZZLAN.E4SA0.0 3 (3,2,1,0)
$ZZLAN.E4SA0.1 3 (3,2,1,0)
$ZZLAN.E4SA52.0 0 (0,1)
$ZZLAN.E4SA52.1 0 (0,1)
$ZZLAN.FESA0.0 0 (0,1,2,3,4,5,6,7)










