z/OS Communications Server control blocks

FEPI uses standard z/OS® Communications Server programming facilities for its communication. The way in which z/OS Communications Server control blocks interact with FEPI control blocks is as follows:

ACBs
Each FEPI node represents a terminal connected to the partner system. Consequently, each node has an access control block (ACB). This ACB is opened when the node is acquired, and closed when the node is released.
NIBs
Each FEPI target contains the applid of the back-end system. This is used to build a node initialization block (NIB), when a connection is acquired by issuing a z/OS Communications Server REQSESS request. In common with CICS® data communication, the “confidential” flag is set off.
RPLs
There are two types of request parameter list (RPL) used by FEPI:
  • Each FEPI outbound request causes the generation of an RPL. This RPL lasts only for the duration of the FEPI request.
  • Each FEPI node has a “Receive-Any” RPL. When an inbound flow occurs, this RPL is attached to the FEPI connection, and turned into a “Receive-Specific” RPL. When the flow has been received, a new “Receive-Any” RPL is generated and attached to the node.


dfhs35b.html | Timestamp icon Last updated: Monday, 5 June 2017