Release may be used incorrectly

The rule “release” provides a warning any time it runs across the RELEASE statement. This is because most programmers have a misconception of what the command actually does.

The Risk:
Developers typically think that RELEASE will release a lock, which does not occur until the end of the transaction. Release simply moves the cursor off the current record, making it no longer available to the remainder of the program. There are times when this is exactly the desired functionality, in which case see “How to suppress” below.

How to solve this:
Nothing to be solved, if the developer is using the RELEASE statement as intended. Remove it if not.

How to suppress these warnings:
You can put the directive {&_proparse_prolint-nowarn(release)} directly before the RELEASE statement. See also: suppress warnings.