SirTune report generation - Revision history

JAL: typos

2017-08-08T19:45:34Z

typos

← Older revision		Revision as of 19:45, 8 August 2017
Line 42:		Line 42:
	Sample data sets from multiple runs may be concatenated. In fact, sample data sets from multiple runs may even be concatenated sequentially into a single data set (with IEBGENER under MVS, or COPYFILE or an equivalent under CMS) and provided as a single data set to SIRTUNEREPORT.</p>		Sample data sets from multiple runs may be concatenated. In fact, sample data sets from multiple runs may even be concatenated sequentially into a single data set (with IEBGENER under MVS, or COPYFILE or an equivalent under CMS) and provided as a single data set to SIRTUNEREPORT.</p>
	<p>		<p>
	When multiple sample data sets are concatenated in any way, the <code>DATASET</code> statement ([[SirTune generation#dsetlst\|DATaset list]]) must be provided in TUNERPTI to have TUNERPTR use any but the first sample data set in the concatenation.</p></td></tr>		When multiple sample data sets are concatenated in any way, the <code>DATASET</code> statement ([[SirTune report generation#dsetlst\|DATaset list]]) must be provided in TUNERPTI to have TUNERPTR use any but the first sample data set in the concatenation.</p></td></tr>

	<tr><th>TUNERPTO</th>		<tr><th>TUNERPTO</th>
	<td>This is the output file for the SIRTUNEREPORT reports.		<td>This is the output file for the SIRTUNEREPORT reports.
	<p>		<p>
	The SOUL code is currently set to output 72 characters per line, so a fixed or fixed-block file with 80-character records is recommended. The output width for report lines is set by the [[SirTune generation#CHARACTERSPERLINE or CPL\|CPL statement]] in the TUNERPTI file. If CPL is not set, the output width defaults to 132 characters. </p>		The SOUL code is currently set to output 72 characters per line, so a fixed or fixed-block file with 80-character records is recommended. The output width for report lines is set by the [[SirTune report generation#CHARACTERSPERLINE or CPL\|CPL statement]] in the TUNERPTI file. If CPL is not set, the output width defaults to 132 characters. </p>
	<p>		<p>
	TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>		TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>

JAL: add former "Report Generator configuration" page

2017-08-08T19:43:18Z

add former "Report Generator configuration" page

Show changes

JAL: add link

2017-08-01T23:40:54Z

add link

← Older revision		Revision as of 23:40, 1 August 2017
Line 49:		Line 49:
	<td>This is the output file for the SIRTUNEREPORT reports.		<td>This is the output file for the SIRTUNEREPORT reports.
	<p>		<p>
	The SOUL code is currently set to output 72 characters per line, so a fixed or fixed-block file with 80-character records is recommended. The output width for report lines is set by the CPL statement in the TUNERPTI file. If ~~this parameter isn't~~ set ~~then~~ the output width defaults to 132 characters. </p>		The SOUL code is currently set to output 72 characters per line, so a fixed or fixed-block file with 80-character records is recommended. The output width for report lines is set by the [[SirTune Report Generator configuration#CHARACTERSPERLINE or CPL\|CPL statement]] in the TUNERPTI file. If CPL is not set, the output width defaults to 132 characters. </p>
	<p>		<p>
	TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>		TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>

DCameron: /* Report files */

2017-08-01T13:52:45Z

Report files

← Older revision		Revision as of 13:52, 1 August 2017
Line 49:		Line 49:
	<td>This is the output file for the SIRTUNEREPORT reports.		<td>This is the output file for the SIRTUNEREPORT reports.
	<p>		<p>
	The SOUL code is currently set to output ~~128~~ characters per line, so a fixed or fixed-block file with ~~132~~-character records is recommended. </p>		The SOUL code is currently set to output 72 characters per line, so a fixed or fixed-block file with 80-character records is recommended. The output width for report lines is set by the CPL statement in the TUNERPTI file. If this parameter isn't set then the output width defaults to 132 characters. </p>
	<p>		<p>
	TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>		TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>

DCameron: /* Report job */

2017-08-01T13:34:47Z

Report job

← Older revision		Revision as of 13:34, 1 August 2017
Line 76:		Line 76:
	//CCAPRINT DD SYSOUT=*,OUTLIM=50000		//CCAPRINT DD SYSOUT=*,OUTLIM=50000
	//CCAIN DD *		//CCAIN DD *
	NFILES=5,NDCBS=5,NDIR=5,MAXBUF=50,NGROUP=5,NORQS=4,~~LIBUFF=132,~~ X		NFILES=5,NDCBS=5,NDIR=5,MAXBUF=50,NGROUP=5,NORQS=4, X
	~~LOBUFF=320,LPDLST=2400,~~LQTBL=~~1350~~,LSTBL=~~2000~~,LNTBL=1200		LQTBL=4000,LSTBL=30000,LNTBL=1200,LVTBL=3000
	LOGON me		LOGON me
	<i>mepassword</i>		<i>mepassword</i>

DCameron: /* Report files */

2017-08-01T13:00:30Z

Report files

← Older revision		Revision as of 13:00, 1 August 2017
Line 49:		Line 49:
	<td>This is the output file for the SIRTUNEREPORT reports.		<td>This is the output file for the SIRTUNEREPORT reports.
	<p>		<p>
	The SOUL code is currently set to output 72 characters per line, so a fixed or fixed-block file with 80-character records is recommended. </p>		The SOUL code is currently set to output 128 characters per line, so a fixed or fixed-block file with 132-character records is recommended. </p>
	<p>		<p>
	TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>		TUNERPTO is an optional file. If it is not present, report output is redirected to standard output; generally, [[CCAPRINT data set\|CCAPRINT]].</p></td></tr>

JAL: remove word

2017-06-12T20:11:24Z

remove word

← Older revision		Revision as of 20:11, 12 June 2017
Line 3:		Line 3:
	in [[SirTune Report Generator configuration]] and [[SirTune reports]].		in [[SirTune Report Generator configuration]] and [[SirTune reports]].
	<p>		<p>
	As of RKTools 7.7, the [[RKTools installation#RKWeb (Model 204 Tools on the Web)\|RKWeb]] browser interface is equipped to invoke and display <code>SIRTUNEREPORT</code> results. Using RKWeb for SirTune reports requires the same set up of input and output files as described on this page.</p>		As of RKTools 7.7, the [[RKTools installation#RKWeb (Model 204 Tools on the Web)\|RKWeb]] browser interface is equipped to invoke and display <code>SIRTUNEREPORT</code> results. Using RKWeb for SirTune reports requires the same set up of input and output files described on this page.</p>

	==Report programs==		==Report programs==

JAL: remove comments re older SIRTUNER versions

2017-06-12T15:57:15Z

remove comments re older SIRTUNER versions

← Older revision		Revision as of 15:57, 12 June 2017
Line 93:		Line 93:

	<li>Under CMS, a similar Batch204 EXEC can be used to invoke <code>SIRTUNEREPORT</code>. </li>		<li>Under CMS, a similar Batch204 EXEC can be used to invoke <code>SIRTUNEREPORT</code>. </li>

	~~<li>Due to format changes in the sample data set, only versions 1.6 and later of SIRTUNER can process a SirTune version 7.0 and later sample data set. </li>~~

	~~<li>Due to format changes in the sample data set in SirTune version 1.5, earlier releases of SIRTUNER cannot process a SirTune 1.5 or higher sample data set. </li>~~
	</ul>		</ul>

JAL: minor formatting

2017-06-10T00:26:37Z

minor formatting

← Older revision		Revision as of 00:26, 10 June 2017
Line 59:		Line 59:

	==Report job==		==Report job==
	Generally, SIRTUNEREPORT is run as a standalone batch job, though		Generally, <code>SIRTUNEREPORT</code> is run as a standalone batch job, though
	it is perfectly acceptable, if perhaps a little resource-intensive, to dynamically allocate the TUNERPT<i>x</i> files and run it from inside an Online.		it is perfectly acceptable, if perhaps a little resource-intensive, to dynamically allocate the TUNERPT<i>x</i> files and run it from inside an Online.

Line 90:		Line 90:
	<li>For RKTools 7.7 or higher, the <code>SIRIUS</code> file is replaced with the <code>M204PROC</code> file. </li>		<li>For RKTools 7.7 or higher, the <code>SIRIUS</code> file is replaced with the <code>M204PROC</code> file. </li>

	<li>For an Online job instead of batch, the same SirTune files are allocated: TUNERPTI (report input parameters), TUNERPTD (reporting data), and an optional TUNERPTO (output destination replacing the screen default). The <~~var~~>OPEN</~~var~~> and <~~var~~>INCLUDE</~~var~~> commands do not change. </li>		<li>For an Online job instead of batch, the same SirTune files are allocated: TUNERPTI (report input parameters), TUNERPTD (reporting data), and an optional TUNERPTO (output destination replacing the screen default). The <code>OPEN</code> and <code>INCLUDE</code> commands do not change. </li>

	<li>Under CMS, a similar Batch204 EXEC can be used to invoke SIRTUNEREPORT. </li>		<li>Under CMS, a similar Batch204 EXEC can be used to invoke <code>SIRTUNEREPORT</code>. </li>

	<li>Due to format changes in the sample data set, only versions 1.6 and later of SIRTUNER can process a SirTune version 7.0 and later sample data set. </li>		<li>Due to format changes in the sample data set, only versions 1.6 and later of SIRTUNER can process a SirTune version 7.0 and later sample data set. </li>

JAL: add headings, introduction

2017-06-10T00:22:59Z

add headings, introduction

← Older revision		Revision as of 00:22, 10 June 2017
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
			Prior to version 7.7 of RKTools, <var class="product">[[SirTune]]</var> reports can only be generated using a SOUL program invoking a call to the <var>[[SirTuneReport (Dataset function)\|SirTuneReport]]</var> method of the <var>Dataset</var> class, as implemented in the <code>SIRTUNEREPORT</code> SOUL program described
			in [[SirTune Report Generator configuration]] and [[SirTune reports]].
			<p>
			As of RKTools 7.7, the [[RKTools installation#RKWeb (Model 204 Tools on the Web)\|RKWeb]] browser interface is equipped to invoke and display <code>SIRTUNEREPORT</code> results. Using RKWeb for SirTune reports requires the same set up of input and output files as described on this page.</p>

			==Report programs==
	The report generation portion of <var class="product">SirTune</var> consists		The report generation portion of <var class="product">SirTune</var> consists
	of two <var class="product">SOUL</var> programs which are distributed in the <var class="product">[[RKTools]]</var> <code>SIRIUS</code> file (prior to RKTools version 7.7) or the <code>M204PROC</code> file (as of RKTools 7.7).		of two <var class="product">SOUL</var> programs which are distributed in the <var class="product">[[RKTools]]</var> <code>SIRIUS</code> file (prior to RKTools version 7.7) or the <code>M204PROC</code> file (as of RKTools 7.7).
Line 15:		Line 21:
	A few <var>[[UTABLE command\|UTABLE]]</var> and environmental settings are executed at the top of SIRTUNEREPORT. These can be adjusted for performance or functional reasons at the client site.		A few <var>[[UTABLE command\|UTABLE]]</var> and environmental settings are executed at the top of SIRTUNEREPORT. These can be adjusted for performance or functional reasons at the client site.

			==Report files==
	SIRTUNEREPORT requires two input files, and it accepts an optional output		SIRTUNEREPORT requires two input files, and it accepts an optional output
	file. These files, described below, may be specified as DD cards or ALLOCATE statements on the job running SIRTUNEREPORT:		file. These files, described below, may be specified as DD cards or ALLOCATE statements on the job running SIRTUNEREPORT:
Line 51:		Line 58:
	The names are chosen to differentiate them from the SIRTUNE<i>x</i> names used during <var class="product">SirTune</var> data collection.		The names are chosen to differentiate them from the SIRTUNE<i>x</i> names used during <var class="product">SirTune</var> data collection.

			==Report job==
	Generally, SIRTUNEREPORT is run as a standalone batch job, though		Generally, SIRTUNEREPORT is run as a standalone batch job, though
	it is perfectly acceptable, if perhaps a little resource-intensive, to dynamically allocate the TUNERPT<i>x</i> files and run it from inside an Online.		it is perfectly acceptable, if perhaps a little resource-intensive, to dynamically allocate the TUNERPT<i>x</i> files and run it from inside an Online.

	A basic TUNERPTR job under MVS would look like this:		A basic TUNERPTR job under MVS would look like this:
	~~====get non-BATCH204 example!! ====~~
	<p class="code">//TUNE JOB (0,0),CLASS=A,MSGCLASS=X		<p class="code">//TUNE JOB (0,0),CLASS=A,MSGCLASS=X
	//TUNERPT EXEC PGM=BATCH204,REGION=4096K,		//TUNERPT EXEC PGM=BATCH204,REGION=4096K,
Line 78:		Line 86:
	</p>		</p>

	~~Under CMS~~, ~~a similar Batch204 EXEC can be used to invoke SIRTUNEREPORT~~.		Notes:
			<ul>
			<li>For RKTools 7.7 or higher, the <code>SIRIUS</code> file is replaced with the <code>M204PROC</code> file. </li>

	~~====get non-BATCH204 example!! ====~~		<li>For an Online job instead of batch, the same SirTune files are allocated: TUNERPTI (report input parameters), TUNERPTD (reporting data), and an optional TUNERPTO (output destination replacing the screen default). The <var>OPEN</var> and <var>INCLUDE</var> commands do not change. </li>

	~~Compatibility notes:~~		<li>Under CMS, a similar Batch204 EXEC can be used to invoke SIRTUNEREPORT. </li>
	~~<ul>~~
	<li>~~As of release 7.2 of the Sirius mods~~, ~~<var class="product">SirTune</var> reports~~ can ~~only~~ be ~~generated~~
	~~using a SOUL program invoking a call~~ to ~~the <var>[[SirTuneReport (Dataset function)\|SirTuneReport]]</var> method of the <var>Dataset</var> class, as implemented in the <code>~~SIRTUNEREPORT~~</code> SOUL program described~~
	~~in [[SirTune Report Generator configuration]] and [[SirTune reports]]~~.</li>

	<li>Due to format changes in the sample data set, only ~~releases~~ 1.6 and later of SIRTUNER can process a SirTune version 7.0 and later sample data set.</li>		<li>Due to format changes in the sample data set, only versions 1.6 and later of SIRTUNER can process a SirTune version 7.0 and later sample data set. </li>

	<li>Due to format changes in the sample data set in SirTune version 1.5, earlier releases of SIRTUNER cannot process a SirTune 1.5 or higher sample data set.</li>		<li>Due to format changes in the sample data set in SirTune version 1.5, earlier releases of SIRTUNER cannot process a SirTune 1.5 or higher sample data set. </li>
	</ul>		</ul>