IBM SC33-1683-02 - Manual (Page 563)

Chapter 14. Writing a program to control autoinstall of Client
virtual terminals
Considerations common to all user-replaceable programs
Note that the comments contained in “Chapter 5. General notes about
user-replaceable programs” on page 401 apply to this chapter.
This chapter describes how to write a program to control the installation of virtual
terminals. Virtual terminals are used by the External Presentation Interface (EPI)
and terminal emulator functions of the CICS Clients products. For an introduction to
the CICS Clients products, and detailed information about CICS Transaction Server
for OS/390 support for them, see the
CICS for MVS/ESA Server support for CICS
Clients manual.
Both the supplied autoinstall control programs, DFHZATDX and DFHZATDY, provide
function to install definitions of Client virtual terminals. You can therefore base your
customized control program on either DFHZATDX or DFHZATDY.
The chapter is divided into the following sections:
1. “How Client virtual terminals are autoinstalled”
2. “The autoinstall control program at INSTALL” on page 534
3. “The autoinstall control program at DELETE” on page 536
4. “Default actions of the sample programs” on page 537.
How Client virtual terminals are autoinstalled
Client virtual terminals are defined to CICS Transaction Server for OS/390 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.
© Copyright IBM Corp. 1977, 1999 531