Download Tivoli Workload Scheduler: Troubleshooting Guide

Survey
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

Transcript
tws_cli
All Tivoli Workload Scheduler command line communications are
traced.
tws_conn
All Tivoli Workload Scheduler connector communications are traced.
tws_db
All Tivoli Workload Scheduler database communications are traced.
tws_info
Only information messages are traced. The default value.
tws_planner
All Tivoli Workload Scheduler planner communications are traced.
tws_secjni
All Tivoli Workload Scheduler jni code auditing and security
communications are traced. The jni code refers to code in shared C
libraries invoked from Java. Only use this option under the guidance
of, IBM Software Support.
tws_utils
All Tivoli Workload Scheduler utility communications are traced.
tws_broker_all
All dynamic workload broker communications are traced.
tws_broker_rest
Only the communication between dynamic workload broker and the
agents is traced.
tws_bridge
Only the messages issued by the workload broker workstation are
traced.
4. Stop and restart the application server, as described in the section on starting
and stopping the application server in the Tivoli Workload Scheduler:
Administration Guide.
To reset the traces to the default value, either run the above procedure with
trace_mode as tws_info, or just stop and start the server, as follows:
1. Log on to the computer where Tivoli Workload Scheduler is installed as the
following user:
UNIX root
Windows
Any user in the Administrators group.
2. Access the directory: <TWA_home>/wastools
3. Stop and restart the application server as described in the section on starting
and stopping the application server in the Tivoli Workload Scheduler:
Administration Guide.
Log files for the command line client
The command line client writes its logs in the following files:
UNIX <command line client install directory>/stdlist/yyyy.mm.dd/
<TWS_user>
Chapter 2. Logs and traces
39
Document related concepts
no text concepts found