Consultor Eletrônico

Execution Buffer - Desc wrong in Port Guide 2.10.4 ( -mmax )

The PROGRESS Portability Guide, Chapter 2, "Operating System
Portability," Section 2.10.4, "R-code Execution," on page
2-15, should read as follows:

2.10.4 R-Code Execution

PROGRESS no longer uses the edit buffer for r#code compilation
or execution. Instead PROGRESS uses a separate execution
buffer. As a result, the Edit Buffer (-e) parameter no
longer affects the space available for r#code. The number
of r#code procedures that you can run at one time and the
memory used is determined by the following factors:

Segment descriptors

PROGRESS uses a segment descriptor for each segment that
it places in memory. The segment descriptor table size
is limited to 480 entries.

Execution buffer ceiling

PROGRESS dynamically allocates memory for r#code segments
in the execution buffer. You can set a ceiling for this
buffer with the Maximum Memory (-mmax) startup parameter.
The default is 512K. When you start a procedure, PROGRESS
loads all of the necessary segments into memory. While
the procedure is active (running, or waiting for a called
procedure to return), the action cell segment and text
segment are locked in memory and cannot be swapped out.
Other cells may be swapped in and out of the execution
buffer as space is needed. If the size of all essential
segments for all active procedures exceeds the -mmax limit,
then PROGRESS automatically allocates additional memory
beyond the ceiling.

Available memory

Available memory is only a factor if it is smaller than
the execution buffer ceiling or PROGRESS needs to allocate
memory beyond that ceiling.


For more information regarding the -mmax startup parameter, see page
2-54 of the "PROGRESS System Administartion Reference".

Progress Software Technical Support Note # 12357