General Discussion
Related: Editorials & Other Articles, Issue Forums, Alliance Forums, Region ForumsKnow COBOL? Work available now!
https://www.cnn.com/2020/04/08/business/coronavirus-cobol-programmers-new-jersey-trnd/index.htmlalwaysinasnit
(5,063 posts)sinkingfeeling
(51,444 posts)dalton99a
(81,432 posts)USALiberal
(10,877 posts)Writing iPad apps now.
TheBlackAdder
(28,182 posts)AirmensMom
(14,642 posts)I took COBOL in college decades ago and never used it in my working life. I might still even have the printouts of my college programming assignments. It wasn't hard to learn, though, so I could probably do it again. This is getting unreal.
Ex Lurker
(3,812 posts)About all I remember is that it had four divisions. Ironically, our class assignments had to do with medical records and billing.
madinmaryland
(64,931 posts)XRubicon
(2,212 posts)I had to write/format a flat data file for a COBOL program running in UNIX to read one time so I needed to understand the code (at old job).
FORTRAN and Basic assignments were an easy A for me.
Blue_true
(31,261 posts)It was very frustrating to work with because it would stop at each coding mistake instead of reviewing all the code then typing out syntax errors. So I would spend several frustrating days and nights getting the syntax right, then execute the program, only to find out that I had programmed an attempt to divide by zero or some other nonsense, then I had to correct my equations, which often threw me back to redoing the syntax in the code. I used Basic in my work life, and I liked that much better.
COBOL was a powerful language, but getting it coded properly was a massive headache.
Ms. Toad
(34,059 posts)Good old Xerox Sigma 9.
MurrayDelph
(5,293 posts)Along with PL/I and APL.
When I quit teaching public school, I learned Fortran, got a job in an Aerospace company working in Fortran (in the early 80's), and then found myself transferred to the payroll department, where I had to maintenance programming in COBOL on IBM mainframes.
Which is why I took a job teaching at DEC. While at DEC, I learned BASIC and C, and sat in on a class in ADA (but fortunately was never tasked with learning it well-enough to teach).
I guess what I'm saying is that anyone old-enough to remember how to code COBOL is in the danger group and shouldn't go out in the workforce.
Hoyt
(54,770 posts)lastlib
(23,204 posts)were done on 8-inch floppies! The launch computers are STILL 70's-vintage mainframes! (They're unhackable, because they have no IP addresses--the machines pre-date the internet!) They just updated the transfer medium to solid-state digital devices (thumb drives?)
I guess they either have, or will, update the computers themselves, according to this article. But how will they ever cope with DOS 3.0??
https://www.engadget.com/2019-10-18-us-military-nuclear-missiles-floppy-disks.html
I *hated* COBOL 😱!
We thought of it as obsolete way back in the Middle Ages when I was getting my bachelors degree,
CentralMass
(15,265 posts)Radio Shack Color Computer that had a smokin' 300 baud modem that plugged into a rom cartridge slot on the side of the computer. The college had a Data General Nova, or it might have been an Eclipse that you could remote into. I was probably the only student that that had a computer at home with a modem. I would log in and enter my length Cobol programs and submit them for compilation. It could take 30 - 45 minutes to get them into the compiler queue and compiled. If I forgot a critical . (period) the compiler would generate 50 or 60 errors. I would have to find it and fix the errors and resubmit, etc.
Those were the days! We called em Radio Sucks, they were just coming on the scene right after I finished my BA.
I wont even describe the rig I used for remote access my last semester to complete a major assignment while sick as a dog. Truly prehistoric!
ret5hd
(20,489 posts)Syndrome medical coverage. Absolutely the most tedious language to program. Easy to read, painful to write.
Leith
(7,808 posts)People wouldn't believe how many installations run on COBOL, mainly government and large corporations. However, unless you live in a state capital or a city where an old and gigantic corporation is headquartered, you aren't going to get a job programming on a mainframe.
But, maybe, if they are desperate enough to let me work from home and they're willing to be patient through my remembering curve, I'd give it a shot. I still have my 30 year old TSO/ISPF (IBM mainframe operating system) and DB2 SQL (mainframe database system) books.
Ms. Toad
(34,059 posts)If it ain't broke, don't fix it.
CentralMass
(15,265 posts)Skittles
(153,138 posts)it's death has been projected for DECADES
raccoon
(31,107 posts)Guess I could program it again.
USALiberal
(10,877 posts)lapfog_1
(29,199 posts)a very long time ago.
Hekate
(90,627 posts)Ziggysmom
(3,406 posts)Have not coded COBOL in 20 years, I moved on to EDI. The USS Hopper Navy Warship was named for Ms. Hopper. She was quite a woman!
tinrobot
(10,893 posts)Coding in COBOL is like writing a damn novel. Too verbose.
Leith
(7,808 posts)COBOL taught me how to type. I just couldn't get the hang of where my fingers needed to go until I was forced to by typing
Now it's
I always figured that COBOL was so verbose so that the boss could figure out what was going on.
The_jackalope
(1,660 posts)I'm a total assembly language geek - PDP-10, PDP-11, 6809, 68000 and a smattering of RCA 1802. The highest level language I ever liked was plain C. As far as I was concerned, C++ was a joke perpetrated on an unsuspecting coding community.
So guess how much I hated COBOL?
But the gods had their little laugh at my expense. My first computer summer job after second year in 1980 required me to port a General Ledger package from COBOL-68 to COBOL-74, using home-made TECO macros.
Jesus.
Ms. Toad
(34,059 posts)Back to the future!!!
Fortran, Pascal, Basic, anyone? Got those skills, too!
USALiberal
(10,877 posts)Fortran as a sophomore in High School
COBOL as a Junior
RPG as a Senior
Punch cards!
Then C, Visual Basic, C64 Basic, etc!
Ms. Toad
(34,059 posts)I dreaded walking across campus with my punch cards - hoping not to trip and send them all over the place so I would have to re-sort them before submitting them for the one run a day I was permitted.
I taught BASIC (on C64s) from 1978 - 1989 (the first few years with a single live terminal and 2-3 punch tape terminals)
USALiberal
(10,877 posts)Ms. Toad
(34,059 posts)I started teaching BASIC with two (maybe 3) dumb terminals and one with a tape reader and modem for ~40 students to run programs on. So I was pretending to be a computer a lot of the time in order to be able to grade their work.
I convinced them to upgrade to C64s, so we had about one for every other student. Much better!
But i automated my gradebook, randomized question order and answer option order in multiple choice quizzes, created identical concept but different detailed assignments (Write a program that request 5 users to ask for each of the 7 wonders of the world; Write a program that asks 7 people the names of the origina colonies. In order to cheat by borrowing someone else's coding, they had to understand what they were doing. I also wrote a program to create word search puzzles that hid a list of words vertically , horizontally, and diagonally (foward and backward), and created an answer key that got a lot of use by my peers when they needed to create (I mostly wrote the last when my boss told me she didn't think I could).
I miss coding - but I haven't had a chance to do any since a HarvardX couse I took a few years ago when I needed to learn enough C++ to make sure my engineers weren't lying to me to avoid me telling them they were infringing someone else's patent. They were. The look on their faces was priceless when they realized their lawyer could, and had, read their code.
USALiberal
(10,877 posts)Mainframes to iPhones. I do miss the old bits and bytes days. Harder but seemed more knowledge needed.
Ms. Toad
(34,059 posts)Or of the constant need to create a new version of something that works quite well, just for the sake of making it look different.
They pried my DOS from my fingers by killing the DOS-based programs I needed to do legal research when I was in law school.
I'm currently battling Teams - which seems to me to add very little beyond creating one more place I need to go to check for mission critical correspondence