IBM E027SLL-H Troubleshooting Guide - Page 62

Setting the trace option for the portal client trace, Setting the trace option for the portal server

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

used to trace groups of routines related by function (or component). Use this keyword only at the explicit request of an IBM Software Support representative. component_type Identifies a component type. An IBM Software Support representative can tell you what value to specify. ENTRY Narrows a filtering routine to specify a specific ENTRY POINT. Since multiple entry points for a single routine are rare, use this keyword only at the explicit request of an IBM Software Support representative. entry_point Represents the name of the entry point. An IBM Software Support representative can tell you what value to specify. UNIT Indicates that the trace is to look for a match between the compilation unit dispatched and the fully or partially qualified compilation unit specified on the RAS1 statement. A match results in a trace entry. unit_name Represents the name of the compilation unit. In most instances, this name defines the component that is being traced. The value is likely to be the three-character component identifier for the monitoring agent (KHL for OMEGAMON® z/OS Management Console). class One of the same values specified for global_class but, because of its position inside the parentheses, narrowed in scope to apply only to the unit_name specified. Setting the trace option for the portal client trace A log file is created automatically the first time you start the Tivoli Enterprise Portal, and is named install_dir\cnp\logs\kcjras1.log. This log file contains all of the RAS1 tracing for the portal client. Whenever you start a new work session, the log file is purged and rewritten for the current work session. If you want to preserve the log file from the last work session, you must rename it or copy it to another directory before starting the portal client again. The kcj.log file contains errors generated by the Java™ libraries used in the portal client. Procedure 1. Always backup the files before altering them. 2. From the Tivoli Enterprise Portal menu, select File > Trace Options. 3. Select a trace class from the list or as instructed by IBM Software Support (such as UNIT:Workspace ALL): v ALL provides data for all classes. Use the setting temporarily, because it generates large amounts of data. v ERROR logs internal error conditions. This setting provides the minimum level of tracing, with little resource overhead, and ensures that program failures will be caught and detailed. v NONE turns off the error log so no data is collected. 4. Click OK to close the window and turn on logging. Setting the trace option for the portal server trace Set the trace options for the Tivoli Enterprise Portal Server through Manage Tivoli Enterprise Monitoring Services. 44 IBM Tivoli Monitoring: Troubleshooting Guide

  • 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
used to trace groups of routines related by function (or component). Use
this keyword only at the explicit request of an IBM Software Support
representative.
component_type
Identifies a component type. An IBM Software Support representative can
tell you what value to specify.
ENTRY
Narrows a filtering routine to specify a specific ENTRY POINT. Since
multiple entry points for a single routine are rare, use this keyword only at
the explicit request of an IBM Software Support representative.
entry_point
Represents the name of the entry point. An IBM Software Support
representative can tell you what value to specify.
UNIT
Indicates that the trace is to look for a match between the compilation unit
dispatched and the fully or partially qualified compilation unit specified on
the RAS1 statement. A match results in a trace entry.
unit_name
Represents the name of the compilation unit. In most instances, this name
defines the component that is being traced. The value is likely to be the
three-character component identifier for the monitoring agent (KHL for
OMEGAMON
®
z/OS Management Console).
class
One of the same values specified for global_class but, because of its
position inside the parentheses, narrowed in scope to apply only to the
unit_name specified.
Setting the trace option for the portal client trace
A log file is created automatically the first time you start the Tivoli Enterprise
Portal, and is named
install_dir
\cnp\logs\kcjras1.log
. This log file contains all
of the RAS1 tracing for the portal client. Whenever you start a new work session,
the log file is purged and rewritten for the current work session. If you want to
preserve the log file from the last work session, you must rename it or copy it to
another directory before starting the portal client again. The
kcj.log
file contains
errors generated by the Java
™
libraries used in the portal client.
Procedure
1.
Always backup the files before altering them.
2.
From the Tivoli Enterprise Portal menu, select
File
>
Trace Options
.
3.
Select a trace class from the list or as instructed by IBM Software Support (such
as UNIT:Workspace ALL):
v
ALL
provides data for all classes. Use the setting temporarily, because it
generates large amounts of data.
v
ERROR
logs internal error conditions. This setting provides the minimum
level of tracing, with little resource overhead, and ensures that program
failures will be caught and detailed.
v
NONE
turns off the error log so no data is collected.
4.
Click
OK
to close the window and turn on logging.
Setting the trace option for the portal server trace
Set the trace options for the Tivoli Enterprise Portal Server through Manage Tivoli
Enterprise Monitoring Services.
44
IBM Tivoli Monitoring: Troubleshooting Guide