Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-P-PA (Application Component) Performance Analysis (Transaction ST05)⤷
ST05 (Package) ST05 Performance Trace
Basic Data
| Data Element | ST05_ENQ_OPERATION |
| Short Description | Lock Operation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Operation |
| Medium | 15 | Lock Operation |
| Long | 20 | Lock Operation |
| Heading | 14 | Lock Operation |
Documentation
Definition
Description of the executed lock operation.
The lock operations have the following meaning:
ENQUEUE Sets lock for lock object or increases lock counter for this lock object.
DEQUEUE Releases lock for lock object or decreases lock counter for this lock object if multiple locks exist.
DEQUEUE_ALL Releases all locks for all lock objects for an owner characterized by the enqueue owner ID or the enqueue transaction ID.
REMOVE Deletes any locks, including other owners' locks - for example with SM12.
GETUSER Gets own enqueue owner ID (for example, for forwarding to an RFC function module if the locks in the RFC function module are to be made under the owner ID of the caller).
ENQUEUE_PERM Saves the locks inherited by an update request from the backup file.
QUERY Reads lock entries from the lock table. (Used in high availability solutions .) In the default setting, lock entries are read by RFC.
GET_STAMP Gets unique, guaranteed increasing numbers. (Used for qRFC, for example.)
STATISTICS Reads statistics of the enqueue server.
OPERATIONS FOR SPECIAL USES SUCH AS ERROR DIAGNOSIS, ADMINISTRATION, and so on.
LOG_ON Activates logging. Operations of the enqueue server are recorded for diagnosis in the files ENQLOG<number>. Recording is usually used to diagnose the lock operations of application programs.
LOG_OFF Deactivates logging.
BCK_ON Activates backup file. During the update request the inherited locks are saved to the backup file so that they can, like the update request, survive a restart. The backup file is activated by default. In special performance-relevant cases, however, and with the customer's agreement, it can be deactivated. In this case, you must make sure that there are no open update requests at shutdown, and after startup make sure by using administrative measures that all existing update requests have been processed before new transactions are started.
BCK_OFF Deactivates backup file, compare with operation BCK_ON.
GET_ENQID Reads the lock table ID to find out, for example, whether lock table content was lost during a connection termination and reconnection between the client and the server.
CLEANUP_USER Like DEQUEUE_ALL, but the owner ID can contain wildcard characters. Used to delete the locks of all owners of an application server at startup and shutdown.
ENQUEUE_ON Activates the emergency operation mode; lock operations deliver ok, but do nothing. Used to execute diagnosis and administration transactions, during partial failure of the R/3 system.
ENQUEUE_OFF Deactivates emergency operation mode - compare with operation ENQUEUE_ON.
ENQUEUE_STATE Queries whether emergency operation mode is activated.
SET_ENQID Used for diagnostic purposes.
GET_HRES_TIME Used for diagnostic purposes.
STATE_TRANSFER Used for diagnosis purposes in high availability solutions.
LOG_ON_REPL Activates recording of replicated lock entries for high availability solutions based on the standalone server for diagnostic purposes.
LOG_OFF_REPL Deactivates recording - compare with operation LOG_ON_REPL.
CLRSTAT Resets time measurement statistics on the client interface.
GETSTAT Reads time measurement statistics on the client interface.
DUMP For diagnostic purposes.
VERIFY For diagnostic purposes.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 703 |
