[mod.computers.vax] INSTALLing language-specific RTLs

LLACROIX%carleton.edu@RELAY.CS.NET (Les LaCroix) (09/19/86)

Here's something that all VMS system managers really should be aware of
but maybe aren't.  You know all those DEC-supplied language specific RTLs?
Well, they're not all INSTALLed, let alone INSTALLed /SHARE.  Of course
you probably don't want them *all* INSTALLed.  But, unless you've looked
at which ones are being used, I bet you don't have *enough* of them installed.

Which RTLs you use regularly will depend not only on the local software
you develop but also on the other software you run (DEC utilities, DEC
layered products, third-party software--did I leave anything out?).
That means that you are probably using RTLs corresponding to compilers
that you don't even have.  To compound the problem, DEC's idea of which
RTLs should automatically be installed has been conservative, or at least
it has in the past.

I recently helped do a performance study at a nearby VMS 4.3 site.  We
found that one library (FORRTL, I believe) was INSTALLed but not /SHARE.
During the study we periodically did a LIST/FULL from within INSTALL.  I never
saw the current shared count drop below 5; the maximum shared count was
just under 20!  Now, *there's* a potential for conserving memory.

Of course, we would never have known this was happening if FORRTL
hadn't been INSTALLed in the first place.  After seeing it at this
site, we went home and looked at our own machines.  It turns out
that we weren't sharing FORRTL either, even though we are primarily
a FORTRAN shop...how embarrasing.

What we recommended to the site was that they go ahead and INSTALL
all of the DEC RTLs and run for awhile, and then do LIST/FULL in INSTALL
to find out just what is being used.  Based on what they find, take
steps necessary to have the heavily used images INSTALLed (possibly with
/SHARE) during system startup.  We also recommended that they should
not "deINSTALL" the images that DEC chose to install, since maybe DEC
had a good reason for installing them.

I'm not going to say just what those steps are because a) it's been a long time
since I've actually had to do system management and I don't want to misinform
anyone; b) the "correct" way to do it is probably in a manual somewhere;
and c) this message is already too long.  Good luck, campers!

Les LaCroix                |   csnet:  llacroix@carleton.edu
SPSS, Inc.                 |   uucp:   ...{ihnp4,decvax}!stolaf!ccnfld!llacroix
402 Washington Street      |
Northfield, MN 55057-2027  |   "I don't work here--I just use the net."

garry@TCGOULD.TN.CORNELL.EDU (Garry Wiegand) (09/22/86)

In a recent article LLACROIX%carleton.edu@RELAY.CS.NET (Les LaCroix) wrote:
>Here's something that all VMS system managers really should be aware of
>but maybe aren't.  You know all those DEC-supplied language specific RTLs?
>Well, they're not all INSTALLed, let alone INSTALLed /SHARE...

As far as I know, all of them that come with the normal base system are
indeed Installed, and none of them are given the /SHARE qualifier.

At least one reason they are installed is because of the check the image-
activator makes on privileged images that reference them:

  "Shareable images must be installed to run privileged image"

I found this out the hard way - I deinstalled one that Install itself
references - lo and behold, *no way* to put it back :-)