ENQTIME parameter: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204</var> version 7.8 (and available via maintenance in version 7.7) | <dd><var class="product">Model 204</var> version 7.8 (and available via maintenance in version 7.7 with zap 77Z299) | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
The <var>ENQTIME</var> parameter specifies the number of milliseconds waited for each automatic record locking retry wait. | |||
<var>ENQTIME</var> can be between 1 and 60000, corresponding to a minimum of 1 millisecond and a maximum of 1 minute. | |||
The default value of <var>ENQTIME</var> is 3000 (3 seconds). | |||
==Usage notes== | |||
<ul> | |||
<li>If record locking conflicts occur frequently in a busy Online, it is recommended that you decrease <var>ENQTIME</var> from its default value, which is 3000 (3 seconds). | |||
<p> | |||
Using that default value, any user with a non-zero value for <var>[[ENQRETRY parameter|ENQRETRY]]</var> will wait at least 3 seconds before the conflict is dealt with. This can degrade overall system performance. </p> | |||
<p> | |||
For example, assume <var>ENQRETRY</var> is 7. If you reset <var>ENQTIME</var> to 100: After a record locking conflict occurs, the thread may retry 7 times with wait intervals of 1/10 second. So within at | |||
most 7/10 seconds, the lock becomes available, or the | |||
conflict triggers an On unit or cancels the request. </p></li> | |||
<li>The <var>ENQTIME</var> parameter may also be reset with <var>[[$Resetn]]</var>. </li> | |||
</ul> | |||
[[Category:Parameters]] | [[Category:Parameters]] | ||
[[Category:User parameters]] | [[Category:User parameters]] | ||
Latest revision as of 15:13, 18 April 2018
Record locking retry wait time, milliseconds
Summary
- Default value
- 3000 (i.e., 3 seconds)
- Parameter type
- User
- Where set
- Any user
- Related products
- All
- Introduced
- Model 204 version 7.8 (and available via maintenance in version 7.7 with zap 77Z299)
Description
The ENQTIME parameter specifies the number of milliseconds waited for each automatic record locking retry wait.
ENQTIME can be between 1 and 60000, corresponding to a minimum of 1 millisecond and a maximum of 1 minute. The default value of ENQTIME is 3000 (3 seconds).
Usage notes
- If record locking conflicts occur frequently in a busy Online, it is recommended that you decrease ENQTIME from its default value, which is 3000 (3 seconds).
Using that default value, any user with a non-zero value for ENQRETRY will wait at least 3 seconds before the conflict is dealt with. This can degrade overall system performance.
For example, assume ENQRETRY is 7. If you reset ENQTIME to 100: After a record locking conflict occurs, the thread may retry 7 times with wait intervals of 1/10 second. So within at most 7/10 seconds, the lock becomes available, or the conflict triggers an On unit or cancels the request.
- The ENQTIME parameter may also be reset with $Resetn.