Lock requests and lock releases can be collected in a local lock container and sent together by calling the function module FLUSH_ENQUEUE.

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 if this is possible for all the individual requests.

The local lock container is emptied if all the collected lock requests can be executed; otherwise its contents remain unchanged.

The local lock container can be emptied by calling the function module RESET_ENQUEUE. All the collected lock requests or lock releases are deleted. The local lock container is automatically emptied when the corresponding internal session is ended.

Lock requests and lock releases are managed together in the local lock container. When the collected requests are sent, the lock requests are sent first. The lock releases are sent once all the requested locks have been assigned.

The lock requests and lock releases are not adjusted in the local lock container. The order in which the individual requests are written in the local lock container is of no importance.