mw@ICS.UCI.EDU (Mark Wadsworth) (01/21/88)
We are running VAX Ada 1.3-24 on Micro-VMS 4.6 on a Microvax II. We recently
added another disk drive and configured the two non-system disks as a volume
set. After doing that, we began having trouble with the ACS LINK command.
For example, I have a package named MODDER that is used by a procedure named
VMS_MOD. After compiling MODDER and VMS_MOD, I give the command
$ ACS LINK VMS_MOD
ACS responds with
%ACS-I-CL_LINKING, Invoking the VAX/VMS Linker
%LINK-F-OPENIN, error opening SYS$USER:[ADA.MARK.VAXLIB]MODDER_.OBJ;1 as input
-RMS-E-FNF, file not found
<<job termination statistics>>
%ACS-E-CL_ERRDURLIN, Error(s) during LINK
The file named does exist. If I say
$ ACS LINK/COM VMS_MOD
$ @VMS_MOD
the link succeeds.
(The difference between these is that the first method builds an object file
containing the names of files to be linked in, and the second builds an object
file without file names and specifies the file names in the .COM file it
builds.)
I have not seen this fail on our VMS 4.6 system without a volume set, but it
fails on both Micro-VMS systems that have volume sets. (The VMS system is
not used much for Ada work.)
Does this suggest anything? Bugs in the linker? Problems in the way I set up
the volume set?