SAP DB2CCMS_CKECK_ABAP_STACK Function Module for DB2: Checks for an exising JAVA Stack on target DB2 subystem
DB2CCMS_CKECK_ABAP_STACK is a standard db2ccms ckeck abap stack SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DB2: Checks for an exising JAVA Stack on target DB2 subystem processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for db2ccms ckeck abap stack FM, simply by entering the name DB2CCMS_CKECK_ABAP_STACK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDB2CCMS_METADATA
Program Name: SAPLSDB2CCMS_METADATA
Main Program: SAPLS_CCDSNU_DB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DB2CCMS_CKECK_ABAP_STACK pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'DB2CCMS_CKECK_ABAP_STACK'"DB2: Checks for an exising JAVA Stack on target DB2 subystem.
IMPORTING
IS_ABAP = "General Flag
EXPORTING Parameters details for DB2CCMS_CKECK_ABAP_STACK
IS_ABAP - General Flag
Data type: DB2TDUMMY-FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DB2CCMS_CKECK_ABAP_STACK Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_is_abap | TYPE DB2TDUMMY-FLAG. " |
|   CALL FUNCTION 'DB2CCMS_CKECK_ABAP_STACK' "DB2: Checks for an exising JAVA Stack on target DB2 subystem |
| IMPORTING | ||
| IS_ABAP | = lv_is_abap | |
| . " DB2CCMS_CKECK_ABAP_STACK | ||
ABAP code using 7.40 inline data declarations to call FM DB2CCMS_CKECK_ABAP_STACK
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single FLAG FROM DB2TDUMMY INTO @DATA(ld_is_abap). | ||||
Search for further information about these or an SAP related objects