JCL

The JCL to produce any of the reports is shown in the following figure. This JCL is a single-step procedure in member DZTBTRAC in BBSAMP.

Related topic

Submitting-a-report-request

JCL to print a trace (DZTBTRAC)

------------------------------------------------------------------------
-------- Edit JCL and SUBMIT or save job in permanent data set. -------
------------------------------------------------------------------------
//RDHHVM   JOB (4110,1605B),'MATSON',REGION=0M,TIME=1440,
//         CLASS=T,MSGCLASS=X,NOTIFY=&SYSUID
//*
//*
//DZTBPRNT EXEC PGM=DZTBPRNT,REGION=0M
//STEPLIB DD   DSN=DOM.DMRMV92.BBLINK.BBLINK,DISP=SHR
//SYSPRINT DD   SYSOUT=*
//REPORT1 DD   SYSOUT=*
//SYSUDUMP DD   SYSOUT=*
//TRACIN01 DD   DISP=SHR,DSN=BMCTI.C3410286.SIDEB.TLDS.V02
//SYSIN    DD   *
REPORT REPORTID=REPORT1,
     DATE=25MAR2009,
     TIME=1459,
     LTRAC=YES,
     STRAC=(NO),
     DTRAC=NO,
     POPUP=(NO),
     TSTAT=ALL,
     WIDTH=WIDE,
     LINECNT=66,
     HEADING=YES,
     MAXPAGES=0,
     NEWPAGE=NO
/*
//*-- FORMATTING OPTIONS ---------------
//*     WIDTH=N|NARROW|W|WIDE
//*     LINECNT=NNN
//*     HEADING=YES|NO
//*     MAXPAGES=NNNNNN
//*     NEWPAGE=TRAN|EVENT|FIRSTEVENT|NO
//*-- REPORT OPTIONS -------------------
//*     LTRAC=NO|YES|CORRID
//*         (TO LIST ONE LINE PER THREAD, AND OPTIONALLY,
//*          SHOW CORRELATION ID INSTEAD OF CONNECTION NAME)
//*     STRAC=NO|SUMMARY|ALL|ACCTG|DDF|SQL|SQLPOPUP|SCAN|IOLOCK
//*         |SORTS|ELAPSED|BPOOL|PRLLIO|ENV|SQLCOUNTS|LOCKS
//*         |PKG|PKGPOPUP|SPAS
//*         (=SUMMARY TO PRINT THE FIRST SUMMARY SECTION)
//*         (=ACCTG   TO PRINT ALL SUMMARY TRACE SECTIONS)
//*         (=ALL OR =X,X,X TO PRINT ALL SUMMARY SECTIONS PLUS DETAIL
//*           EVENT SUMMARIES)
//*         (ONLY STRAC=SUMMARY CAN BE PRODUCED CONCURRENTLY WITH DTRAC
//*         (STRAC=ALL CAN BE SPECIFIED IN ANOTHER 'REPORT=')
//*       SORTSQL=PGM|ST|CO|AE|%E|AC|%C|SR|PI|PD|PW|PR|
//*               COP|%EP|%CP|SRP|PIP|PDP|PWP|PRP
//*         (TO SORT SQL SUMMARY AND POP-UPS BY COLUMN VALUE)
//*       SORTSCAN=DA|IS|IP|IR|DS|DP|DR|WS|WP|WR
//*         (TO SORT DATABASE SUMMARY BY COLUMN VALUE)
//*       SORTIOLOCK=DP|LM|LS|LT|SR|SW|SE|SA|AR|AP
//*         (TO SORT DATABASE LOCK AND I/O SUMMARY BY COLUMN VALUE)
//*     DTRAC=NO|YES|SQLERR
//*         (TO PRINT DETAIL EVENTS)
//*       LEVEL=2|1|3
//*         (LEVEL 1 SHOWS ONLY SQL, 3 SHOWS ALL EVENTS)
//*       POPUP=NO|ALL|SQL

JCL to print a trace (DZTBTRAC) (cont.)

                                           //*         (PRINT POPUPS FOR ALL EVENTS OR ONLY SQL EVENTS)
//*     TSTAT=NO|SUMMARY|ALL
//*         (STATISTICS SUMMARY OR ALSO INCLUDE DETAIL SCANS,I/O,LOCKS)
//*     TSUM=A|C|L|P|R|T
//*         (TO SELECT BY AUTHID, CONNECT, LOCATION, PLAN,
//*          CORRELATION, TIME)
//*       INTERVAL|INVTL|I=NM|NH
//*         (TO SPECIFY SUMMARY INTERVAL FOR TSUMT)
//*       GRAPH=NO|AVG|TOT
//*       SORTTSUM=AU|CO|PL|IS|ISD|EC|AE|AC|A#|AG|
//*                TE|TC|T#|TG
//*
//*       XX XN PROVIDES REPORTS BY DATABASE/TABLESPACE PLUS ANOTHER
//*           SUMMARY KEY (TO DETERMINE WHERE THE ACTIVITY AGAINST THE
//*           TABLE SPACES IS ORIGINATING).
//*
//*           NX PROVIDES REPORTS BY A SUMMARY KEY PLUS
//*           DATABASE/TABLESPACE
//*          (TO DETERMINE WHICH TABLE SPACES ARE BEING ACCESSED FROM
//*           THAT SOURCE).
//*
//*           SUPPO000070
//*                //*           SUMMARY KEY (TO DETERMINE WHERE THE ACT
//*           XA - 000071
//*           XC - //*           TABLE SPACE IS ORIGINATING).
//*           XF - 000072
//*           XK - //*
//*           XL - 000073
//*           XP - //*           NX PROVIDES REPORTS BY A SUMMARY KEY PL
//*           XT - 000074
//*                //*           DATABASE/TABLESPACE

Options that are used in this JCL statement are listed in the the following figure.

JCL statements to print a trace (DZTBTRAC)

Statement	Description
PRINT	Specifies the name of the program as PGM=DZTBPRNT and the region required to run the program This program supports a GMWK option in the PARM field, for example: PGM=DZTBPRNT,PARM='GMWK=128K' This option is used to increase the size of the summary work area which is required for processing trace data sets that contain a very large number of threads. This option increases the summary work area for all services (LTRAC, STRAC, and so on). The syntax rules for GMWK are similar to those for the MVS JCL REGION parameter. The size that is specified should be greater than 128KB. Storage acquired with this option is below the 16MB line and is limited by the largest private area that is available in the MVS system. When the GMWK option is used, the job’s REGION size might need to be adjusted accordingly. A general guideline for the size of GMWK is GMWK = 1700+(72 x number of unique threads summarized) If multiple report requests are executed in a single job step, one summary work area is acquired for each report. If the summary work area size is too large, any region size available can be exceeded very quickly.
STEPLIB DD	Defines the program library containing the DZTBPRNT load module
SYSPRINT DD	Defines the data set for printing all input statements and program messages Important The SYSPRINT DD statement must exist. If it is not found, a WTO is issued and the run is terminated.
SYSUDUMP DD	Defines the dump data set for problem determination
STD1	Defines the ddname for the default report
TRACINxx DD	Defines one or more trace log data sets (TLDSs) as input for trace data formatting If TRACINxx is defined, TRACEDIR, SMFIN, ARCIN, and GTFIN are ignored. This DD must refer to a VSAM trace data set (a TLDS not archived to tape), written by the online trace. Multiple TLDS data sets can be processed by specifying each in a DD statement with a ddname of TRACINxx, where xx is any valid set of characters. Each of the TLDSs is processed in the order it exists in the job stream.
TRACEDIR DD	Designates a trace directory data set If no TRACINxx DD statement is found, the TRACEDIR DD statement is processed. The TRACEID keyword is required. All trace data sets produced with this trace ID are eligible for processing by reporting. Important BMC Software recommends (but does not require), that TARGET, DATE, and TIME keywords further restrict which data sets are to be accessed; only those TLDSs which meet the target, date, and time criteria specified by one or more of the report requests are allocated.
SMFIN DD	Defines an unloaded SMF data set (or multiple concatenated data sets) containing Db2 accounting records as input for trace data formatting TRACIN and TRACEDIR must be dummied or NULLFILE. If SMFIN is defined, GTFIN is ignored.
GTFIN DD	Defines a GTF data set (or multiple concatenated data sets) containing Db2 accounting records as input for trace data formatting TRACIN, TRACEDIR, and SMFIN must be dummied or NULLFILE.
ARCIN DD	Defines an archived TLDS. TRACIN, TRACEDIR, SMFIN, and GTFIN must be dummied or NULLFILE Important If none of the five input DD options are defined, trace information is obtained from the active SMF data set.
REPTDD1	Defines the ddname for a report request The report request in the SYSIN stream defines the ddname of the output. There is no restriction on these ddnames other than uniqueness; they cannot duplicate other reserved ddnames. Important If the ddname specified for a report is missing, a diagnostic is written to SYSPRINT and the report is not produced.
SYSIN DD	Defines the input data set containing the report definitions Important All input data is entered through the SYSIN DD statement. If the SYSIN DD statement is missing, DUMMYed, or empty, the default report selection is used. (See Default-report-request).

Individual control statements specify how to read the input data set for each requested report and how to format the output.

JCL

On this page