FEPI server adapter data-containers

FEPI server adapters use data-containers to store state and status data and inputs and outputs for the FEPI request processing.

The following tables list the FEPI data-containers that are used during request processing of simple and complex service flows.

Table 1. FEPI server adapter data-containers for simple flows
Name Size (bytes) Contents and usage
ADAPTER.OUTPUT Variable up to a maximum of 32 760 It contains output from the FEPI server adapter.
ADAPTER.STATUS 512 It contains status information for the FEPI server adapter, including:
  • Interaction status
  • Error information
FEPI.INPUT Variable up to a maximum of 32 760 Mapped input data.
FEPI.STATE 6 144 Target and node state information for the FEPI server adapter. This data-container is used only when a FEPI server adapter error occurs.
Table 2. FEPI server adapter data-containers for complex flows
Name Size (bytes) Contents and usage
ADAPTER.SHARED.C Compiler limit for IBM® COBOL It contains the application context that is shared between FEPI server adapters. This data-container ensures that data is kept consistent between multiple FEPI server adapters in a complex service flow.
FEPI.INPUT Variable up to a maximum of 32 760 Mapped input data.
FEPI.OUTPUT Variable up to a maximum of 32 760 It contains output from the FEPI server adapter.
FEPI.STATE 6 144 Target and node state information for the FEPI server adapter. This data-container is used only when a FEPI server adapter error occurs.
NAVIGATOR.STATUS 512 It contains status information for the FEPI server adapter, including:
  • Interaction status
  • Error information


fepicontainers.html | Timestamp icon Last updated: Sunday, 4 June 2017