On Jan 19, 2022, at 12:27 PM, Carmen Vitullo <[email protected]> wrote: > > I recall my lead operator doing something similar on a data check on a tape, > you know when you see the tape re-read the same block over and over, he hit > stop on the processor, it was a 370/158, then accessed the control unit for > the drives and threw some toggles to bypass the bad block on the tape, > resumed and all was good, our applications were written i a way that bad data > was written to an error report so we could balance the data and account for > the missing input -
That reminds me of a story my father told me. In the late 1960s, while employed by IBM, he was working on a telecommunications program. IBM had arranged for some test time late at night on a customer’s S/360, and the whole team was flown to the customer site for the test. However, when they tried to IPL their test system it failed because the unit address for the tape drive had been coded incorrectly. While his boss was ranting at whoever he held responsible about how much money they were wasting, my father quietly walked over to the console, found where the address was stored in memory, fixed it, and restarted the load. He waited for the boss to run down and then said, “I fixed it; it’s working now.” -- Pew, Curtis G [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
