Operations Sentinel Status User Guide - Public Support Login - Unisys

ClearPath Enterprise
Servers
Operations Sentinel
Status
User Guide
Operations Sentinel Level 9.0
Printed in USA
April 2005 7833 4778–008

ClearPath Enterprise
Servers
Operations Sentinel
Status
User Guide
© 2005 Unisys Corporation.
All rights reserved.
Operations Sentinel Level 9.0
Printed in USA
April 2005 7833 4778–008
UNISYS

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information
described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to
purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the
products described in this document are set forth in such agreement. Unisys cannot accept any financial or other
responsibility that may be the result of your use of the information in this document or software material, including
direct, special, or consequential damages.
You should be very careful to ensure that the use of this information and/or software material complies with the laws,
rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice. Revisions may be issued to advise of such
changes and/or additions.
Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at
private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard
commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data
rights clauses.
Correspondence regarding this publication can be e-mailed to doc@unisys.com.
Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries.
All other brands and products referenced in this document are acknowledged to be the trademarks or registered
trademarks of their respective holders.

ClearPath Enterprise
Servers
Operations Sentinel
Status
User Guide
Operations Sentinel
Level 9.0
ClearPath
Enterprise
Servers
Operations
Sentinel
Status
User Guide
Operations
Sentinel
Level 9.0
7833 4778–008 7833 4778–008
Bend here, peel upwards and apply to spine.

Contents
Section 1. Introduction to Single Point Operations Status
1.1. Description of Status ............................................................... 1–4
1.1.1. How Status Works .......................................................... 1–4
1.1.2. Availability of Status ........................................................ 1–6
1.1.3. Menu Structure ............................................................... 1–7
1.2. Introduction to Components.................................................... 1–8
1.2.1. Component Attributes..................................................... 1–8
1.2.2. Component Classes ........................................................ 1–8
1.2.3. Event Reports.................................................................. 1–9
1.2.4. Shared Components ..................................................... 1–10
1.2.5. How Components Are Identified .................................. 1–10
1.2.6. Creating Components ................................................... 1–11
1.2.7. Component Groups....................................................... 1–11
1.2.8. Instruction and Note Files ............................................. 1–11
1.2.9. Alarms ........................................................................... 1–12
1.2.10. External Applications..................................................... 1–12
Section 2. Getting Started
2.1. Operating Considerations ........................................................ 2–2
2.1.1. Event Report Considerations .......................................... 2–2
2.1.2. Event Report Value Pairs................................................. 2–2
2.1.3. Tape Monitor for OS 2200 and MCP Systems
[OS 2200 MCP] .......................................................... 2–4
2.1.4. OS 2200 Considerations [OS 2200] .............................. 2–5
2.1.5. MCP Considerations [MCP] .......................................... 2–6
2.1.6. UNIX Systems Considerations [UNIX] .......................... 2–7
2.1.7. Windows Considerations [Windows]............................ 2–7
2.1.8. Summary of Status Information Sources........................ 2–8
2.2. Preparing to Use Status ........................................................... 2–9
2.2.1. Preliminary Steps ............................................................ 2–9
2.2.2. Configuring Status......................................................... 2–10
2.3. Setting Up Status................................................................... 2–12
2.3.1. Classifications................................................................ 2–12
2.3.2. Icon Files ....................................................................... 2–13
2.3.3. Resource Sets ............................................................... 2–15
2.3.4. Configurations ............................................................... 2–15
2.3.5. Users ............................................................................. 2–15
2.3.6. Diagram Definitions....................................................... 2–15
7833 4778–008 iii

Contents
2.3.7. Component Sets ............................................................2–17
2.4. Starting and Terminating Status .............................................2–19
2.4.1. Starting Status from Single Point Operations
Console......................................................................2–19
2.4.2. Starting Status Independently of Single Point
Operations Console ...................................................2–20
2.4.3. Automatic Environment Setup on Initialization ..............2–21
2.4.4. Terminating Status.........................................................2–21
2.5. Changing the Status Environment..........................................2–22
2.5.1. Selecting a Different Classification ................................2–22
2.5.2. Selecting a Different Configuration................................2–22
2.5.3. Selecting a Different Resource Set ...............................2–23
2.5.4. Selecting a Different Trace Level...................................2–24
Section 3. Status Displays
3.1. Status Windows .......................................................................3–2
3.1.1. Window Features.............................................................3–2
3.2. Status Diagram .........................................................................3–3
3.2.1. Icon Descriptions .............................................................3–3
3.2.2. How the Status Diagram Is Updated ...............................3–5
3.2.3. Operator Action................................................................3–6
3.2.4. Pull-Down Menus ............................................................3–7
3.2.5. Window Backgrounds......................................................3–9
3.3. Subgroup Windows ................................................................3–10
3.3.1. Pull-Down Menus ..........................................................3–10
3.4. Component Tables..................................................................3–11
3.4.1. Component Group Tables ..............................................3–11
3.4.2. Components with Unexpected Values Table.................3–14
3.4.3. Components with Notes Table ......................................3–15
3.4.4. Unreported Components Table .....................................3–16
3.4.5. Identical Components Table ..........................................3–17
3.5. Attribute List ...........................................................................3–19
3.5.1. Displaying an Attribute List ............................................3–20
3.5.2. Attribute List Menus ......................................................3–21
3.5.3. Initiating Actions ............................................................3–21
3.5.4. Deleting Components ....................................................3–22
3.6. Dialog Windows......................................................................3–23
3.6.1. Entering Information ......................................................3–23
3.6.2. Dialog Window Buttons .................................................3–23
Section 4. Component Attributes
4.1. Types of Attributes ...................................................................4–2
4.1.1. Reported and Specified Attributes...................................4–2
4.1.2. Attribute Data Types ........................................................4–2
4.1.3. Status Attributes ..............................................................4–3
4.1.4. String Attributes...............................................................4–4
4.1.5. Numeric Attributes...........................................................4–4
4.1.6. List Attributes ..................................................................4–5
4.2. Attributes That Apply to All Component Classes .....................4–6
iv 7833 4778–008

Contents
4.2.1. Name............................................................................... 4–6
4.2.2. Host................................................................................. 4–6
4.2.3. Class................................................................................ 4–6
4.2.4. Exceptions....................................................................... 4–6
4.2.5. Seen ................................................................................ 4–7
4.2.6. Notes............................................................................... 4–7
4.2.7. Message.......................................................................... 4–8
4.2.8. Event Report Time .......................................................... 4–8
4.2.9. Event Received ............................................................... 4–9
4.2.10. User Defined ................................................................... 4–9
4.2.11. Groups............................................................................. 4–9
4.2.12. Component Scope........................................................... 4–9
4.2.13. Identical Components ................................................... 4–10
4.3. Site-Defined Attributes .......................................................... 4–11
4.3.1. Site-Defined Status Attributes ...................................... 4–11
4.3.2. Site-Defined Numeric Attributes ................................... 4–12
4.3.3. Site-Defined String Attributes ....................................... 4–13
4.4. Attributes Specific to the OS 2200 Host Component
Class [OS 2200] ............................................................... 4–14
4.4.1. Exec Level ..................................................................... 4–14
4.4.2. Site-Id ............................................................................ 4–14
4.4.3. Data Collection .............................................................. 4–14
4.4.4. Connected Consoles ..................................................... 4–15
4.4.5. System Type ................................................................. 4–15
4.4.6. Application Initialization ................................................. 4–16
4.5. Attributes Specific to the OS 2200 Console
Component Class [OS 2200] ........................................... 4–17
4.5.1. Monitor.......................................................................... 4–17
4.5.2. Connected to Application .............................................. 4–17
4.5.3. Connected to Host ........................................................ 4–17
4.5.4. Connected Host ............................................................ 4–18
4.6. Attributes Specific to the MCP Host Class [MCP]............... 4–19
4.6.1. Monitor.......................................................................... 4–19
4.6.2. Connected to Application .............................................. 4–19
4.6.3. Data Collection .............................................................. 4–19
4.6.4. Host Agent Active ......................................................... 4–20
4.6.5. Application Initialization ................................................. 4–20
4.7. Attributes Specific UNIX Host Class [UNIX] ........................ 4–22
4.7.1. Monitor.......................................................................... 4–22
4.7.2. Connected to Application .............................................. 4–22
Section 5. Diagram Definitions
5.1. Defining Component Groups ................................................... 5–2
5.1.1. Define Groups Tables...................................................... 5–2
5.1.2. Capabilities ...................................................................... 5–3
5.1.3. Changing a Group Name ................................................. 5–3
5.1.4. Changing a Group Label .................................................. 5–3
5.1.5. Selecting Icons ................................................................ 5–4
5.1.6. Positioning Icons ............................................................. 5–5
5.1.7. Changing the Component Group Table Template........... 5–6
7833 4778–008 v

Contents
5.1.8. Specifying Components to Be Included in a
Group ...........................................................................5–7
5.1.9. Defining Subgroups .........................................................5–8
5.1.10. Adding New Component Groups.....................................5–9
5.1.11. Copying a Component Group ..........................................5–9
5.1.12. Deleting Existing Component Groups .............................5–9
5.1.13. Adding Default Groups for a Selected Host...................5–10
5.1.14. Deleting Default Groups for a Selected Host ................5–11
5.1.15. Moving Default Groups for a Selected Host..................5–11
5.1.16. Adding Default Groups for Each Host and Class ...........5–11
5.1.17. Adding Host-Independent Component Groups
for All Component Classes ........................................5–12
5.1.18. Changing the Background..............................................5–12
5.1.19. Changing the Label Color...............................................5–13
5.1.20. Changing the Title ..........................................................5–13
5.2. Defining Component Table Templates...................................5–15
5.2.1. Changing the Screen Size of a Table Template .............5–17
5.2.2. Changing the Display Behavior of a Table
Template....................................................................5–18
5.2.3. Changing the Class Associated with a Table
Template....................................................................5–18
5.2.4. Changing the Attribute Columns in a Table
Template....................................................................5–18
5.2.5. Adding New Component Group Table Templates.........5–19
5.2.6. Deleting Existing Component Group Table
Templates ..................................................................5–20
5.2.7. Selecting a Different Component Group Table
Template as the Default ............................................5–20
5.3. Saving a Diagram Definition ...................................................5–21
5.3.1. Replacing the Current Diagram Definition .....................5–21
5.3.2. Saving a New Diagram Definition ..................................5–21
5.4. Deleting Diagram Definitions..................................................5–22
5.5. Changing the Diagram Definition in Use ................................5–23
Section 6. Component Sets
6.1. Defining Components Explicitly................................................6–2
6.1.1. Edit Components Table....................................................6–2
6.1.2. Changes You Can Make to Component
Definitions....................................................................6–3
6.1.3. Indicating Whether a Component Was Explicitly
Defined ........................................................................6–3
6.1.4. Specifying the Scope of a Component ............................6–3
6.1.5. Specifying the Instruction File..........................................6–4
6.1.6. Specifying Expected or Alarm Values for Status
Attributes .....................................................................6–4
6.1.7. Specifying Minimum and Maximum Threshold
Values ..........................................................................6–5
6.1.8. Defining New Components .............................................6–5
6.1.9. Deleting Components ......................................................6–5
vi 7833 4778–008

Contents
6.1.10. Defining Components for a Different Host or
Class............................................................................ 6–6
6.2. Saving Component Set Definitions.......................................... 6–7
6.2.1. Saving a New Component Set Definition ....................... 6–7
6.2.2. Replacing a Component Set Definition ........................... 6–7
6.3. Deleting Component Set Definitions ....................................... 6–9
6.4. Retrieving a Component Set.................................................. 6–10
Section 7. Defining Classifications
7.1. Status Configuration Overview................................................ 7–2
7.2. Defining Status Classifications................................................. 7–3
7.2.1. Creating or Editing a Classification.................................. 7–3
7.2.2. Selecting a Different Classification ................................. 7–5
7.2.3. Saving Classifications...................................................... 7–5
7.2.4. Deleting Classifications ................................................... 7–6
7.3. Changing Component Class Characteristics............................ 7–7
7.3.1. Renaming a Component Class........................................ 7–7
7.3.2. Selecting the Internal Class............................................. 7–7
7.3.3. Selecting System Types.................................................. 7–7
7.3.4. Changing the Class Label................................................ 7–8
7.3.5. Selecting the Icon Family ................................................ 7–8
7.3.6. Selecting the Default Scope............................................ 7–9
7.3.7. Selecting the Creation Scheme....................................... 7–9
7.3.8. Selecting the Initialization
Mnemonic [OS 2200 MCP]..................................... 7–10
7.3.9. Changing the Initialization
Mnemonic [UNIX Windows Other]........................ 7–11
7.3.10. Specifying Reinitialization.............................................. 7–11
7.3.11. Specifying the Instruction File....................................... 7–12
7.3.12. Specifying Retention of Note Files................................ 7–13
7.3.13. Specifying Alarm Text ................................................... 7–13
7.4. Adding and Deleting Component Classes ............................. 7–15
7.4.1. Adding a New Component Class .................................. 7–15
7.4.2. Copying a Component Class ......................................... 7–15
7.4.3. Merging Classifications ................................................. 7–16
7.4.4. Deleting Component Classes........................................ 7–16
7.5. Configuring Site-Defined Attributes....................................... 7–17
7.5.1. Configuring Status Attributes........................................ 7–17
7.5.2. Configuring Numeric Attributes .................................... 7–19
7.5.3. Configuring String Attributes......................................... 7–21
7.6. Additional Specifications ........................................................ 7–23
7.6.1. Editing a Single Class .................................................... 7–23
7.6.2. Controlling Duplicate Alarm Behavior............................ 7–23
Appendix A. Troubleshooting
A.1. Event Report Logging ..............................................................A–2
A.1.1. Trace Levels ....................................................................A–2
A.1.2. SP-STATUS Log...............................................................A–2
A.1.3. Log Message Information ...............................................A–3
7833 4778–008 vii

Contents
A.1.4. Message Type Codes ..................................................... A–3
A.1.5. Exception Conditions ...................................................... A–3
A.2. Unreported Components Table ............................................... A–5
A.3. Reporting Problems................................................................. A–6
Appendix B. Tape Monitor for OS 2200 Hosts [OS 2200]
B.1. Tape Monitor Features ............................................................ B–2
B.1.1. Capabilities...................................................................... B–2
B.1.2. Accessing the Tape Monitor Application ........................ B–2
B.2. TapeMon Classification [OS 2200] ........................................ B–3
B.2.1. Tape Class Characteristics.............................................. B–3
B.2.2. Host Class Characteristics .............................................. B–5
B.2.3. Diagrams and Component Sets...................................... B–6
B.2.4. Component Group Table Templates............................... B–6
Appendix C. Tape Monitor for MCP Hosts [MCP]
C.1. Tape Monitor Features ............................................................ C–2
C.1.1. Capabilities...................................................................... C–2
C.1.2. Accessing the Tape Monitor Application ........................ C–2
C.2. MCPTapeMon Classification ................................................... C–3
C.2.1. MCP_Tape Class Characteristics .................................... C–3
C.2.2. Host Class Characteristics .............................................. C–4
C.2.3. Diagrams and Component Sets...................................... C–6
C.2.4. Component Group Table Templates............................... C–6
Appendix D. UNIX Resource Monitor [UNIX]
D.1. Using the UNIX Resource Monitor [UNIX] ............................ D–2
D.1.1. UNIX Resource Monitor Features................................... D–2
D.1.2. Capabilities...................................................................... D–2
D.1.3. Accessing the UNIX Resource Monitor .......................... D–2
D.1.4. UnixMon Classification ................................................... D–3
D.2. UnixMon Classification [UNIX]............................................... D–4
D.2.1. UNIX Host Class ............................................................. D–4
D.2.2. CPU Class ....................................................................... D–5
D.2.3. FileSystem Class............................................................. D–5
D.2.4. LongProcess Class.......................................................... D–6
D.2.5. Process Class.................................................................. D–7
D.2.6. User Class....................................................................... D–8
Appendix E. Classifications for ClearPath IX and ClearPath Plus
Servers for OS 2200 [OS 2200 UNIX]
E.1. Using the OS2200Mon Classification...................................... E–2
E.2. Accessing the OS2200Mon Classification .............................. E–3
viii 7833 4778–008

Appendix F. Predefined Icons Supplied with Single Point
Operations Status
Contents
F.1. Viewing Icons........................................................................... F–2
F.1.1. Icons for Use with the UNIX Resource Monitor
Classifications ............................................................. F–2
F.1.2. Icons for Use with Products from SMA and
TeamQuest ................................................................. F–3
F.1.3. Additional Alphabetic Icons ............................................. F–3
F.1.4. Additional System Type Icons......................................... F–4
F.1.5. Additional Hardware Icons .............................................. F–4
F.1.6. Additional Pictorial Icons ................................................. F–5
Appendix G. Related Product Information
Index ............................................................................................. 1
7833 4778–008 ix

Contents
x 7833 4778–008

Figures
1–1. Example of a Status Display .............................................................................. 1–4
1–2. Data Flow to Single Point Operations Status..................................................... 1–5
1–3. Menu Structure of Single Point Operations Status............................................ 1–7
2–1. Tape Monitor Table ............................................................................................ 2–4
2–2. Status and Legacy OS 2200 Systems ............................................................... 2–6
2–3. Status and MCP Systems .................................................................................. 2–7
2–4. How Status Obtains Component Information ................................................... 2–8
2–5. Defining a Classification................................................................................... 2–11
2–6. Relationship of Diagram Definitions to Classifications and
Configurations.............................................................................................. 2–17
3–1. Status Window Features ................................................................................... 3–2
3–2. Example of a Status Diagram............................................................................. 3–3
3–3. Component Group Table.................................................................................. 3–11
3–4. Components with Unexpected Values Table................................................... 3–14
3–5. Components with Notes Table ........................................................................ 3–16
3–6. Unreported Components Table........................................................................ 3–17
3–7. Identical Components Table ............................................................................ 3–18
3–8. Attribute List .................................................................................................... 3–20
3–9. Dialog Window................................................................................................. 3–23
5–1. Define Status Diagram Groups Table................................................................. 5–2
5–2. Table to Define Component Table Templates ................................................. 5–16
5–3. A Component Group for Each Combination of Host and
Component Class ........................................................................................ 5–24
5–4. A Component Group for Each Component Class ............................................ 5–24
6–1. Edit Components Table...................................................................................... 6–2
7–1. Define Status Classification Table...................................................................... 7–3
7–2. Changing the Reinitialize Value ........................................................................ 7–12
D–1. UnixMon Status Diagram...................................................................................D–3
E–1. OS2200Mon Status Diagram ............................................................................. E–3
7833 4778–008 xi

Figures
xii 7833 4778–008

Section 1
Introduction to Single Point Operations
Status
This guide describes Single Point Operations Status and explains how to use it to monitor
the status of hardware and software components on multiple systems, including
OS 2200, MCP, UNIX, Windows, and other systems.
Use of the New Product Name in This Document
Audience
Conventions
Single Point Operations is now called Operations Sentinel. Throughout this document,
however, the former product name, Single Point Operations, has been retained to reflect
the very limited name changes applied within the product at this time.
The primary audience for this guide consists of operators who use Single Point
Operations Status to monitor the status of hardware and software components. A
second audience consists of site administrators who configure Status and require
information about its capabilities and operations.
Use the following guidelines when using your mouse or keyboard for input to Status:
Convention Description
Left mouse button Used to select an item, resize a window, or move a window.
Press Hold down the mouse button.
Release Release the mouse button after pressing it.
Click Press and quickly release the mouse button without moving the
mouse. Unless stated otherwise, the left mouse button is
assumed.
Drag Move the mouse on the pad while the left mouse button is
pressed.
Double-click Click the mouse button twice in rapid succession without moving
the mouse.
Press Enter Press the Enter key.
Press Delete Press the Delete key.
7833 4778–008 1–1

Description of Status
Convention Description
Press Ctrl-key Hold down the Ctrl key while pressing the specified key. Then
release both keys.
Path Abbreviations
Throughout the document, the following path abbreviations are used:
• sp-installation-folder
A path to the folder where Single Point Operations is installed.
• sp-data-folder
A path to the folder where Single Point Operations data is installed.
Host-Specific Information
This document contains information for monitoring and controlling several types of
computer systems. The following labels, and combinations of these labels, identify
information that applies only to specific types of managed systems.
Information in this document not using these labels applies to all system types.
[Legacy OS 2200]
Unisys OS 2200 systems and the OS 2200 nodes of Unisys ClearPath IX systems
[ClearPath Plus OS 2200]
OS 2200 partitions in a ClearPath Plus server
[OS 2200]
Legacy OS 2200 systems and ClearPath Plus OS 2200 servers
[MCP]
Unisys MCP systems and the MCP nodes of ClearPath Plus for MCP, ClearPath NX,
and ClearPath LX systems
[UNIX]
UNIX systems and the UNIX nodes of ClearPath Plus for OS 2200, ClearPath IX, and
ES7000 systems
[Windows]
Microsoft Windows .NET, Windows XP, Windows 2000, and Windows NT systems,
and the Windows nodes of ClearPath Plus, ClearPath, and ES7000 systems
[Other]
Non-UNIX systems compliant with the ANSI X3.64 protocol
These computer system labels can appear in headings, lists, and page headers.
In the following example, all the information in this second-level topic applies only to
MCP and UNIX systems:
20.3. Using Single Point Operations Console [MCP UNIX]
1–2 7833 4778–008

Class
Description of Status
The next example shows a typical block containing only text. The information in the first
paragraph applies to all computer systems (including OS 2200) because the block
heading is unlabeled. All information to the end of the block (in this example, the second
and third paragraphs) applies only to OS 2200 systems, because the block subheading is
labeled [OS 2200].
This attribute identifies the component class to which the component belongs. When
you click the Class attribute, no action occurs.
[OS 2200]
Typically, the class of a component never changes once the component has been
created. However, when Status receives an event report identifying a component of the
Device class more specifically as a disk drive or tape drive, it changes the class
accordingly.
This final example illustrates a typical procedure in numbered steps. The first two steps
apply to all systems. The third step, where the label “Windows” is indented within the
step, applies only to Windows .NET, Windows XP, Windows 2000, and Windows NT
systems. The last two steps apply to all systems. In other words, perform all five steps
in the indicated order if you have a Windows system. Omit step 3 if you have a system
other than Windows.
Use the following procedure to
1. Define classifications for Status.
2. Customize the bar chart sets.
3. [Windows]
Configure alarm policies.
4. Administer the UNIX Resource Monitor agent.
5. Administer the HP OpenView agent.
Release Level
In classification names, x.y.z is the Single Point Operations release level.
7833 4778–008 1–3

Description of Status
1.1. Description of Status
Single Point Operations Status is an application of Single Point Operations that enables
you to monitor the status of software and hardware components across multiple hosts,
including OS 2200, MCP, UNIX, Windows, and other systems. The following illustration
is an example of a Status display. Each row describes one component being monitored
by Status.
1.1.1. How Status Works
Figure 1–1. Example of a Status Display
Status maintains an inventory of components and their attributes based on an internal
data model of component descriptions and attribute data associated with the
components. The data model is populated and updated from messages and event data
that are produced by the various systems being monitored.
Status receives and processes attribute change and delete object event reports
generated by the Single Point Autoaction Message System (SP-AMS), SMART
Autoaction Message System (SMART AMS), ClearPath Plus Autoaction Message
System (CP-AMS), UNIX Resource Monitor (URM) agent, and client applications. These
event reports cause component information maintained and displayed by Status to be
updated. For further information, see the Single Point Operations Administration and
Configuration Guide.
The following illustration shows the flow of data from various sources to Single Point
Operations Status. Items inside the large box reside on the Single Point Operations
server, while items outside the large box reside on other systems. Event server
application program interface (API) clients and user applications can reside on the Single
Point Operations server or on monitored Windows and UNIX systems.
1–4 7833 4778–008

Figure 1–2. Data Flow to Single Point Operations Status
Description of Status
[OS 2200]
For legacy OS 2200 hosts, the AMS component of SMART compares console messages
with user-defined patterns in an AMS database and generates event reports based on
these messages.
CP-AMS supports the automation of OS 2200 consoles in a ClearPath Plus server.
CP-AMS invokes the actions that are defined for a pattern when it receives a message
from an OS 2200 console matching that pattern. Each OS 2200 console in a ClearPath
Plus server uses its own CP-AMS database. A change of database performed for one OS
2200 console does not affect the other OS 2200 consoles in a ClearPath Plus server.
That is, activating or deactivating a CP-AMS database does not affect the automation of
other OS 2200 consoles in a ClearPath Plus server.
ClearPath Plus OS2200 consoles are hosted in at least one Operations Servers. If
desired, the Single Point Operations server itself can act as an Operations Server.
[MCP UNIX]
For MCP and UNIX hosts, SP-AMS compares console messages with user-defined
patterns in an SP-AMS database and generates event reports based on these messages.
7833 4778–008 1–5

Description of Status
[UNIX]
For UNIX systems, Single Point Operations provides the UNIX Resource Manager (URM)
agent to collect resource data on managed UNIX systems and send that data as event
reports to the Single Point Operations server. For a description of the components
monitored by URM, see Appendix D. For information on configuring and installing the
agent, see the Single Point Operations Administration and Configuration Guide.
You can write your own agents to supply component information to Status for managed
UNIX systems. These agents can send event reports to the spo_pipe file on the Single
Point Operations server or they can use the Event Server API, which provides a
programmatic interface for sending event data.
[Windows]
You can write your own agents to supply component information to Status for managed
Windows systems. These agents can either use the spo_event command to send event
reports to Status or they can use the Event Server API, which provides a programmatic
interface for sending event data.
[Other]
You can also monitor the status of arbitrary systems and components associated with
these systems using Status. An arbitrary system can represent a monitored component
not directly connected to Single Point Operations. It can represent, for example, a
system management component that reports events of interest to Single Point
Operations.
You use Single Point Operations Configuration to define arbitrary systems. Event
reports, alarms, and log messages can be posted against a named arbitrary system
through the Event Server application program interface (API), the Single Point Interface
Pipe (spo_pipe), or SP-AMS. For further information, see the Single Point Operations
Administration and Configuration Guide and the Single Point Operations Event Server
Application Program Interface Programming Guide.
1.1.2. Availability of Status
To use the full capabilities of Single Point Operations Status, your site administrator must
purchase and install either the Department or Enterprise Edition of Single Point
Operations. With Basic Edition, you can still use Single Point Operations Status with the
classifications supplied with Single Point Operations, but you cannot create or change
component classes and attributes within these classifications, nor can you create other
classifications.
[MCP OS 2200]
The Tape Monitor, which is a specific use of Status, is provided as part of all editions of
Single Point Operations for OS 2200 systems and as part of Enterprise or Department
Edition for MCP systems. For further information about the Tape Monitor for OS 2200
systems, see Appendix B. For further information about the Tape Monitor for MCP
systems, see Appendix C.
1–6 7833 4778–008

Description of Status
[UNIX]
The UNIX Resource Monitor (see Appendix D) application of Single Point Operations
Status is included as part of all editions of Single Point Operations.
1.1.3. Menu Structure
This illustration shows the main menu structure of Single Point Operations Status.
File
Menu
Select
Diagram
(5.5)
Retrieve
Component
Sets
(6.4)
Select
Classification
(2.5)
Select
Configuration
(2.5)
Select
Resource
Set
(2.5)
Select
Trace Level
(2.5)
Print
Exit
(2.4)
Tables
Menu
Components
with
Unexpected
Values (3.4)
Components
with Notes
(3.4)
Unreported
Components
(3.4)
Status Diagram
(Main Status Display)
Diagrams
Menu
Define
Component
Groups (5.1)
Define
Component
Table
Templates
(5.2)
Save
Diagram
(5.3)
Save
Diagram
As
Delete
Diagrams
(5.4)
Component
Sets Menu
Define
Components
(6.1)
Remove
Unreported
Components
(6.2)
Save
Component
Set
(6.2)
Save
Component
Set As
(6.2)
(5.3) Delete
Component
Sets
(6.3)
Help
Menu
General
7833 4778–008 1–7
Print
Documents
Trademarks
About Status
Figure 1–3. Menu Structure of Single Point Operations Status
For detailed information about a task, refer to the subsection indicated in the
corresponding box.

Introduction to Components
1.2. Introduction to Components
A component is a single instance of an object within the Status data model. Each
component represents a software or hardware object, such as a printer, tape drive,
process, run, or file system. It represents a part of a computer system that you want to
monitor. Status directs your attention to components that need attention. Various
displays in Status show the status of components in summary and detailed form.
Section 3 describes the Status displays.
1.2.1. Component Attributes
Status maintains information about components in the form of attributes. An attribute is
a named property of a component that is of interest to an operator monitoring the
component. An attribute can assume certain values that change over time. An attribute
value describes an aspect of the current state of the component. For example, a status
attribute for a disk drive might describe its current status as up or down. In this case,
“up” and “down” are attribute values. Depending on the attribute, the value may be an
integer or a character string. Some attributes can have more than one value, called a list
of values, simultaneously.
Each component has a set of attributes. The names of these attributes remain fixed, but
their values vary over time. There are attributes with fixed names (Message, Exceptions,
Notes) that are common to all components. Other attributes have site-defined names.
Each component can have up to eight of each type of site-defined attributes: status,
numeric, and string.
For status attributes, you can define alarm and expected values. For numeric attributes,
you can specify threshold values. These settings direct Status to alert you of
components that need attention. For further information about attributes, see Section 4.
1.2.2. Component Classes
Because the nature of components varies, an attribute that applies to one component
may not apply to another. Therefore, Status groups components into classes. All
components within a class have the same attributes.
A classification is a named set of component classes monitored by Status. Status
comes with several classifications already defined. (See 2.3.)
The classification generalx.y.z. supplied with Single Point Operations includes the
following classes:
[OS 2200]
• OS 2200 host
• OS 2200 console
• OS 2200 run
• Instruction processor (IP)
• Input/output processor (IOP)
1–8 7833 4778–008

• Storage area (memory module)
• Channel
• Control unit
• Device
• Disk drive
• Tape drive
[MCP]
• MCP host
• Disk drive
• Disk family
• Tape drive
• Printer
• Application
[UNIX]
• ANSI X3.64-compliant (UNIX) host
• Process
• File system
• Central Processing Unit (CPU)
• Long process
• User
Introduction to Components
If your site has installed the Department or Enterprise Edition of Single Point Operations,
you can change these component classes and define additional component classes using
Single Point Operations Configuration. For further information, see Section 7.
1.2.3. Event Reports
An event report is an unsolicited data packet containing information about a component
or about an event involving a component. Attribute values for a component are reported
to Status by means of event reports. Status uses these event reports to monitor the
components in its data model.
Status processes two types of event reports. Attribute change (AC) event reports create
new components and update the attributes of existing components. Delete object (DE)
event reports delete components from the Status data model.
Some event reports are generated when SP-AMS, SMART AMS, or CP-AMS matches a
console message with a user-defined pattern in a database. Other event reports are
generated by sources such as the URM agent and client applications, which forward
event reports using the Single Point Interface Pipe (SPIP), the spo_event command, or
7833 4778–008 1–9

Introduction to Components
the Event Server Application Program Interface (API). For further information, see the
Single Point Operations Administration and Configuration Guide and the Single Point
Operations Event Server Application Program Interface Programming Guide.
The following examples show attribute change and delete object event reports as they
would be specified in a SP-AMS, SMART AMS, or CP-AMS database, or as they would
be sent to spo_pipe in the Single Point Operations installation directory:
TYPE=AC|CLASS=FileSystem|INSTANCE=/usr|HOST=localhost|
Percent Space Used=78|Inodes Free=2345
TYPE=DE|CLASS=FileSystem|INSTANCE=/usr|HOST=localhost
The following examples show the same attribute change and delete object event reports
as they would be sent by an application using the Event Server API:
SPD_ReportValue("FileSystem","/usr","localhost",NULL,
NULL,0,2,"Percent Space Used",78,"Inodes Free",2345);
SPD_DeleteObject("FileSystem","/usr","localhost",NULL,NULL,0);
1.2.4. Shared Components
For a component shared by multiple hosts, such as a shared disk, the attribute values
reported for the component may differ for each host. For example, a shared disk may be
up on one host and down on another. Therefore, Status maintains a distinct logical
component for each host reporting on the component. Status also provides a way to
display in one table the logical components representing a single physical component.
1.2.5. How Components Are Identified
Components in Status are uniquely identified by a combination of three attributes:
• Component name
• Component class
• Host on which the component resides
By using these three attributes, Status can distinguish between two components of the
same class and with the same name that reside on different hosts. In addition, two
components on the same host can have the same name as long as they are of different
classes. For example, a run and a disk drive on the same host can have the same name.
For each event report Status receives, it checks the attributes in the event report to
determine whether the event applies to a host in the current configuration and a
component class in the current classification. Status discards any event report that
applies to a host not in the current configuration or to a class not in the current
classification.
Once a component is created in Status, its name, host, and class cannot change because
these are used to identify the component.
1–10 7833 4778–008

1.2.6. Creating Components
Introduction to Components
A component in the Status data model can be created automatically based on an event
report, or operations staff can define it explicitly.
A component may be automatically created when Status receives an event report that
applies to a component that it is not already modeling. Depending on the component
class, Status responds to such an event report either by ignoring it or by adding a new
component to its data model.
When you define each component class using Single Point Operations Configuration, you
specify which action to take. For details, see 7.2. Automatic creation of components is
typically used for hardware components. With automatic creation, you do not have to
define explicitly all the hardware components to be monitored. On an OS 2200 or MCP
system, for example, the data collector collects available data for hardware components
and, based on this data, components within Status are automatically created.
You may, however, want to define explicitly some of the components to be monitored.
One reason for doing this is to specify values for attributes (for example, Expected
Status) different from the default values supplied during automatic creation. It is easy to
define components explicitly and to save these definitions in named sets that you can
retrieve later. For details, see Section 6.
1.2.7. Component Groups
A component group is a collection of components that operations personnel have
decided to monitor through a single icon in the Status diagram. (See 3.2.) Components
in a component group can be selected based on the names of the components, the
classes of the components, and the hosts on which the components reside. For
information about defining component groups, see 5.1.
1.2.8. Instruction and Note Files
Each component in Status can have two associated text files: an instruction file and a
note file. These files reside on mass storage, so they remain on the Single Point
Operations server indefinitely, across multiple executions of Status.
Instruction files enable your site to develop explicit instructions for operators: You can
develop a different instruction file for each component, or associate one file with many
similar components. For example
• A site may have one instruction file that applies to all disk drives.
• For tape drives, a site may have one instruction file for reel tapes and another
instruction file for cartridge tapes.
• A site may have a separate instruction file for every background run or process
monitored by Status.
For information about creating instruction files and associating them with components,
see 6.1.
7833 4778–008 1–11

Introduction to Components
Note files enable operators to enter text notes that apply to specific components. Each
note file is associated with only one component. Each component has an attribute
named Notes, which can assume the value “yes” or “no.” Status automatically
determines whether each component has a note file and sets the Notes attribute
accordingly.
It is easy to display the notes associated with a component, edit them, and delete them.
You can also determine quickly which components have notes. For details, see 4.2.
1.2.9. Alarms
An alarm is a condition that requires operator attention. Alarms are displayed in the
Alarms windows of Single Point Operations Console. An alarm can also cause an external
action, if the identifier of the alarm matches the name of an action list in the active alarm
policy.
You can configure Status to raise an alarm for certain conditions it detects. You do this by
specifying alarm text, alarm ids, and alarm severities for the attributes of a component
class, as described in 7.3 and 7.5. You must also specify the attribute values that cause
an alarm condition. For a status attribute, you select the alarm values for the component,
as described in 4.3, 6.1, and 7.5. For a numeric attribute, you can specify a minimum or
maximum alarm threshold, as described in 4.3, 6.1, and 7.5.
While Status is running, if an attribute of a component attains an alarm value, and alarm
text, alarm id, and alarm severity has been specified for the component class and
attribute, Status raises an alarm with the given text, id, and severity. If this attribute later
attains an attention or expected value, Status clears this alarm.
1.2.10. External Applications
An external application is a procedure, defined at your site, which you can initiate from
Single Point Operations Console or Status. Any external applications developed at your
site exist to meet needs specific to your site. When you launch an external application,
the application might execute silently or might display windows on your screen,
depending on what it does and how it was implemented. External applications can only
run on the Single Point Operations workstation.
When you launch an external application from Status, it is always launched on behalf of a
specific component. This means that values from the component are automatically
made available to the application through environment variables. These values include
the name, class, and host of the component, as well as all of its attribute values.
You can launch external applications in Status from various displays. For information on
defining external applications, see the Single Point Operations Administration and
Configuration Guide.
1–12 7833 4778–008

Section 2
Getting Started
This section discusses the following topics:
• Operating considerations
• Preparing to use Status
• Setting up Status
• Starting and terminating Status
• Changing the Status environment
7833 4778–008 2–1

Operating Considerations
2.1. Operating Considerations
The following subsection describes different operation considerations.
2.1.1. Event Report Considerations
Attribute values for a component are reported to Single Point Operations Status by event
reports, which can be sent to Status by various sources. These sources include SP-AMS
(MCP and UNIX systems), SMART AMS (legacy OS 2200 systems), CP-AMS (ClearPath
Plus OS 2200 partitions), URM agents, and client applications that use the Single Point
Interface Pipe (spo_pipe), spo_event, or the Event Server API.
Sometimes an event report is generated when a console message from a managed
system matches a user-defined pattern in the active SP-AMS, SMART AMS, or CP-AMS
database. The event report describes the event that caused the original message to be
generated. The SP-AMS, SMART AMS, and CP-AMS databases contain user-defined
message patterns and define the actions that are taken if there is a match. If the
message does not match any pattern in the active database, no event report is
generated. A different SMART AMS or CP-AMS database can be active for each
OS 2200 system console; a single SP-AMS database provides automation for all MCP
and UNIX systems managed by the Single Point Operations server.
In other cases, an event report is generated by the URM agent running on a managed
UNIX system, which sends the event report to the Single Point Operations server
through the Event Server API. Once an event report is sent to the Single Point
Operations server, it is picked up by the Event Server daemon running there and
forwarded to Status.
You can also use the command spo_event to send any event report from a Windows
host to Single Point Operations. You can call this command from
• A Windows command prompt.
• Within a Windows script.
• Within a user program.
The spo_event executable is installed along with the Single Point Operations Windows
agent in the installation folder. The command spo_event can be called only from a
Windows host on which the Single Point Operations Windows agent is installed. If it is
called from another Windows host, a Single Point Operations license violation occurs.
2.1.2. Event Report Value Pairs
An event report consists of a series of attribute value pairs (for example, TYPE=AC)
separated by separator characters ( | ). An attribute value pair consists of an attribute
name and an attribute value. To be accepted by Status, an event report must contain at
a minimum the following attribute value pairs:
2–2 7833 4778–008

Operating Considerations
• TYPE
The type of event report—AC (attribute change) or DE (delete object)—is required for
the event report to be processed by Status.
• CLASS
The component class associated with the event report. This must be a Status
component class defined in the classification currently selected by the user. This
corresponds to the Class attribute in Status (see 4.2).
• INSTANCE
The name of the component associated with the event report. This corresponds to
the Name attribute in Status (see 4.2). For event reports from SMART AMS and
CP-AMS, the character strings $HOST$ and $CONSOLE$ have a special meaning
when used as values of an instance name. Status substitutes the name of the host
($HOST$) or console ($CONSOLE$) from which the message came.
• HOST
The host to which the component belongs. The Host attribute is required only when
the event report is sent using spo_event or the Event Server API. For event reports
from SP-AMS, SMART AMS, or CP-AMS, the host is automatically assumed to be
the host from which the message came.
An event report may contain additional attribute value pairs, which must conform to the
constraints defined for these attributes in the component class definition. Status rejects
an event report that does not satisfy these requirements. For further information about
event reports, see the Single Point Operations Administration and Configuration Guide.
For further information about defining component classes, see Section 7.
Event Report Example
Consider the following OS 2200 system message to load a tape on system host1:
LOAD CT2043 CTDR31 OBACKUP -3 SAVALL
In this message
• CT2043 is the reel number.
• CTDR31 is the tape drive name.
• OBACKUP is the file name.
• -3 is the file cycle number.
• SAVALL is the run-id.
This message could produce an event report with the following attribute value pairs:
• TYPE=AC
• CLASS=Tape
7833 4778–008 2–3

Operating Considerations
• INSTANCE=CTDR31
• LOAD=YES
• REEL_ID=CT2043
• RUNID=SAVALL
• FILENAME=OBACKUP
After receiving this event report, Status, using the classification TapeMon, displays a
table indicating that tape drive CTDR31 on system host1 requires reel CT2043 to be
loaded.
2.1.3. Tape Monitor for OS 2200 and MCP Systems
[OS 2200 MCP]
The OS2200 Tape Monitor is a specific use of Status and is provided as part of all
editions of Single Point Operations. Similarly, the MCP Tape Monitor is a specific use of
Status, but it is only included in Department and Enterprise Editions of Single Point
Operations. The OS 2200 and MCP Tape Monitors enable your site to monitor tape drive
activity on OS 2200 and MCP hosts. For status information about other component
classes, the Department or Enterprise Edition of Single Point Operations is required.
To use the OS 2200 Tape Monitor, select the classification TapeMonx.y.z when you start
Status. To use the MCP Tape Monitor, select the classification MCPTapeMonx.y.z. In
these classification names, x.y.z is the Single Point Operations release level.
When you start Status with the Tape Monitor, the Tape Monitor diagram appears. This
diagram displays the status of any tape drives you previously configured.
Click an icon in the Tape Monitor diagram to display more detailed information about
specific tape drive components. When you click an icon, Status displays a table
describing the status of tape drives in the component group represented by that icon.
The following illustration is an example of a Tape Monitor table.
Figure 2–1. Tape Monitor Table
2–4 7833 4778–008

2.1.4. OS 2200 Considerations [OS 2200]
Operating Considerations
To use Status with OS 2200 systems, you need the following software installed and
operational at your site:
• OMKEY background run
The OMKEY background run collects basic information about components and
directs this information to the system console.
The data collector is part of the OMKEY background run. It supplies initialization data
for Status. This allows Status to display the status of each hardware component on
the managed system. Without the data collector, Status can determine the
presence of a component only when a message about that component is sent to the
system console.
For accurate reporting by Status, OMKEY must be running on each managed
OS 2200 system. OMKEY level 5R1 or higher is required.
• SMART Autoaction Message System (SMART AMS) [Legacy OS 2000]
SMART AMS runs on each legacy OS 2200 system console and provides automatic
recognition of messages and the execution of corresponding actions. SMART AMS
uses an AMS database to transform the console messages produced by the OMKEY
background run into event reports, which are sent to the Single Point Operations
server.
• The ClearPath for OS 2200 Autoaction Message System (CP-AMS) [ClearPath
Plus OS 2200]
CP-AMS supports the automation of OS 2200 consoles in a ClearPath Plus server. It
uses a database of message patterns and actions for these patterns. CP-AMS
invokes the actions that are defined for a pattern when it receives a message from
an OS 2200 console matching that pattern. Each OS 2200 console in a ClearPath
Plus server uses its own CP-AMS database. A change of database performed for one
OS 2200 console does not affect the other OS 2200 consoles in a ClearPath Plus
server. That is, activating or deactivating a CP-AMS database does not affect the
automation of other OS 2200 consoles in a ClearPath Plus server.
To use the full capabilities of Single Point Operations Status to monitor OS 2200
systems, your site must do the following:
• Purchase and install the Department or Enterprise Edition of Single Point Operations.
• Use the AMS/CP-AMS database status22.bld included with Single Point Operations.
This database is used in conjunction with the OMKEY run to initialize all OS 2200
components described in the OS 2200 master configuration tables. The status22.bld
database is installed in sp-data-folder\os2200-ams on the Single Point Operations
server.
To transfer an AMS database to an OS 2200 Console, use the utility ADBM, which is
described in the Single Point Operations Autoaction Message System Administration
Guide.
7833 4778–008 2–5

Operating Considerations
The following illustration shows how the OMKEY background run on a legacy OS 2200
system collects information and sends it as console messages to the OS 2200 system
console. On the system console, SMART uses an AMS database to match these
messages automatically, transform them into event reports, and send them to Status
running on a Single Point Operations workstation.
System
Components
Initial
State
Data
OMKEY
Background
Run
Console
Messages
AMS
Database
Message
Set
Figure 2–2. Status and Legacy OS 2200 Systems
2.1.5. MCP Considerations [MCP]
Event
Reports
To use Status with MCP systems, you need the following software installed and
operational at your site:
Status
1. Single Point Operations Department or Enterprise Edition
2. Single Point Operations Interface for ClearPath MCP
The MCP agent running on a managed MCP host sends the following information to
the Single Point Operations server:
• Tape load and alert messages
• Status of hardware components (tape, disk, and printer)
• Definition of application programs that are known to the MCP API library
3. Single Point Autoaction Message System (SP-AMS) database
The MCP SP-AMS database (named MCPMon) transforms the information sent by
the MCP agent so that Status and other Single Point Operations processes can use
it.
When Status establishes a connection with an MCP system, it requests hardware
component information and application program information by sending an initialization
message to the Single Point Operations Interface for ClearPath MCP (MCP agent)
running on the MCP host. The MCP agent queries the host for the information and sends
only the requested information back to Status.
The MCP agent can return initialization information for the following hardware
components: tape drives, disk drives, and printers. Also, it can return initialization
information for application programs that are linked to the MCP API library.
2–6 7833 4778–008

Operating Considerations
The MCP agent sends an unsolicited message to the Single Point Operations server for
each applicable hardware and application component. These messages must be matched
by patterns in the active SP-AMS database and converted to event reports that are sent
to Status. The SP-AMS database supplied with Single Point Operations (named
MCPMon) contains these patterns.
All the SP-AMS databases supplied with Single Point Operations are installed in sp-datafolder\sp-ams
on the Single Point Operations server.
For further information about the MCP agent and the ClearPath MCP API library, see the
MCP Single Point Operations Interface Software Installation and Configuration Guide.
The following illustration shows how MCP agent on MCP systems sends collected
information and messages to the Single Point Operations server. On the Single Point
Operations server, SP-AMS uses a database of patterns, matches these messages,
transforms them into event reports, and sends them to Status.
Figure 2–3. Status and MCP Systems
2.1.6. UNIX Systems Considerations [UNIX]
The UNIX Resource Monitor (URM) agent runs on managed UNIX systems on which your
site has installed it, and sends selected attribute values to the Single Point Operations
server. The URM agent uses shell scripts, which report data through event reports using
a remote Single Point Interface Pipe (SPIP) program on the managed host. This program
provides the gateway from the managed host to the Event Server running on the Single
Point Operations server. For each packet of event reports the URM agent sends to the
Single Point Operations server, the remote SPIP program connects to the Event Server
and passes the event reports across the network.
You can change some reporting parameters of the URM agent using Single Point
Operations Configuration. For further information, see the Single Point Operations
Administration and Configuration Guide.
2.1.7. Windows Considerations [Windows]
To monitor components on Windows .NET, Windows XP, Windows 2000, and Windows
NT systems, you must develop your own agents to send component information to
7833 4778–008 2–7

Operating Considerations
Status. These agents can use the program spo_event to send the event reports to the
Single Point Operations server. This program is installed on each managed
Windows system when you transfer the Single Point Operations Windows interface
software to the system. For further information, see the Single Point Operations
Administration and Configuration Guide.
2.1.8. Summary of Status Information Sources
This illustration shows how Status obtains information about components.
Figure 2–4. How Status Obtains Component Information
2–8 7833 4778–008

2.2. Preparing to Use Status
Preparing to Use Status
Before you begin to use Status, you must take the preliminary steps described in this
subsection.
2.2.1. Preliminary Steps
Before using Status, a site typically takes these preliminary steps:
1. Use Single Point Operations Configuration to configure hosts and consoles and to
define classes of components (see “Configuring Status” later in this subsection).
For further information about configuration, see Section 7 and the Single Point
Operations Administration and Configuration Guide.
2. Determine which data is to drive the Status data model. One or more of the
following data sources can supply event reports to Status:
• Console messages
Identify OS 2200, MCP, or UNIX messages that contain information for each
component class. For OS 2200 and MCP systems, also consider messages sent
from the data collector on these systems.
In a SMART AMS, CP-AMS, or SP-AMS database, create a pattern for each
message that has attribute-value information of interest. In this pattern, include
an attribute change event report (TYPE=AC) as an action. For OS 2200 hosts,
activate the appropriate SMART AMS or CP-AMS database on each console. For
UNIX and MCP systems, activate the appropriate SP-AMS database on the
Single Point Operations server.
Note: When both UNIX and MCP systems are being monitored, the active
SP-AMS database must contain patterns for messages from systems of both
types.
• UNIX Resource Monitor agents
Install and configure this agent on each managed UNIX system using the Single
Point Operations Configuration application.
• User-defined applications
First develop a data collection method. The application must format this data
into event reports and pass these event reports to the Single Point Operations
server by one of the following methods:
Ä Using the Event Server application program interface (API) on monitored
UNIX or Windows systems.
The function SPD_ReportValue sends an attribute change event report, while
SPD_DeleteObject sends a delete object event report.
Ä Using the command spo_event on a monitored Windows system to send an
event report string to the Single Point Operations server.
After taking these steps, your site is ready to start Status. For information about starting
Status, see 2.4.
7833 4778–008 2–9

Preparing to Use Status
2.2.2. Configuring Status
Before using Status, your site must use Single Point Operations Configuration to define
the information to be monitored. The specific information depends on how your site
wants to use Status. For detailed information about configuration, see Section 7 and the
Single Point Operations Administration and Configuration Guide.
In general, you must perform the following definition steps:
1. Modify an existing configuration or create a new configuration.
Both Single Point Operations Console and Single Point Operations Status can use the
same configuration. If Status is started from Single Point Operations Console, it
must use the same configuration as the instance of Single Point Operations Console
that started Status. If Status is started independently of Single Point Operations
Console, it can use any available configuration. In this case, it does not matter which
configuration Single Point Operations Console is using (or even whether or not Single
Point Operations Console is running).
When you modify an existing configuration or create a new configuration for use with
Status, you specify the hosts and system consoles that you want to monitor. You
also define users and user classes to identify authorized Status users.
2. Modify an existing classification or define a new classification, as follows.
• Create component classes in the classification.
• Modify characteristics of selected component classes, such as the following:
internal class, class label, icon family, default scope, system types, creation
scheme, initialization mnemonic, instruction file, and alarm text.
• Configure any site-defined status attributes for these component classes,
specifying the following for each attribute: attribute name, possible values,
expected values, alarm values, alarm-id, alarm severity, timeout period, and
default value.
• Configure any site-defined numeric attributes for these component classes,
specifying the following for each attribute: attribute name, default alarm
minimum, default attention minimum, default attention maximum, default alarm
maximum, unreported values, alarm-id, and alarm severity.
• Configure any site-defined string attributes for these component classes,
specifying the attribute name and associated attribute for each site-defined string
attribute.
You can skip all or part of step 2 if you use a classification supplied with Single Point
Operations, such as TapeMonx.y.z, MCPTapeMonx.y.z, or UnixMonx.y.z. See Appendix
B, Appendix C, Appendix D, and Appendix E for more information.
2–10 7833 4778–008

The following illustration shows the steps to define a classification.
Component
Class
Internal
Class
Class
Label
Classification
Component
Class
Component Class Characteristics
Site-Defined
Status
Attributes
Instruction
File
Site-Defined
Numeric
Attributes
Figure 2–5. Defining a Classification
Preparing to Use Status
Component
Class
Alarm
Text
Site-Defined
String
Attributes
After your site administrator has configured Status using Single Point Operations
Configuration, you can use Status to perform additional definition tasks, such as defining
component table templates, component groups, and component sets. For an overview
of the tasks you can perform with Status, see the illustration on the Status menu
structure in 1.1.
See Section 7 for additional configuration information.
7833 4778–008 2–11

Setting Up Status
2.3. Setting Up Status
Minimal setup is needed to get Single Point Operations Status up and running. The
application comes with defaults for most setup information. However, the strength of
this application is the many ways it can be customized. For example, you can customize
Status to accommodate different host and console configurations or operators.
You can alter most of the definitions used by Status if you want to customize it, including
• Classifications
• Icon families
• Resource sets
• Configurations
• Users
• Diagram definitions
• Component sets
2.3.1. Classifications
A classification is a named set of component classes monitored by Status at one time.
You can define multiple classifications. This enables you to use Status for different
applications, with each application monitoring a different set of components.
If your site installed the Department or Enterprise Edition of Single Point Operations, you
can use Single Point Operations Configuration to change these classifications, define
new classifications, merge classifications, or delete existing classifications. For further
information, see Section 7.
Status comes with several classifications already defined:
• generalx.y.z
This classification contains all the component classes listed in 1.2.2 It is predefined
so that you can use it without changes at your site. Typically, however, sites
customize it. This classification is available only if your site has installed the
Department or Enterprise Edition of Single Point Operations.
• MCPMonx.y.z.
This classification contains all component classes in the classification generalx.y.z.
that apply to MCP systems (see 1.2.2).
• OS2200Monx.y.z.
This classification contains those component classes from the classification
UnixMonx.y.z. that apply to OS2200 systems (see Appendix E).
2–12 7833 4778–008

Setting Up Status
• MCPTapeMonx.y.z [MCP]
This classification contains the MCP_Host and MCP_Tape component classes, with
the site-defined attributes needed for the MCP Tape Monitor application.
(See Appendix C for information on MCP tape monitoring.)
• TapeMonx.y.z [OS 2200]
This classification contains the 2200_Host and Tape component classes, with the
site-defined attributes needed for the OS 2200 Tape Monitor application.
(See Appendix B for information on OS 2200 tape monitoring.)
• UnixMonx.y.z [UNIX]
This classification contains the UNIX Resource Monitor component classes, each
with a set of predefined attributes. (See Appendix D for the attributes specific to this
classification.)
• Unix2200Monx.y.z [OS 2200 UNIX]
This predefined classification contains all the component classes in the generalx.y.z
classification (see 1.2) that apply to OS 2200 and UNIX systems. Use this
classification when Status is obtaining information from UNIX and OS 2200 nodes in
a ClearPath Plus or ClearPath IX server. (See Appendix E for information on using this
classification.)
2.3.2. Icon Files
In the Status diagram and subgroup windows, Status can display icons of two types:
• Bitmap icons
Bitmap icons are single-color icons. This color changes to represent the various
states the icon can represent:
- Normal (green)
- Attention (yellow)
- Alarm (red)
- Empty (gray)
For all states, the icon has the same size and shape. Internally, a bitmap icon is
defined by a single file using the xbm format.
• Pixmap icons
Pixmap icons are multicolored icons. The size, shape, and color of these icons can
change for each of the states the icon can represent:
- Normal
- Attention
7833 4778–008 2–13

Setting Up Status
- Alarm
- Empty
Internally, a family of four icon files, one for each state, defines a pixmap icon. The
format of pixmap icons can be
- bmp
- jpeg
- pbm
- pgm
- png
- pnm
- ppm
- tiff
- xpm
All icons in one family must be of the same format.
Status includes two unique pixmap icon definitions for each component class in the
predefined classifications and two pixmaps for generic icons. Pixmaps with names that
end with “_lg” are 50 by 50 pixels; pixmaps with names ending with “_sm” are 30
pixels wide by 25 pixels high. For a list of the pixmap icons supplied with Status,
see Appendix F.
The icon files reside in sp-data-folder\status\xbm, where sp-data-folder is the Single Point
Operations data folder specified during the installation of the server version of Single
Point Operations. The icons in this folder must have the correct file extension. For
example, bitmap icons must have the .xbm file extension. For further information on icon
file types and defining icon families, see the Single Point Operations Administration and
Configuration Guide.
Note: In Single Point Operations Level 7.4, the icons supplied with Status changed
from bitmap icons to pixmap icons with a more modern three-dimensional appearance.
Diagrams you have defined using previous levels of Single Point Operations can continue
to use the obsolete bitmap icons or you can modernize your Status displays with a single
operation if you choose. See 5.1.5 and 7.3.5 for more information.
See 5.1.5 and 7.3.5 for instructions on selecting icons for Status.
2–14 7833 4778–008

2.3.3. Resource Sets
Setting Up Status
A resource set controls the colors and fonts used in various Status displays. Status
provides a number of resource sets from which you can choose. Your site administrator
can use Single Point Operations Configuration to specify a default resource set for each
user. For details, see the Single Point Operations Administration and Configuration
Guide.
While Status is running, you can select a different resource set if you want different
fonts used to display headers and values in the Status diagram and component tables.
For information about changing resource sets, see 2.5.
2.3.4. Configurations
2.3.5. Users
A configuration describes the consoles and hosts monitored by Status, and the
connections between these consoles and hosts. Because you can use Status to monitor
different combinations of consoles and hosts, you can define many different
configurations for Status. You can use only one of the defined configurations at a time.
Status uses the same configuration definitions used by Single Point Operations Console.
Use Single Point Operations Configuration to define configurations. For details, see the
Single Point Operations Administration and Configuration Guide.
The definitions of classifications, configurations, and resource sets are independent, as
explained in the following table:
You can select a different... Without changing or reselecting the...
Classification Configuration or resource set
Configuration Classification or resource set
Resource set Classification or configuration
User definitions provide a means to restrict certain Status operations. Status uses the
same definitions of users and user classes that are defined using the Single Point
Operations Configuration application and used by Single Point Operations Console. Each
user definition is associated with a specific configuration; many users can be associated
with one configuration. Your site administrator can use Single Point Operations
Configuration to specify which Status functions are prohibited for each user class as well
as to specify a default resource set for each user. For details, see the Single Point
Operations Administration and Configuration Guide.
2.3.6. Diagram Definitions
A diagram definition controls the operation of Status and the physical appearance of the
Status diagram and other Status windows. It includes the following information:
7833 4778–008 2–15

Setting Up Status
• Definitions of component groups and how the icons representing them are arranged
in the Status diagram and other group windows. Each component group is a
collection of components your site has decided to monitor through a single icon in
the Status diagram. For further information about the Status diagram, see 3.2.
Typically, when you click an icon that represents a component group, a table opens
listing all components belonging to that group. For a large group, you might want to
define subgroups. When you click the icon for such a group, a lower level group
window opens instead of a table. You can nest component groups in this hierarchical
fashion to any depth.
• Definitions of component table templates. A component table displays information
about individual components and their attributes. A template determines which
attributes (columns) appear in the table, and in what order. For further information
about component tables, see 3.4.
Status provides three default diagram definitions:
• Each Host Class Combination
The diagram definition contains a component group for each combination of host in
the configuration and class in the classification. The icons are arranged in rows by
host and in columns by class.
• Each Class
The diagram definition contains a component group for each class in the
classification, with components from all hosts represented in each component group.
The icons are arranged automatically in one to three rows, depending on the number
of component classes.
• Each Class With Subgroups For Each Host (Department and Enterprise Editions only)
The diagram definition contains a component group for each class in the
classification. Each of these groups has a subgroup defined for each host in the
configuration.
This choice creates a Status diagram that contains one group for each component
class, just as the second choice does. In addition, each top-level group has a
subgroup window that contains one group for each host to which the component
class applies.
For all diagram definitions, only the Status diagram window is initially displayed.
You can use these default diagram definitions as they are, or you can use them as
starting points for defining customized diagram definitions.
You can change the groups and tables that compose a diagram definition while Status is
running. If you create a combination of groups and tables that you want to save, you can
save this combination either as a new diagram definition or as a replacement of the
original diagram definition. For details, see Section 5.
Each diagram definition is associated with one specific combination of classification and
configuration. However, multiple diagram definitions can be associated with the same
2–16 7833 4778–008

Setting Up Status
combination of classification and configuration. This illustration shows the relationship of
diagram definitions to classifications and configurations.
Diagrams for
Classification A
and
Configuration 1
Diagram A
Diagram B
Diagram C
Classification
A
Configuration
1
Diagrams for
Classification B
and
Configuration 1
Diagram A
Diagram D
Diagrams for
Classification A
and
Configuration 2
Diagram A
Diagram E
Diagram F
Diagram G
Classification
B
Configuration
2
Diagrams for
Classification B
and
Configuration 2
None
Figure 2–6. Relationship of Diagram Definitions to Classifications and
Configurations
As illustrated here
• Three diagram definitions are available when you select Configuration 1 and
Classification A.
• Two diagram definitions are available when you select Configuration 1 and
Classification B.
• Four diagram definitions are available when you select Configuration 2 and
Classification A.
• No diagram definitions are available when you select Configuration 2 and
Classification B. In this case, Status asks you to select one of its default diagram
definitions.
All the diagram definitions here are distinct. Although a diagram definition named “A”
exists for three combinations, each diagram definition named “A” is different from the
others.
2.3.7. Component Sets
A component set is a named collection of explicitly defined components and the values
of their specified attributes, such as Expected Status and Instruction File. (Specified
attributes are component attributes whose values you specify within Status. Contrast
this with reported attributes, whose values are set by external agents sending event
reports to Status.)
7833 4778–008 2–17

Setting Up Status
Your site can create component sets that include defined components from only
selected hosts or classes. This lets you quickly change the expected values or instruction
files for only a subset of the components being monitored, rather than for all the
components. You may want to do this when certain events occur, such as a host
changing from attended to unattended mode.
Each component set definition is associated with one specific combination of
classification and configuration. However, many component sets can be associated with
the same combination of classification and configuration.
Component sets are not associated with specific diagram definitions or users. Once you
select a configuration and a classification to be monitored, you can select the diagram
and component sets independently. You can also change these independently of each
other.
For further information about component sets, see Section 6.
2–18 7833 4778–008

2.4. Starting and Terminating Status
Starting and Terminating Status
The following subsection describes different ways to start and stop a Status session.
2.4.1. Starting Status from Single Point Operations Console
The standard way to start Status is from Single Point Operations Console:
1. Click the Applications menu in the Single Point Operations Console main menu bar.
2. The Applications pull-down menu appears. Click Status.
3. After a short time, Status displays a dialog window showing the names of available
resource sets. Choose the desired resource set by double-clicking its name. (If a
default resource set was specified for your user name using Single Point Operations
Configuration, this window is omitted and this default resource set is automatically
selected. For further information, see the Single Point Operations Administration and
Configuration Guide.)
4. Status displays a dialog window showing the names of available classifications. (This
window is omitted if only one classification is available.) Choose the desired
classification by double-clicking its name.
5. Status displays a dialog window showing the names of component sets associated
with the combination of the current configuration and the classification you selected.
(This window is omitted if no component sets are associated with the combination.)
Choose any subset of these component sets by clicking their names, and then
clicking OK. The order in which you select component sets can be important,
because information in one component set may override information in another. If
you click Unknown, no component sets are selected.
6. Status displays a dialog window showing the names of the diagram definitions
associated with the combination of the current configuration and the classification
you selected. (This window is omitted if only one diagram is associated with the
combination.) Choose the desired diagram definition by double-clicking its name.
After completing this procedure, Status determines which components belong in each
component group and displays the selected Status diagram (see 3.2). Status is now
started.
When you start Status in this fashion, it automatically uses the configuration currently
selected for the instance of Single Point Operations Console from which you initiated
Status. When you make any of the following changes in Single Point Operations, the
same changes are automatically carried forward into Status:
• Select Configuration.
• Change to the Monitor attribute of any host or OS 2200 console (see 4.4, 4.5, and
4.6).
7833 4778–008 2–19

Starting and Terminating Status
2.4.2. Starting Status Independently of Single Point Operations
Console
You can also start Status independently of Single Point Operations Console, from the
Windows Start Programs menu on a Single Point Operations workstation.
Starting Status in this fashion lets you run Status with a configuration different from the
configuration currently used by Single Point Operations Console. It also allows you to run
Status without also running Single Point Operations Console.
When you start Status independently of Single Point Operations Console, you are asked
to specify the Single Point Operation server, configuration, resource set, classification,
component sets, and diagram, as follows:
1. On a Single Point Operations workstation, click the Start button, then Programs, then
Single Point Operationsx.y.z, then Single Point Operations Status.
2. Status displays a dialog window showing the Single Point Operations servers the
workstation can connect to choose the desired server by double clicking its name.
(This window is omitted if only one server is available.)
3. Status displays a dialog window showing the names of available Single Point
Operations configurations. (This window is omitted if only one configuration is
available.) Choose the desired configuration by double-clicking its name. After you
select the configuration, Status initializes communication with the various consoles
and hosts defined in the configuration.
4. Status displays a dialog window showing the names of available resource sets.
Choose the desired resource set by double-clicking its name. (If a default resource
set was specified for your user name using Single Point Operations Configuration,
this window is omitted and the default resource set is automatically selected. For
further information, see the Single Point Operations Administration and Configuration
Guide.)
5. Status displays a dialog window showing the names of available classifications. (This
window is omitted if only one classification is available.) Choose the desired diagram
by clicking its name.
6. Status displays a dialog window showing the names of component sets associated
with the combination of classification and configuration you selected. (This window is
omitted if no component sets are associated with the combination.) Choose any
subset of these component sets by clicking their names, and then clicking OK. The
order in which you select component sets can be important, because information in
one component set may override information in another. If you click Unknown, no
component sets are selected.
7. Status displays a dialog window showing the names of diagrams associated with the
combination of configuration and classification selected. (This window is omitted if
only one diagram is associated with the combination.) Choose the desired diagram
by double-clicking its name.
After you complete this procedure, Status determines which components belong in each
component group and displays the selected Status diagram (see 3.2). Status is now
started.
2–20 7833 4778–008

Starting and Terminating Status
2.4.3. Automatic Environment Setup on Initialization
Upon starting, Status examines the Windows environment variables SPOSERVER,
SPCONFIG, SPUSER, SPCLASSIFICATION, SPDIAGRAM, and SPCOMPONENTSET. For
each of these variables that is defined and has a nonnull value, Status uses the variable
as the name of the server, configuration, classification, diagram, or component set and
bypasses displaying the corresponding dialog window.
If a configuration, classification, diagram, or component set does not exist with the
specified name, Status displays a message and asks you to select another. You can
specify any subset of these variables independently of the others, and they apply only
when Status is started. They do not disable or affect the Select Configuration, Select
Classification, Select Diagram, and Retrieve Component Set menu items after Status has
started.
If you start Status from Single Point Operations Console, Status ignores SPCONFIG
because the configuration is taken from the current environment of Single Point
Operations Console.
The environment variable SPCOMPONENTSET can contain several names separated by
spaces. Also, if SPCOMPONENTSET is set to a null value, Status bypasses the “retrieve
component set” dialog window without selecting any component sets.
2.4.4. Terminating Status
If you started Status from Single Point Operations Console, terminating Single Point
Operations Console automatically terminates Status. To terminate Status before
terminating Single Point Operations Console, or to terminate Status when you started it
independently of Single Point Operations Console
1. Click File in the Status diagram menu bar (see 3.2). Status displays the File menu.
2. Click Exit. Status asks if you want to quit.
3. Click OK. This terminates Status.
If you have made changes to the current diagram that you have not saved, Status asks
whether you want to save these changes before it terminates.
7833 4778–008 2–21

Changing the Status Environment
2.5. Changing the Status Environment
Depending on whether you start Status from Single Point Operations Console or
independently, you can make various changes to the Status environment. For example,
while running Status, you may want to
• Select a different diagram definition
• Retrieve additional component sets
• Select a different configuration
• Select a different resource set
• Select a different trace level
The File menu in the Status diagram (see 3.2) lets you make these selections.
This subsection explains how to select a different classification, configuration, resource
set, and trace level. For information about selecting a different diagram definition,
see 5.5. For information about retrieving additional component sets, see 6.4.
2.5.1. Selecting a Different Classification
To select a different classification
1. Click File in the Status diagram menu bar.
2. Status displays the File menu. Click Select Classification.
3. Status displays a dialog window showing the names of all available classifications.
Select the desired classification. (Select Cancel if you decide not to change
classifications.)
4. Status displays a dialog window showing the names of all component sets
associated with the new combination of classification and configuration, and asks
you to select the component sets you want, if any. Select the desired component
sets.
5. Status displays a dialog window showing the names of all diagram definitions
associated with the new combination of classification and configuration, and asks
you to select a diagram definition. When you select a diagram definition, Status
displays it. If the new combination of configuration and classification has only one
diagram definition, Status does not display this dialog window and automatically
selects that diagram definition.
For example, you can perform this procedure to change from the classification
generalx.y.z to the classification TapeMonx.y.z in order to access the Tape Monitor
application.
2.5.2. Selecting a Different Configuration
If you started Status from Single Point Operations Console, the configuration used by
Status changes automatically when you select a different configuration in Single Point
2–22 7833 4778–008

Changing the Status Environment
Operations Console. You cannot change the current configuration directly from Status in
this case.
If you started Status independently of Single Point Operations Console, you can replace
the current configuration being monitored by Status with any other configuration
available to Status.
To replace the current configuration
1. Click File in the Status diagram menu bar.
2. Status displays the File menu. Click Select Configuration.
3. Status displays a dialog window showing the names of all available configurations.
Select the desired configuration. (Select Cancel if you decide not to change
configurations.)
4. Status displays a dialog window showing the names of all component sets
associated with the new configuration and the current classification, and asks you to
select the component sets you want, if any. Select the desired component sets.
5. Status displays a dialog window showing the names of the diagram definitions
associated with the new configuration and the current classification, and asks you to
select a diagram definition. When you select a diagram definition, Status displays it.
If the new combination of configuration and classification has only one diagram
definition, Status does not display the dialog window and automatically selects that
diagram definition.
When you initiate a configuration change, Status
• Terminates its connection with each console and host of the current configuration
• Clears any outstanding alarms that it initiated
• Initiates a connection with each console and host in the new configuration, and, if
applicable, initiates the OS 2200 or MCP data collection process
2.5.3. Selecting a Different Resource Set
You can replace the resource set Status is currently using with any other available
resource set as follows:
1. Click File in the Status diagram menu bar. Status displays a pull-down menu.
2. Click Select Resource Set. Status displays a dialog window showing the names of all
currently defined resource sets.
3. Select a new resource set, or select Cancel if you decide not to change the resource
set. Status reads the resource set specification and changes all open displays to the
new colors and fonts.
7833 4778–008 2–23

Changing the Status Environment
2.5.4. Selecting a Different Trace Level
For help in debugging event reports sent to Status by SMART AMS, CP-AMS, SP-AMS,
and other sources, you can have trace information sent to the log SP-STATUS. You can
view files in this log with the Log Viewer, which is described in the Single Point
Operations Console User Guide. Normally, Status writes no messages to this log.
To turn tracing on or off for Status
1. Click File in the Status diagram menu bar.
2. Click Select Trace Level.
3. Select the level of tracing you want:
• None—no trace messages are written to the log.
• Partial—event reports received by Status that cannot be processed completely
are written to the log, along with the reasons why they cannot be processed.
• Full—all event reports received by Status are written to the log.
After you set the trace level, it remains unchanged until you change it again or exit
Status. For further information about the trace messages logged by Status,
see Appendix A.
2–24 7833 4778–008

Section 3
Status Displays
This section describes the following Single Point Operations Status displays:
• Status windows
• Status diagram
• Subgroup windows
• Component tables
• Attribute list
• Dialog windows
7833 4778–008 3–1

Status Windows
3.1. Status Windows
Single Point Operations Status windows enable you to monitor components and retrieve
detailed information about components. The Status diagram is the primary window
because it lets you see a summary of all components at a glance. The other Status
windows are secondary windows; they let you view detailed information about one
component or a subset of components.
Typically, you keep the Status diagram (the primary window) on the screen at all times,
and bring up secondary windows only when you need more detailed information.
3.1.1. Window Features
Each Status window has a title identifying its purpose and a menu bar that, at a
minimum, lets you close the window and display help text about the window. If the
display size is larger than the window, scroll bars are added so you can see the entire
display. You can also control the size and location of each window by using the mouse.
The following illustration shows the display features. The title of the window appears on
the first line. The second line is the menu bar (the selections here are Window, Edit, and
Help). Note the presence of vertical and horizontal scroll bars.
Figure 3–1. Status Window Features
3–2 7833 4778–008

3.2. Status Diagram
Status Diagram
The Status diagram is the primary window of Single Point Operations Status and appears
automatically when you start Status. You cannot close the Status diagram except when
you terminate Status. However, it disappears momentarily when you perform certain
operations.
The Status diagram enables you to see a summary of all highest-level component groups
at a glance. This window contains a number of icons, each representing one component
group. A component group is a collection of components selected according to sitedefined
criteria based on the names, classes, and hosts of the individual components.
Your site defines the component groups, the shapes of the icons representing them, and
the arrangement of icons in the Status diagram, as described in Section 5.
This illustration is an example of the Status diagram for the classification generalx.y.z.
Figure 3–2. Example of a Status Diagram
Note: The Status diagram has no scroll bars. If you change the size of the Status
diagram using the window manager, the icons are repositioned proportionally within the
display.
3.2.1. Icon Descriptions
Each icon in the Status diagram is unique to depict the four different icon states. The
different colors and shapes indicate how the actual values of component attributes for
7833 4778–008 3–3

Status Diagram
each component group compare to expected values. This lets you see at a glance which
component groups contain components that currently need attention. The icons change
dynamically to reflect the current attribute values of components in each group.
This table describes the icon scheme available with the pixmap icons supplied with
Single Point Operations.
Color and Shape Attention Level Description
Green circle No attention No component in the group requires
attention. There are no exceptions
not marked as Seen. A component
has an exception when the actual
value of a component attribute does
not match one of the expected
values defined for the attribute. An
exception is marked as Seen when
the attribute Seen for the
component is set to yes.
Yellow triangle Attention At least one component in the group
has an attention-level exception not
marked as Seen. An attention-level
exception exists if any actual
attribute of the component does not
match any of its expected or alarm
values. No component has an
alarm-level exception not marked as
Seen.
Red octagon Alarm At least one component in the group
has an alarm-level exception not
marked as Seen. An alarm-level
exception exists if any actual
attribute of the component matches
any of its alarm values.
An alarm-level exception may cause
Status to raise an alarm in Single
Point Operations Console. This
occurs only if the component class
had alarm text specified when the
classification was defined using
Single Point Operations
Configuration. Depending on the
alarm-id specified for the attribute,
an alarm can trigger external actions
defined in the active alarm policy.
For further information, see Section
7 and the Single Point Operations
Administration and Configuration
Guide.
Blue square Empty The group currently contains no
components.
3–4 7833 4778–008

3.2.2. How the Status Diagram Is Updated
Status Diagram
Status automatically updates the Status diagram to reflect the current attribute values of
all components. If a component group contains exactly one component with an
attention-level exception, any of the following actions changes the icon from a yellow
triangle (attention) to a green circle (no attention):
• Status receives an event report for the component that changes the value of the
status attribute that caused the exception to an expected value.
• You change the expected values associated with the status attribute that caused the
exception to include the current value of the attribute.
• Status receives an event report for the component that changes the value of a
numeric attribute so that it is now within the attention threshold range.
• You change a numeric attention threshold value so that the current value of the
numeric attribute is now within the attention threshold range.
• You set the value of the Seen attribute for the component to yes.
Any of the following actions changes the icon to a red octagon (alarm), if it is not already
a red octagon:
• Status receives an event report for the component that changes the value of a status
attribute to an alarm value.
• You change the alarm values associated with a status attribute to include the current
value of the status attribute.
• Status receives an event report for the component that changes the value of a
numeric attribute so that it is below the minimum alarm threshold value or above the
maximum alarm threshold value.
• You change a numeric alarm threshold value so that the current value of the numeric
attribute is now outside the alarm threshold range.
• You set the value of the Seen attribute from yes to no, and the component has at
least one attribute with an alarm value.
Status automatically resets the Seen attribute for a component to no whenever
• The value of a status or numeric attribute changes because an event report was
received.
• You change an expected, alarm, or threshold value.
This ensures that previously setting the Seen attribute to yes does not mask a new
exception.
7833 4778–008 3–5

Status Diagram
3.2.3. Operator Action
When an icon change in the Status diagram indicates an exception, you should determine
the specific component causing the exception and take corrective action, if necessary.
To do this, click the icon of interest. Status then responds as described in the following
table.
If... Then...
The component group has subgroups Status opens a subgroup window, which
contains an icon for each subgroup in the
parent group. If any component in a subgroup
reaches the attention or alarm exception level,
the icons of both the subgroup and the parent
group are affected.
There is no table template associated
with the component group, and there
is only one component in the group
There is no table template associated
with the component group, and there
is more than one component in the
group
There is exactly one table template
associated with the component group
There are multiple table templates
associated with the component group
Status displays the attribute list for that
component immediately.
Status displays a dialog window listing all
components in the group. Select the
component of interest from the dialogue
window. Status displays the attribute list for
that component.
Status immediately displays a component table
using that template.
Status displays a dialog window containing the
names of all the table templates. Select the
template for the table that you want to display.
For further information about subgroups, see 3.3. For further information about
component tables, see 3.4. For further information about attribute lists, see 3.5.
3–6 7833 4778–008

3.2.4. Pull-Down Menus
Status Diagram
The Status diagram menu bar lets you display five pull-down menus: File, Tables,
Diagrams, Component Sets, and Help.
Click File to display the File menu. Use the File menu to make various changes to the
Status environment, such as selecting a different diagram definition, classification,
configuration, or resource set; retrieving component sets; and terminating Status. For
further information, see 2.5.
Click Tables to display the Tables menu. Use the Tables menu to display the following
tables:
• Components with Unexpected Values
• Components with Notes
• Unreported Components
For further information, see 3.4.
Click Diagrams to display the Diagrams menu. Use the Diagrams menu to define, save,
and delete diagram definitions. For further information, see Section 5.
7833 4778–008 3–7

Status Diagram
Click Component Sets to display the Component Sets menu. Use the Component Sets
menu to define, save, and delete component sets, and to remove unreported
components. For further information, see Section 6.
Click Help to display the Help menu. From this menu, you can display information about
the Status diagram, a summary of current information, or you can view the online Single
Point Operations document library.
The About entry displays a summary of current information, which includes
• Application name (Unisys Single Point Operations Status)
• Product level
• Product edition
• Copyright notice
• Single Point Operations server name
• Single Point Operations workstation name
• Name of secondary Single Point Operations server (if defined)
• Single Point Operations installation folder
• Single Point Operations data folder
• Single Point Operations log folder
• Current configuration
• Current user
• Current classification
• Current diagram definition
3–8 7833 4778–008

3.2.5. Window Backgrounds
Status Diagram
The background of a window is the fixed graphic that is displayed in the window behind
any icons displayed in the window. Status allows you to select a background for the
Status diagram, as well as any subgroup windows.
These backgrounds are of fixed size. If the background is smaller than the window, it is
tiled; if the background is larger, it is truncated. When you resize a component group
window, the icons within it are adjusted proportionally, so the icons move in relation to
the background.
The files defining the backgrounds you can select are located in the folder named
backgrounds in the Single Point Operations data folder on the Single Point Operations
server. When Single Point Operations is installed, it includes a number of background
files. You can define additional backgrounds using various graphical tools and add them
to this folder.
The formats that you can use for backgrounds are
• xbm (2-color)
• xpm (color)
• tif (color)
• jpg (color)
• bmp (color)
• png (color)
• pbm (black and white)
• pgm (grayscale)
• pnm (color)
• ppm (color)
These formats are the same formats used for icons within the Status diagram.
7833 4778–008 3–9

Subgroup Windows
3.3. Subgroup Windows
The Status diagram contains an icon for each highest-level component group defined in
the current diagram definition. In a simple environment, it is the only group window.
In a more complex environment, you may wish to define component groups in a
hierarchical fashion. At the highest level, you might define only a few fairly large groups,
each containing many components. Only the icons for these highest-level groups appear
in the Status diagram. The components in these highest-level groups can be further
categorized into subgroups.
As an example, the Status diagram might contain a group labeled Tapes, representing all
tape drives across all systems being monitored. This parent group could contain a
subgroup for each different system. Each subgroup would contain only the tape drives
for a single system.
When you click the icon of a parent group that has subgroups, a subgroup window
opens. A subgroup window appears and behaves very much like the Status diagram, but
contains icons only for the subgroups belonging to its parent group. Each icon in a
subgroup window varies in appearance just as those in the Status diagram. The actions
that occur when you click one of these icons are the same as the actions that occur in
the Status diagram.
3.3.1. Pull-Down Menus
Subgroup windows have a menu structure similar to that of the Status diagram, but
simpler.
Subgroup windows contain the following menus:
From the Help menu, you can display information about the subgroup window.
3–10 7833 4778–008

3.4. Component Tables
Component Tables
Component tables display information about the attributes of specific components.
There are five types of component tables; each has a different function. This table
describes the types of component tables.
Table Type Components Displayed
Component Group Either all components in a particular component group
(static behavior), or components in a particular
component group that have exceptions not marked as
Seen (dynamic behavior)
Components with
Unexpected Values
All components that currently have exceptions not
marked as Seen
Components with Notes All components that currently have operator notes
associated with them
Unreported Components All components for which no event reports were
received
Identical Components All components that represent the same physical
component as a selected component
3.4.1. Component Group Tables
A Component Group table provides information about individual components in a
component group. When you click an icon in the Status diagram or in a subgroup
window and the component group is associated with a table template, a table appears
using the template.
This illustration shows a Component Group table.
Figure 3–3. Component Group Table
7833 4778–008 3–11

Component Tables
The title bar identifies the component group associated with the table and displays the
number of components in the table.
The column headings identify the component attributes. Some attributes have actions
associated with them; the column headings for these attributes appear in a different font
(boldface, in the default resource set). To initiate the action, click the attribute value. For
further information about the actions associated with each attribute, see Section 4.
Click Help to display the Help menu. You can use this menu to display general
information about the table, or to display information about an individual column in the
table.
If your user class permits you to delete components, you can use the Delete menu in the
Component Group table, described later in this subsection.
Display Behaviors
Status lets you choose between two display behaviors for a Component Group table:
• Static—the table contains a row for each component in the component group.
• Dynamic—the table contains rows only for components in the group with exceptions
not marked as Seen (those components with an attention or alarm attribute value
and with Seen=no).
Note: When you define a table template for a component group, you can specify
whether the table is to be displayed as static or dynamic. If you do not specify this when
you define the table template, then Status asks whether you want static or dynamic
behavior before displaying a table using the template. For further information about
defining table templates, see 5.2.
Static Behavior
A static Component Group table contains a row for each component in the component
group represented by the corresponding Status diagram icon.
The order of the rows in the table is as follows:
• First, any components that currently have one or more exceptions, either alarm-level
or attention-level, for which the Seen attribute is n
• Next, any components that currently have one or more exceptions for which the
Seen attribute is set to yes
• Last, any components that currently have no exceptions
Once a static Component Group table appears, the order of the rows does not change. If
a component in the table later develops an exception, the position of the row does not
change, even if it is near the bottom of the table.
Dynamic Behavior
A dynamic Component Group table contains a row for each component in the group with
an exception not marked as Seen. A dynamic table may be empty at certain times. If a
component in the group develops an exception after the table appears, a row for that
3–12 7833 4778–008

Component Tables
component is added to the bottom of the table. A row for a component disappears from
the table if one of the following occurs:
• The exceptions for the component are resolved after the table appears.
• You set the Seen attribute for the component to yes.
As rows are added and removed, the component count in the title of the table changes.
Deleting Components
If your user class permits you to delete components, each Component Group table has a
Delete menu.
To delete components
• Click Delete. Status displays the Delete menu.
• Click Delete Components. Status displays a dialog window listing all components in
the component group. Each component is identified as host.class.name.
• Double-click to delete a single component. Click once on each component to select
multiple components to be deleted, then click OK. Status deletes the selected
components from the data model. Click Cancel if you decide not to delete any
components.
Note: If your user class does not permit you to delete components, the Component
Group tables do not have a Delete menu.
Templates
A Component Group table template specifies the subset of component attributes that
appear when you click a component group icon. Status allows you to define multiple
Component Group table templates. Each component group can be associated with one
or more of these table templates, and many component groups can be associated with
the same table template.
As installed, Status includes a few generic Component Group table templates, each with
a small number of attributes (columns). The names of these templates indicate the
columns they contain. Also included is a table template specifically intended for the Tape
Monitor application.
Status automatically creates a table template with the same name as the class for each
component class in the current classification. Each of these table templates is
specifically tailored to the associated class and contains columns for the site-defined
attributes in the class.
You can
• Change the attribute columns included in these table templates and their order
• Create new Component Group table templates
• Change the table templates associated with each component group
7833 4778–008 3–13

Component Tables
For further information about these procedures, see 5.2.
3.4.2. Components with Unexpected Values Table
The Components with Unexpected Values table contains a row for each component that
currently has at least one exception, either attention-level or alarm-level, and for which
the Seen attribute is no.
If you open this table from the Status diagram, it includes all such components currently
monitored by Status. If you open this table from a subgroup window, it includes only
components that are within the subgroup.
This illustration shows a Components with Unexpected Values table.
Figure 3–4. Components with Unexpected Values Table
To display a Components with Unexpected Values table
1. Click Tables in the menu bar of the Status diagram or a subgroup window. The
Tables menu appears.
2. Click Components with Unexpected Values.
Status dynamically updates the following information in this table:
• The attribute values displayed
• The color highlighting of unexpected values for reported attributes
• The rows in the table, as components develop exceptions and as exceptions are
resolved or marked as Seen
3–14 7833 4778–008

Status adds a row at the bottom of the table when
Component Tables
• A component not already in the table develops an exception because the actual value
of an attribute changed or you changed an expected attribute value.
• You reset the Seen attribute for a component with an exception from yes to no from
another component table or attribute list.
Status removes a row from the table when one the following occurs:
• A component in the table has all its exceptions resolved because the actual values of
attributes changed or you changed the expected attribute values.
• You set the Seen attribute for a component in the table from no to yes.
To change the Seen attribute from no to yes
1. Click the current Seen attribute value. Status displays a window with choices yes or
no.
2. Click yes. The row for the component disappears from the table. (Click no if you
decide not to change the Seen attribute.)
Click Help to display the Help menu. You can use this menu to display general
information about the table, or to display information about an individual column in the
table.
3.4.3. Components with Notes Table
The Components with Notes table contains one row for each component that currently
has a note file associated with it, and one row for each component for which you are
editing a new note. If you open this table from the Status diagram, it includes all such
components currently monitored by Status. If you open this table from a subgroup
window, it includes only components that are in the subgroup.
This table, shown here, lets you determine quickly which components currently have
notes attached.
7833 4778–008 3–15

Component Tables
Figure 3–5. Components with Notes Table
To display a Components with Notes table
1. Click Tables in the menu bar of the Status diagram or a subgroup window. The
Tables menu appears.
2. Click Components with Notes.
Status dynamically updates the values and the rows in the table. When you attach a
note to a component that previously did not have one, Status adds a row for that
component at the bottom of the table. When you delete a note for a component
currently in the table, Status removes the row for that component from the table.
Click Help to display the Help menu. You can use this menu to display general
information about the table or to display information about an individual column in the
table.
3.4.4. Unreported Components Table
The Unreported Components table contains one row for each unreported component. If
you open this table from the Status diagram, it includes all such components currently
monitored by Status. If you open this table from a subgroup window, it includes only
components that are within the subgroup. The Unreported Components table lets you
quickly identify unreported components.
A component is unreported when you have defined a set of values for it, but Status has
received no event report for it. The absence of an event report may indicate that the
component does not actually exist in the host system, or that the process for generating
event reports for the component is faulty. A component can exist for which no
associated event reports were generated yet.
This illustration shows an Unreported Components table.
3–16 7833 4778–008

Figure 3–6. Unreported Components Table
To display an Unreported Components table
Component Tables
1. Click Tables in the menu bar of the Status diagram or a subgroup window. The
Tables menu appears.
2. Click Unreported Components.
Status dynamically updates the values and the rows in this table. When Status receives
an event report for a component currently in the table, it removes the row for the
component from the table.
Click Help to display the Help menu. You can use this menu to display general
information about the table or to display information about an individual column in the
table.
3.4.5. Identical Components Table
Multiple Status components can refer to the same physical component, if the actual
component is known or reported through multiple hosts. For example, three Status
components called P1 may all refer to the same printer used by hosts X, Y, and Z. Use
an Identical Components table to display all Status components that refer to a particular
physical component.
This illustration is an example of an Identical Components table.
7833 4778–008 3–17

Component Tables
Figure 3–7. Identical Components Table
To display an Identical Components table, click the Identical Components attribute in the
attribute list for a component. For further information, see 4.2.
An identical components table for a component identifies the component for which you
opened it in its title. You can display an identical components table for more than one
component at the same time.
Click Help to display the Help menu. You can use this menu to display general
information about the table or to display information about an individual column in the
table.
3–18 7833 4778–008

3.5. Attribute List
Attribute List
An attribute list shows all attributes that apply to one particular component. (Contrast
this with a component table, which shows only selected attributes for many
components.) The attribute list contains one line for each attribute. Each line contains
the attribute name and attribute value. For site-defined attributes (see 4.3), the attribute
name is determined from the class to which the component belongs. Each component
class has a unique attribute list.
Status dynamically updates values in an attribute list whenever the values change.
Unexpected values are highlighted in color just as in the component tables. If you are
using the default resource set, attention-level exceptions appear in yellow and alarm-level
exceptions appear in red.
For detailed information about individual attributes, see Section 4.
The following illustration shows an attribute list.
7833 4778–008 3–19

Attribute List
Figure 3–8. Attribute List
3.5.1. Displaying an Attribute List
To display an attribute list for a component
• Click the component name in any component table that includes the component. A
pop-up menu appears. Click Attribute List in that menu. An hourglass appears for a
3–20 7833 4778–008

Attribute List
short time, and then the attribute list is displayed. (If the pop-up menu would contain
only one item, the attribute list is displayed immediately.)
• Click a group icon in the Status diagram. If the group does not contain subgroups
and there is no table template associated with the group, an attribute list is
displayed. If the group contains a single component, its attribute list appears
immediately. If the group contains multiple components, a dialog window asks you
to select which attribute list to display.
3.5.2. Attribute List Menus
The attribute list contains the following menus:
• Window
From this menu, you can print the attribute list or close it.
• Display
From this menu, you can display or edit the notes associated with the component,
display the instructions defined for the component, or display the full Message value
for the component.
• Applications
From this menu, you can launch an external application on behalf of the component.
For further information on external applications, see 1.3.
• Delete
From this menu, you can delete the component displayed in the attribute list from
the Status data model.
• Help
From this menu, you can display general information about the list or information
about an individual attribute in the list.
3.5.3. Initiating Actions
Some attributes have actions associated with them; the names of these attributes
appear in a different font (boldface, in the default resource set). To initiate the action,
click the attribute name (not the attribute value). For further information about the
actions associated with each attribute, see Section 4.
7833 4778–008 3–21

Attribute List
3.5.4. Deleting Components
If your user class permits you to delete components, the attribute list has a Delete menu.
To delete the component
1. Click Delete. Status displays the Delete menu.
2. Click Delete Component. Status displays a dialog window and asks whether you
really want to delete the component.
3. Click Yes. Status deletes the component from the data model and closes the
attribute list.
Note: If your user class does not permit you to delete components, the attribute list
does not have a Delete menu.
3–22 7833 4778–008

3.6. Dialog Windows
Dialog Windows
A dialog window appears when Status prompts you for further information. These
windows usually appear after you have selected a menu item that requires more
information. This illustration shows a typical dialog window.
3.6.1. Entering Information
Figure 3–9. Dialog Window
You can enter the requested information by clicking the choices displayed in the middle
panel of the dialog window.
In some dialog windows, you can select a single value or multiple values. To select a
single value, double-click the value. To select multiple values, click once on each value,
then click OK. To deselect a value you have already selected, click again on its
highlighted value before you click OK.
3.6.2. Dialog Window Buttons
Most dialog windows provide the buttons listed in this table to help you edit your input.
Button Function
OK Closes the dialog window and sends your input to Status.
Cancel Cancels and closes the dialog window. If you click Cancel, the operation
you requested is not performed.
Unknown Resets the value to Unknown and closes the dialog window; no value is
specified for the attribute. If you are adding something, you must select a
value other than Unknown. Click the Explain button to get specific
information about Unknown for any particular dialog window.
Clear Clears the current value from the input area; the dialog window remains
open.
7833 4778–008 3–23

Dialog Windows
Button Function
Editor Enables multiple lines of text to be entered.
Explain Provides more information about the value you are asked to supply.
Once you open a dialog window or any window that needs more information, you must
provide the information or click Cancel to continue. Status does not allow you to open
any other windows or perform any other actions until you have entered the information
and closed the dialog window.
Some dialog windows do not include a list of choices. For these windows, you must
type on the input line. If the dialog window allows multiple values and you want to enter
multiple values, press Enter after each value.
In some situations, a dialog window might open with its buttons covered by the
Windows icon bar. To view the buttons, use the mouse to move the icon bar.
Note: Status accepts input only if the pointer is on the input line when you are typing in
a new value.
3–24 7833 4778–008

Section 4
Component Attributes
This section describes the component attributes displayed in attribute lists and
component tables. The section provides information about
• Types of attributes
• Attributes that apply to all component classes
• Site-defined attributes
• Attributes specific to various component classes
7833 4778–008 4–1

Types of Attributes
4.1. Types of Attributes
Attributes can be categorized in a number of different ways, as described in the following
subsections.
4.1.1. Reported and Specified Attributes
Single Point Operations Status maintains information about components in the form of
attributes. An attribute is a named property of a component; it can have certain values
that describe an aspect of the current state of the component. Attributes appear in
component tables and attribute lists.
There are two categories of attributes based on the source of the attribute values. This
table explains each category.
Category Source of Attribute Values
Reported attributes Values come from event reports from a managed host, an
application program, a system console, or from Single Point
Operations itself. There are four types of reported attributes:
status attributes, string attributes, numeric attributes, and list
attributes.
Specified attributes Values are specified within Status by you or by the Single
Point Operations administrator.
4.1.2. Attribute Data Types
There are four types of attributes in Status based on the data values the attribute can
attain:
• Status attributes
These attributes can attain any one of a limited number of predefined character
string values. Each of these predefined values can be classified as expected,
attention, or alarm.
• String attributes
These attributes can attain any character string value.
• Numeric attributes
These attributes can attain any integer value. Ranges of these values can be
classified as expected, attention, or alarm.
• List attributes
These attributes can assume multiple character strings as their values.
4–2 7833 4778–008

4.1.3. Status Attributes
Types of Attributes
A status attribute can assume one of a limited number of predefined character string
values (for example, up or down). Two specified attributes are associated with each
status attribute:
• An attribute listing the expected values of the status attribute (for example, up)
• An attribute listing the alarm values of the status attribute (for example, down)
For each status attribute, you select the expected and alarm values for each component.
Any values that are not designated as expected or alarm values are considered attention
values. When the value of a status attribute is an expected value, it is of no concern to
the operator. If the value of the status attribute changes to an alarm or attention value,
Single Point Operations Status directs the operator's attention to this change.
If the value of a status attribute changes to an alarm value, Status can be configured to
raise an alarm in Single Point Operations Console. This occurs only if the component
class has alarm text specified and an alarm-id has been specified for the attribute. These
are specified using Single Point Operations Configuration as described in 7.5. Depending
on the alarm-id specified for the attribute, an alarm can trigger external actions defined in
the active alarm policy.
The Single Point Operations administrator can define up to eight site-defined status
attributes for each component class. The names and allowed values of the site-defined
status attributes vary from one component class to another.
By default, all components monitored by Status have one status attribute with the name
of “Status.” The Single Point Operations administrator can change the name of this
attribute or eliminate it entirely. This attribute reports the primary state of each
component.
Each status attribute can have a timeout period and default value. If the Single Point
Operations administrator specifies a timeout period, Status automatically resets the
attribute to its default value if no event report is received for the attribute during the
timeout period. This is useful, for example, when an agent reports the attribute value on
a periodic basis, and you want to be notified if this agents stops reporting.
[OS 2200]
For OS 2200 systems, the OS 2200 data collector reports a value for the default Status
attribute for each hardware component other than the system consoles. The OS 2200
data collector is part of the OMKEY background run.
The possible values for the default Status attribute of OS 2200 hardware components are
as follows:
• UP
• DOWN
• SUSPENDED
• RESERVED
7833 4778–008 4–3

Types of Attributes
• NOT AVAILABLE
For all types of OS 2200 hardware components, Status attribute values in event reports
are all uppercase.
[MCP]
For MCP systems, the MCP data collector reports a value for the default Status attribute
of disk drive, tape drive, and printer hardware components. The MCP data collector is
part of the Single Point Operations Interface for ClearPath MCP.
4.1.4. String Attributes
A string attribute can assume any character string as its value. There is no limit to the
length of the character string. However, various displays in Status may show only the
initial portion of long strings.
You cannot specify expected values and alarm values for a string attribute. You can use
string attributes to display values of interest to an operator but not to direct the
operator's attention to a component.
All components monitored by Status have two string attributes named Message and
Event Report Time. The Message attribute lets your site associate any message text
with a component; the Event Report Time attribute (TIME) identifies when the latest
event report associated with the component was received.
The Single Point Operations administrator can define up to eight additional site-defined
string attributes for each component class. The names of these site-defined string
attributes vary from one component class to another. When defining a classification
using the Single Point Operations Configuration application, the Single Point Operations
administrator can associate each site-defined string attribute with a status or numeric
attribute in the same component class. If the Single Point Operations administrator does
this, Status displays the string attribute with the same color coding as the associated
attribute. For further information, see Section 7.
4.1.5. Numeric Attributes
A numeric attribute can assume any integer as its value. You can designate ranges of
these values as expected, attention, and alarm values. Do this using two pairs of
specified attributes that are associated with each numeric attribute:
• Minimum and maximum attention threshold values
• Minimum and maximum alarm threshold values
You can specify these threshold values component by component, and you can leave any
or all of them unspecified.
If you specify all four threshold values, the values of the attribute are split into five
ranges, as follows:
4–4 7833 4778–008

Types of Attributes
When the value of a numeric attribute is in range C, between the minimum and
maximum attention threshold values (inclusive), it is considered an expected value and of
no concern to the operator.
If the attribute value falls below the minimum attention threshold but is still above the
minimum alarm threshold, it is in range B. If the attribute value rises above the
maximum attention threshold but is still below the maximum alarm threshold, it is in
range D. Within either of these ranges, the component has an attention-level exception.
This is brought to your attention by an icon changing color or shape in the Status
diagram. By default, attention-level exceptions are shown by an icon becoming yellow.
If the attribute value falls below the minimum alarm threshold, it is in range A. If the
attribute rises above the maximum alarm threshold, it is in range E. Within either of
these ranges, the component has an alarm-level exception. This is brought to your
attention by an icon changing color or shape in the Status diagram. By default, alarmlevel
exceptions are shown by an icon becoming red. In addition, Status can be
configured to raise an alarm in Single Point Operations Console for an alarm-level
exception. This occurs only if the component class has alarm text specified and an
alarm-id has been specified for the attribute. These are specified using Configuration
application, as described in 7.3 and 7.5. Depending on the alarm-id specified for the
attribute, an alarm raised by Status can trigger external actions defined in the active
alarm policy.
The Single Point Operations administrator can define up to eight site-defined numeric
attributes for each component class. The names and threshold values of the site-defined
numeric attributes vary from one component class to another. For further information,
see 7.5.
4.1.6. List Attributes
A list attribute can simultaneously assume any number of character strings as its value.
There is no limit to the number of character strings or to the length of each character
string. However, various displays in Status may show only the initial item of a list.
You cannot specify expected and alarm values for a list attribute. You can use list
attributes to display values of interest to an operator but not to direct the operator's
attention to a component.
7833 4778–008 4–5

Attributes That Apply to All Component Classes
4.2. Attributes That Apply to All Component
Classes
4.2.1. Name
4.2.2. Host
4.2.3. Class
This attribute identifies the name of the component as it is known to the host or agent
that reports its attributes. Once a component has been created in Status, its name
cannot change.
If you click the Name attribute in a component table, a pop-up menu appears. This menu
allows you to display the attribute list for that component, edit or display the notes
associated with that component, display the instructions defined for that component,
display the full Message value for that component, or launch an external application on
behalf of that component. Only applicable items are included in this menu. If displaying
the attribute list would be the only choice, the attribute list opens immediately instead.
This attribute identifies the name of the host system that reports the attribute values of
the component. The host is one of those specified in the configuration under which
Status is currently operating. For a component which itself represents a host system,
the Name and Host attributes have the same value. When you click the Host attribute,
no action occurs.
This attribute identifies the component class to which the component belongs. When
you click the Class attribute, no action occurs.
[OS 2200]
Typically, the class of a component never changes once the component has been
created. However, when Status receives an event report identifying a component of the
Device class more specifically as a disk drive or tape drive, it changes the class
accordingly. The Device class is defined in classifications general (see 1.3.2),
Unix2200Mon, and OS2200Mon see (Appendix E).
4.2.4. Exceptions
This attribute shows the number of exceptions currently outstanding for the component.
Each reported attribute with an unexpected value (attention or alarm) counts as one
exception. When there are one or more exceptions for a component, the Exceptions
attribute in component tables and attribute lists is displayed in the colors of the most
severe exception. This is red for alarm exceptions and yellow for attention exceptions.
Click the Exceptions attribute to display the Instructions window for the component.
This window contains any operator instructions your site has defined for the component.
4–6 7833 4778–008

4.2.5. Seen
4.2.6. Notes
Attributes That Apply to All Component Classes
This specified attribute indicates whether you have noted the exceptions (if any)
associated with the component and no longer want this component to affect icon colors
in the Status diagram. The Seen attribute can have the value yes or no. If your user class
allows it, you can change this value.
When the value is yes, the component
• Does not cause any component group icons to change color.
• Does not appear in the Components with Unexpected Values table or in any dynamic
Component Group table.
Status automatically sets the Seen attribute of a component to no whenever
• The value of a status or numeric attribute for the component changes.
• You change an expected, alarm, or threshold value for the component.
The action that occurs when you click the Seen attribute in a component table varies,
depending on how the template for the component table was defined (see 5.2):
• Seen (toggle)
When you click the Seen attribute, it toggles from yes to no or from no to yes.
• Seen (dialog)
When you click the Seen attribute, Status displays a dialog window asking you to
select the new value.
• Seen (delete)
When you click the Seen attribute, Status displays a dialog window asking you to
select the new value. If you select yes and your user class permits you to delete
components, Status displays another dialog window asking whether the component
should be deleted. If you click yes, Status deletes the component from its data
model. (If your user class does not permit you to delete components, Status does
not ask whether the component should be deleted.)
Certain attribute values can cause Status to raise an alarm in Single Point Operations
Console. The value of the Seen attribute in Status does not affect these alarms. If a
component that caused an alarm to be raised has its Seen attribute set to yes, the alarm
remains raised.
This attribute indicates whether any operator notes are associated with this component.
The Notes attribute can have the value yes or no. Status automatically sets the value
based on whether a notes file exists for the component.
7833 4778–008 4–7

Attributes That Apply to All Component Classes
Click the Notes attribute to display an edit window containing the note text (if any)
associated with the component. While the Notes edit window is open, the value of the
Notes attribute changes to “-“ (unknown) to remind you that the notes file for that
component is being edited. If your user class allows it, you can make changes to the
note text in the edit window.
Follow these guidelines when working with note text:
• When you enter text, an insertion point (a flashing vertical bar) indicates where the
text appears.
• Use the arrow keys to move the insertion point. Press Enter to move the insertion
point to the next line.
• Press Delete to delete text.
• You can copy text from any open window on your screen using Ctrl-C, move the
mouse pointer to the desired location in the edit window, click to move the insertion
point to that location, and press Ctrl-V to paste the selected text in the edit window.
When you close the edit window, you can save the changes you made, discard the
changes, or delete the notes file if your user class allows you to perform these actions.
4.2.7. Message
This reported string attribute contains the latest message string received by Single Point
Operations Status for this component in an event report.
Note: Not every event report need specify a value for this attribute. Therefore, the
Message attribute does not necessarily reflect the latest event report received for the
component.
In component tables and the attribute list, the Message attribute may be truncated.
When you click the attribute, Status displays a window containing the entire message.
4.2.8. Event Report Time
This reported string attribute gives the latest time associated with an event report
received for the component by Single Point Operations Status. This time reflects a time
value reported by the sender of the event report, not the time the event report is
received by Status. When you click this attribute, no action occurs.
Note: Not every event report need specify a value for this attribute. Therefore, the
Event Report Time attribute does not necessarily reflect the time of the latest event
report received for the component.
The name of the attribute associated with Event Report Time is TIME. The value of this
attribute is free format since Status displays the time, but does not use the time for
calculations.
4–8 7833 4778–008

4.2.9. Event Received
Attributes That Apply to All Component Classes
This reported attribute indicates whether at least one event report was received for the
component since you selected the current configuration and classification. The Event
Received attribute can have the value yes or no. Components for which no event report
were received may not actually exist, or the mechanism that reports on these
components possibly might not have been initiated or might be faulty. The value of this
attribute controls whether the component is included in the Unreported Components
table. (See 3.4.) When you click this attribute, no action occurs.
4.2.10. User Defined
This specified attribute indicates whether the component was defined by some action
you took. The User Defined attribute can have the value yes or no. A value of yes
indicates either that you defined the component explicitly (see 6.1), or that the
component was included in a component set you retrieved earlier. (See 2.4 and 6.4.)
When you click this attribute, no action occurs.
4.2.11. Groups
This list attribute contains the name of each component group to which the component
belongs. When a component is created, Status automatically determines the groups to
which the component belongs based on the membership criteria specified for each
group. For further information, see 5.1.
Status displays the names of as many component groups as can fit on the line. Click the
attribute to display a window containing the entire list.
4.2.12. Component Scope
This attribute indicates whether the scope of the component is limited to a single host or
includes all hosts monitored by Status.
This table explains the possible values of the Component Scope attribute.
Value Meaning
Host The scope of the component is limited to a single host. Two
components with the same name and class on different hosts refer
to different actual components. For example, components
representing OS 2200 runs or UNIX processes always have a scope
of Host.
Shared The scope of the component includes all hosts monitored by
Status. Two logical components with the same name and class and
with a scope of Shared model the same actual component. For
example, specify a scope of Shared for disks that are shared across
multiple systems.
7833 4778–008 4–9

Attributes That Apply to All Component Classes
4.2.13. Identical Components
This attribute identifies all other components monitored by Status that model the same
actual component. Status automatically determines the value of this attribute based on
the component’s name, host, class, and scope.
A value of Unknown indicates that no other monitored component models the same
actual component. The value can be other than Unknown only if the scope of the
component is Shared.
Click this attribute to display the Identical Components table for the component. This
table contains a row for each component that refers to the same actual component.
However, if the value is Unknown, a message appears instead, indicating that this
component is not identical to any other component.
4–10 7833 4778–008

4.3. Site-Defined Attributes
4.3.1. Site-Defined Status Attributes
Site-Defined Attributes
The Single Point Operation administrator can define up to eight site-defined status
attributes along with associated expected status and alarm status attributes for each
component class. The Single Point Operations administrator specifies each attribute
name, which is class specific.
This table describes how Status displays these attributes in component tables and
attribute lists.
When Status displays...
Then the column header or attribute
label is...
A site-defined status attribute The site-defined attribute name
The expected status attribute
associated with a site-defined status
attribute
The alarm status attribute associated
with a site-defined status attribute
The site-defined attribute name preceded by
the word Expected
The site-defined attribute name preceded by
the word Alarm
When the value of a status attribute for a component is not an expected value
• The value and its background are displayed in alternate colors (yellow for an attention
value, red for an alarm value) in component tables and attribute lists.
• The value of the Exceptions attribute for the component increases by one.
• The icons of any groups containing the component are displayed in yellow or red,
unless you have set the Seen attribute for the component to yes.
If the unexpected value is an alarm value, Status can be configured to raise an alarm in
Single Point Operations Console. This occurs only if the component class has alarm text
specified and an alarm-id has been specified for the attribute. Depending on the alarm-id
specified for the attribute, an alarm raised by Status can trigger external actions defined
in the active alarm policy. For further information, see 7.3 and 7.5.
Expected Values
This specified attribute contains a list of all expected values for the corresponding status
attribute. In a component table, the values are listed one per line.
If your user class allows it, you can change the expected values of any component. Click
the Expected attribute to display the current list of expected values and a menu of all
possible values for the attribute, except those previously selected as alarm values. The
list may include a hyphen (-) to indicate an unreported value. Unreported values, like
reported values, can be treated as normal, attention, or alarm.
7833 4778–008 4–11

Site-Defined Attributes
Alarm Values
You can select any values from this menu to form a new list of expected values. Click
Cancel to leave the list of expected values unchanged. Click Unknown to remove all
expected values. If you click Unknown, the next nonalarm value received by Single Point
Operations Status for the attribute becomes its only expected value.
This specified attribute contains a list of all alarm values for the corresponding status
attribute. In a component table, the values are listed one per line.
An alarm value causes the icons of any groups containing the component to appear in
red in the Status diagram and subgroup window. It may also cause Status to raise an
alarm in Single Point Operations Console. This occurs only if the component class had
alarm text specified and an alarm-id was specified for the attribute when the
classification was defined. The severity of the alarm is taken from the component class
definition. Depending on the alarm-id specified for the attribute, the alarm can trigger
external actions defined in the active alarm policy. For further information, see 7.3 and
7.5.
If your user class allows it, you can change the alarm values of any component. Click the
Alarm attribute to display the current list of alarm values and a menu of all possible
values for the attribute, except those previously selected as expected values. The list
may include a hyphen (-) to indicate an unreported value. Unreported values, like reported
values, can be treated as normal, attention, or alarm.
You can select any values from this menu to form a new list of alarm values. Click
Cancel to leave the list of alarm values unchanged. Click Unknown to specify that no
values indicate an alarm condition for that attribute.
4.3.2. Site-Defined Numeric Attributes
The Single Point Operations administrator can define up to eight site-defined numeric
attributes along with the two pairs of associated threshold attributes for each component
class. The Single Point Operations administrator specifies the attribute names, which are
class specific.
This table describes how Status displays these attributes in component tables and
attribute lists.
When Status displays... Then the column header or attribute label is...
A site-defined numeric attribute The site-defined attribute name.
A site-defined threshold attribute The site-defined attribute name preceded by the
appropriate one of the following: Min Attn, Max Attn,
Min Alarm, or Max Alarm.
When a numeric attribute for a component attains an integer value outside the attention
threshold range
4–12 7833 4778–008

Site-Defined Attributes
• The value and its background appear in alternate colors (yellow for an attention value,
red for an alarm value) in component tables and attribute lists.
• The value of the Exceptions attribute for the component increases by one.
• The icons of any groups containing the component are displayed in yellow or red,
unless you have set the Seen attribute for the component to yes.
If the value is also outside the alarm threshold range, the Single Point Operations
administrator can configure Status to raise an alarm in Single Point Operations Console.
This occurs only if the component class has alarm text specified and an alarm-id has
been specified for the attribute. The severity of the alarm is taken from the component
class definition. Depending on the alarm-id specified for the attribute, an alarm raised by
Status can trigger external actions defined in the active alarm policy. For further
information, see 7.3 and 7.5.
If your user class allows it, you can change threshold values. When you click the
numeric attribute itself, no action occurs. However, when you click an associated
threshold attribute, Status displays the current threshold value and lets you remove or
replace it. You can leave any or all threshold values unspecified, in which case they do
not apply to the corresponding numeric attribute.
Normally, a numeric attribute has an integer value. However, before any event report
sets its value, its value is unknown. This is indicated by a hyphen (-) in component
tables. As described in 7.5, the Single Point Operations administrator can configure
Status to treat an unknown value as an expected, attention, or alarm value.
4.3.3. Site-Defined String Attributes
The Single Point Operations administrator can define up to eight site-defined string
attributes for each component class. The Single Point Operations administrator specifies
the attribute names, which are class specific. When Single Point Operations Status
displays a site-defined string attribute in a component table or attribute list, the column
header or attribute label is the site-defined attribute name.
Your site administrator can associate a site-defined string attribute for a particular
component class with a status or numeric attribute defined for that class. In this case,
Single Point Operations Status displays the string attribute with the same color-coding as
the associated attribute. For further information, see 7.5.
When you click a site-defined string attribute, no action occurs.
7833 4778–008 4–13

Attributes Specific to the OS 2200 Host Component Class [OS 2200]
4.4. Attributes Specific to the OS 2200 Host
Component Class [OS 2200]
Each classification can contain one component class that models OS 2200 host systems.
This class has OS_2200 specified as its Internal Class. (See 7.3.) In Status, this class
contains one component for each OS 2200 host system in the current configuration.
Components in this class must have a status attribute named “Status.“ In addition, these
components have the special attributes described in the subsections that follow. These
special attributes are displayed only in the attribute lists of these components; you
cannot include them in component tables.
4.4.1. Exec Level
This reported string attribute identifies the current Exec level for the host, as reported by
the data collector running on the host. When you click this attribute, no action occurs.
4.4.2. Site-Id
This reported string attribute identifies the site-id for the host, as reported by the data
collector running on the host. Single Point Operations Status compares this string to the
site-id of the host specified in the current configuration. If they do not match, Single
Point Operations Status
• Displays the attribute value in the alarm color (red) in the attribute list for this
component.
• Displays the icon of any group containing this component in the alarm color.
• Increases the value of the Exceptions attribute for the component by one.
• Raises an alarm of major severity in Single Point Operations Console if it is thus
configured. This occurs only if the Single Point Operations administrator specified
alarm text for the component class when the classification was defined. The alarm-id
is the component class name followed by ”.SiteId.” For further information, see 7.3.
When you click this attribute, no action occurs.
4.4.3. Data Collection
This reported status attribute indicates the status of data collection for the host. Data
collection is a function provided by the OMKEY background run, which is released as part
of SMART, included with the Integrated Operating Environment (IOE). The OMKEY
background run must be installed and running on the OS 2200 host. For further
information, see 2.1.
For OS2000 systems, the Data Collection attribute can have one of the following values:
• not_started
• ready
• keyin_unacknowledged
4–14 7833 4778–008

Attributes Specific to the OS 2200 Host Component Class [OS 2200]
• initiated
• in_progress
• completed
• errored
• OMKEY_not_running
When the value of the Status attribute for the host is up, the only expected value of the
Data Collection attribute is completed. Any other value is treated as an unexpected
value.
When the value of Data Collection is other than completed, errored, or
OMKEY_not_running
• The attribute appears in the attention color (yellow) in the attribute list for this
component.
• The icon of any component group containing the host component appears in the
attention color (yellow).
OMKEY_not_running and errored are unexpected alarm values and appear in the alarm
color (red) in displays. Start the OMKEY background run on the OS 2200 host to resolve
the OMKEY_not_running condition. The value errored represents an internal error
condition.
If the Single Point Operations administrator specified alarm text for the component class,
these two values cause Status to raise an alarm in Single Point Operations Console. The
alarm-id is the component class name followed by ”.DataCollection”. For further
information, see 7.3.
When you click this attribute, no action occurs.
4.4.4. Connected Consoles
This list attribute identifies all consoles through which Single Point Operations Status is
connected to this host. Single Point Operations Status displays as many console names
as can fit on the line. Clicking this attribute produces no action.
4.4.5. System Type
This string attribute identifies the system type (for example, IX-2200) for the host, as
reported by the data collector running on the host. Clicking this attribute produces no
action.
7833 4778–008 4–15

Attributes Specific to the OS 2200 Host Component Class [OS 2200]
4.4.6. Application Initialization
Single Point Operations Status automatically sends an initialization command (console
keyin) to the OMKEY data collector on the host when all of the following conditions are
true:
• Value of Status for the OS 2200 host is up.
• The host is connected to the Single Point Operations server through at least one
system console, and that console is sending continuous display messages to the
Single Point Operations server.
• The Data Collection attribute has the value not_started or ready.
• There is at least one component class in the classification with System
Types = OS2200 and for which an initialization mnemonic was specified. (See 7.3.)
4–16 7833 4778–008

Attributes Specific to the OS 2200 Console Component Class [OS 2200]
4.5. Attributes Specific to the OS 2200 Console
Component Class [OS 2200]
Each classification can contain one component class that models OS 2200 consoles.
This class has CONSOLE specified as its Internal Class. (See 7.3.) In Status, this class
contains one component for each OS 2200 console in the current configuration.
Components in this class must have a status attribute named “Status.” In addition,
these components have the special attributes described in the subsections that follow.
These special attributes are displayed only in the attribute lists of these components; you
cannot include them in component tables.
4.5.1. Monitor
This attribute indicates whether Single Point Operations Status should monitor the
console. Possible values are yes and no.
If you started Single Point Operations Status from Single Point Operations Console, the
value of the Monitor attribute reflects the value of the corresponding attribute in the
Connection Status table of Single Point Operations Console. In this case, when you click
a Monitor attribute value in Status, no action occurs. When you change the value in the
Connection Status table, the value of the Monitor attribute in Status automatically
changes.
If you started Status independently of Single Point Operations Console and your user
class allows it, click a Monitor attribute value to toggle it between yes and no.
4.5.2. Connected to Application
This reported attribute indicates whether the console is correctly connected to Single
Point Operations Status. The attribute has the value yes or no. When you click this
attribute, no action occurs.
4.5.3. Connected to Host
This status attribute identifies the current status of the connection between the console
and its host. The attribute value can be yes or no. When the value of the Status
attribute for the console is active, the expected value of this attribute is yes. If the value
is no, Single Point Operations Status displays the following information in the attention
color (yellow) to draw your attention:
• The attribute value in the attribute list for this component
• The icon of any component group containing the component
When the Status value for the console is not active, Single Point Operations Status does
not compare the value of this attribute to any expected value.
When you click this attribute, no action occurs.
7833 4778–008 4–17

Attributes Specific to the OS 2200 Console Component Class [OS 2200]
4.5.4. Connected Host
This status attribute identifies the host that is currently connected to the console, as
reported by the data collector running on the host.
If the value of this attribute does not match the name of the connected host as specified
in the current configuration, the attribute appears in the alarm color (red).
If alarm text was specified for the component class, this condition causes an alarm to be
raised in Single Point Operations Console. The alarm-id is the component class name
followed by ”.ConnectedHost”. For further information, see 7.3.
When you click this attribute, no action occurs.
4–18 7833 4778–008

Attributes Specific to the MCP Host Class [MCP]
4.6. Attributes Specific to the MCP Host Class
[MCP]
Each classification can contain one component class that models MCP host systems.
This class has MCP specified as its Internal Class. (See 7.3.) In Status, this class
contains one component for each MCP host system in the current configuration.
Components in this class must have a status attribute named “Status.” In addition,
these components have the special attributes described in the subsections that follow.
These special attributes are displayed only in the attribute lists of these components; you
cannot include them in component tables.
4.6.1. Monitor
This attribute indicates whether Single Point Operations Status should monitor the MCP
host. Possible values are yes and no.
If you started Status from Single Point Operations Console, the value of the Monitor
attribute reflects the value of the corresponding attribute in the Connection Status table
of Single Point Operations Console. In this case, when you click the Monitor attribute in
Status, no action occurs. When you change the value in the Connection Status table, the
value of the Monitor attribute in Status automatically changes.
If you started Status independently of Single Point Operations Console and your user
class allows it, click a Monitor attribute value to toggle it between yes and no.
4.6.2. Connected to Application
This reported attribute indicates whether the host is connected to Status. The attribute
has the value yes or no. When you click this attribute, no action occurs.
4.6.3. Data Collection
This reported status attribute indicates the status of data collection for the host. Data
collection is a function provided by the Single Point Operations Interface for ClearPath
MCP (MCP agent), which runs on the MCP host. For more information, see 2.1 and the
MCP Single Point Operations Interface Software Installation and Configuration Guide.
For MCP systems, the Data Collection attribute can have one of the following values:
• not_started
• initiated
• in_progress
• completed
• errored
When the value of the Status attribute for the host is active, any value of the Data
Collection attribute except completed is treated as an unexpected value.
7833 4778–008 4–19

Attributes Specific to the MCP Host Class [MCP]
When the value is other than completed or errored
• The attribute appears in the attention color (yellow) in the attribute list for this
component.
• The icon of any component group containing the host component appears in the
attention color (yellow).
The value errored is an unexpected alarm value and appears in the alarm color (red) in
displays. This value indicates that Status was unable to send the initiate command to the
host, or that a message returned by the MCP host agent indicated a serious problem.
If alarm text was specified for the component class, the value errored raises an alarm in
Single Point Operations Console. The alarm-id is the component class name followed by
”.DataCollection”. For further information, see 7.3.
When you click this attribute, no action occurs.
Note: When a classification requires initialization information about application
components, the Single Point Operations Interface for ClearPath MCP software sends
the INITIALIZE END message to the Single Point Operations server before it sends the
messages for each of the application components. This means that the value of the Data
Collection attribute is set to completed before data collection is complete for the
application components. This happens because the messages for the application
components are sent asynchronously.
4.6.4. Host Agent Active
This reported attribute indicates whether the Single Point Operations Interface for
ClearPath MCP has sent at least one message to the Single Point Operations server.
The attribute has the value yes or no. When the value of the Status attribute for the host
is active, the expected value of this attribute is yes. If the value of this attribute is no,
Single Point Operations Status displays the following information in the attention color
(yellow) to draw your attention:
• The attribute value in the attribute list for this component
• The icon of any component group containing the component
When the Status value for the host is not active, Single Point Operations Status does not
compare the value of this attribute to any expected value.
When you click this attribute, no action occurs.
4.6.5. Application Initialization
Single Point Operations Status automatically sends an initialization request to the MCP
agent when all of the following conditions are true:
• Single Point Operations Status is connected to the MCP host being monitored.
• The value of the Status attribute for the MCP host is either active or timeout.
4–20 7833 4778–008

Attributes Specific to the MCP Host Class [MCP]
• The Data Collection attribute has the value not_started.
• The Host Agent Active attribute has the value yes.
• There is at least one component class in the classification with System Types = MCP
and for which the Single Point Operations administrator specified an initialization
mnemonic. (See 7.3.)
7833 4778–008 4–21

Attributes Specific UNIX Host Class [UNIX]
4.7. Attributes Specific UNIX Host Class [UNIX]
Each classification can contain one component class that models UNIX and other
ANSI X3.64 systems. This class has ANSI_X3_64 specified as its Internal Class.
(See 7.3.) In Status, this class contains one component for each UNIX and other
ANSI X3.64 host in the current configuration. Components in this class must have a
status attribute named “Status.” In addition, these components have the special
attributes described in the subsections that follow. These special attributes are
displayed only in the attribute lists of these components; you cannot include them in
component tables.
4.7.1. Monitor
This attribute indicates whether Single Point Operations Status should monitor the
ANSI X3.64 (UNIX) host. Possible values are yes and no.
If you started Status from Single Point Operations Console, the value of the Monitor
attribute reflects the value of the corresponding attribute in the Connection Status table
of Single Point Operations Console. In this case, when you click the Monitor attribute in
Status, no action occurs. When you change the value in the Connection Status table, the
value of the Monitor attribute in Status automatically changes.
If you started Status independently of Single Point Operations Console and your user
class allows it, click a Monitor attribute value to toggle it between yes and no.
4.7.2. Connected to Application
This reported attribute indicates whether the host is connected to Single Point
Operations Status. The attribute has the value yes or no. When you click this attribute
value, no action occurs.
4–22 7833 4778–008

Section 5
Diagram Definitions
A diagram definition includes
• The definition of each component group displayed in the Status diagram and in each
subgroup window
• The template for each component table that you can display
You can change these definitions, unless your user class restricts you from doing so.
When you develop a combination of definitions that you want to reuse, you can save it as
a named diagram definition.
This section explains how to
• Define component groups and subgroups
• Define component table templates
• Save a diagram definition
• Delete a diagram definition
• Change the diagram definition you are currently using
7833 4778–008 5–1

Defining Component Groups
5.1. Defining Component Groups
You can change the component groups included in the current diagram definition. To
start this process
1. Click Diagrams in the Status diagram menu bar. Status displays the Diagrams menu.
2. Click Define Component Groups. Status displays the Define Status Diagram Groups
table. It also changes the actions that occur when you click icons in the Status
diagram.
If your diagram definition contains group windows in addition to the Status diagram,
Status also opens a Define Groups table for each group window that is open when
you start group definition. The titles of these Define Groups tables include the name
of the parent group. It is recommended that you start group definition with only the
Status Diagram open, and then open subgroup windows later as needed.
5.1.1. Define Groups Tables
The Define Status Diagram Groups table in the following illustration has one row for each
highest-level component group currently defined. The other Define Groups tables have
one row for each subgroup currently defined in the parent group. Each Define Groups
table has a column for each attribute of component groups that you can change. You can
click any value in these tables to change it. The column heading of each column appears
in bold since you can change values in every column.
Figure 5–1. Define Status Diagram Groups Table
Click Help to display the Help menu. You can use this menu to display information about
this table, including information on individual columns.
5–2 7833 4778–008

5.1.2. Capabilities
Defining Component Groups
The Define Groups tables let you make the following changes to component groups:
• Change the name of a group (see 5.1.3.)
• Change the label displayed with a group icon (see 5.1.4.)
• Change the placement of a label in relation to its group icon (see 5.1.4.)
• Change the icon representing a component group (see 5.1.5.)
• Change the location of a group icon (see 5.1.6.)
• Specify the components to be included in a group (see 5.1.8.)
• Define subgroups for a component group (see 5.1.9.)
• Change the Component Group table template associated with a component group
(see 5.1.7.)
• Add or copy new component groups (see 5.1.10. and 5.1.11.)
• Delete existing component groups (see 5.1.12.)
• Add, delete, or move default component groups (see 5.1.13 through 5.1.17.)
• Change the background of a group window (see 5.1.18.)
• Change the color of labels in a group window (see 5.1.19)
• Change the title of a group window (see 5.1.20.)
5.1.3. Changing a Group Name
To change the name of a component group, click its name in the Group Name column of
the Define Groups table that contains the group, and enter the new name in the dialog
window. If the label and name of the group are the same, the label changes also.
5.1.4. Changing a Group Label
To change the label displayed with a component group icon in a group window
1. Click the value in the Label column. Status displays a dialog window that asks you to
enter the new label.
2. Enter the new label. Click the Editor button if you want the label to appear on
multiple lines and press Enter at the end of each line.
To change the placement of the label in relation to its group icon in a group window, click
the value in the Label Position column to toggle among the four values: north, east,
south, and west.
7833 4778–008 5–3

Defining Component Groups
5.1.5. Selecting Icons
In the Status diagram and subgroup windows, Status can display icons of two types:
• Bitmap icons are single-color icons. This color changes to represent the various
states the icon can represent: normal (green), attention (yellow), alarm (red), and
empty (off-white). For all states, the icon has the same size and shape. Internally, a
bitmap icon is defined by a single file using the xbm format.
• Pixmap icons are multicolored icons. The size, shape, and color of these icons can
change for each of the states the icon can represent: normal, attention, alarm, and
empty. Internally, a pixmap icon is defined by a family of four icon files, one for each
state. The format of pixmap icons can be bmp, jpeg, pbm, pgm, png, pnm, ppm, tiff,
or xpm. All icons in one family must be of the same format.
Status is supplied with a large number of pixmap icon families. This includes two
pixmap families for each component class in every classification supplied with
Status. These pixmaps are two different sizes, one large and one small. The
pixmaps whose names end with _lg are the larger icons. The pixmaps whose names
end with _sm are the smaller icons. You can choose large or small icons for a group
window, depending on how many icons you want in the window and how far away
you want them to be visible.
The icon families supplied with Status use the following scheme to depict the various
states the icons represent:
• Normal=green circle
• Attention=yellow triangle
• Alarm=red octagon
• Empty=blue square
For further information on the icon pixmaps supplied with Status, see Appendix F.
For further information on icon file types and defining icon families, see the Single Point
Operations Administration and Configuration Guide.
To select the icon family representing a component group in a group window
1. Click the value in the Icon column of the component group you want to change.
Status displays a dialog window listing all complete icon families available for Status.
2. Select an icon from the dialog window. Select Cancel if you decide not to replace the
icon.
After you make your selection, the icon of the new family replaces the previous icon
in the group window.
To display all icons in an icon family
1. Click Edit in the Define Group menu bar.
2. Click Display Icon Family.
3. Double-click the name of the icon family you want displayed.
5–4 7833 4778–008

Defining Component Groups
A window appears showing the four icons in the icon family depicting the normal,
attention, alarm, and empty states used by Status:
• If the icons are bitmaps, they all have the same size and shape but different colors.
• If the icons are pixmaps, their size, shape, and color depend on the individual icon
files contained in the family.
In Single Point Operations Level 7.4, the icons supplied with Status changed from singlecolor
bitmap icons to multicolor, three-dimensional pixmap icons. Existing diagrams can
continue to use the bitmap icons, or you can update the icons.
To update all obsolete bitmap icons in a diagram
1. Select Edit in the Define Group menu bar.
2. Select Upgrade Obsolete Icons.
3. Click Yes to upgrade all obsolete icons in all component groups in the diagram.
Note: The Upgrade Obsolete Icons menu entry is disabled if the diagram does not use
any obsolete bitmap icons.
5.1.6. Positioning Icons
Each group window has an attribute named “grid increment,” which helps you position
icons quickly and neatly. Each group window is viewed as a grid 1000 units high by 1000
units wide; the default grid increment is 20. When you position an icon with the mouse
pointer, the coordinates of the icon are automatically rounded to the nearest multiple of
the grid increment. Use a smaller increment for a window with many icons; use a larger
grid increment for a window with few icons.
To change the grid increment for a group window
1. Click Edit in the menu bar of the Define Groups table corresponding to the group
window. Status displays a pull-down menu.
2. Click Change Grid Increment. Status opens a dialog window and asks for the new
grid increment.
3. Enter an integer from 1 to 500. Status stores this value in the diagram definition.
The new grid increment affects icons that you subsequently move and create, but it does
not affect the positions of existing icons.
To position automatically all existing icons in a group window to conform to the new grid
increment
1. Click Edit in the menu bar of the Define Groups table corresponding to the group
window. Status displays a pull-down menu.
2. Click Snap to Grid. Status displays a dialog window and asks whether you want to
continue or cancel the task.
7833 4778–008 5–5

Defining Component Groups
3. Click Continue. Status rounds the coordinates of each existing icon in the group
window to the nearest multiple of the grid increment.
There are two ways to change the location of a particular icon in a group window:
• In the group window itself
− Click the icon to be moved.
− Click the new location for the icon. The new location must be in any empty part
of the same group window; that is, it must not be within the borders of any icon,
including the icon being moved. The icon moves to the new location, rounded to
the nearest multiple of the grid increment for that window. The X coordinate and
Y coordinate attributes in the corresponding Define Groups table change to
reflect the new location of the icon.
• In the Define Groups table corresponding to the group window
− Click the value in the X Coord column to change the horizontal position of the
icon. Status opens a dialog window and asks you to enter the new horizontal
position (which refers to the center of the icon). Enter a value from 0 to 1000.
− Click the value in the Y Coord column to change the vertical position of the icon.
Status opens a dialog window and asks you to enter the new vertical position
(which refers to the center of the icon). Enter a value from 0 to 1000.
Both the horizontal and vertical scales run from 0 to 1000 (from left to right and
from top to bottom). When either value is changed, the icon automatically
moves to the new position. When you position an icon using this method, the
coordinates are not automatically rounded to the nearest multiple of the grid
increment.
5.1.7. Changing the Component Group Table Template
The Component Group table template determines which attribute columns appear when
you click the group icon in its group window. To change the Component Group table
template associated with a component group
1. Click the value in the Component Group Table Template column of the component
group you want to change. Status displays a dialog window listing the names of all
Component Group table templates.
2. Select one or more Component Group table templates that you want to be
associated with this component group. If you select more than one template, you
are prompted to choose one of them when you click the group icon to display a
component table.
Note: Select Unknown if you want no Component Group table template to be
associated with the component group. If you select Unknown, Status displays the
attribute list of a component selected from the group instead of a component table.
To define new Component Group table templates, or to change existing templates,
follow the instructions in 5.2.
5–6 7833 4778–008

Defining Component Groups
5.1.8. Specifying Components to Be Included in a Group
To specify components to be included in a component group, you set values for three
attributes of the component group. This table describes these attributes.
Attribute Description
Hosts List of hosts whose components are to be included in the
group.
Classes List of classes of components to be included in the group.
Component Names List of names of components to be included in the group.
Any component that has one of the names you specify and belongs to a host and class
you select is a member of the component group.
To specify components to be included in a component group set the values of the Hosts,
Classes, and Component Names attributes as follows:
1. Click the Hosts, Classes, or Component Names entry you want to set. Status opens
a window and asks you to select or enter the values you want.
2. Select or enter the values, and click OK. You can enter multiple values for each of
these entries. Select the value Unknown if you want to include components in the
group regardless of their hosts, classes, or component names.
When entering a component name, use wildcards if you want to include components
based on only a portion of the component name. A question mark (?) in the component
name means that any character can occupy that position. For example, you can specify
A?C to include components named AAC, ABC, ACC, and so forth.
An asterisk (*) means that any number of characters (zero or more) can occupy that
position in the component name. For example, you can specify A*C to include
components named AC, ABC, AABC, AABBC, and so forth. Or, you can specify DK* to
include components whose names start with DK.
Example of Defining a Group of Tape Drives
To define a component group that contains all tape drives for hosts RS01 and RS02
1. Click the Hosts value for that component group. Select the values RS01 and RS02,
and then click OK.
2. Click the Classes value for the component group. Select Tape, and then click OK.
3. If the value for Component Names is a hyphen (-), leave this value as is. Otherwise,
click the value and select Unknown. This causes components to be included in the
group regardless of their names.
Example of Defining a Group of All /home File Systems
To define a component group that contains all file systems (for all managed UNIX hosts)
whose names begin with “/home”
7833 4778–008 5–7

Defining Component Groups
1. If the value for Hosts is a hyphen (-), leave this value as is. Otherwise, click the value
and select Unknown.
2. Click the Classes value for the component group. Select File System, and then click
OK.
3. Click the value for Component Names. Enter “/home*”, and then click OK. The
asterisk indicates that any characters can follow the characters “/home”.
Component Membership in Subgroups
When you define groups in a group window other than the Status diagram, selection
criteria from the parent group are carried down to each subgroup automatically. For
example, if a parent group contains components only from a certain component class,
then all subgroups of this parent group are limited to components of this class,
regardless of what you specify for the Classes attribute of these subgroups.
If you select membership criteria for a group using the Hosts and Classes columns, the
hosts and classes from which you can select are limited to those to which the parent
group is restricted. Specifying no hosts for a subgroup limits the subgroup to the same
host systems as the parent group, and likewise for classes and component names.
Any changes of membership criteria for a parent group are implicitly carried down to the
parent group's subgroups, even though explicit changes are not made to the
membership criteria of the subgroups. For example, if a parent group is limited to host
systems S1, S2, and S3, its subgroups can individually be limited to S1, S2, or S3 (or any
combination of these). However, if you later exclude S3 from the parent's class,
components belonging to S3 will no longer be in any subgroup of that parent group even
though these subgroups might still show S3 in the Hosts selection list (if they were thus
defined previously).
5.1.9. Defining Subgroups
The Subgroups? column has the value yes or no for each component group, with no as
the default. Click a value in this column to open a dialog window with Yes and No
buttons and text explaining the column and indicating the column's current value:
• Click Yes to open a subgroup window and a Define Groups table for the associated
component group (if they are not already open). If the value was previously No, the
window and table are empty.
• Click No to close the associated subgroup window and Define Groups table (if they
are open).
If any subgroups were previously defined for the group, you are warned that these
will be automatically deleted, and are asked to confirm or cancel.
5–8 7833 4778–008

5.1.10. Adding New Component Groups
To add new component groups individually to a group window
Defining Component Groups
1. Click Edit in the menu bar of the corresponding Define Groups table. Status displays
a pull-down menu.
2. Click Add Groups. Status opens a dialog window and asks for the names of the
groups to be added.
3. Enter the names of the groups to be added and press Enter at the end of each
name. Click OK.
Status creates the new groups, supplies default values for all group attributes, and adds
rows for these new groups at the bottom of the Define Groups table. The new icons
appear in the bottom left of the group window; they may overlay existing icons. It is
recommended that you move them immediately to the desired locations, as described in
5.1.6. Specify the icon family, group membership, and other group attributes as
described in the previous subsections.
5.1.11. Copying a Component Group
You can add new component groups by copying an existing component group with its
defined set of attributes.
To copy attributes from an existing component group
1. Click Edit in the menu bar of the Define Groups table in which the group appears.
Status displays a pull-down menu.
2. Click Copy Groups. Status opens a dialog window and asks you to select the group
you want to copy.
3. Double-click the name of the group you want to copy. Status opens a dialog window
and asks for the names of the groups to be added.
4. Enter the names of the groups to be added and press Enter after each name. Click
OK.
Status creates a new group for each name you enter, and adds rows for these new
groups at the bottom of the Define Groups table. Except for location and label
information, the new groups have the same group attribute values as the existing group
you selected. The labels of the new groups are the same as their names. The new icons
appear in the bottom left of the group window. It is recommended that you move them
immediately to the desired locations.
5.1.12. Deleting Existing Component Groups
To delete existing component groups from a group window
1. Click Edit in the menu bar of the corresponding Define Groups table. Status displays
a pull-down menu.
7833 4778–008 5–9

Defining Component Groups
2. Click Delete Groups. Status displays a dialog window containing all existing
component groups in the group window.
3. Double-click the desired component group to delete a single component group. Click
once on each group name to select multiple component groups to be deleted, and
then click OK.
Status deletes the selected groups, removing their rows from the Define Groups table
and their icons from the group window.
5.1.13. Adding Default Groups for a Selected Host
For each host in the current configuration, there is one default component group for each
component class that is applicable to the host type. Default groups provide a quick and
easy way for you to define component groups. The name of each default group is the
host name, followed by a period, followed by the class name.
Each default group is automatically associated with a Component Group table template
appropriate for the component class. When you click the group icon, a table with the
appropriate columns appears.
To add default groups for a selected host
1. Click Edit in the menu bar of the applicable Define Groups table. Status displays a
pull-down menu.
2. Click Add Default Groups for Host. Status displays a dialog window containing the
name of each host in the current configuration. If you are defining default groups for
a subgroup window, the dialog window contains only the names of hosts included in
the parent group.
3. Select a host from the list. Status asks for the vertical position where you want to
place the icons for the default groups.
4. Enter a number from 0 to 1000.
Status then creates a default group for each component class that applies to the host
you selected. If you are defining default groups for a subgroup window, subgroups are
created only for the component classes included in the parent group. Status supplies
default values for all group attributes. In particular
• The Hosts attribute for every group is set to the host you selected.
• The Classes attribute is set to each of the different classes for each of the different
groups.
• The Names attribute for every group is set to Unknown, meaning that components
are included in the group regardless of their names.
Status places the associated icons in a horizontal row at the vertical position you
specified, and adds rows at the end of the Define Groups table for each group. After the
default groups are created, you can change, move, or delete each individual group as
desired.
5–10 7833 4778–008

5.1.14. Deleting Default Groups for a Selected Host
To delete default groups from a group window for a selected host
Defining Component Groups
1. Click Edit in the menu bar of the corresponding Define Groups table. Status displays
a pull-down menu.
2. Click Delete Default Groups for Host. Status displays a dialog window containing the
name of each host in the current configuration or parent group.
3. Select a host from the window.
Status deletes each component group in the group window that is a default component
group for the specified host. (A default group is one whose name consists of the host
name followed by a period and a component class name.) There is no error if some or all
default groups for the host were deleted earlier; Status deletes any remaining default
groups.
5.1.15. Moving Default Groups for a Selected Host
To move default groups in a group window for a selected host
1. Click Edit in the menu bar of the corresponding Define Groups table. Status displays
a pull-down menu.
2. Click Move Default Groups for Host. Status displays a dialog window containing the
name of each host in the current configuration or parent group.
3. Select a host from the window. Status asks for the vertical position where you want
to place the icons for the default groups.
4. Enter a number from 0 to 1000.
Status moves each default group associated with the host to the specified vertical
position; the horizontal position is unchanged. (A default group is one whose name
consists of the host name followed by a period and a component class name.) There is
no error if some or all default groups for the host were deleted earlier; Status moves any
remaining default groups.
5.1.16. Adding Default Groups for Each Host and Class
You can easily create an entire status diagram that consists of default component groups
for all meaningful combinations of hosts in the configuration and component classes in
the classification. Similarly, you can create an entire subgroup window that consists of all
meaningful combinations of host and classes in the parent group.
To create such a group window
1. Click Edit in the menu bar of the Define Groups table. Status displays a pull-down
menu.
2. Click Create Default Groups for All Hosts and Classes.
7833 4778–008 5–11

Defining Component Groups
Status immediately creates component groups in the group window for each
combination of host and component class, arranged in evenly spaced rows and columns.
After the groups are created, you can change, move, or delete them individually as
desired.
5.1.17. Adding Host-Independent Component Groups for All
Component Classes
You can easily create an entire group window of host-independent component groups for
all component classes in the classification or parent group. In this case, each component
group contains components from all hosts in the configuration or parent group.
Each host-independent group is automatically associated with a Component Group table
template appropriate for its component class. When you click the group icon, a table
with the appropriate columns appears.
To add default groups for all component classes
1. Click Edit in the menu bar of the Define Groups table. Status displays a pull-down
menu.
2. Click Add Default Groups for All Classes. Status displays a dialog window asking
whether you want a lower level group window defined for each group it creates.
3. Click No if you do not want Status to create subgroups for each group it creates.
Click Yes if you want Status to create one subgroup for each host belonging to each
group.
Status creates one component group for each component class in the classification or
parent group. Each group contains components from all hosts in the configuration or
parent group. The icons for the component groups are arranged in one, two, or three
rows in the group window, depending on the number of icons. Status also creates
subgroups for each of these groups if you clicked Yes for this. After the groups are
created, you can change, move or delete them individually as desired.
5.1.18. Changing the Background
The background of a window is the fixed graphic that is displayed in the window behind
any icons displayed in the window.
To change the background for a group window
1. Select the Change Background item in the Edit menu of the corresponding Define
Groups table.
A dialog window appears showing the current choice and displaying a list of all
possible choices.
2. Either select Unknown to remove the background or select the name of a
background. The background appears immediately in the corresponding group
window.
5–12 7833 4778–008

Defining Component Groups
Background bitmaps and pixmaps are fixed in size. The background is tiled if it is smaller
than the window; it is truncated if it is too large for the window. Further, whenever you
resize a group window, the icons within the window are adjusted proportionately. The
icons, therefore, move in relation to the background.
Background files are located in the folder named backgrounds in the Single Point
Operations data folder on the Single Point Operations server. You can define additional
background files using various graphical tools, and add them to this folder, where they
will be automatically made available to Single Point Operations Console and Single Pont
Operations Status.
5.1.19. Changing the Label Color
Depending on the background you select, you can change the label colors in clusters to
provide greater visibility. To change the label color of a group window
1. Select Change Label Color in the Edit menu of the corresponding Define Groups
table.
2. Select the name of the desired color. The label in the group window is displayed
using the color selected.
5.1.20. Changing the Title
To change the title of a group window
1. Select the Change Title item in the Edit menu of the corresponding Define Groups
table.
2. Enter a string of characters as the title for the group window. The new title with
substitutions is displayed immediately in the title bar of the group window. The title
is limited to a single line and can include the following substitution strings:
\_LEVEL\ Single Point Operations release level
\_CONFIGURATION\ Current configuration
\_CLASSIFICATION\ Current classification
\_USER\ Current user
\_DIAGRAM\ Current diagram
\_GROUP\ Name of the parent group of the window
\_GROUPLABEL\ Label of the parent group of the window (with newlines
converted to spaces)
\_SERVER\ Name of the Single Point Operations server
7833 4778–008 5–13

Defining Component Groups
The default title string for the Status Diagram is
Single Point Operations Status(Configuration: \_CONFIGURATION\ Classification: \_CLASSIFICATION\
Diagram: \_DIAGRAM\)
The default title string for each subgroup window is
Group: \_GROUPLABEL\
5–14 7833 4778–008

Defining Component Table Templates
5.2. Defining Component Table Templates
A component table template specifies the appearance, behavior, and attributes of a
component table. It determines which attributes appear in a table when you open the
table. As explained in 3.4, there are five types of component tables:
• Component Group
• Components with Unexpected Values
• Components with Notes
• Unreported Components
• Identical Components
You can specify how Status displays attributes in each of these tables. For example, you
can change the screen size, display behavior, and attribute columns of any component
table template defined in the current diagram definition.
You can also change, add, and delete Component Group table templates. When a
component group is displayed using a particular Component Group table template, Status
displays the component attributes as specified for that template.
To start defining component table templates
1. Click Diagrams in the Status diagram menu bar. Status displays the Diagrams menu.
2. Click Define Component Tables. Status displays a table called Define Component
Tables. This illustration shows the table.
7833 4778–008 5–15

Defining Component Table Templates
Figure 5–2. Table to Define Component Table Templates
Click Help to display the Help menu for the window. You can use this menu to display
general information about this table including information on individual columns.
Capabilities
The Define Component Tables table contains one row for each component table
template in the diagram definition. These templates include:
• unexpected_components
This template controls the Components with Unexpected Values table.
• noted_components
This template controls the Components with Notes table.
• unreported_components
This template controls the Unreported Components table.
• identical_components
This template controls the Identical Components tables.
5–16 7833 4778–008

Defining Component Table Templates
• Miscellaneous predefined Component Group templates
The names of these templates indicate which columns they include.
• Component Group templates whose names match the component classes
Status automatically creates one template for each class in the current classification.
Each of these templates, by default, includes columns for the Name, Host,
Exceptions, Seen, and Notes attributes, plus one column for each site-defined
attribute in the associated class.
The Define Component Tables table contains one column for each attribute of
component table templates that you can change. The column headers of these columns
appear in bold to indicate that you can change the values. You can click any value in this
table to change it, except a value in the first column, which is the table template name.
With the Define Component Tables table, you can make the following changes to
component table templates:
• Change the screen size of a table template.
• Change the display behavior of a table template.
• Change the component class associated with the table template.
• Change the attribute columns in the component table template and the order in
which they appear.
You can use the Edit menu of the Define Component Tables table to perform the
following operations on Component Group table templates:
• Add new Component Group table templates
• Delete existing Component Group table templates
• Select a different Component Group table template as the default
5.2.1. Changing the Screen Size of a Table Template
To change the screen size of a component table template
• Click the value labeled Width to change the displayed width of the table in pixels.
Status opens a dialog window and asks you to enter the new value. Enter a value
from 50 to 1280.
• Click the value labeled Height to change the displayed height of the table in pixels.
Status opens a dialog window and asks you to enter the new value. Enter a value
from 50 to 1000.
When you open a table using the template, if the displayed width or height of the table is
less than its actual width or height, the table has scroll bars.
The size you specify here determines the size of the table on your screen when you open
it. You can change its size later by using the mouse.
7833 4778–008 5–17

Defining Component Table Templates
5.2.2. Changing the Display Behavior of a Table Template
As explained in 3.4, Status can display a component table in two ways:
• Static—the table contains a row for each component in the component group.
• Dynamic—the table contains rows only for components with exceptions not marked
as seen (those components with an attention or alarm value and with Seen=no).
To specify the display behavior as dynamic or static, click a value in the column labeled
Behavior. Status opens a dialog window and asks you to choose between static and
dynamic behavior. If you click Unknown, then whenever you open a component group
using this table template, Status asks whether you want static or dynamic behavior.
Note: The Behavior attribute applies only to Component Group table templates. It does
not affect the unexpected_components, noted_components, unreported_components, or
identical_components table templates.
5.2.3. Changing the Class Associated with a Table Template
When you select the attribute columns to be included in a component table template, it
is useful to have these columns labeled with the names that appear when the table is
displayed. Since these names depend on the classes displayed in the table, Status lets
you associate a component class with each template for that purpose. This association
does not prevent you from displaying components from other classes in a table that uses
that template.
To select the component class associated with a table template
1. Click the value labeled Class for that template. Status opens a dialog window
containing a list of all classes in the current classification.
2. Double-click the name of the desired class. Click Unknown if you want no
component class associated with the template. In that case, Status displays generic
attribute names when you select the columns to be included in the template.
5.2.4. Changing the Attribute Columns in a Table Template
When you open a component table, its table template determines which attribute
columns appear and the order in which they appear. The Attributes column in the Define
Component Tables table shows the column order for each table template. Column
names for each template are listed one per line.
To change the attribute columns for a table template
1. Click a value in the column labeled Attributes. Status displays a dialog window
containing a list of all attribute columns that are currently included in the table
template, and another list of all possible attribute columns for the component class
associated with that template. Because there are many columns, this dialog window
includes scroll bars.
5–18 7833 4778–008

Defining Component Table Templates
2. Click the attribute column names you want in the order you want them. You can also
click a column you selected earlier to deselect it.
3. Click OK when you have finished selecting columns.
Notes:
• There are columns listed for each site-defined attribute in the component class
associated with the template. These columns are labeled with the attribute names
defined for the component class, which are the same names that appear as column
headings when you open a table using the template. If you have not associated a
component class with the template, site-defined attributes are identified by their
generic names, and you must refer to the classification definition to determine how
each generic attribute name maps with the actual attribute name for any particular
component class.
• There are three columns for the Seen attribute:
• Seen (toggle)—Lets you toggle the Seen attribute in a component table simply
by clicking it. It is suggested you use the Seen (toggle) column in table templates
with static behavior.
• Seen (dialog)—Lets you change the Seen attribute by using a dialog window, so
you are less likely to change the attribute inadvertently. It is suggested you use
the Seen (dialog) column in table templates with dynamic behavior, and in the
Components with Unexpected Values table template.
• Seen (delete)—Lets you change the Seen attribute by using a dialog window.
Also lets you delete a component after changing the Seen attribute to yes. Use
Seen (delete) in table templates for which you want to provide the capability to
delete components.
Do not include more than one of these columns in the same table template.
• There are two columns for the Message attribute:
− Message (narrow)—Displays the Message attribute truncated to 10 characters.
− Message (wide)—Displays the Message attribute truncated to 40 characters.
Either column allows you to see the entire message by clicking it. Do not include
both columns in the same table template.
5.2.5. Adding New Component Group Table Templates
To add new Component Group table templates
1. Click Edit in the menu bar of the Define Component Tables table. Status displays a
pull-down menu.
2. Click Add Tables. Status asks for the names of one or more new table templates.
3. Enter the names of the table templates, and press Enter at the end of each name.
4. Click OK. Status creates the new table templates with default values for size,
behavior, associated class, and attributes. You can then change these default
values, as described earlier in this section.
7833 4778–008 5–19

Defining Component Table Templates
5.2.6. Deleting Existing Component Group Table Templates
To delete existing Component Group table templates
1. Click Edit in the menu bar of the Define Component Tables table. Status displays a
pull-down menu.
2. Click Delete Tables. Status displays a menu of all Component Group table templates
currently defined.
3. Double-click to delete a single table template. To delete multiple table templates,
click once on the name of each table template and then click OK. Click Cancel if you
decide not to delete any table templates.
5.2.7. Selecting a Different Component Group Table Template
as the Default
When you create a new component group, one table template is automatically
associated with the component group. This table template is the default.
To select a different template as the default
1. Click Edit in the menu bar of the Define Component Tables table. Status displays a
pull-down menu.
2. Click Change Default. Status displays a dialog window containing all Component
Group table templates currently defined.
3. Select one Component Group table template to be the new default. The default
template appears in bold in the Define Component Tables table.
5–20 7833 4778–008

5.3. Saving a Diagram Definition
Saving a Diagram Definition
After making any number of changes to component groups and component table
templates, you can save the current values for all these items as a named diagram
definition. This diagram definition can replace the current diagram definition, or it can be
a new diagram definition.
5.3.1. Replacing the Current Diagram Definition
If your user class allows it, you can replace the current diagram definition as follows:
1. Click Diagrams in the Status diagram menu bar. Status displays the Diagrams menu.
2. Click Save Diagram. Status replaces the previously saved information with the
current specifications.
Note: If you did not select a named diagram definition when you started Status, Status
used an unnamed default diagram (indicated by ““ in the title bar and About
window). In this case, Status asks you for a diagram name, since the default diagram
has no name.
5.3.2. Saving a New Diagram Definition
To save a new diagram definition
1. Click Diagrams in the Status diagram menu bar. Status displays the Diagrams menu.
2. Click Save Diagram As. Status asks for the name of the new diagram definition.
3. Enter the name of the new diagram definition, and click OK. Status verifies that the
name does not match the name of an existing diagram definition for the current
combination of classification and configuration, and then saves the current
specifications as a new diagram definition with the name you specified. The name of
the new diagram definition replaces the name of the previous diagram definition in
the title bar of the Status diagram.
7833 4778–008 5–21

Deleting Diagram Definitions
5.4. Deleting Diagram Definitions
If your user class allows it, you can delete one or more diagram definitions as follows:
1. Click Diagrams in the Status diagram menu bar. Status displays the Diagrams menu.
2. Click Delete Diagrams. Status displays a dialog window containing the names of all
diagrams currently defined for the current combination of classification and
configuration.
3. Double-click the desired diagram name to delete a single diagram. To select multiple
diagrams from this list, click once on each diagram name and click OK. Status then
deletes their definitions.
A diagram definition depends on both the configuration and the classification under
which it was defined. When the definition of a configuration or classification is deleted
using the Single Point Operations Configuration application, all diagram definitions related
to the configuration or classification are automatically deleted.
5–22 7833 4778–008

Changing the Diagram Definition in Use
5.5. Changing the Diagram Definition in Use
You can replace the current diagram definition used by Status with any other diagram
defined for the current configuration and classification, as follows:
1. Click File in the Status diagram menu bar. Status displays the File menu.
2. Click Select Diagram. Status displays a dialog window containing the names of all
diagram definitions for the current combination of classification and configuration.
3. Select a diagram definition from this list. (Select Cancel if you decide not to change
the diagram definition.)
If you select Unknown instead of a diagram definition, Status creates a new diagram
definition and asks you to choose one of the following options:
• Create one component group for each combination of host and component class. If
you choose this option, Status creates a component group for every combination of
host and class for which components can exist. The icons for these groups are
arranged in evenly spaced rows and columns in the Status diagram. In Figure 5-3,
icons were created for each configuration of the 3 host systems in configuration
UnixOnly, and the 6 component classes in classification UnixMon.
• Create one component group for each component class. If you choose this option,
Status creates a component group for each component class; each group contains
components from all hosts. The icons for these groups are evenly arranged in one,
two, or three rows in the Status diagram, depending on the number of icons present.
(See Figure 5-4.)
• Create one component group for each component class, with subgroups for each
host. If you choose this option, Status creates a status diagram containing one
component group for each component class, just as with the previous option. With
this option, Status also creates subgroups for each of these top-level groups. When
you click any icon in the status diagram, a subgroup window opens. This window
contains one subgroup for each host to which the components in the parent class
can belong.
• Create no default groups. If you choose this option, Status displays a Status diagram
containing no groups.
After choosing any of these options, you can change the new diagram definition created
for you, as described in 5.1 and 5.2. If you save these changes, Status then asks you to
supply a name for the new diagram definition.
7833 4778–008 5–23

Changing the Diagram Definition in Use
Figure 5–3. A Component Group for Each Combination of Host and
Component Class
Figure 5–4. A Component Group for Each Component Class
5–24 7833 4778–008

After you select a diagram definition, Status
Changing the Diagram Definition in Use
• Removes from the screen all of its open windows, such as the Status diagram,
component tables, and attribute lists.
• Erases all current diagram specifications.
• Reads the diagram specifications from the diagram definition you selected.
• Determines which components being monitored belong in which groups of the new
diagram definition.
• Displays the Status diagram associated with the new diagram definition.
7833 4778–008 5–25

Changing the Diagram Definition in Use
5–26 7833 4778–008

Section 6
Component Sets
This section explains how to
• Define components explicitly
• Save component definitions in named component sets
• Delete previously defined component sets
• Retrieve component definitions previously saved in component sets
7833 4778–008 6–1

Defining Components Explicitly
6.1. Defining Components Explicitly
In most cases, you can rely on Single Point Operations Status to create components
automatically based on the receipt of event reports. Sometimes, however, you may
choose to define components explicitly so that you can specify nondefault values for
specified attributes, such as expected and alarm values.
To start defining components
1. Click Component Sets in the Status diagram menu bar. Status displays the
Component Sets menu.
2. Click Define Components. Status displays a dialog window listing all hosts in the
current configuration.
3. Select one of the hosts. Status displays a dialog window listing all component
classes in the current classification.
4. Select one of the component classes. Status displays the Edit Components table,
described next.
6.1.1. Edit Components Table
The Edit Components table contains a row for each component currently modeled by
Status for the selected host and class. The table title indicates the host and class of the
components. The first column shows the name of each component for this host and
class. The remaining columns display each specified attribute whose value you can
change. Click any of these values to change them. Figure 6-1 shows the Edit
Components table.
Figure 6–1. Edit Components Table
Click Help to display the Help menu. You can use this menu to display general
information about this table, including information on individual columns.
6–2 7833 4778–008

Defining Components Explicitly
6.1.2. Changes You Can Make to Component Definitions
You can use the Edit Components table to make the following changes to component
definitions:
• Indicate whether a component was explicitly defined.
• Specify the scope of a component.
• Specify the instruction file associated with a component.
• Specify expected and alarm values for any status attributes defined for the
component class.
• Specify minimum and maximum threshold values for any numeric attributes defined
for the component class.
• Add definitions for new components.
• Delete definitions for existing components.
6.1.3. Indicating Whether a Component Was Explicitly Defined
Click a value in the column labeled User Defined? to toggle between the values yes and
no. The following table explains when the attribute is set to each value.
The attribute is set to... For components that were...
Yes Defined explicitly or defined in a component set
selected by the user.
No Created upon receipt of an event report.
The value of the User Defined attribute controls the behavior of Status if it loses
connection to a host and re-establishes that connection. If User Defined is no for a
component belonging to that host, the component is deleted when the connection is reestablished.
Presumably, Status will subsequently receive an event report for that
component and automatically add the component back into its data model. If User
Defined is yes, the component is not deleted when the connection is re-established, but
the values of all its reported attributes are reset to the unreported state (shown by a
hyphen in component tables).
Note: A component is deleted or has its attribute values reset when a host connection
is re-established only if the Single Point Operations administrator set Reinitialize? to yes
for the component class during classification definition. (See 7.3.)
The value of the User Defined attribute can be used to control which components are
saved in a component set. For details, see 6.2.
6.1.4. Specifying the Scope of a Component
As explained in 4.2, a component can have a scope of
• Host—The component is limited to a single host.
7833 4778–008 6–3

Defining Components Explicitly
• Shared—The component scope includes all hosts monitored by Status.
Click the value in the Component Scope column to toggle between the values of Host
and Shared.
6.1.5. Specifying the Instruction File
To specify the instruction file associated with a component
1. Click a value in the Instruction File column. Status asks for the instruction file name.
2. Enter the file name, and click OK. The file might not exist initially. Status asks if you
want to edit the instruction file.
3. Choose yes or no. If you choose yes, Status displays an edit window with the
current contents of the instruction file, if any. When you are finished editing, you can
save or discard the changes when you close the edit window.
The edit window for instruction text works like the edit window for notes described in
4.2.6.
6.1.6. Specifying Expected or Alarm Values for Status
Attributes
If your user class allows it, you can specify expected or alarm values for any status
attributes defined for the component class. These values appear in the Edit Components
table in columns labeled with the attribute name, preceded by the word Expected or
Alarm.
To specify expected values for a status attribute
1. Click a value in the Expected attribute column. Single Point Operations Status
displays a dialog window listing all possible status values for the attribute, except for
any values selected earlier as alarm values.
2. Select one or more expected values, or select Unknown to specify no expected
values. If you select Unknown, Single Point Operations Status sets the expected
value for the component to the next value received for the attribute in an event
report, provided this value is not an alarm value.
To specify alarm values for a status attribute
1. Click a value in the Alarm attribute column. Single Point Operations Status displays a
dialog window listing all possible values for the attribute, except for any values
selected earlier as expected values.
2. Select one or more alarm values, or select Unknown to specify no alarm values.
To add or remove values from the set of possible values for a status attribute, use the
Single Point Operations Configuration application. For details, see 7.5.
6–4 7833 4778–008

Defining Components Explicitly
6.1.7. Specifying Minimum and Maximum Threshold Values
If your user class allows it, you can specify minimum and maximum threshold values for
any numeric attributes defined for the component class. Each numeric attribute can
have four threshold values: minimum alarm, minimum attention, maximum attention, and
maximum alarm. The values appear in the Edit Components table in columns labeled
with the attribute name, preceded by the following: Min Alarm, Min Attn, Max Attn, and
Max Alarm.
To specify a minimum or maximum threshold value
1. Click a value in the Min Alarm, Min Attn, Max Attn, or Max Alarm attribute column.
Single Point Operations Status asks for the new threshold value.
2. Enter the new threshold value, or click Unknown to disable checking of that
threshold.
Single Point Operations Status prevents you from specifying a value that is out of order.
For example, you cannot specify a Min Attn value that is less than the Min Alarm value or
greater than the Max Attn value.
6.1.8. Defining New Components
To add definitions for new components
1. Click Edit in the menu bar of the Edit Components table. Status displays a pull-down
menu.
2. Click Add Components.
3. Enter the names of all new components to be added for the selected host and class.
If you enter more than one, press Enter after each name. For each name you enter,
Status creates a new component, sets its User Defined attribute to yes, gives
default values to all other specified attributes based on the component class, and
adds a row at the end of the table to display the component. You can change any
values for these new components, as described earlier.
6.1.9. Deleting Components
To delete definitions of existing components
1. Click Edit in the menu bar of the Edit Components table. Status displays a pull-down
menu.
2. Click Delete. Status displays a dialog window containing the names of all
components for the selected host and class.
3. Double-click to delete a single component. Click once each component name to
select multiple components to be deleted, then click OK. Click Cancel if you decide
not to delete any components.
You can delete components only if your user class allows you to perform this action.
7833 4778–008 6–5

Defining Components Explicitly
6.1.10. Defining Components for a Different Host or Class
After you have finished defining components for one host and class, you can start
defining components for a different host or class as follows:
1. Click Reselect in the menu bar of the Edit Components table. Status displays a pulldown
menu.
2. Click one of the menu items:
• Select Different Host
• Select Different Class
• Select Different Host & Class
Depending on your selection, Status displays a dialog window of available hosts, a
dialog window of available component classes, or both.
3. Select the desired hosts or classes. Status redisplays the Edit Components table
with components of the selected host and class. If you select a different component
class, the columns in the table change to reflect the attributes defined in the new
class.
6–6 7833 4778–008

6.2. Saving Component Set Definitions
Saving Component Set Definitions
At any time while running Status, if your user class allows, you can save some or all of
the currently defined components as a named component set.
6.2.1. Saving a New Component Set Definition
To create a new component set
1. Click Component Sets in the Status diagram menu bar. Status displays the
Component Sets menu.
2. Click Save Component Set As. Status displays a dialog window containing a list of all
component classes in the current classification.
3. Select one or more of these component classes, or click Unknown to select all
component classes. Status displays a dialog window containing a list of all hosts in
the current configuration.
4. Select one or more hosts, or click Unknown to select all hosts. Status asks if you
want to save all components of the selected hosts and classes, or only components
for which the User Defined attribute is set to yes.
5. Specify whether you want to save all components or only user-defined ones.
6. Status asks for the name to be given to the component set. Enter a name for the
component set (select Cancel if you decide not to save the component set). Status
saves the components you selected as a component set with the specified name. If
the name you specified is the name of another component set defined for the
current configuration and classification, Status asks if you want to overwrite the
existing component set. If you answer No, the new component set is not saved.
Note: Regardless of the value of the User Defined attribute of each component when
the component set is saved, the User Defined attribute is set to yes for each component
when the component set is retrieved.
6.2.2. Replacing a Component Set Definition
At any time while running Status, if your user class allows, you can replace the
components in a previously defined component set by the components in the same
hosts and classes currently being monitored by Status.
To replace a component set
1. Click Component Sets in the Status diagram menu bar. Status displays the
Component Sets menu.
2. Click Save Component Set. Status displays a dialog window listing all component
sets defined for the current configuration and classification.
3. Click the name of the component set you want to replace. Status asks if you want
to save all components of the hosts and classes selected for the component set, or
only components whose User Defined attribute is set to yes (see 6.1.3).
7833 4778–008 6–7

Saving Component Set Definitions
4. Select whether you want to save all components or only user-defined ones. Status
displays a dialog window stating for which classes and hosts components will be
saved, and asking for your confirmation to continue.
5. Click Continue to replace the component set you selected, or click Cancel if you
decide to leave this component set unchanged.
Note: Regardless of the value of the User Defined attribute of each component when
the component set is saved, the User Defined attribute is set to yes for each component
when the component set is retrieved.
6–8 7833 4778–008

Deleting Component Set Definitions
6.3. Deleting Component Set Definitions
If your user class allows, you can delete one or more previously defined component sets
for the current configuration and classification, as follows:
1. Click Component Sets in the Status diagram menu bar. Status displays the
Component Sets menu.
2. Click Delete Component Sets. Status displays a dialog window listing all component
sets in the current configuration and classification.
3. Double-click the desired component set name to delete a single component set. To
select multiple component sets to be deleted, click once on the name of each
component set and then click OK.
Note: A component set definition depends on the configuration and classification in
which it was defined. When the definition of a configuration or classification is deleted
using the Single Point Operations Configuration application, all component sets related to
the configuration or classification are automatically deleted.
7833 4778–008 6–9

Retrieving a Component Set
6.4. Retrieving a Component Set
You can retrieve component definitions that were saved previously in component sets as
follows:
1. Click File in the Status diagram menu bar. Status displays the File menu.
2. Click Retrieve Component Sets. Status displays a dialog window listing all
component sets for the current combination of classification and configuration.
3. Double-click the component set name to select a single component set. To select
multiple component sets from the dialog window, click once on each component set
and then click OK.
After you select component sets, Status reads the information in each component set
consecutively. For each component in these sets, Status
1. Determines whether a component matching the one in the component set already
exists. If not, Status creates such a component.
Note: When you define a component class using the Single Point Operations
Configuration application, you can specify the creation scheme as automatic,
explicit_only, or none. If the creation scheme is none, Status does not create
components in this class under any circumstances, even if you retrieve a component
set containing them. For further information, see 7.3.
2. Sets the User Defined attribute to yes, signifying that the component was created
through explicit user action.
3. Sets the values of all specified attributes of the component based on the information
stored in the component set definition, overwriting any existing values. If a
component is defined in more than one of the selected component sets, Status uses
the values from the last component set selected. Therefore, the order in which you
select component sets may be important.
Note: When you retrieve a component set, Status never deletes components that were
previously defined. If an existing component does not appear in any of the component
sets you select, then Status leaves that component unchanged.
6–10 7833 4778–008

Section 7
Defining Classifications
This section explains how to
• Define Status classifications
• Change component class characteristics
• Add and delete component classes
• Configure site-defined attributes
7833 4778–008 7–1

Status Configuration Overview
7.1. Status Configuration Overview
Some capabilities of the Configuration application apply specifically to Status. In addition
to defining configurations for use by both Single Point Operations Console and Status,
you can use the Configuration application to
• Define classifications, which contain the classes of components monitored
simultaneously by Status.
• Specify the basic characteristics of component classes.
• Configure site-defined attributes within component classes.
• Specify Status functions to be restricted for different user classes.
• Select default resource sets for different users.
• Define external applications that can be initiated from Status.
The first three of these tasks are described in the remainder of this section. The last
three of these tasks are described in the Single Point Operations Administration and
Configuration Guide.
A configuration and a classification are independent definitions. A classification is not
associated with a single configuration, and a configuration is not associated with a single
classification.
You can perform the following functions with the Configuration application only if your
site has purchased and installed the Department or Enterprise Edition of Single Point
Operations:
• Define new classifications
• Define new component classes in a predefined classification
• Define new site-defined attributes in a predefined classification
If only Basic Edition of Single Point Operations is installed, the menu entries for these
functions are disabled.
7–2 7833 4778–008

7.2. Defining Status Classifications
7.2.1. Creating or Editing a Classification
Defining Status Classifications
Use the following procedure to create a new classification or to edit an existing
classification:
1. Click Application in the menu bar of Single Point Operations Configuration.
2. Click Define Status Classification.
The Configuration application determines whether the environment variable
SPCLASSIFICATION is defined and contains a nonnull value, and responds in one of
two ways the first time you select a classification:
• If the environment variable SPCLASSIFICATION was set to a nonnull value
before you started the Configuration application, the Configuration application
uses its value as the name of the classification to be edited. However, if a
classification with this name does not exist, a message is displayed and you are
asked to select another classification.
• If the environment variable SPCLASSIFICATION was not set, the Configuration
application displays a dialog window listing the available classifications.
3. From the list of available classifications, perform one of the following actions:
• Select the classification you want to edit.
• Click Unknown to create a new classification.
The Configuration application displays the Define Status Classification table, as
shown in the following illustration.
Figure 7–1. Define Status Classification Table
7833 4778–008 7–3

Defining Status Classifications
If you clicked Unknown to create a new classification, the table is empty and
appears in the window title. The Define Status Classification table has
• One row for each component class defined in the classification, listed in
alphabetical order by class name
• One column for each basic characteristic of component classes that you can
change
Click Help in the menu bar to display help text about the Define Status Classification
table.
4. Use the Define Status Classification table to change the following component class
characteristics:
Internal Class
The internal class for this component class. Special internal classes are used for
monitoring host systems and system consoles.
System Types
The types of host systems that can contain components of this class. These
include MCP, OS 2200, ANSI X3.64, Windows, and Arbitrary.
Class Label
The label Status uses for default component groups that contain components of
this component class.
Icon Bitmap
The name of the icon bitmap file used for default component groups that contain
components of this class.
Default Scope
The scope used as a default for all new components of this class. This can be
Host or Shared.
Creation Scheme
The creation scheme for components of this class. This can be automatic,
explicit-only, or none.
Init Mnemonic [OS 2200 MCP]
The mnemonic by which the data collector on the host system knows this
component class. Used only for OS 2200 and MCP component classes.
Reinitialize
Indicates if components of this class should be reinitialized when Status
reestablishes a connection with the host system to which the components
belong.
Instruction File
The name of the instruction file used as a default for all new components of this
class.
7–4 7833 4778–008

Defining Status Classifications
Retain Notes
Indicates whether operator notes created for a component are deleted
automatically when the component is deleted.
Alarm text
The alarm text that is displayed in the Configuration Alarms window when an
attribute of a component in this class attains an alarm-level unexpected value.
This text can contain keywords to indicate the substitution of variable
information. A value of Unknown indicates that Status should not raise alarms
for components in this class.
For further information on changing component class characteristics, see 7.3.
5. Click the File menu and then Exit Classification Definition to close the Define Status
Classification table. If you have made changes to the classification that you have not
saved, the Configuration application asks whether you want to save the changes
before closing the table.
7.2.2. Selecting a Different Classification
Use the following procedure to select a different classification or to create a new
classification:
1. Click the File menu in the Define Status Classification window.
2. Click Select Classification. The Configuration application displays a dialog window
with the names of available classifications.
3. Click the name of the classification you want to change, or click Unknown to create a
new classification. The Define Status Classification table displays component
classes for the classification you selected.
If you clicked Unknown to create a new classification, the table is empty.
If you made changes to the previous classification that you have not saved, the
Configuration application asks if you want to save the changes before it closes the
previous classification.
7.2.3. Saving Classifications
After you change the component class definitions in a classification, you can replace the
previous definitions with the new definitions using the following procedure:
1. Click the File menu of the Define Status Classification window.
2. Click one of the following to perform the desired action:
• Save Classification
Saves the changed class definitions under the current classification name. The
Configuration application then replaces the previous definitions with the new
definitions. If you are editing a new classification, the Configuration application
asks you to name it at this time.
7833 4778–008 7–5

Defining Status Classifications
• Save Classification As
Creates a new classification and leaves the old one intact. A dialog window
opens. Enter the name of the new classification. Click Explain for a description
of the guidelines the name must conform to. The classification is saved when
you click OK. The new classification becomes the current classification, and its
name appears in the title bar of the Define Status Classification table, and in the
About window.
Note: If a user of Status is currently using the classification you saved, the changes you
made are not visible until the other user does a Select Classification.
7.2.4. Deleting Classifications
Use the following procedure to delete one or more classifications. Once you delete a
classification, you can no longer retrieve it.
1. Click the File menu of the Define Status Classification table.
2. Click Delete Classifications. A dialog window opens.
3. Select one or more classifications.
4. Click OK to delete them.
You cannot delete a classification that
• You are currently editing
• Another user of the Configuration application is editing
• Single Point Operations Status is using
Diagram definitions and component sets depend on both the configuration and
classification under which they were defined. When you delete a classification, all
diagram definitions and component sets related to it are automatically deleted.
7–6 7833 4778–008

Changing Component Class Characteristics
7.3. Changing Component Class Characteristics
The following subsection provides information on changing class characteristics.
7.3.1. Renaming a Component Class
To rename a component class, click the name of the component class in the Define
Status Classification table. A pop-up menu with two entries appears:
• Edit Class
Click this entry to bring up the characteristics list for the class. (See 7.6.)
• Rename Class
Click this entry to bring up a dialog window for renaming the class.
Since the component classes in the Define Status Classification table are listed in
alphabetical order, the position of a class may change when you rename it.
When you rename component classes, all diagram definitions and component sets
associated with the classification being edited are rewritten to reflect the name changes
when the classification is saved. This can be time consuming.
7.3.2. Selecting the Internal Class
Click the value in the Internal Class column to change the internal class for a component
class. The possible values for Internal Class are
• OS2200—Use only for the component class that represents OS 2200 host systems.
• CONSOLE—Use only for the component class that represents OS 2200 system
consoles.
• MCP—Use only for the component class that represents MCP host systems.
• ANSI_X3_64—Use only for the component class that represents UNIX host systems.
• GENERAL—Use for all other types of components you want to monitor with Status.
You can assign each internal class, except GENERAL, to no more than one component
class. All internal classes except GENERAL automatically include extra attributes that
monitor the operating state and connections of the host systems or system consoles
modeled by the components in the class. These extra attributes are described in 4.4,
4.5, 4.6, and 4.7. Each of these component classes must include a status attribute
named “Status.” (See 7.5.)
7.3.3. Selecting System Types
Click a value in the System Types column to specify the types of hosts to which a
component class applies. Status creates and monitors components of a class only for
those types of host systems to which the class applies. Not all component classes apply
7833 4778–008 7–7

Changing Component Class Characteristics
to all types of hosts. Some component classes may apply to more than one type of host.
The System Types value lets Status know which component classes are associated with
which types of hosts. These types include MCP, OS 2200, ANSI X3.64, Windows, and
Arbitrary.
For example, suppose you want to monitor tape drives on OS 2200 systems. When you
define the component class for tape drives, select OS 2200 as its only System Type.
Note: You must specify a value for this class characteristic. If you leave it unspecified,
Status does not monitor any components of this class.
7.3.4. Changing the Class Label
Click a value in the Class Label column to change the label used by Status to identify a
class of components. The Configuration application opens a dialog window and queries
you for the label. The label can include any sequence of characters and can span
multiple lines. This label is included in the labels of the default component groups
created by Status. (See 5.1.)
7.3.5. Selecting the Icon Family
In the Configuration application, you can select a default icon family for each component
class. Status uses this icon family to depict the default component groups it creates for
components of this class (see 5.1.). All icons in the Status diagram are customizable.
To select an icon family for a component class, click the value in the Icon column. The
Configuration application opens a dialog window from which you choose the desired icon
family.
To display the icons comprising an icon family
1. Click Edit in the Define Status Classification menu bar.
2. Click Display Icon Family.
3. Select the name of an icon family from the dialog window showing all available icon
families.
A window appears showing icons representing the normal, attention, alarm, and empty
states depicted by Status:
• If the icons in the family are bitmaps, they all have the same size and shape but
different colors.
• If the icons in the family are pixmaps, their size, shape, and color can vary for each
state.
In Single Point Operations Level 7.4, the icons supplied with Status changed from singlecolor
bitmap icons to multicolor, three-dimensional pixmap icons. Existing diagrams can
continue to use the bitmap icons, or you can update the icons.
7–8 7833 4778–008

Changing Component Class Characteristics
The Configuration application enables you to update all obsolete bitmap icons in a
classification for a single operation:
1. Select Edit in the Define Status Classification menu bar.
2. Select Upgrade Obsolete Icons.
3. Click Yes to upgrade all obsolete icons in the classification
Note: The Upgrade Obsolete Icons menu entry is disabled if the diagram does not use
any obsolete bitmap icons.
See Appendix F for a description of the Status icon families that are supplied with Single
Point Operations.
7.3.6. Selecting the Default Scope
Click a value in the Default Scope column to change the default scope for components in
a component class. Whenever Status automatically creates a component in the
component class based upon receipt of an AC event report, Status sets the scope of the
component to the specified value. This table explains the possible values of the scope.
Value Description
Host The scope of the component is limited to a single host. Two
components with the same name and class on different hosts
refer to different actual components.
Shared The scope of the component includes all hosts monitored by
Status. Two logical components with the same name and class
and with a scope of Shared refer to the same actual component.
For example, specify a scope of Shared for disks that are shared
across multiple systems.
For a further discussion on component scope, see 4.2.
7.3.7. Selecting the Creation Scheme
Click a value in the Creation Scheme column to change the creation scheme for
components of a class. The value you select determines how Status handles an event
report it receives for a component of this class that does not already exist.
This table lists the possible Creation Scheme values.
Value Description
automatic If Status receives an event report for a component of this class
that it is not already monitoring, it automatically creates the
component and processes the event report. This is the default
value.
explicit_only Status ignores event reports for components of this class that are
7833 4778–008 7–9

Changing Component Class Characteristics
Value Description
not already defined. However, an entry is made in the Status log
(SP-STATUS) for these event reports if you have set the trace level
in Status to partial or full (see 2.5). You can define a component of
this class only by explicit action (see 6.1), or by retrieving a
component set containing the component (see 2.4 and 6.4).
none Status does not monitor components in this class under any
circumstances and ignores all event reports for components of
this class. If a user of Status retrieves a component set containing
a component in this class, Status ignores the component. Use
this value to effectively remove from a classification a component
class that you might want to restore later.
7.3.8. Selecting the Initialization Mnemonic [OS 2200 MCP]
Click a value in the Init Mnemonic column to change the initialization mnemonic, which
applies only to component classes with a System Type of OS 2200 or MCP. The
initialization mnemonic is used when Status calls the data collector to send initial
attribute values. The data collector identifies the component class by its initialization
mnemonic. For further information on the data collectors, see 2.1.
This table lists the possible values for the initialization mnemonic.
Value Description System Type
sys Host system OS 2200
tape Tape drive OS 2200
7–10 7833 4778–008
MCP
disk Disk drive OS 2200
MCP
ip Instruction processor OS 2200
iop Input/output processor OS 2200
chan Channel OS 2200
cu Control unit OS 2200
sa Storage area OS 2200
dev Any other device OS 2200
printer Printer MCP
application Application program registered with
API library
MCP
When you click the initialization mnemonic value for component classes whose System
Types include OS 2200 and MCP, a list of possible values is displayed.

Changing Component Class Characteristics
Note: If you specify an initialization mnemonic for any MCP component class, you must
include a class with an Internal Class of MCP in the classification; otherwise, the
component class is not initialized by the MCP data collector. If you specify an
initialization mnemonic for any OS 2200 component class, you do not need to include a
class with an Internal Class of OS2200 in the classification, but it is recommended that
you do.
7.3.9. Changing the Initialization Mnemonic [UNIX Windows
Other]
The Init Mnemonic column does not apply to component classes with a System Type of
ANSI X3.64, Windows, or Arbitrary. The initialization mnemonic value is always
Unknown, since there is no data collector for these types of host systems.
7.3.10. Specifying Reinitialization
Reinitialization determines if components in a class are reinitialized when the host that
the components are associated with reestablishes a connection to Status.
If set to yes (the default), all dynamically created components are deleted when the
connection is reestablished. The components that were explicitly created or were read in
from a component set have all their reported attribute values reset to defaults. Select
yes if the agent that reports component information depends on the connection between
Status and the host system.
If set to No, the components in that class will not be deleted or otherwise reinitialized
when a connection is reestablished with the host. Select no if the agent that reports the
component information can continue to operate even when the connection between
Status and the host system is down.
Reinitialization is specified on a class by class basis, providing maximum flexibility. To
change the value, click the Reinitialize value for the class to change it from yes to no or
no to yes.
7833 4778–008 7–11

Changing Component Class Characteristics
Figure 7–2. Changing the Reinitialize Value
7.3.11. Specifying the Instruction File
Click on a value in the Instruction File column to change the default file containing
operator instructions for components in a class. You can override this default for
individual components within the component class using Status, as described in 6.1.5.
To specify an instruction file
1. Click a value in the Instruction File column. The Configuration application asks for the
file name.
2. Enter the file name, or click Cancel to leave the file name unchanged. You can
specify an existing text file or a file that does not previously exist.
3. After you specify the file name, the Configuration application asks if you want to edit
the instruction file. If you reply Yes, the Configuration application displays an edit
window containing the current contents of the instruction file.
Follow these guidelines when editing text in an instruction file:
• When you enter text, an insertion point (a flashing vertical bar) indicates where the
text will appear.
• Use the arrow keys to move the insertion point. Press the Enter key to start a new
line of text.
7–12 7833 4778–008

Changing Component Class Characteristics
• Press the Delete key to delete the character ahead of the insertion point or the
Backspace key to delete the character behind the insertion point.
• You can copy text from any open window on your screen using Ctrl-C, move the
mouse pointer to the desired location in the edit window, click to move the insertion
point to that location, and press Ctrl-V to paste the selected text in the edit window.
When you are done editing the file, click File in the Edit window and then Exit to close
the window. The Configuration application asks whether you want to save the changes.
Note: If you prefer, you can use any text editor to edit an instruction file outside of the
Configuration application. These files reside in folder sp-data-folder\status\instructions.
7.3.12. Specifying Retention of Note Files
As described in 1.2 and 4.2, a user of Status can create a note file for any component
monitored by Status. When a component is deleted in Status, you might want its note
file deleted automatically, or you might want it retained in case another component is
later created with the same name, host, and class. Click a value in the Retain Notes?
column to specify this behavior for all components of a component class.
This feature applies to components that are deleted either by explicit user action (see 3.4
and 4.2), or by a DE event report received by Status. Notes for components that still
exist when Status terminates are retained regardless of which value you select for Retain
Notes?.
7.3.13. Specifying Alarm Text
The alarm text of a component class is displayed in the Configuration Alarms window of
Single Point Operations Console when an attribute of a component in this class attains
an alarm-level unexpected value.
You can edit the alarm text for a component class by clicking the value in the Alarm Text
column. The Configuration application displays a dialog window in which you can enter
the alarm text. If you do not want Status to raise any alarms for components in this
class, select Unknown instead.
The alarm text can include the following substitution strings. Each substitution string
must start with a backslash and an underline, be specified with uppercase letters, and
end with a backslash.
\_NAME\ The name of the component to which the alarm condition applies.
\_CLASS\ The class of the component.
\_HOSTID\ The host system containing the component.
\_ATTRIBUTE\ The name of the attribute that caused the alarm condition.
\_VALUE\ The value of the attribute that caused the alarm condition.
\_MESSAGE\ The value of the Message attribute for the component.
\_TIME\ The value of the Event Report Time attribute for the component.
7833 4778–008 7–13

Changing Component Class Characteristics
\_XXX\ The value of the site-defined attribute named XXX. You must specify
XXX with all uppercase letters, regardless of the case you used in the
actual name. If the actual name you specified contains a newline, tab,
or multiple consecutive spaces, you must replace these with a single
space in the substitution string.
Example
By default, the alarm text for each component class is
\_CLASS\ \_NAME\ on \_HOSTID\ has \_ATTRIBUTE\ = \_VALUE\
You define a component class named Tape with this alarm text to monitor tape drives.
For this class, you define a status attribute named “Status,” and specify down as an
alarm value for this attribute. In Single Point Operations Status, a tape drive named
DriveA is monitored on system Host1. If Single Point Operations Status receives an
event report from DriveA setting its Status to down, Single Point Operations Status
raises an alarm. The text of this alarm is as follows:
Tape DriveA on Host1 has Status = down
7–14 7833 4778–008

Adding and Deleting Component Classes
7.4. Adding and Deleting Component Classes
The following subsection provides information about
• Adding a component class
• Copying a component class
• Merging classifications
• Deleting classes
7.4.1. Adding a New Component Class
Use the following procedure to add a class to the current classification:
1. Click Edit in the menu bar of the Define Status Classification window.
2. Click Add Classes. A dialog window requesting the names of the new classes
appears.
3. Move your pointer to the text input line and type in the new class names. To enter
multiple class names, press the Enter key after each name. Each name must match
exactly the class name used in attribute-change (AC) and delete-object (DE) event
reports; however, the name is not case sensitive.
4. When the names are correct, click OK. The dialog window closes and the Define
Status Classification window is dynamically updated to include the new component
classes in alphabetical order.
5. The characteristics of these new classes are given default values; edit them as
described in 7.3 and 7.5.
Note: You must supply a value for the System Types characteristic after you add the
class, or the class will never be populated.
7.4.2. Copying a Component Class
Use the following procedure to add a class to the current classification by copying the
definition of another class in the classification:
1. Click Edit in the menu bar of the Define Status Classification window.
2. Click Copy Class. A dialog window requesting the name of the new class appears.
3. Type in the new class name, and then click OK. A second dialog window listing all
classes in the classification appears.
4. Double-click the class you want to copy. The dialog window closes and the new
class is inserted into the Define Status Classification window in alphabetical order.
5. Edit the characteristics of the new class as described in 7.3 and 7.5.
7833 4778–008 7–15

Adding and Deleting Component Classes
7.4.3. Merging Classifications
Use the following procedure to copy all component classes from another classification
into the current classification. This procedure can be useful if you have developed two
separate applications using Status, and you want to combine them.
1. Click File in the menu bar of the Define Status Classification window.
2. Click Merge Classification. A dialog window listing all other classifications appears.
3. Double-click the classification whose component classes you want to copy. The
dialog window and the Define Status Classification window close. After a few
seconds, the Define Status Classification window reappears with the copied
component classes inserted in alphabetical order.
If the selected classification contains classes with the same names as those in the
current classification, those classes are not copied, and a message stating this is
displayed. Similarly, if the selected classification contains classes with the same Internal
Class (except GENERAL) as the current classification, those classes are not copied, and a
message stating this is displayed.
7.4.4. Deleting Component Classes
Use the following procedure to delete classes from the current classification:
1. Click Edit in the menu bar of the Define Status Classification window.
2. Click Delete Classes. A dialog window listing all component classes in the
classification appears.
3. Click the names of the classes you want to delete.
4. After you have selected the classes you want to delete, click OK. The window
closes and the Define Status Classification window is dynamically updated.
7–16 7833 4778–008

7.5. Configuring Site-Defined Attributes
Configuring Site-Defined Attributes
This subsection provides information on configuring the following types of attributes:
• Status
• Numeric
• String
7.5.1. Configuring Status Attributes
You can define up to eight status attributes for each component class. The first status
attribute has the default name of “Status,” but you can change this name.
To define status attributes, click the Edit menu, click Configure Site-Defined Status
Attributes, and then click the number of the attribute you want to define. A table
appears with the following columns:
Attribute name
The name of the attribute. This name must match the attribute name used in
attribute-change event reports sent to Single Point Operations Status; however, the
name is not case sensitive. The name can span multiple lines and is displayed as
such in the Status displays. In event reports, replace any newline characters in the
name with spaces.
If you do not specify a name (Unknown), the attribute is not defined for the
component class, regardless of other values that you have specified for the attribute.
Do not specify any of the following as attribute names:
• APPL
• APPLQUAL
• SENDER_TIME
• SERVER_TIME
Possible values
A list of all possible values for this attribute. Click these values in the table to add to
them, to delete from them, or to alter them. If you add more values, press the Enter
key after each value. These values are case sensitive. Click OK or Cancel to close
this dialog window.
After you specify the possible values for this attribute, group them into three sets:
expected values, attention values, and alarm values. Do this by selecting the
expected and alarm values using the next two columns. Attention values are the
possible values you do not select as either expected or alarm values.
Expected values
The list of attribute values that do not cause an attention or alarm exception. When a
component is created automatically by Status, it assumes the expected values you
specify here. Click these values to select additional ones, or to remove values you
7833 4778–008 7–17

Configuring Site-Defined Attributes
previously selected. You can choose from all the possible values you specified in the
Possible Values column, except any you have already selected as alarm values.
You can also select hyphen (-) as an expected value. The hyphen represents the
value of the attribute before any event report has set its value. If you select this as
an expected value, then the operator's attention will not be drawn to this attribute
prior to it receiving a value.
If you select Unknown as the expected value, when a component of this class is
created, Status sets its only expected value to the first nonalarm value it receives for
the component.
The expected values you specify are defaults for the component class. To change
the expected values, see 4.3.1 and 6.1.6.
Alarm values
The list of values that cause an alarm exception in Status. When a component is
created automatically by Status, it assumes the alarm values you specify here. Click
these values to select additional ones, or to remove values you previously selected.
You can choose from all the possible values you specified in the Possible Values
column, except any you have already selected as expected values.
You can also select hyphen (-) as an alarm value. The hyphen represents the value of
the attribute before any event report has set its value. If you select this as an alarm
value, then Status will raise an alarm for this attribute until it receives a value.
If you select Unknown as the alarm value, no value of this attribute causes an alarm
exception for components of this class.
The alarm values you specify are defaults for the component class. To change the
alarm values, see 4.3.1 and 6.1.6.
Alarm Id
You can use the Alarm Id to identify an alarm raised by Status in external alarm
actions, or to associate the alarm with help text. The default Alarm Id is the
component class name and the attribute name separated by a period. If you select
Unknown for the Alarm Id, Status does not raise an alarm when this attribute attains
an alarm value.
The Alarm Id is used only if you also specified Alarm Text for this component class.
(See 7.3.)
If the Alarm Id matches the name of an action list in the active alarm policy, then
Single Point Operations will perform the appropriate alarm actions from that action
list whenever this alarm is raised, acknowledged, or cleared. If the Alarm Id matches
the name of a file in the help folder, then the text in this file will be included in the
Alarm Detail window displayed for this alarm by Single Point Operations.
The Alarm Id can be a literal string, or it can contain one or more of the following
substitution strings. When Status raises an alarm for this attribute, it replaces each
substitution string with the indicated text. Each substitution string must start with a
7–18 7833 4778–008

Configuring Site-Defined Attributes
backslash and an underline, be specified in all uppercase letters, and end with a
backslash.
\_NAME\ The name of the component to which the alarm
condition applies
\_HOSTID\ The host system containing the component
\_VALUE\ The value of the attribute that caused the alarm
condition
Severity
The severity of any alarm raised by Status for this attribute, when the attribute
attains an alarm value. The default is major. This value is applicable only if you have
specified alarm text for the component class, and an alarm-id for this attribute.
Timeout
If Single Point Operations Status does not receive for the duration of the timeout
period an event report that sets this attribute for a component of this class, the
attribute is set to the default value. If you want to use this feature, you must provide
values in both the Timeout and Default columns. The Timeout value is expressed in
seconds.
Default
If Single Point Operations Status has not received an event report for a component
of this class for the duration of the Timeout period, the attribute for that component
is set to this default value. Click this value to select a different default. You can
choose as the default any of the values you specified as possible values, or you can
choose hyphen (-), which causes the attribute value to be reset to the unreported
state. The value you select as the default can be an expected value, an attention
value, or an alarm value.
Configure status attributes for component classes according to the requirements of your
site. A status attribute's name and values must match the attribute-value pairs in event
reports received by Single Point Operations Status. The attribute name is case
insensitive; attribute values are case sensitive. For further information about site-defined
status attributes, see 4.3. For information about specifying event reports, see the Single
Point Operations Administration and Configuration Guide.
7.5.2. Configuring Numeric Attributes
Each component class can include up to eight configured site-defined numeric attributes.
To configure a site-defined numeric attribute, click Edit in the menu bar, then Configure
Site-Defined Numeric Attributes, and then the number of the attribute you want to
define. The selected Configure Site-Defined Numeric Attribute table opens. The table
contains the following columns:
Attribute Name
The name of the numeric attribute. This attribute name must match the attribute
name used in attribute-change event reports sent to Single Point Operations Status,
except that the name is not case sensitive. The name can span multiple lines and is
7833 4778–008 7–19

Configuring Site-Defined Attributes
displayed as such in the Status displays. In event reports which set a value to this
attribute, replace any newline characters in the name with spaces.
If you do not specify an attribute name, then the attribute is not defined for the
component class, regardless of other values that you have specified for the attribute.
Do not specify any of the following as attribute names:
• APPL
• APPLQUAL
• SENDER_TIME
• SERVER_TIME
Default Alarm Minimum
The lowest value that does not cause an alarm exception. Any value less than this
number is considered an alarm value.
Default Attention Minimum
The lowest value that does not cause an attention exception. Any value less than
this number is considered an unexpected value.
Default Attention Maximum
The highest value that does not cause an attention exception. Any value greater than
this number is considered an unexpected value.
Default Alarm Maximum
The highest value that does not cause an alarm exception. Any value greater than
this number is considered an alarm value.
Unreported Value
This characteristic determines how Status will treat this numeric attribute in each
component of this class, before any event report assigns a value to the attribute. The
possible values are
normal An unreported value does not cause an attention or alarm condition.
This is the default.
attention An unreported value is treated as an attention condition, just as if the
value fell outside the attention thresholds but inside the alarm
thresholds.
alarm An unreported value is treated as an alarm condition, just as if the
value fell outside the alarm thresholds.
Alarm Id
You can use the Alarm Id to identify an alarm raised by Status in external alarm
actions, or to associate the alarm with help text. The default Alarm Id is the
component name and the attribute name separated by a period. If you select
Unknown for the Alarm Id, Status does not raise an alarm when this attribute attains
an alarm value.
7–20 7833 4778–008

Configuring Site-Defined Attributes
The Alarm Id is used only if you also specified Alarm Text for this component class.
(See 7.3.)
If the Alarm Id matches the name of an action list in the active alarm policy, then
Single Point Operations will perform the appropriate alarm actions from that action
list whenever this alarm is raised, acknowledged, or cleared. If the Alarm Id matches
the name of a file in the help folder, then the text in this file will be included in the
Alarm Detail window displayed for this alarm by Single Point Operations.
The Alarm Id can be a literal string, or it can contain one or more of the following
substitution strings. When Status raises an alarm for this attribute, it replaces each
substitution string with the indicated text. Each substitution string must start with a
backslash and an underline, be specified in all uppercase letters, and end with a
backslash.
\_NAME\ The name of the component to which the alarm condition applies
\_HOSTID\ The host system containing the component
\_VALUE\ The value of the attribute that caused the alarm condition
Severity
The severity of any alarm raised by Status for this attribute, when the attribute
attains an alarm value. The default is major. This value is applicable only if you have
specified alarm text for the component class, and an alarm-id for this attribute.
The Configuration application prevents you from specifying a value that is out of order.
For example, you cannot specify an Attention Maximum value that is less than the
Attention Minimum value or greater than the Alarm Maximum value.
The minimum and maximum values you specify using the Configuration application are
defaults for the component class. To change the threshold values, see 4.3.2 and 6.1.7.
For further information about site-defined numeric attributes, see 4.3. For information
about specifying event reports, see the Single Point Operations Administration and
Configuration Guide.
7.5.3. Configuring String Attributes
Each component class can include up to eight site-defined string attributes. To configure
string attributes, click Edit in the menu bar and then click Configure Site-Defined String
Attributes. The Configure Site-Defined String Attributes table opens.
The Configure Site-Defined String Attributes table has the following columns:
First String Attribute Name
The name of the first site-defined string attribute. This name must match the
attribute name used in attribute-change event reports sent to Single Point Operations
Status, except that the name is not case sensitive. The name can span multiple lines
and is displayed as such in the Status displays. In event reports that set a value to
this attribute, replace any newline characters in the name with spaces.
7833 4778–008 7–21

Configuring Site-Defined Attributes
Do not specify any of the following as attribute names:
• APPL
• APPLQUAL
• SENDER_TIME
• SERVER_TIME
Associated Attr
This attribute determines how the first string attribute is highlighted in Status
displays. By default, Status displays the string attribute value in component tables
and attribute lists without any highlighting. However, you can select one of the
status or numeric attributes that you defined for the class to control the highlighting
of this string attribute.
If you select one of these, the value of the string attribute is always displayed by
Status with the same highlighting as the selected attribute. Click the value in this
column and select one of the possible attributes to associate with the first string
attribute, or select Unknown to disable this feature. The possible attributes are the
names of site-defined status and numeric attributes you previously specified.
The rest of the columns in this table supply similar information for the remaining sitedefined
string attributes.
For further information about site-defined string attributes, see 4.3. For information
about specifying event reports, see the Single Point Operations Administration and
Configuration Guide.
7–22 7833 4778–008

7.6. Additional Specifications
7.6.1. Editing a Single Class
Additional Specifications
You might find it easier to edit all information for one component class from a single
window. The Configuration application provides a form that lets you view and edit all
characteristics that apply to a single component class.
To edit a single class, click the Edit menu, and then click Edit Single Class. A dialog
window opens presenting the names of all defined classes. Select a class to edit. The
list of characteristics for that class appears.
An alternative way to open the list of characteristics for a class is to click the name of the
class in the Define Status Classification table. A pop-up menu appears. Click Edit Class
in this menu.
After you have opened the list of characteristics for a component class, click the name of
any characteristic in this list to change its value.
7.6.2. Controlling Duplicate Alarm Behavior
If you are running multiple instances of Single Point Operations Status and monitoring
the same component from each, each instance of Status issues its own alarm for that
component. (The component is identified by its host, class, and component name.)
By default, these alarms are considered duplicate alarms and only one alarm appears in
the Configuration Alarms window of Single Point Operations Console. You can control
duplicate alarm behavior and choose to have the same alarm appear multiple times in the
Configuration Alarms window.
If you choose the default behavior of having these alarms considered duplicates and any
instance of Status clears an alarm, it is removed from the Configuration Alarms window.
Therefore if two instances of Status raise an alarm and one is terminated, the alarm is
cleared even though the other instance of Status is still running and has not cleared the
alarm.
To control duplicate alarm behavior
1. Click the Edit menu in the Define Status Classification table.
2. Click Select Behavior For Duplicate Alarms.
3. A dialog box asks you to select the desired behavior for duplicate alarms.
7833 4778–008 7–23

Additional Specifications
7–24 7833 4778–008

Appendix A
Troubleshooting
This appendix explains how to
• Use the event report logging capabilities of Single Point Operations Status
• Use the Unreported Components table to detect potential problems
• Report problems to Unisys
7833 4778–008 A–1

Event Report Logging
A.1. Event Report Logging
The event reports received by Single Point Operations Status are crucial to its correct
operation. Event reports specify attribute changes for monitored components. Some
event reports are created by SMART AMS, CP-AMS, and SP-AMS databases as a result
of specified message actions. SMART AMS runs on OS 2200 consoles, and CP-AMS
and SP-AMS run on the Single Point Operations server. Other sources of event reports
are the URM agent, and client applications, which send event reports by using the
spo_event command or the Event Server API.
Status provides a facility for logging the event reports that it receives and processes.
This enables you to verify that the event reports sent by various sources do what you
expect.
For further information about event reports, see the Single Point Operations
Administration and Configuration Guide.
A.1.1. Trace Levels
Logging of event reports by Status is controlled through the item Select Trace Level in
the File menu of the Status diagram, as described in 2.5. Click this menu item to choose
one of three levels of tracing:
• None
No logging of event reports is done. This is always the initial value when you start
Status. (To enable logging during initialization of a classification or configuration, first
change the trace level and then select the configuration or classification whose
initialization you want to monitor.)
• Partial
Event reports that Status could not process completely are logged. One or more
explanations of the cause follow each event report. Note that an event report that
could not be processed completely by Status is not necessarily an error. In some
cases, one instance of Status might receive event reports that apply to another
instance of Status (running a different classification, for example) or to another
process entirely. When you analyze the log of event reports, you must decide which
unprocessed event reports represent errors and which represent anticipated
situations.
• Full
All event reports received by Status are logged. The message type field in the log
distinguishes event reports that were processed completely from event reports that
were not processed completely. As with a trace level of Partial, the event reports
that Status could not process completely are followed by one or more explanations.
A.1.2. SP-STATUS Log
Status writes its trace information to the Single Point Operations log named SP-STATUS.
This log can be selected and viewed by using the Log Viewer, just like any other log
A–2 7833 4778–008

Event Report Logging
produced by Single Point Operations. For further information about using the Log
Viewer, see the Single Point Operations Console User Guide.
A.1.3. Log Message Information
Each log message Status writes to the log SP-STATUS includes the following
information:
• The source of the message, which is always STATUS.
• A message type code, explained in the following subsection.
• The time the event report was received by Status.
• An application qualifier (APPLQUAL), which is the Single Point Operations
workstation name and the process-id (pid) of the instance of Status that added the
message to the log. This information is important only if you have multiple instances
of Status, each with event report tracing turned on simultaneously (which is not
recommended).
• The text of the log message. This text is either a copy of an event report received by
Status or an information message. Messages that echo event reports are preceded
by the name of the host from which the event report came. Event reports from
SMART AMS and CP-AMS are also preceded by the name of the OS 2200 console
that generated the event report.
A.1.4. Message Type Codes
The log SP-STATUS contains log entries with three different message type codes:
EN This code indicates an environment change in Status. These log messages are
added to the log every time you select a different trace level, configuration, or
classification in Status. These messages enable you to track environment changes
that affect how event reports are processed and what appears in the log.
EX This code flags an event report for which Status detected one or more exceptions
that prevented the complete processing of the event report. This code also flags
the information messages that follow such an event report and explain why the
event report was not completely processed.
NO This code flags event reports that Status was able to process completely and
normally. These event reports appear in the log only when you set the trace level
to Full.
A.1.5. Exception Conditions
Status flags the following conditions as exceptions in the log SP-STATUS. Unless
otherwise stated, the entire event report is discarded when one of these exceptions is
detected.
• Inappropriate event report type. Status can process only event reports with
TYPE=AC (attribute change) or TYPE=DE (delete object).
• The component class specified in the event report either does not exist in the
classification currently being used by Status, or this class exists but has a Creation
7833 4778–008 A–3

Event Report Logging
Scheme equal to none. Remember that class names specified in event reports are
not case sensitive. (See 7.3.)
• The component class and host specified in the event report are not compatible.
When the component class was defined using the Single Point Operations
Configuration application, the System Types specified for the component class did
not include the system type of the host to which the event report refers. (See 7.3.)
• A component with the name (instance) specified in the event report does not exist
for the class and host to which the event report applies. For AC event reports, this
exception can occur only if the Creation Scheme for the class is “explicit_only.” This
means that automatic creation of components is not done for that class. Remember
that the component name (instance) specified in an event report is case sensitive.
• An attribute name included in the event report (on the left side of the equal sign) is
not defined in the class to which the event report applies. In this case, the attribute
is ignored, but the rest of the event report is processed normally. Note that attribute
names are not case sensitive.
• An attribute value specified in the event report (on the right side of the equal sign) is
not legal for the attribute to which it applies. A value for a status attribute is
considered illegal if it is not one of those listed as a possible value for the attribute
when the class was defined. (See 7.5.) It is also illegal if a noninteger value is
specified for a numeric attribute. In these cases, Status sets the attribute to
unknown and processes the rest of the event report normally. Remember that
attribute values are case sensitive.
• An event report with TYPE=DE has attributes in addition to TYPE, CLASS,
INSTANCE, and HOST. In this case, Status processes the event report (that is, the
component is deleted), and ignores the extraneous attributes.
Note that the log SP-STATUS does not contain event reports with errors that were
detected by SMART AMS, CP-AMS, or SP-AMS, since these event reports are never
sent. For event report errors detected by SMART AMS and CP-AMS, you can examine
the log for the appropriate host. For event report errors detected by SP-AMS, you can
examine either the appropriate host log or the log SP-AMS.
A–4 7833 4778–008

A.2. Unreported Components Table
Unreported Components Table
The Unreported Components table is one of the component tables available in Status.
This table contains only components that were created by Status and for which no event
reports were received since you selected the current configuration and classification. For
detailed information about the Unreported Components table, see 3.4.
Typically, the components in the Unreported Components table either were created
explicitly during the current session of Status (see 6.1), or were brought in as part of a
component set that you retrieved (see 2.4 and 6.4). The presence of a component in this
table does not necessarily indicate an error. However, you can examine this table to see
components for which Status has received no information (event report). Absence of
such information can indicate a problem in the SMART AMS, CP-AMS, or SP-AMS
database, or in another agent that generates the event reports.
Another possible cause for a component in this table is a problem in the connection
between the Single Point Operations server and the host or OS 2200 console that
contains the component. Absence of an event report can also indicate that the
component was given an incorrect name when it was explicitly created. Remember that
component names are not case sensitive.
7833 4778–008 A–5

Reporting Problems
A.3. Reporting Problems
When you have problems using this product or need further assistance, call a Unisys
Support Center:
• In the United States and Canada, the number to call for support is 1-800-328-0440.
Call between 8:00 a.m. and 8:00 p.m., Eastern Time, Monday through Friday,
excluding holidays.
• Outside the United States, call the Unisys Support Center number provided by your
sales representative.
When you report a problem to the Unisys Support Center, describe what is happening as
best you can. Include any pertinent information such as your Single Point Operations
server hardware and software levels, any unusual circumstances before encountering
the problem, and any actions you have taken to resolve the problem.
Contact your site administrator, if you have one, for all software problems before calling
the Unisys Support Center.
A–6 7833 4778–008

Appendix B
Tape Monitor for OS 2200 Hosts [OS
2200]
This appendix describes the Tape Monitor for OS 2200 hosts, which is a specific use of
Single Point Operations Status provided with all editions of Single Point Operations. The
OS 2200 Tape Monitor provides status information about the OS 2200 host and tape
component classes. For status information about other component classes, your site
must purchase and install the Department or Enterprise Edition of Single Point
Operations.
Follow the guidelines in this appendix when using this application. Study this application
as an example before developing applications of your own.
7833 4778–008 B–1

Tape Monitor Features
B.1. Tape Monitor Features
The OS 2200 Tape Monitor includes the following:
• A classification definition called TapeMonx.y.z, which defines the component classes
required by the application. For detailed information about the classification
TapeMonx.y.z, where x.y.z is the release level of Single Point Operations, see B.2.
• Component group table templates, which include the columns you typically need to
view to monitor tape load requests.
• The SMART AMS or CP-AMS database patterns needed to match the load, service,
and other console messages involved in tape loading. The actions associated with
these patterns are event reports specific to the component classes 2200_Host and
Tape. These patterns are contained in file tapmon22.bld in
sp-data-folder\os2200-ams on the Single Point Operations server. You must include
these patterns in the active SMART AMS or CP-AMS database of the OS 2200
system console of each host with tape drives you want to monitor.
B.1.1. Capabilities
The OS 2200 Tape Monitor application enables you to
• Display a component table that shows all tape drives that are not operational or that
require a cartridge to be loaded.
• Define component groups so that tape drives are organized into groups based on the
hosts to which they are connected, their physical locations in the computer room, or
some other site-specific criteria. For each group, you can display a different table
identifying the units in the group that require service.
• Change the definition of the component classes and SMART AMS or CP-AMS
database patterns to reflect local terminology or to capture additional information
from load, service, and other tape-related console messages.
B.1.2. Accessing the Tape Monitor Application
To access the OS 2200 Tape Monitor application, select the classification TapeMonx.y.z
when you start Status. Status provides a default diagram for use with the OS 2200 Tape
Monitor. You can select the default diagram or you can define your own diagrams. For
further information about diagram definitions, see Section 5.
You may want to combine the OS 2200 Tape Monitor application with other applications
for Status that your site develops. You can do this by adding the patterns in the SMART
AMS or CP-AMS database tapmon22 to your own SMART AMS or CP-AMS database,
and by merging the classification TapeMonx.y.z with your own classification, as
described in 7.4.
B–2 7833 4778–008

B.2. TapeMon Classification [OS 2200]
TapeMon Classification [OS 2200]
This subsection provides a detailed description of the classification TapeMonx.y.z
supplied by Unisys as part of the Basic Edition of Single Point Operations. As supplied,
this classification works in conjunction with the SMART AMS or CP-AMS database
tapmon22, which is located in sp-data-folder\os2200-ams on the Single Point Operations
server. Your site can alter both the classification TapeMonx.y.z and the database
tapmon22 to suit your specific needs as long as complementary changes are made to
each.
For information on modifying classifications, see Section 7. For information on modifying
AMS databases, see the SMART Administration and Configuration Guide.
The classification TapeMonx.y.z contains the classes Tape and 2200_Host. The class
Tape is used to monitor tape drives on OS 2200 hosts, and the class 2200_host is used
to monitor OS 2200 hosts.
B.2.1. Tape Class Characteristics
The class Tape has the following characteristics:
• Internal Class = GENERAL. This is used for all classes except those used to monitor
host systems and system consoles.
• System Types = OS 2200. This indicates that components in this class apply only to
OS 2200 Series hosts.
• Creation Scheme = automatic. This implies that Status automatically creates a
component in this class if it receives an event report for a component in the class
that it was not monitoring previously.
• Init Mnemonic = tape. This causes Status to request that the OS 2200 data
collector, which is part of the OMKEY background run, retrieve information for all
tape drives when it establishes connection with each OS 2200 host.
• Default Scope = Host. This implies that components in this class are, by default, not
shared across different hosts.
• Icon = tape_lg. This is the pixmap icon family tape_lg.png supplied with Status.
• Instruction File is unspecified. These files contain site-specific operator instructions
and are, therefore, not supplied by Unisys.
• Alarm Text = “\_CLASS\ \_NAME\ on \_HOSTID\ has \_ATTRIBUTE\ = \_VALUE\.”
This causes Status to raise an alarm whenever an attribute of a tape component
attains an alarm value. The alarm appears in the Configuration Alarms window of
Single Point Operations Console. In the alarm text, the strings enclosed by
backslashes are replaced by the appropriate values for the tape drive causing the
alarm.
• The class Tape has three site-defined status attributes: Status, Load, and
Aux_Condition.
The attribute Status for the class Tape has the following values defined: UP, DOWN,
RESERVED, SUSPENDED, and NOT_AVAILABLE. The default expected value for
7833 4778–008 B–3

TapeMon Classification [OS 2200]
this attribute is not specified (unknown). This causes the first actual Status value
received in an event report to become the expected Status value for each tape drive.
The first event report results from matching a message produced by the data
collector, so the expected Status value for each component is the value reported by
the data collector. Since none of the Status values is defined as an alarm value, all
the remaining values are treated as attention values. The attribute Status has no
timeout period or default value defined.
The attribute Load is used to monitor whether or not a tape drive requires a reel or
cartridge to be mounted. This attribute has the following possible values: no, yes,
and service. Of these, no (indicating no outstanding load or service message) is the
expected value, yes (indicating an outstanding load message) is the attention value,
and service (indicating an outstanding service message) is the alarm value. The
alarm-id associated with this attribute is Tape.Load, so Status raises an alarm with
ALARMID = Tape.Load whenever this attribute attains a value of service. Status
clears the alarm when the attribute attains any value other than service. The timeout
period for the attribute Load is 150 seconds, and the default value is no. The timeout
period was chosen to be somewhat larger than the usual OS 2200 interval between
load and service messages (120 seconds).
The attribute Aux_Condition is used to report auxiliary conditions that can apply to a
tape drive.
This attribute has the following possible values:
none No auxiliary condition is present.
remove_ring A reel was mounted on the drive with a write ring, which must be
removed.
add_ring A reel was mounted on the drive without a write ring, but a write
ring is required.
wrong_reel The incorrect reel was mounted on the drive.
supply_reelid There is an outstanding message requiring the operator to enter
the identifier of the reel that was mounted on the drive.
not_ready The tape drive is offline.
Of these values, none is the expected value, and all others are attention values. The
attention values are set as the result of specific error messages that are matched in
the AMS database tapmon22. The attribute Aux_Condition has no default value or
timeout period.
• The class Tape has four site-defined string attributes: Equipment _Mnemonic,
Reel_Id, Ring ?, and Runid.
The string attribute Equipment_Mnemonic contains the equipment mnemonic for the
tape drive, as supplied by the OS 2200 data collector.
The string attribute Reel_Id contains the reel-id or cartridge-id extracted by the
database tapmon22 from the most recent load or service message sent for the tape
drive. The attribute Reel_Id is associated with the site-defined status attribute Load,
so that the reel-id appears in all component tables and attribute lists with the same
B–4 7833 4778–008

TapeMon Classification [OS 2200]
color coding as the attribute Load. With this association, your site might decide not
to display the attribute Load in tables where the attribute Reel_Id appears.
The string attribute Ring ? indicates whether or not a write ring is required for the
volume to be mounted on the tape drive. The AMS database tapmon22 extracts this
information from the most recent load or service message sent for the tape drive.
Note that this attribute name includes a space before the question mark.
The string attribute Runid gives the run-id of the run that requested a volume to be
mounted on the drive. The AMS database tapmon22 extracts this information from
the most recent load or service message sent for the tape drive.
• There are no site-defined numeric attributes defined for the class Tape.
• The class Tape also includes the string attributes Message and Time, which are
automatically included in all component classes. Your site can use these to include a
text message and event report time with event reports sent to Status. The AMS
database tapmon22 as supplied with Single Point Operations does not set either of
these attributes.
B.2.2. Host Class Characteristics
The class 2200_Host has the following characteristics:
• Internal Class = OS2200. This is used only for a class that monitors OS 2200 hosts.
• System Types = OS 2200. This implies that components in this class apply only to
OS 2200 hosts.
• Creation Scheme = explicit_only. This implies that only OS 2200 hosts defined in the
current configuration are monitored by Status. (This is the only value allowed for this
class.)
• Init Mnemonic = sys. This causes Status to request that the OS 2200 data collector
retrieve configuration information about the host when it establishes connection with
the host. This information includes the attributes Exec_Level, System_Type, and
Site_Id. If your site is not interested in displaying any of this information, you can set
Init Mnemonic to unknown for the class 2200_Host.
• Default Scope = Host. This is because host components cannot be shared across
different hosts.
• Icon = 2200Host_lg. This is the pixmap icon family 2200Host_lg.png supplied with
Status.
• Instruction File is unspecified because these files contain site-specific operator
instructions and are, therefore, not supplied by Unisys.
• Alarm Text = “\_CLASS\ \_NAME\ on \_HOSTID\ has \_ATTRIBUTE\ = \_VALUE\.”
This causes Status to send an alarm event to Single Point Operations whenever an
attribute of a 2200_Host component attains an alarm value. The alarm event report
causes an alarm to appear in the Configuration Alarms window of Single Point
Operations Console. In the alarm text, the strings enclosed by backslashes are
replaced by the appropriate values for the host causing the alarm.
7833 4778–008 B–5

TapeMon Classification [OS 2200]
• The class 2200_Host has one site-defined status attribute named “Status.” This
attribute has the possible values initializing, up, and down defined. The value
initializing indicates that the host is up and that Status has an active connection to
the host, but that continuous display messages are not being received from the host.
The value up indicates that the host is up, that Status has an active connection to the
host, and that continuous display messages are being received from the host. The
value down indicates that Status does not have an active connection to the host
(although the host itself might be running). When the attribute Status of an OS 2200
host is down or initializing, the attribute values for the Tape components associated
with that host are not current because Status is no longer receiving event reports for
any of the components associated with that host.
• Because the class 2200_Host is implemented using the internal class OS2200, the
2200_Host class automatically includes the following additional attributes:
Data_Collection, Connected_Consoles, Exec_Level, System_Type, and Site_Id.
These are described in 4.4. For the purposes of the classification TapeMonx.y.z, only
Data_Collection is important.
• The attribute Data_Collection indicates the outcome of the data collection process for
that host. The value of this attribute is set by Status based on information it
maintains internally and information sent from the AMS database tapmon22. In
particular, the values ready, in_progress, OMKEY_not_running, and completed are
set as the result of actions in the tapmon22 database. You can usually see the
values not_started, ready, initiated, and in_progress during initialization of the
connection between Status and the host. These are attention values and should be
present only for a short time. The value completed indicates either that the data
collection process has completed successfully or that no component classes
required initialization. The values OMKEY_not_running and errored are treated as
alarm values. OMKEY_not_running indicates that the OMKEY background run was
not started on the host; errored indicates that Status was not able to send the
console keyin that initiates the data collector. When Data_Collection assumes one of
the alarm values, Status raises an alarm with ALARMID = 2200_Host.DataCollection.
Status clears the alarm when this attribute attains any non-alarm value.
B.2.3. Diagrams and Component Sets
No diagrams or component sets are supplied with the classification TapeMonx.y.z
because these definitions also depend on the configuration being monitored, which your
site must define. However, when Status is brought up with the classification
TapeMonx.y.z, you can choose to have it create default component groups for each
combination of host and component class. Because there are only two component
classes, two of these groups are created for each OS 2200 host in the configuration you
select.
B.2.4. Component Group Table Templates
Also supplied with Status are a small number of predefined Component Group table
templates. Some of these templates, as their names indicate, are intended especially for
use with the classification TapeMonx.y.z Status also creates a table template named for
each of the two classes in this classification; each of these templates contains all of the
site-defined attributes in the associated class. When you define customized diagrams in
B–6 7833 4778–008

TapeMon Classification [OS 2200]
Status, you can use the supplied table templates as they are, alter the supplied
templates, or create your own templates.
7833 4778–008 B–7

TapeMon Classification [OS 2200]
B–8 7833 4778–008

Appendix C
Tape Monitor for MCP Hosts [MCP]
This appendix describes the MCP Tape Monitor, which is a specific use of Single Point
Operations Status. The MCP Tape Monitor provides status information about the MCP
host and tape component classes. MCP Tape Monitor is provided with Department and
Enterprise Edition of Single Point Operations.
Follow the guidelines in this appendix when using this application. Study this application
as an example before developing applications of your own.
7833 4778–008 C–1

Tape Monitor Features
C.1. Tape Monitor Features
The MCP Tape Monitor includes the following:
• A classification definition called MCPTapeMonx.y.z, which defines the component
classes required by the application. For detailed information about the classification
MCPTapeMonx.y.z, where x.y.z is the release level of Single Point Operations,
see C.2.
• Component group table templates, which include the columns you typically need to
view to monitor tape load requests.
• The Single Point Autoaction Message System (SP-AMS) database patterns needed to
match the tape messages and other system messages involved in tape loading,
which are sent by the MCP host agent. The actions associated with these patterns
are event reports specific to the component classes MCP_Host and MCP_Tape.
These patterns are contained in the text file MCPMon.bld in sp-data-folder\sp-ams on
the Single Point Operations server. You must include these patterns in the active
SP-AMS database on the Single Point Operations server. Please read the comments
in file MCPMon.bld for detailed information.
C.1.1. Capabilities
The MCP Tape Monitor application enables you to
• Define component groups so that tape drives are organized into groups based on the
hosts to which they are connected. For each group, the operator can display a
different table identifying the units in the group that require service.
• Change the definition of the tape component classes and SP-AMS database patterns
to reflect local terminology or to capture additional information from other taperelated
messages.
C.1.2. Accessing the Tape Monitor Application
To access the MCP Tape Monitor application, select the classification MCPTapeMonx.y.z
when you start Status. Status provides a default diagram for use with the MCP Tape
Monitor. You can select the default diagram or you can define your own diagrams. For
further information about diagram definitions, see Section 5.
You may want to combine the MCP Tape Monitor application with other applications for
Status that your site develops. You can do this by adding the patterns in the SP-AMS
database MCPMon to your own SP-AMS database, and by merging the classification
MCPTapeMonx.y.z with your own classification, as described in 7.4.
C–2 7833 4778–008

C.2. MCPTapeMon Classification
MCPTapeMon Classification
This subsection provides a detailed description of the classification MCPTapeMonx.y.z
supplied by Unisys as part of Single Point Operations Department and Enterprise
Editions. As supplied, this classification works in conjunction with the SP-AMS database
MCPMon, which is also supplied with Single Point Operations. Your site can alter both
the classification MCPTapeMonx.y.z and the database MCPMon to suit your specific
needs, as long as you make complementary changes to each.
For information on modifying classifications, see Section 7. For information on modifying
SP-AMS databases, see the Single Point Operations Single Point Autoaction Message
System Administration Guide.
The classification MCPTapeMonx.y.z contains the classes MCP_Tape and MCP_Host.
The class MCP_Tape is used to monitor tape drives on MCP hosts and the class
MCP_host is used to monitor MCP hosts.
C.2.1. MCP_Tape Class Characteristics
The class MCP_Tape has the following characteristics:
• Internal Class = GENERAL. This is used for all classes except those used to monitor
host systems and system consoles.
• System Types = MCP. This implies that components in this class apply only to MCP
hosts.
• Creation Scheme = automatic. This implies that Status automatically creates a
component in this class when it receives an event report for a component in the
class that it was not monitoring previously.
• Init Mnemonic = tape. This causes Status to request that the MCP data collector,
which is part of the Single Point Operations Interface for ClearPath MCP, retrieve
information for all tape drives when it establishes connection with each MCP host.
• Default Scope = Host. This implies that components in this class are not shared
across different hosts.
• Icon = tape_lg. This is the pixmap icon family tape_lg.png supplied with Status.
• Instruction File is unspecified. These files contain site-specific operator instructions
and are, therefore, not supplied by Unisys.
• Alarm Text = “\_CLASS\ \_NAME\ on \_HOSTID\ has \_ATTRIBUTE\ = \_VALUE\.”
This causes Status to raise an alarm whenever an attribute of an MCP_Tape
component attains an alarm value. The alarm appears in the Configuration Alarms
window of Single Point Operations Console. In the alarm text, the strings enclosed
by backslashes are replaced by the appropriate values for the tape drive causing the
alarm.
• The class MCP_Tape has two site-defined status attributes: Status and
Volume-Scratch.
The attribute Status for the class MCP_Tape has the following possible values
defined: ONLINE, OFFLINE, RESERVED, SAVED, READY, FREED and INUSE. The
7833 4778–008 C–3

MCPTapeMon Classification
default expected value for this attribute is not specified (unknown). This causes the
first actual Status value received in an event report to become the only expected
Status value for each component. The first event report results from matching a
message produced by the MCP data collector, so the expected Status value for each
component is the value reported by the data collector. Since none of the Status
values is defined as an alarm value, all the remaining values are treated as attention
values. The attribute Status has no timeout period or default value defined.
The attribute Volume-Scratch is used to indicate tapes that no longer have valid data
(Purged). Possible values are Y, N, and blank. All of these are defined as expected
values, so this attribute effectively acts as a string attribute.
• The class MCP_Tape has four site-defined string attributes: Write-Enabled, Serial-
Number, Tape-Name, and Tape-Density.
The string attribute Write-Enabled shows whether the tape currently on this drive is
write enabled. If no tape is mounted, this attribute is represented by a hyphen (-).
The string attribute Serial-Number contains the reel or cartridge identifier for the tape
currently mounted on this tape drive. If no tape is mounted, this attribute is
represented by a hyphen (-).
The string attribute Tape-Name displays the tape name for the tape currently
mounted. If no tape is mounted, this attribute is represented by a hyphen (-).
The string attribute Tape-Density indicates recording density of the tape currently
mounted on this drive. If no tape is mounted, this attribute is represented by a
hyphen (-).
• There are no site-defined numeric attributes defined for the class MCP_Tape.
• The class MCP_Tape also includes the string attributes Message and Time, which
are automatically included in all component classes. Your site can use these to
include a text message and event report time with event reports sent to Status. The
SP-AMS database MCPMon, as supplied with Single Point Operations, does not set
either of these attributes.
C.2.2. Host Class Characteristics
The class MCP_Host has the following characteristics:
• Internal Class = MCP. This is used only for a class that monitors MCP hosts.
• System Types = MCP. This implies that components in this class apply only to MCP
hosts.
• Creation Scheme = explicit_only. This implies that only MCP hosts defined in the
current configuration are monitored by Status.
• Init Mnemonic is unspecified, because the Single Point Operations Interface for
ClearPath MCP does not report initialization information for the host system itself.
• Default Scope = Host. This is because host components cannot be shared across
different hosts.
C–4 7833 4778–008

MCPTapeMon Classification
• Icon = MCPHost_lg. This is the pixmap icon family MCPHost_lg.png supplied with
Status.
• Instruction File is unspecified because these files contain site-specific operator
instructions and are, therefore, not supplied by Unisys.
• Alarm Text = “\_CLASS\ \_NAME\ on \_HOSTID\ has \_ATTRIBUTE\ = \_VALUE\.”
This causes Status to raise an alarm whenever an attribute of an MCP_Host
component attains an alarm value. The alarm appears in the Configuration Alarms
window of Single Point Operations Console. In the alarm text, the strings enclosed
by backslashes are replaced by the appropriate values for the host causing the alarm.
• The class MCP_Host has one site-defined status attribute named “Status.” The
Status attribute has the possible values active, inactive, timeout, busy, and
unrecognized.
Active Single Point Operations Status has successfully created a
communications link to the system.
Inactive Monitoring is off for the host system or the host system is down.
Timeout No message traffic was sent within the time interval specified for
the host in the configuration.
Busy Two Single Point Operations servers are trying to connect to the
same host. The host whose Status is busy is connected to
another Single Point Operations server.
Unrecognized The network name specified for the host in the configuration does
not appear in the hosts file or Domain Name Server on the Single
Point Operations server.
When the attribute Status of an MCP host is inactive, busy, or unrecognized, the
attribute values for the tape components associated with that host are not current
because Status is no longer receiving event reports for any of the components
associated with that host.
• Because the class MCP_Host is implemented using the internal class MCP, the class
MCP_Host automatically includes the following additional attributes: Monitor,
Connected_To_Application, Data_Collection, and Host_Agent_Active. These are
described in 4.6. For the purposes of the classification MCPTapeMonx.y.z, only
Data_Collection and Host_Agent_Active are important.
• The attribute Data_Collection for a host indicates the outcome of the data collection
process for that host. The value of this attribute is set by Status based on
information it maintains internally and information sent from the SP-AMS database
MCPMon.
In particular, the values in_progress and completed are set as the result of actions in
the database MCPMon. You can usually see the values not_started, initiated, and
in_progress during initialization of the connection between Status and the host.
These are attention values and should only be present for a short time. The value
completed indicates either that the data collection process has completed
successfully or that no component classes required initialization. The value errored is
treated as an alarm value and indicates that Status was not able to send the
command message that initiates the data collection process in the Single Point
Operations Interface for ClearPath MCP. When Data_Collection assumes this value,
7833 4778–008 C–5

MCPTapeMon Classification
Status raises an alarm with ALARMID = MCP_Host.DataCollection. Status clears
this alarm when the attribute attains any value other than errored.
• The attribute Host_Agent_Active indicates whether the MCP agent has sent at least
one utilization message to the Single Point Operations server. Status uses this
attribute to verify that the MCP agent is running and that a valid usercode/password
was sent to the interface software from the Single Point Operations server. Status
does not initiate the data collection process until the value of Host_Agent_Active is
yes. The active SP-AMS database on the Single Point Operations server must
contain a pattern that matches the utilization messages sent by the interface
software and it must send an event report setting Host_Agent_Active to yes as a
result. The database MCPMon contains a pattern that matches the utilization
messages and starts the data collection process.
C.2.3. Diagrams and Component Sets
No diagrams or component sets are supplied with the classification MCPTapeMonx.y.z
because they also depend on the configuration being monitored, which your site must
define. However, when Status is brought up with the classification MCPTapeMonx.y.z,
you can choose to have it create default component groups for each combination of host
and component class. Because there are only two component classes, two of these
groups are created for each MCP host in the configuration you select.
C.2.4. Component Group Table Templates
Also supplied with Status are a small number of predefined Component Group table
templates. Some of these, as their names indicate, are intended especially for use with
the classification MCPTapeMonx.y.z. Status also creates a table template named for
each of the two classes in this classification; each of these templates contains all of the
site-defined attributes in the associated class. When you define customized diagrams in
Status, you can use the supplied table templates as they are, alter the supplied
templates, or create your own templates.
C–6 7833 4778–008

Appendix D
UNIX Resource Monitor [UNIX]
This appendix describes the UNIX Resource Monitor, which is a specific use of Single
Point Operations Status. It is included with all editions of Single Point Operations.
Follow the guidelines in this appendix when using this application.
7833 4778–008 D–1

Using the UNIX Resource Monitor [UNIX]
D.1. Using the UNIX Resource Monitor [UNIX]
The UNIX Resource Monitor (URM) is a specific use of Status, which enables your site to
monitor selected resources on UNIX systems monitored by Single Point Operations.
The UNIX Resource Monitor provides status information about components in the
following component classes:
• UNIX hosts
• CPUs
• File systems
• Long-running processes
• Critical processes
• Users
D.1.1. UNIX Resource Monitor Features
The UNIX Resource Monitor includes the following:
• A classification definition named UnixMonx.y.z, which defines the component
classes monitored by the application. For detailed information about the classes and
attributes associated with the classification UnixMonx.y.z, where x.y.z is the release
level of Single Point Operations, see D.2.
• The URM agent, which is a set of shell scripts that must be installed on each
managed UNIX system. For information on installing and configuring the URM agent
on managed UNIX systems, see the Single Point Operations Administration and
Configuration Guide.
D.1.2. Capabilities
The UNIX Resource Monitor application enables you to define component groups so that
monitored resources are organized into groups. For each group, the operator can display
a different table identifying the units in the group that require service.
D.1.3. Accessing the UNIX Resource Monitor
To access the UNIX Resource Monitor, select the classification UnixMonx.y.z when you
start Status. Status provides a default diagram for use with the UNIX Resource Monitor.
You can select the default diagram or you can define your own diagrams. For further
information about diagram definitions, see Section 5.
You may want to combine the UNIX Resource Monitor with other applications for Status
that your site develops. You can do this by merging the classification UnixMonx.y.z with
your own classification, as described in 7.4.
This illustration shows the Status diagram for the classification UnixMonx.y.z.
D–2 7833 4778–008

D.1.4. UnixMon Classification
Using the UNIX Resource Monitor [UNIX]
Figure D–1. UnixMon Status Diagram
The classification UnixMonx.y.z supplied with Single Point Operations contains a set of
component classes, each with predefined attributes. This classification has alarm
generation turned on for all classes. This classification is described in D.2.
Your site can modify the classification UnixMonx.y.z to suit your specific needs. For
information on modifying classifications, see Section 7.
7833 4778–008 D–3

UnixMon Classification [UNIX]
D.2. UnixMon Classification [UNIX]
This subsection describes the component classes and attributes defined in the
classification UnixMonx.y.z. For information on customizing UnixMon classes and
attributes, see Section 7.
Data is supplied for each of the classes from each managed system on which your site
has installed and enabled the URM agent, and for which the URM policy that controls the
agent includes the class in its list of monitored classes.
D.2.1. UNIX Host Class
This class monitors each UNIX host system in the current configuration. There is one
such component for each ANSI X3.64 system in the configuration (including hosts not
running under UNIX and UNIX hosts on which the URM agent is not installed). This class
corresponds with the internal class ANSI_X3_64, which implies that its attribute named
Status reflects the network connection between Single Point Operations Status and the
managed system, see 4.7.
Attribute Description
Name This string attribute reports the name of the UNIX host as named
in the current configuration.
Status This status attribute reflects the network connection between
Single Point Operations Status and the managed system.
Possible values include active, inactive, busy, unrecognized, and
timeout. The expected value is active.
Heartbeat Status This status attribute indicates if the UNIX host is still operational,
and that the URM agent is still running on it. Possible values
include active and timeout. The expected value is active, and the
alarm value is timeout. The timeout period for this attribute is 150
seconds, which is 30 seconds longer than the default heartbeat
period on the URM agent. If 150 seconds has elapsed without the
URM agent sending a heartbeat event report, this attribute value
changes to timeout and an alarm is raised.
Users This numeric attribute reports the total number of unique
connections to the host. By default, this attribute has no
thresholds.
Connections This numeric attribute reports the total number of user
connections to the host. The URM agent determines this value by
counting the lines produced by the command who. By default,
this attribute has no thresholds.
Sample Period This numeric attribute reports the URM agent sample period. By
default, this attribute has no thresholds.
Heartbeat Period This numeric attribute reports the URM agent heartbeat period.
By default, this attribute has no thresholds.
D–4 7833 4778–008

D.2.2. CPU Class
Attribute Description
UnixMon Classification [UNIX]
OS Version This string attribute identifies the operating system version.
Model This string attribute identifies the UNIX system model as reported
by the command name.
The purpose of this class is to provide CPU utilization statistics. This class monitors each
UNIX host system in the current configuration for which CPU monitoring is enabled.
Single Point Operations Status automatically creates a component for each host as it
receives an event report for it. The URM agent generates the event reports.
Attribute Description
Name This string attribute reports the name of the UNIX host as named
in the current configuration.
Idle % This numeric attribute reports the percentage of time the system
is idle. The default minimum attention threshold is 15 (percent).
User % This numeric attribute reports the percentage of time the system
is running in user mode. The default maximum attention
threshold is 75 (percent).
System % This numeric attribute reports the percentage of time the system
is running in system mode. The default maximum attention
threshold is 75 (percent).
Wait % This numeric attribute reports the percentage of time the system
is waiting with some process blocked for input or output. The
default maximum attention threshold is 75 (percent).
D.2.3. FileSystem Class
This class monitors each file system on each host in the current configuration for which
file system monitoring is enabled. Status automatically creates a component in this class
for each file system as Status receives an event report for it. The URM agent generates
the event reports. The URM agent generates the event reports.
Attribute Description
Name This string attribute identifies the mount directory for the file
system.
Host This string attribute identifies the name of the host on which the
file system resides.
Inodes Free This numeric attribute reports the number of inodes not currently
allocated. By default, this attribute has no thresholds.
Space Used This string attribute reports the number of units of mass storage
currently allocated, where the units are blocks or kilobytes, as
indicated by the Unit attribute.
7833 4778–008 D–5

UnixMon Classification [UNIX]
Attribute Description
Inodes Used This string attribute reports the number of inodes currently
allocated.
Total This string attribute reports the total storage capacity of the file
system in units of blocks or kilobytes, as indicated by the Unit
attribute.
Unit This string attribute identifies the unit of measurement used for
the attributes Space Free, Space Used, and Total. Possible units
are blocks and Kbytes (kilobytes).
Percent Space
Used
Percent Inodes
Used
This numeric attribute reports the percentage of blocks used. The
default maximum attention threshold is 85 (percent). The default
maximum alarm threshold is 90 (percent).
This numeric attribute reports the percentage of inodes used. The
default maximum attention threshold is 85 (percent). The default
maximum alarm threshold is 90 (percent).
Space Free This numeric attribute reports the number of units of mass
storage not currently allocated, where the units are blocks or
kilobytes, as indicated by the Unit attribute. By default, this
attribute has no thresholds.
D.2.4. LongProcess Class
This class monitors processes that accumulate at least one minute of CPU time on each
UNIX host in the current configuration for which LongProcess monitoring is enabled. The
only exceptions are those processes identified to the URM agent as daemon processes.
Specifically, the URM agent sends an AC event report for each process on the UNIX host
that has accumulated at least 60 seconds of CPU time, if the process is not in the list of
daemon processes defined in the URM policy installed on the managed system. For
information on specifying daemon processes, see the Single Point Operations
Administration and Configuration Guide.
Single Point Operations Status automatically creates a LongProcess component in its
data model when it receives the event report, if it has not already created that
component. When the URM agent determines that a process previously added to this
class is no longer active, it sends a DE event report to delete the component from the
Single Point Status data model.
Attribute Description
Name This string attribute identifies the pid (process-id) of a running
process; it uniquely identifies the process.
Process Name This string attribute identifies the program being executed by the
running process, as reported by the command ps.
Host This string attribute identifies the name of the host on which the
process is running.
D–6 7833 4778–008

Attribute Description
UnixMon Classification [UNIX]
Status This status attribute reflects the process status. Possible values
are running and indeterminate. Normally, this attribute has a value
of running. If the URM agent stops reporting on a process without
deleting it, the attribute is set to its default value of indeterminate.
You can delete such a process from Status manually. The timeout
period for this attribute is 330 seconds, which is 30 seconds
longer than the default sample period of the URM agent.
Message This string attribute has the same value as Process Name. If the
program name is too long to appear in its entirety in tables or
attribute lists, you can click on this attribute to see the full
program name.
CPU Time This string attribute reports the total CPU time accumulated by the
process since its inception. The format of this attribute is
minutes:seconds.
Userid This string attribute reports the user-id associated with the
process.
Seconds Gained This numeric attribute reports the number of seconds the process
has gained during the sample interval. The default maximum
attention threshold value is 60 (seconds).
D.2.5. Process Class
This class monitors all processes that are identified to the URM agent as critical
processes on each UNIX host in the current configuration for which Process monitoring
is enabled. A critical process is a process that is expected to remain up (running) at all
times. By default, only cron is considered a critical process. For information on defining
additional critical processes, see the Single Point Operations Administration and
Configuration Guide.
The URM agent reports on each critical process whether it is running or not, since the
primary purpose is to ensure that each is up and running. Single Point Operations Status
automatically creates a component for each process as it receives an event report for it.
Attribute Description
Name This string attribute reports the name of the program executed by
a critical process. It may be anything from a full path name
(preceding the file name) to just the file name, depending on how
the user has specified it in the URM policy.
Host This string attribute identifies the name of the host on which the
critical process runs.
Status This status attribute reflects critical process status. Possible
values are up and down. As long as the URM agent detects that
the program remains running, it reports a status of up. If the
agent no longer finds (or has never found) the program running, it
reports a status of down, which raises an alarm.
Userid This string attribute identifies the user-id associated with the
7833 4778–008 D–7

UnixMon Classification [UNIX]
Attribute Description
process.
Process Id This string attribute identifies the process-id (pid) of the critical
process.
CPU Time This string attribute reports the total CPU time accumulated by the
process since its inception. The format of this attribute is
minutes:seconds.
D.2.6. User Class
This class monitors all users currently logged onto each UNIX host in the current
configuration for which user monitoring is enabled. Single Point Operations Status
automatically creates a component for each user as it receives an AC event report from
the URM agent for that user. The URM agent sends a DE event report for each of these
users as they log off, causing the User components to be automatically deleted from the
Single Point Operations Status data model as users log off the managed hosts.
Attribute Description
Name This string attribute identifies the UNIX log-on of the user.
Host This string attribute identifies the name of the host on which the
user is logged in.
Status This status attribute reflects the running status of the user.
Possible values are logged in, superuser, and indeterminate. A
status of logged in means that the user is logged onto the system
with normal privileges; this is the expected value. A status of
superuser means that the user has acquired superuser (root)
privileges and, by default, raises an alarm. If the URM agent stops
reporting on a user without deleting it, this attribute is set to its
default value of indeterminate. You can delete such a process
from Status manually. The timeout period for this attribute is 330
seconds, which is 30 seconds longer than the default sample
period of the URM agent.
Person This string attribute reports the actual name of the person
corresponding to the log-on, as specified in the file /etc/passwd on
the managed system.
D–8 7833 4778–008

Appendix E
Classifications for ClearPath IX and
ClearPath Plus Servers for OS 2200
[OS 2200 UNIX]
This appendix describes the use of Single Point Operations Status in conjunction with a
ClearPath IX or ClearPath Plus server for OS 2200. Status includes three predefined
classifications that are designed primarily for monitoring ClearPath servers with Single
Point Operations.
OS2200Mon This predefined classification allows you to monitor the OS 2200 nodes
of ClearPath IX or ClearPath Plus for OS2200 servers. You can also use
this classification for general monitoring of OS 2200 systems that are
not part of ClearPath IX or ClearPath Plus for OS2200 servers.
Unix2200Mon This predefined classification allows you to monitor the UNIX and
OS 2200 nodes of ClearPath IX or ClearPath Plus for OS2200 servers.
You can also use this classification for general monitoring of UNIX and
OS 2200 systems that are not part of ClearPath IX or ClearPath Plus for
OS2200 servers.
TapeMon This predefined classification enables you to monitor tape drive activity
on the OS 2200 nodes of ClearPath IX or ClearPath Plus for OS2200
servers. See Appendix B for detailed information about the OS 2200
Tape Monitor.
7833 4778–008 E–1

Classifications for ClearPath IX and ClearPath Plus Servers for OS 2200 [OS 2200
UNIX]
E.1. Using the OS2200Mon Classification
The classification OS2200Monx.y.z supplied with Single Point Operations consists of
predefined classes from the classification generalx.y.z , where x.y.z is the release level of
Single Point Operations.
[OS 2200]
OS2200Monx.y.z includes the following classes from the classification generalx.y.z to
support the OS 2200 component of ClearPath IX or ClearPath Plus for OS 2200 servers:
• 2200_Host
• Channel
• Console
• Control_Unit
• Device
• Disk
• IOP
• IP
• Run
• Storage_Area
• Tape
In addition, the following classes are included to support the OS 2200 nodes of ClearPath
IX and ClearPath Plus servers:
2200_Process This class reports the status of OS 2200 processes. Possible
Status values include up and down. There is no default
expected value for the Status attribute of this class.
Background_Run This class reports the status of OS 2200 background runs.
Possible Status values include running, completed,
error_completed, not_running, and error_condition.
The default expected Status value is running. The default
attention value is error_condition. The remaining values
generate an alarm.
For Status to obtain information about these classes, you must use the patterns in the
AMS database hmp_ix22 supplied with Single Point Operations.
E–2 7833 4778–008

Classifications for ClearPath IX and ClearPath Plus Servers for OS 2200 [OS 2200
UNIX]
E.2. Accessing the OS2200Mon Classification
To access the classification OS2200Mon, select the classification OS2200Monx.y.z when
you start Status. Status provides a default diagram. For further information about
diagram definitions, see Section 5.
This illustration shows the Status diagram for the classification OS2200Mon.
Figure E–1. OS2200Mon Status Diagram
7833 4778–008 E–3

Classifications for ClearPath IX and ClearPath Plus Servers for OS 2200 [OS 2200
UNIX]
E–4 7833 4778–008

Appendix F
Predefined Icons Supplied with Single
Point Operations Status
Single Point Operations Status includes a set of predefined .png icons for your use in two
sizes:
• Large icons are 50 pixels wide by 50 pixels high. The name of each large icon ends
with “_lg.”
• Small icons are 30 pixels wide by 25 pixels high. The name of each small icon ends
with “_sm.”
The following groups of predefined icons are provided with Single Point Operations
Status:
• UNIX Resource Monitor classes
• SMA and TeamQuest product icons
• Alphabetic icons
• System type icons
• Hardware icons
• Pictorial icons
Note: In Single Point Operations Level 7.4, the icons supplied with Status changed
from bitmap icons to pixmap icons with a more modern three-dimensional appearance.
Diagrams you have defined using previous levels of Single Point Operations can continue
to use the obsolete bitmap icons or you can modernize your Status displays with a single
operation if you choose. See 5.1.5 and 7.3.5 for more information.
See the Single Point Operations Administration and Configuration Guide for further
information on the icons used by Status and on defining you own icon families.
7833 4778–008 F–1

Predefined Icons Supplied with Single Point Operations Status
F.1. Viewing Icons
Both Single Point Operations Status and the Configuration application allow you to view
icons before you select them in component classes and component groups. In Status,
you can view an icon family from a Define Groups table, as described in 5.1. In the
Configuration application, you can view an icon family from the Define Status
Classification table, as described in 7.3.
F.1.1. Icons for Use with the UNIX Resource Monitor
Classifications
The following icons are designed for use with the component classes defined in the
classifications UnixMon (see Appendix D) and Unix2200Mon (see Appendix E):
CpuChip_lg
CpuChip_sm
CriticalProcess_lg
CriticalProcess_sm
File_lg
File_sm
FileCompare_lg
FileCompare_sm
FileCompare2_lg
FileCompare2_sm
FilePattern_lg
FilePattern_sm
FileSystem_lg
FileSystem_sm
NetworkCollisions_lg
NetworkCollisions_sm
NetworkIO_lg
NetworkIO_sm
NetworkRPC_lg
NetworkRPC_sm
PrinterQueue_lg
PrinterQueue_sm
Process_lg
Process_sm
RemoteSystem_lg
RemoteSystem_sm
Runner_lg
Runner_sm
Safe_lg
Safe_sm
Smile_lg
Smile_sm
System_lg
System_sm
SystemLoad_lg
SystemLoad_sm
UnixHost_lg
UnixHost_sm
User_lg
User_sm
User2_lg
User2_sm
User3_lg
User3_sm
F–2 7833 4778–008

User4_lg
User4_sm
UserDefinedAsync_lg
UserDefinedAsync_sm
UserDefinedMonitor_lg
UserDefinedMonitor_sm
UserDefinedScript_lg
UserDefinedScript_sm
Yuk_lg
Yuk_sm
Predefined Icons Supplied with Single Point Operations Status
F.1.2. Icons for Use with Products from SMA and TeamQuest
The following icons are designed for use with products from SMA and TeamQuest:
Alpha_SMA_lg
Alpha_SMA_sm
Alpha_TQ_lg
Alpha_TQ_sm
SMAerror_lg
SMAerror_sm
SMAheld_lg
SMAheld_sm
SMArunning_lg
SMArunning_sm
SMAsetup_lg
SMAsetup_sm
F.1.3. Additional Alphabetic Icons
Each of the following icons consists of the letters in the central part of its name. For
example, alpha_ApG_lg is a large bitmap of the letters “ApG.”
Alpha_ApG_lg
Alpha_ApG_sm
Alpha_CM_lg
Alpha_CM_sm
Alpha_CPU_lg
Alpha_CPU_sm
Alpha_Dev_lg
Alpha_Dev_sm
Alpha_FS_lg
Alpha_FS_sm
Alpha_IOP_lg
Alpha_IOP_sm
Alpha_IP_lg
Alpha_IP_sm
Alpha_Mem_lg
Alpha_Mem_sm
Alpha_Prnt_lg
Alpha_Prnt_sm
Alpha_Proc_lg
Alpha_Proc_sm
7833 4778–008 F–3

Predefined Icons Supplied with Single Point Operations Status
F.1.4. Additional System Type Icons
The following additional system type icons are included with Single Point Operations
Status:
2200Host_lg
2200Host_sm
MCPHost_lg
MCPHost_sm
ArbSystem_lg
ArbSystem_sm
NTHost_lg
NTHost_sm
F.1.5. Additional Hardware Icons
The following additional hardware icons are included with Single Point Operations Status:
Channel_lg
Channel_sm
Console_lg
Console_sm
ControlUnit_lg
ControlUnit_sm
Device_lg
Device_sm
Disk_lg
Disk_sm
IOP_lg
IOP_sm
IP_lg
IP_sm
Memory_lg
Memory_sm
Printer_lg
Printer_sm
SPO_lg
SPO_sm
Tape_lg
Tape_sm
F–4 7833 4778–008

Predefined Icons Supplied with Single Point Operations Status
F.1.6. Additional Pictorial Icons
The following additional pictorial icons are included with Single Point Operations Status:
Backup_lg
Backup_sm
Ekg_lg
Ekg_sm
Error_lg
Error_sm
EyesUNIX_lg
EyesUNIX_sm
Eyes_lg
Eyes_sm
Generic_lg
Generic_sm
Held_lg
Held_sm
Horse_lg
Horse_sm
Log_lg
Log_sm
Messages_lg
Messages_sm
Paging_lg
Paging_sm
Run_lg
Run_sm
Running_lg
Running_sm
Setup_lg
Setup_sm
Status_lg
Status_sm
Telephone_lg
Telephone_sm
7833 4778–008 F–5

Predefined Icons Supplied with Single Point Operations Status
F–6 7833 4778–008

Appendix G
Related Product Information
The Operations Sentinel product documentation library is provided as a set of online
documents in Portable Documentation Format (PDF) on the Operations Sentinel
Software and Product Information CD-ROM. The CD-ROM contains the Operations
Sentinel software, product documentation library, and the Adobe Reader. Print-ready
versions (PDF files) of the product documentation are available on the Unisys Support
Web site at (http://www.support.unisys.com/).
Online Help is embedded in the Operations Sentinel software. Installation Help is
available from the Operations Sentinel browser.
The following documents may be helpful when you use Operations Sentinel. Use the
version that corresponds to the level of software in use at your site.
2200 Series Single Point Operations Interface Software Installation and
Configuration Guide (7831 3400)
This guide explains how to install and configure the Single Point Operations Interface
software on each of the OS 2200 system consoles you want to manage.
MCP/AS System Administration Guide (8600 0437)
This guide provides the information required to make decisions about system
configuration, peripheral configuration, file management, resource use, and other matters
related to MCP system administration. It is written for users with some, little, or no MCP
experience who are responsible for making decisions about system administration.
MCP/AS System Configuration Guide (8600 0445)
This guide describes how to organize a complex MCP computer system into different
hardware configurations. It also describes the steps required to dynamically change a
system from one configuration to another. This guide is written for experienced system
administrators and system operators.
ClearPath Enterprise Servers System Messages Support Reference Manual
(8600 0429)
This guide lists and describes MCP messages.
7833 4778–008 G–1

Related Product Information
Single Point Operations Interface for ClearPath MCP Installation and
Configuration Guide (7844 8131)
This guide explains how to configure Single Point Operations Interface software on each
of the MCP host systems that you want to manage. The tasks include installing,
configuring, and starting the software.
ClearPath Enterprise Servers Operations Sentinel Autoaction Message
System Administration Guide (7862 6900)
This guide provides information about how to develop and use Single Point Operations
Autoaction Message System (SP-AMS) to automate your MCP and UNIX system and
ClearPath Plus OS 2200 Autoaction Message System (CP-AMS) to automate your
ClearPath Plus servers.
ClearPath Enterprise Servers Operations Sentinel Administration and
Configuration Guide (7862 2321)
This guide explains how to configure Single Point Operations.
ClearPath Enterprise Servers Operations Sentinel Console User Guide
(7862 5977)
This guide explains the operator functions for Single Point Operations Console.
ClearPath Enterprise Servers Operations Sentinel Event Server
Application Program Interface Programming Guide (7844 8107)
This guide explains how to program and administer clients for the Event Server
application program interface (API) of Single Point Operations.
ClearPath Enterprise Servers Operations Sentinel Master Glossary
(7847 4244)
This glossary consolidates terminology and definitions, including abbreviations and
acronyms.
SMART for ClearPath OS 2200 Administration and Operations Guide
(7830 7337)
This guide explains how to set up an OS 2200 host system to operate with SMART,
enabling you to automate system operations.
G–2 7833 4778–008

Index
A
adding
component class, 7-15
component definitions, 6-5
Component Group table templates, 5-19
component groups, 5-9
default component group, 5-10, 5-11
host-independent component group, 5-12
Alarm attribute, 4-12
alarm Default Alarm Maximum value, 7-20
Alarm Id
numeric attribute, 7-21
status attribute, 7-19
alarm text substitution strings, 7-13
alarm values, 6-4, 7-18
alarms, controlling duplicate behavior, 7-23
alphabetic icons, predefined, F-3
ANSI X3.64 host attributes, 4-22
application initialization mnemonic value
(table), 7-10
arbitrary systems, 1-6
Associated Attr string attribute, 7-22
attention Default Alarm Maximum value, 7-20
attribute lists
description (figure), 3-19
displaying, 3-20
menus, 3-21
updating, 3-19
attribute name
numeric attribute, 7-20
status attribute, 7-17
ATTRIBUTE substitution string, 7-13
attribute value pairs, 2-2
attributes
Alarm, 4-12
alarm values, 6-4
applicable to all component classes, 4-6
Class, 1-3, 4-6
Classes (table), 5-7
component, 4-1
Component names (table), 5-7
Component Scope, 4-9
Connected Consoles, 4-15
Connected Host, 4-18
Connected to application, 4-19
Connected to application, 4-17, 4-22
Connected to Host, 4-17
Connections, D-4
CPU Time, D-7, D-8
Data Collection, 4-14, 4-19
data types, 4-2
description, 1-8
Event Received, 4-9
Event Report Time, 4-8
Exceptions, 4-6
Exec Level, 4-14
Expected, 4-11
expected values, 6-4
for ANSI X3.64 hosts, 4-22
for MCP hosts, 4-19
for OS 2200 consoles, 4-17
for OS 2200 hosts, 4-14
for UNIX hosts, 4-22
for UnixMon classification, D-4
Groups, 4-9
Heartbeat Period, D-4
Heartbeat Status, D-4
Host, D-5, D-6, D-7, D-8
Host, 4-6
Host Agent Active, 4-20
Hosts (table), 5-7
Identical Components, 4-10
Idle %, D-5
initiating actions, 3-21
Inodes Free, D-5
Inodes Used, D-6
list, 4-5
Message, D-7
Message, 4-8
Model, D-5
Monitor, 4-17, 4-19, 4-22
Name, D-4, D-5, D-6, D-7, D-8
Name, 4-6
Notes, 4-7
numeric, 4-12
numeric, 4-4
OS Version, D-5
7833 4778–008 Index–1

Index
Percent Inodes Used, D-6
Percent Space Used, D-6
Person, D-8
Process Id, D-8
Process Name, D-6
reported (table), 4-2
Sample Period, D-4
Seconds Gained, D-7
Seen, 4-7
Site Id, 4-14
site-defined, 4-11, 7-17, 7-21
Space Free, D-6
Space Used, D-5
specified (table), 4-2
status, 7-17
status, 4-3, 4-11
Status, D-4, D-7, D-8
string, 4-13, 7-21
string, 4-4
System %, D-5
System Type, 4-15
threshold values, 6-5
Total, D-6
types (table), 4-2
Unit, D-6
User %, D-5
User Defined, 4-9
User Defined, 6-3
Userid, D-7, D-8
Users, D-4
Wait %, D-5
Autoaction Message System (AMS) database
MCP Tape Monitor, 2-6
OS 2200 Tape Monitor, 2-6
OS 2200 Tape Monitor, 2-5
automatic creation scheme value (table), 7-9
automatic environment setup, 2-21
B
bitmap icons
updating, 5-5, 7-9
C
Cancel button (table), 3-23
chan initialization mnemonic value
(table), 7-10
changing
attribute columns in component table
template, 5-18
background for group window, 5-12
class associated with table template, 5-18
classification, 2-22
classification, 2-12
component definitions, 6-3
Component Group table template, 5-6
component groups in current diagram, 5-2
configurations, 2-23
current diagram definition, 5-23
display behavior of component table
template, 5-18
environment, 2-22
label of component group, 5-3
name of component group, 5-3
resource sets, 2-23
screen size of component table
template, 5-17
title of group window, 5-13
trace level, 2-24
Class attribute, 1-3, 4-6
CLASS attribute value pairs, 2-2
class label, 7-8
CLASS substitution string, 7-13
classifications
changing, 2-22
changing, 2-12
creating, 7-3
defining, 2-11
description, 2-12
editing, 7-3
for ClearPath servers, E-1
general, 1-8
general, 2-12
independent of resource sets and
configurations, 2-15
MCP, C-2
MCPTapeMon, 2-13
OS 2200 TapeMon, B-2
relation to configuration, 7-2
relationship to diagram definitions
(figure), 2-17
removing, 7-6
saving, 7-5
selecting, 7-5
TapeMon, 2-13
Unix2200Mon, 2-13, E-3
UnixMon, D-2
UnixMon, 2-13
Clear button (table), 3-23
ClearPath server classifications, E-1
Index–2 7833 4778–008

color coding, 3-4
component classes
adding, 7-15
class label, 7-8
copying, 7-15
creation scheme, 7-9
default scope, 7-9
deleting, 7-16
description, 1-8
editing
single, 7-23
initialization mnemonic, 7-10, 7-11
instruction file, 7-12
internal class, changing, 7-7
merging, 7-16
renaming, 7-7
retaining notefile s, 7-13
system types, 7-8
component definitions
adding, 6-5
changing, 6-3
Component Group table
adding templates, 5-19
changing template, 5-6
deleting templates, 5-20
description (figure), 3-11
display behaviors, 3-12
selecting default templates, 5-20
templates, 3-13
component groups
adding, 5-9
adding default, 5-11
copying, 5-9
default
adding, 5-10
deleting, 5-11
moving, 5-11
defining, 5-2
deleting, 5-9
description, 1-11
host-independent, adding, 5-12
label, changing, 5-3
name, changing, 5-3
specifying components for, 5-7
Component Scope attribute values (table), 4-9
component sets
definitions
deleting, 6-9
replacing, 6-7
description, 2-18
introduction, 6-1
retrieving, 6-10
Component Sets menu (figure), 3-8
Index
component tables
changing
attribute columns in template, 5-18
display behavior of template, 5-18
screen size of template, 5-17
defining templates, 5-15
types, 3-11
components
attributes, 1-8
attributes, 4-1
class, 1-10
class label, 7-8
creating, 1-11
creation scheme, 7-9
default scope, 7-9
defining
new, 6-5
defining
explicitly, 6-2
deleting, 3-13, 6-5
deleting, 3-22
description, 1-8
host, 1-10
identifying, 1-10
initialization mnemonic, 7-10, 7-11
instruction file, 7-12
instruction file, 6-4
name, 1-10
new, defining, 6-5
obtaining information on (figure), 2-8
reselecting for different host or class, 6-6
retaining note files, 7-13
scope, 6-3
shared, 1-10
specifying for group, 5-7
system types, 7-8
Components with Notes table, 3-15
Components with Unexpected Values table
(figure), 3-14
Configuration application, 7-2
configurations
changing, 2-23
description, 2-15
independent of classifications and
resource sets, 2-15
relationship to diagram definitions
(figure), 2-17
configuring
site-defined attributes, 7-17, 7-21
Status, 2-10
status attributes, 7-17
string attributes, 7-21
Connected Consoles attribute, 4-15
7833 4778–008 Index–3

Index
Connected Host attribute, 4-18
Connected to application attribute, 4-17, 4-19,
4-22
Connected to Host attribute, 4-17
Connections attribute, UNIX Host class
(table), D-4
controlling duplicate alarm behavior, 7-23
copying
component class, 7-15
component groups, 5-9
CPU class, D-5
CPU Time attribute, LongProcess class
(table), D-7
CPU Time attribute, Process class (table), D-8
creating
components, 1-11
new classification, 7-3
Creation Scheme host class characteristic
MCP, C-4
OS 2200, B-5
Creation Scheme tape class characteristic
MCP, C-3
OS 2200, B-3
creation scheme values (table), 7-9
cu initialization mnemonic value (table), 7-10
D
Data Collection attribute, 4-14, 4-19
data collector, 1-11
MCP, 2-6
OS 2200, 2-6
OS 2200, 2-5
data flow to Status (figure), 1-6
data types of attributes, 4-2
Default Alarm Maximum status attribute, 7-20
Default Alarm Minimum numeric
attribute, 7-20
Default Attention Maximum numeric
attribute, 7-20
Default Attention Minimum status
attribute, 7-20
default scope, 7-9
Default Scope host class characteristic
MCP, C-4
OS 2200, B-5
Default Scope tape class characteristic
MCP, C-3
OS 2200, B-3
Default status attribute, 7-19
Define Component Groups table (figure), 5-2
Define Component Tables table (figure), 5-15
Define Status Classification window, 7-3
defining
classifications, 7-3
component groups, 5-2
component table templates, 5-15
components for different host or class, 6-6
subgroups, 5-8
defining classification (figure), 2-11
deleting
component classes, 7-16
Component Group table templates, 5-20
component groups, 5-9
component set definitions, 6-9
components, 3-13, 6-5
components, 3-22
default component group, 5-11
diagram definitions, 5-22
dev initialization mnemonic value (table), 7-10
diagram definitions
automatic deletion, 5-22
changing current, 5-23
deleting, 5-22
description, 2-15, 5-1
relationship to classifications and
configurations, 2-17
replacing current, 5-21
saving, 5-21
Diagrams menu (figure), 3-7
dialog windows
buttons (table), 3-23
description (figure), 3-23
entering information, 3-23
disk initialization mnemonic value (table), 7-10
display behavior
component table template, changing, 5-18
introduction, 3-12
displaying
attribute list, 3-20
icons, 2-13
displays
behavior, 3-12
features (figure), 3-2
introduction, 3-1
primary, 3-2
secondary, 3-2
duplicate alarm behavior, controlling, 7-23
dynamic display behavior, 3-12, 3-13
Index–4 7833 4778–008

E
Edit Components table (figure), 6-2
editing
existing classification, 7-3
single component class, 7-23
entering information in dialog windows, 3-23
environment
automatic setup, 2-21
changing, 2-22
Event Received attribute, 4-9
Event Report Time attribute, 4-8
event reports
considerations, 2-2
description, 1-9
example, 2-3
logging, A-2
exception conditions, A-3
exceptions and operator action, 3-6
Exceptions attribute, 4-6
Exec Level attribute, 4-14
Expected attribute, 4-11
expected values, status attribute, 6-4, 7-18
Explain button (table), 3-24
explicit_only creation scheme value
(table), 7-10
F
File menu (figure), 3-7
files
instruction, 1-11
note, 1-11
FileSystem class, D-5
first string attribute name, string
attribute, 7-21
G
general classification, 1-8, 2-12
Generate Alarms host class characteristic
MCP, C-4
OS 2200, B-5
Generate Alarms tape class characteristic
MCP, C-3
OS 2200, B-3
gray, 3-4
green, 3-4
Groups attribute, 4-9
Index
7833 4778–008 Index–5
H
hardware icons, predefined, F-4
Heartbeat Period attribute, UNIX Host class
(table), D-4
Heartbeat Status attribute, UNIX Host class
(table), D-4
Help menu, 3-8, 3-21
Host Agent Active attribute, 4-20
Host attribute, 4-6
FileSystem class (table), D-5
LongProcess class (table), D-6
Process class (table), D-7
User class (table), D-8
Host scope value (table), 4-9, 7-9
HOSTID substitution string, 7-13
I
icon bitmap files, 2-14
Icon host class characteristic
MCP, C-4
OS 2200, B-5
Icon tape class characteristic
MCP, C-3
OS 2200, B-3
icons
color coding, 3-4
displaying, 2-13
family, selecting, 7-8
positioning, 5-5
predefined, F-1
selecting, 5-4
update obsolete bitmap icons, 5-5, 7-9
Identical Components attribute, 4-10
Identical Components table (figure), 3-17
Idle % attribute, CPU class (table), D-5
Init Mnemonic host class characteristic
MCP, C-4
OS 2200, B-5
Init Mnemonic tape class characteristic
MCP, C-3
OS 2200, B-3
initialization mnemonic, 7-11
initialization mnemonic values (table), 7-10
initialization of applications, 4-16, 4-20
initiating actions, 3-21
Inodes Free attribute, FileSystem class
(table), D-5
Inodes Used attribute, FileSystem class
(table), D-6

Index
INSTANCE attribute value pairs, 2-2
instruction file, 1-11, 6-4, 7-12
Instruction File host class characteristic
MCP, C-4
OS 2200, B-5
Instruction File tape class characteristic
MCP, C-3
OS 2200, B-3
internal class, 7-7
Internal Class host class characteristic
MCP, C-4
OS 2200, B-5
Internal Class tape class characteristic
MCP, C-3
OS 2200, B-3
iop initialization mnemonic value (table), 7-10
ip initialization mnemonic value (table), 7-10
L
labels, changing, 5-3
list attributes, 4-5
log
event reports, A-2
exception conditions, A-3
message information, A-3
message type codes, A-3
recording trace information, 2-24
SP-STATUS, A-3
Log View window, 2-24
logging event reports, A-2
LongProcess class, D-6
M
maximum threshold values, 6-5
MCP
data collector, 2-6
operating considerations, 2-6
requirements
Single Point Autoaction Message
System (SP-AMS) database, 2-6
Single Point Operations for ClearPath
MCP software, 2-6
MCP
Creation Scheme host class
characteristic, C-4
Creation Scheme tape class
characteristic, C-3
Default Scope host class
characteristic, C-4
Default Scope tape class
characteristic, C-3
Generate Alarms host class
characteristic, C-4
Generate Alarms tape class
characteristic, C-3
Icon host class characteristic, C-4
Icon tape class characteristic, C-3
Init Mnemonic host class
characteristic, C-4
Init Mnemonic tape class
characteristic, C-3
Instruction File host class
characteristic, C-4
Instruction File tape class
characteristic, C-3
Internal Class host class characteristic, C-4
Internal Class tape class characteristic, C-3
Status Attribute host class
characteristic, C-4
Status Attribute tape class
characteristic, C-3
System Types host class
characteristic, C-4
System Types tape class
characteristic, C-3
Tape Class string attributes tape class
characteristic, C-3
Tape Monitor, C-1
MCP systems and Status (figure), 2-7
MCPTapeMon classification, 2-13
menu structure of Status (figure), 1-7
menus
attribute list, 3-21
Delete, 3-22
pull-down, 3-7
merging component classes, 7-16
Message attribute, 4-8
Message attribute, LongProcess class
(table), D-7
MESSAGE substitution string, 7-13
message type codes, A-3
minimum threshold values, 6-5
Model attribute, UNIX Host class (table), D-5
Monitor attribute, 4-17, 4-19, 4-22
moving default component group, 5-11
Index–6 7833 4778–008

N
Name attribute, 4-6
CPU class (table), D-5
FileSystem class (table), D-5
LongProcess class (table), D-6
Process class (table), D-7
UNIX Host class (table), D-4
User class (table), D-8
NAME substitution string, 7-13
none creation scheme value (table), 7-10
normal Default Alarm Maximum value, 7-20
note files, 1-11
Notes attribute, 4-7
numeric attributes, 4-4, 4-12
Alarm Id, 7-21
Default Alarm Minimum, 7-20
Default Attention Maximum, 7-20
name, 7-20
Severity, 7-21
O
OK button (table), 3-23
OMKEY background run, 2-5, 2-6
operating considerations, 2-2
MCP, 2-6
OS 2200, 2-6
OS 2200, 2-5
operator actions (table), 3-6
OS 2200
console attributes, 4-17
Creation Scheme host class
characteristic, B-5
Creation Scheme tape class
characteristic, B-3
data collector, 2-5, 2-6
Default Scope host class
characteristic, B-5
Default Scope tape class
characteristic, B-3
Generate Alarms host class
characteristic, B-5
Generate Alarms tape class
characteristic, B-3
host attributes, 4-14
Icon host class characteristic, B-5
Icon tape class characteristic, B-3
Init Mnemonic host class
characteristic, B-5
Index
Init Mnemonic tape class
characteristic, B-3
Instruction File host class
characteristic, B-5
Instruction File tape class
characteristic, B-3
Internal Class host class characteristic, B-5
Internal Class tape class characteristic, B-3
operating considerations, 2-5, 2-6
Status Attribute host class
characteristic, B-5
Status Attribute tape class
characteristic, B-3
System Types host class
characteristic, B-5
System Types tape class
characteristic, B-3
Tape Class string attributes tape class
characteristic, B-3
Tape Monitor AMS database, 2-5, 2-6
OS 2200 systems and Status (figure), 2-6
OS Version attribute, UNIX Host class
(table), D-5
7833 4778–008 Index–7
P
Percent Inodes Used attribute, FileSystem
class (table), D-6
Percent Space Used attribute, FileSystem
class (table), D-6
Person attribute, User class (table), D-8
pictorial icons, predefined, F-5
positioning icons, 5-5
possible values
status attribute, 7-17
predefined icons, F-1, F-3, F-4, F-5
primary windows, 3-2
printer initialization mnemonic value
(table), 7-10
Process class, D-7
Process Id attribute, Process class (table), D-8
Process Name attribute, LongProcess class
(table), D-6
pull-down menus, 3-7
R
red, 3-4
renaming component class, 7-7

Index
replacing
component set definition, 6-7
current diagram definition, 5-21, 5-23
reported attributes (table), 4-2
resource sets
changing current, 2-23
description, 2-15
independent of classifications and
configurations, 2-15
retaining note files, 7-13
retrieving component set, 6-10
S
sa initialization mnemonic value (table), 7-10
Sample Period attribute, UNIX Host class
(table), D-4
saving
diagram definitions, 5-21
scope of component, 6-3
secondary windows, 3-2
Seconds Gained attribute, LongProcess class
(table), D-7
Seen attribute, 4-7
setting up Status, 2-12
Severity numeric attribute, 7-21
Severity status attribute, 7-19
shared component, 1-10
Shared scope value (table), 4-9, 7-9
Single Point Autoaction Message System
(SP-AMS), 2-6
Single Point Operations Configuration
application, 7-2
Single Point Operations workstation, starting
Status from, 2-20
Site Id attribute, 4-14
site-defined attributes
configuring, 7-17, 7-21
numeric, 4-12
status, 4-11, 7-17
status, 4-3
string, 4-13, 7-21
table, 4-11
SMA products, predefined icons for, F-3
Space Free attribute, FileSystem class
(table), D-6
Space Used attribute, FileSystem class
(table), D-5
specified attributes (table), 4-2
SP-STATUS log, A-3
starting Status, 2-19
static display behavior, 3-12
Status Attribute host class characteristic
MCP, C-4
OS 2200, B-5
Status Attribute tape class characteristic
MCP, C-3
OS 2200, B-3
status attributes
Alarm Id, 7-19
alarm values, 7-18
configuring, 7-17
Default, 7-19
Default Alarm Maximum, 7-20
Default Attention Minimum, 7-20
description, 4-3
expected values, 7-18
in component tables and attribute
lists, 4-11
LongProcess class (table), D-7
name, 7-17
possible values, 7-17
Process class (table), D-7
Severity, 7-19
Timeout, 7-19
UNIX Host class (table), D-4
User class (table), D-8
Status diagram
as primary window, 3-2
color coding, 3-4
definition, 2-15
icons, 2-13
introduction, 3-3
operator action, 3-6
pull-down menus, 3-7
subgroup windows, 3-10
updating, 3-5
Status diagram (figure), 3-3
Status display (figure), 1-4
string attributes, 4-4, 4-13
Associated Attr, 7-22
configuring, 7-21
first string attribute name, 7-21
subgroups
defining, 5-8
menus, 3-10
windows, 3-10
substitution strings for alarm text, 7-13
sys initialization mnemonic value (table), 7-10
System % attribute, CPU class (table), D-5
system icons, predefined, F-4
System Type attribute, 4-15
system types, 7-8
Index–8 7833 4778–008

System Types host class characteristic
MCP, C-4
OS 2200, B-5
System Types tape class characteristic
MCP, C-3
OS 2200, B-3
T
tables
component, types (table), 3-11
Components with Notes (figure), 3-15
Components with Unexpected Values
(figure), 3-14
Define Component Groups (figure), 5-2
Define Groups, 5-2
Identical Components (figure), 3-17
Unreported Components, 3-16, A-5
Tables menu (figure), 3-7
Tape Class string attributes tape class
characteristic
MCP, C-3
OS 2200, B-3
tape initialization mnemonic value
(table), 7-10
Tape Monitor
AMS database, 2-6
AMS database, 2-5
table, 2-4
Tape Monitor table (figure), 2-4
TapeMon classification, 2-13
TeamQuest products, predefined icons
for, F-3
templates
Component Group table
deleting, 5-20
description, 3-13
selecting different, 5-20
Component Group table
adding, 5-19
component table, changing
attribute columns in, 5-18
component table, changing
behavior of, 5-18
class associated with, 5-18
screen size, 5-17
component table, defining, 5-15
defining component table, 5-15
terminating Status, 2-21
threshold values, 6-5
TIME substitution string, 7-13
Index
Timeout status attribute, 7-19
Total attribute, FileSystem class (table), D-6
trace levels, 2-24, A-2
troubleshooting, A-1
TYPE attribute value pairs, 2-2
7833 4778–008 Index–9
U
Unisys Support Center, A-6
Unit attribute, FileSystem class (table), D-6
UNIX host attributes, 4-19, 4-22
UNIX Host class, D-4
UNIX Resource Monitor, icons predefined for
use with, F-2
UNIX systems
considerations, 2-7
UNIX Resource Monitor, D-2
Unix2200Mon classification, 2-13, E-3
Unix2200Mon Status diagram (figure), E-3
UnixMon classification, 2-13
attributes, D-4
CPU class, D-5
FileSystem class, D-5
LongProcess class, D-6
Process class, D-7
UNIX Host class, D-4
User class, D-8
UnixMon Status diagram (figure), D-2
Unknown button (table), 3-23
Unreported Components table
contents, A-5
figure, 3-16
User % attribute, CPU class (table), D-5
User class, D-8
user classes, 2-15
User Defined attribute, 4-9, 6-3
Userid attribute
LongProcess class (table), D-7
Process class (table), D-8
users
definitions, 2-15
Users attribute, UNIX Host class (table), D-4
V
VALUE substitution string, 7-13

Index
W
Wait % attribute, CPU class (table), D-5
windows
dialog (figure), 3-23
features (figure), 3-2
group, changing
background, 5-12
title, 5-13
Windows NT considerations, 2-8
Index–10 7833 4778–008
X
XXX substitution string, 7-14
Y
yellow, 3-4

*78334778-008*
78334778–008