Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!rochester!udel!burdvax!bpa!drexel!rickers
From: rickers@drexel.UUCP (Rick Wargo)
Newsgroups: comp.databases
Subject: Re: UNIFY lockrec
Message-ID: <568@drexel.UUCP>
Date: 21 Mar 88 18:17:35 GMT
References: <316@fairlight.oz> <6656@charlie.OZ>
Organization: Drexel University, Phila., Pa.
Lines: 28
Keywords: UNIFY, lockrec

In article <6656@charlie.OZ>, wayne@charlie.OZ (Ian Jennings) writes:
>We have experienced this here as well. We are running ACCELL/Unify3.2 on
>our Gould PN6040. Within the Accell scripts we carry out locking. We also
>have a UNIFY 'C' program that runs simultaneously performing inquiries on
>related records and updates on non-related records. i.e. (that is related
>to those of the Accell scripts). We have found here that everything runs
>O.K. until we get about 8-10 users running our Accell application
>whereupon the same problem arises.

I have had the same problem.  We had been working on a large ACCELL project
for a while (ACCELL/Unify 3.2 on a Compact 386 running uPort 286/AT-U2.2)
with a few background daemons running that had to access the database.  We
found that we had two large problems.  One was t whenever the ACCELL code l
was accessing the record I wanted (the HLI daemon) ACCELL would let me use it.
As a matter a fact, it would let me use it ever after that until the user
went back to the initial screen and committed the transaction.  What a bad
workaround.  We waited for the new realease of ACCELL/Unify and our new uPort
operating system, but we haven't given it a try.

The other problem was that these daemons couldn't access the database while
they were running in the background.  When they ran in the foreground they
worked fine.  This was a while ago.  I was on the phone with Unify Tech Support
and had managed to figure out why this happened, but for the life of me, I
just can't remember the explanation on we had decided. Sorry.  Maybe it will
hit me sooner or later, probably later when we restart the project.

							Rickers
							..!drexel!rickers