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-2
Monitoring the Status of TMF
Monitoring the Status of TMF
To monitor TMF using TMFCOM:
1. At a TACL prompt:
> TMFCOM
2. At the TMFCOM prompt:
~ STATUS TMF
A TMFCOM report summarizing the current activity of the TMF subsystem, audit
trails, and the audit dump and catalog processes is displayed. For example:
For an explanation of the TMF state in this display, see TMF States on page 13-3.
Monitoring Data Volumes
To display information about the data volumes for which the TMF subsystem generates
audit records on behalf of transactions performed on those volumes, at a TMFCOM
prompt, type:
~ STATUS DATAVOLS
To control which volumes are displayed, use the STATE, AUDITTRAIL, and
RECOVERYMODE parameters.
The normal operating state for a data volume is STARTED, which indicates that the
volume is ready to process TMF transactions. Audited requests are allowed for data
volumes in this state only where transaction processing is enabled within the
subsystem.
Note. The STATUS TMF command presents status information about the audit dump,
audit trail, and catalog processes. Thus, in addition to the general TMF information, the
STATUS TMF command combines information from the STATUS AUDITDUMP, STATUS
AUDITTRAIL, and STATUS BEGINTRANS commands. However, information from the
other STATUS commands (STATUS DATAVOLS, STATUS OPERATIONS, STATUS
SERVER, and STATUS TRANSACTION) does not appear in the STATUS TMF display.
TMF Status:
System: \SAGE, Time: 6-Jul-1994 11:08:06
State: Started
Transaction Rate: 0.10 TPS
AuditTrail Status:
Master:
Active audit trail capacity used: 55%
First pinned file: $MAT1.ZTMFAT.AA000044
Reason: Active transaction(s).
Current file: $MAT1.ZTMFAT.AA000045
AuditDump Status:
Master: State: enabled, Status: active, Process $X545,
File: $MAT2.ZTMFAT.AA000042
BeginTrans Status: Enabled
Catalog Status:
Status: Up










