Next: ANALYSIS_CONTROL Interface to
Up: Some Advanced Features
Previous: Using BLREADs in
Many of the utilities that ANALYSIS_CONTROL links to support VMS sharable
image versions of their libraries. The advantages of using them are:
- They reduce user linking time since symbols in the images are already
resolved.
- The size of the users resulting EXE is much smaller, so they save on
disk space.
- Without relinking it is possible to change the size of any YBOS
array or use a debug version of the utility instead of a nondebug version
by simply redefining a logical name.
- If a bug fix is made to a utility the user does not have to relink
their job. They will get the change as soon as they rerun it.
- If many of the jobs on the system are using the same utility
(eg. YBOS) there should be an increase in performance. The program
should run faster since VMS will not have to make as many disk accesses.
For those who would like to link to sharable images of the
utilities instead of the libraries here is the procedure:
Make sure that you are happy with the size of the YBOS arrays that are
setup in your BUILD_JOB procedure. BUILD_JOB creates a commands file
that must be executed before linking and running with sharable images.
This file defines all of the logicals you need to link or run your job.
Then when you run LINK_ANA add the SHR key to the optional library list.
For example:
$ @MYMOD_BUILD_JOB_OUTPUT
$ LINK_ANA MYMOD MYMOD N "SHR,PAW,HBK4,..."
If you want to take advantage of number 3. above, you just redefine
<utility>$library to be <utility>$debuglib just before you run the job;
however there are some extra debugger commands you will need to use in
order to debug a problem inside the image. For this reason it is probably
best that you bring the problem to the appropriate consultant if you
believe there is a bug that requires you to look at utility code.
Next: ANALYSIS_CONTROL Interface to
Up: Some Advanced Features
Previous: Using BLREADs in
sexton@fnal.gov