Running setup programs

The setup program is typically initiated by a program list table (PLT) program.

About this task

Using this method, the setup program is run automatically at every CICS startup. Follow this procedure:

Procedure

  1. Write your setup program.
  2. Define it to CICS, using RDO, and associate it with a transaction. You can define your setup program statically, or allow it to be installed automatically (autoinstalled) when it is invoked. For details of the CICS autoinstall facility for programs, see Autoinstalling programs, map sets, and partition sets.
  3. Write a PLT program containing the command:
    EXEC CICS START TRANSID(tranid) INTERVAL(1)
    where tranid is the ID of your setup transaction. For programming information about writing PLT programs, see Writing initialization and shutdown programs.
  4. Define your PLT program to CICS, and include it in the second part of the program list table post initialization (PLTPI) list. For information about coding entries in the PLTPI list, see Program list table (PLT).

What to do next

There may be a good reason for you to decide not to use the PLT to start the setup transaction. For example, you might want to have several, time-sensitive, setup programs, each having a corresponding discard program. If you decide not to use the PLT, you must arrange to start the setup transactions manually.

Restrict access to the setup programs, because they are of a sensitive nature.



dfhp71j.html | Timestamp icon Last updated: Sunday, 4 June 2017