Scribd
Upload
56 views

Miscellaneous

The following TWS directories need periodic cleaning: 1) ~maestrohome/atjobs, ~maestrohome/audit, and ~maestrohome/schedlog which need to be cleaned out manually. 2) ~maestrohome/stdlist which can be cleaned using the "rmstdlist" command. 3) ~twshome/tmp which can be cleaned out manually when files are no longer in use.

Uploaded by

Shrikant Bhardwaj
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
56 views

Miscellaneous

The following TWS directories need periodic cleaning: 1) ~maestrohome/atjobs, ~maestrohome/audit, and ~maestrohome/schedlog which need to be cleaned out manually. 2) ~maestrohome/stdlist which can be cleaned using the "rmstdlist" command. 3) ~twshome/tmp which can be cleaned out manually when files are no longer in use.

Uploaded by

Shrikant Bhardwaj
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

TWS directories need periodic maintenance

Question
Tivoli Workload Scheduler (TWS) directories need periodic maintenance. What specific directories
must be maintained?

Answer
The following TWS directories will continue to grow in size unless periodically cleaned out.

NOTE: It is highly recommended that regular, accurate backups be obtained of all the TWS
directories, and to always perform a backup before removing any information from the TWS
environment.

o ~maestrohome/atjobs

The ~maestrohome/atjobs directory needs to be cleaned out manually.

o ~maestrohome/audit

If auditing is not functioning, no activity will be written to the "~maestrohome/audit /database" and
"/plan" directories. However, if auditing is turned on, these directories will grow in size with daily
activity.

The ~maestrohome/audit directories need to be cleaned out manually.

o ~maestrohome/stdlist

The "~maestrohome/stdlist" directory can be cleaned out using the "rmstdlist" command.

Allowing files to build in this directory can cause significant space issues.

o ~maestrohome/schedlog

The "~maestrohome/schedlog" directory needs to be cleaned out manually. Allowing more than 200
files to accumulate in this directory can cause problems when attempting to retrieve information from
earlier production control files (Symphony).

o ~twshome/tmp

The "twshome/tmp" directory can be cleaned out manually as long as the files in the directory are not
being used by another job or process.

o The Job Scheduling Console (JSC) component of TWS has the capability to write error logs and
trace information to its own directory. The JSC error.log and JSConsole.log(s) can be found in:

~JSConsolehomedirectory\dat\.tmeconsole\error.log

~JSConsolehomedirectory\dat\.tmeconsole\JSConsole.log

By default, the maximum size of each JSConsole.log can reach 3 MB. When this limit is reached, the
tracing facility creates an additional log file. The tracing facility can create up to ten log files for a
total of 30 MB, which can create significant unusable space.

An additional note of importance is that the total size can be changed by using the advanced
customization options (See the JSC User Guide, Appendix A for further information), so this can
create a large drain on space. It is advised that if tracing has been set for any reason, once the logs
have been obtained, tracing should be unset to avoid all JSConsole actions being needlessly traced
and written to logfiles.

TWS LoadLeveler log files


Tivoli Workload Scheduler LoadLeveler Diagnosis and Messages Guide
GA22-7882-06

TWS LoadLeveler log files include messages indicating what the daemon or process is doing
and when that processing is occurring, using timestamps. This includes what transactions
being received from and sent to other daemons or processes, and indication of error
conditions encountered. Indication of transactions sent to daemons as a result of invoking
TWS LoadLeveler commands are also included in the daemon logs.

There is a separate log for each TWS LoadLeveler daemon and for each of the starter
processes on each machine in the TWS LoadLeveler cluster. The starter logs are appended
with the process ID of the starter process and exist as long as the starter processes are
running. Upon each job's termination, the individual starter logs are appended to a single
starter log.

By default, TWS LoadLeveler stores only the two most recent iterations of a daemon's log
file (<daemon_name>Log, and <daemon_name>Log.old). Occasionally, for problem
diagnosing, users will need to capture TWS LoadLeveler logs over an extended period.
Users can specify that all log files be saved to a particular directory by using the
SAVELOGS keyword in a local or global configuration file. Be aware that TWS LoadLeveler
does not provide any way to manage and clean out all of those log files, so users must be
sure to specify a directory in a file system with enough space to accommodate them. This
file system should be separate from the one used for the TWS LoadLeveler log, spool, and
execute directories.

Each log file is represented by the name of the daemon that generated it, the exact time
the file was generated, and the name of the machine on which the daemon is running.

See TWS LoadLeveler: Using and Administering for information on how to control log file
contents and maximum size information. You can find a job step by name in the logs by
using the vi editor and looking for JOB_START or other job states.

TWS LoadLeveler log files are not translated.

You might also like