CICS configuration

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.

Now you have to define your FEPI applications to CICS® in the usual way. This includes the setup programs, any common functions, and any additional transient data queues that you need for handling pool-specific events.

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. See Transient data queues for details of the queues. Before starting, you should ensure that your CICS system has enough storage available to support your FEPI configuration: for details see Planning FEPI storage.

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.

Setup-initialization program in PLT

The setup transaction that installs your FEPI nodes, targets, and pools is typically started by a program list table (PLT) program. 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.

For information about coding entries in the PLTPI list, see the CICS Resource Definition Guide.

[[ Contents Previous Page | Next Page Index ]]