Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!NGP.UTEXAS.EDU!mike
From: mike@NGP.UTEXAS.EDU (wes birdwell)
Newsgroups: mod.computers.vax
Subject: VAX C .OLB Files missing in MicroVMS 4.4
Message-ID: <8607081432.AA10312@ngp.UTEXAS.EDU>
Date: Tue, 8-Jul-86 10:32:44 EDT
Article-I.D.: ngp.8607081432.AA10312
Posted: Tue Jul  8 10:32:44 1986
Date-Received: Wed, 9-Jul-86 07:29:34 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16
Approved: info-vax@sri-kl.arpa

Recently I installed MicroVMS 4.4 and VAX C 2.2 on our MicroVAX II.
I retained the definitions for LNK$LIBRARY and LNK$LIBRARY_1, etc, so
that the linker could find any unresolved function references in the
VAX C object libraries.  According to the installation guide for VAX C
these object libraries are new shipped with VMS, not VAX C.  However
the object libraries weren't on my system after the 4.4 installation.
I then searched all of the save sets on the release tape and they weren't
there either.  Then I called DEC and inquired about this and they didn't
really commit and say that the files were supposed to be there, only 
that we could link our programs with the shareable images.  I am familiar
with the advantages of doing this but what, if any, are the tradeoffs?
Is there any reason that I absolutely need these object libraries?
Has anyone else had a similar response from DEC?  Any any information
will be much appreciated.

Mike O'Donnell @ LCRA