SirTune data collection under CMS: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (more conversion cleanup)
m (misc cleanup)
Line 4: Line 4:
<!-- Page name: Sirtune data collection under CMS -->
<!-- Page name: Sirtune data collection under CMS -->


As of the integration of the <var class="product">SirTune</var> data collector with the <var class="product">[[Sirius Mods]]</var>.
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.
(in <var class="product">Sirius Mods</var> version 6.9), how you invoke <var class="product">SirTune</var> depends on its version.


==Versions of SirTune after 1.5==
==Versions of SirTune 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.
It also requires a load module called SIRTUNED, which runs in a separate
It also requires a load module called <code>SIRTUNED</code>, which runs in a separate service machine.
service machine.
The data collector becomes available once the <var class="product">Sirius Mods</var> is link edited into the <var class="product">Model 204</var> <code>ONLINE</code> module and once the SIRTUNED service machine is made available.
The data collector becomes available once the <var class="product">Sirius Mods</var> is link edited into the <var class="product">Model 204</var> ONLINE module
and once the SIRTUNED service machine is made available.


<div id="stuncms"></div>
<div id="stuncms"></div>
Line 26: Line 24:
(which is described in [[#istncms|Invoking the SIRTUNE module]]).
(which is described in [[#istncms|Invoking the SIRTUNE module]]).


<var class="product">SirTune</var> also requires the presence of a virtual machine running the
<var class="product">SirTune</var> also requires the presence of a virtual machine running the SIRTUNED load module (as described in [[#stundvm|The SIRTUNED virtual machine]]).
SIRTUNED load module (as described in [[#stundvm|The SIRTUNED virtual machine]]).
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.
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.
<ul>
<ul>
Line 33: Line 30:
<p>
<p>
No changes are necessary to any <var class="product">SirTune</var> DDs you were using.
No changes are necessary to any <var class="product">SirTune</var> DDs you were using.
However, if you specified SIRTUNEI configuration statements for the data collector,
However, if you specified <code>SIRTUNEI</code> configuration statements for the data collector,
the PGM statement is ignored, since <var class="product">SirTune</var> no longer loads the <var class="product">Model 204</var> ONLINE load module.</p></li>
the PGM statement is ignored, since <var class="product">SirTune</var> no longer loads the <var class="product">Model&nbsp;204</var> ONLINE load module.</p></li>


<li>If you want to prevent the <var class="product">SirTune</var> data collector from being initialized:
<li>If you want to prevent the <var class="product">SirTune</var> data collector from being initialized:
<p>
<p>
Set the SIRTUNE parameter to 0.</p>
Set the <var>[[SIRTUNE parameter|SIRTUNE]]</var> parameter to 0.</p>
<p>
<p>
The SIRTUNE parameter, which controls whether the <var class="product">SirTune</var> data collector is initialized at the start of a <var class="product">Model 204</var> run, can be set to either of these values:</p>
The <var>SIRTUNE</var> parameter, which controls whether the <var class="product">SirTune</var> data collector is initialized at the start of a <var class="product">Model&nbsp;204</var> run, can be set to either of these values:</p>
<table class="thJustBold">
<table class="thJustBold">
<tr><th>0</th>
<tr><th>0</th>
Line 58: Line 55:
<!--Caution: <div> above-->
<!--Caution: <div> above-->
<p>
<p>
<var class="product">SirTune</var> has the optional DD described below, for which a
<var class="product">SirTune</var> has the optional DD described below, for which a FILEDEF can be added to M204FDEF EXEC or any other
FILEDEF can be added to M204FDEF EXEC or any other
EXEC invoked before the ONLINE module.</p>  
EXEC invoked before the ONLINE module.</p>  
<p class="note"><b>Note:</b> The SIRTUNEO DD used in earlier versions of <var class="product">SirTune</var> is obsolete in versions of <var class="product">SirTune</var> after 1.5.</p>
<p class="note"><b>Note:</b> The SIRTUNEO DD used in earlier versions of <var class="product">SirTune</var> is obsolete in versions of <var class="product">SirTune</var> after 1.5.</p>
Line 76: Line 72:


==Version 1.5 or earlier of SirTune==
==Version 1.5 or earlier of SirTune==
<p></p>
The data collection portion of <var class="product">SirTune</var> consists of:
The data collection portion of <var class="product">SirTune</var> consists of a load
<ul>
module called SIRTUNE that runs in the <var class="product">Model 204</var> ONLINE virtual machine
<li>A load module called <code>SIRTUNE</code>, which runs in the <var class="product">Model&nbsp;204</var> <code>ONLINE</code> virtual machine or virtual machines.
or virtual machines
 
and another load module called SIRTUNED which runs in a separate service
<li>A load module called <code>SIRTUNED</code>, which runs in a separate service machine.
machine.
</ul>


<div id="istncms"></div>
<div id="istncms"></div>
Line 123: Line 119:
<table class="thJustBold">
<table class="thJustBold">
<tr><th>SIRTUNEI</th>
<tr><th>SIRTUNEI</th>
<td>See [[#stdd|Optional <var class="product">SirTune</var> DD name]].</td></tr>
<td>See [[#stdd|Optional SirTune DD name]].</td></tr>


<tr><th>SIRTUNEO</th>
<tr><th>SIRTUNEO</th>
Line 137: Line 133:
<!--Caution: <div> above-->
<!--Caution: <div> above-->
<p>
<p>
<var class="product">SirTune</var> requires the presence of a virtual machine
<var class="product">SirTune</var> requires the presence of a virtual machine running the SIRTUNED load module. It is recommended that this virtual machine be given the userid <code>SIRTUNED</code>.
running the SIRTUNED load module. It is recommended that this virtual
machine be given the userid <code>SIRTUNED</code>.
The installation tape contains
The installation tape contains
a sample exec called SIRTUNED EXEC which can be used as PROFILE EXEC
a sample exec called <code>SIRTUNED EXEC</code> which can be used as PROFILE EXEC for this service machine.</p>
for this service machine.</p>
<p>
<p>
This service machine communicates with
This service machine communicates with all running ONLINE virtual machines running <var class="product">SirTune</var>, saving their
all running ONLINE virtual machines running <var class="product">SirTune</var>, saving their
sample data to disk.
sample data to disk.
Because of this, appropriate directory statements
Because of this, appropriate directory statements
must be added to the CP directory to allow IUCV communications between
must be added to the CP directory to allow IUCV communications between
the <var class="product">Model 204</var> virtual machines and the SIRTUNED virtual machine.
the <var class="product">Model 204</var> virtual machines and the SIRTUNED virtual machine.
The easiest way to accomplish this is by adding the IUCV ALLOW directory
The easiest way to accomplish this is by adding the <code>IUCV ALLOW</code> directory statement for user SIRTUNED.</p>
statement for user SIRTUNED.</p>
<p>
<p>
The sample SIRTUNED EXEC invokes the SIRTUNED MODULE as follows:</p>
The sample SIRTUNED EXEC invokes the SIRTUNED MODULE as follows:</p>
Line 157: Line 148:
</nowiki></p>
</nowiki></p>
To authorize users to issue commands to SIRTUNED via
To authorize users to issue commands to SIRTUNED via
SMSG, list the authorized users after the SIRTUNED command.
SMSG, list the authorized users after the <var>SIRTUNED</var> command.
The userids in the list can contain wildcard characters.
The user IDs in the list can contain wildcard characters.
For example,
For example, the following command authorizes user ID <code>SYSOPER</code> and any user ID beginning with the characters
<code>MARGE</code> to issue a command to SIRTUNED via SMSG.
<p class="code"><nowiki>'SIRTUNED SYSOPER MARGE*';
<p class="code"><nowiki>'SIRTUNED SYSOPER MARGE*';
</nowiki></p>
</nowiki></p>
authorizes userid SYSOPER and any userid begining with the characters
 
MARGE to issue a command to SIRTUNED via SMSG.
For more information about using wildcards in this list, see [[SirTune statement wildcards]].
For more information
on using wildcards in this list, see [[SirTune statement wildcards]].
<p>
<p>
SIRTUNED will use MSGNOH for its responses if it is authorized; otherwise
SIRTUNED will use MSGNOH for its responses if it is authorized; otherwise
Line 173: Line 163:
"cleanly" if the <var class="product">Model 204</var> virtual machines running <var class="product">SirTune</var> are themselves terminated cleanly.
"cleanly" if the <var class="product">Model 204</var> virtual machines running <var class="product">SirTune</var> are themselves terminated cleanly.
However, if it becomes necessary to terminate the SIRTUNED
However, if it becomes necessary to terminate the SIRTUNED
service machine while <var class="product">Model 204</var> virtual machines are running,
service machine while <var class="product">Model&nbsp;204</var> virtual machines are running, log onto SIRTUNED and issue any one of the following commands:</p>
log onto SIRTUNED and issue any one of the following commands:</p>
<ul>
<ul>
<li>QUIT
<li>QUIT
Line 181: Line 170:
<li>SHUTDOWN
<li>SHUTDOWN
</ul>
</ul>
<p class="note"><b>Note:</b> When SIRTUNED terminates, data collection on all <var class="product">Model 204</var> service
<p class="note"><b>Note:</b> When SIRTUNED terminates, data collection on all <var class="product">Model&nbsp;204</var> service
machines running <var class="product">SirTune</var> will be immediately terminated.
machines running <var class="product">SirTune</var> is immediately terminated.
They will, however, continue to run <var class="product">Model 204</var> without interruption.
They do, however, continue to run <var class="product">Model&nbsp;204</var> without interruption.
</p>
</p>
<p>
<p>
Every time an ONLINE running <var class="product">SirTune</var> is brought up, <var class="product">SirTune</var> attempts to establish an IUCV connection with SIRTUNED.
Every time an ONLINE running <var class="product">SirTune</var> is brought up, <var class="product">SirTune</var> attempts to establish an IUCV connection with SIRTUNED.
If it is unable to do so, the ONLINE is not brought up.
If it is unable to do so, the ONLINE is not brought up.
If a connection is established, SIRTUNED immediately invokes an EXEC called SIRTUNEF.
If a connection is established, SIRTUNED immediately invokes an EXEC called <code>SIRTUNEF</code>.
This exec can then issue FILEDEFs or other commands as required.</p>
This exec can then issue FILEDEFs or other commands as required.</p>
<p>
<p>
Line 194: Line 183:
file that will contain the <var class="product">SirTune</var> sample data.
file that will contain the <var class="product">SirTune</var> sample data.
The default DDNAME used
The default DDNAME used
for the open is the userid of the <var class="product">Model 204</var> service machine.
for the open is the user ID of the <var class="product">Model&nbsp;204</var> service machine.
The actual DDNAME can be modified with a <var class="product">SirTune</var>
The actual DDNAME can be modified with a [[SirTune configuration statements|SirTune statement]], and it is passed to SIRTUNEF.</p>
statement ([[SirTune configuration statements]]), and it is passed to SIRTUNEF.</p>
<p>
<p>
A sample SIRTUNEF is provided on the installation tape and
A sample SIRTUNEF is provided on the installation tape and
Line 202: Line 190:
SIRTUNEF is passed two parameters:</p>
SIRTUNEF is passed two parameters:</p>
<ul>
<ul>
<li>The userid of the <var class="product">Model 204</var> virtual machine </li>
<li>The user ID of the <var class="product">Model&nbsp;204</var> virtual machine </li>


<li>The DDNAME to be used for the open (that is, the name
<li>The DDNAME to be used for the open (that is, the name
Line 212: Line 200:
the ONLINE from coming up.
the ONLINE from coming up.
After SIRTUNEF returns to SIRTUNED, SIRTUNED attempts to open the appropriate DDNAME for output.
After SIRTUNEF returns to SIRTUNED, SIRTUNED attempts to open the appropriate DDNAME for output.
If this open fails, an open error is reflected to <var class="product">SirTune</var> and the IUCV
If this open fails, an open error is reflected to <var class="product">SirTune</var> and the IUCV connection is closed, preventing the ONLINE from coming up.
connection is closed, preventing the ONLINE from coming up.
<p>
In general, it is sufficient to allow the sample data sets to
reside on a CMS-format minidisk. Although data can be sent to tape,
delays in manual tape handling could result in hung <var class="product">Model&nbsp;204</var> virtual machines waiting for SIRTUNED to process a tape mount. </p>
<p>
<p>
In general, it is sufficient to allow the sample datasets to
Data can also be sent to OS-format minidisks.
reside on a CMS format minidisk. Although data can be sent to tape,
To do this, however, SIRTUNED must be run under the <var class="product">Model&nbsp;204</var> CMS interface (<code>M204CMS</code>). To do this, change this line in <code>SIRTUNED EXEC</code>: </p>
delays in manual tape handling could result in hung <var class="product">Model 204</var>
virtual machines waiting for SIRTUNED to process a tape mount.
Data can also be sent to OS format minidisks.
To do this, however, SIRTUNED must be run under the <var class="product">Model 204</var> CMS interface (M204CMS). To do this, change the line in SIRTUNED EXEC that reads: </p>
<p class="code"><nowiki>'SIRTUNED';
<p class="code"><nowiki>'SIRTUNED';
</nowiki></p>
</nowiki></p>
to read
To:
<p class="code"><nowiki>'M204CMS SIRTUNED';
<p class="code"><nowiki>'M204CMS SIRTUNED';
</nowiki></p>
</nowiki></p>
While it is somewhat more efficient to send sample data
While it is somewhat more efficient to send sample data
to an OS format minidisk than to a CMS format disk,
to an OS-format minidisk than to a CMS-format disk,
this advantage is probably outweighed in most cases
this advantage is probably outweighed in most cases
by the advantage of not having to preallocate space for each sample dataset.
by the advantage of not having to preallocate space for each sample dataset.
<p>
<p>
The sample datasets must be variable format and should generally have a large block size
The sample data sets must be variable format and should generally have a large block size (greater than 10000). 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. If a sample data set fills up or a CMS minidisk becomes full, the virtual machine(s) running <var class="product">SirTune</var> and associated with the full minidisk or data set will simply stop collecting data for the duration of the run.
(greater than 10000). If DCB information is not explicitly specified, the defaults
20 megabytes for each <var class="product">SirTune</var> sample data set
selected by <var class="product">SirTune</var> should be adequate for all but the most extreme cases. If a sample dataset fills up or a CMS minidisk becomes full,
should be sufficient for most shops, while 50 megabytes per data set should be sufficient for almost any requirements.</p>
the virtual machine(s) running <var class="product">SirTune</var> and associated with the full
minidisk or dataset will simply stop collecting data for
the duration of the run.
20 megabytes for each <var class="product">SirTune</var> sample dataset
should be sufficient for most shops, while 50 megabytes per dataset should be sufficient for almost
any requirements.</p>
<p>
<p>
Since the only cost of running out of space on SIRTUNED is the
Since the only cost of running out of space on SIRTUNED is the
loss of some data, it's not worth spending a lot of time trying to size SIRTUNED
loss of some data, it is not worth spending a lot of time trying to size SIRTUNED exactly. Simply allocate the SIRTUNED minidisk at 20 megabytes per <var class="product">Model 204</var> virtual machine for which data is to be collected (or less if disk space
exactly. Simply allocate the SIRTUNED minidisk at 20 megabytes per <var class="product">Model 204</var> virtual machine for which data is to be collected (or less if disk space
is tight), and adjust the size based on experience.</p>
is tight), and adjust the size based on experience.</p>
<p>
<p>
For more information on sizing SIRTUNED, see [[SirTune size requirement for SIRTUNED]].
For more information on sizing SIRTUNED, see [[SirTune size requirement for SIRTUNED]].
The sample SIRTUNEF EXEC on the installation tape is an example of how samples from several runs
The sample SIRTUNEF EXEC on the installation tape is an example of how samples from several runs can be kept simultaneously available.</p>
can be kept simultaneously available.</p>
<p>
<p>
If <var class="product">Model 204</var> ONLINE service machines are brought up (AUTOLOG'ed) automatically at system initialization and some of these virtual machines will run
If <var class="product">Model&nbsp;204</var> ONLINE service machines are brought up (by <code>AUTOLOG</code>) automatically at system initialization, and some of these virtual machines will run
with <var class="product">SirTune</var>, the SIRTUNED service machine must complete
with <var class="product">SirTune</var>, the SIRTUNED service machine must complete SIRTUNED initialization before any <var class="product">SirTune</var> in a <var class="product">Model&nbsp;204</var> virtual machine attempts to establish an IUCV connection to SIRTUNED.
SIRTUNED initialization before any <var class="product">SirTune</var> in a <var class="product">Model 204</var> virtual machine attempts to establish an IUCV connection to SIRTUNED.
Because SIRTUNED initialization is extremely quick, this can probably be guaranteed by placing an AUTOLOG command for SIRTUNED ahead of AUTOLOG commands for <var class="product">Model 204</var> service machines in the exec(s) executing the AUTOLOG.
Because SIRTUNED initialization is extremely quick, this can probably be guaranteed
To be even more certain, place a <code>CP SLEEP <i>x</i> SEC</code> after
by placing an AUTOLOG command for SIRTUNED ahead of AUTOLOG commands
for <var class="product">Model 204</var> service machines in the exec(s) doing the AUTOLOG'ing.
To be even more certain, a <code>CP SLEEP x SEC</code> can be placed after
the AUTOLOG of SIRTUNED to give SIRTUNED time to get through initialization, where
the AUTOLOG of SIRTUNED to give SIRTUNED time to get through initialization, where
<i>x</i> is some small number (1 is probably sufficient).</p>
<var class="term">x</var> is some small number (1 is probably sufficient).</p>
<p>
<p>
Using SIRTUNEA EXEC guarantees that the <var class="product">Model 204</var> service machines
Using <code>SIRTUNEA EXEC</code> guarantees that the <var class="product">Model&nbsp;204</var> service machines
won't be logged on until SIRTUNED has completed initialization.
are not logged on until SIRTUNED has completed initialization.
SIRTUNEA EXEC is invoked by SIRTUNED after it has completed initialization.
SIRTUNEA EXEC is invoked by SIRTUNED after it has completed initialization.
If the AUTOLOG commands for the <var class="product">Model 204</var> service machines are moved into SIRTUNEA EXEC, SIRTUNED is authorized to issue the appropriate AUTOLOGs, and
If the AUTOLOG commands for the <var class="product">Model 204</var> service machines are moved into SIRTUNEA EXEC, SIRTUNED is authorized to issue the appropriate AUTOLOGs, and
an AUTOLOG command for SIRTUNED is added to the initialization exec, then
an AUTOLOG command for SIRTUNED is added to the initialization exec, then
SIRTUNED will automatically be logged on, and it will initialize and then bring up
SIRTUNED is automatically logged on, and it will initialize and then bring up (AUTOLOG) the <var class="product">Model&nbsp;204</var> service machines.
(AUTOLOG) the <var class="product">Model 204</var> service machines.


==See also==
==See also==

Revision as of 19:35, 5 November 2015


As of the integration of the SirTune data collector with the Sirius Mods (in Sirius Mods version 6.9), 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. It also requires a load module called SIRTUNED, which runs in a separate service machine. The data collector becomes available once the Sirius Mods is link edited into the Model 204 ONLINE module and once the SIRTUNED service machine is made available.

Invoking SirTune

To invoke SirTune, the EXEC that invokes the Model 204 load module should do so directly:

M204CMS M204ONLN ...

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

SirTune also requires the presence of a virtual machine running the SIRTUNED load module (as described in The SIRTUNED virtual machine). 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 any SirTune DDs 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:

    Set the SIRTUNE parameter to 0.

    The SIRTUNE parameter, which controls whether the SirTune data collector is initialized at the start of a Model 204 run, 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:

    M204CMS M204ONLN ( SIRTUNE 0 ...

Optional SirTune DD name

SirTune has the optional DD described below, for which a FILEDEF can be added to M204FDEF EXEC or any other EXEC invoked before the ONLINE module.

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

SIRTUNEI This optional DD contains configuration statements that alter the SirTune defaults.

These statements (SirTune configuration statements) allow control over the name of the 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.

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

The following is a sample FILEDEF:

FILEDEF SIRTUNEI DISK SIRTUNE INPUT A

Version 1.5 or earlier of SirTune

The data collection portion of SirTune consists of:

  • A load module called SIRTUNE, which runs in the Model 204 ONLINE virtual machine or virtual machines.
  • A load module called SIRTUNED, which runs in a separate service machine.

Invoking the SIRTUNE module

To have SirTune collect data for a particular ONLINE machine, do the following:

  1. Place the SIRTUNE load module on a minidisk accessible to the virtual machine running Model 204.
  2. Modify the EXEC that invokes Model 204 so that it invokes SIRTUNE instead.

    For example, to have SIRTUNE monitor an ONLINE that is invoked with:

    M204CMS M204ONLN ( SYSOPT 155 LIBUFF 600

    Change the line to read:

    M204CMS SIRTUNE ( SYSOPT 155 LIBUFF 600

SIRTUNE will then invoke Model 204 collecting polling data as required.

SirTune data collection should have no significant impact on the performance of the ONLINE virtual machine.

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 allows leaving SIRTUNE in place in your EXECs while a temporary problem is being solved.

Optional SIRTUNE DD names

The SIRTUNE load module has some optional DDs. FILEDEFs can be added for these DDs to M204FDEF EXEC or any other EXEC invoked before SIRTUNE. The optional DDs are:

SIRTUNEI See Optional SirTune DD name.
SIRTUNEO This optional DD receives informational SIRTUNE messages. If this DD is not specified, SIRTUNE messages go to the virtual console. SIRTUNEO must have LRECL greater than or equal to 80.

The following is a sample FILEDEF:

FILEDEF SIRTUNEO FISK SIRTUNE LISTING A

The SIRTUNED virtual machine

SirTune requires the presence of a virtual machine running the SIRTUNED load module. It is recommended that this virtual machine be given the userid SIRTUNED. The installation tape contains a sample exec called SIRTUNED EXEC which can be used as PROFILE EXEC for this service machine.

This service machine communicates with all running ONLINE virtual machines running SirTune, saving their sample data to disk. Because of this, appropriate directory statements must be added to the CP directory to allow IUCV communications between the Model 204 virtual machines and the SIRTUNED virtual machine. The easiest way to accomplish this is by adding the IUCV ALLOW directory statement for user SIRTUNED.

The sample SIRTUNED EXEC invokes the SIRTUNED MODULE as follows:

'SIRTUNED';

To authorize users to issue commands to SIRTUNED via SMSG, list the authorized users after the SIRTUNED command. The user IDs in the list can contain wildcard characters. For example, the following command authorizes user ID SYSOPER and any user ID beginning with the characters MARGE to issue a command to SIRTUNED via SMSG.

'SIRTUNED SYSOPER MARGE*';

For more information about using wildcards in this list, see SirTune statement wildcards.

SIRTUNED will use MSGNOH for its responses if it is authorized; otherwise it will use MSG.

It is generally not important to terminate the SIRTUNED service machine "cleanly" if the Model 204 virtual machines running SirTune are themselves terminated cleanly. However, if it becomes necessary to terminate the SIRTUNED service machine while Model 204 virtual machines are running, log onto SIRTUNED and issue any one of the following commands:

  • QUIT
  • END
  • STOP
  • SHUTDOWN

Note: When SIRTUNED terminates, data collection on all Model 204 service machines running SirTune is immediately terminated. They do, however, continue to run Model 204 without interruption.

Every time an ONLINE running SirTune is brought up, SirTune attempts to establish an IUCV connection with SIRTUNED. If it is unable to do so, the ONLINE is not brought up. If a connection is established, SIRTUNED immediately invokes an EXEC called SIRTUNEF. This exec can then issue FILEDEFs or other commands as required.

After SIRTUNEF returns to SIRTUNED, SIRTUNED attempts to open the file that will contain the SirTune sample data. The default DDNAME used for the open is the user ID of the Model 204 service machine. The actual DDNAME can be modified with a SirTune statement, and it is passed to SIRTUNEF.

A sample SIRTUNEF is provided on the installation tape and should be modified to suit installation requirements. SIRTUNEF is passed two parameters:

  • The user ID of the Model 204 virtual machine
  • The DDNAME to be used for the open (that is, the name to be used on a FILEDEF command)

If SIRTUNEF sets a non-zero return code, SIRTUNED will return an open error to SIRTUNED and close the IUCV connection, preventing the ONLINE from coming up. After SIRTUNEF returns to SIRTUNED, SIRTUNED attempts to open the appropriate DDNAME for output. If this open fails, an open error is reflected to SirTune and the IUCV connection is closed, preventing the ONLINE from coming up.

In general, it is sufficient to allow the sample data sets to reside on a CMS-format minidisk. Although data can be sent to tape, delays in manual tape handling could result in hung Model 204 virtual machines waiting for SIRTUNED to process a tape mount.

Data can also be sent to OS-format minidisks. To do this, however, SIRTUNED must be run under the Model 204 CMS interface (M204CMS). To do this, change this line in SIRTUNED EXEC:

'SIRTUNED';

To:

'M204CMS SIRTUNED';

While it is somewhat more efficient to send sample data to an OS-format minidisk than to a CMS-format disk, this advantage is probably outweighed in most cases by the advantage of not having to preallocate space for each sample dataset.

The sample data sets must be variable format and should generally have a large block size (greater than 10000). If DCB information is not explicitly specified, the defaults selected by SirTune should be adequate for all but the most extreme cases. If a sample data set fills up or a CMS minidisk becomes full, the virtual machine(s) running SirTune and associated with the full minidisk or data set will simply stop collecting data for the duration of the run. 20 megabytes for each SirTune sample data set should be sufficient for most shops, while 50 megabytes per data set should be sufficient for almost any requirements.

Since the only cost of running out of space on SIRTUNED is the loss of some data, it is not worth spending a lot of time trying to size SIRTUNED exactly. Simply allocate the SIRTUNED minidisk at 20 megabytes per Model 204 virtual machine for which data is to be collected (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. The sample SIRTUNEF EXEC on the installation tape is an example of how samples from several runs can be kept simultaneously available.

If Model 204 ONLINE service machines are brought up (by AUTOLOG) automatically at system initialization, and some of these virtual machines will run with SirTune, the SIRTUNED service machine must complete SIRTUNED initialization before any SirTune in a Model 204 virtual machine attempts to establish an IUCV connection to SIRTUNED. Because SIRTUNED initialization is extremely quick, this can probably be guaranteed by placing an AUTOLOG command for SIRTUNED ahead of AUTOLOG commands for Model 204 service machines in the exec(s) executing the AUTOLOG. To be even more certain, place a CP SLEEP x SEC after the AUTOLOG of SIRTUNED to give SIRTUNED time to get through initialization, where x is some small number (1 is probably sufficient).

Using SIRTUNEA EXEC guarantees that the Model 204 service machines are not logged on until SIRTUNED has completed initialization. SIRTUNEA EXEC is invoked by SIRTUNED after it has completed initialization. If the AUTOLOG commands for the Model 204 service machines are moved into SIRTUNEA EXEC, SIRTUNED is authorized to issue the appropriate AUTOLOGs, and an AUTOLOG command for SIRTUNED is added to the initialization exec, then SIRTUNED is automatically logged on, and it will initialize and then bring up (AUTOLOG) the Model 204 service machines.

See also