Running Dynamic Workload Console reports and batch reports
- Job Run History Report
- A report collecting the historical job run data during a specified time interval. It is useful to detect which jobs ended in error or were late, as well as critical and promoted jobs and the latest time within which the job can start without causing the critical job miss its deadline. It also shows which jobs missed their deadline, long duration jobs, and rerun indicators for reruns.
- Job Run Statistics Report
- A report collecting the job run statistics. It is useful to detect success, error rates; minimum, maximum, and average duration; late and long duration statistics.
- Workstation Workload Summary Report
- A report showing the workload on the specified workstations. The workload is expressed in terms of number of jobs that ran on them. It is useful for capacity planning adjustments (workload modelling and workstation tuning).
- Workstation Workload Runtimes Report
- A report showing job run times and duration on the specified workstations. It is useful for capacity planning adjustments (workload modelling and workstation tuning).
- Planned Production Details Report
- A report based on the information stored either in a trial or in a forecast plan. The information contained in these plans is retrieved from the HCL Workload Automation database. A Planned Production Details Report can be run on distributed engines (master domain manager and backup domain manager). A real production report extracted from a fault-tolerant agent might contain different information with respect to a plan extracted from a master domain manager. For example, the number of jobs and job streams is the same, but their status can change, because a job successful on the master can be in hold or ready on the agent. The update status rate is the same only on the full status agent that runs on the domain master.
- Actual Production Details Report
- A report based on the information stored either in the current or in an archived plan. The information contained in these plans is retrieved from the Symphony files. Actual Production Details Report can be run on distributed engines (master domain manager, backup domain manager, domain manager with connector, and fault-tolerant agent with connector).
- Custom SQL Report
- It enables you to create reports by running your own SQL queries. The reports will display a table with the column name as specified in the SELECT part of the SQL statement. The data for reporting is stored in a DB2 relational database and resides on the distributed side. HCL Workload Automation for Z connects to the database through the Java Database Connectivity (JDBC) interface. A JDBC driver type 4 is used to connect to the remote DB2 for LUW version 8.2, or later.
- Personalized reports created with Business Intelligence and Reporting Tools (BIRT)
- Use this function to upload your custom reports created with BIRT and import them as task.
For more information about creating reports from the Dynamic Workload Console, see Reporting.
Some of these reports are also available as batch reports and can be run from a command line. For more information on how to run batch reports, see Running batch reports from the command line interface.
Name of the report | Output formats supported by the Dynamic Workload Console | Output formats supported by batch reports |
---|---|---|
Job Run Statistics Report | HTML, CSV, PDF |
HTML, CSV, PDF |
Job Run History Report |
HTML, CSV, PDF |
HTML, CSV, PDF |
Workstation Workload Summary Report | HTML, CSV, PDF |
HTML, CSV, PDF |
Workstation Workload Runtimes Report | HTML, CSV, PDF |
HTML, CSV, PDF |
Actual Production Details Report | XML, CSV |
N/A |
Planned Production Details Report |
XML, CSV |
N/A |
Custom SQL Report | HTML, CSV, PDF |
HTML, CSV, PDF |
Auditing general report (For more information, see Keeping track of database changes using audit reports) |
N/A | HTML, CSV, PDF |
Auditing details report (For more information, see Keeping track of database changes using audit reports) |
N/A | HTML, CSV, PDF |
You must have the appropriate security file authorizations for report objects to run these reports (granted by default to the tws_user on fresh installations). See the Administration Guide for security file information.
See also the Administration Guide to learn how to configure the Dynamic Workload Console to view reports.