Skills

Ebcdic Overpunch Decoding

Reference for the EBCDIC "overpunch" / zoned-decimal sign convention where the units...

Install

npx skills add benchflow-ai/skillsbench --skill ebcdic-overpunch-decoding -g -a claude-code -y
Category
Engineering
Updated
12d ago
License
Apache-2.0
Context cost
Lightabout 908 tokens
Runs scripts
No, instructions only

What it does

Reference for the EBCDIC "overpunch" / zoned-decimal sign convention where the units position of a numeric field is replaced with a letter that encodes both a digit and a sign. Useful when reading mainframe-style fixed-length tapes whose amount fields appear as digits followed by a letter (e.g. "0000000000123D" or "0000000000045M").

EBCDIC overpunch (zoned decimal sign)

On classic mainframe tapes, signed numeric amounts are stored as N-1 digits followed by a single byte where the high-order bits carry the sign and the low-order bits carry the final decimal digit. When the file is converted to ASCII / printable form, the last byte is rendered as a letter (or a brace).

Sign and digit table

CharSignLast digitCharSignLast digit
{+0}−0
A+1J−1
B+2K−2
C+3L−3
D+4M−4
E+5N−5
F+6O−6
G+7P−7
H+8Q−8
I+9R−9

Positive zero is {; negative zero is }. Both decode to magnitude 0, keep the sign attached so downstream arithmetic doesn't drop a debit's polarity.

A common defect

The positive half of the table ({, A, I) is the visible-looking case and is often handled first. The negative half (}, J, R) looks like ordinary letters and is easy to forget. If only the positive letters are decoded, debits and credits both come through as positive, the totals look plausible but signs are wrong on every negative row.

Decoding pattern (placeholder names)

Split the field into the leading digits and the overpunch byte, look up the sign + units digit from the table above, recombine, then build the signed working-storage value. The shape below uses generic identifiers, substitute your own field names:

Read the whole SKILL.md on GitHub

More in Engineering