SAP STU3_MAP_DB2_CLIENT_INFO Function Module for Maps DB2 IDs to SAP's usage
STU3_MAP_DB2_CLIENT_INFO is a standard stu3 map db2 client info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maps DB2 IDs to SAP's usage 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 stu3 map db2 client info FM, simply by entering the name STU3_MAP_DB2_CLIENT_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: STU3
Program Name: SAPLSTU3
Main Program: SAPLSTU3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function STU3_MAP_DB2_CLIENT_INFO 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 'STU3_MAP_DB2_CLIENT_INFO'"Maps DB2 IDs to SAP's usage.
EXPORTING
* RAW_CLIENT_INFO = "ST04: DB2 thread overview
IMPORTING
SAP_IDS = "DB2 Performance Monitor: Thread List
IMPORTING Parameters details for STU3_MAP_DB2_CLIENT_INFO
RAW_CLIENT_INFO - ST04: DB2 thread overview
Data type: DB2QTHDLSTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STU3_MAP_DB2_CLIENT_INFO
SAP_IDS - DB2 Performance Monitor: Thread List
Data type: DB2THREADSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STU3_MAP_DB2_CLIENT_INFO 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_sap_ids | TYPE DB2THREADS, " | |||
| lv_raw_client_info | TYPE DB2QTHDLST. " |
|   CALL FUNCTION 'STU3_MAP_DB2_CLIENT_INFO' "Maps DB2 IDs to SAP's usage |
| EXPORTING | ||
| RAW_CLIENT_INFO | = lv_raw_client_info | |
| IMPORTING | ||
| SAP_IDS | = lv_sap_ids | |
| . " STU3_MAP_DB2_CLIENT_INFO | ||
ABAP code using 7.40 inline data declarations to call FM STU3_MAP_DB2_CLIENT_INFO
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.Search for further information about these or an SAP related objects