Operations Sentinel Status User Guide - Public Support Login - Unisys

More documents

Recommendations

Info

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
Page 1:
ClearPath Enterprise Servers Operat
Page 4 and 5:
NO WARRANTIES OF ANY NATURE ARE EXT
Page 7 and 8:
Contents Section 1. Introduction to
Page 9 and 10:
Contents 4.2.1. Name...............
Page 11 and 12:
Contents 6.1.10. Defining Component
Page 13 and 14:
Appendix F. Predefined Icons Suppli
Page 15 and 16:
Figures 1-1. Example of a Status Di
Page 17 and 18:
Section 1 Introduction to Single Po
Page 19 and 20:
Class Description of Status The nex
Page 21 and 22:
Figure 1-2. Data Flow to Single Poi
Page 23 and 24:
Description of Status [UNIX] The UN
Page 25 and 26:
• Storage area (memory module)
Page 27 and 28:
1.2.6. Creating Components Introduc
Page 29 and 30:
Section 2 Getting Started This sect
Page 31 and 32:
Operating Considerations • TYPE T
Page 33 and 34:
2.1.4. OS 2200 Considerations [OS 2
Page 35 and 36:
Operating Considerations The MCP ag
Page 37 and 38:
2.2. Preparing to Use Status Prepar
Page 39 and 40: The following illustration shows th
Page 41 and 42: Setting Up Status • MCPTapeMonx.y
Page 43 and 44: 2.3.3. Resource Sets Setting Up Sta
Page 45 and 46: Setting Up Status combination of cl
Page 47 and 48: 2.4. Starting and Terminating Statu
Page 49 and 50: Starting and Terminating Status 2.4
Page 51 and 52: Changing the Status Environment Ope
Page 53 and 54: Section 3 Status Displays This sect
Page 55 and 56: 3.2. Status Diagram Status Diagram
Page 57 and 58: 3.2.2. How the Status Diagram Is Up
Page 59 and 60: 3.2.4. Pull-Down Menus Status Diagr
Page 61 and 62: 3.2.5. Window Backgrounds Status Di
Page 63 and 64: 3.4. Component Tables Component Tab
Page 65 and 66: Component Tables component is added
Page 67 and 68: Status adds a row at the bottom of
Page 69 and 70: Figure 3-6. Unreported Components T
Page 71 and 72: 3.5. Attribute List Attribute List
Page 73 and 74: Attribute List short time, and then
Page 75 and 76: 3.6. Dialog Windows Dialog Windows
Page 77 and 78: Section 4 Component Attributes This
Page 79 and 80: 4.1.3. Status Attributes Types of A
Page 81 and 82: Types of Attributes When the value
Page 83 and 84: 4.2.5. Seen 4.2.6. Notes Attributes
Page 85 and 86: 4.2.9. Event Received Attributes Th
Page 87 and 88: 4.3. Site-Defined Attributes 4.3.1.
Page 89: Site-Defined Attributes • The val
Page 93 and 94: Attributes Specific to the OS 2200
Page 95 and 96: Attributes Specific to the MCP Host
Page 97 and 98: Attributes Specific to the MCP Host
Page 99 and 100: Section 5 Diagram Definitions A dia
Page 101 and 102: 5.1.2. Capabilities Defining Compon
Page 103 and 104: Defining Component Groups A window
Page 105 and 106: Defining Component Groups 5.1.8. Sp
Page 107 and 108: 5.1.10. Adding New Component Groups
Page 109 and 110: 5.1.14. Deleting Default Groups for
Page 111 and 112: Defining Component Groups Backgroun
Page 113 and 114: Defining Component Table Templates
Page 119 and 120: 5.3. Saving a Diagram Definition Sa
Page 121 and 122: Changing the Diagram Definition in
Page 123 and 124: After you select a diagram definiti
Page 125 and 126: Section 6 Component Sets This secti
Page 127 and 128: Defining Components Explicitly 6.1.
Page 129 and 130: Defining Components Explicitly 6.1.
Page 131 and 132: 6.2. Saving Component Set Definitio
Page 133 and 134: Deleting Component Set Definitions
Page 135 and 136: Section 7 Defining Classifications
Page 137 and 138: 7.2. Defining Status Classification
Page 139 and 140: Defining Status Classifications Ret
Page 141 and 142:
Changing Component Class Characteri
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Adding and Deleting Component Class
Page 151 and 152:
7.5. Configuring Site-Defined Attri
Page 153 and 154:
Configuring Site-Defined Attributes
Page 155 and 156:
Configuring Site-Defined Attributes
Page 157 and 158:
7.6. Additional Specifications 7.6.
Page 159 and 160:
Appendix A Troubleshooting This app
Page 161 and 162:
Event Report Logging produced by Si
Page 163 and 164:
A.2. Unreported Components Table Un
Page 165 and 166:
Appendix B Tape Monitor for OS 2200
Page 167 and 168:
B.2. TapeMon Classification [OS 220
Page 169 and 170:
TapeMon Classification [OS 2200] co
Page 171 and 172:
TapeMon Classification [OS 2200] St
Page 173 and 174:
Appendix C Tape Monitor for MCP Hos
Page 175 and 176:
C.2. MCPTapeMon Classification MCPT
Page 177 and 178:
MCPTapeMon Classification • Icon
Page 179 and 180:
Appendix D UNIX Resource Monitor [U
Page 181 and 182:
D.1.4. UnixMon Classification Using
Page 183 and 184:
D.2.2. CPU Class Attribute Descript
Page 185 and 186:
Attribute Description UnixMon Class
Page 187 and 188:
Appendix E Classifications for Clea
Page 189 and 190:
Classifications for ClearPath IX an
Page 191 and 192:
Appendix F Predefined Icons Supplie
Page 193 and 194:
User4_lg User4_sm UserDefinedAsync_
Page 195 and 196:
Predefined Icons Supplied with Sing
Page 197 and 198:
Appendix G Related Product Informat
Page 199 and 200:
Index A adding component class, 7-1
Page 201 and 202:
color coding, 3-4 component classes
Page 203 and 204:
E Edit Components table (figure), 6
Page 205 and 206:
N Name attribute, 4-6 CPU class (ta
Page 207 and 208:
System Types host class characteris
Page 210:
*78334778-008* 78334778-008
show all

Operations Sentinel Status User Guide - Public Support Login - Unisys

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?