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

Document related concepts
no text concepts found
Transcript
|
|
|
|
|
This problem is due to a missing option setting in the EDWA configuration file. To
solve this problem, add the following line in the files <TWS_INST_DIR>/TWS/ssm/
bin/preload_ssmagent_0.sh and <TWS_INST_DIR>/TWS/EDWA/ssm/bin/
preload_ssmagent_0.sh:
|
where <TWS_INST_DIR> is the Tivoli Workload Scheduler installation directory.
export LDR_CNTRL=MAXDATA=0x80000000
File creation and deletion actions not triggered
|
|
|
|
You are monitoring the creation or the deletion of a file on Windows using the
FileCreated and FileDeleted events. The file is created or deleted, but the event
action is not triggered.
|
Cause and solution:
|
|
|
|
|
The SSM agent monitors the file creation and deletion. An event is sent when a file
that matches the string in the event rule is created or is deleted. However, on
Windows platforms, if the file path contains forward slashes ("/"), the event action
is not triggered. Replace forward slashes ("/") with backward slashes ("\") and
redeploy the rule.
Problems using the "legacy" global options
This section describes problems that might occur when running Tivoli Workload
Scheduler with the "legacy" global options set. The "legacy" global options are
those that have the word "Legacy" in their option name in optman. Use them if you
want to maintain certain Tivoli Workload Scheduler behaviors as they were in
previous versions of Tivoli Workload Scheduler.
v “Time zones do not resolve correctly with enLegacyStartOfDayEvaluation set”
v “Dependencies not processed correctly when enLegacyId set”
Time zones do not resolve correctly with
enLegacyStartOfDayEvaluation set
You are using Tivoli Workload Scheduler with the enLegacyStartOfDayEvaluation
and enTimeZone options set to yes to convert the startOfDay time set on the master
domain manager to the local time zone set on each workstation across the
network. You submit a job or job stream with the at keyword, but the job or job
stream does not start when expected.
Cause and solution:
Add the absolute keyword to make sure that the submission times are resolved
correctly. The absolute keyword specifies that the start date is based on the
calendar day rather than on the production day.
Dependencies not processed correctly when enLegacyId set
You are using Tivoli Workload Scheduler in a network which includes agents
running on versions older than 8.3, but managed by a version 8.3 or later master
domain manager, with the enLegacyId option set to yes, to enable the use of the
former job stream ID format. When you create multiple instances of a job stream as
pending predecessors, errors caused by identification problems at submission time
are given.
136
Tivoli Workload Scheduler: Troubleshooting Guide