(no subject)
Oct. 13th, 2005 07:41 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
plonqI made some changes to one of my scheduled jobs last night - specifically I removed some filters to accommodate a programming change that was supposed to go in on the mainframe side yesterday. My job crashed during the night, and this morning I had to manually resubmit the jobs in order to populate the work queues for our staff. It was my fault, of course. I'd forgotten to comment out a critical line of code when I was making the changes. Not a big deal - I'm in early enough to run these things manually in the event of a failure.
A few minutes ago one of our reps came into the office and announced that she was a bit flustered over the workload this morning. The work queue which usually consists of about 4-6 packages was over 100 this morning. We were expecting a modest spike in the workload when I removed the filters, but not something of this magnitude. Like a trout left in a desk drawer over the weekend, something didn't smell quite right here. The changes that I put in were coordinated with a programming change that IT was implementing on the mainframe. We did some quick spot-checking, and confirmed our suspicion that they either hadn't implemented the changes, or the changes were failing in the production environment.
We put in an emergency call with the programmer that said, in essence, "Ack!" He called us back almost immediately (what's he doing in at that hour?) and apologized for the mix-up. The change was supposed to go in yesterday, but there was a bit of a shakeup in IT that caused a bit of disruption. To be more precise, the president of IT sent out a terse note to the company yesterday announcing that - effective immediately - our Toronto IT office is now closed. Thank you for all your years of tireless work. You're fired. Apparently this left our whole IT department a bit flustered.
Oh wait - this is the department that is absorbing OUR department, isn't it?
This is why I drink.
A few minutes ago one of our reps came into the office and announced that she was a bit flustered over the workload this morning. The work queue which usually consists of about 4-6 packages was over 100 this morning. We were expecting a modest spike in the workload when I removed the filters, but not something of this magnitude. Like a trout left in a desk drawer over the weekend, something didn't smell quite right here. The changes that I put in were coordinated with a programming change that IT was implementing on the mainframe. We did some quick spot-checking, and confirmed our suspicion that they either hadn't implemented the changes, or the changes were failing in the production environment.
We put in an emergency call with the programmer that said, in essence, "Ack!" He called us back almost immediately (what's he doing in at that hour?) and apologized for the mix-up. The change was supposed to go in yesterday, but there was a bit of a shakeup in IT that caused a bit of disruption. To be more precise, the president of IT sent out a terse note to the company yesterday announcing that - effective immediately - our Toronto IT office is now closed. Thank you for all your years of tireless work. You're fired. Apparently this left our whole IT department a bit flustered.
Oh wait - this is the department that is absorbing OUR department, isn't it?
This is why I drink.
