FUNMAXT parameter: Difference between revisions
m (typos) |
m (UL Interface becomes SOUL Interface) |
||
| Line 9: | Line 9: | ||
<dd>System manager resettable | <dd>System manager resettable | ||
<dt>Related products | <dt>Related products | ||
<dd>[[Fast/Unload | <dd>[[Fast/Unload SOUL Interface]] | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">[[Sirius Mods]]</var> 6.7 | <dd><var class="product">[[Sirius Mods]]</var> 6.7 | ||
| Line 16: | Line 16: | ||
==Description== | ==Description== | ||
This is a numeric parameter (with valid values from 0 to 36000) that indicates | This is a numeric parameter (with valid values from 0 to 36000) that indicates | ||
the maximum amount of time, in seconds, a [[Fast/Unload | the maximum amount of time, in seconds, a <var class="product">[[Fast/Unload SOUL Interface]]</var> request is to be given to complete. | ||
complete. | The timer starts from the initiation of the request, either via <var>[[$Funload]]</var>, | ||
The timer starts from the initiation of the request, either via $Funload, | or via the <var>[[FastUnload (Recordset function)|FastUnload]]</var> and <var>[[FastUnloadTask (Recordset function)|FastUnloadTask]]</var> methods in the <var>Recordset</var> class. | ||
or via the <var>FastUnload</var> and <var>FastUnloadTask</var> methods | |||
in the <var>Recordset</var> class. | |||
The default value of <var>FUNMAXT</var>, 0, means that there will be no time limit | The default value of <var>FUNMAXT</var>, 0, means that there will be no time limit | ||
placed on <var class="product">Fast/Unload | placed on <var class="product">Fast/Unload SOUL Interface</var> requests. | ||
The purpose of <var>FUNMAXT</var> is to prevent user requests being "hung up" | The purpose of <var>FUNMAXT</var> is to prevent user requests being "hung up" | ||
indefinitely while queuing for busy [[Fast/Unload]] tasks or for unintentionally | indefinitely while queuing for busy <var class="product">[[Fast/Unload]]</var> tasks or for unintentionally long-running requests. | ||
long-running requests. | |||
<var>FUNMAXT</var> can be overridden for specific requests by using either of these: | <var>FUNMAXT</var> can be overridden for specific requests by using either of these: | ||
| Line 59: | Line 57: | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
[[Category:Fast/Unload | [[Category:Fast/Unload SOUL Interface]] | ||
Revision as of 21:07, 16 March 2015
Default Fast/Unload request timeout (seconds)
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- System manager resettable
- Related products
- Fast/Unload SOUL Interface
- Introduced
- Sirius Mods 6.7
Description
This is a numeric parameter (with valid values from 0 to 36000) that indicates the maximum amount of time, in seconds, a Fast/Unload SOUL Interface request is to be given to complete. The timer starts from the initiation of the request, either via $Funload, or via the FastUnload and FastUnloadTask methods in the Recordset class.
The default value of FUNMAXT, 0, means that there will be no time limit placed on Fast/Unload SOUL Interface requests.
The purpose of FUNMAXT is to prevent user requests being "hung up" indefinitely while queuing for busy Fast/Unload tasks or for unintentionally long-running requests.
FUNMAXT can be overridden for specific requests by using either of these:
- The MaxTime
named parameter on the FastUnload and FastUnloadTask methods in the
Recordset class
* Make sure request completes in one minute %rc = %recset:funload(%inList, %outList, %reportList, 'NEBUFF=10', maxtime=60)
- The sixth parameter on $Funload:
* Make sure request completes in one minute %rc = $funload('LABEL', %inList, %outList, %reportList, 'NEBUFF=10', 60)
A reasonable strategy would be to set FUNMAXT to a fairly low value, then selectively set it higher for requests that need more time. Of course, it can be very difficult to ensure that short-running requests complete quickly, if the Online also has long-running requests that might tie up all the Fast/Unload tasks. The odds are better if there are more Fast/Unload tasks (FUNTSKN bigger), but even with more tasks, these potential problems remain:
- If there are enough long running requests, all tasks might be tied up, anyway.
- Some of the Fast/Unload tasks might have trouble getting dispatched because there are more of them than CPUs to run them.