Skip to main content
Question

Unverse 14.2.1 UNLOCK behaviour

  • June 18, 2026
  • 1 reply
  • 27 views
GilSteidle
Forum|alt.badge.img+1

We are validating our software package will run on UV version 14.2.1 and noticed the TCL UNLOCK command has been changed since version 11.3.1. UNLOCK ALL is no longer valid and the command will not unlock some record locks. For example: 

UNLOCK PID 9312 FILE D:\IBM\ACCOUNTS\BRIDGETON\SFH.CONTROL RECORD SFH@BRIDGETON
 

Does not release the lock:

 

06 LIST.READU DETAILS

Active Locks:
Device.... Inode.... FileName. UsrNo Pid.... LoginId ItemId... M LockTime.......
1680857659 562949953428398 D:\IBM\ACCOUNTS\DDICLOUD\SFH.CONTROL -26 7636 ddiadmin SFH.CLEANUP@DDICLOUD X Wed Jun 17 23:18:54 2026

1680857659 562949953433153 D:\IBM\ACCOUNTS\BRIDGETON\SFH.CONTROL -24 9312 ddiadmin SFH@BRIDGETON X Thu Jun 18 14:14:34 2026

 

Any insights on:

  1. How to release all locks?
  2. Why the SFH@BRIDGETON lock is not released?
  3. Any other UNLOCK gotchas in version 14.2.1 v 11.3.1?

Thanks in advance.

1 reply

John Jenkins
Forum|alt.badge.img+1
  • John Jenkins
  • Participating Frequently
  • June 18, 2026

Just a thought - try adding quotes to the fill file nama soa s to enclose the while string containing the @ symbol.

 

Otherwise (from the release notices) there were some UNLOCK hotfixes that are worth reviewing, one of them specific relating to releasing locks owned by another user. So it;s worth truiong as both root (Unix) or “Run as Administrator” (Windows) and also using RunAs to use the specific user who owns the lock concermed.
 

Worth opening a support ticket through your normal routes id this looks like an issue with the command.

 

Regards

JJ: . 

JJ
Still scrolling?
Ask a question
Terms & ConditionsAccessibility statement