VMCDBG_PROCESS SAP (VMCDBG: Entry in the process list) Structure details
Description: VMCDBG: Entry in the process list
Related tables to VMCDBG_PROCESS
Access table VMCDBG_PROCESS
Structure field list including key, data, relationships and ABAP select examples
VMCDBG_PROCESS is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "VMCDBG: Entry in the process list" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_VMCDBG_PROCESS TYPE VMCDBG_PROCESS.
The VMCDBG_PROCESS table consists of various fields, each holding specific information or linking keys about VMCDBG: Entry in the process list data available in SAP. These include VM_HANDLE (Number of the Java VM), WP_NUMBER (Work Process Number), VM_TYPE (VM Type), VM_STATE (VM State).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)
SAP VMCDBG_PROCESS structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| VM_INFO | 0 | ||||||||
| VM_HANDLE | Number of the Java VM | VM_HANDLE | INT4 | 10 | VM_HANDLE | ||||
| WP_NUMBER | Work Process Number | WPINDEX | INT4 | 10 | WPINDEX | ||||
| VM_TYPE | VM Type | VM_TYPE | INT4 | 10 | VM_TYPE | ||||
| VM_STATE | VM State | VM_STATE | INT4 | 10 | VM_STATE | ||||
| VM_CPU | Virtual Machine CPU | VM_CPU | DEC | 20 | VM_INT64 | ||||
| VM_APPL | VM: Application Currently Running | VM_APPL | CHAR | 256 | VM_APPL | ||||
| VM_USED_BYTES | VM: Memory Consumption (MB) | VM_BYTES | DEC | 20 | VM_INT64 | ||||
| VM_DEBUG_STATE | VM: Debugging State | VM_DBGSTATE | INT4 | 10 | VM_DBGSTATE | ||||
| VM_DEBUG_PORT | VM: Debug Port | VM_DBGPORT | INT4 | 10 | VM_DBGPORT | ||||
| VM_USED_TIME | Start Time of Last Request | VM_USED_TIME | CHAR | 8 | VM_USED_TIME | ||||
| VM_USER | User Currently Served | WPBNAME | CHAR | 12 | UBNAME | ||||
| VM_SGC_STATE | VM State of the Shared Garbage Collector (SGC) | VM_SGC_STATE | INT4 | 10 | VM_SGC_STATE | ||||
| VM_SGC_WAITING | VM Shared GC Waiting | VM_SGC_WAITING | INT4 | 10 | VM_SGC_WAITING | ||||
| VM_LOCKS | Number of Cross-VM Locks | VM_LOCKS | INT4 | 10 | VM_LOCKS | ||||
| VM_TRACE | VM-Specific Trace | VM_TRACE | INT1 | 3 | VM_TRACE | ||||
| VM_LWP | Last process in which VM was active | VM_LWP | INT4 | 10 | WPINDEX | ||||
| DBG_STATE_ICON | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure VMCDBG_PROCESS using ABAP code?
As VMCDBG_PROCESS is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on VMCDBG_PROCESS as there is no data to select.How to access SAP table VMCDBG_PROCESS
Within an ECC or HANA version of SAP you can also view further information about VMCDBG_PROCESS and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects