Chapter 6. Integrating Tivoli Decision Support for OS/390 235
6.5 Running the OPC reports
Now that we have successfully collected some TWS for z/OS data into our Tivoli
Decision Support for OS/390 database, we can produce some reports. This
section demonstrates how to produce reports and discusses some of the
limitations. It also shows how to overcome these limitations using TWS for z/OS.
6.5.1 Creating the report batch JCL
First, we need to obtain the batch JCL that is required. You can use the sample
JCL that is provided in <hlq>.SDRLCNTL(DRLJBATR). However, that JCL
requires that you code all of the data sets correctly. So, in our scenario, we let
the product do this for us in the following way:
1. Select option 1 (Reports) from the Tivoli Decision Support for OS390 Primary
Menu panel and press Enter.
2. Select a report and press F10 (Actions). We choose the OPC09 report.
3. Tab across to the Batch menu and press Enter.
4. Select option 2 (Invoke batch...) and press Enter.
5. Enter the report variables as requested and press Enter. Example 6-9 shows
our selection.
Example 6-9 Entering report data selection values
Batch Reports Data Selection Row 1 to 3 of 3
Type information. Then press Enter to edit JCL.
Report ID . : OPC09
Variable Value Oper Req
DATE '2005-02-01' > = Yes
PERIOD_NAME 'PRIME' > = No
OPC_SYSTEM_ID '01' > = Yes
***************************** Bottom of data ******************************
6. We can now copy the JCL to a data set. Figure 6-18 on page 236 shows the
BATCHJCL member in our local library.
After pressing Enter, the column information in the top right-hand corner of
the panel changes to Member BATCHJCL created.
Important: The quotes are required to prevent an error when running the job
later.
236 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
Figure 6-18 Creating report batch JCL
7. Either press F3 (Exit) or F12 (Cancel) to go back to the Reports panel.
6.5.2 Running the batch job
Adding a valid job card and submitting the JCL that you just created results in a
JCL error because the ADMDEFS DD statement is coded with DSN= . So, you
comment out that statement and submit the job again. Then, a report is
produced. The destination of the actual report output is defined by the coding of
the DSQPRINT DD statement. Example 6-10 on page 237 shows our JCL.
Note: To demonstrate the reports, we collected some historic tracklog data
from another installation. It was a week’s worth of data that covered the dates
from January 31 to February 6. Thus, we used that date in our example.
Chapter 6. Integrating Tivoli Decision Support for OS/390 237
Example 6-10 Report JCL as a batch job
//TWSRES3R JOB (ACCT#),'TWS REPORT09',MSGLEVEL=(1,1),
// CLASS=A,MSGCLASS=X,TIME=1440,REGION=0M
//***************************************************************
/*JOBPARM LINES=999999,CARDS=999999,SYSAFF=SC64
//***************************************************************
//**********************************************************
//* BATCH REPORTING *
//**********************************************************
//EPDMBAT EXEC PGM=IKJEFT01,DYNAMNBR=25
//STEPLIB DD DISP=SHR,DSN=DRL.SDRLLOAD
// DD DISP=SHR,DSN=QMF810.SDSQLOAD
// DD DISP=SHR,DSN=DB8Q8.SDSNLOAD
// DD DISP=SHR,DSN=GDDM.SADMMOD
//SYSPROC DD DISP=SHR,DSN=DRL.SDRLEXEC
// DD DISP=SHR,DSN=QMF810.SDSQCLTE
// DD DISP=SHR,DSN=QMF810.SDSQEXCE
//SYSEXEC DD DISP=SHR,DSN=DRL.SDRLEXEC
// DD DISP=SHR,DSN=QMF810.SDSQCLTE
// DD DISP=SHR,DSN=QMF810.SDSQEXCE
//**********************************************************
//* MESSAGES *
//**********************************************************
//DRLOUT DD SYSOUT=*
//*
//**********************************************************
//* SAVED TABULAR AND GRAPHIC REPORTS TO *
//**********************************************************
//DRLREP DD DISP=SHR,DSN=DRL.LOCAL.REPORTS
//ADMGDF DD DISP=SHR,DSN=DRL.LOCAL.CHARTS
//*
//**********************************************************
//* PRINT REPORTS TO: *
//**********************************************************
//DSQPRINT DD SYSOUT=T,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)
//*
//**********************************************************
//* GDDM LIBRARIES *
//**********************************************************
//ADMGGMAP DD DISP=SHR,DSN=QMF810.SDSQMAPE
//ADMCFORM DD DISP=SHR,DSN=DRL.SDRLFENU
// DD DISP=SHR,DSN=QMF810.SDSQCHRT
//ADMSYMBL DD DISP=SHR,DSN=GDDM.SADMSYM
//*ADMDEFS DD DISP=SHR,DSN=
//DSQUCFRM DD DISP=SHR,DSN=DRL.LOCAL.ADMCFORM
//**********************************************************
//* QMF LIBRARIES *
//**********************************************************
238 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
//DSQDEBUG DD DUMMY
//DSQUDUMP DD DUMMY
//DSQPNLE DD DISP=SHR,DSN=QMF810.DSQPNLE
//DSQSPILL DD DSN=&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096)
//DSQEDIT DD DSN=&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE),
// DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029)
//DRLFORM DD DSN=TWSRES3.DRLFORM,UNIT=SYSDA,SPACE=(TRK,(5,5),RLSE),
// DCB=(RECFM=VB,LRECL=255,BLKSIZE=2600),DISP=(NEW,DELETE)
//*
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLEBATR +
SYSTEM=DB8Q +
SYSPREFIX=DRLSYS +
PREFIX=DRL +
QMF=YES +
GDDM=YES +
REPORT=+
OPC09 +
&DATE='''2005-02-01''' +
&PERIOD_NAME='''PRIME ''' +
&OPC_SYSTEM_ID='''01''' +
DIALLANG=1 +
PRODNAME=Tivoli Decision Support +
/*
This JCL is specific to the OPC09 report that was selected with the variables. To
run the same report with different variables, you need to update the SYSTSIN
DD statement before submitting the job again.
If you wanted to run a different report, you would need to change the SYSTSIN
DD statement accordingly. It is best to change this statement as described in
6.5.1, “Creating the report batch JCL” on page 235 to ensure that everything is
coded correctly.
Remember: If your system is part of a sysplex, you need to code the correct
SAFF= value on the JOBPARM statement.

Get Integrating IBM Tivoli Workload Scheduler with Tivoli Products now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.