Autoinstalling consoles--preliminary considerations

The reasons for using autoinstall for MVS™ consoles are the same as those that apply to the autoinstall for VTAM® devices: you don't have to define each device explicitly, and you save on storage (see Autoinstalling terminals--preliminary considerations).

Leaving it all to CICS

For consoles, in addition to the normal autoinstall support, you can also choose to let CICS® autoinstall consoles without calling the autoinstall program. In this case, CICS uses either:

If the autoinstall control program is not called, CICS generates a 4-character termid starting with the ¬ (logical not) symbol.

If you want CICS to install your consoles automatically:

Using an autoinstall control program

If you choose to have your autoinstall control program invoked for consoles, follow these steps:

If AICONS=YES is specified, or a CEMT (or EXEC CICS) SET AUTOINSTALL CONSOLES(PROGAUTO) has been issued, CICS invokes your autoinstall control program when:

Related tasks
Rewriting user-replaceable programs
Assembling and link-editing user-replaceable programs
Writing a program to control autoinstall of terminals
Writing a program to control autoinstall of APPC connections
Writing a program to control autoinstall of shipped terminals
Writing a program to control autoinstall of virtual terminals
Related reference
The autoinstall control program at INSTALL
The autoinstall control program at DELETE
The sample autoinstall control programs for consoles
[[ Contents Previous Page | Next Page Index ]]