Table of Contents
This section describes the LOGGER utility program, which enables a user to obtain reports that aid in the analysis of system performance and utilization. LOGGER also serves as a basis for the installation's billing system. The following are two important features of this log analysis program:
-
LOGGER generates a wide variety of reports, depending on individual installation requirements.
-
LOGGER combines data over various time intervals in order to generate long-term reports.
LOGGER accepts a set of report-specification commands from the user and interprets these specifications. These commands can specify information such as which data from each log file is to be included in the report, sorting by a particular data item, and data items to be used as control breaks. Usually, a set of report specifications consists of only six or seven commands. Therefore, the setup time involved in running LOGGER is minimal. If an installation has several different reports that it periodically wishes to obtain, the reports can be kept in one disk file. At run time, LOGGER reads the appropriate report specifications from this file.
Original data for LOGGER is stored in either the current log file or in one or more of the system logs created with the TL (Transfer Log) system command. LOGGER can also generate reports from files that it saves each time it is run, thereby avoiding the need to load large numbers of system log files in order to generate weekly or monthly reports.
LOGGER accesses both the SUMLOG and the Security Log. Nonprivileged users have limited access to records in the Security Log. They do not see the BOJ/BOT entries for privileged programs run under other usercodes, or any security violation records. Refer to the material under “Finding Missing Log Entries” in Section 16, “LOGANALYZER.” Most of the records used by LOGGER are likely to reside in the SUMLOG. References to SUMLOG in this section generally include both files.
When run, LOGGER can be instructed to obtain the data necessary for a specified report from one of four sources:
-
SYSTEM/SUMLOG. Refer to the System Log Programming Reference Manual for more information about this file.
-
SUMLOG files for either one date or a range of dates.
-
Files generated and saved from a previous run of LOGGER.
-
The disk resource control (DRC) system resource usage contained in the USERDATAFILE.
Each time LOGGER is run using SUMLOG files as the source, it creates files titled JOBSUMMARY/<mmddyyyy> and STATISTICS/<mmddyyyy> and, optionally, a file titled FILEIODATA/<mmddyyyy>. These files contain the saved data referred to previously along with the information needed to generate additional reports. Subsequently, LOGGER can be run with specifications to generate a report from one of these files or from files covering a range of dates.
Thus, long-term reports can be generated without having all of the original log files present. The saved files are much smaller than the original log files. For example, LOGGER could be run each day of the week and the log files removed. At the end of the week, LOGGER could also be used to generate a weekly report using the files that it created daily.
LOGGER can generate detailed and summary reports. A detailed report consists of one line for each record in the file; a summary report consists of one line for a particular group of records.
