Kbase P134686: Unable to run r-code with same filenames from different procedure libraries
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/29/2008 |
|
Status: Unverified
SYMPTOM(s):
Unable to run r-code with same filenames from different procedure libraries
R-code with same filename is contained in 2+ procedure libraries
Only r-code referenced first in the code is executed
Only r-code referenced first in the code is executed even though the name of the procedure library is specified
R-code from other procedure libraries is not executed
Example:
RUN pl1.pl<<module1.r>>.
RUN pl2.pl<<module1.r>>.
In this case, only the r-code from library pl1.pl is executed; the r-code in pl2.pl is not
Using memory-mapped procedure libraries has no effect
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CAUSE:
The first piece of r-code accessed is loaded into memory. The r-code is indexed in memory by filename. When the client comes to run the second piece of r-code with the same name, it searchs on 'module1.r' but finds that 'module.r' is already loaded and so re-runs the version already in memory.
FIX:
Use folders of different folders within each procedure library to separate the r-code. For example.
f1\module1.r
f2\module1.r
The example code would then change to this, which would return the correct results i.e. the r-code from libraries pl1.pl and pl2.pl is executed:
RUN pl1.pl<<f1\module1.r>>.
RUN pl2.pl<<f2\module1.r>>.