SShortSingh.
Back to feed

Why COBOL's COMP-3 packed decimal format still breaks Pix and ISO 20022 integrations

0
·23 views

Brazilian banks, acquirers and fintechs often run instant Pix payments and ISO 20022 messaging alongside core ledgers still built on COBOL mainframes. The article identifies the binary translation layer, especially the COMP-3 packed decimal format, as a frequent but overlooked source of integration failures. In COMP-3, each byte holds two decimal digits and the final nibble encodes the sign, so values like +12345.67 occupy four bytes. Converting through floating-point arithmetic can corrupt cents during end-of-day reconciliation, so the author recommends fixed-precision types such as BigDecimal or integer cent values. The piece also warns that misreading implied decimal points or sign nibbles can produce misplaced or inverted entries that only surface during accounting reconciliation.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Saga Pattern Explained: Orchestration Versus Choreography for Distributed Transactions

When an order spans separate services with their own databases, no single transaction can cover inventory, payment, and shipping, and cross-service two-phase commit is rarely practical. The saga pattern addresses this by running a sequence of local transactions, with compensating actions that semantically reverse earlier steps if a later one fails. Steps are classified as compensable, pivot, or retryable, and ordering them correctly determines whether the system can reach a consistent state. Sagas can be coordinated centrally by an orchestrator, which keeps the flow in one place and simplifies tracing, or through choreography, where services react to each other's events and suit simpler flows. The article also notes that sagas introduce eventual consistency and do not solve isolation problems on their own.

0
ProgrammingDEV Community ·

Developer builds local-first Windows memory tool in Rust and tests its privacy claims

A developer created Synapse Mind, a local-first memory app for Windows that records recent activity to help users recover lost context. Unlike similar tools, it avoids periodic screenshots and never sends data off the device. Sensitive content such as secrets and personal data is masked before it reaches storage, and password managers and sensitive file windows are excluded entirely. The project is a Rust workspace with a Tauri interface, using encrypted SQLite and Windows DPAPI for key protection. The developer also describes moving UI Automation reads into a short-lived helper process so that text lingering in memory is reclaimed by the operating system, and tests the claims by dumping the app's memory and searching it for planted secrets.

0
ProgrammingDEV Community ·

pass^k, not pass@k: Measuring whether AI agents succeed reliably every time

A DEV Community author argues that the common pass@k metric, which counts success if at least one of k attempts works, hides unreliability in AI agents. The alternative pass^k requires all k attempts to succeed, giving a truer picture of trustworthiness. The piece notes that per-step failures compound across long tool-call sequences, so a 99% per-call success rate can still yield only about 60% task success over 50 calls. The author recommends reporting pass^k alongside pass@k, evaluating full trajectories rather than final answers, and using a deterministic verifier instead of another model to check results. The author also discloses that they run an AI-ops store and write about agent verification.

0
ProgrammingDEV Community ·

Five Lessons from Packaging Self-Hosted PHP Software for Customer Installs

A developer shares practical lessons learned while preparing self-hosted PHP applications for commercial distribution. Apps that ran correctly at a domain root often broke when installed in a subfolder because of hardcoded URLs and redirects. Empty directories such as storage folders were frequently lost in ZIP packages, so placeholder files and writability checks were recommended. The author also explains the difference between license activation and periodic verification for self-hosted installs. The article stresses testing the extracted ZIP package rather than only the development directory.