IBM E027SLL-H Troubleshooting Guide - Page 217

A message appears after accepting the license

Get IBM E027SLL-H - Tivoli Monitoring - PC PDF manuals and user guides View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals

Page 217 highlights

SHIFTPERIOD: Indicator of shifts to include. -1 = AllShifts, 1 = OffPeak, 2 = Peak VACATIONPERIOD: Indicator of vacation days to include. -1 = AllDays, 0 = WorkDays, 1 = VacationDays TIMESPAN: Set of values captured by the Timespan window. It is not practical to construct this directly. SUMMARY_DAY: Day to select. A string in the format YYYY/MM/DD. The following is an example link wizard expression that can build such a string value from the a TEP 16 character timestamp attribute value (assuming years in the 20yy range): dt = $knt.Processor:ATTRIBUTE.NTPROCSSR_H.WRITETIME$; yyyy = "20" + STR(dt, 2, 2); mm = STR(dt, 4, 2); dd = STR(dt, 6, 2); yyyy + "/" + mm + "/" + dd SUMMARY_WEEK: First day of week to select. A string in the format YYYY/MM/DD Because of the open-ended nature of the custom queries and their provision by multiple agent groups, it is possible that other symbols might also be used. One way to understand what values are required is to save a copy of the query and edit it to remove clauses involving the symbols. When the modified query is assigned to a view (assuming any syntax errors are overcome), it should return an unfiltered view of the table. The values in the table, in conjunction with close examination of the query text, can be used as a guide to what to provide as filter values. Another symbol that has been specifically asked about is $Server_Name$. This is the name of the server of interest. If the workspace is below the agent level in the navigator tree, $NODE$ will usually return an appropriate value. If the value is being provided through a link, it can often be picked from the Server Name attribute of the link source row. When in doubt, examining a display of the unfiltered table can help determine what is expected. In summary, it should be emphasized that the product-provided workspaces based on these queries should be used whenever possible. A message appears after accepting the license UNIX only During installation of the Monitoring Agent, immediately after accepting the license agreement, a message similar to the following lslpp: message might be displayed: Press Enter to continue viewing the licenseagreement, or enter "1" to accept the agreement, "2" to decline it, "3" to print it,"4" to read non-IBM terms, or "99" togo back to the previous screen. 1 lslpp: Fileset gsksa.rte not installed. This message is harmless and is associated with verifying the versions of the gskit component installed by IBM Tivoli Monitoring. The message is displayed at a point where the UNIX installation normally pauses for a number of seconds, causing a tendency to think the installation has failed, although this is not the case. Chapter 10. Monitoring agent troubleshooting 199

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
SHIFTPERIOD: Indicator of shifts to include. -1 = AllShifts, 1 = OffPeak, 2 = Peak
VACATIONPERIOD: Indicator of vacation days to include. -1 = AllDays, 0 =
WorkDays, 1 = VacationDays
TIMESPAN: Set of values captured by the Timespan window. It is not practical to
construct this directly.
SUMMARY_DAY: Day to select. Astring in the format YYYY/MM/DD. The
following is an example link wizard expression that can build such a string value
from the a TEP 16 character timestamp attribute value (assuming years in the 20yy
range):
dt = $knt.Processor:ATTRIBUTE.NTPROCSSR_H.WRITETIME$; yyyy = "20" +
STR(dt, 2, 2); mm = STR(dt, 4, 2); dd = STR(dt, 6, 2); yyyy + "/" + mm + "/" + dd
SUMMARY_WEEK: First day of week to select. A string in the format
YYYY/MM/DD
Because of the open-ended nature of the custom queries and their provision by
multiple agent groups, it is possible that other symbols might also be used. One
way to understand what values are required is to save a copy of the query and
edit it to remove clauses involving the symbols. When the modified query is
assigned to a view (assuming any syntax errors are overcome), it should return an
unfiltered view of the table. The values in the table, in conjunction with close
examination of the query text, can be used as a guide to what to provide as filter
values.
Another symbol that has been specifically asked about is $Server_Name$. This is
the name of the server of interest. If the workspace is below the agent level in the
navigator tree, $NODE$ will usually return an appropriate value. If the value is
being provided through a link, it can often be picked from the Server Name
attribute of the link source row. When in doubt, examining a display of the
unfiltered table can help determine what is expected.
In summary, it should be emphasized that the product-provided workspaces based
on these queries should be used whenever possible.
A message appears after accepting the license
UNIX only During installation of the Monitoring Agent, immediately after
accepting the license agreement, a message similar to the following
lslpp:
message
might be displayed:
Press Enter to continue viewing the licenseagreement, or
enter "1" to accept the agreement, "2" to decline it, "3" to print it,"4"
to read non-IBM terms, or "99" togo back to the previous screen.
1
lslpp: Fileset gsksa.rte not installed.
This message is harmless and is associated with verifying the versions of the gskit
component installed by IBM Tivoli Monitoring. The message is displayed at a point
where the UNIX installation normally pauses for a number of seconds, causing a
tendency to think the installation has failed, although this is not the case.
Chapter 10. Monitoring agent troubleshooting
199