IBM E027SLL-H Troubleshooting Guide - Page 71

Dynamically modify trace settings for an IBM Tivoli Monitoring, component

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 71 highlights

configuration_file_name The file name of the actively loaded configuration file as indicated by the situpdate.properties file. trace_level Specifies the level of trace as low, med, or verbose. Setting up RAS1 tracing on z/OS systems Edit the KpcENV (where pc is the product code) environment file to set the RAS1 trace level for your OMEGAMON product. This syntax is used to specify a RAS1 trace in the KppENV file (where pp is the product code: HL for the OMEGAMON z/OS Management Console or DS for the Tivoli Enterprise Monitoring Server). After you add this configuration setting to the KppENV file, you must stop and restart the address space for the setting to take effect. After that, it remains in effect for the life of the address space. To end the trace, you must edit the KppENV file again to reset the trace level, and stop and restart the address space. RAS1 trace setting syntax The KBB_RAS1 environment variable setting follows the RAS1 trace setting syntax as described in "RAS1 syntax" on page 43. Note: The default setting for monitoring agents on z/OS is KBB_RAS1=ERROR, meaning that only error tracing is enabled. You can specify any combination of UNIT, COMP, and ENTRY keywords. No keyword is required. However, the RAS1 value you set with the global class applies to all components. For more information on setting RAS1 tracing on z/OS systems, see your individual monitoring agent's user's guide. Dynamically modify trace settings for an IBM Tivoli Monitoring component You can access the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, almost all of the agents, and other IBM Tivoli Monitoring components from this utility. This method of modifying trace settings on an IBM Tivoli Monitoring component is the most efficient method since it allows you to do so without restarting the component. Settings take effect immediately. Modifications made this way are not persistent. Note: When the component is restarted the trace settings are read again from the .env file. Dynamically modifying these settings does not change the settings in the .env files. In order to modify these trace settings permanently, modify them in the .env files. How to turn tracing on: In order to use this utility you need to know a local log-on credential for the system. This method uses the IBM Tivoli Monitoring Service Console. The Service Console is accessed using a web browser. Access the utility by using the following link: http://hostname:1920 Chapter 4. Tools 53

  • 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
configuration_file_name
The file name of the actively loaded configuration file as indicated by the
situpdate.properties
file.
trace_level
Specifies the level of trace as
low
,
med
, or
verbose
.
Setting up RAS1 tracing on z/OS systems
Edit the
K
pc
ENV
(where
pc
is the product code) environment file to set the RAS1
trace level for your OMEGAMON product.
This syntax is used to specify a RAS1 trace in the
K
pp
ENV
file (where
pp
is the
product code:
HL
for the OMEGAMON z/OS Management Console or
DS
for the
Tivoli Enterprise Monitoring Server). After you add this configuration setting to
the
KppENV
file, you must stop and restart the address space for the setting to take
effect. After that, it remains in effect for the life of the address space. To end the
trace, you must edit the
KppENV
file again to reset the trace level, and stop and
restart the address space.
RAS1 trace setting syntax
The KBB_RAS1 environment variable setting follows the RAS1 trace setting syntax
as described in “RAS1 syntax” on page 43.
Note:
The default setting for monitoring agents on z/OS is
KBB_RAS1=ERROR
,
meaning that only error tracing is enabled. You can specify any combination of
UNIT, COMP, and ENTRY keywords. No keyword is required. However, the RAS1
value you set with the global class applies to all components.
For more information on setting RAS1 tracing on z/OS systems, see your
individual monitoring agent's user's guide.
Dynamically modify trace settings for an IBM Tivoli Monitoring
component
You can access the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal
Server, almost all of the agents, and other IBM Tivoli Monitoring components from
this utility.
This method of modifying trace settings on an IBM Tivoli Monitoring component
is the most efficient method since it allows you to do so without restarting the
component. Settings take effect immediately. Modifications made this way are not
persistent.
Note:
When the component is restarted the trace settings are read again from the
.env
file. Dynamically modifying these settings does not change the settings in the
.env
files. In order to modify these trace settings permanently, modify them in the
.env
files.
How to turn tracing on:
In order to use this utility you need to know a local log-on credential for the
system.
This method uses the IBM Tivoli Monitoring Service Console. The Service Console
is accessed using a web browser. Access the utility by using the following link:
http://hostname:1920
Chapter 4. Tools
53