Download Tivoli Workload Scheduler: Troubleshooting Guide

yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
You can choose to use any number of segments (each is identified by a
unique number) and for each segment can determine how much shared
memory the segment is to use. More and bigger segments consume more
memory, with all the normal consequences that entails.
Any number of Tivoli Workload Scheduler programs can be configured to
be saved to the same segment. You decide which programs are to be traced
to which segments, and whether those segments are to be enabled for
tracing, by modifying the basic configuration. Any of the Tivoli Workload
Scheduler programs and utilities can be configured for tracing.
Basic configuration
The basic configuration determines which segments are enabled for tracing,
and makes an initial determination of whether the tracing for a specific
program is activated. It is achieved by editing a configuration file with a
text editor. The Tivoli Workload Scheduler engine (the product) must be
restarted to make the changes take effect. The configuration is divided into
the following sections:
This section not only includes general information like the product
code and the segment size, but also acts as a "catch-all", where
traces from programs not specifically configured are configured.
If a program is not to be traced under the "global" section, a
specific program section must be configured, defining which
segment the program is to be traced in, and other basic
information. The information in a program section overrides that in
the global section, but just for that program.
Activating and deactivating traces
For segments which are enabled, traces for specific programs can be
activated and deactivated on-the-fly, from the command line, as these flags
are held in memory.
Trace levels
Events in the code have been assigned trace levels. The lower the level, the
more drastic the event. The levels range from reporting only unrecoverable
errors, through recoverable errors, warnings, and informational messages
and three debug levels to the maximum reporting level, where even
function entry and exit events are recorded.
Trace levels can also be changed on-the-fly, from the command line,
without restarting the engine.
In-Flight Trace lets you take a snapshot of the current contents of the traces
for a program or segment and save it to a file. You can optionally clear the
memory in the segment after taking the snapshot. The snapshot file is in
the internal format, containing function IDs, etc., and is not easily readable.
It must be formatted to make it readable.
Formatting the snapshot
A command-line option lets you format a snapshot file for the standard
output. The output can be in CSV or XML format, and information about
the source data (file name and line number) is automatically included. Or
you can select the standard trace format (one line per trace record) and
Tivoli Workload Scheduler: Troubleshooting Guide