When loading r-code from a standard procedure library, OpenEdge opens the library file and loads the required r-code segments into local memory. The library remains open until the end of your OpenEdge session or until you remove the library from the PROPATH. When OpenEdge needs to load an r-code segment for a member in that library, it accesses the open library in local memory. This process is much faster than loading r-code from an operating system file.

When executing r-code from a standard procedure library, OpenEdge accesses and executes the r-code segments in the execution buffer in local memory. OpenEdge does not swap r-code segments to 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.