I need to update my Docker images with this. In reality, someone needs to write a Hitchhiker's Guide to VM/370, CP and CMS. I haven't been able to do much beyond seeing what's on the disks and running some sample programs.
True but then it was somewhat a fashion of the time to add Open to things (marketing trying to capitalise upon the Opensource movement heh). For VMS the history is:
"In July 1992, DEC renamed VAX/VMS to OpenVMS as an indication for its support of open systems industry standards such as POSIX and Unix compatibility, and to drop the VAX connection since a migration to a different architecture was underway."
Likewise there is very few Open in POSIX and UNIX standards, for a long time, just like with ISO C and C++, one really needed to buy them in paper form to read them.
Unless things have changed recently, hobbyists can sign up for a license for OpenVMS. However a condition of the license is that you can't use a hobbyist license for commercial purposes.
HPE has divested VMS Software Inc., so if you want hobbyist license you have to go to VSI and not to HPE. And under VSI the process of getting the hobyist license is simpler (ie. you don't have to be member of anything) and IIRC you can even get images of installation media directly from VSI.
"To help us qualify your application for this evaluation release kit, please fill out the following survey. Please be advised that community (hobbyist) licenses are not currently available, evaluation licenses are provided to commercial customers only."
> I'm guessing because they didn't have attached copyright notices as required in US law at the time they fell into public domain
In IBM’s case, it wasn’t an oversight, it was an intentional decision. They intentionally put their core mainframe operating systems into the public domain, but they still copyrighted certain applications and add-ons. In later versions (like this one and its immediate predecessors), most new OS features went into copyrighted add-ons only, and the core OS by itself became more and more backward and limited. Then eventually, they came out with new versions of their operating systems where even the core was copyrighted.
They did use other methods of “closing” software than copyright - much of MVS was written in a proprietary dialect of PL/I for which no compiler was publicly available. So even though they shipped the source code to customers, and the source code was public domain, nobody could compile it (unless you wrote your own compiler). VM/CMS (especially at this stage) was still mostly assembler though, so it was easier to modify than MVS was.
Not sure I agree completely with that. These were simpler OSs for a simpler time. A lot of what I do today I accomplished in the 80s with an Apple II, a phone line, and a modem. I read emails (we didn’t call them that back then), wrote software, built databases, discussed esoteric topics in BBSs… Even met my first wife online over a Minitel-like system.
Similar for me but on BBC-B Micro. Rose tinted memories perhaps. And replication of that experience now would be a very interesting exercise in patience and acceptance for me. Indeed simpler times.
Could I personally go back? As much as technology has given us super fast hardware, very complex and flexible operating systems, GUIs and complex software am I any better off for it? Outside of my professional work where I have to deliver my work within a defined technology stack, I wonder how much I could do without and go back in time.
And even then a lot of what I produce professionally resides in text files, so I could originate them on an older system - the key to this is, of course, interconnectivity or a bridging technology. SCSI to USB stick anyone!
As much as there is an alternative lifestyle to be had rooted in minimalism and contentment in simpler things (which I aspire to) I am tempted to stop the hyper-driven tech world and get off!
Reading the work and enthusiasm of retro-computing people is actually quite inspiring.
> And even then a lot of what I produce professionally resides in text files, so I could originate them on an older system - the key to this is, of course, interconnectivity or a bridging technology. SCSI to USB stick anyone!
One think I did a lot, which is kind of cheating, is to use X to run the heavy lifting on my Linux box while sitting in front of a Sun.
A lot of what we do is just larger versions of what we did before. We call batch processing ETL and use tables instead of tapes, but the ideas are there.
And, unlike some MacBooks, a BBC has an ESC key ;-)
I routinely do. I have a number of old computers that are still functional. Won’t be writing anything to network drives from the Apple II, but DOS PCs (yuck!) and Macs are fair game.
I actually have one (or close to it) since we have an old AS/400 terminal in the backroom. We bought a new iSeries and that, sadly, uses a PC as a console terminal.
reply