Cross-System Locks

Use

The application that requests a CSL is in an SAP LUW that consists of a dialog and an update. When a lock has been requested, the application can decide when the cross-system lock will automatically be released again. That is why the CSLEO_ENQUEUE function module has the PSCOPE parameter:

• PSCOPE=1: Implicit release of the token at the end of the dialog

• PSCOPE=2: Implicit release of the token at the end of the update

Locally, standard locks are used for the cross-system locking of a token. Once a token is locked, the status is set to FREE (locked transiently) since the system releases the cross-system locks when it releases the standard locks. The locks are released implicitly according to the value of PSCOPE either at the end of the dialog or at the end of the update.

Since the CSL builds on the standard lock mechanism, the cumulation principle can be adopted directly. Regardless of PSCOPE, the locks that were requested with CSLEO_ENQUEUE are cumulative. See also: Cumulating Locks.

Cross-system locks can be explicitly released by the corresponding owner using the CSLEO_DEQUEUE module.