Cannot use memory-mapped procedure library if r-code codepage doesn't match -cpinternal

Cannot use memory-mapped procedure library if r-code codepage doesn't match -cpinternal
Trying to do so results in "Code page  for memory-mapped r-code does not match -cpinternal . (9073)"
This can prevent the use of memory-mapped .pls in deployments where multiple codepages are used.
 

Memory-mapped libraries are normally used to reduce overall resource consumption on machines where multiple OpenEdge clients run - meaning: terminal servers, classic AppServer/classic WebSpeed hosts, etc. (See  How does using memory mapped shared libraries affect performance ? for more information)

If r-code and session codepage do not match, r-code Text segments need to be converted to session codepage (-cpinternal).
There's no codepage conversion mechanism in place to do this for memory-mapped procedure libaries.

Upgrade to OpenEdge 10.2B or later. 

In current releases the codepage conversion is implemented:
- If the codepages do not match the text segment gets cloned to the session's -mmax pool in private memory, where the conversion then is performed.
- If the codepages do match, the text segment is read directly from the shared memory instead.

Therefore, using matching codepages is still recommended for maximum efficiency.
 

References to Other Documentation:

Progress Article(s):
 How does using memory mapped shared libraries affect performance ?