#ebcdic — Public Fediverse posts

@loriemerson : Is your keybord #ASCII or #EBCDIC ?

@astrid

If you flip it over, does it have EBCDIC?

#EBCDIC #ASCII #encoding

#ebcdic - Erase Backup Chew Disk Ignite Cards 🤭

Colorized #ASCIIart at #NASA using an #IBM System/370 in 1981.

Or is it called #EBCDIC art?

#ProgrammingHumor time.

New #EBCDIC song.

(To the tune of Mozart, K265).

A, B, C, D, E-F-G-H, I

Other-codes-plus/minus-J-K, L-M-N-O-Pie

R, other-codes, tilde-S-T-U-V

#AIX is dead, Y use System Z?

I almost know my ebsy-dickee-dee.

Now say "To hell with #IBM " with me.

Les demandes de nos clients support nous guident régulièrement dans nos travaux sur #PostgreSQL.
Jehan-Guillaume partage aujourd'hui le résultat des travaux conjoints avec la DGFiP concernant la création d'une collation #EBCDIC => https://dali.bo/202309_ebcdic
#SGBD #opensource #configuration

A fascinating video on the history of the humble @ sign, from 1345 to the present day: https://youtube.com/watch?v=MjE03a8PGko

#ConstantinusManasses #arroba #CommercialAtSign #HermanHollerith #PunchedCards #EBCDIC #ASCII #FORTRAN #RayTomlinson #email

A fascinating video on the history of the humble @ sign, from 1345 to the present day: https://youtube.com/watch?v=MjE03a8PGko

#ConstantinusManasses #arroba #CommercialAtSign #HermanHollerith #PunchedCards #EBCDIC #ASCII #FORTRAN #RayTomlinson #email

A fascinating video on the history of the humble @ sign, from 1345 to the present day: https://youtube.com/watch?v=MjE03a8PGko

#ConstantinusManasses #arroba #CommercialAtSign #HermanHollerith #PunchedCards #EBCDIC #ASCII #FORTRAN #RayTomlinson #email

A fascinating video on the history of the humble @ sign, from 1345 to the present day: https://youtube.com/watch?v=MjE03a8PGko

#ConstantinusManasses #arroba #CommercialAtSign #HermanHollerith #PunchedCards #EBCDIC #ASCII #FORTRAN #RayTomlinson #email

A fascinating video on the history of the humble @ sign, from 1345 to the present day: https://youtube.com/watch?v=MjE03a8PGko

#ConstantinusManasses #arroba #CommercialAtSign #HermanHollerith #PunchedCards #EBCDIC #ASCII #FORTRAN #RayTomlinson #email

TIL, the German #Datev uses #IBM #zOS for paycheck #PDF generation. PDFs are generated through PDFlib by the Munich based company of the same name:

PDF producer: PDFlib+PDI 9.0.4-m (zSeries z/OS)

The API ref is promising some fun:
"For use with C, C++, Cobol, COM, Java, .NET, Objective-C, Perl, PHP, Python, REALbasic/Xojo, RPG, Ruby"
(https://www.pdflib.com/fileadmin/pdflib/pdf/manuals/PDFlib-9.0.4-API-reference.pdf)

As well as:
"PDFlib is available on a variety of platforms, including Unix,
Windows, OS X, and EBCDIC-based systems such as IBM i5/iSeries and zSeries."
(https://www.pdflib.com/fileadmin/pdflib/pdf/manuals/PDFlib-9.0.4-tutorial.pdf)

And since IBM #zSeries does everything in #EBCDIC, this, of course is also supported:

"stringformat ebcdicutf8: All strings and option lists are expected in EBCDIC-UTF-8 format with or without BOM."

And although I do hope that Datev uses Unix System Services #USS instead of plain #MVS on z/OS, this does give me the creeps:

"MVS versions of PDFlib GmbH products are not thread-safe"
(https://www.pdflib.com/fileadmin/pdflib/System_Requirements/PDFlib-9.0.4-system-requirements.txt)

Truly curséd. But PDFlib on zSeries doesn't support networking ... unfortunately?

@debcha

Supposedly, though I don’t know how true it is, the reason why #EBCDIC had such a weird layout for symbols was so that you wouldn’t end up with too many adjacent holes when punching cards in common cases.

Again, no idea if it’s true but it’s nice to think there was *some* method to the madness.

@aka_pugs P.S. 2000 cards * 80 bytes = 160K
Only undergrads used all 80 columns for data. Grad students used 72 for data and reserved the last 8 columns for sequence numbers. If you dropped the box or deck, you could run the cards thru the sorter to retrieve the ordered deck. Thus
2000 * 72 chars = about 140K.
#nerd #nitpicking #EBCDIC

That's neat, but what if you want #SAS code that runs on both #ASCII and #EBCDIC?

Or what if you are like me and want to avoid the <> trap?

SAS also offers the alpha-based EQ and NE operators, which perform "equal to" and "not equal to" comparisons.

I got in the habit of only using the character-based operators in part to avoid the <> trap. However, I'm doing maintenance coding tonight, and in trying to avoid a style clash, I fell into the <> trap again!

Today, I found a bug that I'm responsible for. It's in a validation routine written in #COBOL on an #IBM i. I checked the value of characters by checking if they are < "A" or > "Z". I didn't keep in mind that with #EBCDIC encoding they are arranged differently :mastofacepalm: Thankfully the program hasn't been in use before last week and there haven't been any invalid data accepted yet.