SirAud - Revision history

JAL: misc formatting

2016-10-12T22:16:13Z

misc formatting

← Older revision		Revision as of 22:16, 12 October 2016
Line 1:		Line 1:
	<var class="product">SirAud</var> reads a single journal file produced by <var class="product">Model 204</var> and it generates		<var class="product">SirAud</var> reads a single journal file produced by <var class="product">Model 204</var> and it generates a set of reports, using
	a set of reports, using
	statistics entries as well as other information in the journal.		statistics entries as well as other information in the journal.
	These reports are intended to provide an overview		These reports are intended to provide an overview
	of the resource usage for one <var class="product">Model 204</var> run.		of the resource usage for one <var class="product">Model 204</var> run.
	Each report summarizes a different aspect of the run.		Each report summarizes a different aspect of the run.

Line 11:		Line 10:
	The sections on this page give the report names and a brief description of the report contents.		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 <var class="product">SirAud</var> program parameter		If a report is selected by specifying a <var class="product">SirAud</var> program parameter (see [[SirAud parameters#allpr\|ALLPR and NOPR]]), all reports are
	(see [[SirAud parameters#allpr\|ALLPR and NOPR]]), all reports are		produced on the <code>SYSPRINT</code> file, and only there.
	produced on the SYSPRINT file, and only there.		Otherwise, the name of the report given in the following table is the same as the name of the DD statement (in MVS, or the FILEDEF command, in CMS) to which the report is written.
	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===~~		<table class="thJustBold">
	~~This report summarizes system-level performance over each ACCTIM interval.~~		<caption>SirAud reports</caption>
			<tr class="head"><th>Report</th>
			<th>Description</th></tr>

	~~===FILEREPT===~~		<tr><th>PERFREPT</th>
	This report summarizes ~~the resource utilization of~~ each <var ~~class="product"~~>~~Model 204~~</var> ~~file~~.		<td>This report summarizes system-level performance over each <var>[[ACCTIM parameter\|ACCTIM]]</var> interval.
	~~Files are reported in descending order by total disk I~~/~~O (~~<~~code~~>~~DKRD+DKWR~~</~~code~~>).		<p>
			For more information about the report content, see [[SirAud report contents#PERFREPT\|PERFREPT]]. </p></td></tr>

	===PROCREPT~~===~~		<tr><th>FILEREPT</th>
	This report summarizes the resource utilization of each <var class="product">Model 204</var> procedure.		<td>This report summarizes the resource utilization of each <var class="product">Model 204</var> file.
			Files are reported in descending order by total disk I/O (<code>DKRD+DKWR</code>).
			<p>
			For more information about the report content, see [[SirAud report contents#FILEREPT\|FILEREPT]]. </p></td></tr>

			<tr><th>PROCREPT</th>
			<td>This report summarizes the resource utilization of each <var class="product">Model 204</var> procedure.
	Procedures are reported by subsystem and file, in descending order by total CPU.		Procedures are reported by subsystem and file, in descending order by total CPU.
			<p>
			For more information about the report content, see [[SirAud report contents#PROCREPT\|PROCREPT]]. </p> </td></tr>

	~~===~~SUBREPT~~===~~		<tr><th>SUBREPT</th>
	This report summarizes the resource utilization of each <var class="product">Model 204</var> subsystem.		<td>This report summarizes the resource utilization of each <var class="product">Model 204</var> subsystem. Subsystems are reported in descending order by total CPU.
	Subsystems are reported in descending order by total CPU.		<p>
			For more information about the report content, see [[SirAud report contents#SUBREPT\|SUBREPT]]. </p></td></tr>

	~~===~~UTBLREPT~~===~~		<tr><th>UTBLREPT</th>
	This report summarizes the current high water mark of each user-resettable server		<td>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.
	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.		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		A separate line is produced for each procedure in the subsystem that
	has a table high water mark that is above the "target" value.		has a table high water mark that is above the "target" value.
			<p>
			For more information about the report content, see [[SirAud report contents#UTBLREPT\|UTBLREPT]]. </p></td></tr>

	~~===~~UTBLSUMM~~===~~		<tr><th>UTBLSUMM</th>
	This report summarizes the current high water mark of each user-resettable server table for each subsystem.		<td>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.
	Subsystems are reported in descending order		<p>
	by the largest server size needed to run all of its procedures executed during the run.		For more information about the report content, see [[SirAud report contents#UTBLSUMM\|UTBLSUMM]]. </p></td></tr>
			</table>

	==Additional SirAud files==		==Additional SirAud files==
Line 54:		Line 64:
	is always written to SYSPRINT:		is always written to SYSPRINT:
	<ul>		<ul>
	<li>Various <b>AUD</b>nnn messages, which are explained in		<li>Various <b>AUD</b><i>nnn</i> messages, which are explained in
	[[:Category:SirAud messages\|SirAud messages]].		[[:Category:SirAud messages\|SirAud messages]].

	<li>Identification of the <var class="product">Model 204</var> run that created the JOURNAL file.		<li>Identification of the <var class="product">Model 204</var> run that created the <code>JOURNAL</code> file.

	<li>A list of pertinent run-time parameters as specified in the <var class="product">Model 204</var> run's EXEC, user 0,		<li>A list of pertinent run-time parameters as specified in the <var class="product">Model 204</var> run's EXEC, user 0,
Line 64:		Line 74:

	Also, if any <var class="product">SirAud</var> reports are specified as program parameters,		Also, if any <var class="product">SirAud</var> reports are specified as program parameters,
	reports are contained in the SYSPRINT file, and only there; see [[SirAud parameters#allpr\|ALLPR and NOPR]].		reports are contained in the <code>SYSPRINT</code> file, and only there; see [[SirAud parameters#allpr\|ALLPR and NOPR]].

	===<b id="sysin"></b>SYSIN===		===<b id="sysin"></b>SYSIN===
	Prior to version 1.05 of <var class="product">SirAud</var>, no SYSIN file contents were read by <var class="product">SirAud</var>.		Prior to version 1.05 of <var class="product">SirAud</var>, no SYSIN file contents were read by <var class="product">SirAud</var>.
	As of version 1.05, all <var class="product">SirAud</var> [[SirAud parameters\|program parameters]] may be specified on input records in the SYSIN data set, which is read and parsed under MVS and CMS.		As of version 1.05, all <var class="product">SirAud</var> [[SirAud parameters\|program parameters]] may be specified on input records in the <code>SYSIN</code> data set, which is read and parsed under MVS and CMS.

	You can specify multiple parameters on one SYSIN record, and you can specify multiple records, but you		You can specify multiple parameters on one <code>SYSIN</code> record, and you can specify multiple records, but you
	cannot specify a parameter on one record and "continue" its value(s) on another record.		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:		The following simple example of <code>SYSIN</code> content shows valid SirAud parameter specifications:
	<p class="code"><nowiki>FROM 04169 10:00		<p class="code"><nowiki>FROM 04169 10:00
	PERFRP		PERFRP

JAL: misc cleanup

2016-10-12T19:37:42Z

misc cleanup

← Older revision		Revision as of 19:37, 12 October 2016
Line 22:		Line 22:

	===FILEREPT===		===FILEREPT===
	This report summarizes the resource utilization of each <var class="product">Model 204</var> file.		This report summarizes the resource utilization of each <var class="product">Model 204</var> file.
	Files are reported in descending order by total disk I/O (DKRD+DKWR).		Files are reported in descending order by total disk I/O (<code>DKRD+DKWR</code>).

	===PROCREPT===		===PROCREPT===
	This report summarizes the resource utilization of each <var class="product">Model 204</var> procedure.		This report summarizes the resource utilization of each <var class="product">Model 204</var> procedure.
	Procedures are reported by subsystem and file, in descending order by total CPU.		Procedures are reported by subsystem and file, in descending order by total CPU.

	===SUBREPT===		===SUBREPT===
	This report summarizes the resource utilization of each <var class="product">Model 204</var> subsystem.		This report summarizes the resource utilization of each <var class="product">Model 204</var> subsystem.
	Subsystems are reported in descending order by total CPU.		Subsystems are reported in descending order by total CPU.

	===UTBLREPT===		===UTBLREPT===
	This report summarizes the current high water mark of each user-resettable server		This report summarizes the current high water mark of each user-resettable server
	table on a subsystem basis.		table on a subsystem basis. A set of "target" table settings is also presented.
	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.
	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		A separate line is produced for each procedure in the subsystem that
	has a table high water mark that is above the "target" value.		has a table high water mark that is above the "target" value.
Line 50:		Line 48:

	===JOURNAL===		===JOURNAL===
	This is the input <var class="product">Model 204</var> journal file. ~~:h2 id=syspr.SYSPRINT~~		This is the input <var class="product">Model 204</var> journal file.

			===<b id="syspr"></b>SYSPRINT===
	Various information is written to this file; the following information		Various information is written to this file; the following information
	is always written to SYSPRINT:		is always written to SYSPRINT:
	<ul>		<ul>
	<li>Various <b>AUD</b>nnn messages, which are explained in		<li>Various <b>AUD</b>nnn messages, which are explained in
	[[SirAud messages]].		[[:Category:SirAud messages\|SirAud messages]].

	<li>Identification of the <var class="product">Model 204</var> run that created the JOURNAL file.		<li>Identification of the <var class="product">Model 204</var> run that created the JOURNAL file.

	<li>A list of pertinent run-time parameters as specified in the <var class="product">Model 204</var> run's EXEC, user 0,		<li>A list of pertinent run-time parameters as specified in the <var class="product">Model 204</var> run's EXEC, user 0,
	and user n parameters.		and user <var class="term">n</var> parameters.
	</ul>		</ul>

Line 69:		Line 68:
	===<b id="sysin"></b>SYSIN===		===<b id="sysin"></b>SYSIN===
	Prior to version 1.05 of <var class="product">SirAud</var>, no SYSIN file contents were read by <var class="product">SirAud</var>.		Prior to version 1.05 of <var class="product">SirAud</var>, no SYSIN file contents were read by <var class="product">SirAud</var>.
	As of version 1.05, all <var class="product">SirAud</var> ~~program parameters (~~[[SirAud parameters]]) may		As of version 1.05, all <var class="product">SirAud</var> [[SirAud parameters\|program parameters]] may be specified on input records in the SYSIN data set, which is read and parsed under MVS and CMS.
	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,		You can specify multiple parameters on one SYSIN record, and you can specify multiple records, but you
	and you can specify multiple records, but you		cannot specify a parameter on one record and "continue" its value(s) on another record.
	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~~		The following simple example of SYSIN content shows valid SirAud parameter specifications:
	parameter specifications:
	<p class="code"><nowiki>FROM 04169 10:00		<p class="code"><nowiki>FROM 04169 10:00
	PERFRP		PERFRP

Admin: 1 revision: SirAud pages

2016-10-10T23:00:37Z

1 revision: SirAud pages

← Older revision	Revision as of 23:00, 10 October 2016
(No difference)

JAL: add "topics"

2016-10-10T21:26:02Z

add "topics"

New page

<var class="product">SirAud</var> reads a single journal file produced by <var class="product">Model 204</var> 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 <var class="product">Model 204</var> 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 <var class="product">SirAud</var> 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 <var class="product">SirAud</var> program parameter
(see [[SirAud parameters#allpr|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 <var class="product">Model 204</var> file.
Files are reported in descending order by total disk I/O (DKRD+DKWR).

===PROCREPT===
This report summarizes the resource utilization of each <var class="product">Model 204</var> procedure.
Procedures are reported by subsystem and file, in descending order by total CPU.

===SUBREPT===
This report summarizes the resource utilization of each <var class="product">Model 204</var> 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 <var class="product">Model 204</var> journal file. :h2 id=syspr.SYSPRINT

Various information is written to this file; the following information
is always written to SYSPRINT:
<ul>
<li>Various AUDnnn messages, which are explained in
[[SirAud messages]].

<li>Identification of the <var class="product">Model 204</var> run that created the JOURNAL file.

<li>A list of pertinent run-time parameters as specified in the <var class="product">Model 204</var> run's EXEC, user 0,
and user n parameters.
</ul>

Also, if any <var class="product">SirAud</var> reports are specified as program parameters,
reports are contained in the SYSPRINT file, and only there; see [[SirAud parameters#allpr|ALLPR and NOPR]].

===SYSIN===
Prior to version 1.05 of <var class="product">SirAud</var>, no SYSIN file contents were read by <var class="product">SirAud</var>.
As of version 1.05, all <var class="product">SirAud</var> 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:
<nowiki>FROM 04169 10:00
PERFRP
TO 04170 12:00
</nowiki>

==SirAud topics==
The <var class="product">SirAud</var> 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 <var class="product">SirAud</var> version, see
the [[M204wiki main page#Release notes, wishlists, and punch lists|Model 204 release notes]].

For information about product error messages, see [[:Category:SirAud messages|SirAud messages]].

{{Template: SirAud topic list}}

[[Category: SirAud]]