SirTune report generation

Prior to version 7.7 of RKTools, SirTune reports can only be generated using a SOUL program invoking a call to the SirTuneReport method of the Dataset class, as implemented in the SIRTUNEREPORT SOUL program described in SirTune Report Generator configuration and SirTune reports.

As of RKTools 7.7, the RKWeb browser interface is equipped to invoke and display SIRTUNEREPORT results. Using RKWeb for SirTune reports requires the same set up of input and output files described on this page.

Report programs

The report generation portion of SirTune consists of two SOUL programs which are distributed in the RKTools SIRIUS file (prior to RKTools version 7.7) or the M204PROC file (as of RKTools 7.7).

The SOUL reporting programs of SirTune are:

SIRTUNEREPORT	The "outer" SirTune report program.
SHARED_REPORT	Report methods used by SIRTUNEREPORT.

To run SIRTUNEREPORT from a procedure file other than SIRIUS or M204PROC, move both these procedures to the new file, and update the single INCLUDE statement in SIRTUNEREPORT. A few UTABLE and environmental settings are executed at the top of SIRTUNEREPORT. These can be adjusted for performance or functional reasons at the client site.

Report files

SIRTUNEREPORT requires two input files, and it accepts an optional output file. These files, described below, may be specified as DD cards or ALLOCATE statements on the job running SIRTUNEREPORT:

TUNERPTI	Input cards that specify the SirTune reports and other run characteristics. This file may contain older style input, with REPORT, RANGE, RESOLUTION, and other statements, or it may contain newer-style input in XML format. If old-style card images are input, a subroutine in SIRTUNEREPORT converts them to XML. For detailed information about this input, see SirTune Report Generator configuration. TUNERPTI is a required file. The file format of TUNERPTI is not critical: Since input lines should be shorter than 80 characters, a fixed 80-character file works fine.
TUNERPTD	This is the input data to SIRTUNEREPORT. TUNERPTD is a required file. This is the same file as SIRTUNED in the SirTune data collection run. Sample data sets from multiple runs may be concatenated. In fact, sample data sets from multiple runs may even be concatenated sequentially into a single data set (with IEBGENER under MVS, or COPYFILE or an equivalent under CMS) and provided as a single data set to SIRTUNEREPORT. When multiple sample data sets are concatenated in any way, the DATASET statement (DATaset list) must be provided in TUNERPTI to have TUNERPTR use any but the first sample data set in the concatenation.
TUNERPTO	This is the output file for the SIRTUNEREPORT reports. The SOUL code is currently set to output 128 characters per line, so a fixed or fixed-block file with 132-character records is recommended. TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, CCAPRINT.

The names of these files are hard-coded in SIRTUNEREPORT, but they may be changed if you run SIRTUNEREPORT from another procedure file and decide to customize it. The names are chosen to differentiate them from the SIRTUNEx names used during SirTune data collection.

Report job

Generally, SIRTUNEREPORT is run as a standalone batch job, though it is perfectly acceptable, if perhaps a little resource-intensive, to dynamically allocate the TUNERPTx files and run it from inside an Online.

A basic TUNERPTR job under MVS would look like this:

//TUNE JOB (0,0),CLASS=A,MSGCLASS=X //TUNERPT EXEC PGM=BATCH204,REGION=4096K, // PARM='SYSOPT=134,LIBUFF=1000,LOBUFF=1000',TIME=250 //CCASTAT DD DSN=M204.CCASTAT,DISP=SHR //CCATEMP DD DSN=M204.TEMP1,DISP=SHR //CCAJRNL DD DSN=M204.CCAJRNL,DISP=SHR //SIRIUS DD DSN=ULSPF700.SIRIUS,DISP=SHR //TUNERPTI DD DSN=SIRTUNER.REPORT.INPUT,DISP=SHR //TUNERPTD DD DSN=SIRTUNER.DATA.INPUT,DISP=SHR //TUNERPTO DD DSN=SIRTUNER.REPORT.OUTPUT,DISP=SHR //CCAPRINT DD SYSOUT=*,OUTLIM=50000 //CCAIN DD * NFILES=5,NDCBS=5,NDIR=5,MAXBUF=50,NGROUP=5,NORQS=4, X LQTBL=4000,LSTBL=30000,LNTBL=1200,LVTBL=3000 LOGON me mepassword O SIRIUS INCLUDE SIRTUNEREPORT /* //

Notes:

• For RKTools 7.7 or higher, the SIRIUS file is replaced with the M204PROC file.
• For an Online job instead of batch, the same SirTune files are allocated: TUNERPTI (report input parameters), TUNERPTD (reporting data), and an optional TUNERPTO (output destination replacing the screen default). The OPEN and INCLUDE commands do not change.
• Under CMS, a similar Batch204 EXEC can be used to invoke SIRTUNEREPORT.

See also

• SirTune introduction
• SirTune data collection under MVS
• SirTune data collection under CMS
• SirTune data collection statements
• SirTune MODIFY and SMSG commands
• SirTune report generation
• SirTune reports
• SirTune user states
• SirTune and Model 204 quad types
• SirTune statement wildcards
• SirTune date processing