Report control statements for PRSCLNDR
You can use report control statements to request one report, any combination of reports, or all calendar reports in a single PRSCLNDR execution.
No specific input sequence is required and there are no default reports.
There are positional and keyword control statements.
Positional statements
The statement position defines the type of report and specifies the month (or months) and the year to be reported. The IRUF input must contain the month and year data specified in the control statements.
The following table shows positional statement syntax for PRSCLNDR:
Position | Input |
|---|---|
01-03 | Program code: CAL |
04-07 | Report code:
|
08 | Comma or blank |
09-12 | Month and year selection field 1
When a specific month is selected, additional months and month ranges can be specified in subsequent statement fields. |
13 | Comma, blank, or dash (dash used between months in a range) |
14-17 | Month and year selection field 2 (same format at selection field 1) |
18 | Comma, blank, or dash (dash used between months in a range) |
19-22 | Month and year selection field 3 (same format at selection field 1) |
23 | Comma, blank, or dash (dash used between months in a range) |
24-27 | Month and year selection field 4 (same format at selection field 1) |
28 | Comma, blank, or dash (dash used between months in a range) |
29-32 | Month and year selection field 5 (same format at selection field 1) |
33 | Comma, blank, or dash (dash used between months in a range) |
34-37 | Month and year selection field 6 (same format at selection field 1) |
38 | Comma, blank, or dash (dash used between months in a range) |
39-42 | Month and year selection field 7 (same format at selection field 1) |
43 | Comma, blank, or dash (dash used between months in a range) |
44-47 | Month and year selection field 8 (same format at selection field 1) |
48 | Comma, blank, or dash (dash used between months in a range) |
49-52 | Month and year selection field 9 (same format at selection field 1) |
53 | Comma, blank, or dash (dash used between months in a range) |
54-57 | Month and year selection field 10 (same format at selection field 1) |
58 | Comma, blank, or dash (dash used between months in a range) |
59-62 | Month and year selection field 11 (same format at selection field 1) |
63 | Comma, blank, or dash (dash used between months in a range) |
64-67 | Month and year selection field 12 (same format at selection field 1) |
Keyword statement
The following table shows keyword statement syntax for PRSCLNDR:
Position | Input |
|---|---|
01-04 | DBT= | TPI= DBT specifies whether DBCTL threads are included in the calendar reports. TPI specifies whether TPI transactions are included in the calendar reports. |
05-07 | YES | NO YES specifies to include DBCTL threads or TPI transactions from the calendar reports (the default) |
If DBT=YES is specified to include DBCTL threads, you should keep the following considerations in mind when you examine the reports for historical trends:
Input queue time
Zero is used for DBCTL threads, which tends to lower the averages for non-DBCTL transactions if DBCTL threads are included.
Elapsed time
If you have conversational CICS transactions, they tend to raise the average elapsed time and response time.
Response time
If you generated the IRUF with the response option, the response time for DBCTL threads is zero, which tends to lower the averages for non-DBCTL transaction response time if the DBCTL threads are included.
Terminal-related data
Message queue and character counts are zero for DBCTL transactions, which lowers the averages for non-DBCTL transactions in these reports if DBCTL threads are included.
CPU time
CPU time for DBCTL threads is the time spent processing the DL/I requests, which tends to lower the CPU time-related averages for non-DBCTL transactions if DBCTL transactions are included.
System Availability Calendar Report
Active DBCTL threads are included in the #MPP UP field.
If TPI=YES is specified to include TPI transactions, TPI transactions are similar to DBCTL threads in that they have no input queue time, response time, or terminal-related data.
Related topic