It would appear that your program is attempting to lock some entries in the
database using mode 6.  This is conditional locking and is designed to fail
if there are already entries locked that would conflict with your lock
request, and returns the control to the program.

Your program then decided to call DBUNLOCK, which is always a good thing to
do if your mode 6 DBLOCK failed so as to release whatever locks may have
been applied.  Then your program called DBEXPLAIN with the status array of
the failed called to DBLOCK and since it was after a subsequent call to
DBUNLOCK, it got some of that information on the display.  The message
CONFLICTING LOCKS... comes from DBERROR as the usual message from DBEXPLAIN
after a failed DBLOCK mode 6 is "ENTRY OR ENTRIES ALREADY LOCKED."

All this means is that you program tried to lock something that was already
locked by some other program and failed to do so.

Denys.

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of ianne
Sent: Thursday, April 24, 2008 3:46 AM
To: [log in to unmask]
Subject: [HP3000-L] Database lock issue

Hi,

Could anyone help me with this and elaborate more on the error I'm getting?

 TURBOIMAGE RESULT AT $004190f4; RETURN STATUS = 25

 DBUNLOCK, MODE 1, ON flt

 CONFLICTING DATA ENTRY LOCK ALREADY IN EFFECT


Thanks! =)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *