User statistics displayed in SirMon - Revision history

JAL: typos

2017-06-12T22:30:49Z

typos

← Older revision		Revision as of 22:30, 12 June 2017
Line 170:		Line 170:

	<tr><th>FLGS</th>		<tr><th>FLGS</th>
	<td>User flags modifying the thread's current wait. This statistic is displayed in hexadecimal. If the thread is not currently waiting,		<td>User flags modifying the thread's current wait. This statistic is displayed in hexadecimal. If the thread is not currently waiting, the flags displayed are the result of the threads most recent wait. The bits in the flag byte have the following meaning:
	the flags displayed are the result of the threads most recent wait. The bits in the flag byte have the following meaning:
	<p class="code"><nowiki>X'80' - Always enter scheduler even if ECB posted		<p class="code"><nowiki>X'80' - Always enter scheduler even if ECB posted
	X'40' - The wait is swappable		X'40' - The wait is swappable
Line 367:		Line 366:

	<tr><th>PNAME</th>		<tr><th>PNAME</th>
	<td>Name of the currently executing or last executed procedure. PNAME can be followed by a number indicating the number of bytes of the procedure name to be displayed and an optional 'L' or 'R' to indicate whether		<td>Name of the currently executing or last executed procedure. PNAME can be followed by a number indicating the number of bytes of the procedure name to be displayed and an optional 'L' or 'R' to indicate whether the leftmost or rightmost bytes of the procedure name should be displayed. For example, PNAME20 and PNAME20L would display the leftmost 20 bytes of the procedure name and PNAME9R would display the rightmost 9 bytes of the procedure name.
	the leftmost or rightmost bytes of the procedure name should be displayed. For example, PNAME20 and PNAME20L would display the leftmost 20 bytes of the procedure name and PNAME9R would display		<p>
	the rightmost 9 bytes of the procedure name. The requested length must be between 6 and 32 inclusive. PNAME is the same as PNAME16L.		The requested length must be between 6 and 32 inclusive. PNAME is the same as PNAME16L. All procedure names are actually the leftmost 32 or LAUDPROC bytes of the true procedure name whichever is shorter. </p>
	All procedure names are actually the leftmost 32 or LAUDPROC bytes of the true procedure name whichever is shorter.		<p>
	To save screen space, SIRMON limits the display of PNAME to LAUDPROC bytes, even when the user requests a longer display. The default for LAUDPROC is 21.</td></tr>		To save screen space, SIRMON limits the display of PNAME to LAUDPROC bytes, even when the user requests a longer display. The default for LAUDPROC is 21.</p></td></tr>

	<tr><th>PRTY</th>		<tr><th>PRTY</th>

JAL: minor formatting

2017-06-12T19:48:31Z

minor formatting

← Older revision		Revision as of 19:48, 12 June 2017
Line 73:		Line 73:

	<tr><th>CCATDIFF</th>		<tr><th>CCATDIFF</th>
	<td>Difference between CCATEMP pages allocated and freed by the thread. This is an imperfect indicator of the number of CCATEMP pages a thread has allocated. ~~Imperfect~~ because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, threads with high CCATDIFF values are likely culprits. ~~Under Model 204 7.8 and later the SLCCATD and SLCCATDH since-last statistics provide alternatives for trying to track down threads responsible for an acute CCATEMP page shortage.<br/>~~		<td>Difference between CCATEMP pages allocated and freed by the thread. This is an imperfect indicator of the number of CCATEMP pages a thread has allocated. CCATDIFF is imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, threads with high CCATDIFF values are likely culprits.
	<p>		<p>
	~~Only~~ available in Model 204 7.7 and ~~later~~.</p></td></tr>		Under Model 204 7.8 and later, the SLCCATD and SLCCATDH since-last statistics provide alternatives for trying to track down threads responsible for an acute CCATEMP page shortage.</p>
			<p>
			CCATDIFF is available in Model 204 7.7 and higher.</p></td></tr>

	<tr><th>CFRALL</th>		<tr><th>CFRALL</th>
	<td>Returns a 16 character string that describes the thread's critical file resource holdings. If a thread holds or is attempting to obtain a critical file resource lock,		<td>Returns a 16-character string that describes the thread's critical file resource holdings. If a thread holds or is attempting to obtain a critical file resource lock, this statistic returns the name of the file associated with the critical file resource, followed by 6 characters that indicate the mode for the various critical file resource locks: Direct, Index, Exists, Recenq, Allod, and Alloe. These characters contain '<tt>.</tt>' meaning not held, 'X' meaning exclusive, or 'S' meaning share.</td></tr>
	this statistic returns the name of the file associated with the critical file resource followed by 6 characters that indicate the mode for the various critical file resource locks
	- Direct, Index, Exists, Recenq, Allod, and Alloe. These characters contain ~~either~~ '.' meaning not held, 'X' meaning exclusive, or 'S' meaning share.</td></tr>

	<tr><th>CFRCONF</th>		<tr><th>CFRCONF</th>
Line 86:		Line 86:

	<tr><th>CFRDIER</th>		<tr><th>CFRDIER</th>
	<td>Returns a 12 character string that describes the thread's critical file resource activity.		<td>Returns a 12-character string that describes the thread's critical file resource activity.
	If a thread holds or is attempting to obtain a critical file resource lock, this statistic returns the name of the file associated with the critical file resource followed by 4 characters		If a thread holds or is attempting to obtain a critical file resource lock, this statistic returns the name of the file associated with the critical file resource followed by 4 characters
	that indicate the mode in which the thread holds the 4 critical file resource locks - Direct, Index, Exists and Recenq (hence the DIER in CFRDIER).		that indicate the mode in which the thread holds the four critical file resource locks: Direct, Index, Exists, and Recenq (hence the DIER in CFRDIER).
	The characters indicating the lock mode are '.' meaning not held, 'X' meaning exclusive and 'S' meaning share.</td></tr>		The characters indicating the lock mode are '.' meaning not held, 'X' meaning exclusive, and 'S' meaning share.</td></tr>

	<tr><th>CFRWTT</th>		<tr><th>CFRWTT</th>
Line 412:		Line 412:

	<tr><th>RCLKSRE</th>		<tr><th>RCLKSRE</th>
	<td>Number of		<td>Number of single record entries in the record locking table. Single record entries are associated with locked individual records such as used in a FOR RECORD NUMBER statement, or the exclusive lock obtained on a record being updated in a FOR EACH RECORD loop.</td></tr>
	single record entries in the record locking table. Single record entries are associated with locked individual records
	such as used in a FOR RECORD NUMBER statement, or the exclusive lock obtained on a record being updated in a FOR EACH RECORD loop.</td></tr>

	<tr><th>RECADD</th>		<tr><th>RECADD</th>
Line 516:		Line 514:
	<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.		<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.
	<p>		<p>
	~~Only available~~ in Model 204 7.8 and later.</p></td></tr>		Available only in Model 204 7.8 and later.</p></td></tr>

	<tr><th>SLCCATDH		<tr><th>SLCCATDH
	<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.		<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.
	<p>		<p>
	~~Only available~~ in Model 204 7.8 and later.</p></td></tr>		Available only in Model 204 7.8 and later.</p></td></tr>

	<tr><th>SLCMMITS</th>		<tr><th>SLCMMITS</th>

Alex at 18:27, 12 June 2017

2017-06-12T18:27:11Z

← Older revision		Revision as of 18:27, 12 June 2017
Line 75:		Line 75:
	<td>Difference between CCATEMP pages allocated and freed by the thread. This is an imperfect indicator of the number of CCATEMP pages a thread has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, threads with high CCATDIFF values are likely culprits. Under Model 204 7.8 and later the SLCCATD and SLCCATDH since-last statistics provide alternatives for trying to track down threads responsible for an acute CCATEMP page shortage.<br/>		<td>Difference between CCATEMP pages allocated and freed by the thread. This is an imperfect indicator of the number of CCATEMP pages a thread has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, threads with high CCATDIFF values are likely culprits. Under Model 204 7.8 and later the SLCCATD and SLCCATDH since-last statistics provide alternatives for trying to track down threads responsible for an acute CCATEMP page shortage.<br/>
	<p>		<p>
	Only ~~avalailable~~ in Model 204 7.7 and later.</p></td></tr>		Only available in Model 204 7.7 and later.</p></td></tr>

	<tr><th>CFRALL</th>		<tr><th>CFRALL</th>
Line 516:		Line 516:
	<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.		<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.
	<p>		<p>
	Only ~~avalailable~~ in Model 204 7.8 and later.</p></td></tr>		Only available in Model 204 7.8 and later.</p></td></tr>

	<tr><th>SLCCATDH		<tr><th>SLCCATDH
	<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.		<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.
	<p>		<p>
	Only ~~avalailable~~ in Model 204 7.8 and later.</p></td></tr>		Only available in Model 204 7.8 and later.</p></td></tr>

	<tr><th>SLCMMITS</th>		<tr><th>SLCMMITS</th>

Alex at 18:26, 12 June 2017

2017-06-12T18:26:12Z

← Older revision		Revision as of 18:26, 12 June 2017
Line 516:		Line 516:
	<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.		<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.
	<p>		<p>
	Only avalailable in Model 204 7.7 and later.</p></td></tr>		Only avalailable in Model 204 7.8 and later.</p></td></tr>

	<tr><th>SLCCATDH		<tr><th>SLCCATDH
	<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.		<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.
	<p>		<p>
	Only avalailable in Model 204 7.7 and later.</p></td></tr>		Only avalailable in Model 204 7.8 and later.</p></td></tr>

	<tr><th>SLCMMITS</th>		<tr><th>SLCMMITS</th>

Alex at 00:14, 12 June 2017

2017-06-12T00:14:08Z

← Older revision		Revision as of 00:14, 12 June 2017
Line 71:		Line 71:
	<tr><th>BXSPLI</th>		<tr><th>BXSPLI</th>
	<td>Node splits in the ordered index by the user (rate or total).</td></tr>		<td>Node splits in the ordered index by the user (rate or total).</td></tr>

			<tr><th>CCATDIFF</th>
			<td>Difference between CCATEMP pages allocated and freed by the thread. This is an imperfect indicator of the number of CCATEMP pages a thread has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, threads with high CCATDIFF values are likely culprits. Under Model 204 7.8 and later the SLCCATD and SLCCATDH since-last statistics provide alternatives for trying to track down threads responsible for an acute CCATEMP page shortage.<br/>
			<p>
			Only avalailable in Model 204 7.7 and later.</p></td></tr>

	<tr><th>CFRALL</th>		<tr><th>CFRALL</th>
Line 507:		Line 512:
	<td>"Since-Last" version of BXRFND (ordered index node splits). Since-Last stats reflect activity in the current work unit.		<td>"Since-Last" version of BXRFND (ordered index node splits). Since-Last stats reflect activity in the current work unit.
	When the work unit (typically a compilation or evaluation) completes, the Since-Last stats are output to the journal and reset to 0. The WHAT stat contains the work unit type.</td></tr>		When the work unit (typically a compilation or evaluation) completes, the Since-Last stats are output to the journal and reset to 0. The WHAT stat contains the work unit type.</td></tr>

			<tr><th>SLCCATD
			<td>Difference between CCATEMP pages allocated and freed in the request. This is an imperfect indicator of the number of CCATEMP pages a request has allocated. Imperfect because it is difficult to fully account for pages allocated or freed on behalf of the system or other users. However, if there is an acute CCATEMP page shortage, requests with high SLCCTAD values are likely culprits.
			<p>
			Only avalailable in Model 204 7.7 and later.</p></td></tr>

			<tr><th>SLCCATDH
			<td>High water mark of SLCCATD in a request. This can be useful if a request allocated a lot of CCATEMP pages, causing an acute shortage but then freed those pages. Of course, the most likely time such a request will free its pages is at end of request so this statistic is probably more useful when looking at the journal than in SirMon.
			<p>
			Only avalailable in Model 204 7.7 and later.</p></td></tr>

	<tr><th>SLCMMITS</th>		<tr><th>SLCMMITS</th>
Line 516:		Line 531:
	When the work unit (typically a compilation or evaluation) completes, the Since-Last stats are output to the journal and reset to 0. The WHAT stat contains the work unit type.		When the work unit (typically a compilation or evaluation) completes, the Since-Last stats are output to the journal and reset to 0. The WHAT stat contains the work unit type.
	This stat is collected in milliseconds but presented by SirMon in seconds.</td></tr>		This stat is collected in milliseconds but presented by SirMon in seconds.</td></tr>

	<tr><th>SLCPU</th>		<tr><th>SLCPU</th>
	<td>"Since-Last" stat for CPU consumed while in current work unit. Since-Last stats reflect activity in the current work unit.		<td>"Since-Last" stat for CPU consumed while in current work unit. Since-Last stats reflect activity in the current work unit.

JAL: `for menu items`


2017-06-06T19:35:43Z
<code> for menu items

				
				
				
				
				
				← Older revision
				Revision as of 19:35, 6 June 2017
				
Line 3:
Line 3:
state within the Online for that particular user. state within the Online for that particular user.



In [[RKWeb]], you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button. In [[RKWeb]], you can display all the user statistics and view their descriptions by selecting <code>Performance > Custom</code> from the <code>Monitor</code> tab, then clicking the <b>Users</b> radio button.



<table class="thJustBold"> <table class="thJustBold">



JAL: add link
2017-06-06T15:17:32Z
add link

				
				
				
				
				
				← Older revision
				Revision as of 15:17, 6 June 2017
				
Line 3:
Line 3:
state within the Online for that particular user. state within the Online for that particular user.



In RKWeb, you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button. In [[RKWeb]], you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button.



<table class="thJustBold"> <table class="thJustBold">



JAL: mention RKWeb equivalents
2017-05-11T23:39:09Z
mention RKWeb equivalents

				
				
				
				
				
				← Older revision
				Revision as of 23:39, 11 May 2017
				
Line 1:
Line 1:
<!--Page automatically generated by CMSTOWIK EXEC and will be 
** 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: User statistics displayed in SirMon --> 
User statistics provide information about each user logged on to the Online system. User statistics provide information about each user logged on to the Online system.
The value of each user statistic is determined by the activity and The value of each user statistic is determined by the activity and
state within the Online for that particular user. state within the Online for that particular user.

In RKWeb, you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button.



<table class="thJustBold"> <table class="thJustBold">



Admin: 1 revision: SirMon pages
2015-09-10T22:05:22Z
1 revision: SirMon pages

				
				← Older revision
				Revision as of 22:05, 10 September 2015
				
(No difference)



JAL at 23:58, 8 September 2015
2015-09-08T23:58:47Z

Show changes

← Older revision		Revision as of 19:35, 6 June 2017
Line 3:		Line 3:
	state within the Online for that particular user.		state within the Online for that particular user.

	In [[RKWeb]], you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button.		In [[RKWeb]], you can display all the user statistics and view their descriptions by selecting <code>Performance > Custom</code> from the <code>Monitor</code> tab, then clicking the <b>Users</b> radio button.

	<table class="thJustBold">		<table class="thJustBold">

← Older revision		Revision as of 15:17, 6 June 2017
Line 3:		Line 3:
	state within the Online for that particular user.		state within the Online for that particular user.

	In RKWeb, you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button.		In [[RKWeb]], you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button.

	<table class="thJustBold">		<table class="thJustBold">

← Older revision		Revision as of 23:39, 11 May 2017
Line 1:		Line 1:
	~~<!--Page automatically generated by CMSTOWIK EXEC and will be~~
	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: User statistics displayed in SirMon -->~~
	User statistics provide information about each user logged on to the Online system.		User statistics provide information about each user logged on to the Online system.
	The value of each user statistic is determined by the activity and		The value of each user statistic is determined by the activity and
	state within the Online for that particular user.		state within the Online for that particular user.

			In RKWeb, you can display all the user statistics and view their descriptions by selecting Performance > Custom from the Monitor tab, then clicking the <b>Users</b> radio button.

	<table class="thJustBold">		<table class="thJustBold">

← Older revision	Revision as of 22:05, 10 September 2015
(No difference)

User statistics displayed in SirMon - Revision history

JAL: typos

JAL: minor formatting

Alex at 18:27, 12 June 2017

Alex at 18:26, 12 June 2017

Alex at 00:14, 12 June 2017

JAL: for menu items

JAL: add link

JAL: mention RKWeb equivalents

Admin: 1 revision: SirMon pages

JAL at 23:58, 8 September 2015

JAL: `for menu items`