Browse Prior Art Database

Application of Distributed Computing Environment Remote Procedure Call and Cell Directory Service with CICS Terminals

IP.com Disclosure Number: IPCOM000111463D
Original Publication Date: 1994-Feb-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 70K

Publishing Venue

IBM

Related People

Kolban, N: AUTHOR

Abstract

Disclosed is the ability for all AutoInstalled terminals to be given unique Terminal Identifiers (TERMIDs) throughout a complete set of CICS systems which may potentially communicate with each other.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Application of Distributed Computing Environment Remote Procedure
Call and Cell Directory Service with CICS Terminals

      Disclosed is the ability for all AutoInstalled terminals to be
given unique Terminal Identifiers (TERMIDs) throughout a complete set
of CICS systems which may potentially communicate with each other.

      In the CICS family of products, the action of attaching a
terminal to a CICS system is known as "AutoInstall" if the terminal
is not defined to the CICS region.  The AutoInstall process generates
a four-character name for the new terminal known as the Terminal
Identifier or TERMID.  The actual name of the TERMID is generated
through the use of a User Exit function (or the default if no other
user exit is supplied).

      The user exit function takes as input, a SNA Netname (or
virtual netname if SNA is not being used, for example, in CICS/6000*)
and returns the TERMID.  TERMIDs must be unique on a single CICS
system, that is, no two terminals attached to a CICS system can have
the same TERMIDs.  CICS also allows the capability to ship a terminal
definition from one CICS system to another, as in the case of
Transaction Routing using the CRTE CICS supplied transaction.  A
problem is that this terminal shipping causes the remote (not
terminal owning) region to install a terminal definition with the
same TERMID as the local region.  Since no two terminals in a single
CICS system are allowed to have the same TERMID, if the local TERMID
is the same as an already installed terminal in the remote CICS
system, a problem occurs.

      A Solution exists on certain CICS systems (for example, CICS
OS/2*) where a second user exit is available and is invoked to allow
an incoming TERMID to be renamed so it does not clash with the
original TERMID.  The exi...