A REPORT command indicates to LOGGER that it is to read a set of report specifications. Refer to “REPORT Command” for more information.
If an integer is present in the REPORT command, the report is located in the LOGREPORTS file, and the integer is the identifying number of the report. Report-specification commands are read until an END command is found, at which time reading of input records is resumed. If no integer is present in the REPORT command, the report-specification commands are assumed to be on input records immediately following the REPORT command. Commands are scanned up to column 72. Columns 73 through the end can be used for sequence numbers or comments.
A LOGREPORTS file can contain as many report specifications as are needed. Each command has an identifying number associated with it.
In the following example, the LOGREPORTS file contains only two reports. The records containing a number sign (#) as the first character are the report identification records, and the number following the number sign is the identifying number of the report that follows it.
|
Record Number |
Contents |
|---|---|
|
1 |
#1 |
|
2 |
SOURCE FILE IS JOBSUMMARY |
|
3 |
OUTPUT ITEMS ARE NAME, USERCODE, STARTTIME |
|
4 |
PAGE SIZE IS 57 |
|
5 |
HEADING IS "SYSTEM USAGE REPORT" |
|
6 |
END |
|
7 |
#2 |
|
8 |
SOURCE FILE IS STATISTICS |
|
9 |
OUTPUT ITEMS ARE TIME, TASKS, JOBS, DISK, PACK, |
|
10 |
BREAK ON DATE |
|
11 |
SORT BY DATE, TIME |
|
12 |
END |
LOGGER does not provide facilities for updating the LOGREPORTS file; however, it can be updated using CANDE. The file can also be maintained as a card deck and put on disk by using the WFL DECK statement. Refer to the Work Flow Language (WFL) Programming Reference Manual for information about the DECK statement.
