My Most Interesting Job free essay sample

My Most Interesting Job John Myszkowski Everest online Composition I – ENC 1101-111 ? I brain stormed by making a list of different things that I experienced in my life. This list is varied but not too long. I tried to keep the list positive. I had a lot of fun and interesting experiences to pick from. Some of the most fun ones I am saving for later. My subject is my most interesting job. My most interesting job was when I worked for Control Data Corporation. I was a customer engineer; I was assigned to a customer site which had the responsibility for supporting several other customer sites. I was supporting their mainframe computer systems, and their terminals and mini computers and any other equipment that they supplied to the customer. Every year that I worked for them I went to training classes to learn about a new piece of equipment. They stayed on the cutting edge of computer technology with new innovations. We will write a custom essay sample on My Most Interesting Job or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page They were the first computer company to design and build the first super computers and market it. Then the people at the top who were suppose to know what they were doing made a major mistake that started the down fall of the company. And you can guess the rest. But one of the most interesting incidents that happened in my time at Control Data was the night that I spent tracking down an intermittent compare move problem in one of Cyber A’s CPU’s. Cyber A had dual scalar processors. A compare move unit was a special unit that compared fields of data and then moved them as dictated by the instruction. The instruction was a 60 bit instruction for a simple compare or move instruction but if it was a compare move collates it could be a 120 bit instruction. And you had to know what every bit in that instruction did. These instructions could be extremely difficult to diagnose when something went wrong. Because you had to know which one of the instructions was failing and you hoped for the easiest one to be failing instruction. In the test software output you had to determine whether you were dropping or picking a bit. Dropping a bit would be if you set the bit to a one and read back a zero. Picking a bit would be no matter what you set the bit to you would always read back a one. So you had to run the test with many different data patterns to make sure of what the problem was and which module was the failing module. Because this was a main frame computer it had many modules that were the same kind so what you would do is swap modules between locations and run the test again to see if you moved the problem and where it moved to. And that would be the failing module. Once I got the problem to stabilize and failing consistently and I traced it down in nothing flat. I worked on many problems over the years at Control Data some of them resulted in changes to the equipment. I went to various classes on equipment that worked faster and processed more data in less time. At the time the space race was on and the need for more computing power was very important. I worked on the same models of computers that got man to the moon and back safely. I wrote many reports as to why certain problems were occurring, and there was always a trip report to be filled. I enjoyed working for Control Data Corporation because the job presented a new challenge every day and no two days were the same. One day you could be sitting at your desk looking for something to do and the next you could be getting on an airplane and flying to a distant city to solve a major problem. Being in a reserve tech support position life was always exciting. I have been too many places and seen many things some of them are still secret today.