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
If Tivoli Workload Scheduler does not receive a return code from the extended
agent job, it substitutes the return code with the exit code of the method. If this
last is zero, the job has finished successfully. If it is not zero, contact IBM Software
Support for an explanation of the exit code and a resolution of the problem.
Planner problems
The following problems could be encountered with the planner:
There is a mismatch between Job Scheduler instances in the
Symphony file and the preproduction plan
You notice that there are Job Scheduler instances in the Symphony file that are not in
the preproduction plan.
Cause and solution:
Job streams are automatically deleted from the preproduction plan when they are
completed. However, it is possible to set the "carryStates" global option (using
optman) so that job streams with jobs in the SUCC status are carried forward. In
this case such job streams are carried forward to the new Symphony file when the
plan is extended, but are deleted from the preproduction plan if the job streams
have been successfully completed. This is not an error. These job streams can
remain in the current plan (Symphony file) and can even be run again.
To resolve the situation for a given plan, use conman or the Dynamic Workload
Console to delete the Job Scheduler instances from the plan.
To prevent the problem reoccurring, consider why the "carryStates" global option is
set so that job streams with jobs in the SUCC status are carried forward. If it has
been set in error, or is no longer required, change the settings of the option (using
optman) so that this no longer happens.
Planman deploy error when deploying a plug-in
When using the planman deploy command to deploy a plug-in, the deploy fails
with the following error:
AWSJCS011E An internal error has occurred. The error is the following:
"ACTEX0019E The following errors
from the Java compiler cannot be parsed:
error: error reading <file_name>; Error opening zip file
<file_name>
Cause and solution:
The .jar file identified in the message is corrupt. Check and correct the format of
the file before retrying the deploy.
An insufficient space error occurs while deploying rules
When using the planman deploy command with the -scratch option to deploy all
non-draft rules, the following error occurs:
AWSJCS011E An internal error has occurred. The error is the following:
"ACTEX0023E The Active Correlation Technology compiler cannot
communicate with the external Java compiler.
java.io.IOException: Not enough space".
Cause and solution:
Chapter 8. Troubleshooting engine problems
117
Document related concepts
no text concepts found