SirTune data collection under MVS: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (add links)
m (misc formatting)
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&nbsp;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&nbsp;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&nbsp;204</var> load module:
The EXEC statement in your JCL should directly invoke the <var class="product">Model&nbsp;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&nbsp;204</var> as a subtask of SIRTUNE, collecting polling data as required:
<var class="product">SirTune</var> will run <var class="product">Model&nbsp;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&nbsp;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&nbsp;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,

Revision as of 19:02, 11 July 2017

How you invoke SirTune depends on its version.

Versions of SirTune after 1.5

The data collection portion of SirTune is part of the Sirius Mods object. The data collector becomes available once the Sirius Mods is link edited with the Model 204 Online module.

JCL for SirTune

To invoke SirTune, The EXEC statement in your JCL should directly invoke the Model 204 load module:

//ONLINE EXEC PGM=ONLINE,...

This statement differs from that required for version 1.5 and earlier of SirTune (which is described in Invoking the SIRTUNE module).

In addition, the JCL that invokes Model 204 must include a DD statement for the SIRTUNED dataset (see The SirTune DD statements). Then, if SirTune is authorized for use at your site, the SirTune data collector will be initialized.

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

If you want to prevent the SirTune data collector from being initialized, do either of the following:

  • Under z/OS or OS/390, include no SIRTUNED DD statement during initialization.
  • Set the SIRTUNE parameter to 0.

    SIRTUNE, which is only allowed as a parameter in the EXEC JCL statement, controls whether the SirTune data collector is initialized at the start of a Model 204 run.

    The SIRTUNE parameter can be set to either of these values:

    0 Disables initialization of the integrated SirTune product for a particular run.
    1 Enables initialization (this is the default).

    For example:

    //ONLINE EXEC PGM=ONLINE,PARM='SIRTUNE=0'

The SirTune DD statements

SirTune uses one or both of the DD statements described below.

Note: The SIRTUNEO dataset used in earlier versions of SirTune is obsolete in versions of SirTune after 1.5.

  • SIRTUNED

    This required DD specifies the data set that receives the data collected by SirTune. This data set must have variable blocked (VB) format, and it should generally have a large block size (>10000). If DCB information is not explicitly specified, the defaults selected by SirTune should be adequate for all but the most extreme cases.

    If SIRTUNED is preallocated under ISPF or its equivalent, the recommended blocksizes are 23,476 on a 3380 and 27,998 on a 3390. If this dataset fills up, SirTune will simply stop collecting data for the duration of the run. A 20 megabyte SIRTUNED should be sufficient for most shops, while a 50 megabyte SIRTUNED should be sufficient for almost any requirements.

    Since the only cost of running out of space in SIRTUNED is the loss of some data, it's not worth spending a lot of time trying to size SIRTUNED exactly. Simply allocate SIRTUNED at 20 megabytes (or less if disk space is tight), and adjust the size based on experience. For more information on sizing SIRTUNED, see SirTune size requirement for SIRTUNED. To keep available data from several runs, make SIRTUNED part of a GDG.

  • SIRTUNEI

    This optional DD specifies a data set that contains statements that alter the SirTune defaults. These statements allow control over the name of the Model 204 load module, the level of detail to which data is collected, the time intervals over which data is collected, the sampling rate, authorization to issue MODIFY commands, and more. For a list of the available statements, see SirTune configuration statements.

    SIRTUNEI can have either fixed or variable format, and it can have any record length.

Version 1.5 or earlier of SirTune

The data collection portion of SirTune consists of a single load module called SIRTUNE.

Invoking the SIRTUNE module

To have SirTune collect data for a particular Online job, you must do the following so that SirTune will run Model 204 as a subtask of SIRTUNE, collecting polling data as required:

  • Modify the JCL that invokes Model 204 so that it invokes SIRTUNE instead. For example, to have SirTune monitor an Online invoked with:

    //ONLINE EXEC PGM=ONLINE,REGION=4096K,TIME=1440, // PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'

    change the line to read:

    //ONLINE EXEC PGM=SIRTUNE,REGION=4096K,TIME=1440, // PARM='LIBUFF=600,SYSOPT=155,NJBUFF=2'

  • Place the SIRTUNE load module into the same load library as the Online load library, or concatenate the library containing the SIRTUNE load module with the Model 204 load library.

SirTune data collection should have no significant impact on the performance of the Online region.

If the Model 204 load module that is being monitored with SirTune must run authorized, the SIRTUNE load module must be placed into an APF-authorized library.

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

The SIRTUNE DD statements

The SIRTUNE load module uses as many as three DD statements: the first (SIRTUNED) is required and specifies the data set to receive the collected data; the other two are optional:

SIRTUNED See SIRTUNED, above.
SIRTUNEI See SIRTUNEI, above.
SIRTUNEO This optional DD receives informational SIRTUNE messages. If this DD is not specified, these messages go to the MVS job log. SIRTUNEO must have LRECL greater than or equal to 80.

JCL example

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

//DAILY204 JOB (0),CLASS=C,MSGCLASS=A //BATCH204 EXEC PGM=SIRTUNE,REGION=4096K, // PARM='SYSOPT=209,LIBUFF=1000' //STEPLIB DD DSN=M204.V410.LOADLIB,DISP=SHR // DD DSN=SIRIUS.LOAD,DISP=SHR //SIRTUNEI DD * PGM BATCH204 /* //SIRTUNED DD DSN=SIRTUNE.SAMPLE.DATA,DISP=SHR //CCAPRINT DD SYSOUT=* //CCAAUDIT DD SYSOUT=* //CCASNAP DD SYSOUT=* //CCATEMP DD UNIT=WORK,SPACE=(CYL,(40,0)) //CCASTAT DD DSN=M204.CCASTAT.DISP=SHR //POPDATA DD DSN=LOCAL.PROD.POPDATA,DISP=SHR //POPPROC DD DSN=LOCAL.PROD.POPPROC,DISP=SHR //CCAIN DD * SPCORE=20000,MAXBUF=1000,MINBUF=50,SERVSIZE=300000 ..... //

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=SirTune_data_collection_under_MVS&oldid=103694"