Autoinstall for terminals, consoles and APPC connections
Autoinstall for terminals provides the ability to log on to CICS® from a logical unit (LU), known to z/OS® Communications Server but not previously defined to CICS, and to make a connection to a running CICS system.
A new connection is created and installed automatically if autoinstall
for connections is enabled, and either of the following occurs:
- An APPC BIND request or CINIT request is received for an APPC service manager (SNASVCMG) session that does not have a matching CICS CONNECTION definition
- A BIND is received for a single session that does not have a matching CICS CONNECTION definition.
A new console is created and installed automatically if autoinstall for consoles is enabled and a CIB (Command Input Buffer sent from MVS™) is received by CICS (DFHZCNA) and the console TCTTE does not already exist.
For an introduction to autoinstall, and information about how to
implement it, see Autoinstall.Writing a program to control autoinstall of LUs gives information about
implementing the autoinstall user program. The CICS-supplied
programs are:
- DFHZATDX, which provides autoinstall for terminals only
- DFHZATDY, which provides autoinstall for terminals and APPC connections.
These programs are user-replaceable, because you may need to tailor the basic function to suit your CICS environment.