Oninit® SQLMorph — What Is Refused
A construct that cannot be converted is always an error with a code, a file, a line and a column, never a silent skip.
Because a function that quietly drops a statement would give wrong answers, the whole file is refused and nothing is
written. Messages look like
order_entry.4gl:2:5: error SQLM-4GL-UI003: enter_order: OPEN WINDOW: interactive/screen statement is not allowed in a converted function.
| Code | Meaning |
|---|---|
SYN010-017 | Syntax errors. |
SEM001-004 | GLOBALS, module-level DEFINE, MAIN, REPORT: a UDR is one function with no shared state. Pass globals as arguments. |
SEM005-031 | Names, types, labels; inconsistent RETURN counts or types; an argument or returned value whose type cannot be determined. |
UI001-004 | Windows, forms, menus, prompts, INPUT, DISPLAY ... TO and the other screen statements. Rejected even in code that never runs, so behaviour cannot change silently. |
ENG001-003 | File, pipe and process I/O, connection statements, session SET. |
NYI001 | BEGIN / COMMIT / ROLLBACK WORK: refused at conversion, because the calling statement owns the transaction. Remove it and have the caller manage the transaction. |
NYI002-003 | TEXT and BYTE; an inner array used as a whole (a[i].b without a subscript); some built-ins. |
NYI004-005 | an empty SQL ... END SQL, LOCATE, PUT ... FROM with an expression. |
NYI006 | Assigning to sqlca.*; more than eight return values. |
“Not yet” (NYI) entries are gaps in the backend, not decisions: they are the list of what remains
to be converted. The UI, ENG and SEM001-004 entries are by design.
--json-diagnostics prints the same information as JSON, one object per diagnostic, for a build script.