CPTS parameter: Difference between revisions
Jump to navigation
Jump to search
m (Automatically generated page update) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:CPTS parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 10: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 V6.1</var> | <dd><var class="product">Model 204 V6.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
You can specify a time interval, in seconds, during which new transactions, both User Language and IFAM are prevented from starting. If non-zero, the CPTS parameter gives in-flight transactions a chance to end before they are forced into sub-transaction wait. If all transactions end during the specified interval, a transaction checkpoint is taken instead of a sub-transaction checkpoint.The parameter applies only when sub-transaction checkpoints are activated: that is CPTYPE=1. | You can specify a time interval, in seconds, during which new transactions, both User Language and IFAM are prevented from starting. If non-zero, the CPTS parameter gives in-flight transactions a chance to end before they are forced into sub-transaction wait. If all transactions end during the specified interval, a transaction checkpoint is taken instead of a sub-transaction checkpoint. The parameter applies only when sub-transaction checkpoints are activated: that is <var>[[CPTYPE_parameter|CPTYPE]]</var>=1. | ||
<p class="note"><b>Note:</b> When non multicursor IFAM updating threads are active the CPTS parameter may be ineffective, because for those threads transactions are always in progress.</p> | <p class="note"><b>Note:</b> When non multicursor IFAM updating threads are active the CPTS parameter may be ineffective, because for those threads transactions are always in progress.</p> | ||
[[Category:System | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 10:09, 14 October 2014
Sub-transaction timeout in seconds
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- User 0's parameter line, resettable
- Related products
- All
- Introduced
- Model 204 V6.1
Description
You can specify a time interval, in seconds, during which new transactions, both User Language and IFAM are prevented from starting. If non-zero, the CPTS parameter gives in-flight transactions a chance to end before they are forced into sub-transaction wait. If all transactions end during the specified interval, a transaction checkpoint is taken instead of a sub-transaction checkpoint. The parameter applies only when sub-transaction checkpoints are activated: that is CPTYPE=1.
Note: When non multicursor IFAM updating threads are active the CPTS parameter may be ineffective, because for those threads transactions are always in progress.