Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: C07 — System Context and Components — topic detail
Forms and compiled artifacts
In this document
System: Forms and compiled artifacts
Seven .frm files—ordcur.frm, order.frm, orderform.frm, p_ordcur.frm, state_list.frm, stock1.frm, and stock_sel.frm—were reported as binary or NUL-containing and were not analyzed as ordinary text. Their corresponding .per files provide source-level definitions, but do not prove byte-for-byte or semantic identity with the compiled forms. File-identifying hashes establish artifact identity but do not validate contents or generation history. E0009 E0010
The source also references forms such as custform, custwind, state_list, ordcur, and p_ordcur. Missing or unverified binary forms and referenced runtime forms remain a verification gap; a source-level form definition should not be treated as proof that the corresponding compiled or runtime form is present and equivalent. E0008 E0009
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.