Wayfinder / Case study / CSI reports

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: deprecation and support assessment

In this document

Assessment baseline: 22 October 2026. No applicable deprecation notice or end-of-support date has been established. The evidence identifies technologies and source dependencies, but not the installed product releases, maintenance levels or support arrangements needed to assign a lifecycle deadline. CARD-SRC-05 CARD-SRC-06

Current lifecycle position

CARD-FIND-03 records an inventory gap. It does not state that CardDemo or any installed dependency is unsupported. A sample application's technology choices and project badge cannot establish the lifecycle status of a particular installation. CARD-SRC-01 CARD-SRC-05 CARD-SRC-06

Notice or support question Evidence required for an application decision Position at this baseline
Is an installed release approaching or past a support deadline? Exact product/edition, platform, installed release, applicable support terms and an authoritative lifecycle notice. No deadline assigned.
Is an API or feature used here deprecated? A specific vendor notice and evidence that the affected API/feature and conditions occur in the selected deployed baseline. No applicable deprecation notice established.
Is a migration or replacement required by a vendor change? A matched notice, its required action and a bound application/runtime inventory. No vendor-mandated migration asserted.
Which application behaviour should a relevant runtime change preserve? Source relationships and candidate verification linked to the selected build. Two useful traces are identified; verification is not run. CARD-SRC-02 CARD-SRC-03 CARD-SRC-09

Product identities still needed

The inspected artefacts do not establish installed versions or service levels for MQ, CICS, IMS, Db2, the COBOL compiler or z/OS. The optional authorisation extension is documented as dependent on the base application and additional technologies; its deployment in any particular environment is unverified. CARD-SRC-05 CARD-SRC-06

Dependency Evidence currently available Required next record
IBM MQ Request/reply calls and source options. CARD-SRC-02 Installed product/release/service level, relevant deployment mapping and support arrangement.
CICS Program statements and sample transaction/file definitions. CARD-SRC-02 CARD-SRC-03 CARD-SRC-04 Installed product/release/service level, effective resource settings and support arrangement.
IMS Optional authorisation database and persistence path. CARD-SRC-06 CARD-SRC-08 Installed product/release/service level, effective resource configuration and support arrangement.
Db2, COBOL compiler and z/OS Technology context without established installed identities. CARD-SRC-05 CARD-SRC-06 Exact installed identities and their relationship to the selected application build.

CARD-TEST-04 requests these facts before any notice is applied. Record the date and provenance of each value. An unverified field should remain unknown rather than inheriting a version from a README badge or a documentation URL.

Vendor documentation is semantic context

The IBM references used in this assessment describe MQ no-syncpoint behaviour, CICS rollback and FILE recovery configuration. Their URL versions identify the documentation consulted. They do not establish an installed MQ 9.4.x or CICS 6.x runtime, and they are not lifecycle findings. CARD-SRC-10 CARD-SRC-11 CARD-SRC-12 CARD-SRC-13

The distinction matters because the source supports an application-impact question independently of whether a support deadline exists. A reviewer can already identify what would need checking after a relevant runtime or configuration change, while leaving the reason and timing of that change unresolved.

Behaviour to preserve during a relevant change

For the optional authorisation path, preserve the meaning and correlation of the approval/decline reply and examine its relationship to durable authorisation state. The retained handler sends its reply before the later IMS write. Candidate C13-13 provides a starting point for observing this boundary if an applicable MQ, IMS or CICS change is planned. CARD-TEST-01 remains not run. CARD-SRC-02 CARD-SRC-08 CARD-SRC-09

For account maintenance, preserve validated paired updates, unchanged-field behaviour and stale-update handling. A change to CICS recovery, file definitions or catalog settings should direct review to the effective recoverability of ACCTDAT and CUSTDAT. The rollback statement and sample RECOVERY(NONE) settings do not by themselves establish the actual recovery outcome. CARD-TEST-02 and CARD-TEST-03 remain not run. CARD-SRC-03 CARD-SRC-04 CARD-SRC-09 CARD-SRC-12 CARD-SRC-13

These are conditional change-review implications, not evidence that a change has occurred or is required.

When a lifecycle finding can be added

A reviewer can add a dated lifecycle finding once the installed identity and support arrangement are bound, the official notice is retained with its conditions, and the application-to-runtime relationship is established. The finding should distinguish a vendor deadline from a proposed application change date, and should explain which of the recovered paths the notice affects.

Before adopting an expected result for a change test, complete CARD-TEST-05. The retained source archive and public PDF edition remain separate baselines. No older retained specification is automatically authoritative for the selected executable. CARD-SRC-01 CARD-SRC-07 CARD-SRC-09 CARD-SRC-14

At this baseline, the action is to collect the missing inventory and support evidence, then evaluate a specific notice. The report supplies no invented retirement date, support commitment or migration deadline.