Writer instructions | |
---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines |
Print with a batch utility job
You can specify one or more trace log data sets in a series of DD statements with the ddnames in the form TRACINxx.
Only trace log data sets can be specified in this manner. To specify archived trace log data sets, use the DSN in the ARCIN DD statement.
If you do not know the exact names of the trace data sets, you can use the TRACEID keyword to specify which trace is to be printed. In this case, you must also use the TRACEDIR DD statement to specify the trace directory data set. It is recommended but not required that you use the TARGET, DATE, and TIME keywords to further qualify which trace data sets are to be selected.
You can use the batch utility job WATBTRAC to print history trace data offline. To do so, you must modify and then submit the JCL described in this section. The skeleton JCL to print trace data sets is a single-step procedure located in BBSAMP member WATBTRAC.
The individual JCL control statements specify how to read the input data set for each of the requested traces and how to format the output. The statements and control card input keywords are described in the following tables:
WATBTRAC JCL control statements
Statement | Description |
---|---|
WATBPRNT program and region required to run the program The GMWK option in the PARM field is used to increase the size of the summary work area needed to process trace data sets that contain a very large number of transactions. The 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 operating system JCL REGION parameter. The size specified should be greater than 128K. Storage acquired with the option is below the 16M line and is limited by the largest private area available in the operating system. When the GMWK option is used, the job's REGION size may need to be adjusted accordingly. Use the following general guideline to determine the size of GMWK: GMWK = 1700 + (72 × number of unique transactions summarized) | |
STEPLIB DD | Program library containing the WATBPRNT load module |
SYSPRINT DD | Data set for printing all input statements and program messages The SYSPRINT DD statement must exist. If it is not found, a WTO is issued and the run is terminated. |
SYSUDUMP DD | Dump data set for problem determination |
STD1 DD | DDname for the default report |
TRACINxx DD | One or more trace log data sets (TLDSs) as input for trace data formatting If TRACINNxx is defined, TRACEDIR and ARCIN 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 if you specify each one 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 | Trace directory data set If no TRACINxx DD statement is found, the TRACEDIR DD statement is processed. If you specify TRACEDIR DD, you must use the TRACEID keyword. All trace data sets defined with this trace ID are eligible for printing. |
ARCIN DD | Archived TLDS TRACIN and TRACEDIR must be dummied or you must specify NULLFILE. |
REPORT1 | DDname for the trace print output |
SYSIN DD | Input data set containing the control card specifying the amount of detail to print |
Control card print request keywords (listed alphabetically)
Keyword and Operand | Description |
---|---|
AB | ABEND | The keyword selects only transactions with a nonzero system or user completion code. |
CLASS=(nnn,...nnn) | The keyword selects only transactions from the specified class or classes. Valid transaction classes are 1 to 999. To specify multiple classes, separate each value with a comma. The specification can extend to multiple lines. For example: CLASS=(1,2,3,4,5, 6,7) |
DATABASE=(dbName,... dbName) | The variable represents a database name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by database name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: DATABASE=(ABC*,D+F*,GHIJK, DB6,DB7) |
DATE=ddmmmyyyy| ddmmmyyyy-ddmmmyyyy | The date value is used to select a date range or starting date from the input. The input can be a single date, which defines a starting day, or a date range, which defines starting and ending dates to process. An asterisk is used to specify current date. To select all entries from yesterday, specify: DATE=*_1 The underscore is used instead of a hyphen, since a hyphen is already used for the date range format. If you were to specify DATE=*-1, the date would be interpreted as a range from the current date to day 1 (which is invalid). To process only one day, specify the date as both the starting day of a date range, such as: 15APR2007-15APR2007 The default is to select all records. |
D | DAY=nn | nn-nn | The variable represents a day or a range of days as a relative number from the date of the first trace entry (first date is 1, up to a maximum of 99) in the trace buffer or trace log data set. The keyword selects a subset of the entries by a day or range of days. If there is only one day's data, the END TIME timestamp is hh:mm:ss. If the trace buffer or trace log data set contains more than one day's data, END TIME changes to dd-hh:mm:ss, where dd is the day number relative to the date of the first record in the trace buffer or trace log data set. If DAY is not specified, but TIME is, the default is the day of the most current record in the buffer or trace log data set. |
DB2C | DB2CNT<nnnnnn | >nnnnnn | =nnnnnn | The variable represents the number of DB2 database calls. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by DB2 database call counts. You can specify the variable as a single numeric value or as a range. For example: DB2CNT=100, DB2CNT>100, DB2CNT<100, or DB2CNT=1-100 |
DB2PLAN=(planName,...planName) | The variable represents a DB2 plan name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by DB2 plan name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: DB2PLN=(ABC*,D+F*,GHIJK, DP6,DP7) |
DB2T | DB2TIME<nnnnnn | >nnnnnn | =nnnnnn | The variable represents CPU time in milliseconds. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by DB2 elapsed time. You can specify the variable as a single numeric value or as a range. For example: DB2TIME=200, DB2TIME>200, DB2TIME<200, or DB2TIME=1-200 |
DLIC | DLICNT<nnnnnn | >nnnnnn | =nnnnnn | The variable represents number of DL/I database calls. The parameter selects a subset of the trace entries in the online trace storage buffer or trace log data set by DL/I database call counts. You can specify the variable as a single numeric value or as a range. For example: DLICNT=10, DLICNT>10, DLICNT<10, or DLICNT=1-10 |
DLIT | DLITIME<nnnnnn | >nnnnnn | =nnnnnn | The variable represents DL/I CPU time in milliseconds. The parameter selects a subset of the trace entries in the online trace storage buffer or trace log data set by DL/I elapsed time. You can specify the variable as a single numeric value or as a range. For example: DLITIME=50, DLITIME>50, DLITIME<50, or DLITIME=1-50 |
DTRAC=YES | NO | The DTRAC keyword requests that a one-line entry be printed for each detail trace event. For ease of associating the detail data with a transaction, it is recommended that you also request either LTRAC or STRAC. The default is DTRAC=YES. |
EL | ELAPSED<nnnnnn | >nnnnnn | =nnnnnn | The variable represents elapsed time in milliseconds. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by elapsed time. You can specify the variable as a single numeric value or as a range. For example: ELAPSED=3000, ELAPSED>3000, ELAPSED<3000, or ELAPSED=1-3000. |
IOC | IOCNT<nnnnnn | >nnnnnn | =nnnnnn | The variable represents number of total I/Os (READs and WRITEs). The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by total I/O count. You can specify the variable as a single numeric value or as a range. For example: |
LEVEL=1 | 2 | 3 | 4 | The keyword specifies the data that will be printed:
|
LTRAC=YES | NO | The LTRAC keyword is used to request the LTRAC one-line entry for each transaction. If LTRAC is specified in conjunction with STRAC or DTRAC, each transaction starts with the LTRAC line followed by the other displays as requested. The default is LTRAC=YES. |
MSW | The keyword selects only transactions that are a result of a message switch. |
OTMAMEM=(tjName,... tjName) | The variable represents a TMEMBER or IMS Connect job name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by TMEMBER or JOB name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: OTMAMEM=(ABC*,D+F*,GHIJK, TM6,J7) |
PR | PROG | PROGRAM=(pName,... pName) | The variable represents a program name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by program name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: PROGRAM=(ABC*,D+F*,GHIJK, P6,P7) |
PSB=(psbName,... psbName) | The variable represents a PSB name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by PSB name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: PSB=(ABC*,D+F*,GHIJK, PSB6,PSB7) |
REPORTID=name | Each trace print must have a unique identification provided by REPORTID. This is the only required keyword. REPORTID is also used as the ddname of the output data set. The value can be up to eight characters long, and special characters are allowed. |
REGION=(rgnName,... rgnName) | The variable represents a region name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by region name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: REGION=(ABC*,D+F*,GHIJK, RGN6,RGN7) |
RE | RESPONSE<nnnnnn | >nnnnnn | =nnnnnn | The variable represents response time in milliseconds. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by response time. You can specify the variable as a single numeric value or as a range. For example: RESPONSE=3000, RESPONSE>3000, RESPONSE<3000, or RESPONSE=1-3000 |
RGNID=(nnn,...nnn) | The keyword selects only transactions from the specified region ID or IDs. Valid region IDs are 1 to 999. To specify multiple region IDs, separate each value with a comma. The specification can extend to multiple lines. For example: RGNID=(1,2,3,4,5, 6,7) |
STRAC=YES | NO | The STRAC keyword is used to request the STRAC transaction summary display. STRAC=NO suppresses the STRAC displays. STRAC=YES (the default) requests only the first section of the STRAC display. These requests can be combined with any of the DTRAC requests. |
TERM=(ltcName,... ltcName) | The variable represents an LTERM name, Tpipe name, or CICS terminal ID. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by LTERM name, tpipe name, or CICS terminal ID. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: TERM=(ABC*,D+F*,GHIJK,CICST10 LTERM6,TPIPE7) Additionally, you can use the following keywords instead of specific or qualified names:
|
T|TIME=hhmm | hhmm-hhmm | The variable represents a start time or time period. The keyword selects a subset of the trace entries in the online trace buffer or trace log data set by a start time or time period. When the start time is higher than the end time (for example, TIME=2000-0300), 24 hours are added. |
TITLE1=title | The title value is centered on the first line of each page of the report. The value can be up to 60 characters long. If the TITLE1 keyword is not included, the title is left blank on the report. |
TITLE2=title | The secondary title is centered on the second line of each page of the report. The value can be up to 60 characters long. If the TITLE2 keyword is not included, the secondary title is taken from the title specified when the trace was created. |
TRACEID=id | BLANK | This keyword defines the ID of the trace that is to be matched in a search through the trace directory. All TLDS data sets that meet this requirement, plus any TARGET, TIME, and DATE requirements, are dynamically allocated and processed. To define a trace ID of blank, specify: TRACEID=BLANK The DD statement TRACEDIR must be present before this keyword is processed. If the TRACEDIR DD statement is not present, the TRACEID keyword is ignored. |
TRAN=(trnName,... trnName) | The variable represents a transaction name. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by transaction name. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: TRAN=(ABC*,D+F*,GHIJK, TRN6,TRN7) |
TY | TYPE=xxx | The variable represents a region type. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by region type. Replace the variable with one of the following region types:
|
TRANTYPE=xxx | The variable represents a transaction type. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by transaction type. Replace the variable with one of the following transaction types:
|
US | USER=(id,... id) | The variable represents a user or LTERM ID. The keyword selects a subset of the trace entries in the online trace storage buffer or trace log data set by user or LTERM. You can use wildcard characters to qualify variables. The + character replaces any single character, and the * character replaces any number of characters at the end of the variable. To specify multiple variables, separate each variable with a comma. The specification can extend to multiple lines. For example: USER=(ABC*,D+F*,GHIJK, USER6,USER7) |
hh:mm:ss. th.