After locating r-code in a standard library, OpenEdge loads the member into local memory.

The following figure shows the load operation when executing r-code from a standard library.

Figure 1. Loading r-code from a standard library


As shown in the above figure, when a client process accesses a member from a standard library, OpenEdge loads the member into local memory for that individual client and executes the segments from local memory. OpenEdge does not swap segments to and from the r-code swap file unless you specify the PROLIB Swap (-pls) startup parameter. By default, OpenEdge reloads segments from the open library in local memory.

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.