$FunForc: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{DISPLAYTITLE:$FunForc}} | {{DISPLAYTITLE:$FunForc}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Cancel running or waiting [[Fast/Unload]] request</span> | ||
This cancels a ''[[Fast/Unload]]'' request which is either running or enqueued to run. | This cancels a ''[[Fast/Unload]]'' request which is either running or enqueued to run. |
Revision as of 21:21, 22 November 2011
Cancel running or waiting Fast/Unload request
This cancels a Fast/Unload request which is either running or enqueued to run.
The $FunForc function accepts one argument and returns a numeric result.
The only argument is a string that identifies the request number for the request to be cancelled. To cancel a request, a user must either have initiated the request or have system manager privileges. For example, the following code creates an asynchronous unload request, and then immediately cancels it:
%RC = $FunLoad('DATA',..,'ASYNC') IF %RC GE 0 THEN %RC = $FunForc(%RC) END IF
Syntax
<section begin="syntax" /> %RESULT = $FunForc(req_num) <section end="syntax" />
5 - User does not have privilege to cancel request 6 - Request not found
$FunForc immediately DETACH'es a Fast/Unload task while $FunPurg allows the Fast/Unload task to do a "clean" termination. Indiscriminate use of $FunForc could result in certain resources (such as sort work files) being left "in use". $FunForc should be used when $FunPurg cannot purge the request cleanly.