MCP AIS .Net Call-in supports accessing MCP Libraries from the .NET environment. To take advantage of this feature with AB Suite MCP Runtime, the user must enable AIS .Net Call-in access to the AB Suite public segment methods Exports Library. Refer to the Application Integration Services Installation and Programming Guide, for more information.

AIS .Net Call-in access to the AB Suite public segment methods Exports Library is enabled by setting the TASKSTRING attribute of utility (<RT User Code>)NGEN28SYS/BLD on <RT Pack> to SETRPC. When this is done, as part of the application deployment, processing will occur during the generate of the Exports Library that results in the creation of a Library Definitions File (LDF), titled XML/<system>/EXPORTS/LIBRARY. This file details, in an XML format, the public segment methods and their signatures, that is, parameter(s), parameter type(s), return type(s).

The user processes the LDF file using the Windows AIS Libra AIS ProxyStub Generator to create both a .NET DLL and an MCP proxy stub library source. The .NET DLL passes the method request and parameter value(s) to the MCP proxy stub library that formats the parameter(s) into MCP native types and then calls the Exports Library. The process is reversed upon return from the Exports Library method call, the parameter value(s) are reformatted back in .NET format by the MCP proxy stub library and the data returned to the calling .NET DLL.

When calling into AB Suite MCP Public Segment Methods from AIS .Net Call-in, best runtime performance will be obtained if the user selects the <model method name>_DIRECT entrypoint(s) when running the Windows AIS Libra ProxyStub generator. See Technical Notes in the section, Invoking a Public Segment Method from an External Program for further details on exported methods.

Refer to the Application Integration Services Installation and Programming Guide for further details on enabling .Net Call in to MCP Libraries.