Documentation Updates
This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in problem list entry (PLE)19221172. To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support Web site:
http://www.support.unisys.com/all/ple/19221172
Note: If you are not logged into the Product Support site, you will be asked to do so.
Overview
This section summarizes key functional aspects of using Operations Sentinel to monitor and control MCP host systems. Read this section before managing MCP host systems with Operations Sentinel.
This section contains the following subjects:
Overview of Operations Sentinel (see 1.1)
Overview of Operations Sentinel Interface for MCP (see 1.2)
Software and hardware requirements (see 1.3)
Operator interface (see 1.4)
Using SP-AMS to monitor MCP systems (see 1.5)
Using Operations Sentinel to monitor MCP systems (see 1.6)
Application Program Interface (API) library (see 1.7)
Configuration File and Filter File (see 1.8)
Interface start-up and recovery (see 1.9)
Connection timeout alarm (see 1.10)
Responding to alarms raised by Operations Sentinel (see 1.11)
Configuring resilient Operations Sentinel servers (see 1.12)
The primary audience for this guide is the staff who installs and configures the software for managing MCP host systems.
Notation Conventions
This guide uses the following conventions:
Variable names for which you must supply values appear in italics. For example: internet–address.
Italicized words can also be variables in a string. These variables are defined by the user or sometimes by the operating system.
Brackets ( [ ] ) enclose parts of statements (phrases) that are optional.
Braces ( { } ) group similar information in which one of the values is required.
The separator symbol ( | ) indicates that the item following the symbol is an alternative to the item preceding it.