Path: utzoo!mnetor!uunet!munnari!mulga!charlie!wayne
From: wayne@charlie.OZ (Ian Jennings)
Newsgroups: comp.databases
Subject: Re: UNIFY lockrec
Message-ID: <6656@charlie.OZ>
Date: 18 Mar 88 03:14:35 GMT
References: <316@fairlight.oz>
Reply-To: wayne@charlie.UUCP (Wayne Jennings)
Organization: Deakin University
Lines: 29
Keywords: UNIFY, lockrec

In article <316@fairlight.oz> gary@fairlight.oz (Gary Evesson) writes:
>For all those UNIFY 3.2 people out there.....
>
>Has anyone ever had a problem with lockrec never returning if a record is
>locked by another process? If so, how did you get around it? I would love
>to know because it is driving me crazy killing off hung processes.
>

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.

Our easier solution is to kill this background Unify 'C' program which
then lets the Accell users keep going. We have never had any problems
with Accell, only when Unify 'C' is used as well.

Will be interested to hear anything about this!!!!

Wayne Jennings
Computing Services,
Deakin University,
Victoria, 3217.
Australia.

UUCP:	..!uunet!munnari!charlie.oz!wayne