The set-runaway-limit command in the DM account establishes the maximum number of frames allowed before an overflow runaway condition occurs. If the number of frames acquired by the specified process when either writing or retrieving an item reaches the specified limit, the system detects an overflow runaway condition and reports it. This command can be applied globally to all lines or locally to the current line. See set-runaway-autoquit Command for more information.
All overflow runaway conditions are logged to the errors file.
Syntax
set-runaway-limit {limit} (options |
Parameter(s)
limit |
Maximum number of frames allowed before a overflow runaway condition occurs. If 0 (zero) is specified, there is no maximum. If left blank, the current maximum setting is displayed. |
|
options |
pib |
Sets the specified limit on the specified port. |
d |
Specifies the default runaway limit (7000). |
|
l |
Specifies setting the runaway limit locally for the current line (instead of globally). |
|
r |
Removes the limit on the line executing the command, allowing it to use the global limit. |
|
If no parameters are provided with the command, the current limit displays.
CAUTION |
If a process creates a very large item, or select list, it may hit the specified limit. The command has to be aborted, the limit changed, and the command restarted. The default is normally set to a value which should suit most configurations. |
Example(s)
Displays the current global limit.
set-runaway-limit [110] Overflow runaway limit set to 7000 Frames |
Sets the runaway limit to 5000 for the current line.
set-runaway-limit 5000 |
Sets the default runaway limit for the current line.
set-runaway-limit (d |
Removes any local runaway limit set on the current line, allowing it to use the global limit.
set-runaway-limit (r |
See Also