Being older than dirt, war stories from Gabe and Phil contain golden nuggets of truth and forewarnings from which any new z/VM sysprog should consider learning (ahead of time).
In my best "As Seen On TV" huckster voice: But wait! There's more! Operators are standing by to share even MORE (FREE with this offer!!) war stories (perhaps prevent you from repeating the same mistakes)! The IBMVM listserve has a very powerful and **EASY TO USE** web browser based archival search facility. Go to: http://listserv.uark.edu/scripts/wa.exe?S1=IBMVM In the "Search for:" box, enter: system programmer war stories then press "Submit" Very shortly thereafter you will be regaled with the real-life experiences of "live systems programmers (not on stage)!" Learn from the past grasshopper, or you are condemned to repeat it. And then... **BOOKMARK** the IBMVM listserve search page in your browser - as the "first stop" the next time you need a little help late at night or on a weekend... or any time! :-) Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Gabe Goldberg" <[email protected]> Sent by: "The IBM z/VM Operating System" <[email protected]> 02/06/2010 03:13 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: Hi everybody Long ago (long enough that communication with service machines was via punch files), a site had a similar SVM for executing privileged commands on behalf of suitably authorized users. Just for grins, when he needed to shut down the system, one of them did it via command to the SVM. Problem was, the system shut down before the punch file was purged. AND, the SVM was automatically started by Autolog1 with no time delay. So when the system was warm started, it found the command file waiting, and shut down. Wash, rinse, repeat. Cold start. (Hey, they were only developers and sales people.) Followed by adding a time delay to Autolog1 processing. And it wasn't me, that was before I joined the company. Much longer ago, when Mitre was first installing VM (1972, VM/370, Release 1 PLC 9) I was working from home on a Silent 700 terminal. The second shift operator did something that annoyed me, so I shut down the system. Followed by, "Oops, we're in production now. There might be real users logged on". Phil Smith III reminisced: On Fri, Feb 5, 2010 at 10:46 AM, James A. Bohnsack<[email protected]> = wrote: > >I've accidentally shutdown the main production system "once", as has = > every systems programmer with whom I worked or who worked for me has = done. Only once tho. Indeed. A very, very long time ago, back at UofW, we had a machine = called PRIV, that had a table of users and commands. You could "SMSG = PRIV somecmd" and if you were enabled, it would do it. It was very = granular, down to the specific operands: This let us do things like let = a professor force his students, without giving him general FORCE privs = (I was going to write "force his admin", but that had the wrong = connotation!). Anyway, I was doing some maintenance to PRIV. I logged on and was in a = CP READ. Since I didn't want to take it down mid-command, I had the = brilliant idea of doing an "SMSG * SHUTDOWN" (it was single-threaded, of = course). And then I waited. And waited.=20 All of a sudden one of the operators comes running out of the Red Room = (the raised floor), yelling "SYSA just shut itself down!" Of course, I immediately realized what I'd done. Hey, they were only = students;-) -- Gabriel Goldberg, Computers and Publishing, Inc. (703) 204-0433 3401 Silver Maple Place, Falls Church, VA 22042 [email protected] LinkedIn: http://www.linkedin.com/in/gabegold The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
