WorkStack: Difference between revisions
Jump to navigation
Jump to search
Gordon.dye (talk | contribs) |
Gordon.dye (talk | contribs) |
||
| Line 19: | Line 19: | ||
====Parameter==== | ====Parameter==== | ||
"Integer" is a whole number that represents the number of bytes that the work stack may contain. It must be greater than 499 and may be arbitrarily high (e.g. up to | "Integer" is a whole number that represents the number of bytes that the work stack may contain. It must be greater than 499 and may be arbitrarily high (e.g. up to 99 million bytes). | ||
====Technical Considerations==== | ====Technical Considerations==== | ||
Latest revision as of 00:04, 29 June 2015
The WorkStack specification allows you to change the size of the work stack, which keeps track of temporary variables that are passed and localized during user- defined function calls, concatenations, or complex expressions.
Checking Values
The following environmental variables may be used to check your workstacks during a BR! session.
- ENV$("STATUS.STACKS.WORKSTACK")
- ENV$("STATUS.STACKS.WORKSTACK.MAX")
- ENV$("STATUS.STACKS.WORKSTACK.USED")
- ENV$("STATUS.STACKS.WORKSTACK.AVAILABLE")
- ENV$("STATUS.STACKS.WORKSTACK.MAX_USAGE")
Also the command STATUS STACKS shows the current stack settings.
Syntax
Start-up Default
WorkStack 500000 (version 4.3+)
Parameter
"Integer" is a whole number that represents the number of bytes that the work stack may contain. It must be greater than 499 and may be arbitrarily high (e.g. up to 99 million bytes).
Technical Considerations
- WorkStack may be specified only in the BRConfig.sys file; it is not valid with the Config command.
- The amount of stack memory available depends upon several variables. You may need to monitor your memory usage to determine the optimal stack size for your needs.