JAL: link repair

2017-08-08T20:56:53Z

link repair

← Older revision		Revision as of 20:56, 8 August 2017
Line 7:		Line 7:
	to issue certain commands to <var class="product">SirTune</var> while the ONLINE job is running.		to issue certain commands to <var class="product">SirTune</var> while the ONLINE job is running.
	Users can be authorized to do this with <var class="product">SirTune</var>'s AUTHORIZE command.		Users can be authorized to do this with <var class="product">SirTune</var>'s AUTHORIZE command.
	For more information on the AUTHORIZE command, see [[SirTune ~~configuration~~ statements]].		For more information on the AUTHORIZE command, see [[SirTune data collection statements]].

	Under MVS, these commands can be issued via the <code>MODIFY</code> operator command.		Under MVS, these commands can be issued via the <code>MODIFY</code> operator command.

ELowell at 21:49, 20 July 2016

2016-07-20T21:49:24Z

← Older revision		Revision as of 21:49, 20 July 2016
Line 93:		Line 93:
	</ul></li>		</ul></li>

	<li>The RESTART command will generally result in a [[Storing diagnostic information (CCASNAP ~~and CCAMDMP~~)\|CCASNAP]] being taken rather		<li>The RESTART command will generally result in a [[Storing diagnostic information (CCASNAP)\|CCASNAP]] being taken rather
	than (or in addition to) a SYSMDUMP, SYSUDUMP, or VMDUMP.		than (or in addition to) a SYSMDUMP, SYSUDUMP, or VMDUMP.
	CCASNAPs are generally easier to deal with than other types of dumps. </li>		CCASNAPs are generally easier to deal with than other types of dumps. </li>

JAL: misc formatting

2015-11-05T20:14:15Z

misc formatting

Show changes

JAL: more conversion cleanup

2015-07-03T00:09:24Z

more conversion cleanup

Show changes

Admin: 1 revision: SirTune doc

2015-07-02T17:47:04Z

1 revision: SirTune doc

← Older revision	Revision as of 17:47, 2 July 2015
(No difference)

JAL: /* See also */

2015-07-02T16:13:54Z

See also

New page

Users outside the <var class="product">Model 204</var> or SIRTUNE/<var class="product">Model 204</var> address space can be authorized
to issue certain commands to <var class="product">SirTune</var> while the ONLINE
job is running.
Users can be authorized to do this with <var class="product">SirTune</var>'s AUTHORIZE command.
For more information on the AUTHORIZE command, see [[SirTune configuration statements]].

Under MVS, these commands can be issued via the MODIFY operator
command.
This command can be issued at an operator console or
under SDSF or an equivalent virtual console system.
For example,
to issue the STATUS command to <var class="product">SirTune</var> running under job
PRODONLN under SDSF's LOG screen, you can simply enter
<nowiki>/MODIFY PRODONLN,STATUS
</nowiki>
or
<nowiki>/F PRODONLN,STATUS
</nowiki>
Responses to MODIFY commands go to the system log and should
be viewable under SDSF.

Under CMS, these commands can be issued via the SMSG CP command.
For example, to issue the STATUS command to <var class="product">SirTune</var> running on
a virtual machine named PRODONLN, you can enter
<nowiki>SMSG PRODONLN STATUS
</nowiki>
or
<nowiki>CP SMSG PRODONLN STATUS
</nowiki>
Responses to SMSG commands are sent via MSGNOH, if the <var class="product">SirTune</var>/<var class="product">Model 204</var> service
machine is authorized to use MSGNOH, and they are sent via MSG otherwise.

Available MODIFY/SMSG commands are listed here.
Optional statement parameters are enclosed in brackets (<code>[</code><code>]</code>).
Alternatives are separated with a vertical line (<code>|</code>).
==BUMP user_num==

This command requests that <var class="product">SirTune</var> issue the equivalent of the
<var class="product">Model 204</var> BUMP command against the indicated user number.
This command
is useful if a high priority user is looping in an ONLINE, making it
impossible for anyone else to do anything.
To "bump" user number 18, issue this command:
<nowiki>BUMP 18
</nowiki>

Unlike the <var class="product">Model 204</var> BUMP command, the <var class="product">SirTune</var> BUMP command
accepts only a single user number, and it does not accept userids or file names.
To determine the user number of the running user, issue <var class="product">SirTune</var>'s
MONITOR command.
It is recommended that the MONITOR command be issued
several times to ensure that a single user is indeed looping and
that a performance problem is not simply the result of excess demand.

If a loop situation is caused by a <var class="product">Model 204</var> bug, it is possible that
a BUMP command will fail to force the looping user off the system.
In this case, it might be necessary to issue the RESTART command to
break the loop.
==CLOSE==

This command requests that <var class="product">SirTune</var> close the sample dataset.
This makes it possible to run the report generator against a sample data
set that is still being updated by <var class="product">SirTune</var>.
This command has no effect on sampling activity in the <var class="product">Model 204</var> address space.
==MONITOR==

This command requests that <var class="product">SirTune</var> return information about what is
currently happening in <var class="product">Model 204</var>
This command is especially useful
if <var class="product">Model 204</var> appears to be hung or looping and, hence, it is impossible
to log on to <var class="product">Model 204</var> to determine the cause of the problem.

Information is returned for the main <var class="product">Model 204</var> task and any
subtasks (if the MP/204 feature is being used).
The information returned
indicates whether each task is running or waiting (corresponding to
looping and hung situations respectively) and where in the <var class="product">Model 204</var>
load module the task is running or waiting.
This latter piece of information
is most useful to <var class="product">Model 204</var> internals experts.

If any <var class="product">Model 204</var> task is indicated as running, information is also provided
on the user number and userid of the running user, the current activity
(evaluating, compiling, etc.), and the name of the procedure that is
currently running.
This information can be used to determine whether
a BUMP or RESTART command should be issued.
==RESTART abend_code USER user_num | TASK task_num==

This command requests that <var class="product">SirTune</var> issue the equivalent of a user abend
in <var class="product">Model 204</var> for the indicated user or task.
This command should be
used only as a last resort when a <var class="product">Model 204</var> ONLINE is looping or hung and all
efforts to clear up the situation have failed (see the BUMP command).
In this
situation, the only options left are to cancel (FORCE under CMS) the run or
to issue <var class="product">SirTune</var>'s RESTART command.
The RESTART command is preferable because:
<ul>
<li>The ONLINE might intercept the abend, possibly take a snap dump, and then
continue running.
<li>Even if the ONLINE does not continue, it might at least intercept the abend
and terminate "cleanly," preventing files from being broken and
eliminating the need to run recovery.
Cancelling or forcing the ONLINE ensure that any files
with active updating transactions will be left broken and that recovery will have
to be run before the ONLINE can be used again.
<li>The RESTART command will generally result in a CCASNAP being taken rather
than (or in addition to) a SYSMDUMP, SYSUDUMP, or VMDUMP.
CCASNAPs are generally
easier to deal with than other types of dumps.
</ul>

The abend_code value must be a 1- to 3-digit hexadecimal code that
indicates the abend code to be used for the artificially generated abend.
Under CMS
the abend code must be between 0C1 and 0CF.
Any dumps will indicate the specified abend code.
It is important to inform support personnel examining
the dump that the abend code was artificially generated by <var class="product">SirTune</var> and that
the situation was actually a hung or looping ONLINE.

To prevent accidentally terminating a user or an ONLINE, a user number can be
specified on the restart command.
When a user number is specified on the RESTART
command, no simulated abend will occur if the indicated user is not running in
the ONLINE.
For example, the following RESTART simulates a 0C4 abend if user 23 is running.
If user 23 is not running, no abend will be simulated.
<nowiki>RESTART 0C4 USER 23
</nowiki>

If no user is running (a hung ONLINE), it might be necessary to issue the RESTART
command with a task number instead.
Unless running MP/204, the task number must be specified as 0.
If MP/204 is running, the task number must be 0 (for the maintask)
or the subtask number (from 1 to NMPSUBS) to be restarted.
For example, the following RESTART simulates a 0A9 abend on the <var class="product">Model 204</var> maintask:
<nowiki>RESTART 0A9 TASK 0
</nowiki>
<blockquote class="note">Note: It is almost always
preferable to specify a user number on the RESTART command rather than a task number.
</blockquote>
==SAMPLE ON | OFF | AUTO==

This command either places sampling back into automatic mode (SAMPLE AUTO),
where sampling is controlled by INCLUDE/EXCLUDE statements in SIRTUNEI, or it
initiates (SAMPLE ON) or terminates (SAMPLE OFF) collection of sample data.
This command has no effect on the collection of compilation data: Compilation
data is collected regardless of the sampling state.

For example, to immediately start collecting data, the following command
should be issued:
<nowiki>SAMPLE ON
</nowiki>
To immediately stop collecting data, issue:
<nowiki>SAMPLE OFF
</nowiki>

After a SAMPLE ON or SAMPLE OFF command is issued, <var class="product">SirTune</var>
is in "manual" sampling mode.

==STATUS==

This command requests the current sampling status of <var class="product">SirTune</var>.
<var class="product">SirTune</var>'s response to this command indicates the current
sampling mode (AUTO or MANUAL), the current sampling state
(ON or OFF), and the number of samples collected to this point.

==STOP==

This command requests that <var class="product">SirTune</var> stop collecting both sampling
and compilation data and that it close the sample dataset.
After this command is issued, sampling cannot be restarted for the run.
Since the sample dataset is closed by a STOP command,
it is possible to use this dataset to generate reports after
a STOP command, even while the ONLINE job continues to run.

==See also==
{{Template:SirTune topic list}}

[[Category: SirTune]]

SirTune MODIFY and SMSG commands - Revision history

JAL: link repair

ELowell at 21:49, 20 July 2016

JAL: misc formatting

JAL: more conversion cleanup

Admin: 1 revision: SirTune doc

JAL: /* See also */