Operations Sentinel Status User Guide - Public Support Login - Unisys

More documents

Recommendations

Info

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
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 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 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: Changing Component Class Characteri
Page 147 and 148: Changing Component Class Characteri
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?