[email protected] (John P. Baker) writes: > Give that staggering number of financial transactions processed on a daily > basis, over 90% of which is done on large-scale IBM mainframes, is it not > strange that you have never heard of a mainframe virus? IBM RAS and IBM > Security (whether implemented via IBM RACF, CA ACF/2, CA-Top Secret > Security, or some other External Security manager (ESM)) is what keep these > systems running.
the original mainframe tcp/ip implementation was done in pascal and never experienced any buffer length related problems ... some past posts modifying mainframe tcp/ip so that instead of taking 3090 processor to get 44kbytes/sec ... a small part of 4341 processor got channel speed thruput http://www.garlic.com/~lynn/subnetwork.html#1044 Majority of of internet-related exploits and vulnerability during the 90s were buffer-length related ... associated with C language programming enviornment .... misc. past posts http://www.garlic.com/~lynn/subintegrity.html#buffer that started to shift in this decade to transfer of network files that were executed containing malicious code (either automatic execution or social engineering prompting execution). I've done some word occurance analysis of internet theat & vulnerability reports ... and advocated that the centers asked for categorization ... since the reports have been free-form making it more difficult to categorize. there were some of this kind of viruses in the 70s & 80s on mainframes, both the internal network ... some internal network past posts http://www.garlic.com/~lynn/subnetwork.html#internalnet and bitnet/earn http://www.garlic.com/~lynn/subnetwork.html#bitnet lots of the financial stuff grew up in mainframe batch ... some past references/discussions (this from linkedin greater ibm) http://www.garlic.com/~lynn/2009o.html#51 8 ways the American information worker remains a Luddite and slightly older from year ago http://www.garlic.com/~lynn/2008p.html#27 Father of Financial Dataprocessing some amount of the transactions starting moving "online" during the 70s & 80s ... but would only be partially be performed ... with the completion of process still being performed in mainframe batch (in "overnight batch window"). In the 90s, there were several large financial institutions that worked on leverage massive numbers of parallel "killer micros" to implement "straight through processing" for these online transactions (actually going to comletion). The issue was growing business and growing global business was putting extreme pressure on the "overnight batch windows" (more work & decreasing size). However, the parallelization technology they were using added two orders of magnitude overhead (compared to the mainframe batch) ... completely swamping any anticipated thruput increase (several projects were billions into the efforts before doing any serious look at the speeds&feeds and then declared success and abandoned the efforts). On the other hand there was a lot of mainframe clustering, continuous availability and disaster survivability done in the 70s and early 80s ... that never made it out as product. For instance at the hillgang user group meeting yesterday ... they had presentation about new single-system-image cluster support for z/VM. We had done that in the mid-to-late 70s for the HONE system (world-wide online marketing and sales support) ... and in the early 80s, for US HONE datacenter in california, it was replicated in Dallas and then Boulder (three site, load-balancing, and fall-over). misc. past posts mentioning HONE http://www.garlic.com/~lynn/subtopic.html#hone Long ago and far away, my wife had been con'ed into going to POK to be in charge of loosely-coupled architecture. She was responsible for peer-coupled architecture ... but because of very little response at the time (except for IMS hot-standby), she didn't stay long. http://www.garlic.com/~lynn/subnetwork.html#sharedata Later we started HA/CMP product with rs/6000s for both availability and cluster scaleup: http://www.garlic.com/~lynn/subtopic.html#hacmp reference to Jan92 meeting on cluster scaleup http://www.garlic.com/95.html#13 and some old email http://www.garlic.com/~lynn/lhwemail.html#medusa however, within a month of the Jan92 meeting, the cluster scaleup was transferred, we were told we couldn't work on anything with more than four processors ... and then there was announcement for (JUST) the numerical intensive marketplace: http://www.garlic.com/~lynn/2001n.html#6000clusters1 http://www.garlic.com/~lynn/2001n.html#6000clusters2 along with numerous others in these old posts: http://www.garlic.com/~lynn/2001n.html#70 http://www.garlic.com/~lynn/2001n.html#83 While we were out marketing ha/cmp, I coined the terms geographic survivability and disaster survivability (to differentiate from disaster recovery)I was also asked to write a section for the corporate continuous availability strategy document ... but it got pulled after both Rochester and POK complained that they couldn't (then) meet the objectives. misc. past posts on availability http://www.garlic.com/~lynn/submain.html#available not long after we left, we were asked to consult with small client/server startup that wanted to do payment transactions on their server; the startup had also invented this technology called SSL they wanted to use ... it is now frequently called "electronic commerce". Part of that "electronic commerce" effort was something called a "payment gateway" (we sometimes call the original SOA) ... which acted as gateway between internet webservers and the payment infrastructure. That original implementation leveraged lots of the HA/CMP technology ... and included lots of stuff we worked on for internet avavailability and security. misc. past payment gateway posts http://www.garlic.com/~lynn/subnetwork.html#gateway -- 40+yrs virtualization experience (since Jan68), online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
