CPSM's wrong interpretation about some FEPI resource definitions.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server

For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server

It is worth clarifying that when the FENODDEF is installed, it installs the nodes in the NODELIST.
When the FEPOODEF is installed, it references the nodes that were just installed and which also appear in the NODELIST of the FEPOODEF.

The descriptions of the Node and Target lists in the FEPI POOL definitions state:

Node listNODELIST The node names to be used to create new connections in the pool. You can specify a maximum of 128 node names. Each node name in the list must be 8 characters long. Shorter node names should be padded to 8 characters using blanks. These names should be defined by creating corresponding FENODDEFs.
Format: AdvancedTarget region listTARGETLIST The target names used to create new targets in the pool. You can specify up to a maximum of 32 target names. Each target name in the list must be 8 characters long. Shorter target names should be padded to 8 characters using blanks. These names should be defined by creating corresponding FETRGDEFs.
Format: Advanced

If we take the NODELIST first, what this means is that: 

1) First you need to define a FENODDEF which lists the nodes e.g. FENODDEF (FENODES1) has a NODELIST of "NODE0001 NODE0002 NODE0003" 
2) Then you need to define a FEPOODEF which also lists the nodes e.g FEPOODEF(FEPOOL1) has a NODELIST of "NODE0001 NODE0002 NODE0003"

It does not mean that you need to defined a FEPOODEF which has a NODELIST of "FENODES1"

The same applies to the TARGETLIST.

If you try the above then you should find that it works.