A sudden thought today about the Ganguly - Chappell spat worked upon in my mind into a familiar happening in an IT company - a typical production support call! This is what happens in a support project. A well conceived product with prodigious amount of design and coding effort goes into production. Once there, if there are any issues, there would be a call and a fix is to be put in within the SLA. Depending on the enormity of the problem, a ticket would be raised with appropriate severity (usually 1 through 4, 1 being the highest). The job would be worked upon and restarted and the trail would resume. Something similar happened in this recent ignominy to Indian cricket.
Shastri, Gavaskar and Co. in their endeavor scheduled a very good Batch Trail (that’s basically the system, all jobs, critical in their own respect, were well scheduled – a very good coach in the interest of Indian cricket). The Initiators were all set and it kicked off in the Emerald Isle. Teething problems unmindful, it pulled itself along until a mainline driver program (Ganguly) caused an outage despite a successful, albeit laborious run. The root cause of the malfunction was reported to the System Administrators who in the meantime were busy themselves in finding out who the real administrator was. The admins in the melee got themselves lost and in the meanwhile helped the report programs (Media) scheduled in the trail to be triggered in Express mode (that’s the jobs running with more CPU resources - the leak'o'mania).
A severity 1 ticket was raised amidst fear of losing the project and the programmers had their task cut out (that was the emergency meeting). But the managers simply had the job marked complete and the batch trail resumed. The cause for more CPU utilization after the job failure is not being considered at the moment (:-)). The impact analysis of the problem could be done only in the long run. What could be the result? A system crash?!?
Shastri, Gavaskar and Co. in their endeavor scheduled a very good Batch Trail (that’s basically the system, all jobs, critical in their own respect, were well scheduled – a very good coach in the interest of Indian cricket). The Initiators were all set and it kicked off in the Emerald Isle. Teething problems unmindful, it pulled itself along until a mainline driver program (Ganguly) caused an outage despite a successful, albeit laborious run. The root cause of the malfunction was reported to the System Administrators who in the meantime were busy themselves in finding out who the real administrator was. The admins in the melee got themselves lost and in the meanwhile helped the report programs (Media) scheduled in the trail to be triggered in Express mode (that’s the jobs running with more CPU resources - the leak'o'mania).
A severity 1 ticket was raised amidst fear of losing the project and the programmers had their task cut out (that was the emergency meeting). But the managers simply had the job marked complete and the batch trail resumed. The cause for more CPU utilization after the job failure is not being considered at the moment (:-)). The impact analysis of the problem could be done only in the long run. What could be the result? A system crash?!?
5 comments:
Excellent... though I must confess I didn't understand most of the jargon
good comparison.. though as VK says I have never encountered the kind of stuff u r talking abt!!
thx guys... this is a typical scenario in many mainframe projects.. jargon puriyathathukku remba sorry... :-)
good one.
---iwalrhf---
mm...good...But, too much of mainframe jargon i felt.:-)
Post a Comment