Is it possible to let a user acquire a lock but not release it?
Accepted answer
The permissions for locking and unlocking files are the same, presumably because only the same user can unlock something they locked (or a Jazz Admin).
Ignoring this permissions issue, you would have to develop a script/operational behavior extension to release the lock. Maybe you should make this automation take both sides of the issue. When a user starts working in a file, the file is locked by a script using some service account (maybe it can run as the system itself, haven't written any myself lately). The script would then unlock it with the same service account when the validation is done. I don't know how you want to determine "working in a file"; if you lock it when the user checks it out that could get annoying to the other users, but I don't know how your SCM is set up and utilized so maybe that is ok. Regardless, sounds like a bunch of scripting is your option here.