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-14
System Startup File
Comment -- If you have used SCF to start a persistent $ZEXP Expand
Comment -- manager process pair, you do not need an explicit SCP
Comment -- command to start $ZEXP, unless you load the system from a
Comment -- different CONFIG file.
Comment -- If you have not configured $ZEXP as a persistent generic
Comment -- process,remove the commenting from the following SCP
Comment -- command and start $ZEXP as a nonpersistent process pair.
Comment -- OZEXP / NAME $ZEXP, NOWAIT, PRI 180, OUT $ZHOME, CPU 0/1
comment -- Warm start the spooler subsystem using the SPOOLCOM command
comment -- file SPLWARM
OBEY $SYSTEM.STARTUP.SPLWARM
comment -- Start the Transaction Management Facility (TMF) subsystem
comment -- using the TMFCOM command file TMFSTART
TMFCOM / IN $SYSTEM.STARTUP.TMFSTART, OUT $ZHOME /
comment -- Configure and start the TCP/IP stacks on the LAN adapter ports
comment -- used by the SWAN
OBEY $SYSTEM.STARTUP.IPSTK*
comment -- Start the CP6100 lines on the SWAN
SCF / IN $SYSTEM.STARTUP.STRTCP6, OUT $ZHOME /
comment -- Start the ATP6100 lines on the SWAN
SCF / IN $SYSTEM.STARTUP.STRTATP, OUT $ZHOME /
comment -- Start the X.25 lines on the SWAN
SCF / IN $SYSTEM.STARTUP.STRTX25, OUT $ZHOME /
comment -- Start the printers on the SWAN
SCF / IN $SYSTEM.STARTUP.STRTLP, OUT $ZHOME /
comment -- Start the Expand-over-IP line to \Case2
SCF / IN $SYSTEM.STARTUP.IP2CASE2, OUT $ZHOME /
comment -- Start the direct-connect line
SCF / IN $SYSTEM.STARTUP.STRTLH, OUT $ZHOME /