The reporting feature allows you to collect historical workload data and archiving it. This white paper provides you with the instructions about how to set up the environment to use reporting.
Complete the following procedure after ensuring that the prerequisites are all met.
To use the archiving capabilities and generate reports, you must have added the fault-tolerant end-to-end feature using SMP/E on your IBM Workload Scheduler for z/OS installation.
If you migrated to the current version of IBM Workload Scheduler for z/OS from a previous release, ensure that you migrated DB2 reporting data. For detailed information about migrating DB2, see IBM Workload Scheduler for z/OS: Planning and Installation.
Set up the JZOS environment by identifying the name of the JZOS Batch Launcher module located in /usr/lpp/java/J7.1_64/mvstools and copying the JZOS Batch Launcher module in the PDSE library. You will be required to specify the library and module names when running EQQJOBS.
1. Run EQQJOBS to create or modify the following skeletons:
Historical data archiver.
Daily plan extend skeleton.
Daily plan replan skeleton.
and the following samples:
To set up the DB2 database in the z/OS environment.
To set up the working directory.
To allocate VSAM and GDG files.
To set DBOPT parameters.
To encrypt the password specified in the DBOPT statement.
To set server parameters.
To set batch options, if controller and tracker run in the same address space.
To set batch options, if controller and tracker run in separate address spaces.
2. Run EQQPCS09 to allocate a VSAM data set, used to archive data, and a Generation Data Group (GDG) root with the following characteristics:
Specifies that only the oldest GDG generation is to be deleted and uncataloged when the generation number reaches the maximum limit.
Specifies that all the control information, related to a GDG generation, is to be deleted when the system deletes that generation.
Specify how many versions will be kept in the generation data group.
Run EQQPCS08 to customize the working directory.
If the DB2 database is installed on a z/OS system, edit the env.profile on the working directory to uncomment the statements marked as follows:
If DB2 is on z/OS, customize and uncomment the following line.
- According to the system where DB2 is installed, perform one of the following steps:
If DB2 is on a distributed environment, create the tables where data is archived by running the following script:
For example, on Windows run the following command:
dbsetup dbName dbTableSpace dbDataDir port db2Admin db2AdminPwd
To save the output of the script, run the command as follows:
dbsetup.bat TWS TWSDATA TWSDIR 50000 db2admin db2admin > output.txt
The output is saved in a file named output.txt, where you can check if the
table definition was successful.
If DB2 is on a z/OS environment, create the tables where data is archived
by running the EQQINIRE sample.
Customize the parameter library as follows:
In the BATCHOPT statement, set JRUNHISTORY(YES). This parameter is read by
the daily plan.
In the DBOPT statement, set the parameters to connect to the database as follows:
DBURL(jdbc:db2://db2_url) ensure that jdbc:db2 is in lowercase characters
Note: You must specify a dbuser with read privileges on DB2.
In the SERVOPTS statement, set DBOPTPRM(DBOPT).
Populating the database with historical data
To populate DB2 with historical data, complete the following procedure:
- Run a daily planning EXTEND or REPLAN. during this step, the old current plan is copied into a Generation Data Grouping (GDG) data set. (The GDG data set is identified in the daily planning EXTEND or REPLAN batch job by the EQQOCPBK ddname.)
- Archive the old current plan. From the main menu, select option 3 (DAILY PLANNING) to display the following panel:
EQQDPLNP ----------------- PRODUCING TWSz DAILY PLANS -------------------------
Select one of the following :
1 REPLAN - Replan current planning period
2 EXTEND - Extend the current planning period
3 TRIAL - Produce a trial plan
4 PRINT CURRENT - Print statistics for current planning period
5 SYMPHONY RENEW - Create Symphony file starting from Current Plan
6 ARCHIVE - Archive old current plans
- Select option 6 (ARCHIVE) to display the GENERATING A JCL FOR A BATCH JOB panel.
- Press Enter to obtain a JCL tailored according to the EQQDBARS skeleton JCL generated by the EQQJOBS dialog.
Important: Before submitting the JCL, specify at least 128 MB as region value.
Note: Only occurrences that completed automatically or ended in error with the RECOVERED BY CONDITION field set to Yes are archived.
Viewing data generated by reports
The Dynamic Workload Console provides you with four kinds of reports:
Job Run Statistics
Shows, based on the criteria that you set, information about one or more jobs and runtime statistics for each job.
Job Run History
Shows historical data about jobs that already ran. This report is usually requested for a specific time frame.
Workstation Workload Summary
Collects data about the workload on the workstations and calculates the number of jobs that ran on a specific workstation in a specific interval of time.
Workstation Workload Runtimes
Provides information about the actual jobs that ran on a specific workstation, along with their actual start times and duration.