Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!helios.ee.lbl.gov!ucsd!sdcc6!sdcc12!bi38
From: bi38@sdcc12.ucsd.EDU (Macbeth Ylr)
Newsgroups: comp.databases
Subject: Re: Ingres abf prob
Message-ID: <910@sdcc12.ucsd.EDU>
Date: 27 Jul 89 21:52:10 GMT
References: <909@sdcc12.ucsd.EDU> <3560050@wdl1.UUCP>
Reply-To: bi38@sdcc12.ucsd.edu.UUCP (Macbeth Ylr)
Organization: University of California, San Diego
Lines: 16

I have found the problem.  When we changed the disks we discovered a
very odd VMS logical $disk2.  We have no idea where it was defined.
It was not it systartup.com, sylogin.com or any local login.com
files.  Several people with many years of VMS system management
experience could not find it.  Anyway it was in the sysuaf file and
therefor ended up in as sys$login for most users.  Thus abf created
source dirs by default with it.  Upon saving a form in vifred under
abf vifred tried to write out a .MAR file and failed ($disk2 now
pointing nowhere).  Vifred could only communicate the 44 return
code.  We discovered the problem when we tried to relink the app.

Thanks for all the help to those who responded.

Jude
jpoole@ucsd.edu
jpoole@ucsd.bitnet