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

Return to: Integration data flow

Integration data flow

Who sends which information to whom, in which direction, and through what mechanism?

This view models supported information flows around the legacy Informix-4GL application and its stores7 database. The order program sends customer, order, and item operations to the database, while queries return customer, order, stock, and state information to application screens. E0009 The customer query program constructs SQL against the customer table and retrieves matching rows; its state loader selects rows from the state table. E0009

The model keeps extract files and compiled forms separate from database flows. The evidence describes orders.unl, stock.unl, manufact.unl, state.unl, and syscolatt.unl, but does not establish that the application sends to or receives from those files. E0009 The .per files describe forms, while the corresponding .frm files are binary or unsupported for text analysis; semantic identity between them is unresolved. E0009E0010

Diagram

flowchart LR
  n0e66b17c44cd728d5e74["Order Management Program"]
  nbe2facc2132cbd4018b2["Customer Query Program"]
  n908bfbf241bed220efdc["stores7 Database"]
  n27cb6bedca2e690e6165["Order Forms"]
  n0ea28fb96efbe5f820cd["Orders Extract"]
  n0eb71f1d7ac9c1923fda["Stock Records"]
  n4dcc67d445672ba6a90f["Manufacturer Records"]
  n6e90622414d3e73001ce["State Reference Records"]
  nfa22c9357357ccbba6bd["System Catalog Attributes"]
  n97ba0f4aec3185676d3c["Compiled Form Artifacts"]
  n0e66b17c44cd728d5e74 -->|"Order operations"| n908bfbf241bed220efdc
  n908bfbf241bed220efdc -->|"Order query results"| n0e66b17c44cd728d5e74
  n908bfbf241bed220efdc -->|"Stock lookup"| n0e66b17c44cd728d5e74
  nbe2facc2132cbd4018b2 -->|"Customer search"| n908bfbf241bed220efdc
  n908bfbf241bed220efdc -->|"Customer query results"| nbe2facc2132cbd4018b2
  n908bfbf241bed220efdc -->|"State reference lookup"| nbe2facc2132cbd4018b2
  n0e66b17c44cd728d5e74 -.->|"Order form display (inferred)"| n27cb6bedca2e690e6165

Elements

Order Management Program

Kind: component
Basis: reported
Description: The order program displays the order form, accepts customer, order, and item input, inserts orders and items, queries a customer’s orders, and can modify or delete a selected order. E0009
Evidence: E0009
Goal: Not applicable

Customer Query Program

Kind: component
Basis: reported
Description: The customer query program connects to stores7, constructs customer search criteria, selects matching customer rows, and loads state rows for state selection. E0009
Evidence: E0009
Goal: Not applicable

stores7 Database

Kind: store
Basis: reported
Description: The application sources declare or connect to a database named stores7; the displayed forms and programs reference customer, orders, items, stock, manufact, and state tables. E0009
Evidence: E0009
Goal: Not applicable

Order Forms

Kind: component
Basis: reported
Description: The order form definitions expose customer, order, item, stock, manufacturer, quantity, price, and total fields mapped to database or form-only attributes. E0009
Evidence: E0009
Goal: Not applicable

Orders Extract

Kind: store
Basis: reported
Description: The extract contains 15 pipe-delimited order records with order identifiers, dates, delivery text, flags, identifiers, and numeric values. E0009
Evidence: E0009
Goal: Not applicable

Stock Records

Kind: store
Basis: reported
Description: The stock extract contains stock numbers, manufacturer codes, descriptions, prices, units, and unit descriptions; the order program retrieves description and unit price from stock after stock and manufacturer values are entered. E0009E0010
Evidence: E0009, E0010
Goal: Not applicable

Manufacturer Records

Kind: store
Basis: reported
Description: The manufacturer extract contains three-letter manufacturer codes paired with manufacturer names, including SMT/Smith, ANZ/Anza, NRG/Norge, HSK/Husky, and HRO/Hero. E0009
Evidence: E0009
Goal: Not applicable

State Reference Records

Kind: store
Basis: reported
Description: State records contain two-letter codes and state names; the customer query program selects state rows and presents them for selection. E0009
Evidence: E0009
Goal: Not applicable

System Catalog Attributes

Kind: store
Basis: reported
Description: The catalog extract contains table names, column names, numeric attributes, flags, and optional conditions for customer, orders, items, and stock records. E0009
Evidence: E0009
Goal: Not applicable

Compiled Form Artifacts

Kind: store
Basis: reported
Description: The compiled .frm files for order and selection forms are reported as binary or NUL-containing and were not analyzed as text. Their correspondence with the .per definitions is unresolved. E0009E0010
Evidence: E0009, E0010
Goal: Not applicable

Relationships

Order operations

From: Order Management Program
To: stores7 Database
Relation: sends
Basis: reported
Description: The order program sends customer selection, order input, item input, order insertion, item insertion, order modification, and deletion operations to the database. The source explicitly describes inserting orders and items and updating or deleting selected orders and items. E0009
Information: Customer identifiers, order dates, order metadata, item identifiers, stock numbers, manufacturer codes, quantities, calculated totals, and order or item changes. E0009
Mechanism: Informix-4GL SQL statements, prepared queries, cursor operations, and database INSERT, UPDATE, DELETE, and SELECT operations. E0009E0010 Evidence: E0009 E0010

Order query results

From: stores7 Database
To: Order Management Program
Relation: sends
Basis: reported
Description: The order program obtains a customer and iterates through that customer’s orders, displaying each order and its items. E0009
Information: Customer order records, order dates, ship dates, order metadata, and associated item records. E0009
Mechanism: SQL selection and cursor retrieval into program records and item arrays. E0009 Evidence: E0009

Stock lookup

From: stores7 Database
To: Order Management Program
Relation: sends
Basis: reported
Description: During item entry, the program retrieves stock description and unit price after stock and manufacturer values are entered. E0009
Information: Stock description and unit price for the entered stock-number/manufacturer-code combination. E0009E0010
Mechanism: SQL lookup against the stock table; exact missing-row behavior is not established because no visible status or NOTFOUND handling is shown. E0010 Evidence: E0009 E0010

Customer search

From: Customer Query Program
To: stores7 Database
Relation: sends
Basis: reported
Description: The customer query program collects query-by-example criteria, builds a SELECT * FROM customer WHERE statement, prepares it, and opens a cursor. E0009
Information: Customer search criteria. E0009
Mechanism: Informix-4GL CONSTRUCT BY NAME, dynamic SQL preparation, and a scroll cursor. E0009 Evidence: E0009

Customer query results

From: stores7 Database
To: Customer Query Program
Relation: sends
Basis: reported
Description: The program iterates through matching customer rows into a customer record and displays each result in the customer form. E0009
Information: Customer records matching the constructed search criteria. E0009
Mechanism: Cursor fetches into the program’s customer record. E0009 Evidence: E0009

State reference lookup

From: stores7 Database
To: Customer Query Program
Relation: sends
Basis: reported
Description: get_states() selects all rows from the state table ordered by state name and stores them in the program’s state array; state selection then uses those loaded records. E0009
Information: State codes and state names. E0009
Mechanism: SQL SELECT ordered by sname, followed by storage in an in-memory state array. E0009 Evidence: E0009

Order form display

From: Order Management Program
To: Order Forms
Relation: sends
Basis: inferred
Description: The order program displays customer, order, item, stock, manufacturer, quantity, price, and total values through the declared order form fields. The evidence supports the form mappings and program display behavior, but does not provide a separate runtime observation of this specific data transfer. E0009
Information: Customer details, order metadata, item details, stock descriptions, quantities, prices, and calculated totals. E0009
Mechanism: Informix-4GL form display and input operations; exact compiled-form behavior is unknown because the corresponding .frm artifacts were not text-analyzed. E0009E0010 Evidence: E0009 E0010

Gaps

No source-supported sender or receiver is established for Orders Extract, Stock Records, Manufacturer Records, or System Catalog Attributes as standalone files. Their contents are documented, but file-level transfer into or out of the application is not shown. E0009

The evidence does not establish whether stock.unl, manufact.unl, state.unl, or orders.unl populate corresponding stores7 tables. E0009 It also does not establish whether the manufacturer extract is used by the order program at runtime, even though manufacturer fields and the manufact table appear in form definitions. E0009

The compiled .frm artifacts cannot be verified against the .per definitions, and no deployment or component-host assignment is established. E0009E0010 The exact database schema, referential constraints, transaction behavior, and runtime semantics for incomplete fetch targets and missing stock rows remain unknown. E0010

Recovery limitations

• Ownership, mechanism or boundary controls remain explicitly unverified.
• Some identified concepts have no supported connection.
• The view includes explicitly marked inference.

Sources

• E0009 — SHA256 c4ffb94922eae3cda2f1c6d6b1215da47b424d41fea52db3870783bd43051b30
• E0010 — SHA256 bd29371182d16de63a7651533fa5c84e151a01ea9bf23399f7f6ca0397ab0250