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
are set to be filtered (traced) are removed from whatever
other filter criteria you might have set.
For example, you might create a filter file that configures the
tracing of the communications functions. You could then add this
set of functions to your filter set in one command, or remove them,
depending on whether you think the communications are part of
the problem you are trying to solve.
The add and remove actions are processed in the order you submit them.
Thus if you add a function ID, and then remove a range that includes that
ID it is removed from the criteria. But if you remove the range, and then
add the ID, it is added to the criteria.
-modifyFilter <filter_file>
Modifies the existing filter file named in the parameter.
This subcommand takes all of the parameters used in the -addFilter
subcommand in the same way, with the addition of the following action:
Removes all components and functions from the filter file. Use this
with one of the -add options to create an inclusive "all of the
following" filter.
-clean On UNIX operating systems only, use this to delete the shared memory
segments after you have modified and saved the configuration file, and
stopped the product. If a segment is in use, it is marked for deletion and
will be automatically deleted when no longer in use.
-config [<config_file> ]
This initializes the memory. It is run automatically when the Tivoli
Workload Scheduler engine is restarted, using the default configuration file
./xtrace.ini. In normal circumstances, you never need to run this
manually. If you believe that the shared memory is corrupted, it is better to
restart the product, which automatically re-initializes the memory.
The following examples are a scenario for using the trace to troubleshoot an
instance of Tivoli Workload Scheduler which is hanging for 5 minutes when you
run a particular utility command, without giving any log messages to indicate
The presupposition is that you have the following configuration file:
[ _GLOBAL_ ]
= TWS_8.6.0
= y
= n
= 1
FilterFile = $(install_dir)/bin/xfull.xtrace
= 10240
= 80
SegPerUser = n
Tivoli Workload Scheduler: Troubleshooting Guide