My first exposure to IT was as a keypunch operator. I apologize if this means nothing to you. There may be portions of this post that will also mean nothing, but I will try to clarify when I can. Now let’s get back to my keypunch days.
I did not keypunch on a card machine for long. They were soon phased out and the key punching was done onto a large floppy disk. I hated the work. It was tedious and mundane and prone to errors. Part of my job also entailed dropping off the disks to the IT department where I met a lot of the programmers and operators responsible for keeping the mainframe up and running. When an internship was advertised, I applied and was selected for the position.
My first responsibility was as a programmer. I was a good programmer but not an inspired programmer, especially when responsible for debugging someone else’s programs. Our Cobol programs required recovery routines in the event something went wrong during processing. When an error was encountered, an statement would be executed that said “GoTo and the name of the recovery portion of the code.” I often encountered “GoTo H*ll” or something similar. Worse than that was when the different procedures had meaningless names – it made the work more tedious.
I eventually moved into a position as a System Programmer which had the responsibility for the operation of the internal code that ran the computers, not just the business programs that ran on the computer. I never drank coffee or beer until I started in IT. I worked as much after midnight and weekends as I did during the day. My children spent a lot of weekends at my desk while I worked.
Programmers loved to put the operators who loaded tapes and monitored the main console through their paces especially if they were new. They wrote programs to generate console messages which the operators would see and respond to appropriately. One night one of the guys thought it was time to break in a fairly new operator. It did not go well.
This particular night, the programmer decided it would be funny to send this message: “The system will self destruct in five minutes.” The operator was not experienced enough to detect the possibility this was a hoax. As a result, he immediately issued the SHUTDOWN process which brings everything to a grinding halt. The programmer (a fairly senior guy) rushed in for fear the operator might try to manually dump the halon (a gas used to extinguish fires). (Later fire suppression systems may have eliminated the ability to manually discharge halon. Halon systems have now almost completely been eliminated due to environmental concerns.) That would have been a disaster as you can see in the video below.
It is always an adjustment when contemporaries are promoted into a leadership positions. One of our programmers was promoted into the position of security manager and he took his job very seriously. We implemented IBM VM CMS which allowed individuals to have their own individual profiles – each one controlled by logging in with a user name and password. Our security manager implemented a change that would require the password be changed every thirty days AND required the passwords be randomly generated. My senior Systems Programmer wrote an APLDI program to generate random passwords for every user. It went smoothly – at least the first time. The second month, the program ran and we sent the passwords forward. The only problem was the program generated the SAME random passwords. The program required a ‘seed’ to start the process, and my co-worker forgot to change the ‘seed’. Whoopsie.
I worked on a military installation (we were all civilians) and my mentor was tasked with writing a check writing program. It was a bit complicated and getting the checks to line up properly had not been an easy task. When he went to demonstrate the program to the base Commanding General, the first check that rolled off had my mentor’s name in the Pay to the Order field in the amount of $10,000. Again, it goes without saying the General was not amused.
Mainframes have large disk drives (DASD) that contain a large amount of data. We had one unit that failed and had to be replaced. The device was initialized, uninstalled and a new one replaced which required a weekend of work. Our aforementioned security guy decided the disk drive needed to be remounted and overwritten in its entirety with binary ones and zeroes to ensure no data remained. I do not remember how this was resolved but there were a lot of curse words thrown around in our office for a few weeks.
After a move across country from Alaska to Maine, I again took a job as a Systems Programmer. I had responsibility for all the voice and data communications controllers, devices, and software. It was again a VM shop and it was another team of quirky individuals. When my boss turned 40, his wife threw him a surprise party and invited all the staff. When he finally arrived on the scene, he had been out on the boat fishing and drinking beer all day and was quite ‘toasted’ when he arrived. Someone gave him a bright yellow pair of bikini briefs which he proceeded to put on over his fishing clothes. Long story short, one of the other Systems Programmers decided to edit his profile to execute another program – it displayed a bright yellow flashing pair of bikini briefs on our bosses terminal when he logged on the following Monday. Needed less to say he was not impressed with the breach of security nor the reminder of the prior Saturday’s antics.
These are but a few of the stories that come out of working in a high pressure job that requires a great deal of focus and sacrifice of personal time. I am sure these things would not be tolerated in today’s world. It was a different time for sure.