CardDemo application documentation

Account update includes a specific rollback path

The documentation reports that COACTUPC validates input, compares values retained in commarea, locks records and rewrites account and customer data. If the customer rewrite fails after a successful account rewrite, it checks the CICS response and performs SYNCPOINT ROLLBACK.

This is the reported recovery path. It does not prove that every update failure is covered by one atomic boundary. The chapter also retains the reported lookup and validation concerns, whose runtime effects remain unproven. Read account inquiry and maintenance in chapter 04.

Interactive entry and batch posting have different responsibilities

COTRN02C validates and adds an interactive transaction. CBTRN02C performs the evidenced daily posting work: checking the account and credit conditions, recording rejected input, updating category balances and the account, and writing the transaction. The similarly named CBTRN01C performs lookups without visible posting writes in the supplied analysis.

The batch sequence can update category balances before an account rewrite fails. The visible path does not show rollback or compensation; this supports a possible partial-update state, without proving that production data reaches it. Read transaction entry, inquiry and posting in chapter 04.

The characterisation tests are proposed scenarios

Chapter 13 proposes checks for account maintenance, interactive transactions, batch acceptance and rejection, and other current behaviour. It states that these scenarios have not been executed, passed or verified in a runtime environment. Where the source conflicts or depends on missing definitions, the proposed test retains the question. Read the candidate characterisation tests.