Configuring the z/OS Communications Server

For FEPI to communicate with the network, some information must be defined to the z/OS® Communications Server.

1. Each FEPI node (simulated secondary LU terminal) must have a Communications Server application minor node definition.
   The name of this minor node must be the same as the node name specified on the FEPI INSTALL NODELIST command.
   For example, the FEPI node called ‘FEPI0001' would require the following application minor node definition in the Communications Server:

   DG4FEPI1  APPL ACBNAME=FEPI0001

2. If your network uses a naming convention to manage network resources, you can allow a network-independent name to be used by specifying it on the ACBNAME keyword of the Communications Server APPL statement.If this is not the case, you can simplify the definition of the Communications Server application minor node by omitting the ACBNAME keyword (which means that the margin-name, DG4FEPI1 in the example, must be the same as the FEPI node name).

   FEPI does not impose any additional restrictions on the naming of nodes, other than that the names should not begin with DFH; apart from this, any values acceptable to the Communications Server are acceptable to FEPI.

3. If you require password protection of the minor nodes, you can use the PRTCT keyword of the Communications Server APPL statement to specify a password of 1–8 characters. The password must then be specified on the corresponding FEPI INSTALL NODELIST command.
4. If you are defining multiple FEPI nodes, you can place them all in a single member (also known as a Communications Server application major node) or in several members. You can also add them to an existing Communications Server application major node.
   How you choose to organize the Communications Server definitions can depend on how your installation manages its network resources, or how you plan to manage the FEPI configuration. The Communications Server application minor node definition statements are stored collectively as one or more members of an MVS™ partitioned data set (usually SYS1.VTAMLST), accessed by the Communications Server via the VTAMLST data-definition statement in the Communications Server startup JCL.