|
There is presently no incremental linker for OpenVMS, though dynamic
linking is possible via the image activator and logical names, or via
the use of the lib$find_image_symbol dynamic-activation routine.
As an alternative, I'd suspect these folks need to look at moving to
shareable images (if they're not already using them) or increasing the
number of shareable images (if they are using them), and at the linking
process itself, as well as at the process working sets and quotas.
For customer-visible information on shareable images, see:
http://www.partner.digital.com/www-swdev/ -
pages/Home/TECH/faqs/ovms/ovms-shexe-cook.html
|
|
They may also want to look into optimizing their link environment a
little. It may well be time to defrag the freespace on the linker
target output disk, and how fragmetned are the input OBJs, OLBs?
Does the process running the linker still have adequat Working set
params or is it stuck at a few Mb defined many moons ago? Just check
the old CPU time versus elapsed time, IO counts, Pagefaults and the
likes. Fortunate enough to have a performance monitor going with
hot-file display? Perhpas create a DECram disk for popular linker
input files? Default file extend size bumped from 5 to 100 or so?
and so on...
Hein.
|