It is possible to collect lock requests and lock releases in a local lock container and then send them as a group. The function module FLUSH_ENQUEUE must be called in order to send the collected lock requests.

This has two advantages over sending the lock requests directly:

• Communications with the lock server are minimized if the lock requests are sent as a group.

• The collected lock requests are handled as a group, which means that they are only written to the lock table when this is possible for all the individual requests.

The local lock container is emptied when the collected lock requests can be executed, otherwise its contents remain unchanged.

The local lock container can also be emptied by calling the function module RESET_ENQUEUE and is automatically emptied when the corresponding internal mode ends.

Lock requests and lock releases are managed together in the local lock container. When the collected requests are sent, first the lock requests are sent. If all the requested locks can be assigned, the lock releases are sent.

There is no adjustment of the lock requests and lock releases in the local lock container. The order of the individual requests in the local lock container is of no importance.