I'll add my 2cents worth based upon my own experience regarding this
problem....

Check your program for doing multiple DBLOCKs on whatever set
is being locked. The first lock will be successful, but the second lock
fails (error code 25, entry already locked).

If your database has the "deadlock detection flag" set to ON there is
no need to run the undedlock program in the Telesup account as
someone else suggested. You could even DBLOCK with mode5 and the second lock
would fail and return an error code=26 (Lock not performed since deadlock
would occur).

You can check the status of the deadlock detection flag via DBUTIL.
Inside DBUTIL do a SHOW dbname ALL.

If your program is not doing multiple locks on the same set/item then it
looks like another process (job/session) is running the program and doing
the lock before you are....

Is this program a Vplus app? If so, make sure you are not locking before
the ENTER key gets pressed. The DBLOCK should always come AFTER
the call to VFIELDEDITS.....

HTH,
Brian Donaldson.



On Thu, 24 Apr 2008 04:46:03 -0400, ianne
wrote:

>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 *