All external Automatic Entry communications between applications on your local host and on remote MCP based, OS 2200 based, UNIX, or Windows hosts are supported by a central HUBRouter library, located on the same pack family as SYSTEM/COMS. There is one copy of the HUBRouter library for each host. This library contains global tables to administer connections and control routing of messages. HUBRouter appears in the library mix with the title NGEN28/1/HUBROUTER.

All calls to the HUBRouter are made indirectly, using procedures in the LINCSUPPORT library (one for each application). The LINCSUPPORT library contains code to manage elements of the Two-Phase Commit protocol, and code to maintain state information relative to the application.

The HUBRouter library must be initiated by COMS as a direct window program. This is because the active control procedure of the library routes messages to local systems by using a COMS TP-to-TP send.

Refer to HUBRouter Commands and Inquiries section in Communicating With Other Hosts for more information about the operational aspects of HUBRouter.

Setting up HUBRouter as an Application Library

The HUBRouter library is set up as a system library using the SL command, and therefore does not require to be run from the same pack as COMS. The SL command used for HUBRouter has the following syntax (where pack is the COMS pack):

SL LINCHUBROUTER = *NGEN28/1/HUBROUTER ON pack : MCPINIT