Implementing program autoinstall

The only program that cannot be autoinstalled is the program autoinstall control program.

Procedure

  1. Decide whether your programs are eligible for autoinstall
    All other programs can be autoinstalled, including:
    • All other user-replaceable programs
    • Global user exits (GLUEs) and task-related user exits (TRUEs)
    • PLT programs
    User-replaceable programs and PLT programs are autoinstalled on first reference. GLUEs and TRUEs are autoinstalled when enabled.
  2. Decide whether to use autoinstall for programs

    Using autoinstall for programs can save time spent on defining individual programs, mapsets, and partitionsets. Savings can also be made on storage, because the definitions of autoinstalled resources do not occupy space until they are referenced.

    Use of autoinstall for programs can reduce the number of definitions to be installed on a COLD start, thereby reducing the time taken.

  3. Decide which programs to autoinstall

    Depending on your programs, you can choose to use a mixture of RDO and autoinstall. A suggested way to manage program autoinstall is to continue to use RDO for existing program definitions and for installing groups containing related programs. Use autoinstall as you develop and install new applications, and in test environments, where you might otherwise install large numbers of programs at CICS® startup.

  4. Enable autoinstall for programs

    You can enable autoinstall for programs either by specifying system initialization parameters by using the SET SYSTEM command.

    Three system initialization parameters relate to program autoinstall:
    PGAICTLG
    The PGAICTLG parameter specifies whether autoinstalled program definitions are cataloged. See Cataloging for program autoinstall.
    PGAIPGM
    The PGAIPGM parameter specifies whether the program autoinstall function is active or inactive.
    PGAIEXIT
    The PGAIEXIT parameter specifies the name of the program autoinstall exit.
    Three options relate to program autoinstall on the SET SYSTEM command:
    PROGAUTOCTLG
    The PROGAUTOCTLG option specifies whether autoinstalled program definitions are to be cataloged. See Cataloging for program autoinstall.
    PROGAUTOEXIT
    The PROGAUTOEXIT option specifies the name of the program autoinstall exit.
    PROGAUTOINST
    The PROGAUTOINST option specifies whether the program autoinstall function is active or inactive.

    For programming information on how to specify EXEC CICS commands, see Introduction to System programming commands, and for information on how to use CEMT, see CEMT - main terminal.

  5. Create your model program definitions

    A model definition provides CICS with one definition that can be used for all programs with the same properties. See Model definitions for program autoinstall

  6. Design and write an autoinstall control program

    The autoinstall control program provides CICS with the extra information it needs to complete an autoinstall request, such as the autoinstall model name. You can write your autoinstall program in any language supported by CICS, with full access to the CICS application programming interface. See The autoinstall control program for programs.