Reports
Create a report task to customize and generate HCL Workload Automation reports, which you can then view, print, and save, in different kinds of output. Reports help you in many business-related activities, such as:
- Tuning the workload on the workstations
- Workstation Workload Summary
- Workstation Workload Runtimes
- Extract detailed information about the plan
- Planned Production Details
- Actual Production Details
- Detect jobs with exceptions
- Job Run History
- Job Run Statistics
To generate your reports, you can use either Business Intelligent Report Tool (BIRT) or Tivoli Common Reporting. For more information, see Reporting.
The following table shows the available reports, both for BIRT and Tivoli Common Reporting and their details.
| Report Name | Description | Supported environment | Supported by |
|---|---|---|---|
| Job Run History | Collects the historical job run data during a specified time interval. Use it to detect which jobs ended in error or were late. It also shows which jobs missed their deadline, long duration jobs, and rerun indicators for reruns. | Distributed and z/OS | Tivoli Common Reporting and BIRT |
| Job Run Statistics Chart | Collects the job run statistics. Use it to detect success, error rates; minimum, maximum, and average duration; late and long duration statistics. | Distributed | Tivoli Common Reporting and BIRT |
| Job Run Statistics Table | A report collecting the job run statistics, which returns output in table format. It is useful to detect success, error rates; minimum, maximum, and average duration; late and long duration statistics. | Distributed | Tivoli Common Reporting and BIRT |
| Job Run Statistics | A report collecting the job run statistics, which returns output in table format. It is useful to detect success, error rates; minimum, maximum, and average duration; late and long duration statistics. | z/OS | BIRT |
| Workstation Workload Summary | Shows the workload on the specified workstations. The workload is expressed in terms of number of jobs that ran on them. It helps for capacity planning adjustments (workload modelling and workstation tuning). | Distributed and z/OS | BIRT |
| Workstation Workload Runtimes | Shows job run times and duration on the specified workstations. It helps for capacity planning adjustments (workload modelling and workstation tuning). | Distributed and z/OS | BIRT |
| Custom SQL | Allows you to create reports that best fit your business needs. You can specify an SQL query or import SQL scripts. | Distributed | BIRT |
| Planned Production Details | Extracts information about planned production plans into either an XML or a CSV format, to be used respectively, with Microsoft Project and Microsoft Excel. This also allows users who do not know HCL Workload Automation to access plan information in a familiar format. | Distributed | BIRT |
| Actual Production Details | Extracts current plan information into either an XML or a CSV format, to be used, respectively, with Microsoft Project and Microsoft Excel. This also allows users who do not know HCL Workload Automation to access plan information in a familiar format. | Distributed | BIRT |
| Analysis Job Duration Estimation Error | A report that shows the average estimation error. It is useful to detect whether a job ends in frequent errors, ends in error, or if the jobs have unsatisfactory accuracy rates. You can then drill down to display all the jobs that are in that threshold and finally you can visualize charts that will help you to identify the jobs that have a high estimated error rate allowing you to intervene beforehand on those jobs. | Distributed and z/OS | Tivoli Common Reporting |
| Analysis Job Duration Standard Deviation | A report showing variances in job duration. The variance is calculated as a percentage and according to which variance level the jobs are they will be presented as follows: High variability, Medium variability or a Low variability. You can drill down to display all the jobs that are in that threshold which then returns output in a chart format. This report is useful to identify the run that had a greater duration. | Distributed and z/OS | Tivoli Common Reporting |
The output of historical reports, which is extracted from the database,
consists of the following main sections. The output of a Planned and
Actual report is not structured because it is a file that must be
opened with an external program.
- Report header
- Contains the report title, description, engine name, engine type, creation time, type, and the total number of the result set extracted.
- Report of content
- Contains a set of hyper-links to each section and subsection.
- Report format
- Depending
on the kind of information you are processing, you can choose to view
it in the most appropriate format. The report output can be in:
- Table format
- It shows information organized in rows and columns, in a CSV or HTML file.
- Graphical format (HTML)
- If you choose the graphical formats, depending on the report type, and on the information you choose to include, you can have data displayed in pie charts, bar charts, line charts, or tables.
Note: To see report output correctly, make sure that you configure
your browser as follows:
- Allow pop-up windows.
- Remove any optional browser toolbar that you installed, if its settings prevent new windows from opening.
- To see CSV reports, configure the browser security settings to automatically prompt for file downloads.