SAP DBSYCHK_GET_DB_RELEASE Function Module for DB2/zOS: Get database release
DBSYCHK_GET_DB_RELEASE is a standard dbsychk get db release 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/zOS: Get database release 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 dbsychk get db release FM, simply by entering the name DBSYCHK_GET_DB_RELEASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DBSYCHK_DB2
Program Name: SAPLDBSYCHK_DB2
Main Program: SAPLDBSYCHK_DB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DBSYCHK_GET_DB_RELEASE 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 'DBSYCHK_GET_DB_RELEASE'"DB2/zOS: Get database release.
EXPORTING
* CON_NAME = "Logical name for a database connection
IMPORTING
RELEASE = "DB2 release
EXCEPTIONS
ADBC_SQL_ERROR = 1
IMPORTING Parameters details for DBSYCHK_GET_DB_RELEASE
CON_NAME - Logical name for a database connection
Data type: DBCON-CON_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DBSYCHK_GET_DB_RELEASE
RELEASE - DB2 release
Data type: DB2TDUMMY-DB2RELOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADBC_SQL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DBSYCHK_GET_DB_RELEASE 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_release | TYPE DB2TDUMMY-DB2REL, " | |||
| lv_con_name | TYPE DBCON-CON_NAME, " | |||
| lv_adbc_sql_error | TYPE DBCON. " |
|   CALL FUNCTION 'DBSYCHK_GET_DB_RELEASE' "DB2/zOS: Get database release |
| EXPORTING | ||
| CON_NAME | = lv_con_name | |
| IMPORTING | ||
| RELEASE | = lv_release | |
| EXCEPTIONS | ||
| ADBC_SQL_ERROR = 1 | ||
| . " DBSYCHK_GET_DB_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM DBSYCHK_GET_DB_RELEASE
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 DB2REL FROM DB2TDUMMY INTO @DATA(ld_release). | ||||
| "SELECT single CON_NAME FROM DBCON INTO @DATA(ld_con_name). | ||||
Search for further information about these or an SAP related objects