🌙COB
Close of Business — batch processing, job sequencing, reverse-replay, restart procedures, and how to stay calm when COB does not complete.
6 articles in this topic.
AA and COB
Reverse-replay is the most common source of AA production incidents. A back-dated change triggers a full recalculation of the arrangement history. What it does, what triggers it, and how to diagnose it.
Read the articleCOB fundamentals
A plain-English introduction to Close of Business (COB) in Temenos T24 — what it does, why it matters, what the batch actually processes, and what to do when it does not complete.
Read the articleCOB and support
A practical T24 operations guide to proving that a completed batch produced the expected business outcome, not only a successful return status.
Read the articleCOB operations
A practical guide to the checks to make when T24 COB does not continue normally after a database restore — state verification, evidence gathering, validation, and reconciliation.
Read the articleProduction support
A practical guide to T24 database storage growth — the difference between data and transaction-log storage, why growth and reusable space are not the same thing, and what support teams should monitor before capacity becomes a problem.
Read the articleProduction support
A practical, environment-neutral guide to validating a restored T24 service — covering infrastructure, database, application, integration, batch state, business validation, and sign-off evidence.
Read the article