SAP CCDSNU_CALL_DSNACCMO Function Module for Calls DSNACCMO (DB2 V7 Stored Procedure) for utility schedule
CCDSNU_CALL_DSNACCMO is a standard ccdsnu call dsnaccmo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calls DSNACCMO (DB2 V7 Stored Procedure) for utility schedule 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 ccdsnu call dsnaccmo FM, simply by entering the name CCDSNU_CALL_DSNACCMO into the relevant SAP transaction such as SE37 or SE38.
Function Group: S_CCDSNU_DB2
Program Name: SAPLS_CCDSNU_DB2
Main Program: SAPLS_CCDSNU_DB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCDSNU_CALL_DSNACCMO 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 'CCDSNU_CALL_DSNACCMO'"Calls DSNACCMO (DB2 V7 Stored Procedure) for utility schedule.
EXPORTING
* REMOTE_DBCON = "Logical name for a database connection
CHANGING
PROC_AREA = "Control Center stored procedures parameters
TABLES
MO_TBL = "Structure of global temp input table DSNACC.MO_TBL
MO_TBL2 = "Structure of global temp input table DSNACC.MO_TBL2
* OUTTS = "Output List of Tablespace of CC/390 Stored Procedures
EXCEPTIONS
ERROR_IN_CHECK_VERSION = 1 LESS_THAN_V7 = 2 STOPROC_ABORTED = 3 DSNACCMO_NOT_INSTALLED = 4 CREATE_DATABASE_FAILED = 5 NO_INPUT_TABLES = 6 SQL_ERROR = 7
IMPORTING Parameters details for CCDSNU_CALL_DSNACCMO
REMOTE_DBCON - Logical name for a database connection
Data type: DBCON_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for CCDSNU_CALL_DSNACCMO
PROC_AREA - Control Center stored procedures parameters
Data type: DB2ACCMOOptional: No
Call by Reference: Yes
TABLES Parameters details for CCDSNU_CALL_DSNACCMO
MO_TBL - Structure of global temp input table DSNACC.MO_TBL
Data type: DB2CCMOT1Optional: No
Call by Reference: Yes
MO_TBL2 - Structure of global temp input table DSNACC.MO_TBL2
Data type: DB2CCMOT2Optional: No
Call by Reference: Yes
OUTTS - Output List of Tablespace of CC/390 Stored Procedures
Data type: DB2CCMOUTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_IN_CHECK_VERSION - Error in Function DBSYCHK_COMPARE_VERSION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LESS_THAN_V7 - The DB version is less than V7.1 => DSNACCOR is not available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STOPROC_ABORTED - Call of stored procedure didn't work
Data type:Optional: No
Call by Reference: Yes
DSNACCMO_NOT_INSTALLED - DSNACCMO is not found in SYSIBM.SYSROUTINES
Data type:Optional: No
Call by Reference: Yes
CREATE_DATABASE_FAILED - Creation of TEMP database or tablespace failed.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_INPUT_TABLES - The required global temp tables are not installed.
Data type:Optional: No
Call by Reference: Yes
SQL_ERROR - EXEC SQL resulted in error.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CCDSNU_CALL_DSNACCMO 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: | ||||
| lt_mo_tbl | TYPE STANDARD TABLE OF DB2CCMOT1, " | |||
| lv_proc_area | TYPE DB2ACCMO, " | |||
| lv_remote_dbcon | TYPE DBCON_NAME, " | |||
| lv_error_in_check_version | TYPE DBCON_NAME, " | |||
| lt_mo_tbl2 | TYPE STANDARD TABLE OF DB2CCMOT2, " | |||
| lv_less_than_v7 | TYPE DB2CCMOT2, " | |||
| lt_outts | TYPE STANDARD TABLE OF DB2CCMOUT, " | |||
| lv_stoproc_aborted | TYPE DB2CCMOUT, " | |||
| lv_dsnaccmo_not_installed | TYPE DB2CCMOUT, " | |||
| lv_create_database_failed | TYPE DB2CCMOUT, " | |||
| lv_no_input_tables | TYPE DB2CCMOUT, " | |||
| lv_sql_error | TYPE DB2CCMOUT. " |
|   CALL FUNCTION 'CCDSNU_CALL_DSNACCMO' "Calls DSNACCMO (DB2 V7 Stored Procedure) for utility schedule |
| EXPORTING | ||
| REMOTE_DBCON | = lv_remote_dbcon | |
| CHANGING | ||
| PROC_AREA | = lv_proc_area | |
| TABLES | ||
| MO_TBL | = lt_mo_tbl | |
| MO_TBL2 | = lt_mo_tbl2 | |
| OUTTS | = lt_outts | |
| EXCEPTIONS | ||
| ERROR_IN_CHECK_VERSION = 1 | ||
| LESS_THAN_V7 = 2 | ||
| STOPROC_ABORTED = 3 | ||
| DSNACCMO_NOT_INSTALLED = 4 | ||
| CREATE_DATABASE_FAILED = 5 | ||
| NO_INPUT_TABLES = 6 | ||
| SQL_ERROR = 7 | ||
| . " CCDSNU_CALL_DSNACCMO | ||
ABAP code using 7.40 inline data declarations to call FM CCDSNU_CALL_DSNACCMO
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