FEPI abends
FEPI does not (deliberately) issue either CICS® transaction abends or MVS™ abends.
However, an unexpected failure can occur in the following
places:
- In a FEPI application program when INVREQ is returned
- In the EXEC stubs
- In the FEPI adapter
- In the FEPI Resource Manager transaction (CSZI) code
- In a z/OS® Communications Server exit routine.
These abends have different results, as shown in Table 1.
| Point of failure | Result |
|---|---|
| Application | The usual transaction abend for the error condition. |
| EXEC stubs | The usual transaction abend for a failure within CICS management modules. An example of this is an ‘operation' program check, which generates a CICS AKEA abend, which in turn generates an ASRA abend. |
| FEPI adapter | The usual transaction abend for a failure within CICS management modules. An example of this is an ‘operation' program check, which generates a CICS AKEA abend, which in turn generates an ASRA abend. |
| FEPI Resource Manager | No direct effect on the application program, because the abend occurs under the CSZI Resource Manager task. This probably results in a DFHSZ4099E message (see Message DFHSZ4099E), and the failure of the Resource Manager. An example of this is an ‘operation' program check, which generates a CICS AKEA abend, which in turn generates an ASRA abend. Any CICS FEPI transactions remain waiting on the FEPI_RQE resource (for details of FEPI waits, see FEPI problem determination. |
| z/OS Communications Server exit | A z/OS Communications Server abend; a z/OS Communications Server dump is taken. Because the exit lies within the FEPI Resource Manager, the CICS abend handling routines are activated to process a “normal” failure in the Resource Manager. |