bi38@sdcc12.ucsd.EDU (Macbeth Ylr) (07/25/89)
Abf has begun to act weird on us. When we call vifred from abf and save a form we get a SYSTEM-F-ABORT error and then: ingres error 9044 with 44 0x2c as the return value. Despite this the changes in the form seem to be saved. We are running ingres 5 under vms 4.6. We recently replaced the disk where the data files and user accounts reside (I don't know if this has anything to do with it though). Any ideas? thanks. Jude Poole jpoole@ucsd.edu jpoole@ucsd.bitnet
bg0l+@andrew.cmu.edu (Bruce E. Golightly) (07/25/89)
According to the manuals, that message means that a program (probably VIFRED in this context) could not be executed. Check file protections in the Ingres account and make sure that the executables are all really there. We had a case quite some time ago where a couple of things got "lost" during a disk to disk move. I have, unfortunately, found that Ingres error messages are sometimes less than useful. There seem to be things that return totally irrelevant errors every once in a while. When you get to the bottom of this one, please post a followup. Good luck and good hunting, Bruce
mitchell@wdl1.UUCP (Jo Mitchell) (07/27/89)
About two years ago (I can't remember what version we were on) we
had a problem similar to this. It turned out the job logical table
was filled up. Did you run checkenv already?
==============================================================================
// o ARPA: mitchell@wdl1.fac.ford.com
(O) ( )
/ \_____( ) "Mommy, mommy I don't want to go to Europe!"
o \ |
/\____\__/
_/_/ _/_/
~bi38@sdcc12.ucsd.EDU (Macbeth Ylr) (07/28/89)
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