OVNM 5.3 - Operations Agent for NonStop Object Configuration Client Guide

Appendix A: Subsystems Managed 77
Appendix A: Subsystems Managed
OCC allows you to monitor most of the major HP NonStop subsystems. A list of all the predefined subsystems
managed by OCC is as follows:
NOTE:
The BASE24, MQ-SERIES and TELCO subsystems will not be enabled in OCC by default. These
subsystems will be ac
tivated only when the corresponding plug-ins have been installed.
1. ATP6100
The ATP6100 subsystem consists of the ATP6100 line-handler process and a protocol module. The
ATP6100 line-handler process is a HP NonStop™ process pair running in a HP NonStop™ host. The
process acts as a file-system interface between an application and a protocol module that resides and runs
in the Communication Line Interface Process (CLIP) as a task. In the wide area network (WAN) subsystem
that uses the SWAN concentrator, the ATP6100 line-handler process thus allows communication over a
variety of asynchronous communication devices especially terminals and printers. Application data is
passed to one of several protocol modules by ATP6100. The protocol module gives the application
extensive control over the line, and each protocol module can control either a single line or multiple lines.
2. BASE24
BASE24 is a major ATM application available from ACI. This software is used by most of the world’s major
banking institutions for their credit card transactions. The counters/modifiers defined under this subsystem
help monitor and manage various objects like LINE, LINK, PROCESS, STATION, SYSTEM and TDF-60. The
PNA24 module is used for discovery and recovery of the BASE24 objects and is included in the base
product. This greatly increases the Out-of-the-Box capabilities of OCC, especially regarding a major
application such as BASE24. The BASE24 subsystem will only be available if you have installed the
BASE24 plug-in.
3. CP6100
The CP6100 subsystem consists of the CP6100 input-output process (IOP) and a protocol module. The
CP6100 IOP, also known as the CP6100 Communication Access Process (CAP), is a NonStop™ process
pair running in a NonStop™ host. The process acts as a file-transfer mechanism to move data between an
application and a protocol module that resides and runs in the Communication Line Interface Process (CLIP)
as a task. The protocol module is a microcode file or a download module (DLM) that contains OSI Layer-1
and Layer-2 processing tasks. The CP6100 CAP thus provides the application with a data-link level
interface to asynchronous, byte-synchronous, or bit-synchronous protocol modules in a 6100
Communication Subsystem (CSS), which uses the ServerNet Wide Area Network (SWAN) concentrator.
Application data is passed to one of several protocol modules by CP6100. The protocol module gives the
application extensive control over the line, and each protocol module can control either a single line or
multiple lines.
4. CPU
This subsystem manages and controls one of the major components of the system, the CPU. The
counters/modifiers predefined for this subsystem greatly facilitate the monitoring and recovery of all the
CPUs’ for the HP NonStop node.
5. DISK
Another major component of a system is the Disk subsystem. The predefined disk counters/modifiers help in
managing, monitoring and recovering this complex and major subsystem on the HP NonStop platform.
6. EMS
EMS is the subsystem that handles EVENTS on a HP NonStop node. The counters/modifiers defined for this
subsystem allow the customer to easily monitor and react to any kind of event generated on a HP NonStop
system. The EMS management feature allows the user to trigger actions based on EMS events. This feature
allows the customer to define HP NonStop subsystem generated events as well as user-application
generated events for escalation and automation. Additional slot values as they are known, can also be
added for the HP Operations environment. Any EMS or Non-EMS event can be automated via Gateway
processes or by simple TACL macro commands.