Evaluating Vax Lisp 3.1

> At some point, I brought a MicroVAX with me to a vintage computer convention, and a friend had his MacIvory Symbolics Lisp Machine on display. As the two systems were from the same era, we thought that we should try to bring up some network between them. My VAX ran a fairly recent version of VMS, though, and when we tried to establish a DECNET connection, the Lisp machine would signal an error and put us into a debugger. What got me hooked on Lisp was that my friend could display the source code of the failing DECNET device driver, figure out that the problem was the too-new DECNET version number that the VAX had reported in the connection setup packet, fix the Lisp code in the DECNET driver of the Lisp Machine and then continue the file transfer operation that had signaled the problem. I certainly understood that this would theoretically be possible back then, but I had never seen a system that would have that level of integration of operating system and programming language. I was intrigued.

The language survey class I took as part of my CSci degree, had us use Lisp on a MicroVAX. The resources that Lisp required versus the machine we were running it on made it very much like programing a batch system. The terminals were slow when Lisp was running. It was so bad we typed our programs out on a PC and ftp'd it up to the VAX and then loaded it, check if we got the syntax right, run it, and repeat. The whole interactive lesson was lost on us since it would take forever to do anything. The only good that came out of it was winning enough money at poker played in the lab to pay for pizza that weekend.

This is slightly tangential, but it details my first real professional screw-up on a VMS system.<p>My first serious job was working as a Junior Sysadmin on a large VAXCluster. I literally had NO idea what I was doing. On my first day my boss said to me, &quot;Here&#x27;s your account details, it&#x27;s got the same rights as SYSTEM, if you screw up, we&#x27;ll fire you. Good Luck.&quot;. The senior admin showed me the ropes, and especially the HELP command, and basically spent the next week typing HELP followed by every command I encountered.<p>Fast forward three months, and I&#x27;m fairly comfortable with VMS, writing scripts and improving some of the daily housekeeping tasks to make them faster and more efficient. I&#x27;m working on the startup script that boots the cluster, stepping through the existing one to understand what it does and I encounter a command I&#x27;ve never seen before, so I duly flip terminal screens (VT420 dumb terminal with dual inputs), and type HELP followed by the command.<p>Except I didn&#x27;t actually type HELP. I just typed the command.<p>As I watched the terminal fill up with output, I realised what it did. Basically it flushed all core processes out of memory. Including the one that allowed people to logon.<p>Normally this would be a fairly embarrassing screw up requiring a simple reboot, except that this VAXCluster belonged to the MoD, and it was running military combat scenarios (wargames), and had been running a large war scenario for several weeks, non-stop. Somewhere on the site where I was working, there were two large rooms each filled with soldiers and each day they&#x27;d been planning out their campaign tactics against each other and these decisions were being plumbed into the running scenario in real time by an operator.<p>I&#x27;d basically broken everything, and potentially destroyed the whole scenario. The scenario was still running in memory, but no-one could talk to it anymore. Rebooting the cluster was <i>not</i> an option.<p>Immediately, white faced, I admitted to what I&#x27;d done. One of the &#x27;real&#x27; VMS coders on my team also went ashen. After lots of head scratching, he set to work. I don&#x27;t know in detail what he did, but from what I understood at the time, he effectively manually restarted the 100s of processes that the Cluster needed to operate, as if it was rebooting but without actually flipping the switch.<p>Several hours later, the Cluster was fixed and running normally. I&#x27;d also not been fired.<p>This event, left me with a massive appreciation of multi-user systems and how one small error can affect 100s of people. A year or so later, I transitioned into PC support, as Desktop PCs were slowly replacing the dumb terminals across the site, and later on I started working for an international bank where again networked PCs were new. I found that having cut my teeth and been burned on a large multi-user system gave me an impact perspective that most people working in the fledgling PC support industry didn&#x27;t yet have.<p>Because of this, VAX&#x2F;VMS systems will always be special to me.