© EDV Team Süd GmbHEDVTeamSuedGmbHLogo

 

.NET meets MultiChannel HostConnector

"Connecting .NET applications with mainframe"

 

Connecting .NET applications with mainframe

 

Your conditions

  • existing .NET applications or like to use .NET in the future

  • central data processing on a mainframe

  • you want to connect both systems

 

Then you surely dealt already with the difficulties of a server-to-mainframe-connection. This are known issues:

  • different system architecture

  • komplex definitions of connection

  • different destinations at the mainframe

  • different code pages

  • the both systems programmers can’t figure out what they are taking about

  • …

 

The effort of such a connection will be often shied due to these facts.

 

 

We are able to make your connection came true

 

The connection will be established by two in-house gateway interfaces.

 

At the server’s side:

 

At the servers side our new .NET-mainframe interface gets in touch with the mainframe. It was developed in C# within a state-of-the-art development environment (VisualStudio .NET)  and offers an interface, configurable by XML. It compiles the code and handles the connection establishment towards the mainframe. The interface generates the definitions for the destination system (IMS-connect, OTMA, …). The real connection will be made by TCP/IP. The format for data exchange between server and mainframe is XML. The application can be integrated in web services and then provide the functionality in intranet or internet.

 

 

At the mainframe’s side:

 

On this side our mainframe standard gateway, the Multichannel Hostconnector takes action. It receives the data from the mainframe interface (IMS-connect, OTMA, …) and calls any desired mainframe application. Among other things it handles the data conversion from XML to the mainframe application required format.

 

For further information about our Multichannel Hostconnector, please take note of the additional flyer

 

 

Pre-existing and new application for server and mainframe will be effortlessly jointed together.

 

 

What to be done, to implement such a       connection.

At the server you have to integrate the DLL of the  .NET-mainframe-interface in your application and fill in the

necessary data.

 

At the mainframe the business transaction has to be signed in the MCHC control tables. In addition, if necessary the corresponding Userexits have to be generated.

 

For creating the cross-platform definition of the interface data we recommend our DataDefinitionTool, which automatically creates the needful data definitions and Userexits for both gateway applications (see also our additional flyer).

 

For testing the connection, test environments are available, which allows - in case of new software development - test via mainframe, but the  application at the server is completed.

 

 

Advantages of this solution

 

  • Easy implementation of server to mainframe connections

  • Transparency to  different system architectures

  • Existing applications can  be easily rebound

  • Standardised procedures increase the quality and minimize development costs

  • Support of testing by  the  test tool

 

top