SirTune Report Generator configuration - Revision history

JAL: page content merged into "SirTune report generation" page

2017-08-08T19:57:35Z

page content merged into "SirTune report generation" page

Show changes

JAL: simplify intro; cleanse "7.2" references

2017-08-08T17:21:26Z

simplify intro; cleanse "7.2" references

Show changes

JAL: wordsmithing for introduction

2017-08-07T15:37:38Z

wordsmithing for introduction

← Older revision		Revision as of 15:37, 7 August 2017
Line 8:		Line 8:
	<ul>		<ul>
	<li>Control-card statements		<li>Control-card statements
			<li>XML document format
			</ul>

			===Using control-card statements===
	<p>		<p>
	~~Report~~ configuration parameters ~~are specified~~ in a set of statements		You can specify report configuration parameters in a set of statements
	(only one per line).		(only one per line). There are no line continuations, and a line beginning
	There are no line continuations, and a line beginning
	with an asterisk character (<code>*</code>) is treated as a comment (that is, ignored). </p>		with an asterisk character (<code>*</code>) is treated as a comment (that is, ignored). </p>
	<p>		<p>
Line 26:		Line 29:
	REPORT STATE RUNG CHUNK 4 CHUNK 400 CHUNK 4000		REPORT STATE RUNG CHUNK 4 CHUNK 400 CHUNK 4000
	REPORT CSECT TOTAL CHUNK 512 CHUNK 64		REPORT CSECT TOTAL CHUNK 512 CHUNK 64
	</p~~></li~~>		</p>

	~~<li>~~XML document format ~~(must be <var class~~=~~"product">SirTune</var> 7.2 or later)~~		===Using XML document format===
	<p>		<p>
			XML document format for parameters is available as of <var class="product">SirTune</var> 7.2.
	Report parameters are case-sensitive XML elements or attributes contained		Report parameters are case-sensitive XML elements or attributes contained
	in a <code>SirtuneInput</code> document node. </p>		in a <code>SirtuneInput</code> document node. </p>
Line 64:		Line 68:
	<report type="csect" chunk="512"/>		<report type="csect" chunk="512"/>
	<report type="csect" chunk="64"/>		<report type="csect" chunk="64"/>
	</SirtuneInput> </p~~></li>~~		</SirtuneInput> </p>
	~~</ul~~>

	==<b id="cardcfg"></b>Configuration parameters==		==<b id="cardcfg"></b>Configuration parameters==

JAL: wordsmithing for introduction

2017-08-07T15:13:52Z

wordsmithing for introduction

← Older revision		Revision as of 15:13, 7 August 2017
Line 1:		Line 1:
	An optional DD card allows the reporting run to be customized.		An optional DD card allows the reporting run to be customized.
	For <var class="product">SirTune</var> 7.2, using the [[SirTune report generation\|SIRTUNEREPORT]] SOUL program to generate		For <var class="product">SirTune</var> 7.2 and higher, using the [[SirTune report generation\|SIRTUNEREPORT]] SOUL program to generate
	reports, this DD card is named <code>TUNERPTI</code>.		reports, this DD card is named <code>TUNERPTI</code>.
	For <var class="product">SirTune</var> versions 6.9 and older, using the SIRTUNER module, the DD card is named <code>SIRTUNEI</code>.		For <var class="product">SirTune</var> versions 6.9 and older, using the SIRTUNER module, the DD card is named <code>SIRTUNEI</code>.

	~~This input~~ card must have fixed format, ~~and~~ it ~~must~~		==Two ways to specify parameters==
	use ~~report configuration parameters specified in~~		The DD card for customizing the report specifies configuration parameters in to define the characteristics of the reporting run. The card must have fixed format, but it can use either of the following types of input format:
	either of the following types of input format ~~to define the~~
	~~characteristics of the reporting run~~:
	<ul>		<ul>
	<li>Control-card statements		<li>Control-card statements