Two things to remember:
1. The map is not the territory. Just because somebody uses the word
efficiency doesn't mean that they concerned with efficiency.
2. The application of a language is not the language. Just because
somebody encodes unknown as 150 when writing in COBOL doesn't
mean that 150 (as opposed to, e.g., 77, 88) is intrinsic to COBOL,
nor does it mean that converting to Java will magically cause that
encoding to magically go away.
To me, modernizing the COBOL code means using the language features that have
been added over the decades.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Discussion List on behalf of Mark Regan
Sent: Friday, April 4, 2025 12:52 PM
To: [email protected]
Subject: Fwd: DOGE wants to modernize Social Security’s legacy tech — what
could possibly go wrong? – Computerworld
External Message: Use Caution
This might wrap for some of you.
https://www.computerworld.com/article/3953741/doge-wants-to-modernize-social-securitys-legacy-tech-what-could-possibly-go-wrong.html
Regards,
Mark Regan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
