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-8
If a CIIN File Is Not Specified or Enabled in OSM
If a CIIN File Is Not Specified or Enabled in OSM
The results of the startup TACL process varies depending on whether a CIIN file is
specified in the CONFTEXT file and whether the CIIN option is enabled.
CONFTEXT CIIN Entry
and CIIN File
CIIN
Option Results
1. CONFTEXT has CIIN
entry, and file is
available in specified
location.
Enabled CIIN is executed by initial (startup) TACL process.
Upon completion, this TACL process terminates.
You must log on to a different TACL process (the
TACL process on $YMIOP.#CLCI started by the
CIIN file) to complete the system startup process.
2. CONFTEXT has CIIN
entry, and file is
available in specified
location, but file is
empty or aborts
because of syntax
errors before another
TACL process is
started.
Enabled CIIN is executed by initial (startup) TACL process.
Upon completion, this TACL process terminates,
leaving no TACL process available. You must reload
the system with the CIIN option disabled in the
System Startup dialog box invoked from the OSM
Low-Level Link; then log on and correct the CIIN file.
Then, either enable the CIIN option, using the
System Startup dialog box, and reload; or complete
the system startup process manually.
3. CONFTEXT has CIIN
entry, but file is not
available in specified
location.
Enabled Initial TACL process is started and left in logged-off
state. You must log on to complete the system
startup process.
4. CONFTEXT has CIIN
entry.
Disabled Initial TACL process is started and left in logged-off
state. You must log on to complete the system
startup process.
5. CONFTEXT has no
CIIN entry.
Enabled
or
disabled
Initial TACL process is started and left logged on to
the super ID (255,255). You must initiate the
remainder of the system startup process manually
and then log off.
Caution. Situation 5 presents a security issue: the initial TACL process is left logged on to the
super ID (255,255). You must either immediately continue with the system startup process (as
described in the Results column), log on to another user ID, or log off.