SAP RSDU_EXECUTE_DSNUTIL_DB2 Function Module for Execute a DSNUTILS Stored Procedure
RSDU_EXECUTE_DSNUTIL_DB2 is a standard rsdu execute dsnutil db2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Execute a DSNUTILS Stored Procedure 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 rsdu execute dsnutil db2 FM, simply by entering the name RSDU_EXECUTE_DSNUTIL_DB2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDU_UTIL_DB2
Program Name: SAPLRSDU_UTIL_DB2
Main Program: SAPLRSDU_UTIL_DB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDU_EXECUTE_DSNUTIL_DB2 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 'RSDU_EXECUTE_DSNUTIL_DB2'"Execute a DSNUTILS Stored Procedure.
EXPORTING
I_UTILNAME = "Specification of the Utility
I_STMT = "Utility Control Statement
* I_CONNECTION = "Logical Name for a Database Connection
* I_DUMP_OUTPUT = RS_C_FALSE "Info-Flag for dump
* I_PARALLEL_PROCESSING = RS_C_FALSE "Info-Flag for parallel processing
* I_SM50_INFOSTRING = "Infostring for transaction SM50
IMPORTING
E_T_SYSPRINT = "table SYSIBM.SYSPRINT
E_UTILID = "Unique identifier for a utility in DB2
EXCEPTIONS
UTILITY_ERROR = 1 CONNECTION_ERROR = 2
IMPORTING Parameters details for RSDU_EXECUTE_DSNUTIL_DB2
I_UTILNAME - Specification of the Utility
Data type: DB2DSNUP-UTIL_NAMEOptional: No
Call by Reference: Yes
I_STMT - Utility Control Statement
Data type: DB2DSNUP-UTSTMTOptional: No
Call by Reference: Yes
I_CONNECTION - Logical Name for a Database Connection
Data type: DBCON_NAMEOptional: Yes
Call by Reference: Yes
I_DUMP_OUTPUT - Info-Flag for dump
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: Yes
I_PARALLEL_PROCESSING - Info-Flag for parallel processing
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: Yes
I_SM50_INFOSTRING - Infostring for transaction SM50
Data type: CHAR30Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSDU_EXECUTE_DSNUTIL_DB2
E_T_SYSPRINT - table SYSIBM.SYSPRINT
Data type: RSDU_T_DB2SYSPRINTOptional: No
Call by Reference: Yes
E_UTILID - Unique identifier for a utility in DB2
Data type: DB2UTILIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
UTILITY_ERROR -
Data type:Optional: No
Call by Reference: Yes
CONNECTION_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSDU_EXECUTE_DSNUTIL_DB2 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_i_utilname | TYPE DB2DSNUP-UTIL_NAME, " | |||
| lv_e_t_sysprint | TYPE RSDU_T_DB2SYSPRINT, " | |||
| lv_utility_error | TYPE RSDU_T_DB2SYSPRINT, " | |||
| lv_i_stmt | TYPE DB2DSNUP-UTSTMT, " | |||
| lv_e_utilid | TYPE DB2UTILID, " | |||
| lv_connection_error | TYPE DB2UTILID, " | |||
| lv_i_connection | TYPE DBCON_NAME, " | |||
| lv_i_dump_output | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_i_parallel_processing | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_i_sm50_infostring | TYPE CHAR30. " |
|   CALL FUNCTION 'RSDU_EXECUTE_DSNUTIL_DB2' "Execute a DSNUTILS Stored Procedure |
| EXPORTING | ||
| I_UTILNAME | = lv_i_utilname | |
| I_STMT | = lv_i_stmt | |
| I_CONNECTION | = lv_i_connection | |
| I_DUMP_OUTPUT | = lv_i_dump_output | |
| I_PARALLEL_PROCESSING | = lv_i_parallel_processing | |
| I_SM50_INFOSTRING | = lv_i_sm50_infostring | |
| IMPORTING | ||
| E_T_SYSPRINT | = lv_e_t_sysprint | |
| E_UTILID | = lv_e_utilid | |
| EXCEPTIONS | ||
| UTILITY_ERROR = 1 | ||
| CONNECTION_ERROR = 2 | ||
| . " RSDU_EXECUTE_DSNUTIL_DB2 | ||
ABAP code using 7.40 inline data declarations to call FM RSDU_EXECUTE_DSNUTIL_DB2
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 UTIL_NAME FROM DB2DSNUP INTO @DATA(ld_i_utilname). | ||||
| "SELECT single UTSTMT FROM DB2DSNUP INTO @DATA(ld_i_stmt). | ||||
| DATA(ld_i_dump_output) | = RS_C_FALSE. | |||
| DATA(ld_i_parallel_processing) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects