|
|
|
To produce the same report as Example 2, but only display the summary lines, remove the 1 in position 51 of the SORT statement.
However, some data elements are not logically cumulative and therefore cannot be displayed on a summary line. For this reason, we will remove job name and CPU ID from the DISPLAY statement in this example.
Because this is a summary line-only report, we do not need descriptive headers displayed at the beginning of each change in the sort control. The descriptions are printed on each summary line because DE ID 02 is specified on the DISPLAY statement. So on the SORT statement in sort field one, remove the flag for descriptive headers.
The control statements for the third example are:
position 1 2 3 4 5 8 1........0.........0.........0.........0.........0... ...0 SELECT 1 3 3HEADER CHARGES BASED ON READER QUEUE TIME 3SORT 00101 2 01608 3DISPLAY 002214266262529344 3GROUP 0281 R1956 3GROUPC 1T 3GROUPC 2000000 000030 A 3GROUPC 2000031 000200 B 3GROUPC 2000201 999999 C 3RATE A0500 100 3RATE B1000 100 3RATE C1000 200 3DESCRIPT1A LESS THAN 30 SEC. 3DESCRIPT1B 30 SEC. - 2 MINUTES 3DESCRIPT1C GREATER THAN 2 MIN.
The output report is:
CHARGES BASED ON READER QUEUE TIME BEGIN DATE - 02/05/98 RUN DATE - 02/28/98 END DATE - 02/05/98 PAGE 1 JOB CPU RDR QUE PROCESS PROCESS DESCRIPTION NBR TIME TIME-AVG TIME CHARGE LESS THAN 30 SEC. 496 02:37:30 00:00:08 2.62492 $1,315.09 30 SEC. - 2 MINUTES 187 00:45:00 00:00:42 .74996 $422.28 GREATER THAN 2 MIN. 2 00:00:34 00:02:08 .00931 $4.97 686 03:23:04 00:02:58 3.38429 $1,742.34
Summarization of this type is often used for invoices, and management reports. If the input data is kept, you can always rerun this report as a detail report to illustrate how these totals are calculated.
The remaining chapters of this guide explain in detail all the functions of the various control statements and how to manage the input and output data files.
| Copyright © 2012 CA. All rights reserved. |
|