SirTune data collection under MVS - Revision history

JAL: add word

2017-08-08T22:18:12Z

add word

← Older revision		Revision as of 22:18, 8 August 2017
Line 2:		Line 2:
	as of SirTune 7.1, and it was integrated into the Model 204 nucleus as of Model 204 7.5.		as of SirTune 7.1, and it was integrated into the Model 204 nucleus as of Model 204 7.5.

	Depending on your SirTune ~~version~~, then, you might need to link edit		Depending on your SirTune and Model 204 versions, then, you might need to link edit the <var class="product">Sirius Mods</var> with the <var class="product">Model 204</var> Online module.
	the <var class="product">Sirius Mods</var> with the <var class="product">Model 204</var> Online module.

	This page describes how to modify your Model 204 Online job to accommodate SirTune.		This page describes how to modify your Model 204 Online job to accommodate SirTune.

JAL: add "SirTune size requirement for SIRTUNED" section

2017-08-08T22:16:48Z

add "SirTune size requirement for SIRTUNED" section

← Older revision		Revision as of 22:16, 8 August 2017
Line 3:		Line 3:

	Depending on your SirTune version, then, you might need to link edit		Depending on your SirTune version, then, you might need to link edit
	the <var class="product">Sirius Mods</var> with the <var class="product">Model 204</var> Online module ~~as described on this~~ page.		the <var class="product">Sirius Mods</var> with the <var class="product">Model 204</var> Online module.

			This page describes how to modify your Model 204 Online job to accommodate SirTune.

	==<b id="stunjcl"></b>JCL for SirTune==		==<b id="stunjcl"></b>JCL for SirTune==
Line 64:		Line 66:
	Simply allocate SIRTUNED at 20 megabytes (or less if disk space is		Simply allocate SIRTUNED at 20 megabytes (or less if disk space is
	tight), and adjust the size based on experience.		tight), and adjust the size based on experience.
	For more information on sizing SIRTUNED, see [[#SirTune size requirement for SIRTUNED\|SirTune size requirement for SIRTUNED]].		For more information on sizing SIRTUNED, see [[#SirTune size requirement for SIRTUNED\|SirTune size requirement for SIRTUNED]], below.
	To keep available data from several runs, make SIRTUNED part of a GDG.</p></li>		To keep available data from several runs, make SIRTUNED part of a GDG.</p></li>

JAL: add "SirTune size requirement for SIRTUNED" section

2017-08-08T22:09:06Z

add "SirTune size requirement for SIRTUNED" section

Show changes

JAL: link repair

2017-08-08T20:54:12Z

link repair

← Older revision		Revision as of 20:54, 8 August 2017
Line 82:		Line 82:
	which data is collected, the sampling rate, authorization to issue		which data is collected, the sampling rate, authorization to issue
	MODIFY commands, and more.		MODIFY commands, and more.
	For a list of the available statements, see [[SirTune ~~configuration~~ statements]].</p>		For a list of the available statements, see [[SirTune data collection statements]].</p>
	<p>		<p>
	SIRTUNEI can have either fixed or variable format, and it can have any record length.</p></li>		SIRTUNEI can have either fixed or variable format, and it can have any record length.</p></li>

JAL: add link

2017-08-01T23:33:37Z

add link

← Older revision		Revision as of 23:33, 1 August 2017
Line 27:		Line 27:
	<ul>		<ul>
	<li>Under z/OS or OS/390, include no SIRTUNED DD statement during initialization.</li>		<li>Under z/OS or OS/390, include no SIRTUNED DD statement during initialization.</li>
	<li>Set the <~~code~~>SIRTUNE</~~code~~> parameter to 0.
			<li>Set the <var>[[SIRTUNE parameter\|SIRTUNE]]</var> parameter to 0.
	<p>		<p>
	SIRTUNE, which is only allowed as a parameter in the EXEC JCL statement,		<var>SIRTUNE</var>, which is only allowed as a parameter in the EXEC JCL statement,
	controls whether the <var class="product">SirTune</var> data collector is initialized at the		controls whether the <var class="product">SirTune</var> data collector is initialized at the start of a <var class="product">Model 204</var> run.</p>
	start of a <var class="product">Model 204</var> run.</p>
	<p>		<p>
	The SIRTUNE parameter can be set to either of these values:</p>		The <var>SIRTUNE</var> parameter can be set to either of these values:</p>
	<table class="thJustBold">		<table class="thJustBold">
	<tr><th>0</th>		<tr><th>0</th>
Line 41:		Line 41:
	<td>Enables initialization (this is the default).</td></tr>		<td>Enables initialization (this is the default).</td></tr>
	</table>		</table>
			<p>
	For example:		For example: </p>
	<p class="code"~~><nowiki~~>//ONLINE EXEC PGM=ONLINE,PARM='SIRTUNE=0'		<p class="code">//ONLINE EXEC PGM=ONLINE,PARM='SIRTUNE=0'
	~~</nowiki>~~</p></li>		</p></li>
	</ul>		</ul>

Line 95:		Line 95:
	<ul>		<ul>
	<li>Modify the JCL that invokes <var class="product">Model 204</var> so that it invokes SIRTUNE instead. For example, to have <var class="product">SirTune</var> monitor an Online invoked with:		<li>Modify the JCL that invokes <var class="product">Model 204</var> so that it invokes SIRTUNE instead. For example, to have <var class="product">SirTune</var> monitor an Online invoked with:
	<p class="code"~~><nowiki~~>//ONLINE EXEC PGM=ONLINE,REGION=4096K,TIME=1440,		<p class="code">//ONLINE EXEC PGM=ONLINE,REGION=4096K,TIME=1440,
	// PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'		// PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'
	~~</nowiki>~~</p>		</p>
	<p>		<p>
	~~change~~ the line to read:</p>		Change the line to read:</p>
	<p class="code"~~><nowiki~~>//ONLINE EXEC PGM=SIRTUNE,REGION=4096K,TIME=1440,		<p class="code">//ONLINE EXEC PGM=SIRTUNE,REGION=4096K,TIME=1440,
	// PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'		// PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'
	~~</nowiki>~~</p></li>		</p></li>

	<li>Place the SIRTUNE load module into the		<li>Place the SIRTUNE load module into the
Line 112:		Line 112:
	<var class="product">SirTune</var> data collection should have no significant impact on the performance of the Online region.		<var class="product">SirTune</var> data collection should have no significant impact on the performance of the Online region.

	If the <var class="product">Model 204</var> load module that is being monitored with <var class="product">SirTune</var> must run authorized, the SIRTUNE load module must be placed		If the <var class="product">Model 204</var> load module that is being monitored with <var class="product">SirTune</var> must run authorized, the SIRTUNE load module must be placed
	into an APF-authorized library.		into an APF-authorized library.

JAL: misc formatting

2017-07-11T19:02:55Z

misc formatting

← Older revision		Revision as of 19:02, 11 July 2017
Line 1:		Line 1:
	~~<!--Page automatically generated by CMSTOWIK EXEC and will be~~		How you invoke <var class="product">SirTune</var> depends on its version.
	automatically replaced -- any manual edits will be lost.
	~~You've been warned. .. (Page built by JAL at the SIRIUS VM; file: FUNPGNEW SYSUT2) -->~~
	~~<!-- Page name: Sirtune data collection under MVS -->~~
	~~<p></p>~~
	~~As of the integration of the <var class="product">SirTune</var> data collector with the <var class="product">Sirius Mods</var>.~~
	~~(in <var class="product">Sirius Mods</var> version 6.9), how~~ you invoke <var class="product">SirTune</var> depends on its version.

	~~<div id="vercurr"></div>~~
	~~==Versions of <var class="product">SirTune</var> after 1.5==~~
	~~<!--Caution: <div> above-->~~

			==<b id="vercurr"></b>Versions of <var class="product">SirTune</var> after 1.5==
	The data collection portion of <var class="product">SirTune</var> is part of the <var class="product">Sirius Mods</var> object.		The data collection portion of <var class="product">SirTune</var> is part of the <var class="product">Sirius Mods</var> object.
	The data collector becomes available once the <var class="product">Sirius Mods</var> is link edited with the <var class="product">Model 204</var> ~~ONLINE~~ module.		The data collector becomes available once the <var class="product">Sirius Mods</var> is link edited with the <var class="product">Model 204</var> Online module.

	~~<div id="stunjcl"></div>~~
	~~===JCL for SirTune===~~
	~~<!--Caution: <div> above-->~~

			===<b id="stunjcl"></b>JCL for SirTune===
	To invoke <var class="product">SirTune</var>,		To invoke <var class="product">SirTune</var>,
	The EXEC statement in your JCL should directly invoke the <var class="product">Model 204</var> load module:		The EXEC statement in your JCL should directly invoke the <var class="product">Model 204</var> load module:
Line 59:		Line 47:
	</ul>		</ul>

	<~~div~~ id="stundds"></~~div~~>		===<b id="stundds"></b>The SirTune DD statements===

	~~===~~The SirTune DD statements===
	~~<!--Caution: <div> above-->~~

	<var class="product">SirTune</var> uses one or both of the DD statements described below.		<var class="product">SirTune</var> uses one or both of the DD statements described below.
	<p class="note"><b>Note:</b> The SIRTUNEO dataset used in earlier versions of <var class="product">SirTune</var> is obsolete in versions of <var class="product">SirTune</var> after 1.5.		<p class="note"><b>Note:</b> The SIRTUNEO dataset used in earlier versions of <var class="product">SirTune</var> is obsolete in versions of <var class="product">SirTune</var> after 1.5.
Line 106:		Line 90:
	The data collection portion of <var class="product">SirTune</var> consists of a single load module called <code>SIRTUNE</code>.		The data collection portion of <var class="product">SirTune</var> consists of a single load module called <code>SIRTUNE</code>.

	<~~div~~ id="invstun"></~~div~~>		===<b id="invstun"></b>Invoking the SIRTUNE module===
	~~===~~Invoking the SIRTUNE module===
	~~<!--Caution: <div> above-->~~

	To have <var class="product">SirTune</var> collect data for a particular Online job, you must do the following so that		To have <var class="product">SirTune</var> collect data for a particular Online job, you must do the following so that
	<var class="product">SirTune</var> will run <var class="product">Model 204</var> as a subtask of SIRTUNE, collecting polling data as required:		<var class="product">SirTune</var> will run <var class="product">Model 204</var> as a subtask of SIRTUNE, collecting polling data as required:
Line 137:		Line 118:
	(including unknown <var class="product">Model 204</var> release, <var class="product">SirTune</var> expiration, or operation on an unauthorized CPU), <var class="product">Model 204</var> will still proceed. This lets you leave SIRTUNE in place in your JCL while a temporary problem is being solved.		(including unknown <var class="product">Model 204</var> release, <var class="product">SirTune</var> expiration, or operation on an unauthorized CPU), <var class="product">Model 204</var> will still proceed. This lets you leave SIRTUNE in place in your JCL while a temporary problem is being solved.

	<~~div~~ id="stddv15"></~~div~~>		===<b id="stddv15"></b>The SIRTUNE DD statements===
	~~===~~The SIRTUNE DD statements===
	~~<!--Caution: <div> above-->~~

	The SIRTUNE load module uses as many as three DD statements: the first		The SIRTUNE load module uses as many as three DD statements: the first
	(<code>SIRTUNED</code>) is required and specifies the data set to receive the collected data; the other two are optional:		(<code>SIRTUNED</code>) is required and specifies the data set to receive the collected data; the other two are optional:
Line 154:		Line 132:
	</table>		</table>

	<~~div~~ id="stunxmp"></~~div~~>		===<b id="stunxmp"></b>JCL example===
	~~===~~JCL example===
	~~<!--Caution: <div> above-->~~

	The following is an example of JCL that runs a BATCH204 job under <code>SIRTUNE</code> in an MVS environment.		The following is an example of JCL that runs a BATCH204 job under <code>SIRTUNE</code> in an MVS environment.

	~~====~~get non-BATCH204 example~~====~~		<!-- get non-BATCH204 example -->
	<p class="code"><nowiki>//DAILY204 JOB (0),CLASS=C,MSGCLASS=A		<p class="code"><nowiki>//DAILY204 JOB (0),CLASS=C,MSGCLASS=A
	//BATCH204 EXEC PGM=SIRTUNE,REGION=4096K,		//BATCH204 EXEC PGM=SIRTUNE,REGION=4096K,

JAL: add links

2015-11-05T01:25:25Z

add links

← Older revision		Revision as of 01:25, 5 November 2015
Line 90:		Line 90:
	To keep available data from several runs, make SIRTUNED part of a GDG.</p></li>		To keep available data from several runs, make SIRTUNED part of a GDG.</p></li>

	<li>SIRTUNEI		<li id="sirtunei">SIRTUNEI
	<p>		<p>
	This optional DD specifies a data set that		This optional DD specifies a data set that
Line 148:		Line 148:

	<tr><th>SIRTUNEI</th>		<tr><th>SIRTUNEI</th>
	<td>See ~~list item :liref refid=stunei.~~.</td></tr>		<td>See [[#sirtunei\|SIRTUNEI]], above.</td></tr>

	<tr><th>SIRTUNEO</th>		<tr><th>SIRTUNEO</th>
Line 158:		Line 158:
	<!--Caution: <div> above-->		<!--Caution: <div> above-->

	The following is an example of JCL that runs a BATCH204 job under SIRTUNE		The following is an example of JCL that runs a BATCH204 job under <code>SIRTUNE</code> in an MVS environment.
	in an MVS environment.

	====get non-BATCH204 example====		====get non-BATCH204 example====

JAL: misc cleanup

2015-11-05T01:23:07Z

misc cleanup

← Older revision		Revision as of 01:23, 5 November 2015
Line 12:		Line 12:

	The data collection portion of <var class="product">SirTune</var> is part of the <var class="product">Sirius Mods</var> object.		The data collection portion of <var class="product">SirTune</var> is part of the <var class="product">Sirius Mods</var> object.
	The data collector becomes available once the <var class="product">Sirius Mods</var> is link edited with the <var class="product">Model 204</var> ONLINE module.		The data collector becomes available once the <var class="product">Sirius Mods</var> is link edited with the <var class="product">Model 204</var> ONLINE module.

	<div id="stunjcl"></div>		<div id="stunjcl"></div>
Line 19:		Line 19:

	To invoke <var class="product">SirTune</var>,		To invoke <var class="product">SirTune</var>,
	The EXEC statement in your JCL should directly invoke the <var class="product">Model 204</var> load module:		The EXEC statement in your JCL should directly invoke the <var class="product">Model 204</var> load module:
	<p class="code"><nowiki>//ONLINE EXEC PGM=ONLINE,...		<p class="code"><nowiki>//ONLINE EXEC PGM=ONLINE,...
	</nowiki></p>		</nowiki></p>
Line 26:		Line 26:
	(which is described in [[#invstun\|Invoking the SIRTUNE module]]).		(which is described in [[#invstun\|Invoking the SIRTUNE module]]).

	In addition, the JCL that invokes <var class="product">Model 204</var> must include a DD statement		In addition, the JCL that invokes <var class="product">Model 204</var> must include a DD statement for the SIRTUNED dataset (see [[#stundds\|The SirTune DD statements]]).
	for the SIRTUNED dataset (see [[#stundds\|The ~~<var class="product">~~SirTune~~</var>~~ DD statements]]).
	Then, if <var class="product">SirTune</var> is authorized for use at your site, the <var class="product">SirTune</var>		Then, if <var class="product">SirTune</var> is authorized for use at your site, the <var class="product">SirTune</var>
	data collector will be initialized,		data collector will be initialized.

	If you are upgrading from an earlier version of <var class="product">SirTune</var>,		If you are upgrading from an earlier version of <var class="product">SirTune</var>,
	no changes are necessary to the <var class="product">SirTune</var> DD statements you were using.		no changes are necessary to the <var class="product">SirTune</var> DD statements you were using.
	However, if you specified SIRTUNEI configuration statements for the data collector,		However, if you specified SIRTUNEI configuration statements for the data collector, the PGM statement
	the PGM statement
	is ignored, since <var class="product">SirTune</var> no longer loads the <var class="product">Model 204</var> ONLINE load module.		is ignored, since <var class="product">SirTune</var> no longer loads the <var class="product">Model 204</var> ONLINE load module.

Line 70:		Line 68:
	</p>		</p>
	<ul>		<ul>
	<li>SIRTUNED		<li id="sirtuned">SIRTUNED
	<p>		<p>
	This required DD specifies the data set that receives the data collected by		This required DD specifies the data set that receives the data collected by
	<var class="product">SirTune</var>.		<var class="product">SirTune</var>.
	This data set must have variable blocked (VB) format, and it should generally		This data set must have variable blocked (VB) format, and it should generally have a large block size (>10000).
	have a large block size (>10000).
	If DCB information is not explicitly specified, the defaults selected by		If DCB information is not explicitly specified, the defaults selected by
	<var class="product">SirTune</var> should be adequate for all but the most extreme cases.</p>		<var class="product">SirTune</var> should be adequate for all but the most extreme cases.</p>
	<p>		<p>
	If SIRTUNED is ~~pre-allocated~~ under ISPF or its equivalent, the recommended		If SIRTUNED is preallocated under ISPF or its equivalent, the recommended
	blocksizes are 23,476 on a 3380 and 27,998 on a 3390.		blocksizes are 23,476 on a 3380 and 27,998 on a 3390.
	If this dataset fills up, <var class="product">SirTune</var> will simply stop collecting data for		If this dataset fills up, <var class="product">SirTune</var> will simply stop collecting data for the duration of the run.
	the duration of the run.
	A 20 megabyte SIRTUNED should be sufficient for most shops, while a 50		A 20 megabyte SIRTUNED should be sufficient for most shops, while a 50
	megabyte SIRTUNED should be sufficient for almost any requirements.</p>		megabyte SIRTUNED should be sufficient for almost any requirements.</p>
Line 98:		Line 94:
	This optional DD specifies a data set that		This optional DD specifies a data set that
	contains statements that alter the <var class="product">SirTune</var> defaults.		contains statements that alter the <var class="product">SirTune</var> defaults.
	These statements allow control over the name of the <var class="product">Model 204</var> load module,		These statements allow control over the name of the <var class="product">Model 204</var> load module,
	the level of detail to which data is collected, the time intervals over		the level of detail to which data is collected, the time intervals over
	which data is collected, the sampling rate, authorization to issue		which data is collected, the sampling rate, authorization to issue
Line 104:		Line 100:
	For a list of the available statements, see [[SirTune configuration statements]].</p>		For a list of the available statements, see [[SirTune configuration statements]].</p>
	<p>		<p>
	SIRTUNEI can have either fixed or variable format, and it can have any record		SIRTUNEI can have either fixed or variable format, and it can have any record length.</p></li>
	length.</p></li>
	</ul>		</ul>

	==Version 1.5 or earlier of SirTune==		==Version 1.5 or earlier of SirTune==
	The data collection portion of <var class="product">SirTune</var> consists of a single load		The data collection portion of <var class="product">SirTune</var> consists of a single load module called <code>SIRTUNE</code>.
	module called <b>SIRTUNE</b>.

	<div id="invstun"></div>		<div id="invstun"></div>
Line 116:		Line 110:
	<!--Caution: <div> above-->		<!--Caution: <div> above-->

	To have <var class="product">SirTune</var> collect data for a particular Online job,		To have <var class="product">SirTune</var> collect data for a particular Online job, you must do the following so that
	you must do the following so that		<var class="product">SirTune</var> will run <var class="product">Model 204</var> as a subtask of SIRTUNE, collecting polling data as required:
	<var class="product">SirTune</var> will run <var class="product">Model 204</var> as a subtask of SIRTUNE, collecting polling data as required:
	<ul>		<ul>
	<li>Modify the JCL that invokes <var class="product">Model 204</var> so that it invokes		<li>Modify the JCL that invokes <var class="product">Model 204</var> so that it invokes SIRTUNE instead. For example, to have <var class="product">SirTune</var> monitor an Online invoked with:
	SIRTUNE instead. For example, to have <var class="product">SirTune</var> monitor an Online invoked with:
	<p class="code"><nowiki>//ONLINE EXEC PGM=ONLINE,REGION=4096K,TIME=1440,		<p class="code"><nowiki>//ONLINE EXEC PGM=ONLINE,REGION=4096K,TIME=1440,
	// PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'		// PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'
Line 137:		Line 129:
	</ul>		</ul>

	<var class="product">SirTune</var> data collection should have no significant impact on the		<var class="product">SirTune</var> data collection should have no significant impact on the performance of the Online region.
	performance of the Online region.

	If the <var class="product">Model 204</var> load module that is being monitored with <var class="product">SirTune</var> must run authorized, the SIRTUNE load module must be placed		If the <var class="product">Model 204</var> load module that is being monitored with <var class="product">SirTune</var> must run authorized, the SIRTUNE load module must be placed
	into an APF-authorized library.		into an APF-authorized library.

	If SIRTUNE is able to load <var class="product">Model 204</var> but cannot sample for some reason		If SIRTUNE is able to load <var class="product">Model 204</var> but cannot sample for some reason
	(including unknown <var class="product">Model 204</var> release, <var class="product">SirTune</var> expiration, or operation on an unauthorized CPU), <var class="product">Model 204</var> will still proceed. This lets you leave SIRTUNE in place in your JCL while a		(including unknown <var class="product">Model 204</var> release, <var class="product">SirTune</var> expiration, or operation on an unauthorized CPU), <var class="product">Model 204</var> will still proceed. This lets you leave SIRTUNE in place in your JCL while a temporary problem is being solved.
	temporary problem is being solved.

	<div id="stddv15"></div>		<div id="stddv15"></div>
Line 152:		Line 142:

	The SIRTUNE load module uses as many as three DD statements: the first		The SIRTUNE load module uses as many as three DD statements: the first
	(<b>SIRTUNED</b>) is required and specifies the ~~dataset~~ to receive the collected data; the other two		(<code>SIRTUNED</code>) is required and specifies the data set to receive the collected data; the other two are optional:
	are optional:
	<table class="thJustBold">		<table class="thJustBold">
	<tr><th>SIRTUNED</th>		<tr><th>SIRTUNED</th>
	<td>See ~~list item :liref refid=stuned.~~.</td></tr>		<td>See [[#sirtuned\|SIRTUNED]], above.</td></tr>

	<tr><th>SIRTUNEI</th>		<tr><th>SIRTUNEI</th>

JAL: /* JCL for SirTune */

2015-07-02T23:29:29Z

JCL for SirTune

← Older revision		Revision as of 23:29, 2 July 2015
Line 15:		Line 15:

	<div id="stunjcl"></div>		<div id="stunjcl"></div>
	===JCL for ~~<var class="product">~~SirTune~~</var>~~===		===JCL for SirTune===
	<!--Caution: <div> above-->		<!--Caution: <div> above-->

Line 62:		Line 62:

	<div id="stundds"></div>		<div id="stundds"></div>

	===The SirTune DD statements===		===The SirTune DD statements===
	<!--Caution: <div> above-->		<!--Caution: <div> above-->

JAL: more conversion cleanup

2015-07-02T23:28:44Z

more conversion cleanup

Show changes