Configuring CICS

Before you begin

Getting started with FEPI covers everything that FEPI itself requires: the RDO group DFHFEPI in the startup group list; definitions of the transient data queues CSZL and CSZX; and any required security access controls.

About this task

Now you have to define your FEPI applications to CICS in the usual way. This includes the setup program, any common functions, and any additional transient data queues that you need for handling pool-specific events. Note that, in an intercommunication environment, FEPI itself must be run in the application-owning region (AOR) and all transactions that FEPI may start must run locally. This is because FEPI commands cannot be function shipped.

Procedure

  1. Define transactions that are to be started by FEPI (the event handlers and pseudoconversational access programs) as CICS started tasks, with SPURGE=NO and TPURGE=NO to prevent them from being accidentally canceled by CICS
  2. Define any additional transient data queues. See Transient data queues for details of the queues.
  3. Before starting CICS, you should ensure that your system has enough storage available to support your FEPI configuration: for details see Planning FEPI storage.
  4. If you are using a setup transaction to install your FEPI nodes, targets, and pools that is started by a program list table (PLT) program, you need to include your PLT program in the second part of the program list table post initialization (PLTPI) list. This process is described in Running setup programs. If you use this method, you need to include your PLT program in the second part of the program list table post initialization (PLTPI) list.


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