API for AWSMainframeModernization¶

ABAP Package	`/AWS1/API_M2`
ABAP SDK "TLA"	`M2`
ABAP Interface	`/AWS1/IF_M2`

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for AWSMainframeModernization is M2. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation¶

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the m2 module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service¶

Amazon Web Services Mainframe Modernization provides tools and resources to help you plan and implement migration and modernization from mainframes to Amazon Web Services managed runtime environments. It provides tools for analyzing existing mainframe applications, developing or updating mainframe applications using COBOL or PL/I, and implementing an automated pipeline for continuous integration and continuous delivery (CI/CD) of the applications.

Using the SDK¶

In your code, create a client using the SDK module for AWSMainframeModernization, which is created with factory method /AWS1/CL_M2_FACTORY=>CREATE(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_m2)       = /aws1/cl_m2_factory=>create( go_session ).

Your variable go_m2 is an instance of /AWS1/IF_M2, and all of the operations in the AWSMainframeModernization service are accessed by calling methods in /AWS1/IF_M2.

API Operations¶

For an overview of ABAP method calls corresponding to API operations in AWSMainframeModernization, see the Operation List.

Factory Method¶

`/AWS1/CL_M2_FACTORY=>CREATE( )`¶

Creates an object of type /AWS1/IF_M2.

IMPORTING¶

Required arguments:¶

`IO_SESSION` `TYPE REF TO` `/AWS1/CL_RT_SESSION_BASE`¶

Optional arguments:¶

`IV_PROTOCOL` `TYPE` `/AWS1/RT_PROTOCOL`¶

`IV_REGION` `TYPE` `/AWS1/RT_REGION_ID`¶

`IV_CUSTOM_ENDPOINT` `TYPE` `/AWS1/RT_ENDPOINT`¶

RETURNING¶

`OO_CLIENT` `TYPE REF TO` `/AWS1/IF_M2`¶

/AWS1/IF_M2 represents the ABAP client for the m2 service, representing each operation as a method call. For more information see the API Page page.