JPG40504 wrote:I can recall a 'temporary transplant' from FL coming to Lexington and attempting to use TSO here. At that time(and for years before and after) the 'system' resembled a yo-yo and a very slow one at that! Down time in hours was not unusual, and response time deplorable usually. Only during off hours was turnaround time 'reasonable'.
She tried for five minutes to do some simple task and inquired 'what was wrong with TSO'?. Us locals just sorta grinned and offered no answer. She then asked does 'so and so' know about this problem. Us locals did little more than raise our eyebrows slightly. At that point she stated she was going to call him and let him know about this problem. After about 5 min of weeping and wailing on her part, she hung up and left the terminal room. She was never seen again!:eek: And this took place in the development lab where things were much better than 'over there at the main plant'.
Now as a result of my experience in that environment, I rejoiced at the prospect of being able to do most(eventually) things independently of the Time Squandering Option. Granted backups etc. became MY responsibility and software installation and maintenance became MY responsibility as well as security, but I considered that an advantageous swap. I was fortunate that most of what I was using the main frame for was possible on a PC. I was using MY data with MY programs written and compiled by ME. For that no computer room or terminal room was needed. My office became my computer room/terminal room. I no longer had my 'stuff' lingering in 'queue'.
After conquering JCL, DOS was a snap!
Just a slightly different view from the other side of the main frame's residence.] is[/B] there even such a thing as a 'mainframe' any more?
Wow interesting story. All I know is I had to support mainframes and if they were down as long or as often as you say I would have been looking for a job.
Of course my world was steel production, automotive, banking and hospitals. The accounts that were colleges and research were different because they didn't care much about down time.
But tell someone that has 150 tons of molten steel the computer is down so you can't be sure what the carbon percentage is and they will offer you a swim, in the steel.
Or tell 8000 union workers their pay check is going to be a little late because the accounting computer is down, they would tear you limb from limb.
Or tell the doctor that you can't type blood right now because the mainframe connected to "blood sucker" the affectionate name given to the machine that did the test, was down and they threatened to sew you lower lip to your eyebrow.
Or tell a bank with hundreds of branches that the main frame was down, they never seemed to accept that answer.
I forget the specs but I know we had performance requirements. If the mainframe was down longer than x minutes or more often than x times. Huge fines were paid, and people were looking for jobs.
I once sat behind a computer in a bank holding a broken breaker on until the new one could be flown in (it flew in on a booked seat on the plane and was given exceptional passenger handling to expedite it on and off the plane) and installed live so the computer didn't go down.
Or the time we flew a oil drenched 2311 disk pak from Cleveland to San Jose where it was cleaned, rebuilt, data recovered and reloaded and flown back all in the same day so a car manufacture would not be down should their other disk pak went bad.
I use to get tickled when I stood in a tellers line and be told I would have to wait because the computer was down. However i was wearing a radio which was silent at the time that would alert me the instant computer did go down.