MFJAMS follows the same condition code principles as the mainframe does:
| Condition code | Description |
|---|---|
| 0 | The function was executed as expected. An informational messages might display. |
| 4 | A problem was encountered completing the function, but it was possible to continue. The continuation may cause unexpected results, but no permanent harm will have been done by such continuation. For example, the system was unable to locate an entry in a LISTCAT command. A warning message is displayed. |
| 8 | The requested function was completed, but major specifications were unavoidably bypassed. For example, an entry to be deleted or altered could not be found in the catalog, or a duplicate name was found while an entry was being defined and the define action was terminated. |
| 12 | The requested function could not be performed. This condition code is set as a result of a logical error. A logical error condition exists when inconsistent parameters are specified, when required parameters are missing, or when a value specified for key length, record size, or buffer space is too small or too large. |
| 16 | A severe error occurred that caused the remainder of the command stream to be flushed. For example, a system output data set cannot be opened (a SYSPRINT DD statement was missing, for example). |