Slashdot Mirror


Texas Company's Antique Computers Are For Production, Not Display

concealment writes "Sparkler Filters up north in Conroe [Texas] still uses an IBM 402 in conjunction with a Model 129 key punch – with the punch cards and all – to do company accounting work and inventory. The company makes industrial filters for chemical plants and grease traps. Lutricia Wood is the head accountant at Sparkler and the data processing manager. She went to business school over 40 years ago in Houston, and started at Sparkler in 1973. Back then punch cards were still somewhat state of the art." See kottke.org for an eye-popping view of one of the "programs" — imagine debugging that.

289 comments

  1. Debugging that... by icebike · · Score: 5, Insightful

    "THAT", (a wired board), is vastly easier to debug than any modern software. In fact a trainee can usually debug it by trial an error in just a few minutes.
    Now get off my digital lawn whipersnapper!

    --
    Sig Battery depleted. Reverting to safe mode.
    1. Re:Debugging that... by Anonymous Coward · · Score: 0

      Yeah, you just need to get past the wiring shock first. That said, if I tried to turn in something with this kind of wiring for one of my engineering classes, I think I'd have at least one letter grade knocked off.

    2. Re:Debugging that... by Anonymous Coward · · Score: 4, Funny

      It's not old, it's hacker resistant :D

    3. Re:Debugging that... by Dancindan84 · · Score: 4, Funny

      Not if you're hacking with a box cutter.

      --
      "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    4. Re:Debugging that... by Anonymous Coward · · Score: 0, Flamebait

      Not with that kind of wiring. This reminds me of the lab we had in school to build a simple digital circuit with several TTL old style "caterpillar" ICs. A big factor between spending 1:15 like myself and 4:00 hours was having neat wiring. The champ was 45 minutes, which must have been neat wiring, fast hands, and the luck to have everything stick properly in the breadboard the first time. The 4 hour group was (sorry to say this, but it's a fact) Black girls. Big loopy wires over the boards, and every time they tried to fix one connection, they broke another. Painful to watch.

    5. Re:Debugging that... by greyparrot · · Score: 3, Informative

      I never actually programmed one, but when I worked at Siemens in Iselin, NJ we had some of these. For physical inventory, we needed it to print the name of the spare part on the card my program punched out of the Spectra 70. So a bunch of old guys from all over the company found themselves poking around on the board. And they were successful too. The inventory cards were beautiful! To take inventory, the warehouse people wrote the count on the card, we had it punched at the end, and fed back into the Spectra. (We ran COBOL on that, 64 K of memory allowed even the SORT to run.) Good old days!

    6. Re:Debugging that... by Joce640k · · Score: 0, Offtopic

      The 4 hour group was (sorry to say this, but it's a fact) Black girls. Big loopy wires over the boards, and every time they tried to fix one connection, they broke another. Painful to watch.

      Did they bend the jumper wires into little heart shapes?

      --
      No sig today...
    7. Re:Debugging that... by Peter+Simpson · · Score: 1

      Easy to debug when all you can do is add, subtract, count and print! Much more challenging if you have a reproducing punch hooked up to generate the YTD summary cards... Been there, done that and glad to have C.

    8. Re:Debugging that... by Anonymous Coward · · Score: 1, Insightful

      Did they bend the jumper wires into little heart shapes?

      Just about. Original AC here. Now, I'm not a racist at all; but here's what I think was going on (and there are statistics somewhere to back this up). The University of Virginia is where this happened. The University was doing its best to right past wrongs by admitting X% Blacks, or something like that. I don't know if it was actually a quota system; but the SAT scores of Blacks admitted were always lower than the general population.

      Once again, to reiterate, I'm not a racist. IMHO, it was hard to find Blacks with scores comparable to the average admission because there is a lingering legacy of segregation and a culture that doesn't encourage literacy. Poverty, etc.; all of that. It doesn't mean Blacks are inferior. It just means that it takes a few generations for a culture that was smacked down to rise back up.

      So. A lot of less qualified Blacks were admitted, and being a woman and Black in the E-school? That must have been some kind of diversity bonus prize.

      So then the big deal on grounds (not "campus", but that's another rant) is that Blacks were getting tossed out on honor violations more often than Caucasians. Well duh. When you place the burden of "first generation to attend college" on an applicant with SAT scores and grades that really aren't that great, and they start failing... the pressure is enough to make a lot of them cheat.

      It's nothing to do with race. It's everything to do with putting a bunch of young people under some strange and terrible pressure in order to carry out what you perceive as "justice".

      End rant.

    9. Re:Debugging that... by Two99Point80 · · Score: 1

      Guess what: those jumper wires can break internally but still look okay on the outside. I found *that* out on a 402 I was taught how to program in the late 1960s. Took a while to find the bug...

    10. Re:Debugging that... by Politburo · · Score: 1, Insightful

      Why would you even bring in race when it has nothing to do with the discussion? Somehow I doubt you were "sorry to say" it, especially given the rant below.

    11. Re:Debugging that... by greyparrot · · Score: 5, Interesting

      I was the only girl in my high school physics class. At some point we had to make 1-tube radios (6J5). This was a way long time ago! Anyway, I was very nervous about cutting my wires too short so I had quite a bit of wire on there. I had an extra "tickler" coil which was patched with nail polish where I had to splice two wires together. The tuning knob was stuck through a piece of a refrigerator dish.
      The day of the trial came. The teacher came in with a big battery and a pair of earphones. First they tested all the techie boys. They had nicely arranged boards. Many of them had actually done some electronics work at home. Some of their kit worked; some didn't. There were only about 7 of them. They drifted out of the room.
      The teacher hooked me up -- and mine actually worked! A surprise to all of us. I had never soldered anything before, and had biked around town assembling the collection of parts that I had looked up in a book somewhere.
      The point of this is that those of us with no engineering background whatever can be relied on to do something weird when first confronted with it. Not that those young women were really qualified; that is another issue. But big loops of wire? I can relate to that!

    12. Re:Debugging that... by rnturn · · Score: 1

      My dad used to "write" programs for those computers. He took me to work one day and I was amazed that the tangle of wires was somehow useful. For a long time I had one of the two-pronged plugs/jumpers that were used on those boards. (Lost in the sands of time now.)

      --
      CUR ALLOC 20195.....5804M
    13. Re:Debugging that... by rwa2 · · Score: 1

      Awesome... I better head over to the http://www.livingcomputermuseum.org/ this weekend and brush up on my skills

    14. Re:Debugging that... by Anonymous Coward · · Score: 0

      At least it wasn't an actual bug. Arthropods are the worst, man.

    15. Re:Debugging that... by K.+S.+Kyosuke · · Score: 2

      Why would you even bring in race when it has nothing to do with the discussion? Somehow I doubt you were "sorry to say" it, especially given the rant below.

      He apparently had to say something, didn't he? If he said just "they were girls", you'd pull the sexism card instead. Was he supposed to say "the worst contender was a person"? That would have been a tautology. Most likely he didn't know the majority of those people personally (my experience from college as well), and when you observe someone unfamiliar doing something and you want to say something about them specifically, there is but a small number of immediately observable traits you notice even from distance - sex, approximate age, rough ethnic background, and dialect (if your language happens to have some distinctive ones) come to my mind.

      --
      Ezekiel 23:20
    16. Re:Debugging that... by Charliemopps · · Score: 1

      Having attended school in the south, I can explain exactly why there may have been some sort of educational gap. My family moved there from the north when I was in grade school and when I got to school, every single kid there was black (except me of course) I was kind of perplexed by this, especially when all of these kids started using racial slurs to refer to me and I started getting beaten on a daily basis.

      So... I went home and asked my parents what the deal was. Was everyone that lived in this town black? "No" they said... they explained that it was illegal to segregate people based on race, that they used to do it but it was wrong. In this town however, old habits died hard. So they built a "private" school that was funded by those with money in town and whos rates were relatively low. The difference between it and the public school? The admissions process... If you were white you got in, if you were not, you went to public school. My parents found this appalling so I went to public school.

      And, in case you were wondering, the public school was terrible. My science teacher told us we'd eventually lose our pinky toe because we don't use it for much. No lie.

    17. Re:Debugging that... by bondsbw · · Score: 1

      Yes, but can it display a screen of dynamic data from a distributed data store to hundreds of users thousands of miles away, using fewer characters than this post?

      Get off my Twitter feed, old timer.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    18. Re:Debugging that... by amiga3D · · Score: 1

      We have those kind of schools still. Blacks are welcome though, if they have the money to pay the tuition which is not really all that affordable. They do offer scholarship to black athletes though. Funny to notice a 95 percent white populated school with a 90 percent black football team.

    19. Re:Debugging that... by X0563511 · · Score: 3, Insightful

      No, it doesn't. Leaving that meme tied up in the basement would be doing everyone a favor.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    20. Re:Debugging that... by Alioth · · Score: 1

      My Sinclair ZX Spectrum (a personal computer from 1982) can do this (or rather could: now twitter insist on SSL it's a bit beyond an 8 bit Z80 CPU). I built an ethernet board for it. Displayed it at the 2010 Vintage Computing Festival at Bletchley Park, and many people tweeted from it.

    21. Re:Debugging that... by greyparrot · · Score: 1

      Right! Remember, dudes, we females are watching you...

    22. Re:Debugging that... by Mike+Buddha · · Score: 2

      You know, it might just be that those people that took 4 hours just aren't good at running wires. It might not have had anything to do at all with the fact that they were black or women.

      The fact that you assert that there is a causal link with no evidence pretty much defines you as a racist misogynist. Did you have access to those particular students SAT scores? Have you assessed their high school transcripts? Did you compare their performance with any other students performance, other than your own? Sounds like a flawed observation to me.

      --
      by Mike Buddha -- Someday the mountain might get him, but the law never will.
    23. Re:Debugging that... by fleebait · · Score: 1

      "THAT", (a wired board), is vastly easier to debug than any modern software. In fact a trainee can usually debug it by trial an error in just a few minutes.
      Now get off my digital lawn whipersnapper!

      Except when you get 2 bad plugs, or jacks, or a backside solder joint cracks.

      Can take an hour or two to fix it.

      I seem to remember it taking about 45 minutes for someone else to go over the programming sheet, and check the plugs (including coffee).

    24. Re:Debugging that... by Anonymous Coward · · Score: 0

      I think SSL could be done even on a Z80. As long as you have enough memory, it shouldn't be a problem. Remember: TCP/IP is inherently flow-controlled. You only need to process it as fast as you can.

    25. Re:Debugging that... by Anonymous Coward · · Score: 1

      Not if you're hacking with a box cutter.

      Or a hacksaw

      Isn't that why they're named as such?

    26. Re:Debugging that... by narcc · · Score: 1

      The fact that you assert that there is a causal link with no evidence pretty much defines you as a racist misogynist

      Sadly, those sort of attitudes are disturbingly common in the so-called skeptical community.

    27. Re:Debugging that... by omnichad · · Score: 1

      You can still do this with a dial-in SMS gateway, I think. Since 40404 is still an active shortcode for Twitter.

    28. Re:Debugging that... by serviscope_minor · · Score: 1

      At some point we had to make 1-tube radios (6J5).

      Before my time.

      coil which was patched with nail polish where I had to splice two wires together.

      It's a surprisingly handy quick drying removable glue. It's quite popular for guling down/sealing microscope coverslips too. I usually have a few pots handy for labelling plugs/sockets on embedded boards since they have a tendency to look otherwise indistinguishable.

      But big loops of wire? I can relate to that!

      My wire wrap work was never the cleanest... :)

      --
      SJW n. One who posts facts.
    29. Re:Debugging that... by Anonymous Coward · · Score: 0

      The "sexism card", huh.

      Ooh! Ooh! Share with us exactly why your have Ezekiel 23:20 in your sig! Inquiring minds want to know!

    30. Re:Debugging that... by Anonymous Coward · · Score: 0

      He apparently had to say something, didn't he?

      Yes, by giving a description of just the work itself and possible factors leading to that quality of work. Other groups had "neat wiring and fast hands", he could have just said "the 4 hour group took so long due to shit wiring"

    31. Re:Debugging that... by Anarchduke · · Score: 1

      in the basement... where all the slashdotters live?

      --
      who prays for Satan? Who in 18 centuries has had the humanity to pray for the 1 sinner that needed it most? ~Mark Twain
    32. Re:Debugging that... by kaliann · · Score: 1

      The de facto segregation via private schools still happens in Louisiana, and likely other southern states. Tuition has gone up and actively racist criteria have been diminished, so there are usually a few non-white kids... primarily from successful families that have moved to town rather than local families. Poor people of all colors are excluded, and African Americans in Louisiana are disproportionately impoverished, so it ends up being nearly as "effective" as the original system, but now churches profit (most of the private schools in LA are Catholic or some other Christian denomination).

    33. Re:Debugging that... by Gr33nJ3ll0 · · Score: 1

      I've heard the pinky toe comment before. Not sure how your teacher was using it, but the idea is that the human race will evolve out of having it, mainly due to wearing shoes all the time.

    34. Re:Debugging that... by mattack2 · · Score: 1

      The point of this is that those of us with no engineering background whatever can be relied on to do something weird when first confronted with it.

      There's an episode of "Independent Lens" about women soldering parts for solar panels..

      http://www.pbs.org/independentlens/solar-mamas/

      Rafea has never left her tiny village of tents in Jordan. Now she is traveling to India to become a solar-energy engineer, in hopes she can return and help her village to become sustainable and self-sufficient.

    35. Re:Debugging that... by idunham · · Score: 3, Funny

      Hey, it's the original spaghetti code!

    36. Re:Debugging that... by zedrdave · · Score: 2

      It just means that it takes a few generations for a culture that was smacked down to rise back up

      Pro tip: if you have to assure your readership that you are not racist, not once, not twice, but three times in the course of your post, that's generally not a good sign.

    37. Re:Debugging that... by idunham · · Score: 1

      You do know that the Z80 has 16-bit memory access and is thus limited to 64 kilobyte banks, and more than 4 banks (with the right extenders and drivers!) is unheard-of?
      PolarSSL would just fit in 2 banks, though someone might prune it down to work better.

    38. Re:Debugging that... by kermidge · · Score: 1

      A tube? That's modern. My first radio used a germanium crystal, came as a kit, circa 1957.

      But building a single-tube radio from scrounged material? For class? Yowsah!

      I tip my hat to you, greyparrot; may you live long and prosper.

    39. Re:Debugging that... by fluffy99 · · Score: 1

      The University of MD did the same "equality" thing when I was attending. The State felt black admissions were too low, so they forced the University to try to remedy this by lowering the SAT and GPA cutoffs and establishing grants based on skin color rather than college potential. Unfortunately by actively trying to attract people who otherwise did not meet the same criteria (regardless of the group) they set up the situation that a few years later that group also had the highest dropout/failure rate. So next they pressured the professors to ensure they were teaching equally which translated into more lenient grading.

    40. Re:Debugging that... by dbIII · · Score: 1

      We've got a lot of people that don't bother to parse comments fully here before they comment, and whether it's lack of sleep, drinking or whatever there's some short attention spans here too. I can see why the point is stressed several times, so yes it's not really a good sign about the readership, but most of it can be put down to casually not paying much attention instead of malice.

    41. Re:Debugging that... by Anonymous Coward · · Score: 0

      The AC that wrote it responds (and posters like you are why it's AC)

      The fact that you assert that there is a causal link with no evidence pretty much defines you as a racist misogynist

      No it doesn't. Because if I hadn't reasserted that, you would have concluded that anyway. Damned if you do, damned if you don't.

      Did you have access to those particular students SAT scores?

      No, but SAT scores by race at that school were a statistic that was widely published at the time, and perhaps they still are.

      Now of course it's possible that these women had stellar SAT scores. It's just not statistically likely.

      FWIW, I like to think that at least one of them had the brains and passion underneath all the problems that were holding back, and is presently kicking butt someplace as an engineer. What say you to my racist misogyny now?

    42. Re:Debugging that... by Anonymous Coward · · Score: 0

      he could have just said "the 4 hour group took so long due to shit wiring"

      AC in question here. Yes, I suppose I could have said that and maybe I should have. OTOH, the image is like a scene from a movie in my mind. I got stuck in the trap of relating the events in too much detail, then apologizing for that detail, then going off on my whole opinion on the affirmitive action controversy. In retrospect, simply mentioning the crappy wiring might have been the better course of action, and I could have posted with my userid...

    43. Re:Debugging that... by Cederic · · Score: 1

      So the people that took 4 hours possibly had low SAT scores. That would help explain why they took 4 hours.

      It's still got fuck all to do with their gender or race.

    44. Re:Debugging that... by Anonymous Coward · · Score: 0

      Or an axe?

      Ok, is the captcha context sensitive? It just came up as scythes...

    45. Re:Debugging that... by Joce640k · · Score: 1

      People who can wear narrower shoes will get to breed more often?

      --
      No sig today...
    46. Re:Debugging that... by julesh · · Score: 1

      You do know that the Z80 has 16-bit memory access and is thus limited to 64 kilobyte banks, and more than 4 banks (with the right extenders and drivers!) is unheard-of?

      I do recall reading about a company that was offering a memory extender for the spectrum that would accept up to 4MB (i.e. 64 full address space banks - I think they were actually using 256 x 16K banks for software convenience). Don't know how many they sold, though...

    47. Re:Debugging that... by Anonymous Coward · · Score: 0

      "racist" AC here. That's because the Democratic Party is still the Dixiecrat party. They just changed tactics. Since Blacks were poorly educated due to Jim Crow, they were able to sell them on the idea of handouts.

      Now Blacks continue to be under-educated by the teacher's union and Democratic Party dominated districts in the cities all over the country. These poor kids then get into college on the affirmitive action program. Instead of improving the quality of the graduates coming off the K-12 conveyor, it's easier to accept inferior graduates and as an added bonus they get to pat themselves on the back.

      I blame the GOP of the 60s for foolishly adopting their "Southern Strategy" and allowing this reversal of political alliances to take place. Were it not for that, we might have a Black culture that wasn't so solidly hoodwinked into voting for the very people that keep them down by telling them they need what the Dixiecrats have to offer.

      Once again, I'm the racist??? Who imposes policies that sort people based on race? Not me.

    48. Re:Debugging that... by SeattleGameboy · · Score: 1

      At least he didn't trot out "I have a black friend!!!"

    49. Re:Debugging that... by KingBenny · · Score: 1

      lol, yea that's why i keep a cellphone that doesn't run anything but sms and an alarm clock and has no gps unless the federales get a triangular warrant. Never had any malware on it. If that stuff works for those people and it's still efficient then why upgrade to windows 8 ?

      --
      Free speech was meant to be free for all... how can anyone grow up in a nanny state ?
  2. If it ain't broke... by dontbemad · · Score: 1

    don't fix it.

    1. Re:If it ain't broke... by 0racle · · Score: 5, Insightful

      The problem with that can end up being "when it is broke, how are you going to fix it?"

      --
      "I use a Mac because I'm just better than you are."
    2. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      And I thought doing accounting on an IBM P3 (1.0ghz!) was 'old school'!!! :)

    3. Re:If it ain't broke... by gstoddart · · Score: 4, Insightful

      The problem with that can end up being "when it is broke, how are you going to fix it?"

      I mostly agree with you, but I've also been on a couple of projects trying to replace 30+ year old custom-built mainframe applications.

      I've seen a couple where people try to replace it with more modern software, but nothing which isn't built from scratch can even come close. It usually lacks 30-40 years of tweaks and fixes to do everything they need, often completely changes the workflow, and opens up vast amounts of data transformation you need to do to pull in all of the legacy data into the new system.

      I've seen several of these projects fail after a significant amount of time and money was sunk into it as people realized it wasn't possible to build something which did all of the same things.

      Sometimes, no matter how hard you try, it can be an exceedingly expensive thing to replace old systems like that. So much so that it isn't feasible for companies to really undertake it.

      However, that just pushes out the problem, and sooner or later, you end up with a defunct system and no replacement.

      --
      Lost at C:>. Found at C.
    4. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      don't fix it.

      From the article: "Wood says the cards are slowly being phased out in favor of PCs, but she wasn't sure when."

    5. Re:If it ain't broke... by TWX · · Score: 1

      don't fix it.

      There's a point when the sheer number of paradigm shifts has made the implemented way silly. The power requirements alone should indicate that. I think that the IC in my computer keyboard is powerful enough to handle all of their tasks.

      If you ever watch the Terry Gilliam film Brazil, pay attention to the tech. They took a basic tech and never expanded on it to improve it properly. Instead one had three inch screens with Fresnel lenses to make the image bigger, typewriters with electrical switches for keyboards, and such.

      --
      Do not look into laser with remaining eye.
    6. Re:If it ain't broke... by phantomfive · · Score: 1

      I read somewhere that IBM actually has a program to read in the old punch cards and emulate the system on something more modern. I couldn't find it it with a quick google search, but apparently IBM has a migration plan.

      --
      "First they came for the slanderers and i said nothing."
    7. Re:If it ain't broke... by gstoddart · · Score: 2

      That's great if you have something they have a plan which it covers.

      But I once worked at a place where the mainframe guy had retired, was drawing his pension, and had been hired back as a consultant at 3-4x his previous salary because there wasn't anybody on the planet who could run the old system. Literally, since he'd been the one who maintained it for several decades.

      Not all legacy systems are something you can easily move away from, much to the chagrin of the people who own them. I've literally seen systems with 40+ years of history, huge amounts of data, and more than one attempt to replace it costing millions of dollars and then getting scrapped.

      Sadly, it's not all that uncommon to realize just how massive of a task it will be to replace these things.

      I suspect anybody running museum pieces in production environments have already looked into replacing them, and failed miserably.

      --
      Lost at C:>. Found at C.
    8. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      If it's stuck just force it. If it breaks it needed to be replaced anyways...

    9. Re:If it ain't broke... by Darinbob · · Score: 1

      This thing isn't a mainframe really. It's much more like your tabulating adding machines with the printer roll on the back. "Programming" is essentially just figuring out what calculation to do. I think that advantage that this system has is that you enter the numbers once onto cards and then you can run them through with different calculations instead of typing the numbers in a second time like you would on a calculator.

    10. Re:If it ain't broke... by greyparrot · · Score: 4, Informative

      Yes, the hard part is finding out what the old system actually did, and how much of it was necessary and/or correct. Every miserable data transformation, data structure, business rule, magic number, compiler kludge, and dead end has to be discovered. It is not just a matter of translating the COBOL source either, supposing it is available. The job control and run books have to be examined, and every damn tape or tape emulation has to be dumped.

      Nothing good happens without analysis and specifications up front.

      Frequently the consulting company analysts are more interested in the user interface, where very little happens! But that is the sexy part, of course.

    11. Re:If it ain't broke... by MickyTheIdiot · · Score: 1

      Wood herself is going to be phased out... it's called death.

      That's another major problem here. The system they have might work, but when there is only a couple of people in the whole country that can use it then the company could have a major problem on their hands at literally ANY moment.

    12. Re:If it ain't broke... by Demonantis · · Score: 1

      I realize no one rtfa, but its not a mainframe. Its a freaking adding machine. There is no data migration. This is probably a couple hours tops of spreadsheet work. The best thing from them to do is implement the spreadsheet and compare. It would save a bunch in testing. That way when the sucker does have a aneurism they can just switch over with confidence and no need to perform testing or experience downtime.

    13. Re:If it ain't broke... by egcagrac0 · · Score: 1

      I've seen several of these projects fail after a significant amount of time and money was sunk into it as people realized it wasn't possible to build something which did all of the same things.

      It is possible to build something that does "all of the same things" - if it wasn't, the original system wouldn't exist.

      It may be more expensive and time-consuming than the project budget would allow for, but it's not impossible.

    14. Re:If it ain't broke... by gstoddart · · Score: 4, Insightful

      Nothing good happens without analysis and specifications up front.

      And, with legacy systems, the problem is you can do a huge amount of analysis and specifications -- and still end up having no idea how the system works for all of those corner cases nobody ever mentioned and which can't be shoe horned into what you've now got.

      On one of the projects I was on, at the beginning we did the analysis, and asked them a bunch of questions on how it worked and what the constraints were. We got told thinks like "This can never happen, this is always true, this is always structured like that".

      So you build a system which takes the concrete assumptions they've given you, and then get farther into the process when it suddenly becomes "well, sometimes they can look like this but not always, sometimes that isn't true either, and in a few cases it's entirely different from everything else".

      Then you can quickly discover what you've spent a year building can't possibly work, because in some cases, 1+1 really does equal sqrt(67.89), and you can't make that fit anything you've built since there wasn't supposed to be any real numbers (or whatever metaphor works for you).

      Frequently the consulting company analysts are more interested in the user interface, where very little happens! But that is the sexy part, of course.

      Often because what the company wants is to start with is screen mock-ups because they're focused on the new UI, and it's not until you get deep into the ugly bits that you realize half of what they told you about the actual process is blatantly wrong.

      Sadly, the complexity of system that old can be beyond anything that can be conveyed, or even fully known by the people who own it. And the more specialized the software domain, the more you're likely to find all sorts of things like that.

      --
      Lost at C:>. Found at C.
    15. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      It is 100% possible to reproduce the system. We, as a society, have the coding skill. All that needs to happen is a way for these things to be accurately relayed to the programmers. The last company I worked at had a pretty old accounting system and wanted to upgrade, but couldn't find what they were really looking for. Turns out they just wouldn't explain exactly what it was they were looking for. Ended up being real easy to do once it was in words. It was basically like, system scans invoices as they come in, someone brings up the invoices and tells the computer to pay them, the system forwards the data to a payment processing service that mails out checks and does the payment bullshit. There were several fields that needed to be searchable, it had to keep track of all revisions to a file, and you had to be able to comment on each file. That's it. Easy peasy.

      But to them, it was the most complex system in the fucking world. What they needed was someone that understood their system enough to relay to a programmer what they were looking for. It's eventually what they found, but it took them a while. I think any system is going to be the same way..

    16. Re:If it ain't broke... by lgw · · Score: 1

      I used to do some of that work. The best part is when source and object don't match! Also fun is maintaining the compiled output from some programming language no one has ever heard of (let alone has the compiler for). Ultimately, of course, you can understand and maintain object code with enough time and patience, but it's about the most expensive coding around per fix done.

      And JCL/JECL? Paging Mr Hyde!

      --
      Socialism: a lie told by totalitarians and believed by fools.
    17. Re:If it ain't broke... by greyparrot · · Score: 3, Informative

      Yes, users always lie. It's not their fault. I used to find little scraps of paper up on walls (if I was lucky), with some corner case that everybody knew about, or nobody knew about but the one user. Of course by now these users have long since departed the planet, so lots of luck... You captured it very well!

    18. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      This can be a very short horizon. I was on a contract engagement as one of 2 cost analysts. The other guy had written a database app to roll up actual costs (long story short, the old business systems were failing, and the new ERP system was rushed and not working; we were the plug).

      He goes out sick and the need to carry on with his system lands on my lap. I trace out the tables and the SQL and the dumps from the ERP system (it works, kinda. For some things.) I figure it out and roll the next month's activity, get all the way to the end and realize he's got a magic number in the output that I have no idea what it is, where it comes from, anything. He's out 2 weeks and under sedation, so I can't ask him. Fail. In 2 weeks.

    19. Re:If it ain't broke... by gstoddart · · Score: 1

      OK, let's go with "not possible in the allotted time and available resources".

      Yes, if someone built the system once, in theory someone can do it again. Provided you can find out *all* of the stuff it currently does -- and that's amazingly difficult with legacy systems since there's usually tons of stuff which isn't documented, or only a few people ever use and know about. Lots of stuff gets incrementally added over the span of decades, and there's seldom a definitive thing which describes it all. And often not anything which even describes most of it.

      But those zeroes can keep stacking up to the point where it isn't possible for practical reasons, because it costs too damned much.

      --
      Lost at C:>. Found at C.
    20. Re:If it ain't broke... by X0563511 · · Score: 1

      Business Continuity would have a shitfit over that. What would happen if he got hit by a bus?

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    21. Re:If it ain't broke... by PraiseBob · · Score: 1

      Looks like about 30 lines of code can replace the whole thing.

    22. Re:If it ain't broke... by Mashiki · · Score: 1

      The problem with that can end up being "when it is broke, how are you going to fix it?"

      If I can still buy newly manufactured tubes for a radio made in 1910, you shouldn't have much of a problem fixing that. It may be a niche market in terms of repair, but someone will either make the parts, or be willing to make the parts.

      --
      Om, nomnomnom...
    23. Re:If it ain't broke... by gstoddart · · Score: 2

      Yes, users always lie. It's not their fault.

      It's not even always a lie, which is the most frustrating part of replacing legacy applications.

      People often simply don't know, or don't have a complete picture of all of the dark and scary corners that are in there, or don't realize that things even are dark and scary corners. Several decades worth of tweaks and adjustments makes for an almost intractable problem in some cases.

      Since those projects, every time I've been near anything which says "we're going to replace this legacy application", I try to back away slowly and not get involved in it.

      It will probably hurt, it will likely cost a lot more than you expected, and there's a huge chance you'll go through the whole process for a long time and still have the project fall apart as you discover new things that can't be reconciled.

      I was on one project, and this was the 3rd time they'd tried to replace a system started in the 60's and continuously maintained and updated.

      After 4 years and enough money to keep me on an island under a palm tree for the rest of my life, eventually this one failed too. I strongly suspect they still use it to this day, because I can't imagine it's something which is ever going to get any easier to fix.

      --
      Lost at C:>. Found at C.
    24. Re:If it ain't broke... by bws111 · · Score: 4, Informative

      The question which everyone is ignoring is 'why are they still using this'? The speculation is that they are lazy, cheap, protecting jobs, stupid, etc. However, there is a video of the company on YouTube, and if you watch it you can see why they are still using this machine. The whole place is run by punch cards. They use punch cards for inventory control, job time counting, and controlling some of the industrial machinery. This machine is just used to run reports of inventory, etc.

      Could this all be replaced? Of course. Is it as simple as a spreadsheet? Not even close.

      Note that it is not at all uncommon to be in this situation. Industrial equipment lasts far longer than IT. For some reason, companies seem reluctant to spend a few million dollars replacing perfectly functional equipment just because the IT aspects of it are outdated.

    25. Re:If it ain't broke... by Kaenneth · · Score: 2

      I'm imagining a Smartphone app that can pictures of punchcards, then execute them.

      (In case I'm actually the first person to think of this, I hereby grant any patent interest to the public domain.)

    26. Re:If it ain't broke... by gstoddart · · Score: 1

      Business Continuity would have a shitfit over that. What would happen if he got hit by a bus?

      Oh, it caused a lot of grief to be sure. When he retired in his 60's and left, he had no intention of coming back.

      After a month of so, the panic level started to go up, and they started cranking up the amount of money they were willing to throw at him to come back as a consultant. And this was .com era San Francisco, so you can imagine the numbers involved.

      Sadly, they knew they needed to replace the software for years, but had already tried several times and failed.

      I suspect there is more critical stuff than people realize in various business that is a bus-accident away from becoming unusable. And, quite frankly, that is definitely scary.

      Nonetheless, I've seen it more than once.

      --
      Lost at C:>. Found at C.
    27. Re:If it ain't broke... by greyparrot · · Score: 4, Informative

      And that is why
      "Between 60 and 80 per cent of all business transactions performed worldwide are processed—very effectively and efficiently—by COBOL programs running on mainframes. Within the financial industry (banks and insurance), COBOL is used extensively to process the vast majority of their transactions."
      https://scs.senecac.on.ca/~timothy.mckenna/offline/COBOL_not_dead_yet.htm

      I stopped writing COBOL in about 1985, but we were smart people, and our code was pretty good. It has lived all this time. Most of the new wave crap I have been involved in since has drifted off somewhere. It was relatively easy to create, but the technologies changed so fast that most of it was ephemeral. I bet some of my CICS is still running!

    28. Re:If it ain't broke... by phantomfive · · Score: 1

      Did he end up coming back?

      --
      "First they came for the slanderers and i said nothing."
    29. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      websphere is managed by JACL !

    30. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      After begging, pleading, kicking and screaming to, if not migrate, at least get someone to be my backup in case something happened to me. I finally quit.

      When I had started with the company there was my boss, me and two others in the department. One by one the others quit and I picked up the slack with no additional pay, finally leaving me alone to do everything. Programming, testing, planning, budgets and so on. Everything.

      I would not move anything into production unless it had been tested by someone outside of the department and they would sign off on it. I had almost two years of work waiting for someone to test at one point. Departments would ask for a system and I would build it and test it as best I could. But when it came to final testing no one wanted to take the time and responsibility to formally test it and so I kept it off line to them no matter how much they screamed so there it sat.

      Finally I could not stand it any longer. Found a position with a contract house (tripling my pay) and gave two weeks notice. No one seemed to even care as I left.

      I always wondered whatever happened to them. They were a big company with offices all over the world. Greater than 10,000 employees easily.

      I never looked back.

      Even when you try your hardest to prevent a company from doing stupid things they sometimes will not listen to you.

    31. Re:If it ain't broke... by RabidReindeer · · Score: 1

      The problem with that can end up being "when it is broke, how are you going to fix it?"

      What I want to know is where do they get their blank card stock? Do they pay a junior person to cut out blanks from sheets of Manila paper?

      Bad enough that you probably have to machine custom replacement parts for the hardware, since the scrapyards are likely mined out by now, but a Hollerith card can only make about 2 dozen trips through the machine before it gets too worn to keep using.

    32. Re:If it ain't broke... by balise · · Score: 1

      "Oracle" *would* write this. Answer is, as one of previous posters indicates, it's *EASIER* to debug the wiring than it is to debug masses of code. I have breadboards still in my office, to prove.

      --
      John Eadie [JE46] http://www.c-art.com `one of these days the dogs aren't going to eat the dog food' - Bill Joy
    33. Re:If it ain't broke... by Sussurros · · Score: 1

      Just imagine writing a job listing for someone to replace a retiring remployee!

      Clearly they'd have to train someone suitable on the job, and for the right person it wouldn't be too hard, but when that person moves on it would look very strange on their resume.

      --
      I said - don't look Ethel!..., but it was too late..., she'd already looked.
    34. Re:If it ain't broke... by Anonymous Coward · · Score: 0

      I would say the BA's did not do an effective job - you NEED to spend enough time with the actual users of ALL phases of the system to learn the current operation. Meetings do NOT do this - you need to spend one-on-one with the users and watch them and talk to them individually. THEN you can build a document that lists the current system and its interactions. Only THEN should you start on the replacement system. This is ABSOLUTELY doable, and is only costly because SO MANY CONSULTANTS and managers make such a big deal about it and turn it into a multi-year multi-million dollar project. MUCH of the cost comes in incorrectly documenting the functions and interactions (both internal and human) of the original system.

               

    35. Re:If it ain't broke... by RyoShin · · Score: 2

      It doesn't even have to be as large as a mainframe application.

      For my senior thesis for my Bachelor's degree, I took on the task of taking on an old DOS flat file "database" system and creating a modern equivalent. I did the same as a sibling post, asking how they use it, what could be what, etc., and then I started to make the program. As I did so, I started looking at the data it held for myself--the format (which I forget at the moment, but I think it was something from IBM) could designate "columns" with data types, and then completely disregard those data types. So you would have a field like "weight", and then the data could be "X1444RTTJU8" because when they had a an entry related to a problem, they would use that field for notes. And the program had no problem with this, even searched on that.

      I only had a short time to work on this, and I got in way over my head. In the end, I had to leave the company before I could complete the project. No one there was disappointed, though, as the only reason they seemed interested in replacing it was due to a corporate mandate about replacing technology no longer supported after X years, and I made the fifth or sixth person to attempt and fail (all of us being interns or otherwise low-level devs) on this very task.

      What I took away from the whole project (and what I wrote as the final portion of my thesis) was that I approached it from a completely wrong angle: I was trying to copy the program, when instead I should have been focusing on the task and goals and working from there.[1] Not that you can't miss edge cases in this scenario, but you will be better able to handle them because you won't be trying as stringently to maintain an outdated input system.

      [1] Although I likely wouldn't have gotten too far with this, either, as those who actually used it seemed unwilling to help me; they were all folks that seemed very set in their ways, resistant to any change, and I got the feeling that they saw a replacement as a threat to their jobs. In addition, all of them were trained to use a set of instructions that was "Press X, now press T", etc., and not actually describing what they were doing, but just how to do it. If the program suddenly disappeared, I suspect they would have no idea how to do half their jobs.

    36. Re:If it ain't broke... by volmtech · · Score: 1

      I find it hard to believe that every company has unique needs and has to have custom software. I owned a farm, grossed about $500000 a year. I wrote a program for my Sinclair ZX81 for my financial records, yes, it was custom software but come on, it only had 64k of memory. That and a writing a few things down in a notebook (the paper kind) was enough. At the time developers wanted thousands for their custom "farm" accounting programs.

    37. Re:If it ain't broke... by volmtech · · Score: 1

      I worked at a packing plant that had a potato sorting machine. In 2006 it was 13 years old and ran on a 386 box with DOS 3.1. To upgrade to Win 95 would have cost $40000. The sensor head circuit boards required 3.1 and were no longer available. The new models needed 95. We had two spares. So far it's still running.

    38. Re:If it ain't broke... by RockDoctor · · Score: 1

      But I once worked at a place where the mainframe guy had retired, was drawing his pension, and had been hired back as a consultant at 3-4x his previous salary because there wasn't anybody on the planet who could run the old system. Literally, since he'd been the one who maintained it for several decades.

      I had a friend with a retirement plan like that, but I fucked it up for him. He was given a temporary assignment in his logistics department to help with a particular short-term project, and didn't understand what was involved. So he asked me (who worked in that particular game) for a 10 minute introduction to that part of the business. My intro actually took about 2 pints, but it gave him a clear understanding of the sequence of things that would be needed, what precedes what, likely lead times. All the sorts of things that one needs to understand to supply the project with materials and equipment. And he did this temporary assignment work easily and well.

      UNFORTUNATELY, he did it so well that when his retirement plan came to fruition and most of his normal department were laid off (then re-hired at consultant rates), he was kept on, at employee rates, to do the work of 3 previous people (including himself) in the new department, which became permanent.

      Oh well, he did ask!

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
  3. The manager's moto by Dancindan84 · · Score: 5, Insightful

    "If it ain't broke, don't replace it. Even if replacing it would lead to a 3 fold increase in employee productivity."

    --
    "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    1. Re:The manager's moto by Capt.DrumkenBum · · Score: 1

      Even if replacing it would lead to a 3 fold increase in employee productivity.

      I have seen those kinds of productivity increase numbers thrown around for years, but honestly I have never see a good result. Usually the new system is slower.

      --
      If I were God, wouldn't I protect my churches from acts of me?
    2. Re:The manager's moto by D1G1T · · Score: 2

      I'm gonna bet that they already have a spreadsheet worked up to replace it when it dies. People run stuff like this because they LIKE it. Like those of us who still pull out our old 15C calculators and program them to solve a real problem even though excel would be faster. They are lucky that management permits them to have a little fun at work. Fun = productivity.

    3. Re:The manager's moto by H0p313ss · · Score: 1

      Even if replacing it would lead to a 3 fold increase in employee productivity.

      I have seen those kinds of productivity increase numbers thrown around for years, but honestly I have never see a good result. Usually the new system is slower.

      I was going to say something similar, you usually end up exchanging the problems and limitations of the old system for a the problems and limitations of the new system which is rarely faster and usually requires even more maintenance. Very rarely does the TCO savings, if any, match the cost of implementing the new system.

      That said, sometimes you have to just bite the bullet.

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    4. Re:The manager's moto by Jawnn · · Score: 1

      "If it ain't broke, don't replace it unless you can't fix it when it does break. Then you should work on replacing it as soon as possible. Even if replacing it would lead to a 3 fold increase in employee productivity."

      TFTFY

    5. Re:The manager's moto by Capt.DrumkenBum · · Score: 1

      Yeah, sometimes you have to bite the bullet, but I tend to think the biggest reason should be: "Who is going to fix this thing in 10 years when Bill is retired or dead?"

      --
      If I were God, wouldn't I protect my churches from acts of me?
    6. Re:The manager's moto by Dancindan84 · · Score: 1

      I admittedly don't have experience with something this old, but up until about 8 years ago the college I work for was still using an old HP mainframe for student information and course scheduling. I don't think we've done any metrics on it, but I would guess a 3 fold increase in productivity is likely when we moved to our new system. A few factors:

      -We had 2 programmers who knew COBOL, and I was on a different development team so we only had 1 programmer who knew COBOL who worked with that system. We now have 2 dedicated programmers working on the new student system, on top of a decrease in development time to using a less cumbersome language this has lead to a huge decrease in time to get new reports written.
      -If you wanted a report printed, you had to go into the server room and pray to the mainframe gods that the feed printer didn't jam (he rarely listened to our prayers).
      -There was no kind of self service options for our staff/faculty/students on the old system, so a lot of manpower was used in looking up information in the system that's not on the new one.

      Yes, there was a huge overhead in costs and manpower to get moved over to the new student system, but it's more than paid for itself at this point. Again I don't have any solid metrics on that because I don't know that anyone tracked development/manpower time that went into the old or new system.

      --
      "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    7. Re:The manager's moto by mikechant · · Score: 1

      Also, it buys them some limited but still effectively free publicity (which I don't begrudge them at all, as long they give the kit to a museum when they're finally done with it).

    8. Re:The manager's moto by Anonymous Coward · · Score: 0

      If all you do is replace the old system with a new one, and you require all the same manual steps, of course it's not going to be much different.

      The efficiency increase comes from things like replacing the dude who translates inventory data into punch cards with a barcode scanner next to the loading dock.

    9. Re:The manager's moto by plover · · Score: 4, Interesting

      That's because the new system is frequently implemented in the latest version of a one-size-fits-all, Three-Letter-Acronym, popular technology of the day. And that's because the implementers are obsessed with flexing their technological prowess, instead of solving the business problem. I know a guy who would start by insisting this company should replace this thing with a Grails / Hadoop based solution. Why? Because he's a Grails and Hadoop fanboy, not because they have anything to do with this business' needs. When all you have is a hammer, every problem looks like Michaelangelo's Pieta.

      The bigger question is if this could be replaced with a "faster" system. It probably could, but you have to consider the entire manufacturing and accounting processes it handles. Do they punch the cards and include them with the job? Do workers write notes on the punch cards before returning them? How would all those activities be replaced? There are tons of further things to consider, like a shop floor is a notoriously dirty environment. Labels might be tough because adhesives won't stick due to oil on the work products. A beeping scanner might not work if the employees wear hearing protection. And no matter what, if you have to retrain your employees to do a process differently, there will be a temporary slowdown due to the learning curve.

      On the plus side, if you are honestly looking at your business process with an eye to changing the automation, you can probably find places where the new automation would help you to eliminate waste. Do the shop guys measure things with a dial caliper and write them down? Plug in a data collecting caliper and skip the pencils. Do the guys have to move a job sheet from bin to bin as they do their work? RFID tags on the bins could eliminate the handling of the job sheet. Can a new scheduling program help you find the more profitable jobs, or the faster paying customers, and move them to the front of the queue when cashflow is tight?

      There's likely a lot of things they could improve with automation, but any of them would involve a lot of change, and many people are uncomfortable with that much change.

      --
      John
    10. Re:The manager's moto by Capt.DrumkenBum · · Score: 1

      And there you have it... The exception that proves the rule. :)

      --
      If I were God, wouldn't I protect my churches from acts of me?
    11. Re:The manager's moto by fermion · · Score: 1

      Even if updating meant you did not blow your neighbors to smithereens.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    12. Re:The manager's moto by rickb928 · · Score: 1

      An RPN calculator is still the best way to balance your checking account, if you still balance your account.

      If you don't you may not be able to afford a decent calculator.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    13. Re:The manager's moto by mysidia · · Score: 1

      Yeah, sometimes you have to bite the bullet, but I tend to think the biggest reason should be: "Who is going to fix this thing in 10 years when Bill is retired or dead?"

      Maybe that means you don't need to do anything right now... just have Plan B ready to execute at will, in about 10 years?

  4. I used to write programs in PL1/PLC on punch cards by mark_reh · · Score: 3, Interesting

    at Florida Technological University (now called UCF). I remember a few instances of seeing people trip or drop stacks or boxes of cards on the floor and then crying when they had try to reorder them to get their program to work.

  5. And I thought I was all "1337" by mmcxii · · Score: 2

    My working C=64 ain't got nothing on this fine machine.

    1. Re:And I thought I was all "1337" by Anonymous Coward · · Score: 0

      I have a functional Osborne 1 that I might be convinced to let them upgrade to. :)

    2. Re:And I thought I was all "1337" by Anonymous Coward · · Score: 0

      I'll savor my working C65 prototype over a C64 any day.

    3. Re:And I thought I was all "1337" by Anonymous Coward · · Score: 0

      It does have something. There's a lot more software available for the C64. You just need to link a PC and your 1541, then write disk images to real floppies for convenience (or build a C64 hard drive by breadboarding an SD card with a microcontroller interface). Then you can play New Paradroid.

  6. Points at IBM 402 by Anonymous Coward · · Score: 0, Offtopic

    Hideki!

  7. Debugging that...ladder logic. by Anonymous Coward · · Score: 0

    That shouldn't shock anyone who's dealt with PLCs.

    1. Re:Debugging that...ladder logic. by Redmancometh · · Score: 0

      I have a smartPAC opened up as I type this going to a wintriss clutch control.... the wiring is not a fun task

  8. or a parts cost more then a full new system by Anonymous Coward · · Score: 0

    or a parts cost more then a full new system

  9. More realiable by Anonymous Coward · · Score: 0

    I wouild rather use this than trusting Microsoft products to manage my accounts

  10. Re:I used to write programs in PL1/PLC on punch ca by greyparrot · · Score: 3, Interesting

    Yeah, so did I. You were supposed to use the last 6 columns for a number that you could use in sorting the cards. We also used markers so you could line up the cards based on the position of a diagonal stripe on the edge. PL/1 - what a language! I had to write an assembler in PL/1. It was a great way to learn what we used to call "structured programming".

  11. nice. by Anonymous Coward · · Score: 0

    My dad had an Altair 8080 CP/M machine that he build in 75 and ran in his business until well after the turn of the century.

  12. Re:I used to write programs in PL1/PLC on punch ca by codegen · · Score: 1

    That why you use sequence numbers in 73-80. Been there, done that. But only did it once.

    --
    Atlas stands on the earth and carries the celestial sphere on his shoulders.
  13. But Can You Get Spare Parts? by Anonymous Coward · · Score: 0

    It it ain't broke, don't fix it.

  14. Re:I used to write programs in PL1/PLC on punch ca by karstdiver · · Score: 1

    Learned quickly to run a magic marker squiggly line over the top of those card decks...

  15. I'll reply to you. by Anonymous Coward · · Score: 1

    "If it ain't broke, don't replace it. Even if replacing it would lead to a 3 fold increase in employee productivity."

    A few other folks posted something similar above at the same time.

    Anyway, if I were in charge, here's what I'd do:

    Look at the power consumption of the machine. It's probably a lot.

    Have the accountant write the specs for what that was to do.

    Buy the accountant ANY damn laptop they wanted.

    Sell that old machine to some computer collector that would pay through the nose to acquire.

    Profit. Or at least, it would compensate the costs of moving the system to something a little more modern - a MS Office App is probably all this company needs or an intranet web app.

    Why upgrade?

    That machine is gonna die one day.

    Having something a little more modern will allow for growth and integration.

    1. Re:I'll reply to you. by Darinbob · · Score: 2

      They are slowly migrating to using PCs according to article. They turned down offers to buy the machine from the Computer History Museum, so they must be using it or else have a lot of nostalgia for it (a perfectly valid reason to keep it).

      There's not a lot of details on what exactly they use the machine for. But I suspect they keep it because the current process is working. Punch in numbers, put the cards on file, later gather up groups of cards and run them through the machine to do some simple arithmetic calculation (basically the only thing that machine can do), take the results and use those with a PC accounting package, put cards away until next time.

      It's not a big machine if you look at pictures of some of them. My guess is that it really doesn't take more power than those large Xerox style copier/printer/collator/fax machines you see in most corporate offices. Plus they don't run this machine constantly, probably a couple times a week. Unlike a mainframe you can just turn it on when you need it then turn it back off again.

    2. Re:I'll reply to you. by rickb928 · · Score: 1

      You presume the accountant can write the specs. Which presumes they can figure out all that is part of the current system.

      I would expect that 2 years later, tops, something will come up that requires a patch, and the custom programmer you used is either drunk, dead, or expensive. and the code is undocumented, convoluted, and beyond maintainable.

      Just experience talking here. It could happen in 6 months as well.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    3. Re:I'll reply to you. by mysidia · · Score: 1

      They are slowly migrating to using PCs according to article. They turned down offers to buy the machine from the Computer History Museum, so they must be using it or else have a lot of nostalgia for it (a perfectly valid reason to keep it).

      Perfectly valid reason for a person/individual to keep something (personal sentiment / emotion); not a valid reason for a business to keep it, if the business owns it, and they can make more money by not having it, then keeping it would be a poor business decision in that case.

    4. Re:I'll reply to you. by GuB-42 · · Score: 1

      Businesses may not have feelings but the people that make it up do. Also, they got a slashdot article because of it ;)

  16. How much power does that beast consume? by Radak · · Score: 2

    And now long would you have to run it to spend the same amount of money it takes to buy modern equipment and pay for someone to convert your accounting over?

    I like "if it ain't broke" in general, but this thing has to be a massive power drain, and when it finally does break, they're likely going to be screwed.

    1. Re:How much power does that beast consume? by admdrew · · Score: 2

      I think the "when it finally breaks" issue is probably of bigger importance than the power draw. Generally (and what others in this thread have already alluded to), a conversion may be far more complex/time consuming than we might think. Future functionality is one thing, but migrating old data to a new system can sometimes be very difficult, especially for something as important as accounting. And you usually need someone with intimate knowledge of the legacy system, which can require massive reverse-engineering if the system is older than most of your employees.

    2. Re:How much power does that beast consume? by rahvin112 · · Score: 3, Insightful

      And what happens when the lady that's running this system dies of a heart attack and the only people that even know how to use one of these computers are all retired and senile?

      It's not just the machine costs, the retraining. It's what happens if the only person who truly understands the system gets hit by a bus. The hit by a bus scenario is often overlooked in small businesses. You don't just need to be able to replace the system and hardware, you need to be able to replace the people running it, without advance notice.

    3. Re:How much power does that beast consume? by admdrew · · Score: 1

      Totally agree with you. In the end, that's the risk that people are taking when they "save" the cost of upgrading and leave the legacy stuff in place.

    4. Re:How much power does that beast consume? by mysidia · · Score: 1

      And you usually need someone with intimate knowledge of the legacy system, which can require massive reverse-engineering if the system is older than most of your employees.

      Ah but not all the employees, and it sounds like maybe one employee has got a personal attachment going, and therein lies the problem.

      This could be a little bit of a conflict of interest, as it provides job security for the head accountant; whereas, it would be in the business' best interests to be using commodity equipment, and data processing procedures well-understood by the accounting industry, which are also more easily outsourced, or farmed out to external accounting organizations, for purposes of auditing, verification, or actually hiring external org to do all the company's accounting, for example.

      Management should not be allowing the lead accountant to be choosing such an unusual accounting system, when it should be replaced. :)

    5. Re:How much power does that beast consume? by mysidia · · Score: 1

      And what happens when the lady that's running this system dies of a heart attack and the only people that even know how to use one of these computers are all retired and senile?

      The lady herself might not mind this, as she'll be dead, it's probably the farthest thing from her mind. Even if the very same lead accountant, would recognize this problem in any other department, and ensure that it was fixed.

      The lead accountant might often double as responsible manager role, and address that issue elsewhere in the organization, while being blind to the fact that they themselves are a single-point-of-failure risk.

      For some reason, also, companies often seem to give the people in charge of their accounting department a whole lot of latitude, in deciding what systems they use, and quietly making choices that suffer that problem, as long as the data is produced to management's satisfaction; almost as if accounting becomes an "island", and is the last department to ever come under scrutiny; even when companies' management teams force their other departments, and use that criteria, that every process has to be able to continue if any one person gets hit by a bus, and noone unreplaceable.

      It's as if "accounting department is management", and "different rules apply to management"; we never think of "What if the CEO or CFO gets hit by the bus?".

      Perhaps the personal pain of thinking about that drives them away from responsible action, even when they can clearly see, what is responsible action, with regards to non-management.

      You would never allow a clerical worker to implement a proprietary filing system for paper document storage that noone else could use; such as a "proprietary" sorting order, with a randomized alphabet memorized by one worker.

  17. I still use punch cards ... by perpenso · · Score: 4, Funny

    While in college there was still a working punch card machine on campus. Our intro to computer science professor made us write our first program using punch cards. He said we would get two things out of it. We would understand why some things are the way they are with respect to programming languages and command lines. And we would have book marks for life (the program was short but we had to buy a deck of blanks at the bookstore). I still use these cards for bookmarks.

    1. Re:I still use punch cards ... by Darinbob · · Score: 2

      In a class on numerical analysis and computing we used Fortran for the programming homework. One of my friends decided he wanted to do the entire thing using punch cards. The rest of us laughed at him because the computer center had all these modern CRT terminals. But he would go into the side room with the punch machine and use that while the rest of us called him crazy. Then at the end of the school year there was a big queue to use the terminals from every class at the university that had a programming assignment due. Then we saw my friend walking past the door carrying a stack of cards and telling us with a smirk "there's no line at the punch card reader!"

    2. Re:I still use punch cards ... by Anonymous Coward · · Score: 0

      I remember the first program that I had (including the dataset) that approached a box of cards in Fortran. It was for a new thing at the time called computer mapping. I had to debug the program and the data several times before they agreed that it wasd correct and the reason it was not running was that they had not allocated enough resources on the IBM 360 (fairly new at the time). They shut down everything else one weekend and let it run and then it worked. Debugging hollorith cards is no fun, you are right. The human readable line at the top did not print clearly and sometimes the characters were only partually on the card. AARGH!

  18. So let me see by Anonymous Coward · · Score: 0

    In 1973 a small company could buy a computer to keep books, so well it can still be used today, but just ten years earlier, NASA, with a budget of 6% of the USA's GDP, wasn't able to use computers to help design the F-1 engines?

    1. Re:So let me see by camperdave · · Score: 2

      In 1973 a small company could buy a computer to keep books, so well it can still be used today, but just ten years earlier, NASA, with a budget of 6% of the USA's GDP, wasn't able to use computers to help design the F-1 engines?

      Amazing what the invention of the microchip brought about, isn't it?

      --
      When our name is on the back of your car, we're behind you all the way!
    2. Re:So let me see by Anonymous Coward · · Score: 0

      Considering there were computers using relays, vacuum tubes and discrete transistors before, I find it hard to believe that the same country that was already being computerized in the early 1960s was unable to spare a mainframe to do some calculations for a rocket engine. Maybe they needed all those computers to translate the blueprints from German?

    3. Re:So let me see by kermidge · · Score: 1

      Given the large amount of statistical analysis from testing results and the large amount of theoretical analysis, I'd be mightily surprised to find that computers were not used for this.

      http://history.nasa.gov/SP-4206/ch4.htm#110

      provides a bit of background.

      For much of the testing and engineering fixes, it was largely slipsticks and blackboards, per some of the anecdotal personal remembrances found by search, and a lot of brain-box "sweat" from the wealth of practical engineers who worked on them.

  19. "imagine debugging that" by Anonymous Coward · · Score: 0

    I think that's the point here. It WORKS, so you don't have to. I'm sure all sorts of dipshit hipster technolibertardians are salivating at the mouth to replace a simple system that works with an iPad app and keeping all their data in a "cloud" service, increasing their costs a thousandfold, reducing the reliability of their systems and giving them more complexity for no gain other than to stay buzzword compliant and keep a sad bunch of brogrammers supplied with horn rimmed glasses and pabst for another week.

  20. It's not broken, so let's break it (SAP). by Maxo-Texas · · Score: 4, Interesting

    Company where I worked decided there perfectly fine AS/400 systems were not good enough and would save lots of money replacing the 20 year old system with SAP.

    Hilarity ensued.

    (and lots of 70 hour weeks... only 5% implemented with 15 years worth of projected savings already spent).

    --
    She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    1. Re:It's not broken, so let's break it (SAP). by sandytaru · · Score: 1

      I once met a guy who said that when his company ditched his AS/400, he'd take it as a sign to retire. Smart man.

      --
      Occasionally living proof of the Ballmer peak.
    2. Re:It's not broken, so let's break it (SAP). by Anonymous Coward · · Score: 0

      They may work fine 'now'. But planing for them going kaput is not a bad plan...

    3. Re:It's not broken, so let's break it (SAP). by greyparrot · · Score: 3, Funny

      Jah, SAP. World's slowest suicide method.

    4. Re:It's not broken, so let's break it (SAP). by jellomizer · · Score: 2

      SAP has been known to bring down companies, do to poor IT management, they try to use the system to replace the existing ones, vs. changing the organization to work with the new system.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    5. Re:It's not broken, so let's break it (SAP). by St.Creed · · Score: 1

      It's pretty easy to plan for. See http://en.wikipedia.org/wiki/IBM_System_i

      They're in use at quite a lot of places, and I know of at least one company that moved software from AS/400 to RS/6000 and then to the i-series.

      --
      Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
    6. Re:It's not broken, so let's break it (SAP). by lgw · · Score: 2

      I can remember when "everyone is implementing SAP, no one has implemented SAP". As much as peoplesoft blows goats (and it blows a great many goats indeed), you can see why it took off.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    7. Re:It's not broken, so let's break it (SAP). by frank_adrian314159 · · Score: 1

      I could see getting a new iSeries or even trading up to a zSeries box, but trading down to an xSeries (or worse, some generic junk box) because they wanted to run SAP? That's a sign to find a new job.

      --
      That is all.
    8. Re:It's not broken, so let's break it (SAP). by rickb928 · · Score: 1

      SAP is Satan's preferred method of interaction with this world. Ask him, he'll tell ya. He's the one in the suit that sold it to your boss.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    9. Re:It's not broken, so let's break it (SAP). by mysidia · · Score: 1

      they try to use the system to replace the existing ones, vs. changing the organization to work with the new system.

      Any system your business has to conform to is a bad one; unless the changes to the way the organization works are actually improvements in themself (not because of the system having arbitrary constraints that restrict the way you can run your business, or force otherwise unnecessary change on your business).

    10. Re:It's not broken, so let's break it (SAP). by Maxo-Texas · · Score: 1

      It has it's pluses and minuses.

      We had -- over 2 dozen ways to fill out a purchase order.

      We probably needed two or three.

      OTH, they missed so much basic business functionality because they rushed the blueprinting stage (only 24 months- the results were comically bad).

      The "De Troite" consultants sold them an incredible bill of goods. Some of the specs which they had been paid a couple hundred bucks an hour for were complete nonsense. It was clear to me that they had written junk, gotten a signoff because no one had a clue what was right or wrong, and then left with their "on time bonus".

      It was dead on delivery and had to be redeveloped from scratch under brutal conditions. I still remember some pictures of the blueprinting group having a big party- all their noses were red. They were working long hours but nothing like the rest of us had to work (70+ hours a week- saturdays and some sundays. ended up working a month straight with no days off twice).

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  21. Not very Green by Anonymous Coward · · Score: 1

    Wouldn't the power savings of replacing the computer and all the peripherals justify the replacement of all that with even an entry level PC, from 10 years ago?

    1. Re:Not very Green by Joce640k · · Score: 1

      It might ... if you don't count the man-hours needed to rewrite the software and the constant effort needed to keep a 10-year-old PC from imploding.

      --
      No sig today...
    2. Re:Not very Green by ponraul · · Score: 2

      This computer only has to be on when it's actually processing/tabulating. It's only getting juice for the 20 or so minutes a day you're processing payroll or the day's invoices. Your office PC never gets turned off.

  22. Just one question...WHY?? by dubdays · · Score: 2

    Kind of like mowing the lawn with a pair of scissors. Yeah, I'm sure it could be done.

  23. Is this an old story? by Animats · · Score: 3, Informative

    I thought the Computer History Museum got that IBM 402. There's one in the Computer History Museum now. They may have the machine the company was using for parts.

    Here it is running in Conroe, TX in 2011. (Terrible video, though)

    1. Re:Is this an old story? by 93+Escort+Wagon · · Score: 1

      Most of those "parts" in that photo can be purchased at a hardware store!

      --
      #DeleteChrome
  24. Wow by geek · · Score: 4, Funny

    And people bitch about XP users hanging onto an old and obsolete system.

    1. Re:Wow by Anonymous Coward · · Score: 0

      I understand choosing XP over any other version of Windows.
      I don't understand choosing XP over any version of any other (post-DOS) OS.

    2. Re:Wow by tftp · · Score: 1

      And people bitch about XP users hanging onto an old and obsolete system.

      XP may be old, but it is in no way obsolete.

  25. No need for a laptop either by Anonymous Coward · · Score: 0
  26. no harder than debugging wire-wrap circuits by Chirs · · Score: 1

    I took an embedded systems course in university (Engineering Physics program)....we had to build boards up from components, write software in assembly, and then load it into the hardware and cause the hardware to do stuff.

    My longest debug session was when I couldn't figure out why my software wasn't working properly...turned out that my team-mates had mis-wired the stepper motor. Once I figured out exactly how they had screwed up the wiring I was able to compensate in software and it worked perfectly.

  27. 026 by Peter+Simpson · · Score: 5, Informative

    That's an 026 keypunch he's leaning on, not a 129.

  28. Re:I used to write programs in PL1/PLC on punch ca by cardpuncher · · Score: 2

    That's why smart people punched sequence numbers in columns 73-80. It helped if you had access to a card sorter, otherwise you'd incur machine time using the sort program to punch a new deck.

    There was a lot of standalone electromechanical hardware (not just punches and sorters) to support punched card data processing - my mother (now 80) worked for a utility company in the 50s and alternated her time between doing data entry (card punch) and data verification - essentially retyping the data on a card verifier with the punched card in place to check the data entry was correct.

    Actually, an early version of the IBM FORTRAN compiler (for a real computer) marked the cards according to the statement type on a lexical analysis pass and then sorted the cards by that field so it could load the compiler code that dealt with each particular type of statement in turn (the computer having very little memory). The generated code was then resorted to match the original program card sequence.

  29. Re:I used to write programs in PL1/PLC on punch ca by Rene+S.+Hollan · · Score: 1

    Yeah, BINDERE DUNDAT.

    c. 1977, cutting my teath on "real programming" in Fortran, and CDC 6600 Assembler with punched cards (post HP2000 Basic -- everyone starts with Basic - in high school). We did have a few plugboard computers, including at least one analog computer, as well.

    --
    In Liberty, Rene
  30. I've lost track of the software... by satch89450 · · Score: 4, Interesting

    ...that would take documentation of the plugboard wiring of the old 400 series "accounting machines" and produce source that would work exactly the same as the accounting machine, give 80-column card images for the data. It wouldn't emulate any cross-connects to other tab equipment (sorters, punches, interpreters) but it did a wonderful job of moving plug-board programming to the more modern computers (360, in particular). Anyone know where that software might be? As I recall, it was on a micro-spool of magnetic tape originally, purchased at user group meetings. Time to google...nothing so far...

    1. Re:I've lost track of the software... by Anonymous Coward · · Score: 0

      ...that would take documentation of the plugboard wiring of the old 400 series "accounting machines" and produce source that would work exactly the same as the accounting machine, give 80-column card images for the data. It wouldn't emulate any cross-connects to other tab equipment (sorters, punches, interpreters) but it did a wonderful job of moving plug-board programming to the more modern computers (360, in particular). Anyone know where that software might be? As I recall, it was on a micro-spool of magnetic tape originally, purchased at user group meetings. Time to google...nothing so far...

      One version was called FARGO, went to 1401 code. There are 1401 emulators out there. We did a double emulation in the Air Force in the 1960s, FARGO to 1401 to 360. Worked, believe it or not.

  31. Stupid Stupid Stupid by Anonymous Coward · · Score: 0

    They're paying a huge electricity bill to run a task and iPhone would run faster.

  32. Someone should be fired by frovingslosh · · Score: 4, Insightful

    OK, I get it, Sparkler hates trees. But the insanity of someone protecting their job by never updating technology is just amazing. I would love to see what they have spent on maintenance over the years for that electromechanical junk. And I really wonder where they are getting punch cards. Can you even get them any more, or are they having a printer make custom batches for them? And, of course, there is no really useable backup of all of the company's data for when the inevitable final failure hits. For less than the cost of their next punch card order they could be on a modern system with performance and good data backup. But then I guess that Lutricia Wood might be concerned that others might be able to do thing that only the high priestess of data systems does now. Good thing that she will live forever and never retire, otherwise Sparkler would be in a very bad position.

    --
    I'm an American. I love this country and the freedoms that we used to have.
    1. Re:Someone should be fired by admdrew · · Score: 3, Informative

      someone protecting their job by never updating technology is just amazing

      That may be part of it, but generally an overhaul of an entire system like that, especially something as integral to a business as accounting, isn't a decision any single person can make. Also, it's possible those who would've had job security by maintaining that system have long since retired. Slow-moving business isn't completely built on nefarious intentions.

    2. Re:Someone should be fired by anagama · · Score: 1

      But the insanity of someone protecting their job by never updating technology is just amazing.

      I don't think it is that kind of insanity -- more the kind where the owner doesn't upgrade because the old system works. As a business owner myself, I can understand that sentiment, though Sparkler Filters has taken that to quite an extreme.

      Carl Kracklauer, whose father founded Sparkler Filters in 1927, usually types the data onto the punch cards. The company sticks with the 402 because it's a known entity: Staffers know how to use it, and they have over 60 years of company accounting records formatted for the device.

      http://www.pcworld.com/article/249951/if_it_aint_broke_dont_fix_it_ancient_computers_in_use_today.html

      --
      What changed under Obama? Nothing Good
    3. Re:Someone should be fired by ebno-10db · · Score: 4, Interesting

      I would love to see what they have spent on maintenance over the years for that electromechanical junk.

      I would love to see what they've saved on not having a bunch of programmers wondering why the latest Java update broke everything.

    4. Re:Someone should be fired by lgw · · Score: 2

      And, of course, there is no really useable backup of all of the company's data for when the inevitable final failure hits

      You mean, other than all the punch cards? You can use your smart phone camera as a punch card reader these days - there's an app for that.

      Also, since essentially all paper in the US comes from tree farms, and since that land would be used for farming something other than trees without the demand for paper, I'd say wasting paper is a sign that one likes trees.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    5. Re:Someone should be fired by Dynedain · · Score: 2

      Well for a very high level (CEO) explanation, the money it will take to replace this system now is money that was stolen over the years from the company in the form of larger profits instead of investment.

      --
      I'm out of my mind right now, but feel free to leave a message.....
    6. Re:Someone should be fired by mysidia · · Score: 1

      OK, I get it, Sparkler hates trees. But the insanity of someone protecting their job by never updating technology is just amazing. I would love to see what they have spent on maintenance over the years for that electromechanical junk.

      Come on... there are a few advantages here. (1) They don't need a firewall, or IT department constantly patching things.
      (2) They don't need to worry about malware, or expensive security software, for antivirus, patch management, computer software inventory management, encryption; web filtering to stop accountants surfing on company time --- there are literally hundreds of costs that exist with PCs that aren't needed with simpler equipment.
      (3) They don't need to buy new copies of windows, and retrain their accountants to use the latest version of Windows.

      It's not like personal computer maintenance is free.

      I would argue... the maintenance is quite possibly a lot cheaper.

      The question should be, what are they risking... and are the benefits/rewards for THE COMPANY (not the 40 year punch card vet) better than the potential productivity gains to be made in initiatives that would require major changes?

      Such poor management could be an opportunity for someone else to take over the company, and fix the problem of revenues being suppressed due to reliance on very very old systems; that while proven, are probably less efficient -- if they weren't less efficient, why aren't more organizations still using punch cards?

      There's no way those other companies' managements ditched punch cards just because PCs looked like a cooler technology, there are plenty compelling cases to be made.... (it's just that hardware maintenance isn't one of them)

  33. Re:I used to write programs in PL1/PLC on punch ca by Peter+Simpson · · Score: 5, Informative

    Drawing a diagonal line across the top of the deck is faster and lets you insert cards without having to resequence.,..

  34. So i wonder how this was discovered? by nimbius · · Score: 4, Funny

    accounting intern:"damn, looks like the microwave is getting repaired. wanna go out for bbq?"
    accounting director:"we dont have a microwave. you mean the accounting computer down the hall??"
    BOFH:"so heres the dead man that just pushed a hot pocket into the 402 and took down payroll! let me get the punch cards kid, you're in for a fun night."

    --
    Good people go to bed earlier.
    1. Re:So i wonder how this was discovered? by greyparrot · · Score: 5, Funny

      I found one (or two) of these once as part of a study. The old M-- H-- bank was going to replace some important system, and I was on the illustrious crew of analysts documenting all its interfaces. One of them was a deck of cards that was output at the end of the run. So very early one morning I followed it from the output room to the mail room, and then the wagon to an office, where the cards were placed on the desk of the person who ran that machine. She and her young assistant ran them through the machine, which duplicated them and added some columns, probably totals of some kind. Then they took the new deck and loaded it into another of the same sort of machine, programmed differently. It read the cards and printed a report. Then she put a rubber band around the report and cards, and it went back on the mail cart. I followed it down the hall and to another floor, where it arrived on someone's desk.
      And...
      He picked it up and threw it into the trash.
      When I wrote it up, nobody wanted to believe me.

    2. Re:So i wonder how this was discovered? by MikeTheGreat · · Score: 3, Informative

      Whoops - this was funny but I accidentally mod'd it as "Overrated"

      I can't seem to find a way to undo/change my moderation.

      So I guess I'll do this, instead :/

    3. Re:So i wonder how this was discovered? by rgbscan · · Score: 5, Funny

      It's funny how those things persist. Years ago, I took over a mainframe data processing department. Every month I would be sent a fan-fold report on that old school tractor fed paper that took up a whole copy paper box. It literally was a 50 pound report. I had no idea what it was for, nor did anyone else. It went straight into the shredder. Every month a new bundle would show up. I sent it straight to the shredder. Didn't even look at it. The box came interoffice mail with no return address and there wasn't any identifying information on the report for me to figure out where it came from or how to get it shut off. Not even a report identifier I could look for in the mainframe. I can't imagine how much time, paper, and impact printer ribbon went into it. I mean, how would you even look for anything on that report? Kept coming every month for the whole 4 years I managed that department. I hear it finally and mysteriously, stopped showing up a year or two ago. The new manager has no explanation for it's demise but it was a good thing. /Shrug

    4. Re:So i wonder how this was discovered? by greyparrot · · Score: 1

      Every once in a while the head of Operations (most places) will look at the print queues and wonder if anyone would notice if a particular report were not produced. Possibly this report's number finally came up. If nobody complains, the report output is commented out of the JCL.

      Odd that it didn't have a report divider cover sheet, though.

    5. Re:So i wonder how this was discovered? by Anonymous Coward · · Score: 1

      Years ago I was installing some manufacturing software at an apparel company. The guy who ran the computer room explained to me that he would occasionally grab one of the long reports they ran and printed regularly and keep it on his desk instead of sending it along. If he got a call asking "Where the $&%# is my report?", he'd bring it over with an apology. But if not, he'd demote the report's frequency, (e.g. daily to weekly) and eventually stop producing it at all. He ended up saving the company a lot of money in paper alone.

    6. Re:So i wonder how this was discovered? by Chuckstar · · Score: 1

      "Ah! Yeah. It's just we're putting new coversheets on all the TPS reports before they go out now..."

      Now we know why. :-)

    7. Re:So i wonder how this was discovered? by Anonymous Coward · · Score: 0

      Use D1 discussion system for moderation. Or there's a greasemonkey script, I think. D1 works pretty fucking well though.

    8. Re:So i wonder how this was discovered? by david_thornley · · Score: 1

      Were you the one receiving that report I was told to produce monthly? I always wondered what happened to it when it got to wherever it was going.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  35. Antique? by Anonymous Coward · · Score: 0

    And I thought my alma mater was out-of-touch running an IBM 7094 (w/ core in oil!) in 1976 as its main campus computer.

  36. Re:I used to write programs in PL1/PLC on punch ca by Joce640k · · Score: 2

    seeing people trip or drop stacks or boxes of cards on the floor and then crying

    Grab a marker pen and draw some diagonal lines/crosses on the edges of the stack. You can easily see which ones are out of order.

    You can also see if anybody has swapped a couple of them around as a "joke".

    --
    No sig today...
  37. What a bunch of n00bs! by Anonymous Coward · · Score: 0

    At this company, we use difference engines. And that's the way we like it!

  38. Can it run crysis? by Anonymous Coward · · Score: 0

    But can it run crysis?

    Let's load it up with 10,000+ punch cards.

  39. It's not a matter of "if it ain't broke, don't fix by Anonymous Coward · · Score: 0

    It's not a matter of "if it ain't broke, don't fix it".

    Even if it correctly does the computations it's supposed to do, it's doing it at a cost probably thousands of times of what it would cost with a non-obsolete system. Power costs, paying someone with the incredibly rare skill set needed to operate that machine, repair labor/costs, etc.

    It's no different than, say, using manual labor to grow corn. Sure, it can be done, but at a cost manyfold of using modern techniques.

  40. Replacing operator by sinij · · Score: 1

    Replacing this dated equipment will also result in replacing operator, and that can have all kinds of hidden costs. If someone worked for your business for 40 years and is loyal and productive employee, then why do you care if they want to do it with punch cards or abacus? They had 40 years to prove that whatever they are doing works, unless there are new process requirements, there is no reason to change

    Decision chart:

    1. Did any processes change or about to change? Yes/No

    Yes - Go To 3.
    No - Go To 2.

    2. Job gets done? Yes/No

    Yes - leave it alone.
    3. No - look into optimizing/fixing.

    1. Re:Replacing operator by Anonymous Coward · · Score: 1

      That's a recipe for very poor management.

      It's also important to assess the cost/benefit of a process. If process A and process B can both do a job equally well, but process A costs 1,000x process B, it makes no sense to use A.

      Just how much wasted money has gone into maintaining and using that antiquated system? How many man hours alone have been wasted transferring data in and our of that monstrosity?

    2. Re:Replacing operator by mattventura · · Score: 2

      But what if you lose that employee due to circumstances that are outside of your control? Now you have to find someone who knows how to operate an antique computer. Not only is it hard to find such a person, but they might cost an absurd amount of money as well.

  41. the very definition... by Anonymous Coward · · Score: 0

    ...of spaghetti code!

  42. One vacuum tube away from disaster by BenJeremy · · Score: 3, Insightful

    One critical irreplaceable part breaks, and they can no longer process payroll or inventory.

    All because they don't want to hire somebody to spend a week or two to replace the functionality of that obscene waste of energy with a simple spreadsheet. The simple value of data security, not to mention the inter-operability between the data generated and things like, I dunno... check printing and direct deposit, for example, seems obvious.

    I'd also guess there would be a lot less work for their accounting department. Either they could save the expense of one or two peoples' salaries, or at least spread the workload savings among the staff. In any event, it simply doesn't make sense not to modernize it.

    1. Re:One vacuum tube away from disaster by Tweezak · · Score: 1

      A Chinese hacker takes down the mainframe and they can no longer process payroll or inventory.

      There...fixed that for you.

      There is something to be said for old technology.

    2. Re:One vacuum tube away from disaster by ebno-10db · · Score: 2

      One critical irreplaceable part breaks ...

      Breaks? Guess you haven't seen how those old systems were made. You could rearrange it and make a dandy trash compactor for modern computers.

    3. Re:One vacuum tube away from disaster by Anonymous Coward · · Score: 0

      I'm sure they will modernize the system when Lutricia Wood and her people retire. They likely hold the principle of putting people before efficiency, when the issue is not directly related to their core business.

    4. Re:One vacuum tube away from disaster by Stone316 · · Score: 4, Insightful

      A week or two??? How many enterprise systems have you installed? I've been on a couple of these implementations and it just takes a team of people many months of work. The larger the company the longer it takes. One install, for a customer with less than 300 employees took 8 months. Its not as simple as you make it out to be.

      --
      "Thanks to the remote control I have the attention span of a gerbil."
    5. Re:One vacuum tube away from disaster by Anonymous Coward · · Score: 0

      One does not come in and, in a week or two, replace 60 year old accounting processes.

    6. Re:One vacuum tube away from disaster by Slugster · · Score: 1

      If I am looking at the correct location on Google, there is 33 vehicles in the parking lot--and parking space for maybe about three times that much.

      Also in any modern implementation, generally all the back-end aspects of the company are tied together in the software: schedules, payroll, HR, ERP, warehouse management, logistics ect. That doesn't come close to comparing with what this ancient meat grinder is probably being used for.

      I wish them well and all (they have been around a while) but this simply seems odd in a way that doesn't exactly inspire a lot of confidence.

  43. Article title by nitehawk214 · · Score: 1

    "Don't mess with Texas's old computers."

    Seriously, don't mess with them or they will stop working. I feel like just taking a picture of the insides of that thing will make it fall apart.

    --
    I'm a good cook. I'm a fantastic eater. - Steven Brust
    1. Re:Article title by nitehawk214 · · Score: 1

      Also, the label on the computer says "new A/R daily invoice"

      New... in the 1960s.

      --
      I'm a good cook. I'm a fantastic eater. - Steven Brust
    2. Re:Article title by kermidge · · Score: 1

      That's not the computer's label - that's the name of the job being run.

    3. Re:Article title by nitehawk214 · · Score: 1

      That's not the computer's label - that's the name of the job being run.

      Well it is a picture of the Plugboard that represents the program. Which I am sure was written in the 1940s or 50s. (Note: i was off by a couple of decades on the age of the machine in my previous post.)

      Computers this old are always running programs nearly as old, if not older. A manager at a bank I worked for in 2006 quipped, "We are using the most powerful mainframes IBM makes... running COBOL programs written in the 70s."

      And before someone starts on the "If it aint' broke dont fix it." line of reasoning... the code was a 35 year old refuse pile that nobody could make any sense of anymore.

      --
      I'm a good cook. I'm a fantastic eater. - Steven Brust
    4. Re:Article title by kermidge · · Score: 1

      Yah, the dinosaur droppings of the computer age. Some of it is so bad it's wonderful.

  44. I've seen this before by Anonymous Coward · · Score: 0

    adds new meaning to the term "spaghetti code"

  45. I find it difficult to believe in your sorrow. by Medievalist · · Score: 3, Funny

    The 4 hour group was (sorry to say this, but it's a fact) Black girls.

    http://xkcd.com/385/

    Trust me on this, wiring skill isn't normally supposed to depend on possession of a pale pink penis. You're totally doing it wrong.

    1. Re:I find it difficult to believe in your sorrow. by Anonymous Coward · · Score: 1

      From my own anecdotal evidence (survey group of one), it depends on having a monstrous purple appendage. The kind that makes girls faint and women pant.

    2. Re:I find it difficult to believe in your sorrow. by Anonymous Coward · · Score: 2, Funny

      You should probably get that nose looked at.

  46. It's a Zeberpupin System! by cervesaebraciator · · Score: 2

    PHB: "I want to fire Wally, but I can't risk it. He says he's the only one who can program the Zeberpupin system." Wally: "The word you're trying to think of is 'indispensable.'"

    1. Re:It's a Zeberpupin System! by Anonymous Coward · · Score: 0

      I think the word you're looking for is fast. As in, Dilbert Fucking Fast.
      http://dilbert.com/fast/2011-11-19/
      http://dilbert.com/fast/2011-11-21/

      For people who thickos. Thicko.

  47. Re:no by jellomizer · · Score: 1

    To be more realistic, the guy who operates that machine will be retiring in a few years, the people who are willing and able to work it want to be paid premium bucks, also have a tenancy of having a huge ego problem that makes them difficult to work with. The new system is easier to find guys who can do the work, and they will be more willing to work with you.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  48. Indiana Jones says by GameboyRMH · · Score: 2

    It BELONGS in a MUSEUM!!!

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  49. Support contract by bartjan · · Score: 1

    How much is the IBM support contract for this?

    1. Re:Support contract by guttentag · · Score: 1

      How much is the IBM support contract for this?

      Nothing. When they call IBM for support, the support guy laughs for five minutes, dries his eyes, and then says, "thank you, I needed that." He then hangs up and mails them a free raspberry pi that runs a punch card machine emulator.

  50. Re:no by dubdays · · Score: 2

    No offense AC, but there is an element of "stupid" to doing this. How are you going to fix it if it breaks, and more importantly, what will it cost? Also, the same thing could very likely be done with off the shelf commodity hardware and some cheap (or free) accounting software. Accounting productivity would be DRAMATICALLY increased just in the amount of time saved each day. Sounds to me like someone in that company is lacking some serious business sense. Punched cards had their day, but that day is long gone.

  51. Re:I used to write programs in PL1/PLC on punch ca by emeyer · · Score: 1

    I went there when it was still called FTU. I remember the exact same thing. I remember seeing someone drop a large box of cards in the Florida rain which of course meant they lost everything. I went there 1977-78 ... when were you there?

    -Eric

  52. Banks still using OS/2 Warp3 by Anonymous Coward · · Score: 0

    Banks still using OS/2 Warp3 with custom programs and too expensive to replace. Using ISA boards, motherboards, and cpu's you can't find reliable replacement parts for.

  53. Mechanical Computers are Best by EmagGeek · · Score: 1

    Especially the ones that don't even need punch cards to run. Mechanical computers can handle everything from algebra to complex calculus, and are completely impervious to EMP or hacking (except, perhaps being literally hacked, like with a hacksaw).

    Take this one for example:

    https://www.youtube.com/watch?v=s1i-dnAH9Y4

    1. Re:Mechanical Computers are Best by human_err · · Score: 1

      Thanks for the video link. Makes me really appreciate the tools I have now for my programming work. Now if only I had a reel-to-reel projector to watch this with...

  54. Re:Slashdot refuses to stop abuse... apk by Redmancometh · · Score: 0, Insightful

    Why aren't these posts deleted?

  55. Re:Slashdot refuses to stop abuse... apk by Anonymous Coward · · Score: 0

    Because they're hilarious as hell[1]

    1. For purposes of this post, Hell is funny. Dane Cook is not allowed in hell.

  56. Re:I used to write programs in PL1/PLC on punch ca by codegen · · Score: 1

    Cool. Never thought of that one... Or rather was never told that one by the prof or upper years.

    --
    Atlas stands on the earth and carries the celestial sphere on his shoulders.
  57. Not a Computer, its a tabulator by GrumpyOldPgmr · · Score: 4, Interesting

    IBM 402, 403 and 407's were tabulators not computers. As an old IBM program support rep., the first time I ran in to an RPG program it made no sense to me till I realized that RPG is nothing more than an emulation of a tabulator control panel.

  58. nuclear war resistant by sxpert · · Score: 3, Funny

    This company is probably the only one in the area that will still be operational in case of a nuclear war. that type of computing device is pretty much impervious to EMPs.

    1. Re:nuclear war resistant by MobileC · · Score: 1

      This company is probably the only one in the area that will still be operational in case of a nuclear war. that type of computing device is pretty much impervious to EMPs.

      Ex MP's?

      Jack Reacher may have something to say about that...

      --

      Fran
      :):):)
      1st 1st Poster of the new Millennium!

    2. Re:nuclear war resistant by mysidia · · Score: 1

      This company is probably the only one in the area that will still be operational in case of a nuclear war. that type of computing device is pretty much impervious to EMPs.

      Good thing too... post-EMP... clean water will be very hard to get; and in extraordinary demand, the ability to take dirty water and clean it, in order to survive. I can see a thriving business for liquid filters, even after all other businesses (including their suppliers) have shut down.

  59. I used to program those. by DutchUncle · · Score: 1

    Just sayin'. Bet lots of you wise-guys couldn't even figure out the manual.

  60. Autocoder as well by Anonymous Coward · · Score: 0

    Ran into a tools company in Texas that was still running an old Autocoder machine.

    When they first told us about it they said: "Well its not really Autocoder, we're just doing it under emulation." They lied.

  61. Re:I used to write programs in PL1/PLC on punch ca by Anonymous Coward · · Score: 4, Funny

    Thanks. That would have been real helpful 40 YEARS AGO!

  62. Re:I used to write programs in PL1/PLC on punch ca by kenaaker · · Score: 3, Interesting
    One of our standard pranks with punched cards was to drop a whole box on the floor in front of the submission bin, then gather them up, stuff them back into the box any old way, rearrange them a few times, shrug and put them in the bin.

    The key to the whole thing was the rubber banded few cards at the front of the box that ran IEHSORT(?) on the sequence numbers of the rest of the box.

  63. Re:I used to write programs in PL1/PLC on punch ca by kevmeister · · Score: 1

    Yes, that was SOP when I was in college, but it only helps. It is often possible to swap two cards an not make a visible "jag" in the line. Still, it works pretty well.

    I used to see people carrying multiple cardboard boxes of cards and was impressed until I learned that they were fairly simple COBOL programs. That is when I decided to never learn COBOL. Once saw a student crying after dropping a two tray COBOL deck on a windy day.

    --
    Kevin Oberman, Network Engineer, Retired
  64. Re:Slashdot refuses to stop abuse... apk by ttucker · · Score: 1

    I would downmod this, and trust me... I don't have any clue who you are.

  65. Conroe by Anonymous Coward · · Score: 0

    I lived in Conroe for 10 years. Being a developer means commuting for an hour and a half, or working at walmart.

  66. IBM's Lease-Only Strategy Still Pays Dividends by iluvcapra · · Score: 1

    Hope they aren't still renting that thing. I remember how hard it was to convince my grandma that she didn't have to keep renting her phone.

    --
    Don't blame me, I voted for Baltar.
  67. Re:I used to write programs in PL1/PLC on punch ca by K.+S.+Kyosuke · · Score: 1

    Drawing a diagonal line across the top of the deck is faster and lets you insert cards without having to resequence.,..

    Cool! I knew someone would appear with a useful tip I could use in tech job interviews!

    --
    Ezekiel 23:20
  68. Re:I used to write programs in PL1/PLC on punch ca by St.Creed · · Score: 1

    Cobol != punch cards.

    --
    Therefore, by the (faulty) logic you're using, you're just a cow with a keyboard - osu-neko (2604)
  69. Re:I used to write programs in PL1/PLC on punch ca by lgw · · Score: 3, Interesting

    I had a very annoying related bug in a mainframe program once that took me forever to get to the bottom of, where a text parser I had written was getting the weirdest errors. Eventually I discovered that somewhere in between the input text file on disk and my program was a virtual card punch and virtual card reader - each line of text went through as a virtual punch card for legacy reasons - and the virtual card punch was being ever-so-helpful and automatically punching sequence numbers in 73-80!

    --
    Socialism: a lie told by totalitarians and believed by fools.
  70. Re:I used to write programs in PL1/PLC on punch ca by mikechant · · Score: 2

    and then crying when they had try to reorder them to get their program to work

    That was the tears, later came the laughter when CA's mainframe Librarian product would state:
    "-END CARD MISSING - MAKE SURE DECK WAS NOT DROPPED"
    Even though it was reading from disk or tape...

    (This was about 20 years ago, As far as I know it still does this to this day)

  71. Can't they use an emulator!? by Anonymous Coward · · Score: 0

    Wouldn't it be easier to emulate this hardware? I mean, if anything went wrong with a hardware system like this, the business would cease to exist. Hire a college student to write an emulator (if there isn't one already) and get an emulator image that does the same thing this ancient hardware does. As an added bonus, the thing would probably run 1000x faster on a Pentium II, but that isn't the reason to emulate it. An enterprising programmer would be able to write a JCA layer and tie this system in with a modern web interface.

  72. Re:Slashdot refuses to stop abuse... apk by raydobbs · · Score: 1

    ...because the new owners of /. are to busy swimming through their money ala Scrooge McDuck to simply spend a little time moderating and deleting crap like this, despite being reported constantly.

  73. One of the biggest problems with IT is by Stone316 · · Score: 4, Insightful

    change for the sake of change. Let me say up front that i've worked in IT for over 15 years. Mostly as a DBA but I did network admin, hardware, development and OS.

    I keep hearing how the next version will do X, save Y amount of time and Z money. Won't require as many people to maintain it, etc. Yet it never seems to be the case. Vendors keep us on a continuous upgrade cycle because bug fixes aren't back ported or to get the latest security patches, etc. Managers, architects seem to focus more on resume building than a stable environment.

    I can't get any commitment for maintaining production but if i'm an hour late on a project task i'll have an army standing in my cubicle harassing me. I constantly hear developers wanting to go back to the basics because the new piece of software that's supposed to make their life easier isn't as stable.

    Yes, I love to play with the latest and greatest features but i'm not sure if from the companies perspective if its always worth the money. I have to say working in IT support can be a very frustrating and stressful job.

    --
    "Thanks to the remote control I have the attention span of a gerbil."
  74. Re:Slashdot refuses to stop abuse... apk by Anonymous Coward · · Score: 0

    I downmod you every chance I get mod points. Why?
    Because you post the same spam on every story. Also, I make sure I hit the report button every time I see your post. People are really tired of seeing the same insanely long posts from you and the other guy.

  75. Re:Slashdot refuses to stop abuse... apk by Anonymous Coward · · Score: 0

    Because they're hilarious as hell[1]

    1. For purposes of this post, Hell is funny. Dane Cook is not allowed in hell.

    Hell's Kitchen rules #42.

  76. Tabulating machine operations by Animats · · Score: 4, Informative

    I used all that gear in high school and high school summer jobs. I've wired panels for an IBM 402, an IBM 407 (the last of the electromechanical accounting machines and the best one), a 514/519 reproducer (a 519 has a mark sense reader option), and the 77 and 84 collators. And, of course, card sorters and punches. I was able to draw graphs with a 402 and generate poetry with an 84 collator. This is pushing the limits of those machines.

    The normal processing cycle for a sales/billing operation looks like this:

    • Transactions are punched on cards by a keypunch operator in a fixed format, with customer number, item number, quantity, and price each. Date is automatically punched, copied from the previous card.
    • Payments are also punched on cards in a similar way.
    • There's another deck of cards with three lines of address info on 3 cards, kept by customer number and address line number.
    • Finally, there's a deck of cards with the previous month's balance for each customer.
    • End of month processing begins by running the transaction cards through a 602A Calculating Punch, which can multiply. It multiplies quantity by price each and punches that info into the same card.
    • All the transaction cards are then sorted by customer number and date.
    • The decks are merged together with a collator, which has two input hoppers and four output hoppers. This matches numbers and checks sequence between cards. The assembled deck has, for each customer, three address cards, a previous-balance card, and all the transaction cards, payments first. Each block of cards for one customer thus contains the data for one invoice. The collator kicks out anything that doesn't match and stops if a deck is out of sequence.
    • The merged deck then goes to the tabulator, which is filled with preprinted invoice forms, usually multi-part carbons. The tabulator can add, subtract, and print, but not multiply. The invoices are printed. For this operation, a reproducer (a big card punch used to copy card decks) is cabled up to the tabulator with a cable about 2 inches in diameter. At the end of each invoice, the reproducer is triggered to punch a new previous-balance card for that customer, which will be used in the next billing cycle.
    • After a successful tabulator run, the merged deck is sorted in one pass to separate the name and address cards, which will be used again next month. The transaction cards go into storage as backup. The previous-balance deck is stored for use next month.
    • The fan-fold invoices go through a decollator to pull the carbons apart, and a burster to separate the pages for the copy that gets mailed. Then there's folding, inserting into envelopes, a pass through a postage meter, and mailing.
    • Other reports can be produced from the same cards. The previous-balance deck and the address deck are used to produce reports such as who owes how much, and which customers are buying the most.

    The card operations aren't that bad. All this stuff is slow, but automatic. The data entry is the labor-intensive part of the operation.

  77. Re:I used to write programs in PL1/PLC on punch ca by idontgno · · Score: 2

    True. But you have to admit, much COBOL was stored on and run from 80-column or maybe IBM 96-column) cards. Boxes and boxes of them, given the amazingly low code density (i.e., verbosity) of the language.

    I would venture here and now in the 21st Century COBOL is safely away from punched cards. However, my Air Force computer programming curriculum 30 years ago was 4 weeks (out of a 6-week class) of COBOL punched onto cards and run in batch mode. Rubber bands and the designated runner of the day to take the decks across the base (6 blocks) to the system room to be compiled and run.

    You absolutely DID NOT use the compiler to check your syntax when your code-compile-checkout cycle was measured in hours and you had two days to complete a project. Fanatical desk checking was the rule of the day. And since the instructors were competitive assholes and introduced an under-the-table prize for the first in the class to complete the project, so was sabotage of everyone else's decks. The runner of the day was a hell of a job... wonderful opportunities for bribery and also threats.

    Now get off my runway!

    --
    Welcome to the Panopticon. Used to be a prison, now it's your home.
  78. Seems silly, but,,, by Slugster · · Score: 1

    The main cost of getting off of old systems is usually converting data to a newer format. Is there any bargain-basement way of doing that here? I am thinking of something like, using an arduino connected to the 402's printer port to capture data to a PC, and then having the 402 "print" all the old data. The 402's blazing print speed of "100 (80-column) lines per minute" doesn't sound fast enough to bury an Arduino or even a gen-1 USB connection.

    I am not a professional programmer but I think if I knew the guy and liked him I might be willing to help for free--or at least, pretty darn cheap. The money involved has to be part of the issue here. Of course, maybe they only know how to create programs on the 402.... So what they'd really want is a 'virtual' 402 program, where they could change reports by 'wiring up' new on-screen programming boards. :>D

    1. Re:Seems silly, but,,, by Anonymous Coward · · Score: 0

      You're overengineering it. You get the cards, go to the nearest high-capacity ADF scanner, and just scan them in. Once scanned, it's reasonably easy to do optical alignment and recognition of the punch holes. You can temporarily glue a piece of black background in the scanner so that the punched holes are easier to detect.

      The tabulation, collation and reporting programs can be rather easily implemented from scratch. They are not very complex.

  79. US GOVT by Anonymous Coward · · Score: 0

    Worked for the GOVT back in the late 80s, early 90s at the MEPS Center in Cleveland..

    At that time they were still using reel to reel storage and punch cards!

    Military Intelligence at its best :)

  80. Re:I used to write programs in PL1/PLC on punch ca by macbeth66 · · Score: 1

    Really? We used to drag a marker across the top of the cards in a diagonal line from front to back. It was immediately obvious which cards were out of order.

  81. Re:I used to write programs in PL1/PLC on punch ca by rickb928 · · Score: 1

    And that, audience, is why sort routines were so popular back then.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
  82. Re:I used to write programs in PL1/PLC on punch ca by greyparrot · · Score: 1

    That is what I meant.

  83. Re:I used to write programs in PL1/PLC on punch ca by Bacon+Bits · · Score: 1

    It did originally.

    The reason COBOL required indention originally (and the reason it generally no longer does) is because it was necessary for punch cards. The indention moved the holes to where the card parser could identify codes correctly.

    --
    The road to tyranny has always been paved with claims of necessity.
  84. Re:I used to write programs in PL1/PLC on punch ca by Anonymous Coward · · Score: 0

    everything could equals punch card, my father did some FORTRAN on those cards....

  85. Im all for saving what works by Anonymous Coward · · Score: 0

    But at some point you do have to move on. They have long since past this point. If they have a failure, they are screwed and will have to start from scratch, with a deadline looming over their heads.

  86. I used an IBM 403 in ~1970 by billstewart · · Score: 1

    I used an IBM 403 to run a Boy Scout mailing list in the early 1970s. It's the successor to the 402, and has 133 vertical bars with the character set on them, which slide into position based on the program and punch card data and then get whacked with a hammer to print. The kids and most of the adults weren't allowed to mess with the plug board on the side, but we could do anything we wanted with the paper-tape driver and the keypunch and card sorter, so there was still a fair bit of hacking room. (There was one adult who knew what he was doing with the wires.)

    Later, when I got to high school, the girls in the secretarial-track training got taught how to actually program the things (I think; they definitely learned keypunch typing and drum programming, but I think they also got to do the wires.)

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:I used an IBM 403 in ~1970 by kermidge · · Score: 1

      Good story, Bill, I liked reading it.

      Thing is, though, I really like your sig. I'd read something on compression-only CPR, but the linked story was a good refresher and reminder both. The dramatic increase in survival is even more so when one stops to think each percentage increase is that many more real live humans walking out of hospital.

      I think it's a good idea to try to spread the word.

    2. Re:I used an IBM 403 in ~1970 by billstewart · · Score: 1

      Thanks! I didn't have anything funny to say, and the previous sig was post-election snarkiness which had gotten dated, so I figured I'd do something useful with the space :_)

      --

      Bill Stewart
      New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  87. Have to say, it's kinda cool. by Qbertino · · Score: 2

    I have to admit, that actually *is* sorta cool. Imagine, you can probably repair a bit on that computer with a well-bent paperclip. When everything goes down the drain, this thing will still be up and running, maintainable and you will be able to build your own spare parts for it using a regular toolbox and a soldering iron.

    Then again, my very first computer, a PC 1402 Sharp Pocket Computer from 1986 with cashstrip printer is probably like a bazillion times faster and more powerfull than that thing. It would probalby take less than two weeks to replace the entire workflow with a single cheap-ass current programmable calculator and you could add some features along the way. That makes it quite strange too. Cool, but very strange.

    My 2 cents.

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:Have to say, it's kinda cool. by mysidia · · Score: 2

      I have to admit, that actually *is* sorta cool. Imagine, you can probably repair a bit on that computer with a well-bent paperclip.

      The trouble is... that being broken, and getting 'stuck' at an incorrect value, might not necessarily be detected, as quickly as a blue screen would be detected...

      Punch card devices have this problem of verification, where a card could get lost, misread, or incorrectly punched

      So you need additional error checking at higher layers, that a PC would take care of at a lower level, in the operating system... or in the memory (ECC technology on the hard drive RAID, CPU, and system RAM; checksums in data transmission and storage, to provide tamper resistance; audit logs, regarding access to data and changes....)

  88. "Overclocking" these is apparently possible. by Anonymous Coward · · Score: 0

    a) I am a literal product of IBM. My parents met while working for Big Blue in the late 60's.

    b) I emailed my father with this link, and here is his reply:

    "Actually, I really did know how to wire ("program") the 402. And I probably still could if necessary. It was so easy, but a little complicated. If you made an error, you just re-ran the deck of cards.

    A little known fact was that you could make it run faster if you used a rubber band in a special pulley location.
    "

  89. EAM equipment and Tab Cards.. by Anonymous Coward · · Score: 0

    That's standard Electronic Accounting Machinery and punch cards.. "Tab cards" if you need to order them..
    15 years ago, you could still buy standard 80 column cards by the case (couldn't buy a box of 2000, had to buy 5 boxes), and I suspect someone still makes them and sells them. There's a lot of old S/360 machines around of one sort or another.

    And, I think that's an 029 keypunch (based on the switches above the keyboard), which *was* state of the art in the early 70s, as opposed to the earlier 026. A quick check shows that the 029 was introduced in the mid-60s along with S/360. I used to have to use multipunch in 1973 to get 029 codes for parenthesis and such in FORTRAN programs when using a 026 punch, which is what my HS had. (some motor memory things you never forget.. The last time I used a keypunch was at UCLA in 1979, and I wound up sitting in front of one in around 1997 needing to punch some cards. Reached under to turn on the power, hit the toggle switch above the keyboard for the feed to get the first card in, and blasted away like I had never stopped using it. Truly an odd feeling.)

    see, for instance, http://www.youtube.com/watch?v=iXLfiAvkbyg that's a 129
    http://www.youtube.com/watch?v=QSNox5iqNmU is an 029

  90. Re:I used to write programs in PL1/PLC on punch ca by Anonymous Coward · · Score: 0

    Was that luggage tracking by any chance?

  91. Slide rules rule! by Anonymous Coward · · Score: 0

    What is this calculator thing of which you speak? 15C? Is that a Friden model number?

    Be a man or woman instead of a child and whip out your slip stick and calculate like a pro.

  92. Re:I used to write programs in PL1/PLC on punch ca by jonr · · Score: 1

    It's a shame that I don't have any mod points...

  93. Re:Slashdot refuses to stop abuse... apk by Pseudonym+Authority · · Score: 1

    Lurk more. Shit was never deleted before. Go take a look at old GNAA shitposts from 2001 if you don't believe me. The only post I've ever seen deleted was one with a link to child porn a few years back, and one due to a DCMA take down (there is an article about that, but I'm too lazy to find it).

    I, for one, am glad they don't take it upon themselves to censor the place because a few idiots who need to be babysitted can't figure out how to hide -1 posts.

  94. Re:I used to write programs in PL1/PLC on punch ca by mjwalshe · · Score: 1

    PL/1 yay I worked on a system in the 80's the used PL1 (and FORTRAN) on PR1ME do do map reduce for the billing system used for dialcom systems in the UK

  95. Re: I used to write programs in PL1/PLC on punch c by Peter+Simpson · · Score: 1

    Sort routines, my ass. 083 sorter ftw!

  96. Wait until the accountant retires... by Anonymous Coward · · Score: 0

    Buy cheap laptop with Quickbooks. Seriously, too much is made of "this business's needs". They are a global entity with thousands of products. They're not that special. Fuck.

    1. Re:Wait until the accountant retires... by plover · · Score: 1

      They sound like they are completely dependent upon these cards, and would have to expend at least a few hours of effort to replace them. But overall, converting would probably cost less than two service calls from the card punch guy, and would pay for itself in not many weeks.

      On the other hand, they operate a museum piece and are making the news as a result. Free advertising. Lighten up.

      --
      John
  97. Re:I used to write programs in PL1/PLC on punch ca by Anonymous Coward · · Score: 0

    probably iebsort

  98. Re:I used to write programs in PL1/PLC on punch ca by mark_reh · · Score: 1

    That's when I was there! Maybe we ran into each other back then.

  99. Re:I used to write programs in PL1/PLC on punch ca by kermidge · · Score: 1

    Sure, we used punch cards for the two Fortran-for-engineers classes I took in '66-67. We coded Fortran IV and Fast Fortran using "official Fortran coding forms."

  100. It works when the requirements are set high ... by dbIII · · Score: 1

    It works when the requirements are set high for some artificial reason, for instance to reduce numbers of applicants to a popular course or school, and the actual background required to do the course is less than demanded. Of course that creates a lot of ill felling where some people that couldn't get in via general entry are allowed in, but if you have a limited number of places and want the next generation of doctors or whatever to be spread all over the country instead of just in the affluent parts of major cities then admission has to be a bit more complex than just the few with the highest test scores. Sucks for those that miss out but better overall.

  101. no so by frovingslosh · · Score: 1

    In a small company like that? The head accountant who was there for forty years could certainly make the call to upgrade the system if she wanted to. At the most she might need the OK of the boss that she is on a first name basis with. But simply saying to the boss, "we really need to update this ancient equipment, it will save up a lot of money in just a few years" should be enough. No, the only thing that makes much sense is someone standing in the way of the logical choice. And if it is the boss he isn't being well advised.

    --
    I'm an American. I love this country and the freedoms that we used to have.
  102. Re:I used to write programs in PL1/PLC on punch ca by Anonymous Coward · · Score: 0

    Yup... CDC 6600 assembler made no sense at all until you realized or were told that the 6600 was designed to run FORTRAN fast. Then the light was blinding.

  103. I'm getting old... by dumb+kid · · Score: 1

    One of my first engineering jobs was programming an old milling machine. You wrote the program code in an editor on a computer, then had it output on a roll of punched paper tape. The code was punched into the tape transversely, in simple 8-bit ASCII. Hanging chads would really ruin your day.

    My big contribution was a program that could punch a human readable header onto the tape. Written in the finest QBASIC.

    --
    - Never attribute to malice that which can adequately be explained by stupidity.
  104. Re:I used to write programs in PL1/PLC on punch ca by Anonymous Coward · · Score: 0

    You mean your stacks of blank cards didn't come with the Rubber Band(TM) technology attached?

    Can everyone stop using this retarded proxy for "I'm so leet and old skool" retarded retardedness? Try to at least move to more sophisticated stupidities! You are boring.

  105. Old Mainframes by Anonymous Coward · · Score: 0

    In the mid 70's Josten's, of school ring and caps/gowns fame used a Honeywell Octal Tape Operating System Mainframe for Payroll, and an IBM 360 - 40 with 64k core for all other DP. They also had a 360-30 to create punched tape to control the machines that made the rings. Honeywell SSEC used a Fairchild with cards full of reed relays for substrate (wafer) measurements in the mid 70's, and to 'fix' it we would open the card drawers and fan the cards, USUALLY unsticking a stuck relay. As late as 2000, Ryobi was using a DEC mainframe for engineering MRP/ ERP. Then there were the old UNIX boxes and the 1200 BAUD modems (an upgrade) with audio coupling - lol

  106. Re:Fix the thing? by Anonymous Coward · · Score: 0

    With equipment like that, you're going to need an old grey-bearded mechanic on-site daily to keep things running. I supported a microfilm lab a really long time ago that processed aperture cards for distribution. They had a room full of antique IBM "unit record" machines and an old support engineer overhauling one machine or another every day. And that stuff was fossilized back in the 70's.

  107. Re:I used to write programs in PL1/PLC on punch ca by techsimian · · Score: 1

    punchcards + hurricane == funny