CSI baseline CSI-CARD-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.

CardDemo: impact graphs

Assessment baseline: 22 October 2026. These graphs connect inspected application relationships to business behaviour and candidate checks. They distinguish what the source documents from what is inferred and what remains unresolved. They are static evidence graphs; no application execution or test result is represented. CARD-SRC-02 CARD-SRC-03 CARD-SRC-09

How to read the edges

Dotted edges mark inferred or unresolved relationships. The text label states which class applies. Sources for each edge group follow its graph.

Authorisation reply and IMS persistence

The retained handler makes the credit decision and sends a correlated reply before the later IMS write. The request and reply use no-syncpoint options. The graph therefore identifies the response/state comparison as a concrete verification target without claiming that an actual requester received an inconsistent approval. CARD-FIND-01 is externally correlated with IBM API semantics; CARD-FIND-03 leaves deployed runtime applicability unresolved. CARD-SRC-02 CARD-SRC-10 CARD-SRC-11

flowchart TD
    Q["MQGET request: no syncpoint"] -->|"Documented: received by"| H["COPAUA0C"]
    H -->|"Documented: evaluates"| D["Available-credit decision"]
    D -->|"Documented: determines"| R["Correlated MQPUT1 reply: no syncpoint"]
    H -->|"Documented: writes after reply"| S["IMS authorisation summary and detail"]
    R -.->|"Inferred: exposes decision"| B["Received response agrees with recorded state"]
    S -.->|"Inferred: supplies state to compare"| B
    B -->|"Documented candidate: C13-13"| T["CARD-TEST-01: not run"]
    M["Installed MQ release: unknown"] -.->|"Unresolved: inventory binding"| I["Bound runtime inventory"]
    C["Installed CICS and IMS releases: unknown"] -.->|"Unresolved: inventory binding"| I
    I -.->|"Inferred: scopes future notice regression"| T

The IMS state is described as DBPAUTP0 summary/detail persistence using PAUTSUM0 and PAUTDTL1. A later CICS syncpoint appears in the retained processing loop. Neither fact supplies evidence that a previously available reply would be withdrawn or that a controlled IMS failure has already been observed. CARD-SRC-02 CARD-SRC-08 CARD-SRC-10

Paired account/customer update and rollback

The account-maintenance path compares original values, rewrites the account and then the customer. A customer-rewrite failure requests rollback. Whether the installed resources restore a consistent pair remains unresolved. CARD-FIND-02 therefore connects source control flow to a configuration review and two candidate scenarios. CARD-SRC-03 CARD-SRC-04 CARD-SRC-09

flowchart TD
    A["CAUP account update"] -->|"Documented: executes"| P["COACTUPC: original-value comparison"]
    P -->|"Documented: rewrites first"| AC["ACCTDAT account"]
    P -->|"Documented: rewrites second"| CU["CUSTDAT customer"]
    CU -->|"Documented: failure triggers"| RB["SYNCPOINT ROLLBACK request"]
    RB -->|"Documented: resource dependency"| RC["Effective FILE and catalog recovery"]
    RC -.->|"Unresolved: determines rollback outcome"| B["Paired account/customer integrity"]
    AC -->|"Documented: participates"| B
    CU -->|"Documented: participates"| B
    B -->|"Documented candidate: C13-03"| T2["CARD-TEST-02: not run"]
    P -->|"Documented candidate: C13-04"| T3["CARD-TEST-03: not run"]
    I2["Bound runtime inventory"] -.->|"Inferred: scopes future notice regression"| T2

What would change an edge's status

CARD-TEST-04 can establish installed identities and deployment relationships. CARD-TEST-02 can provide effective resource settings and observed recovery outcomes. CARD-TEST-01 and CARD-TEST-03 can supply observations for their respective behaviour boundaries. Those tasks have not yet supplied evidence.

CARD-TEST-05 must establish the authority of the selected candidate scenarios for the chosen executable. Until then, a documented candidate edge means that the public edition proposes the scenario; it does not mean that the expected result is an approved requirement or that the retained source and PDF edition are identical. This preserves CARD-FIND-04. CARD-SRC-01 CARD-SRC-07 CARD-SRC-09 CARD-SRC-14