CSI baseline CSI-IFX-2026-10-22 · 22 October 2026. Limited to the registered source set. Application execution and proposed tests were not run; source findings do not establish runtime behaviour.
Informix4GL Demo: deprecation, support and upgrade requirements
In this document
Dated baseline: 22 October 2026 · One declared-dependency support finding and one conditional compatibility finding
Support decisions supported by the evidence
The iText declaration can be correlated with an explicit vendor lifecycle statement. The Informix evidence supports a target-dependent Java prerequisite and a bounded lifecycle lookup, but it does not support an Informix end-of-life finding or a conclusion about the installed edition's entitlement. The report keeps those decisions separate. IFX-S-ITEXT-EOL IFX-S-IBM-JRE IFX-S-IBM-LIFECYCLE
IFX-F-001: declared iText dependency belongs to an unsupported family
Status: externally correlated support finding on the launch declaration.
The retained launch configuration names itext-2.1.7.jar. The vendor's iText 2 page identifies that family as end of life and unsupported. That is sufficient to flag the declared dependency for a support decision. The conclusion does not depend on proving CVE-2017-9096 applicable, and it does not mean that a report has failed. IFX-S-E0014 IFX-S-ITEXT-EOL
The declaration alone does not prove the contents of the deployed jar or any separate support arrangement. It also leaves actual callers unknown. The framework's Report implementation is unavailable in the retained evidence, so the named labels, accounts-receivable and invoice functions are change-assessment surfaces pending a use map. IFX-S-C10 IFX-S-E0012
Decision paths
| Evidence obtained | Appropriate next decision | Verification required |
|---|---|---|
| The declared jar is absent from the assessed build | Correct the inventory and finding scope for that build. | Retain the artifact inventory and build identity. |
| The jar is present and proven unnecessary | Consider removal from the distribution and launch configuration. | Demonstrate the agreed application and report behaviours without it. |
| The jar is present and used | Assess a supported PDF-library or framework target. | Review API, output, packaging and licence implications; characterise and compare affected behaviour. |
| Identity or use remains unresolved | Keep IFX-F-001 open on the declaration. | Complete IFX-V-001 and IFX-V-002 before asserting an affected caller set or completed remediation. |
The last two columns are proposed engineering decisions. They follow the evidence gaps recorded in IFX-S-E0012 and IFX-S-E0014 and the vendor lifecycle position in IFX-S-ITEXT-EOL.
A replacement should be selected against the application's actual use. This assessment does not prescribe a particular successor version or treat the work as an automatic jar substitution. IFX-V-003 and IFX-V-004 supply the retained report and order/invoice scenarios needed to judge a change. IFX-S-C13
IFX-F-003: an Informix upgrade can change the Java prerequisite
Status: conditional on the selected target.
IBM's system-requirements page, as recorded in the baseline, states that bundled Java was removed from Informix 14.10.FC11 onward and identifies a Java 11 prerequisite for 14.10.FC11W1 and later. The retained application setup names an FC5 archive. An upgrade across that packaging boundary therefore needs an explicit decision about the Java required by the selected installation and tools. IFX-S-IBM-JRE IFX-S-E0014
The current Java distribution and version are unknown, and no upgrade target has been selected. The finding does not assert that FC5 currently lacks Java or that the application has failed. A suitable Java environment may already be available; the missing evidence is whether it meets the exact target's requirements and is used by the relevant tools. IFX-S-C10 IFX-S-IBM-JRE
For IFX-V-005, select a precise server edition, fix pack, platform and immutable image or archive. Check that target's requirements, provision its Java prerequisite explicitly, and verify startup and JDBC operations before the order and reporting regressions. If the target does not cross the documented change, record the target-specific rationale rather than carrying the compatibility finding forward as an unconditional defect. IFX-S-IBM-JRE IFX-S-C13
Informix lifecycle outcome
The retained IBM Enterprise Edition 14.10.x page did not show an end-of-support date in the retrieved content. The installed edition and entitlement are also unknown. This assessment therefore makes no Informix end-of-life finding and no affirmative support-entitlement determination. A later support decision needs the exact edition and the applicable vendor support terms. IFX-S-IBM-LIFECYCLE IFX-S-C10
Remaining support gaps
No authoritative applicable lifecycle finding was established for SwingX in the bounded search. JDBC, framework, Java and image records lack the identities needed for a precise lifecycle comparison. Collecting those identities through IFX-V-001 is the prerequisite for extending the support assessment. A non-result in a bounded search is not evidence that a component is supported. IFX-S-C10 IFX-S-E0014
This Wayfinder CSI assessment is limited to the registered source set. Findings, inference, recommendations and evidence gaps remain distinct. It does not establish a completed migration, production suitability or functional equivalence.
Independent Harten analysis of the Informix4GL Demo source material. No maintainer endorsement is implied. The exact analysed upstream revision remains unbound. The source records do not establish runtime behaviour or equivalence between the 4GL and Java implementations.
Inspect the evidence and external lookups · Read the existing application documentation edition.