SirTune introduction: Difference between revisions
m (minor cleanup) |
m (misc formatting) |
||
| Line 10: | Line 10: | ||
<li>Data is collected in a running Online region. | <li>Data is collected in a running Online region. | ||
This data is obtained by "polling." | This data is obtained by "polling." | ||
That is, at regular intervals <var class="product">SirTune</var> examines the state of the Online | That is, at regular intervals <var class="product">SirTune</var> examines the state of the Online region and records data pertinent to this state. | ||
region and records data pertinent to this state. | |||
<p> | <p> | ||
The part of <var class="product">SirTune</var> that collects this data is called the | The part of <var class="product">SirTune</var> that collects this data is called the | ||
<b | <b>data collection</b> portion, which was integrated with the [[Sirius Mods]] prior to version 7.5 of <var class="product">Model 204</var>.</p> | ||
was integrated with the [[Sirius Mods]] prior to version 7.5 of <var class="product">Model 204</var>.</p> | |||
<p> | <p> | ||
Occasionally in the SirTune documentation, the product name "<var class="product">SirTune</var>" is also used to refer to just the data collection portion of the product.</li> | Occasionally in the SirTune documentation, the product name "<var class="product">SirTune</var>" is also used to refer to just the data collection portion of the product.</p></li> | ||
<li>After this data is collected, it is summarized and presented in a set of reports that indicate to a SOUL programmer the potential performance problem areas. | <li>After this data is collected, it is summarized and presented in a set of reports that indicate to a SOUL programmer the potential performance problem areas. | ||
These problem areas can generally be refined to an arbitrary level of | These problem areas can generally be refined to an arbitrary level of | ||
detail (for example, individual lines of code in a procedure). | detail (for example, individual lines of code in a procedure). | ||
<p> | <p> | ||
The part of <var class="product">SirTune</var> that summarizes and produces reports is called the | The part of <var class="product">SirTune</var> that summarizes and produces reports is called the <b>reporting</b> portion, which consists of a SOUL program named <code>SIRTUNEREPORT</code>, distributed in the <code>SIRIUS</code> file as part of <var class="product">UL/SPF</var>.</p></li> | ||
<b | |||
</ol> | </ol> | ||
| Line 51: | Line 48: | ||
<li>For versions of <var class="product">SirTune</var> after 7.0:</li> | <li>For versions of <var class="product">SirTune</var> after 7.0:</li> | ||
<ul> | <ul> | ||
<li>The <var class="product">SirTune</var> data collector is integrated with the | <li>The <var class="product">SirTune</var> data collector is integrated with the <var class="product">Sirius Mods</var>, and you <b>must</b> install the <var class="product">Sirius Mods</var>.</li> | ||
and you <b>must</b> install the Sirius Mods.</li> | |||
<li>The <var class="product">UL/SPF</var> file SIRIUS must be downloaded to make the SIRTUNEREPORT | <li>The <var class="product">UL/SPF</var> file <code>SIRIUS</code> must be downloaded to make the <code>SIRTUNEREPORT</code> program available for reporting.</li> | ||
program available for reporting.</li> | |||
</ul></li> | </ul></li> | ||
</ul> | </ul> | ||
Revision as of 16:38, 16 July 2015
The primary function of SirTune is to provide information to User Language (SOUL) programmers to make it easy for them to improve the performance of their programs. This is accomplished in two stages:
- Data is collected in a running Online region.
This data is obtained by "polling."
That is, at regular intervals SirTune examines the state of the Online region and records data pertinent to this state.
The part of SirTune that collects this data is called the data collection portion, which was integrated with the Sirius Mods prior to version 7.5 of Model 204.
Occasionally in the SirTune documentation, the product name "SirTune" is also used to refer to just the data collection portion of the product.
- After this data is collected, it is summarized and presented in a set of reports that indicate to a SOUL programmer the potential performance problem areas.
These problem areas can generally be refined to an arbitrary level of
detail (for example, individual lines of code in a procedure).
The part of SirTune that summarizes and produces reports is called the reporting portion, which consists of a SOUL program named
SIRTUNEREPORT, distributed in theSIRIUSfile as part of UL/SPF.
Versions
The SirTune documentation assumes that a site is running SirTune version 7.4 or later. Any documented feature or facility that requires a later version of SirTune will be clearly marked to indicate this.
For example, a statement that is only available in versions 7.5 and later of SirTune will have a sentence in its documentation such as, "This statement is only available in version 7.5 or later of SirTune." If a feature or parameter is not indicated as requiring any specific version of the SirTune, it can be assumed that it is available in all versions covered by this document: that is, versions 7.4 and later of SirTune.
System requirements
SirTune requires the following components to run:
- Mainframe operating systems — one of the following:
- z/OS
- CMS (releases currently supported by IBM) under z/VM
- Model 204 V6R1 or later, running in its Online or IFAM4 configuration.
- For versions of SirTune after 7.0:
- The SirTune data collector is integrated with the Sirius Mods, and you must install the Sirius Mods.
- The UL/SPF file
SIRIUSmust be downloaded to make theSIRTUNEREPORTprogram available for reporting.
SirTune topics
The SirTune 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 SirTune version, see the release notes.
For information about product error messages, see SirTune data collector messages.
- SirTune introduction
- SirTune data collection under MVS
- SirTune data collection under CMS
- SirTune data collection statements
- SirTune MODIFY and SMSG commands
- SirTune report generation
- SirTune reports
- SirTune user states
- SirTune and Model 204 quad types
- SirTune statement wildcards
- SirTune date processing