SAP STU3_GET_ZOS_LPAR_INFO Function Module for Get LPAR Info
STU3_GET_ZOS_LPAR_INFO is a standard stu3 get zos lpar 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 Get LPAR Info 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 get zos lpar info FM, simply by entering the name STU3_GET_ZOS_LPAR_INFO into the relevant SAP transaction such as SE37 or SE38.
Function Group: STU3_SYSPLEX_MONITOR
Program Name: SAPLSTU3_SYSPLEX_MONITOR
Main Program: SAPLSTU3_SYSPLEX_MONITOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STU3_GET_ZOS_LPAR_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_GET_ZOS_LPAR_INFO'"Get LPAR Info.
EXPORTING
LAST_FIVE_MINUTES = "Single-Character Flag
* URL_SERV = "RMF DDS Server
* URL_PORT = "RMF DDS Port
* URL_USER = "User for RMF DDS access (may be initial if not needed)
* URL_PWD = "Password for RMF DDS user
* REMOTE_DBCON = "Logical name for a database connection
* ASSIGN_MEMBER_NAME = "
IMPORTING
MINTIME = "Natural number
LPAR_INFO_ZOS = "DB2: LPAR information for z/OS
ROOT_EX_CAUSE = "Root exception cause
EXCEPTIONS
NO_MONITOR_URL = 1 HTTP_CALL_FAILED = 2 ROOT_EXCEPTION = 3
IMPORTING Parameters details for STU3_GET_ZOS_LPAR_INFO
LAST_FIVE_MINUTES - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
URL_SERV - RMF DDS Server
Data type: DB2_HOSTOptional: Yes
Call by Reference: No ( called with pass by value option)
URL_PORT - RMF DDS Port
Data type: DB2_PORTOptional: Yes
Call by Reference: No ( called with pass by value option)
URL_USER - User for RMF DDS access (may be initial if not needed)
Data type: DB2CCUIDOptional: Yes
Call by Reference: Yes
URL_PWD - Password for RMF DDS user
Data type: DB2CCPSWOptional: Yes
Call by Reference: Yes
REMOTE_DBCON - Logical name for a database connection
Data type: DBCON-CON_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
ASSIGN_MEMBER_NAME -
Data type: ABAP_BOOLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for STU3_GET_ZOS_LPAR_INFO
MINTIME - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
LPAR_INFO_ZOS - DB2: LPAR information for z/OS
Data type: DB2_LPAR_INFO_ZOS_TABOptional: No
Call by Reference: Yes
ROOT_EX_CAUSE - Root exception cause
Data type: STRINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_MONITOR_URL -
Data type:Optional: No
Call by Reference: Yes
HTTP_CALL_FAILED -
Data type:Optional: No
Call by Reference: Yes
ROOT_EXCEPTION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for STU3_GET_ZOS_LPAR_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_mintime | TYPE INT4, " | |||
| lv_no_monitor_url | TYPE INT4, " | |||
| lv_last_five_minutes | TYPE CHAR1, " | |||
| lv_url_serv | TYPE DB2_HOST, " | |||
| lv_lpar_info_zos | TYPE DB2_LPAR_INFO_ZOS_TAB, " | |||
| lv_http_call_failed | TYPE DB2_LPAR_INFO_ZOS_TAB, " | |||
| lv_url_port | TYPE DB2_PORT, " | |||
| lv_root_ex_cause | TYPE STRING, " | |||
| lv_root_exception | TYPE STRING, " | |||
| lv_url_user | TYPE DB2CCUID, " | |||
| lv_url_pwd | TYPE DB2CCPSW, " | |||
| lv_remote_dbcon | TYPE DBCON-CON_NAME, " | |||
| lv_assign_member_name | TYPE ABAP_BOOL. " |
|   CALL FUNCTION 'STU3_GET_ZOS_LPAR_INFO' "Get LPAR Info |
| EXPORTING | ||
| LAST_FIVE_MINUTES | = lv_last_five_minutes | |
| URL_SERV | = lv_url_serv | |
| URL_PORT | = lv_url_port | |
| URL_USER | = lv_url_user | |
| URL_PWD | = lv_url_pwd | |
| REMOTE_DBCON | = lv_remote_dbcon | |
| ASSIGN_MEMBER_NAME | = lv_assign_member_name | |
| IMPORTING | ||
| MINTIME | = lv_mintime | |
| LPAR_INFO_ZOS | = lv_lpar_info_zos | |
| ROOT_EX_CAUSE | = lv_root_ex_cause | |
| EXCEPTIONS | ||
| NO_MONITOR_URL = 1 | ||
| HTTP_CALL_FAILED = 2 | ||
| ROOT_EXCEPTION = 3 | ||
| . " STU3_GET_ZOS_LPAR_INFO | ||
ABAP code using 7.40 inline data declarations to call FM STU3_GET_ZOS_LPAR_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.| "SELECT single CON_NAME FROM DBCON INTO @DATA(ld_remote_dbcon). | ||||
Search for further information about these or an SAP related objects