FUNMAXT parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
m (typos)
Line 20: Line 20:
The timer starts from the initiation of the request, either via $Funload,
The timer starts from the initiation of the request, either via $Funload,
or via the <var>FastUnload</var> and <var>FastUnloadTask</var> methods
or via the <var>FastUnload</var> and <var>FastUnloadTask</var> methods
in the <var>RecordSet</var> class.
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 User Language Interface</var> requests.
placed on <var class="product">Fast/Unload User Language Interface</var> requests.


The purpose of <var>FUNMAXT</var> is to prevent user requests being &ldquo;hung up&rdquo;
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 [[Fast/Unload]] tasks or for unintentionally
long-running requests.
long-running requests.
Line 32: Line 32:
<li>The <var>MaxTime</var>
<li>The <var>MaxTime</var>
named parameter on the <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the
named parameter on the <var>FastUnload</var> and <var>FastUnloadTask</var> methods in the
R<var>ecordSet</var> class
<var>Recordset</var> class
<p class="code">* Make sure request completes in one minute
<p class="code">* Make sure request completes in one minute
%rc = %recset:funload(%inList, %outList, %reportList, 'NEBUFF=10', maxtime=60)
%rc = %recset:funload(%inList, %outList, %reportList, 'NEBUFF=10', maxtime=60)

Revision as of 17:08, 20 January 2015

Default Fast/Unload request timeout (seconds)

Summary

Default value
0
Parameter type
System
Where set
System manager resettable
Related products
Fast/Unload User Language 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 User Language 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 User Language 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.