Step - 1:Identify the lock

To identifying the file-item locks-  enter command "LIST.READU" this shows user, pid & other relavent data regarding specific file-item locks.  See the UniVerse documentation for further explaination.

LIST.READU

Active Record Locks:

Device.... Inode....  Netnode Userno  Lmode   Pid Login Id Item-ID.............

655369    325891        0  45385  49 RU 18448 mrfrear  UniVerse\localuv\BudE

xpEncTable 

655369     59639        0  45385  93 RL 18448 mrfrear  development&!DS.ADMIN

!& 

655369     59639        0  57425  93 RL 06408 mrfrear  development&!DS.ADMIN

!&

Step - 2: Clearing the lock

You need to use UNLOCK command for this.  For the above example enter

"UNLOCK USER 45385 READULOCK"   to release the ReadUlock (RU).  RU locks

are the most common problem.  This command must be executed from the "uv" account by an administrator.

Access the uv account by executing "/home/mrfrear/script/startuv development", at the ">" prompt type "LOGTO UV".

Syntax for UNLOCK command:

UNLOCK [NODE node] [USER user.number]

[FILE pathname | [DEVICE device.number] [INODE i.node.number]]

[GROUP group.address] [RECORD record.ID]

{FILELOCK | GROUPLOCK | READULOCK | READLLOCK |

ALL}