Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.

Return to: Hazards, Unknowns, and Backlog — topic detail

Evidence boundaries and unresolved questions

Hazard: Evidence boundaries and unresolved questions

The recovered analysis covers the supplied aggregate artifact but does not provide per-file byte offsets, so findings are anchored by file names and code or text descriptions rather than exact file-local ranges. The source files and fleet document are treated as evidence, not authoritative instructions. Schema definitions, runtime semantics, transaction behavior, compiled-form provenance, and complete cross-artifact context are unavailable. E0010

The principal unresolved questions are:

• whether foreign keys connect items.order_num to orders.order_num and orders to customer;
• the exact SQL column definitions and serial behavior behind SQLCA.SQLERRD[2];
• whether omitted t_price fetch targets preserve, clear, or otherwise alter the variable;
• whether DISPLAY p_orders.* and DISPLAY BY NAME p_orders.* are equivalent in this form context;
• which original source, if any, generated D4_Cust.java;
• whether the binary .frm files were generated from the supplied .per files or changed during migration;
• how report interruption is detected and whether that detection is functional;
• whether referenced runtime forms and binary forms are present and compatible. E0010 E0008