Introduction to the Mumps Language (2017) [pdf]
31–40 of 46 posts
Re: Introduction to the Mumps Language (2017) [pdf]
#32I am entering data and running queries on a MUMPS system right now, over SSH running OpenVMS 8.4. Last application software update: 1999. I suspect we would keep using it, except, last I heard, HP off-shored their OpenVMS maintanance to India and declared, in like 2011, that it would be EOL'd in 2017. edit: I retract the statement that it's running on a PDP-11, though I have to say I was told that in teleconference j…
1. OpenVMS doesn't run on PDP-11. The only platforms it has ever supported are VAX, Alpha and Itanium. 2. OpenVMS is alive and well. It wasn't outsourced to India and it does not have EOL date. Currently it's being developed by VSI ( https://www.vmssoftware.com/ ) and they're porting it to x86.
http://h41379.www4.hpe.com/openvms/openvms_supportchart.html
Re: Introduction to the Mumps Language (2017) [pdf]
#33Of the places I've encountered Mumps/Pick/Cache, there has always been that one gatekeeper guy - only he knew the arcane abbreviations and structure in his head, everyone else had to bow and scrape to get things done. Very good language if unmaintainable, arcane code and/or job security through obscurity is your thing. Cache even let it onto the web some years back I think with ObjectScript. Just wholly nasty. The po…
I remember full page ads for Cache in Datamation and similar IT-management-oriented publications, in the mid 1990s. They called it a "post-relational database" without ever really explaining what that meant.
Re: Introduction to the Mumps Language (2017) [pdf]
#34A lot of this language's unreadability is due to how it was originally interpreted instead of compiled because of the cost of memory at the time of its invention: > Since memory was tight originally, the language design for MUMPS valued very terse code. Thus, every MUMPS command or function name could be abbreviated from one to three letters in length, e.g. Quit (exit program) as Q, $P = $Piece function, R = Read com…
Also mentioned in the linked tutorial: Memory on early mini-computers was limited, sometimes only a few thousand characters. Mumps programs were loaded into memory as source code rather than as compiled binary. This was done because it was determined that compiled Mumps programs would be far larger than the corresponding source code versions, especially if the source code employed size reducing abbreviations. So why…
Re: Introduction to the Mumps Language (2017) [pdf]
#35Earlier quoted context omitted.
1. OpenVMS doesn't run on PDP-11. The only platforms it has ever supported are VAX, Alpha and Itanium. 2. OpenVMS is alive and well. It wasn't outsourced to India and it does not have EOL date. Currently it's being developed by VSI ( https://www.vmssoftware.com/ ) and they're porting it to x86.
perhaps I misrepresented "MPS w/o SE: Mature Product Support without Sustaining Engineering" http://h41379.www4.hpe.com/openvms/openvms_supportchart.html
Re: Introduction to the Mumps Language (2017) [pdf]
#36Total cost approx. 2 billion euros majority going to Accenture and Epic Systems (which if you didn't read thedailywtf recommend checking out). The new medical system in Estonia cost about 5 millions I heard. It's just incomprehensible to me how they are going spend 400 times more money with 5x more population.
Re: Introduction to the Mumps Language (2017) [pdf]
#37Re: Introduction to the Mumps Language (2017) [pdf]
#38Re: Introduction to the Mumps Language (2017) [pdf]
#39The new finnish medical system I heard is being built with Mumps Accenture being the main contractor. Fun times, I imagine. Total cost approx. 2 billion euros majority going to Accenture and Epic Systems (which if you didn't read thedailywtf recommend checking out). The new medical system in Estonia cost about 5 millions I heard. It's just incomprehensible to me how they are going spend 400 times more money with 5x m…