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.
- Add the com.ibm.tws.conn.plan.output.logtype property in the TWSConfig.properties file.
- Set the property to file.
- Stop and start all the HCL Workload Automation processes.
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. |
|
rmstdlist | |
Trace messages These are messages written when a problem occurs that you can probably not solve without the assistance of HCL Software Support. |
|
||
Master domain manager job management | The job manager process on the master domain manager archives the previous period's Symphony file. |
|
Manual |
Job | Each job that runs under HCL Workload Automation control creates an output file. These files are archived. |
|
rmstdlist |
Dynamic agent |
Log messages |
|
Regular housekeeping is performed through the configuration of several parameters. See Regular maintenance. |
Trace messages |
|
||
Jobs with advanced options |
where date is in the format yyyy.mm.dd |
||
Forecast and trial plan creation | The creation of forecast and trial plans require manual maintenance. |
|
Manual |
Audit | The audit facility writes log files. |
|
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 |
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 the Dynamic Workload Console:
|
Manual |
Netcool® SSM monitoring agent (not supported on IBM i systems) | The agent writes log files. (ssmagent.log, traps.log) |
|
Manual |
Other | Other activities also write trace and log files. |
|
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.