LEARN. PRACTICE. GROW.File-flow stages
A flow may include creation, readiness to send, transfer, receipt, format validation, processing, and reconciliation. Transport status does not prove every subsequent stage. Record transfer identifiers, partner, file, business date, and processing correlation. With Transfer CFT or another tool, use documented states and codes for the installed version; avoid turning an isolated code into a business conclusion.
Integrity, completeness, and identity
A checksum compares bytes under the chosen algorithm; it does not prove the file contains all expected records or matches the correct date. Combine integrity with agreed name/identifier, plausible size, counts, control totals, and structure validation. Partner identity and authorization are separate controls. Keep sensitive files and evidence only in authorized locations.
Resend without duplicating effects
When a sender loses confirmation, the receiver may already have received or applied the file. Check both sides and the business identifier before resending. Agree with the partner how to handle duplicates, partial files, quarantine, and replay. If recovery needs a corrected file, preserve its link to the original and relevant approval to support later reconciliation.
Workplace application
Use a reconciliation record with business identifier, date, origin, destination, expected count, and observed result. Distinguish file receipt from acceptance of each record. If an acknowledgment was lost, request recipient evidence before replaying. Concrete CFT instructions depend on installed version and procedure; this path does not invent universal codes.
Transport reports completed delivery, but the consumer rejected the business date. Restarting transport does not correct content. Recovery should involve the producer and replacement/correction process, with duplicate prevention and renewed validation.
Common pitfalls
Confusing checksum with correct date; replaying with a different identity.
Related topics: Measure impact and confirm recovery · Turn incidents into verifiable improvement
Transferred, received, and processed are different states; reconciliation connects them to business outcomes.
Reference: Data integrity · DR Production Support L3 2026.4; Linux, JDK 25 HotSpot, OpenSSL 3.5 and Kubernetes examples require installed-version checks