It is significant iron days at a military base, recalls pilot fish who was there, and a new, larger and more quickly mainframe laptop is installed in a somewhat short-term laptop center.
Installation goes good and every little thing checks out OK.
Till a day later, when the new mainframe dies. Shortly right after, it is brought up and it runs fine once again.
Till the subsequent day, when it dies after once again. Engineers are on internet site and verify points out. All diagnostics run with no errors the method is fantastic.
Till the subsequent day … similar factor.
Meanwhile, the old method sitting correct subsequent to the new method hasn’t even burped after. Fish is referred to as in with other engineers to attempt to figure out what is going on.
Immediately after a lot of detailed evaluation, it emerges that the method only goes down in the afternoon inside a two-to-3-hour time period.
That leads to a lot of head scratching and theorizing and coming up empty. No achievable explanation can be ignored, and so the engineers take note when a member of the military employees tends to make the offhand observation that the mainframe is going down correct about the time that helicopters return to the base each and every afternoon right after everyday flight education.
It is accurate that the base radar is turned for the duration of that activity to sweep for incoming helicopters. But why would that have an effect on 1 mainframe and not the other?
Turns out the old mainframe had what was referred to as “ROS retry,” and the new mainframe did not. The radar brought on ROS errors, which had been retried by the old model and corrected just before the subsequent sweep of the radar. The new model couldn’t make these corrections.
The mainframes had been moved out of that short-term laptop center sooner than planned.
Your accurate tale of IT life is on Sharky’s radar. Send it to me at [email protected] You can also subscribe to the Every day Shark Newsletter and study some good old tales in the Sharkives.