Shipping a TCTTE for transaction routing
For transaction routing, a terminal can be defined by an entry in the terminal-owning region (TOR) with the SHIPPABLE=YES attribute.
In this case, the terminal definition is shipped to any application-owning region (AOR) when the terminal user invokes a transaction owned by and defined to that region. Definitions for advanced program-to-program communication (APPC) devices always have the SHIPPABLE=YES attribute set.
The entry in the TOR could have been installed using CEDA INSTALL, the GRPLIST at system initialization, or autoinstall. When an autoinstalled TCTTE in a TOR is deleted, the relevant shipped terminals are deleted using a separate timing mechanism.
The first time a transaction is invoked
For
non-APPC devices (see Figure 1),
the following processing is performed:
- In the AOR, look for an existing skeleton TCTTE (TCTSK) whose REMOTENAME is the same as the local name in the TOR. If found, skip the following steps; otherwise:
- Issue ZC_INQUIRE to the TOR.
- In the TOR:
- Send a builder parameter set (BPS) representing the TCTTE to the AOR.
- Set on the SHIPPED flag (TCTEMROP) in the TCTTE.
- Set on the SHIPPED flag (TCSEMROP) in the TCTSE for the AOR system.
- Rewrite each entry to the catalog.
- In the AOR:
- Use the existing name from the TOR.
- INSTALL the terminal (DFHZATS does the remote install).
- Set on the SHIPPED flag (TCTSKSHI) in the TCTSK.
- Set on the SHIPPED flag (TCSEMROG) in the TCTSE for the TOR system.
- Rewrite each entry to the catalog.
Figure 1. Transaction-routing
flow for non-APPC devices

For APPC devices:
- In the AOR, look for an existing skeleton TCTTE (TCTSK) whose REMOTENAME is the same as the local name in the TOR. If found, skip the following steps; otherwise:
- INSTALL the terminal (DFHZATS does the remote install).
- Set on the SHIPPED flag (TCTSKSHI) in the TCTSK.
- Set on the SHIPPED flag (TCSEMROG) in the TCTSE for the TOR system.
- Rewrite each entry to the catalog.