There was a single Windows 95 PC at US Bank that ran the machine that cut open the mail and made an image of the checks folks mailed in for bill payments. It wasn't allowed on the network, it was stand alone.
There was a single Windows 95 PC at US Bank that ran the machine that cut open the mail and made an image of the checks folks mailed in for bill payments. It wasn't allowed on the network, it was stand alone.
There was a single Windows 95 PC at US Bank that ran the machine that cut open the mail and made an image of the checks folks mailed in for bill payments. It wasn't allowed on the network, it was stand alone.
I believe this. US Bank is the gov contractor for CCs and it's the absolute worst interface I've ever seen. I don't know why or how it takes so long for transactions to post...when on my own personal card I see it pretty much instantly. I would never in a million years recommend US Bank based on their CC stuff.
I believe this. US Bank is the gov contractor for CCs and it's the absolute worst interface I've ever seen. I don't know why or how it takes so long for transactions to post...when on my own personal card I see it pretty much instantly. I would never in a million years recommend US Bank based on their CC stuff.
from personal experience The Federal Reserve still does all its transactional processing on IBM Mainframes. We added an interface to eliminate the original tape drives (I worked for Grau Data at the time) in 2000
Answer (1 of 3): There are many reasons to it, let me try to explain to my best knowledge. 1. When Banking sector adapted computer technology, the only available processing system and programming is Mainframe. So, almost all the core banking systems were developed using Mainframe. 2. Mainframe i...
Answer (1 of 3): There are many reasons to it, let me try to explain to my best knowledge. 1. When Banking sector adapted computer technology, the only available processing system and programming is Mainframe. So, almost all the core banking systems were developed using Mainframe. 2. Mainframe i...
It's not so much an issue with the technology (it is still working), the issue is the lack of support. US Bank had internal incentives to learn Cobol trying to get the next generation of folks at least up to speed. It hasn't been taught in schools in over 30 years. And if you have ever done anything with a mainframe, it isn't a cool graphical interface.
It's not so much an issue with the technology (it is still working), the issue is the lack of support. US Bank had internal incentives to learn Cobol trying to get the next generation of folks at least up to speed. It hasn't been taught in schools in over 30 years. And if you have ever done anything with a mainframe, it isn't a cool graphical interface.
Thanks for making me feel ancient.
I used to code COBOL and a little RPG3 on the big 'puters and xbase (mostly Clipper compiler) on the PC's after they became a bit more ubiquitous. Gave up coding for playing with routers and firewalls. After a dozen years retired, I would be of absolutely no use anymore. And I am perfectly ok with it; I hated chasing damn periods anyway.
Thanks for making me feel ancient.
I used to code COBOL and a little RPG3 on the big 'puters and xbase (mostly Clipper compiler) on the PC's after they became a bit more ubiquitous. Gave up coding for playing with routers and firewalls. After a dozen years retired, I would be of absolutely no use anymore. And I am perfectly ok with it; I hated chasing damn periods anyway.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.