Kbase P132250: -y startup parameter reports the incorrect Max Stack used value in client.mon
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/26/2009 |
|
Status: Unverified
SYMPTOM(s):
The Max Used value is always reported as ((-s) - 16), where -s is the stack size client session startup parameter.
FACT(s) (Environment):
The stack is an internal memory area used by ABL program modules.
The -y startup parameter writes statistics information to the default output file client.mon.
Using -y reports the Current, Max Used and Limit values for Stack usage.
The -y startup parameter is used for the client session.
All Supported Operating Systems
OpenEdge 10.1C
CAUSE:
Bug# OE00169040
CAUSE:
This is expected behavior. The Max Used value of -s will always reflect 16 bytes less than the total stack size if any string conversion is done (which is always the case when starting the Procedure Editor).
FIX:
The SHOW-STATS ABL command will cause the current stack usage, maximum stack usage and the stack limit (as specified by the -s startup parameter) to be written out to the client.mon file in the same manner as using the -y startup parameter.
To use the SHOW-STATS command properly you must invoke it once at the beginning of your code execution in order to open the client.mon file for output. The first execution of the SHOW-STATS command will not actually dump information into the client.mon file, it just opens the client.mon file for output.
To see the stack usage you should then insert the SHOW-STATS command at appropriate points in your application code. Each time you invoke the SHOW-STATS command, more information will be written to the client.mon file showing the current state of the stack.