For local testing (testing performed on the workstation) of character-based (block mode) applications, the recommended method is to package several procedures (and all of their procedure steps) into one load module. This recommendation has to do with performance of generated code because of the number and size of load modules.
During generation, each load module becomes an executable file. When a load module is called, it must be loaded into memory. When the next load module is called, it, in turn, is loaded while the previous load module is removed from memory.
If the load modules are too small, a performance penalty occurs when loading and reloading executable files.
In contrast, if the load modules are too big (for example, if you package all procedure steps into one load module), the executable file may be too large to fit into available memory, or the load module may exceed the size requirements of the compiler.
|
Copyright © 2013 CA.
All rights reserved.
|
|