When loading r-code from an archive 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. If the archive is not signed, this process is much faster than loading r-code from an operating system file. If the archive is signed, it will be validated and that has a cost that may impact performance.

When executing r-code from an archive library, OpenEdge accesses and executes the r-code segments in the execution buffer in local memory. OpenEdge may swap r-code segments to the r-code swap file.