Super Work Blunder Number 3
I really really wanted to disappear on the face of this planet this morning.....or maybe I was wishing I am/could be like Casper, who could turn invisible when I want to hide my face.
Yeah, I may sound so cowardly, but I really can't help it. I'm so shameful of that stupid mistake that caused implementation number 3 to be backed-out (once again) last night. :'(
I know I already did this before. Why didn't I learn from that mistake? Again, I left an 'EXEC CICS WRITEQ TS QUEUE' command inside the code. I wasn't able to remove it before the programs were migrated to production. :'(
I admit it was my pure carelessness that made this very simple command be the culprit of the backout. The command itself is not harmful. But when the queue reached its maximum number of entries (which is 32,767. I'll never ever forget that number), the whole transaction will abend.
When this happened in EPCIB, all the ATMs went offline. This time in RCBC, all 32768th-up savings account transactions done in ATM yesterday were not successful. :'(
Comparing the two blunder incidents, I say that what happened in EPCIB was less disastrous because the problem took place earlier in the morning, when ATM transactions were not at its peak. But this time, almost all savings transactions were rolled out. I just can't imagine how much money RCBC lost that time. :'(
Added the fact, that this is our first project in RCBC. Somehow, this incident has tainted the company. My bosses, Sir Mike and Sir Richard did not say a word. They did not scold me. Though I know, they were really upset.
Ramil said I should not think about it anymore. Dan said "it's okay because the mistake was still fruit from your hardwork". But I just can't get over it. Once is just a plain mistake, twice is too much of stupidity. And I definitely am not wanting to hit strike 3. :'(
So maybe they were right - stop thinking of the past and start learning from my mistakes (dapat magsink na ito..).
Yeah, I may sound so cowardly, but I really can't help it. I'm so shameful of that stupid mistake that caused implementation number 3 to be backed-out (once again) last night. :'(
I know I already did this before. Why didn't I learn from that mistake? Again, I left an 'EXEC CICS WRITEQ TS QUEUE' command inside the code. I wasn't able to remove it before the programs were migrated to production. :'(
I admit it was my pure carelessness that made this very simple command be the culprit of the backout. The command itself is not harmful. But when the queue reached its maximum number of entries (which is 32,767. I'll never ever forget that number), the whole transaction will abend.
When this happened in EPCIB, all the ATMs went offline. This time in RCBC, all 32768th-up savings account transactions done in ATM yesterday were not successful. :'(
Comparing the two blunder incidents, I say that what happened in EPCIB was less disastrous because the problem took place earlier in the morning, when ATM transactions were not at its peak. But this time, almost all savings transactions were rolled out. I just can't imagine how much money RCBC lost that time. :'(
Added the fact, that this is our first project in RCBC. Somehow, this incident has tainted the company. My bosses, Sir Mike and Sir Richard did not say a word. They did not scold me. Though I know, they were really upset.
Ramil said I should not think about it anymore. Dan said "it's okay because the mistake was still fruit from your hardwork". But I just can't get over it. Once is just a plain mistake, twice is too much of stupidity. And I definitely am not wanting to hit strike 3. :'(
So maybe they were right - stop thinking of the past and start learning from my mistakes (dapat magsink na ito..).