Slashdot Mirror


UK Government Department Still Runs VME Operating System Installed In 1974

Qedward writes: The UK government's Department for Work and Pensions is on the hunt for a new £135,000-a-year CTO, with part of their annual budget of £1 billion and responsibility for DWP's "digital transformation" to oversee the migration of the department's legacy systems which are still run on Fujitsu mainframes using the VME operating system installed in 1974.

41 of 189 comments (clear)

  1. Well, no one will hack in by jfdavis668 · · Score: 2

    Hackers probably couldn't even find a manual for one.

    1. Re:Well, no one will hack in by Anonymous Coward · · Score: 3, Informative

      If they can't, then they have no Google-Fu....

      http://www.fujitsu.com/uk/services/application/application-development/vme/

  2. Modern Technology by Galaga88 · · Score: 4, Interesting

    How many modern systems can anybody imagine still working and apparently doing what we need them to 40 years from now?

    1. Re:Modern Technology by jbolden · · Score: 3, Interesting

      Give me what that system cost in 1974 inflation adjusted dollars and I'll be happy to flip out a modern system every year. Using cheap less durable components with redundancy is a better strategy. I live in a 1830s house so I get the advantages of good quality construction. But if I were building a house I'd use 2014 cheap materials.

    2. Re:Modern Technology by jbolden · · Score: 3, Informative

      Absolutely true. Today's structures will not stand the test of time. Even the concrete we use is steel reinforced which means in 2 centuries without ongoing care, it will be dust. Though Jerusalem where limestone is dirt cheap and still an excellent building material is an interesting counter example to that global trend towards throw away buildings.

    3. Re:Modern Technology by TheRaven64 · · Score: 5, Insightful

      I am always amazed how buildings constructed thousands, or even hundreds, of years ago are still standing although often in a state of disrepair due to neglect

      That's what's known as survivor bias. The only examples you see of thousand-year-old buildings are the ones that didn't fall down. The ones that collapsed within a decade are long forgotten.

      A modern-day castle might survive a century whereas the castles throughout Europe remain or at least remnants of their existence survive to this day

      And yet, in the village where I grew up, and near countless other villages in Britain, there was a hill with a raised mound on top, which was the only remaining evidence of the castle that stood there 900 years ago.

      --
      I am TheRaven on Soylent News
    4. Re:Modern Technology by TheGratefulNet · · Score: 4, Interesting

      http://www.eevblog.com/forum/t...

      nice old classic tek test gear. highly in demand by collectors and those who appreciate good old fashioned engineering and build quality. the last of the 'repairable' tek scopes, pretty much (and even this is borderline repairable, with many custom chips).

      still, a few new caps, a new battery backed nvram module and you have another 20 or 30 yrs left on this scope.

      search that same forum for other old test gear (power designs (brand) power supplies are also built like tanks and run forever. I have 4 of them at home in my lab and they date from the mid 50's to early 60's. still hold their precision and would cost $5k to $10k today if you could even buy them.

      I have audio gear that I personally built in the 70's and 80's that still runs fine (hafler amps, etc).

      today, its hard to find things built to last, but it USED to be the norm "before your mother was born", so to speak.

      --

      --
      "It is now safe to switch off your computer."
    5. Re:Modern Technology by TWX · · Score: 2

      We've seen screencaps of 14-year uptimes on Cisco 2500-series Routers before, so I'd bet that a lot of networking equipment, if high quality to begin with, could make it that long, assuming that it's still doing what the users need.

      --
      Do not look into laser with remaining eye.
    6. Re:Modern Technology by gstoddart · · Score: 5, Insightful

      Give me what that system cost in 1974 inflation adjusted dollars and I'll be happy to flip out a modern system every year.

      Sorry, I'm calling complete and utter bullshit.

      I've worked on enough legacy systems to know they didn't start off with some astronomical budget. They built it based on a set of requirements, coded it in house, and then it gradually expanded over many years of service.

      Mainframe applications aren't sexy or glamorous, they're built on relatively simple interfaces, and slowly expand in scope over time.

      They keep running because eventually they're woven into fabric of every other business process you have until they become something you can't trivially get rid of ... because every other damned thing relies on it even if it isn't obvious to the user. You end up having to replace everything

      My experience with migrating from legacy apps says you'd churn out a half asses solution, which isn't compatible with the existing stuff, and which can't be made so, and which would eventually be abandoned as untenable.

      You'd produce some solution which might be good if it didn't depend on throwing away every other system which touched this.

      The vast majority of people who claim they could produce a functional replacement for legacy software in a short period of time have never been involved in that kind of process.

      If it was easy, they'd have replaced it by now.

      The problem with looking for a "track record of transitioning a large enterprise from ageing mainframe technologies to next generation web, social, mobile cloud, Big Data and deep learning technologies" is that it's a set of requirements written by idiots who don't want to replace the system, they want something completely different which will involve re-tooling everything else that touches this existing system.

      Put your money where your mouth is, apply for the damned job.

      --
      Lost at C:>. Found at C.
    7. Re:Modern Technology by mrbester · · Score: 5, Insightful

      Because, as a student, if you hit it and it breaks you did something dumb and reduce the number of units for the class to use. However, as an instructor, if he hits it and it breaks, it was due for replacement.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    8. Re:Modern Technology by csnydermvpsoft · · Score: 5, Insightful

      What basis do you have for the claim that we "couldn't even begin to recreate" those structures? There are certainly some ancient structures for which we haven't figured out how they were constructed with the technology available at the time, but nothing that we couldn't reproduce with today's technology.

      The sticking point isn't technology—it's economics. A large portion of recent development has been around cost-effectiveness. This is why we're able to have so many more material possessions, even in the face of stagnant wages (for most classes). Of course, many (including myself) would argue that we've gone too far in this direction at the expense of durability, but that's an economic choice we've made. Look hard enough, and you can find any product that meets your durability specifications—if you're willing to pay the higher price.

      That being said, I do agree with the sentiment that there is more than survivor bias at work. My house was built in 1916, and has an unusually open floor plan for its age. Lacking CAD, the builders accomplished this by massively overbuilding—the floor joists (with are already quite thick) rest on beams comprised of four 2x10's laminated together. Despite its age, this house feels more solid than just about any other wood-framed building I've been in. I have no doubt that if it were placed alongside a newly-constructed house and both left to nature, that the 99-year-old house would remain intact longer.

    9. Re:Modern Technology by Ed+Avis · · Score: 2

      I think you're missing the point. It is not about hardware durability. The original hardware installed in 1974 has long since been replaced (probably several times over). It is the software that costs money over the long term - hiring programmers to maintain it. And it is the software that is the reason the system hasn't been replaced with something else.

      --
      -- Ed Avis ed@membled.com
    10. Re:Modern Technology by gstoddart · · Score: 4, Insightful

      Well, the problem happens when some technology evangelist or manager who doesn't know a damned thing about the existing system claims it's easy to migrate it to modern tools.

      And neither the customer, nor the guy saying it's easy, has the barest clue about just how many other things depend on that system, and nobody can fully enumerate the functionality and corner cases.

      And then you end up trying to shoe-horn a purpose built piece of software which has ran fine for decades into a modern paradigm, and realize you are failing utterly.

      Because the modern tools usually simply can't accommodate all of the rules and logic in that system. They can't be cajoled into having enough flexibility, or simply can't do the same task.

      People consistently underestimate just how well these systems do their job, and just how many little corner cases and integration points have been woven into them over the years. The platform is no longer elegant, or easy to explain, but it just keeps working. But dozens of other things rely on it, and if you change the underlying thing you rebuild everything else.

      I've been on several projects trying to replace stuff built in the 60's and 70's -- and I wouldn't go near another one without very loudly saying how much risk is involved. Hell, even a system which has been around only since the 90s might be non-trivial to migrate away from -- precisely because in the 90s people were still building much more purpose-specific software.

      It's a catch 22 ... they get increasingly difficult to maintain, but they sometimes are impossible to replace.

      As I said, if it was easy to replace these systems, it would have been done already. Discovering just how difficult this can be has been the downfall of many a naive person who claims it's an easy thing to do.

      --
      Lost at C:>. Found at C.
    11. Re: Modern Technology by thetoadwarrior · · Score: 3, Insightful

      That's BS. There are plenty of homes missing now from that era and castles that went to shit too. Saffron Walden in the UK has a castle but you'd probably not notice since it's just a small pile of remains. Famous structures like Ely Cathedral still stand because it gets repaired on an annual basis. There are plenty of bits on it that are only a couple years old at most. They've even got scaffolding all up the side it right now. They've also been digging at the foundation. You underestimate how much effort goes into keeping old buildings going. I've lived in Victorian homes and new build and the maintenance costs are like night and day. My current home might not be around in 500 years but I don't care and why should it? It's not special and there will be far better ways to build homes in that time. Maybe by then all those old Victorian homes will finally be rid bad technology like lead pipes.

    12. Re:Modern Technology by jeremyp · · Score: 4, Interesting

      Without knowing *why* the castle is gone, I have no idea what your point is.

      Usually, if it was a stone castle, the building materials were robbed out to make new dwellings. The reason that people could do that is because the owners abandoned them as being shit places to live.

      With buildings, as with other man made items, technology moves on. Generally speaking, a house built now will be more comfortable, easier to heat and more suited to modern life styles than a house built 50 years ago. Who cares if the old ones fall down? If you are going to knock it down and replace it with something better, money spent making it last a millennium is wasted money.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    13. Re: Modern Technology by Blaskowicz · · Score: 2

      What I recently learned about is how asian temples at least in Korea are teared down and rebuilt every 20 years to 40 years (I don't remember and I don't know if it varies). Wooden parts fit together (no nails, bolts etc.)
      There is not the western obsession with preserving extremely old buildings and parts of building in their original state for as long as possible, but instead cyclical continuity like the fable of the hammer whose head and handle were replaced mutiple times each.

    14. Re: Modern Technology by cnkurzke · · Score: 2
      The only "permanent structures" we will leave to our next millenium ancestors will be:
      1. trash dumps
      2. nuclear powerplants (will those be the equivalents of castles and cathedrals of the 31st century? Oh, look at those complex curved titanium barrels they were able to produce with their ancient primitive tools!!)

      Consider this, When we talk about nuclear storage facilities, we intend to build structures which will last tens of thousands of years. Good luck.

    15. Re:Modern Technology by jbolden · · Score: 2

      I and the GP were talking about the cost of the mainframe not the application layer at all.

      As for legacy conversions click on my link I've done dozens of them and quite successfully. Absolutely capturing business rules is a big deal. And frankly most mainframe applications were labor inefficient in their construction. That doesn't mean $100m worth of programming can be replaced for $1m but it can be replaced for $10m.

    16. Re:Modern Technology by disambiguated · · Score: 2

      Even given the short(er) lifespan of modern buildings, most of the buildings we tear down are torn down while they are still structurally sound and useful. They just aren't useful enough. We tear them down because they are not the building we want on that site any more. For example, consider single family houses in the middle of a crowded city. They don't have modern energy efficiency, safety or ease of maintenance, and they don't house enough people to justify the forgoing the alternative uses of the land they are on. A few rich people will live in them anyway, an we keep a few around as historical sites, but the rest we tear down to build something we want more.

      Computers are even worse. If we wanted to, we could build a smart phone that would last a century but nobody wants that. It won't even be 5 years before we won't want the phone we have, because there will be better ones by then. Centuries-old buildings were built in a time when technology and society itself were relatively static. With today's pace of technological and societal change, it doesn't make sense to build much of anything to last that long because what we will want in a few hundred years or even a few decades is unknowable. Forget about thousands of years. Anything we build today is not going to be what we want anymore long before that. I suppose that some day, when the pace of change stabilizes, we will start building more permanent things again. In the mean time, there's a balance to be struck between construction/manufacturing costs, and what we expect the thing's useful lifespan to be.

    17. Re:Modern Technology by clawsoon · · Score: 2

      That's a great point. The evolution of life has worked the same way. There are some proteins which are interacted with and depended on by so many other proteins that changing them would be catastrophic; I happened to be reading about tubulin and actin today:

      The likely explanation is that the structure of the entire surface of an actin filament or microtubule is constrained because so many other proteins must be able to interact with these two ubiquitous and abundant cell components. A mutation in actin that could result in a desirable change in its interaction with one other protein might cause undesirable changes in its interactions with a number of other proteins that bind at or near the same site. Genetic and biochemical studies in the yeast Saccharomyces cerevisiae have demonstrated that actin interacts directly with dozens of other proteins, and indirectly with even more (Figure 16-15). Over time, evolving organisms have found it more profitable to leave actin and tubulin alone, and alter their binding partners instead.

      The more complex a system becomes, the more it gets life-like constraints like this.

    18. Re:Modern Technology by ogdenk · · Score: 2

      Because the Romans made piers and bridges which still stand in salt water, and we really can't come close to that.

      Actually, that's not true. We've figured out how to make Roman Concrete but it has it's own limitations and is less safe to work with in some ways and much harder to make in vast quantities cheap. Our construction processes and material shipping methods would have to change considerably in order to use it in a widespread fashion.

  3. old != bad by AndroSyn · · Score: 5, Informative

    My money is on this VME system being around for another 20 years while the mess of Java and Oracle(you know they're going to use Oracle). It'll be overpriced, late and won't actually work.

    Just because something is old, doesn't mean it needs replaced. In short, why not just upgrade the mainframe?

    1. Re:old != bad by Shinobi · · Score: 4, Interesting

      Nono, like other big IT projects in the UK, it will be using "the very latest in Agile know-how", and cost 3 times as much as any clusterfuck that involves Oracle, take 50% longer, and spread 300% more blame on "old fossiles"....

      Disclaimer: Had to interface with a EU project under UK IT auspices last year.... Painful....

    2. Re:old != bad by ranton · · Score: 3, Insightful

      Just because something is old, doesn't mean it needs replaced. In short, why not just upgrade the mainframe?

      I have no idea how common VME developers are, but when dealing with legacy systems you do have to worry about being able to find qualified people to work on your software. Not only are the skills rare, but most people are going to be wary about pigeon-holing their career by focusing on such a obscure system. You will either have to rely on sub-par employees or pay well over market rates.

      Hiring expensive employees / consultants may still be desirable over a risky migration, but the expense (either in salary or in low quality employees) shouldn't be ignored.

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    3. Re:old != bad by Wintermute__ · · Score: 2

      Changed? Sure.

      Improved? Well, the jury is out.

    4. Re:old != bad by fahrbot-bot · · Score: 2

      I have no idea how common VME developers are, but when dealing with legacy systems you do have to worry about being able to find qualified people to work on your software. Not only are the skills rare, but most people are going to be wary about pigeon-holing their career by focusing on such a obscure system. You will either have to rely on sub-par employees or pay well over market rates.

      These days, I'd take more job security over "over market rate" salary and fancy perks. As long as I can pay my bills, the work is fairly interesting, my teammates and managers actually appreciate me and value my skill set - and I'm not micro-managed to death, I'd be happy to pick up some VME skills.

      I don't consider myself a "low quality" employee, I just don't have fancy tastes or a tech-toy habit to feed (nor do I have kids). Now 51, I have always lived responsibly, am debt-free (with enough savings/investments to survive another 60+ years w/o a job - not counting SSI). I currently work for a large defense contractor on a three-person team using about 10 programming languages for about 500k lines of code on both Windows and Unix/Linux systems. I have previously worked for the NYT and at NASA.

      Overly highly paid and/or low quality workers are not the only options - for many jobs.

      --
      It must have been something you assimilated. . . .
  4. Does it still work? by 91degrees · · Score: 3, Interesting

    If so, why fix it? What are the tangible benefite of a new system?

    1. Re:Does it still work? by Lunix+Nutcase · · Score: 2

      Government contracting money.

    2. Re:Does it still work? by Dr_Barnowl · · Score: 2

      Depends what the requirements are.

      Usually, this sort of thing happens because requirements are changing faster than the old system can be maintained to keep up.

      I wouldn't be surprised if this is to help automate the swingeing series of "sanctions" that are carried out to remove the benefits from job seekers in this country.

      Things like suspending their payments for...

      * Being late for an appointment at the job centre (by approx 2 minutes).... because they were attending a job interview
      * Not attending a job interview
      * Applying for 6 jobs one week, and 3 jobs the next, and not realising that the directive to apply for 4 jobs a week is not met by an *average*
      * Applying for jobs on Monday and Friday, then being sanctioned because the accounting is done Tuesday and the count of jobs on Monday wasn't high enough

  5. It is called good coding. by www.sorehands.com · · Score: 4, Insightful

    Many people are shocked that computers/systems for 20 years still run, but is says a few things:

    1. That people are used to crap code that can't keep running.
    2. That people are used to crap products that can't last for more than a couple of years.

    If it ain't broke, why fix it? They sent man to the moon on less CPU horsepower than my Nexus 6. Voyager has been running for more than 35 years in the harshness of space.

    1. Re:It is called good coding. by Todd+Knarr · · Score: 4, Insightful

      They have. But they didn't do it overnight, they did it small bits at a time and those 40-year-old systems were patched or updated and debugged with each change. The result is a twisted nightmare of code that works but nobody really understands why and how anymore. And the documentation on the requirements changes is woefully incomplete because much of it's been lost over the years (or was never created because it was an emergency change at the last minute and everybody knew what the change was supposed to be, and afterwards there were too many new projects to allow going back and documenting things properly) or inaccurate because of changes during implementation that weren't reflected in updated documentation. As long as you just have to make minor changes to the system, you can keep maintaining the old code without too much trouble. Your programmers hate it, but they can make things work. Recreating the functionality, OTOH, is an almost impossible task due to the nigh-impossibility of writing a complete set of requirements and specifications. Usually the final fatal blow is that management doesn't grasp just how big the problem really is, they mistakenly believe all this stuff is documented clearly somewhere and it's just a matter of implementing it.

    2. Re:It is called good coding. by ratboy666 · · Score: 2

      In the Apollo timeframe, a "supercomputer" would be a CDC 6600 (1964).

      3 MFLOPS and up to 10 million instructions per second, 60 bit word size, 262144 words of main memory (~3 million 6 bit characters) -- yes, your smartphone is more powerful. This was STILL the most powerful mainframe in 1969.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
  6. Paging John Titor by Anonymous Coward · · Score: 2, Funny

    John Titor... Please report to... Oh, nevermind. Some bloke in a blue callbox has already claimed it.

  7. Orange Leos? by sysjkb · · Score: 4, Interesting

    I wonder if they are running "orange Leos"? Here's a post from alt.folklore.computers in 1998. Terribly impressive. I'm not sure his age estimate is necessarily accurate, though: the final incarnation of the Leo ceased to be manufactured in the latter half of the 60s, so it may be a bit younger.

    From: Deryk Barker (dbarker@camosun.bc.nospam.ca)
    Subject: Re: Multics
    Newsgroups: alt.folklore.computers, alt.os.multics
    Date: 1998/11/09

    [...]

    When my wife was working for Honeywell, in the 1980s, one of the
    customers she had dealings with was British Telecom.

    BT, at one location, had what they called the "orange Leos".

    Now, for those who don't know this, the LEO was the world's first-ever
    commercially-oriented machine (1951). Even more amazingly, the Lyons
    Electronic Office was designed and built by the J Lyons company,
    best-known as manufacturers of cakes and for their nationwide chain of
    corner tea shops.

    Anyway, an "orange Leo" was an ICL 2900 mainframe (they came in orange
    cabinets), emulating an ICL 1900 mainframe, emulating a GEC System 4
    mainframe emulating a LEO.

    30+ year old executable code over 3 architecture changes....

  8. New Platform by Dr.+Evil · · Score: 5, Funny

    Port it to minecraft. There seems to be some good 1970's CS work happening there.

  9. It is broken (probably) by sjbe · · Score: 4, Insightful

    Many people are shocked that computers/systems for 20 years still run,

    Only people who don't know much. It's not shocking that such a thing would happen or that hardware can be made that robust. What IS shocking is that people put systems in place without any thought whatsoever to what people might want to do 20 years later. Seriously do you REALLY think it will be efficient or practical without problems for you to use the PC you are reading this on today in 20 years? Why would it be any different for a business or government?

    If it ain't broke, why fix it?

    Because it probably IS broken in a multitude of ways. Just because it can get a specific job done doesn't mean it does so efficiently or without problems. I've driven a lot of beater automobiles over the years and while they usually got me from point A to point B they were unquestionably broken if a number of ways. I have PCs that are 10-15 years old here in my company doing specific jobs and they definitely have problems. Yes we still get some productive work out of them but that doesn't mean I shouldn't think about replacing them when I can.

    They sent man to the moon on less CPU horsepower than my Nexus 6.

    Because that is all they had at the time. Nobody would even dream of doing that way today because we have better options now. Why limit yourself to yesterday's technology if you have a choice?

    Voyager has been running for more than 35 years in the harshness of space.

    Which is relevant how? You're comparing a spacecraft that human eyes will never see again with a earthbound computer system that we can modify or replace any time we want.

  10. Extreme example here, but... by ErichTheRed · · Score: 4, Interesting

    Not all legacy stuff is bad. Not all legacy stuff should be kept around to the point where you can't find people to run it, however,

    I've had experience working in die-hard IBM mainframe shops as well as places that used the HP MPE operating system on the HP 3000 minicomputer system. In the 3000 case, the customer was relying on a service provider that was providing an application that was way way way out of date but still worked. All the IBM places I've ever worked have been slowly "modernizing" their application stack, but in most cases, the core transaction processing has remained on the mainframe because that was the best solution. It's extremely rare these days to see an end user facing green screen application, but they do exist as well. (Yes, I work in "boring" old school industry sectors, very few web-framework-du-jour hipsters here, but we're also not old farts.)

    The problem I've seen is that vendors love the fact that customers are locked in and will do nothing to encourage them to get off. Most ancient mainframe code can run virtually unmodified on newer hardware, and that backwards compatibility is a big selling point. It allows IBM to go in, swap out your entire hardware platform at $x million, and keep billing you by the MIPS without changing any code.

    But...the reverse problem is that "mainframe migration" projects often end up becoming case studies of how Big Consulting Company X was paid hundreds of millions to not deliver a working system. I believe I read about DWP's "Universal Credit" project that has Accenture, IBM or Oracle written all over it. These kinds of projects usually try to port all the business logic and transaction processing to some horrible-to-maintain J2EE monstrosity backed by an Oracle database. They usually fail because (a) no one correctly estimates the work required to pull all that business logic out of 30+ years of cruft, and (b) the consulting companies replace their star team (that travels with the sales force) with new grads in India (who do the actual work.) I've seen this cycle over and over again, and am still amazed that CIOs aren't wary of consultants.

  11. Re:It's paid for. by Fished · · Score: 2

    Listen up, Junior ...

    In some ways, Token Ring was very much superior to Ethernet. A hospital I worked for in the late 90's had a huge (1000 nodes) 4Mbps TR, all as one big subnet, built long before switches came along. If you tried to do that with Ethernet, it would have crashed and burned in a week. This was, on the whole, pretty reliable (if slow). The downside was that if one card in the ring failed, the whole thing would generally die. So it was great until the 10 year old TR cards started failing regularly due to capacitors failing. We ended up replacing the whole thing with 100Mbps switched ethernet, which wasn't really noticeably faster despite a 25-fold increase in nominal bandwidth, and failed more often. :)

    --
    "He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
  12. Is it broken? Is it unsupported/sunsetting? by davidwr · · Score: 2

    If it's not broken, it gets the job done, it's vendor-supported, and you don't expect that support to end in the foreseeable future, then I don't see the problem.

    Age alone is not any reason to declare technology obsolete.

    Here's a common example: Stores still sell 4-function calculators for $5 or less. As far as the user is concerned, they are less-expensive versions of the same calculators you could buy from the mid-1980s on, and thinner-and-cheaper-with-LCD-and-button-battery versions of the kind you could buy in the 1970s. In other words, if you still have a 1985 four-function calculator and it's still working, it still meets your needs, and you can still get batteries for it, there's no reason to throw it out.

    Heck, even the lowly manual typewriter is still better than a pencil, pen, electric typewriter, or computer+word processor+printer in certain situations. In others, the best choice is a pen or pencil.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  13. The California DMV has them beat. by funwithBSD · · Score: 2

    The California DMV has them beat, they are still using code installed on UNISYS mainframes in 1970 to run the DMV core applications.

    It is as old as I am...

    --
    Never answer an anonymous letter. - Yogi Berra
  14. Re:VME is not an operating system. by Guy+Harris · · Score: 2

    It is a bus and connector specification.

    "VME" can refer either to the VME operating system or the VMEbus.