SirAud: Difference between revisions

Revision as of 23:00, 10 October 2016

SirAud reads a single journal file produced by Model 204 and it generates a set of reports, using statistics entries as well as other information in the journal. These reports are intended to provide an overview of the resource usage for one Model 204 run. Each report summarizes a different aspect of the run.

SirAud reports

A report is generated when a corresponding file is defined or when the report is requested by a SirAud program parameter. The sections on this page give the report names and a brief description of the report contents.

If a report is selected by specifying a SirAud program parameter (see ALLPR and NOPR), all reports are produced on the SYSPRINT file, and only there. Otherwise, the name of the report given in the section headings on this page is the same as the name of the DD statement (in MVS, or the FILEDEF command, in CMS) to which the report is written.

PERFREPT

This report summarizes system-level performance over each ACCTIM interval.

FILEREPT

This report summarizes the resource utilization of each Model 204 file. Files are reported in descending order by total disk I/O (DKRD+DKWR).

PROCREPT

This report summarizes the resource utilization of each Model 204 procedure. Procedures are reported by subsystem and file, in descending order by total CPU.

SUBREPT

This report summarizes the resource utilization of each Model 204 subsystem. Subsystems are reported in descending order by total CPU.

UTBLREPT

This report summarizes the current high water mark of each user-resettable server table on a subsystem basis. A set of "target" table settings is also presented. Subsystems are reported in descending order by the largest server size needed to run all of the subsystem procedures executed during the run. A separate line is produced for each procedure in the subsystem that has a table high water mark that is above the "target" value.

UTBLSUMM

This report summarizes the current high water mark of each user-resettable server table for each subsystem. Subsystems are reported in descending order by the largest server size needed to run all of its procedures executed during the run.

Additional SirAud files

JOURNAL

This is the input Model 204 journal file. :h2 id=syspr.SYSPRINT

Various information is written to this file; the following information is always written to SYSPRINT:

Various AUDnnn messages, which are explained in SirAud messages.
Identification of the Model 204 run that created the JOURNAL file.
A list of pertinent run-time parameters as specified in the Model 204 run's EXEC, user 0, and user n parameters.

Also, if any SirAud reports are specified as program parameters, reports are contained in the SYSPRINT file, and only there; see ALLPR and NOPR.

SYSIN

Prior to version 1.05 of SirAud, no SYSIN file contents were read by SirAud. As of version 1.05, all SirAud program parameters (SirAud parameters) may be specified on input records in the SYSIN dataset, which will be read and parsed under MVS and CMS.

You can specify multiple parameters on one SYSIN record, and you can specify multiple records, but you cannot specify a parameter on one record and "continue" its value(s) on another record.

The following simple example of SYSIN content shows valid SIRAUD parameter specifications:

FROM 04169 10:00 PERFRP TO 04170 12:00

SirAud topics

The SirAud documentation consists of the pages listed below. This list is also available as a "See also" link from each of the pages.

For information about product changes and Model 204 feature support per SirAud version, see the Model 204 release notes.

For information about product error messages, see SirAud messages.