Reporting with IBM Workload Scheduler for z/OS
This chapter describes how the product supports the Dynamic Workload Console reporting
feature, collecting historical workload data and archiving it in dedicated
tables in a DB2® database. The
console process retrieves the archived data and returns it to you
by using the Business Intelligent Report Tool (BIRT) Report Viewer
and Tivoli Common Reporting. The same reports can also be generated
using a command line interface.
Tivoli Common Reporting is
an optional integration service of Jazz for Service Management extension for
WebSphere,
which is installed with WebSphere Application Server. Tivoli Common Reporting provides
a web user interface functioning as a portal for IBM Cognos and
allows you to administer, run, customize, and create reports on IBM® DB2.
It provides web-based, launch-in-context report administration and
editing.
Using reporting with IBM Workload Scheduler for z/OS, you archive historical data about jobs and workstation workloads in the DB2 database. The historical data consist of old current plan data collected at daily planning time.
For example, you can extend or replan your current plan more than once a day but decide to run the archiving process only once, selecting the new ARCHIVE option from the daily planning dialog. This triggers the submission of a batch job that archives the historical data in the DB2 database, by Java™ Data Base Connectivity (JDBC) services.
- Host system
-
- Ensure that you have added the fault-tolerant end-to-end feature using SMP/E on your IBM Workload Scheduler for z/OS installation.
- In the BATCHOPT statement, specify JRUNHISTORY(YES); in the parameter library, create the DBOPT statement to connect to DB2; in the SERVOPTS statement, set DBOPTPRM(DBOPT).
- Run the required sample jobs (EQQPCS08 and EQQPCS09) to create feature-specific files. For a detailed description about how to run these jobs, see Configuring your environment for BIRT or Configuring your environment for Tivoli Common Reporting.
- If the DB2 is installed on the z/OS system, setup the database for reporting on the Dynamic Workload Console and create the dedicated tables.
- Distributed system with the DB2 database installed
- If the DB2 is installed on a distributed system, setup the database for reporting on the Dynamic Workload Console and create the dedicated tables.
The following sections provide detailed information about the reporting feature. They include setting up the environment and the database for running reports from both the Dynamic Workload Console and the command line interface. They also explain how you customize the security support to protect access to your historical run data using a RACF® fixed resource and sub-resource and an encryption utility for the password used when archiving data on DB2.
Before you can generate reports with BIRT, you need to complete the operations described in Configuring your environment for BIRT.