Operations Sentinel Status User Guide - Public Support Login - Unisys

More documents

Recommendations

Info

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
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: Section 2 Getting Started This sect
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 and 90:
Site-Defined Attributes • The val
Page 91 and 92:
Attributes Specific to the OS 2200
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 115 and 116:
Page 117 and 118:
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

Create successful ePaper yourself

Delete template?

Save as template?