Previous Topic

Next Topic

Book Contents

Book Index

Step 22.5 – CICS considerations (optional)

CICS requires that each terminal or terminal type that communicates with it must be defined to CICS before a connection can be established. From the CICS point of view, there is no difference between a real LUTYPE2 terminal and a KOA terminal. Therefore, the KOA terminals must be defined in the same way as all the other terminals are defined. There are several methods for defining a terminal to CICS:

The best method for defining KOA terminals is Auto-Install. This is the most flexible method, since there is no need to define each individual terminal and the characteristics of the terminal, such as screen size, can be different in each session. A corresponding TYPETERM and terminal MODEL should exist to reflect all different KOA terminals, LUTYPE2 models 2, 3, 4, and 5, with or without extended data stream. At logon, the CICS Auto-Install program chooses a corresponding terminal model according to the LOGMODE supplied by KOA.

Other methods, such as RDO and TCT, can be used, but they are not as flexible. Each KOA terminal should be defined and the characteristics of the terminal should be specified. The LOGMODE parameters that were supplied during session initiation are ignored. This means that KOA is not able to specify the characteristics of the terminal according to script commands such as SCREENSIZE and COLOR.

Parent Topic

Step 22 – Install KOA and IOA routes (optional)