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
In many of the parameters of the xcli command, you are required to select a
program or a segment, and optionally a product. To avoid repeating the same
information, details of how to do this are supplied here:
Select a program for a specific action by identifying the global section ([
_GLOBAL_ ]) or any of the configuration file sections containing Tivoli
Workload Scheduler programs ([<program>] ).
Select one of the segment numbers that were defined in the configuration
file when the shared memory was initialized. If you need to use extra
segments or redistribute the programs within the segments, you must edit
and save the configuration file and then stop and restart the Tivoli
Workload Scheduler engine.
The tracing facility is multi-product. However, if you run the xcli
command from the same directory as a configuration file, you
automatically run it on the product defined in that configuration file,
without having to define the product in the command.
But if you are using In-Flight Trace to trace more than one product, and
you want to use the command supplied with product A to modify the
tracing of product B, you must supply the product code for product B as a
parameter to the command, by adding the -P <product> parameter to the
command string. This parameter in only applicable to the -snap, -query,
-active, -level, and -filter subcommands.
xcli command syntax
Gives the full syntax of the xcli command.
Controls all of the runtime aspects of the In-Flight Trace facility. It modifies the
information in shared memory. Shared memory is initialized from the information
in the configuration file, but any changes to shared memory made using the
options of this command are not saved in the configuration file.
You must be the TWS_user to run the command.
-snap <snap_file>
{ -p <program> | -s <segment> }
[ -descr <description> ]
[ -clean ]
[ -P <product> ]
-format <snap_file>
-d <symbols_database>
[ -full ]
[ -noHeader ]
[ -standard [ -source ] | -xml | -csv ]
-query [ -p <program> | -s <segment> ] [-P <product> ]
Chapter 4. In-Flight Trace facility