Filter
Top Products
Chapter 15. Writing a program to control autoinstall of virtual
terminals
Virtual terminals are used by the External Presentation Interface (EPI) and terminal
emulator functions of the CICS Clients products, as well as the CICS Link3270
bridge.
In a bridged environment, these virtual terminals replace the real 3270 that is the
principal facility of a 3270 transaction. They are known as bridge facilities.
Both the supplied autoinstall control programs, DFHZATDX and DFHZATDY, provide
function to install definitions of virtual terminals. You can therefore base your
customized control program on either DFHZATDX or DFHZATDY.
This information is divided into the following sections:
1. “How Client virtual terminals are autoinstalled”
2. “The autoinstall control program at INSTALL” on page 571
3. “The autoinstall control program at DELETE” on page 575
4. “Default actions of the sample programs” on page 577.
How Client virtual terminals are autoinstalled
Client virtual terminals are defined to CICS Transaction Server for z/OS, Version 3
Release 2 as remote 3270 datastream devices.
Autoinstall models
The autoinstall model used to install a virtual terminal is determined using the
following sequence:
1. For EPI programs:From the DevType parameter of the CICS_EpiAddTerminal
function, if specified by the Client EPI program. (For details of EPI calls, see the
CICS Family: Client/Server Programming manual.)
For the Client terminal emulator:From the /m parameter of the cicsterm
command used to start the emulator, if specified by the workstation user. (For
details of the cicsterm command, see the CICS Clients: Administration manual.)
Note: Any autoinstall models specified by Clients must, of course, be defined to
CICS. However, because VTAM definitions are not required for Client
virtual terminals, there is no need to create matching entries in the VTAM
LOGMODE table.
2. The CICS-supplied autoinstall model, DFHLU2.
The autoinstall control program cannot choose a different autoinstall model.
Terminal identifiers
The terminal identifier (TERMID) passed to the CICS autoinstall function at install of
a virtual terminal is determined using the following sequence:
1. For EPI programs: From the NetName parameter of the CICS_EpiAddTerminal
function, if specified by the Client EPI program.
For the Client terminal emulator: From the /n parameter of the cicsterm
command used to start the emulator, if specified by the workstation user.
2. A name generated automatically by CICS.
© Copyright IBM Corp. 1977, 2011 567