The installation process

The process comprises the following tasks:

A note about loading FEPI modules into the LPA

Any of the FEPI modules can be loaded in the MVS™ Link Pack Area (LPA). However, as with CICS modules in general, it is not recommended that you do so. (For information about installing modules in the LPA, see the CICS Transaction Server for z/OS® Installation Guide.)

Updating CICS definitions

The RDO group DFHFEPI, which is on the product tape, contains definitions of the following resources:

DFHFEPI is included in the default startup group list, DFHLIST.

You must use the CEDA transaction:

Transient data queues

Sample definitions for the transient data (TD) queues required by FEPI are supplied in group DFHDCTG. You can use the sample definitions, or create your own, together with any extra queues that you need. The required queues are:

CSZL
The FEPI message log. You can define CSZL as an intrapartition, extrapartition, or indirect queue. Note that CSZL must be defined as non-recoverable.

It is recommended that you define CSZL as an indirect queue, pointing to CSSL.

CSZX
The queue for information about unexpected events (including setup errors) that do not relate to specific pools. You can define CSZX as an intrapartition, extrapartition, or indirect queue. Note, however, that it must be defined as non-recoverable.

It is recommended that you define CSZX as an intrapartition queue, with a trigger level of 1, so that each event is processed immediately it is reported. (You must also, of course, write and install the event-handling transaction that is to be triggered.)

Any pool-specific TD queues that you require
Such queues receive information about events that affect specific pools. They can be defined as intrapartition, extrapartition, or indirect queues. Note, however, that they must be defined as non-recoverable.

It is recommended that you define pool-specific queues as intrapartition queues with trigger levels of 1, so that each event is processed immediately it is reported.

For information about defining transient data queues, see the CICS Resource Definition Guide.

System initialization parameter, FEPI=YES|NO

Code FEPI=YES, to specify that FEPI is available. (The default is FEPI=NO.) For information about setting system initialization parameters, see the CICS System Definition Guide.

Command-level security

If your installation uses CICS command-level security, you can restrict access to the EXEC CICS FEPI system programming commands (and to the equivalent commands that you can issue with the CEMT master terminal transaction) by defining access authorizations to your external security manager (ESM). The commands you can protect in this way are those listed in FEPI system programming reference and in the CEMT section of Operator control of FEPI. You cannot restrict access to the FEPI application programming commands (as listed in FEPI application programming reference).

To protect the FEPI system programming commands, use the resource identifier ‘FEPIRESOURCE’ when defining resource profiles to the ESM. Note that, if you use command security, you must ensure that authorized users of CEMT are also authorized to use the FEPI commands.

For RACF® users, details of how to define resource profiles to the ESM are in the OS/390 Security Server (RACF) Security Administrator’s Guide. For information about using RACF with CICS, see the CICS RACF Security Guide. Users of other security managers must refer to the documentation for their own product.

Installing FEPI resource definitions

Ensure that the RDO group DFHFEPI is in your startup group list. (DFHFEPI is in the DFHLIST startup group list, so this should have been done automatically when you installed CICS.)

Starting CICS

Start your CICS region. This is described in the CICS System Definition Guide.

[[ Contents Previous Page | Next Page Index ]]