External Automatic Entries Between Runtime Applications

The external Automatic Entry (HUB) facility enables an application to interface to other applications on the same or different host types. Any application is able to initiate a transaction.

MCP-based, OS 2200-based, UNIX, and Windows host types can communicate using the TCP/IP networking protocol.

The Ispec being transferred must exist in exactly the same format on both applications. The process uses the same logic regardless of the destination or originating host type.

An external Automatic Entry enables an application to pass a transaction to another application. This is achieved by defining the application name and location details for the destination of the transaction in your logic, then using the appropriate logic commands.

An external Automatic Entry transaction invokes the _Prepare and Main methods in the receiving Ispec being performed. _Construct method is not invoked.

Security (Security Module) and multiple language facilities are supported by external Automatic Entries.

Refer to Standard Message Routing for more information on the transaction flow (message routing) involved in external Automatic Entry communications.

Notes:

  • The implementation uses a library mechanism without the need for an intermediary HUB program or database.

  • External Automatic Entries using VPN (Virtual Private Network) are not supported.