CFRWPCT parameter - Revision history

JAL: link repair

2015-05-20T20:30:51Z

link repair

← Older revision		Revision as of 20:30, 20 May 2015
Line 13:		Line 13:
	<dd><var class="product">Model 204 V6.1</var> or earlier		<dd><var class="product">Model 204 V6.1</var> or earlier
	</dl>		</dl>

	==Description==		==Description==
	<p>Specifies the percentage of servers, <var>[[~~NSERVS_parameter~~\|NSERVS]]</var>, that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.</p>		<p>
	<p>When you issue a <~~var~~>[[~~VIEW_parameter~~\|VIEW]]</~~var~~> ~~CFRWPCT~~ command, the value returned is the actual number of servers (CFRWPCT * NSERVS), not percentage, that might contain users in a non-swappable wait for CFR in EXCL mode.</p>		Specifies the percentage of servers (<var>[[NSERVS parameter\|NSERVS]]</var>) that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.</p>
			<p>
			When you issue a <code>[[VIEW command\|VIEW CFRWPCT]]</code> command, the value returned is the actual number of servers (<code>CFRWPCT * NSERVS</code>), not the percentage of, that might contain users in a non-swappable wait for CFR in EXCL mode.</p>

	====Performance tuning access to critical file resources====		====Performance tuning access to critical file resources====
	<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>		<p>
	<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>		The <var>CFRWPCT</var> parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>
			<p>
			When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, <var>CFRWPCT</var> can be set to allow up to 75 percent of <var>NSERVS</var> to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2014-10-14T08:22:23Z

Description

← Older revision		Revision as of 08:22, 14 October 2014
Line 14:		Line 14:
	</dl>		</dl>
	==Description==		==Description==
	<p>Specifies the percentage of servers, NSERVS, that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.</p>		<p>Specifies the percentage of servers, <var>[[NSERVS_parameter\|NSERVS]]</var>, that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.</p>
	<p>When you issue a VIEW CFRWPCT command, the value returned is the actual number of servers (CFRWPCT * NSERVS), not percentage, that might contain users in a non-swappable wait for CFR in EXCL mode.</p>		<p>When you issue a <var>[[VIEW_parameter\|VIEW]]</var> CFRWPCT command, the value returned is the actual number of servers (CFRWPCT * NSERVS), not percentage, that might contain users in a non-swappable wait for CFR in EXCL mode.</p>
	====Performance tuning access to critical file resources====		====Performance tuning access to critical file resources====
	<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>		<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>

DmeWiccan: Automatically generated page update

2013-08-27T16:25:25Z

Automatically generated page update

← Older revision		Revision as of 16:25, 27 August 2013
Line 1:		Line 1:
			{{Template:CFRWPCT parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

DmeWiccan: Automatically generated page update

2013-04-23T01:50:48Z

Automatically generated page update

← Older revision		Revision as of 01:50, 23 April 2013
Line 18:		Line 18:
	<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>		<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>
	<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>		<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>
	[[Category:System ~~Parameters~~]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Dme: Undo revision 56824 by DmeWiccan (talk)

2013-04-19T15:32:45Z

Undo revision 56824 by DmeWiccan (talk)

← Older revision		Revision as of 15:32, 19 April 2013
Line 18:		Line 18:
	<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>		<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>
	<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>		<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>
	[[Category:System ~~parameters~~]]		[[Category:System Parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DmeWiccan: Automatically generated page update

2013-04-19T14:38:24Z

Automatically generated page update

← Older revision		Revision as of 14:38, 19 April 2013
Line 18:		Line 18:
	<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>		<p>The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. </p>
	<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>		<p>When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.</p>
	[[Category:System ~~Parameters~~]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Alex: Automatically generated page update

2013-02-28T00:55:22Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>Set in CCAIN, not resettable, range 0-75 percent
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V6.1</var> or earlier
</dl>
==Description==
Specifies the percentage of servers, NSERVS, that can be occupied by non-swappable users waiting for exclusive access to a critical file resource (CFR). These file-level resources consist of DIRECT, EXISTS, INDEX, and RECENQ.
When you issue a VIEW CFRWPCT command, the value returned is the actual number of servers (CFRWPCT * NSERVS), not percentage, that might contain users in a non-swappable wait for CFR in EXCL mode.
====Performance tuning access to critical file resources====
The CFRWPCT parameter helps balance access to CFRs at a site. A CFR is acquired in SHR mode for read access and EXCL mode for update access. 
When many users have a CFR in SHR mode, users needing EXCL mode must wait and that wait is, by default, swappable. The result can be poor response time and increased system overhead due to server thrashing-users swapped in attempting to get a CFR in EXCL mode, then swapped out because the resource is unavailable, and repeating the cycle. To avoid this, CFRWPCT can be set to allow up to 75 percent of NSERVS to hold users waiting in a non-swappable wait for a CFR in EXCL mode.
[[Category:System Parameters]]
[[Category:Parameters]]