News for hackers. Stuff that matters.
Re:Banks should let COBOL die by mavhc on Wednesday April 26, 2017 @09:47AM (#14202865)
If I were a bank I'd start a new bank, in Not COBOL, and put all my new customers on that. Then after 10 years offer to move people still at the old to the new bank, to get new offers.
Re:Banks should let COBOL die by potato_mOWX2EVX on Wednesday April 26, 2017 @10:20AM (#14203163)
You forget the old customers have credit contracts that last 50 years which have business rules, implemented in mainframe software, which no one understands or knows.

You can't migrate that way. An Insurance company can do that (contracts usually last 1 year) but Banks can't.

Re:Banks should let COBOL die by mavhc on Sunday April 30, 2017 @12:48PM (#14232428)
Right, I didn't put in "and the few remaining accounts that can't be moved can stay on the old system"

It was more a suggestion of how to move to a new system at all.

What happens if the bank closes before those 50 years?

Re:Banks should let COBOL die by kristianc on Wednesday April 26, 2017 @09:58AM (#14202967)
How do you message to your existing customers that you're holding their life savings on fragile 1970s tech?

Also, you'll still have to write wrappers for the old tech (iPhone apps which access the COBOL core) in order to maintain feature parity with the other banks.

Re:Banks should let COBOL die by coldtea on Wednesday April 26, 2017 @10:03AM (#14203002)
>How do you message to your existing customers that you're holding their life savings on fragile 1970s tech?

You mean "battle tested for 40+ years, totally solid 1970s tech"?

If anything, it's any crap they'd write now that would be MORE fragile.

Re:Banks should let COBOL die by kristianc on Wednesday April 26, 2017 @10:15AM (#14203124)
You're thinking like an engineer.

You're right, of course, but the public is trained to trust the latest and greatest.

If 'battle tested' was the most salient selling point we'd be on Series 60 or QNX phones.

'We're putting new customers on the latest technology and keeping existing ones on our old systems' is not going to be an easy thing to message to the general public.

Re:Banks should let COBOL die by GFischer on Wednesday April 26, 2017 @05:18PM (#14207086)
If 'battle tested' was the most salient selling point we'd be on Series 60 or QNX phones.

Actually, there are more Series 40 and Symbian phones sold today than iPhones - 350 million to 200 million (India / rest of Asia, Africa and Latin America are the main buyers). Many people here still miss the old Nokias. Of course, Android is the new Series 60.

http://gadgets.ndtv.com/mobiles/news/nokia-sold-35-million-f...

http://tech.firstpost.com/news-analysis/india-smartphone-shi...

Re:Banks should let COBOL die by Bluestrike2 on Wednesday April 26, 2017 @10:36AM (#14203319)
The code is from the 1970s, but a lot of the hardware has been replaced over the years. IBM has been pretty aggressive about maintaining compatibility options because they're fully aware of just how much legacy code their customers need to use. And when it hasn't been, maintenance has usually been pretty well-handled. Those machines were usually built to last. There's even a company that was still using an IBM 402 accounting machine as of 2012.[0] And there's plenty of military hardware using 70s/80s computer tech.

But I don't see this ever really coming to consumer attention. They're never directly--or visibly--interacting with old mainframes. From their perspective, they're using the newest tech. The mainframe in the background doesn't exist to them. If they even think about it, it's just magic. The closest you might have gotten to the public talking about legacy systems was probably the healthcare.gov debacle, when a number of news articles mentioned integration issues as being an problem. Those were big issues in themselves, but they weren't the main problem behind the site's development nor were they ever a major discussion point.

0. http://www.pcworld.com/article/249951/computers/if-it-aint-b...

Re:Banks should let COBOL die by kristianc on Wednesday April 26, 2017 @10:54AM (#14203464)
Here in the U.K. at least, banks using legacy systems is usually mentioned when a bank has an outage / ATMs failing.

The canonical example when it comes to UK banking is the RBS outage, which meant that customers could not make payments for three weeks. RBS was hit with a £56m fine for that.

http://www.telegraph.co.uk/finance/newsbysector/epic/rbs/112...

Re:Banks should let COBOL die by insomniacity on Wednesday April 26, 2017 @12:56PM (#14204769)
And this right here is the reason that banks can't just sit on their ticking timebombs.

Another commenter says there's no incentive for managers or execs to stick their necks out, but £56m is quite an incentive.

Re:Banks should let COBOL die by Bluestrike2 on Wednesday April 26, 2017 @05:58PM (#14207420)
Not really, because the risk of such a fine is ridiculously low. From reading up on the incident, it seems like it was more a matter of a software update rather than specifically the use of legacy code that caused the incident. UBS was fined because the outages were unacceptable to consumers and regulators and because "the potential for problems had been raised in an internal audit two years before the incident took place in 2012"[0] and nothing was done.

One could argue that legacy code makes that more likely because of unseen factors that predate the people actively working on it. It's hard to miss a landmine, after all, if you don't have any clue that it's there. But while a rewrite might eliminate that specific risk, it does so by inviting a lot of new ones to replace it. In some ways, the risks are probably greater as you need to figure out possibly decades of business logic and then re-implement everything. From a business decision perspective, the existence of legacy code on its own is an insufficient argument on its own. After all, the problems inherent in legacy code will eventually surface yet again in another 10-15 years anyhow. The better solution in most cases would be to identify specific problems and determine what can be done to hedge against them.

0. https://www.theguardian.com/business/2014/nov/20/royal-bank-...