Reggie X. Preston
by Alex Papadimoulis
in Feature Articles
on 2007-05-14
At the time, it seemed like a good idea. When a fatal error would occur in a batch program, a message would be sent to the operator’s console that notified him of the error and prompted him to terminate the program. From there, the operator would call the program’s support contact (generally a programmer) and ask him what to do. Management figured that someone with some knowledge of the program should be the one that decides, not just some operator.
Of course, as the years passed by, management learned three things about this policy. First, the support contact’s answer was always “it’s a fatal error! What can I possibly do from home at 2:00 AM? Just terminate it!” Second, after years and years of developing batch programs for internal clients, there were a whole lot of batch programs (about 20,000 in all) and a whole lot of programmers that were called in the middle of the night. And third, because the operator notification would block until an answer was received, subsequent programs would be delayed while the operator tried to get a hold of the responsible programmer, who would occasionally disconnect his phone at night to avoid the inevitable call. Obviously, something had to be done.