Implementing autoinstall for MVS consoles

CICS® autoinstall support for consoles is not provided automatically—there are some tasks to be completed to enable the support. Basically, you need to specify that you want the support, and ensure that the required model resource definitions are installed. This is because the autoinstall models supplied in DFHLIST do not contain models suitable for console autoinstall. The IBM®-supplied group DFHTERMC contains an autoinstall model definition for a console, but this is not included in DFHLIST. Also, an optional requirement is the support of an autoinstall control program

The following steps describe how to enable autoinstall for consoles:
  1. Define a console terminal definition that:
    • Specifies AUTINSTMODEL(YES), or AUTINSTMODEL(ONLY)
    • Start of changeSpecifies the CONSNAME(name)End of change
    • References a TYPETERM that specifies DEVICE(CONSOLE)

    You can use the model console definition defined in the group DFHTERMC, which is added to your CSD by the INITIALIZE and UPGRADE commands.

    Note: Start of changeWhen a model terminal definition is used by the console autoinstall function, CICS ignores the console name specified on the model definition.End of change
  2. Install the model console definition either by adding its group to a group list and perform a cold start, or use the CEDA INSTALL command.
  3. If you decide that you want the autoinstall control program to be invoked for console autoinstall, modify your autoinstall control program to handle console install and delete requests. To reactivate your modified program, either restart CICS or use the CEMT, or EXEC CICS, SET PROGRAM(…) NEWCOPY command.

    To ensure CICS invokes your autoinstall control program, specify system initialization parameter AICONS=YES, or use the CEMT, or EXEC CICS, SET AUTOINSTALL CONSOLES(PROGAUTO) command to specify console autoinstall dynamically.

  4. If you decide to let CICS autoinstall consoles without invoking your autoinstall control program, specify system initialization parameter AICONS=AUTO, or use the CEMT, or EXEC CICS, SET AUTOINSTALL CONSOLES(FULLAUTO) command to specify console autoinstall dynamically. With the AUTO option, CICS allocates the termid automatically.
  5. As in the case of VTAM® terminal autoinstall, ensure that the necessary autoinstall programs and transactions are installed. These are your autoinstall control program, the transactions CATA and CATD, and the programs DFHZATD and DFHZATA. The CICS-supplied autoinstall control program, DFHZATDX or DFHZATDY, accepts a request from any console, provided an autoinstall model for a console is found in the AMT. Use the model definition supplied in group DFHTERMC, or alternatively create your own autoinstall console models (see The autoinstall control program for MVS consoles)

If, when your CICS system is in production, you want to restrict the consoles that are allowed to be autoinstalled, control this in the autoinstall control program. There are other reasons why you might write your own autoinstall control program, such as security requirements or varying the default delete-delay period. See the CICS Customization Guide for information about including support for consoles in your autoinstall console program. You may have to change the way you use console names and terminal names, or you may have to make special arrangements in the autoinstall control program to allow you to continue to use the names in the way that you do.