NonStop Operations Guide for H-Series and J-Series RVUs

6 Processes: Monitoring and Recovery
“When to Use This Chapter” (page 79)
“Types of Processes” (page 79)
“System Processes” (page 79)
“CIP Processes” (page 80)
“I/O Processes (IOPs)” (page 79)
“Generic Processes” (page 80)
“Monitoring Processes” (page 80)
“Monitoring System Processes” (page 81)
“Monitoring IOPs” (page 82)
“Monitoring CIP Processes” (page 82)
“Monitoring Generic Processes” (page 82)
“Recovery Operations for Processes” (page 84)
“Related Reading for Processes” (page 84)
When to Use This Chapter
This chapter provides basic information about the different types of processes for NonStop systems.
It gives a brief example of monitoring each type of process and provides information about the
commands available for recovery operations.
Types of Processes
Three types of processes are of major concern to a system operator of NonStop NS-series systems
and NonStop BladeSystems:
“System Processes” (page 79)
“I/O Processes (IOPs)” (page 79)
“CIP Processes” (page 80)
“Generic Processes” (page 80)
System Processes
A system process is a privileged process that is created during system load and exists continuously
for a given configuration for as long as the processor remains operable. Examples of system
processes include the memory manager, the monitor, and the I/O control processes.
I/O Processes (IOPs)
An I/O process (IOP) is a system process that manages communications between a processor and
I/O devices. IOPs are often configured as fault-tolerant process pairs, and they typically control
one or more I/O devices or communications lines. Each IOP is configured in a maximum of two
processors, typically a primary processor and a backup processor.
An IOP provides an application program interface (API) that allows access to an I/O interface. A
wide area network (WAN) communications line is an example of an I/O interface. IOPs configured
using the SCF interface to the WAN subsystem manage the input and output functions for the
When to Use This Chapter 79