Overview of how shipped terminals are deleted

In a transaction routing environment, terminal definitions can be shipped from a terminal-owning region (TOR) to an application-owning region (AOR) when they are first needed, rather than being statically defined in the AOR.

The "terminal" could be an APPC device or system. In this case, the shipped definition would be of an APPC connection.

Shipped definitions can become redundant in the following situations:
  • A terminal user logs off.
  • A terminal user stops using remote transactions.
  • The TOR is shut down.
  • The TOR is restarted, autoinstalled terminal definitions are not recovered, and the autoinstall user program, DFHZATDX, assigns a new set of termids to the same set of terminals.

At some stage, redundant definitions must be deleted from the AOR (and from any intermediate systems between the TOR and AOR). For brevity, we shall refer to AORs and intermediate systems collectively as back-end systems. This is particularly necessary in the last situation in the previous list, to prevent a possible mismatch between termids in the TOR and the back-end systems.

CICS® method of deleting redundant shipped definitions consists of two parts:
  • Selective deletion
  • A timeout delete mechanism.


dfht1lx.html | Timestamp icon Last updated: Monday, 5 June 2017