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.
- DFHSZAPA for assembler language
- DFHSZAPO for COBOL
- DFHSZAPP for PL/I
- DFHSZAPC for C.
The following conditions and RESP2 values can occur for any system programming command:
| Condition | RESP2 | Meaning |
|---|---|---|
| INVREQ | 10 | Command bypassed by user exit. |
| INVREQ | 11 | FEPI not installed, or not active. |
| INVREQ | 12 | CICS shutting down, command not allowed. |
| INVREQ | 13 | FEPI unavailable. |
| INVREQ | 14 | FEPI busy or cannot get storage. |
| INVREQ | 15 | Unknown command. |
| INVREQ | 16 | Internal error. |
| INVREQ | 17 | FEPI cannot get storage for user exit. |
| INVREQ | 18 | Command failed through operator or system action. |
| NOTAUTH | 100 | Not authorized for this command. |
If there is an error, the command does nothing, and the output arguments are not changed.
By their nature, some commands (for example, FEPI SET NODE INSERVICE) initiate a function and return before the function has completed. Errors in the execution of the function cannot be reported as an exception condition on the command. Such errors are reported by writing a record to a transient data (TD) queue and a message to the message log CSZL. See Transient data queue records for details.