Example

This example demonstrates how an AOR can resolve terminal identifiers from two terminal-owning regions that use the same set of terminal identifiers.

Assume that you have two terminal-owning regions, TORA and TORB, and that they use the same set of terminal identifiers, T001 through T500. TORA and TORB route transactions to the same application-owning region, AOR1. To prevent naming conflicts when terminals are shipped to AOR1, your control program in AOR1 could:
  • Accept the TERMIDs allocated by TORA. That is, leave the TERMINAL attribute of the remote definition set to the same as the REMOTENAME attribute.
  • Create aliases for the TERMIDs allocated by TORB. That is, reset the TERMINAL attribute of the remote definition, using a mapping file as described. For example, TERMIDs of T001 through T500 could be mapped to aliases of A001 through A500.

This solution allows two TORs using the same set of TERMIDs to access the same AOR. However, even though the aliases created in the AOR are mapped consistently to TERMIDs in the TOR, the solution does not guarantee that data mismatch problems cannot occur if terminals are re-shipped. This is because it relies on TERMIDs being allocated consistently in the TOR—that is, on specific TERMIDs always being assigned to the same physical devices.

Note: Your control program could use the correlation identifier contained in each terminal and connection definition to check whether a definition has been re-installed in the TOR—see the description of the INSTALL_SHIPPED_CORRID_PTR parameter in The communications area at INSTALL for shipped terminals.

A better solution might be to map the terminal alias in the AOR to the netname of the terminal. This would at least guarantee that a specific alias always relates to the same physical device. But it would still require TERMIDs for which aliases are not created to be consistently allocated in the TOR.



dfha3c00219.html | Timestamp icon Last updated: Sunday, 4 June 2017