Log files and archived files

Log files are produced from a variety of HCL Workload Automation activities. Other activities produce files which are archived after they have been used. The details are given in Log and trace file maintenance.

Starting from version 10.1 Fix Pack 1, when generating a job log in the monitoring section of the Dynamic Workload Console, by default the log is stored in memory. This ensures compliance with the PCI standard.

To change this behavior and have the job log stored in a file, as it was in versions earlier than version 10.1 Fix Pack 1, perform the following steps:
  1. Add the com.ibm.tws.conn.plan.output.logtype property in the TWSConfig.properties file.
  2. Set the property to file.
  3. Stop and start all the HCL Workload Automation processes.
Table 1. Log and trace file maintenance
Activity Description Location Maintenance method
Fault-tolerant agent Each HCL Workload Automation process logs its activities, writing them in log and trace message files:

Log messages

These are messages intended for use directly by you, and provide information, errors and warnings about the processes.
netman
On Windows systems
TWA_home/TWS/stdlist/logs/yyyymmdd_NETMAN.log
On UNIX operating systems
<TWA_DATA_DIR>/stdlist/logs/yyyymmdd_NETMAN.log
Other processes
On Windows systems
TWA_home/TWS/stdlist/logs/yyyymmdd_TWSMERGE.log
On UNIX operating systems
<TWA_DATA_DIR>/stdlist/logs/yyyymmdd_TWSMERGE.log
This is the default situation. You can set an option in the localopts file to create separate log files for the major processes.		 rmstdlist

Trace messages

These are messages written when a problem occurs that you can probably not solve without the assistance of HCL Software Support.
netman
On Windows systems
TWA_home/TWS/stdlist/traces/yyyymmdd_NETMAN.log
On UNIX operating systems
<TWA_DATA_DIR>/stdlist/logs/yyyymmdd_NETMAN.log
Other processes
On Windows systems
TWA_home/TWS/stdlist/traces/yyyymmdd_TWSMERGE.log
On UNIX operating systems
<TWA_DATA_DIR>/stdlist/logs/yyyymmdd_TWSMERGE.log
This is the default situation. You can set an option in the localopts file to create separate trace files for the major processes.
Master domain manager job management The job manager process on the master domain manager archives the previous period's Symphony file.
On Windows systems
TWA_home>\TWS\schedlog\date
On UNIX systems
<TWA_DATA_DIR>/TWS/schedlog/date
 Manual
Job Each job that runs under HCL Workload Automation control creates an output file. These files are archived.
On Windows systems
TWA_home\TWS/stdlist\date
On UNIX systems
<TWA_DATA_DIR>/TWS/stdlist/date
where date is in the format yyyy.mm.dd		 rmstdlist
Dynamic agent

Log messages
Windows
TWA_home>\TWS\stdlist\JM\JobManager_message.log
UNIX
<TWA_DATA_DIR>/TWS/stdlist/JM/JobManager_message.log
 Regular housekeeping is performed through the configuration of several parameters. See Regular maintenance.

Trace messages
Windows
  • TWA_home>\TWS\stdlist\JM\ITA_trace.log
  • TWA_home>\TWS\stdlist\JM\JobManager_trace.log
  • TWA_home>\TWS\JavaExt\logs\javaExecutor0.log
UNIX
  • <TWA_DATA_DIR>/TWS/stdlist/JM/ITA_trace.log
  • <TWA_DATA_DIR>/TWS/stdlist/JM/JobManager_trace.log
  • <TWA_DATA_DIR>/TWS/JavaExt/logs/javaExecutor0.log

Jobs with advanced options
Windows
TWA_home>\TWS\stdlist\JM\date>
UNIX
<TWA_DATA_DIR>/TWS/stdlist/JM/date>

where date is in the format yyyy.mm.dd
Forecast and trial plan creation The creation of forecast and trial plans require manual maintenance.
Forecast plan
These files are to be maintained manually
Trail plan
These files are to be maintained manually
 Manual
Audit The audit facility writes log files.
On Windows operating systems
TWA_home/TWS/audit
On UNIX operating systems
<TWA_DATA_DIR>/audit
 Manual
DB2® UDB DB2® logs its activities. Information about the location and viewing method for DB2® log files is supplied in the DB2® documentation, in Product Documentation for DB2®.

The main file to control is the db2diag.log file, which is the most important DB2® diagnostic file, which, without intervention, grows endlessly with no reuse of wasted space. This does not apply, however, to the database log files used by HCL Workload Automation, which are set up for circular reuse of disk space, so they don't grow in size over a maximum value.

 See the DB2® documentation.
Oracle database Oracle logs its activities. See the Oracle documentation. See the Oracle documentation.
WebSphere Application Server Liberty The application server writes log files.
On the server components:
On Windows operating systems
TWA_home>\TWS\stdlist\appserver\engineServer\logs
On UNIX operating systems
<TWA_DATA_DIR>/stdlist/appserver/engineServer/logs
On the Dynamic Workload Console:
On Windows operating systems
TWA_home>\stdlist\appserver\dwcServer\logs
On UNIX operating systems
<TWA_DATA_DIR>/stdlist/appserver/dwcServer/logs
 Manual
Netcool® SSM monitoring agent (not supported on IBM i systems) The agent writes log files. (ssmagent.log, traps.log)
On Windows operating systems
TWA_home>\TWS\ssm\Log
On UNIX operating systems
<TWA_DATA_DIR>/EDWA/ssm/Log/
 Manual
Other Other activities also write trace and log files.
On Windows operating systems
TWA_home>\TWS\methodes
On UNIX operating systems
TWA_home>/TWS/methods
 Manual

The easiest method of controlling the growth of these directories is to decide how long the log files are needed, then schedule a HCL Workload Automation job to remove any files older than the given number of days. Use the rmstdlist command for the process and job log files, and use a manual date check and deletion routine for the others. Make sure that no processes are using these files when you perform these activities.

See rmstdlist for full details of the rmstdlist command.
Note: The rmstdlist command might give different results on different platforms for the same scenario. This is because on UNIX® platforms the command uses the –mtime option of the find command, which is interpreted differently on different UNIX® platforms.