Errors and exception conditions
All FEPI commands support the RESP and RESP2 options to signal successful completion or an exception condition. Alternatively, you can use HANDLE CONDITION to trap errors.
Most FEPI command errors give the ‘INVREQ’ exception condition. The particular error in each case is uniquely identified by the RESP2 value.
If there is an error, the command does nothing and the output arguments are not changed. Note, however, that commands such as FEPI SEND may have transferred data before the condition is recognized.
Both RESP and RESP2 take, as an argument, the name of a user-defined fullword
binary data area. Possible values of the RESP2 option are given in the description
of each of the commands and a full list is given in FEPI RESP2 values. The following copy books provide declarations for
the RESP2 values:
- DFHSZAPA for Assembler language
- DFHSZAPO for COBOL
- DFHSZAPP for PL/I
- DFHSZAPC for C.
The INVREQ condition and the following RESP2 values can occur for any application programming command:
- RESP2
- Meaning
- 10
- Command bypassed by user exit.
- 11
- FEPI not installed, or not active..
- 12
- CICS shutting down, command not allowed.
- 13
- FEPI unavailable.
- 14
- FEPI busy or cannot get storage..
- 15
- Unknown command..
- 16
- Internal error.
- 17
- FEPI cannot get storage for user exit..
- 18
- Command failed through operator or system action..