Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!utastro!bigtex!pmafire!mike
From: mike@pmafire.UUCP (mike caldwell)
Newsgroups: comp.databases
Subject: Re: Problem with UNIFY
Summary: UNIFY support
Keywords: UNIFY report
Message-ID: <771@pmafire.UUCP>
Date: 20 Sep 89 14:05:46 GMT
References: <669@ncs.dnd.ca>
Reply-To: mike@pmafire.UUCP (mike caldwell)
Distribution: comp.databases
Organization: WINCO, INEL, Idaho
Lines: 45

In article <669@ncs.dnd.ca> bacic@ncs.dnd.ca (Eugen Bacic) writes:
>
>
>My wife is having some problems with UNIFY and perhaps someone else out
>
> ... Description of problem
>
>In the error log, error code 126 and 25 say: "Unable to open shell".
>NCR's UNIX experts are pointing the finger at UNIFY; unfortunately UNIFY
>is pointing the finger at NCR's port of UNIX, or the particular
>application (which is written in UNIFY and C)...
>
>UNIFY is also indicating that the problem is unique to my wife's site,
>however she knows of at least one other such problem here in Ottawa.
>They haven't solved that problem either...
>
>                                        Eugen Bacic


We had a very similiar problem with UNIFY and because of there lack of
support, we dropped them and went to another database vendor.  We were
trying to interface an application using both C and UNIFY and it
wouldn't even compile.  We would comment out the calls to the UNIFY
library and it would compile fine.  UNIFY insisted that it was our
problem or the OS vendors problem and that it was unique to our site.
After a lot of time with nm and a dissasembler I tracked the problem
down to a couple of global variables that no longer existed and
hadn't been officially included in the operating system for a couple
of years.

So we went back to UNIFY again (couldn't be unique, if it was missing
from the OS) and told them what the problem was and asked when they
were going to update the product to work with the current version of
the OS.  They had already had a couple of years to update.  They
informed us that it was the OS vendors responsibility to maintain
backward compatibility and we were SOL if the vendor wouldn't.  Like I
said, we bought a different database.

Mike



-- 
Mike Caldwell (mike@pmafire.UUCP)
Paths: ...uunet!pmafire!mike | ...!ucdavis!egg-id!pmafire!mike