After locating a member in a memory-mapped library, OpenEdge loads the member by mapping the library in shared memory where one or more clients can access it.

The following image shows the load operation when executing a member from a memory-mapped library.

Figure 1. Loading r-code from a memory-mapped library


As shown in the above image, when one or more client processes access a member in a memory-mapped library, they access the same segments in shared memory. Because OpenEdge executes the segments from the mapped library in shared memory (not local memory), no reloading is necessary. If you specify the PROLIB Swap (-pls) startup parameter with memory-mapped libraries, OpenEdge ignores it.
Note: The AVM swaps codepage-converted text segments for procedure libraries from the execution buffer to the r-code swap file and reloads the converted text segments from the swap file instead of the library when necessary.