Filter
Top Products
v The USERID of the first transaction in a pseudoconversation can be obtained
using EXEC CICS ASSIGN USERID.
v The TRANSID of the first transaction in a pseudoconversation can be obtained
from EIBTRNID.
The autoinstall control program can use the USERID and TRANSID values to
derive new TERMID and NETNAME values and return them in the communications
area.
Autoinstall of a Link3270 bridge facility
Bridge facility name uniqueness
Some applications use the termid to allocate a unique resource. This relies on the
name being unique within the CICSPlex
®
. Bridge facility names have the same
namespace as termids. However, CICS is unable to ensure that the bridge facility
name returned by the autoinstall control program is not the same as a termid
somewhere in the CICSPlex. Neither the termid nor netname returned by the
autoinstall control program are validated.
The autoinstall control program at INSTALL
The autoinstall control program is invoked at INSTALL for:
v Local VTAM terminals
v MVS consoles
v Local APPC single-session connections initiated by a CINIT
v Local APPC parallel-session connections initiated by a BIND
v Local APPC single-session connections initiated by a BIND
v Client virtual terminals
v Bridge facility virtual terminals
v Remote shipped terminals and connections (including shipped definitions of
Client virtual terminals).
On each invocation, CICS passes a parameter list to the control program by means
of a communication area addressed by DFHEICAP. The parameter list passed at
INSTALL of local terminals and APPC single-session connections initiated by CINIT
is described in “The communication area at INSTALL for terminals” on page 518.
The parameter list passed at INSTALL of local APPC connections initiated by BIND
requests is described in “The communication area at INSTALL for APPC
connections” on page 545. The parameter list passed at INSTALL of MVS consoles
is described in “The autoinstall control program at INSTALL” on page 536. The
parameter list passed at INSTALL of shipped terminals and connections is
described in “The communications area at INSTALL for shipped terminals” on page
562. This section describes only parameters passed at INSTALL of Client virtual
terminals, in “The communications area at INSTALL for Client virtual terminals,” and
of bridge facilities in “The communications area at INSTALL for bridge facility virtual
terminals” on page 573.
The communications area at INSTALL for Client virtual terminals
The communications area is mapped by the DSECT for the assembler version of
DFHZATDX or DFHZATDY, which are supplied in CICSTS32.CICS.SDFHMAC.
Chapter 15. Writing a program to control autoinstall of virtual terminals 571