When a terminal belonging to (local to and fully defined in) one system
invokes a transaction belonging to another system, it is known to the application-owning
region as a
remote terminal. The application-owning system needs to
have access to at least a partial definition of the remote terminal. This
partial definition is often known as a
remote definition. This is a
partial definition of the terminal, installed in the application-owning region
and intermediate regions. It contains the minimum information necessary for
the terminal to access a transaction in that system. You create remote definitions
only if you are using the
duplicating method.
- The REMOTESYSTEM name must be the name of the CONNECTION definition for
the next region in the transaction routing path to the terminal-owning region.
- REMOTESYSNET must be the netname (generic applid) of the terminal-owning
region. If REMOTESYSTEM names a direct CONNECTION to the terminal-owning region,
REMOTESYSNET is not required unless the terminal-owning region is a member
of a VTAM® generic
resource group, and the direct connection is an APPC link.
- The REMOTENAME is the name by which the terminal or APPC device is known
by in the terminal-owning region. It may be the same as or different from
the TERMINAL or CONNECTION name, which must be the name the terminal is known
by in the application-owning system. REMOTENAME defaults to the TERMINAL name
if not specified.
- SHIPPABLE on the TYPETERM is NO for non-APPC devices.
- SHIPPABLE on the TYPETERM is obligatory for APPC devices.
- Some of the attributes on the TERMINAL and TYPETERM definitions may be
omitted. For further guidance about these definitions, see CICS® Intercommunication Guide.
The following terminals and logical units cannot use transaction routing
and therefore cannot be defined as remote:
- Pooled 3600 or 3650 pipeline logical units
- IBM® 2260
terminals
- The MVS™ console