MONITOR TASKS command - Revision history

JAL: /* Usage notes */ maintask instead of main task

2015-06-17T19:23:17Z

Usage notes: maintask instead of main task

JAL: remove Sys Man guide

2014-11-17T18:47:52Z

remove Sys Man guide

Show changes

JALWiccan: Automatically generated page update

2013-04-20T01:30:24Z

Automatically generated page update

← Older revision		Revision as of 01:30, 20 April 2013
Line 117:		Line 117:
	</table>		</table>
	<p>MONITOR TASKS indicates a zIIP subtask by displaying a lowercase letter z beside the subtask number. </p>		<p>MONITOR TASKS indicates a zIIP subtask by displaying a lowercase letter z beside the subtask number. </p>
	<p>Most of the statistics described in the table above are also written to the journal (CCAJRNL) whenever system final or partial statistics are logged. For more information about statistics in journal entries and for general information about task off-loading and related MP concepts, refer to the <var>Model 204 System Manager's Guide</var>.</p>		<p>Most of the statistics described in the table above are also written to the journal (CCAJRNL) whenever system final or partial statistics are logged. For more information about statistics in journal entries and for general information about task off-loading and related MP concepts, refer to the <var class="book">Model 204 System Manager's Guide</var>.</p>
	==Example 2==		==Example 2==
	When the terminal is MODEL=2, as specified by the MODEL parameter, MONITOR TASKS displays the following columns. The LKWTIME and LKPTIME columns are not displayed.		When the terminal is MODEL=2, as specified by the MODEL parameter, MONITOR TASKS displays the following columns. The LKWTIME and LKPTIME columns are not displayed.

Alex: Automatically generated page update

2013-02-28T01:05:16Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System administrator
<dt>Function
<dd>Usage statistics for maintask, MP subtasks, and zIIP subtasks
</dl>
==Syntax==
MONITOR TASKS

==Example 1==
MONITOR TASKS

==Usage notes==
At installations using the MP (multiprocessing) or zIIP feature, the system administrator can use the MONITOR TASKS command to view usage information for all attached Online tasks, including the main task.
The MONITOR TASKS command displays the data shown in the table below. When the terminal is MODEL=2, as specified by the MODEL parameter, the ZDEQ, SDEQ, LKWTIME, LKPTIME, and ZIPCPU columns are not displayed.
<table>
<caption>MONITOR TASKS display information</caption>

<tr> <th>
Statistic
</th> <th>
Meaning
</th> </tr>

<tr> <th><var>
TASK
</var></th> <td>
The task number. 0 always denotes the main task, 1 the highest priority offload subtask, 2 the next highest priority subtask, and so forth.
</td> </tr>

<tr> <th><var>
CPU
</var></th> <td>
The total amount of CPU time used by the task (in milliseconds). For a zIIP subtask, this figure includes the CPU actually consumed on the zIIP engine (see ZIPCPU below), plus the overhead of running the zIIP subtask.
</td> </tr>

<tr> <th><var>
PR
</var></th> <td>
Total elapsed time during which the task has been available for offload processing.
</td> </tr>

<tr> <th><var>
PCPU
</var></th> <td>
CPU used, as a percentage of elapsed time (CPU/PR).
</td> </tr>

<tr> <th><var>
WAIT
</var></th> <td>
The number of times the task has issued a real operating system WAIT, excluding waits for MP locks.
</td> </tr>

<tr> <th><var>
POST
</var></th> <td>
The number of times the task issued a real operating system POST, excluding posts for MP locks.
</td> </tr>

<tr> <th><var>
LKWAIT
</var></th> <td>
The number of times the task issued a real operating system WAIT to wait for an MP lock to become available.
</td> </tr>

<tr> <th><var>
LKPOST
</var></th> <td>
The number of times the task issued a real operating system POST to indicate the availability of an MP lock to another task.
</td> </tr>

<tr> <th><var>
MQWTM
</var></th> <td>
The average length of time (in microseconds) required for a unit of work to get to the task from another task. This is a measure of queue delay between main task and subtasks.
</td> </tr>

<tr> <th><var>
DEQ
</var></th> <td>
The number of units of work taken by the corresponding task - main task, MP subtask, or zIIP subtask - regardless of the queue that the work was taken from.
</td> </tr>

<tr> <th><var>
ZDEQ
</var></th> <td>
The number of units of work taken from a zIIP queue by either the main task or an MP subtask. This column has meaning only for the main task and MP subtasks. For zIIP subtasks this column always contains a zero. Displayed only when the terminal is MODEL=5.
</td> </tr>

<tr> <th><var>
SDEQ
</var></th> <td>
The number of units of work taken from an MP subtask queue by the main task. This column has meaning only for the main task; for other tasks this column always contains a zero. Displayed only when the terminal is MODEL=5.
</td> </tr>

<tr> <th><var>
LKWTIME
</var></th> <td>
Lock wait time-Total elapsed time in milliseconds, this task spent waiting for MP locks. Displayed only when the terminal is MODEL=5.
</td> </tr>

<tr> <th><var>
LKPTIME
</var></th> <td>
Lock preemption time-Total elapsed time in milliseconds, this task spent waiting, due to operating system preemption. 
This is the elapsed time between when an MP lock becomes available (lock post) making the task ready to run, and when the task actually gets the CPU. That preemption delay is caused by the operating system dispatching other tasks ahead of this task. Displayed only when the terminal is MODEL=5.
</td> </tr>

<tr> <th><var>
ZIPCPU
</var></th> <td>
The total CPU time (in milliseconds) consumed by this zip engine. It is zero for MP subtasks and greater than zero when "z" precedes the task number and that zIIP subtask has been active (AMPSUBZ>0) at some point during the run. Displayed only when the terminal is MODEL=5.
</td> </tr>

</table>
MONITOR TASKS indicates a zIIP subtask by displaying a lowercase letter z beside the subtask number. 
Most of the statistics described in the table above are also written to the journal (CCAJRNL) whenever system final or partial statistics are logged. For more information about statistics in journal entries and for general information about task off-loading and related MP concepts, refer to the <var>Model 204 System Manager's Guide</var>.
==Example 2==
When the terminal is MODEL=2, as specified by the MODEL parameter, MONITOR TASKS displays the following columns. The LKWTIME and LKPTIME columns are not displayed.
 TASK CPU PR PCPU WAIT POST LKWAIT LKPOST MQWTM DEQ
0 234 834 280 76 14 0 0 179 78
1 0 6 0 10 8 0 0 8000 1
2 0 10 0 1 1 0 0 0 0
z 3 0 16 0 2 1 0 0 0 0
z 4 0 19 0 1 1 0 0 0 0

==zIIP processing information==
MONITOR TASKS displays three zIIP-related columns, ZDEQ, SDEQ, and ZIPCPU, on screens formatted as a 3270 Model 5 terminal.
See the preceding table for details on these statistics.
==Example 3==
The following display illustrates the output of a MONITOR TASKS command with zIIP processing statistics, as displayed on the terminal where MODEL=5. The LKWTIME and LKPTIME columns are also displayed.
TASK CPU PR PCPU WAIT POST LKWAIT LKPOST MQWTM DEQ ZDEQ SDEQ LKWTIME LKPTIME ZIPCPU
0 225 824 273 70 14 0 0 189 74 19 10 0 0 0
1 0 6 0 10 8 0 0 8000 1 0 0 0 0 0
2 0 10 0 1 1 0 0 0 0 0 0 0 0 0
z 3 0 16 0 2 1 0 0 0 0 0 0 0 0 0
z 4 0 19 0 1 1 0 0 0 0 0 0 0 0 0

[[Category: System administrator commands]]
[[Category:Commands]]

← Older revision		Revision as of 19:23, 17 June 2015
Line 17:		Line 17:
	==Usage notes==		==Usage notes==
	<p>		<p>
	At installations using the MP (multiprocessing) or zIIP feature, the system administrator can use the <var>MONITOR TASKS</var> command to view usage information for all attached Online tasks, including the ~~main task~~.</p>		At installations using the MP (multiprocessing) or zIIP feature, the system administrator can use the <var>MONITOR TASKS</var> command to view usage information for all attached Online tasks, including the maintask.</p>
	<p>		<p>
	The <var>MONITOR TASKS</var> command displays the data shown in the table below. When the terminal is <code>MODEL=2</code>, as specified by the <var>MODEL</var> parameter, the ZDEQ, SDEQ, LKWTIME, LKPTIME, and ZIPCPU columns are not displayed.</p>		The <var>MONITOR TASKS</var> command displays the data shown in the table below. When the terminal is <code>MODEL=2</code>, as specified by the <var>MODEL</var> parameter, the ZDEQ, SDEQ, LKWTIME, LKPTIME, and ZIPCPU columns are not displayed.</p>
Line 27:		Line 27:

	<tr> <th><var><p>TASK</p></var></th>		<tr> <th><var><p>TASK</p></var></th>
	<td><p>The task number. <i>0</i> always denotes the ~~main task~~, <i>1</i> the highest priority offload subtask, <i>2</i> the next highest priority subtask, and so forth.</p></td> </tr>		<td><p>The task number. <i>0</i> always denotes the maintask, <i>1</i> the highest priority offload subtask, <i>2</i> the next highest priority subtask, and so forth.</p></td> </tr>

	<tr> <th><var><p>CPU</p></var></th>		<tr> <th><var><p>CPU</p></var></th>
Line 52:		Line 52:

	<tr> <th><var><p>MQWTM</p></var></th>		<tr> <th><var><p>MQWTM</p></var></th>
	<td><p>The average length of time (in microseconds) required for a unit of work to get to the task from another task. This is a measure of queue delay between ~~main task~~ and subtasks.</p></td> </tr>		<td><p>The average length of time (in microseconds) required for a unit of work to get to the task from another task. This is a measure of queue delay between maintask and subtasks.</p></td> </tr>

	<tr> <th><var><p>DEQ</p></var></th>		<tr> <th><var><p>DEQ</p></var></th>
	<td><p>The number of units of work taken by the corresponding task - ~~main task~~, MP subtask, or zIIP subtask - regardless of the queue that the work was taken from.</p></td> </tr>		<td><p>The number of units of work taken by the corresponding task - maintask, MP subtask, or zIIP subtask - regardless of the queue that the work was taken from.</p></td> </tr>

	<tr> <th><var><p>ZDEQ</p></var></th>		<tr> <th><var><p>ZDEQ</p></var></th>
	<td><p>The number of units of work taken from a zIIP queue by either the ~~main task~~ or an MP subtask. This column has meaning only for the ~~main task~~ and MP subtasks. For zIIP subtasks this column always contains a zero. Displayed only when the terminal is <code>MODEL=5</code>.</p></td> </tr>		<td><p>The number of units of work taken from a zIIP queue by either the maintask or an MP subtask. This column has meaning only for the maintask and MP subtasks. For zIIP subtasks this column always contains a zero. Displayed only when the terminal is <code>MODEL=5</code>.</p></td> </tr>

	<tr> <th><var><p>SDEQ</p></var></th>		<tr> <th><var><p>SDEQ</p></var></th>
	<td><p>The number of units of work taken from an MP subtask queue by the ~~main task~~. This column has meaning only for the ~~main task~~; for other tasks this column always contains a zero. Displayed only when the terminal is <code>MODEL=5</code>.</p></td> </tr>		<td><p>The number of units of work taken from an MP subtask queue by the maintask. This column has meaning only for the maintask; for other tasks this column always contains a zero. Displayed only when the terminal is <code>MODEL=5</code>.</p></td> </tr>

	<tr> <th><var><p>LKWTIME</p></var></th>		<tr> <th><var><p>LKWTIME</p></var></th>