Updates from around the country
follow Sun.Star on Twitter

ePaper
Pacquiao vs Cotto

SECTIONS


Weather Bulletin

Issued At: 5:00 a.m., 02 December 2009

  Northeast Monsoon affecting Northern and Eastern Luzon and Eastern Visayas.

Metro Manila

Partly cloudy to at times cloudy with isolated rainshowers
21°C to 32°C
Moderate to Strong:
Northeast
Manila Bay:
Moderate to Rough

More


PCSO Lotto Results
Lotto Results 12/1/2009
Superlotto 6/49: 43 29 20 01 13 24
6Digit: 6 9 1 5 2 8
Lotto 6/42: 17 37 11 20 04 40
Swertres: 168 * 950 * 961

More results

IBM refutes GSIS claims



INTERNATIONAL computer hardware and software manufacturer IBM slammed the Government Service Insurance System's (GSIS) accusations blaming the company for the failure of its multi-million Integrated Loans, Membership, Acquired Assets and Accounts Management System (Ilmaaams).

Ilmaaams is a computerization system entered into by the GSIS with IBM for a reported amount of P80 million for its software and hardware.

For updates from around the country, follow Sun.Star on Twitter

In an official statement, IBM said that it "feels compelled to issue a clarification of the key facts that have been omitted from the public statements made by the GSIS."

In a press briefing Friday, GSIS senior vice president Josefina Valera said the recent slowdown experienced in the processing of transactions with the GSIS throughout the country is due to the crash of the IBM software dubbed as the IBM-DB2.

The press briefing was intended to clarify issues hounding GSIS, particularly the slowdown in the processing of transactions.

Further explained by lawyer Orlando Polinar of the GSIS legal department, the crash was worsened by the alleged delay in the reaction of IBM despite the numerous correspondences sent by the government-run insurance company.

"The crash happened in March 30, 2009, but IBM only responded 45 days later, on May 15," Polinar said.

An email from IBM sent to Sun.Star Davao refuted the allegations made by GSIS against the company.

"The fact is that IBM provided assistance to GSIS as soon as we were notified. Out of goodwill, IBM Philippines provided a database specialist to work with Questronix, the systems integrator for Ilmaaams. Through SAP, the IBM Toronto Lab provided technical solutions (special builds) on May 15 and May 21 to address the issues related to GSIS' database management," IBM's official statement said.

IBM also refuted the allegations that their laboratories in Canada admitted the company has installed flawed database management software.

"IBM Laboratories in Canada did not make such an admission. IBM did not supply, design and install the system. Under an SAP/DB2 OEM arrangement, all customers receive one-stop service through SAP. Behind the scenes, the IBM Toronto Lab is fully integrated into the SAP services process. The special builds were provided to GSIS through this arrangement even without maintenance support agreements between SAP and GSIS, as part of SAP and IBM's commitment to help resolve the issues faced by the GSIS," IBM clarified.

With the crash of the IBM DB2, transactions with the GSIS, which would usually take a course of three-day processing, will now have to be processed for two weeks, Polinar said.

IBM maintains that it has not entered into any agreement or contract with GSIS in the supply, design, or installation of the Ilmaaams.

"The overall stability of the Ilmaaams will continue to be in question until the GSIS takes steps to address the many issues impacting the system, a fact communicated to the GSIS by Questronix in correspondence dated May 15 and May 28. According to Questronix, the stability of Ilmaaams remains at risk until the GSIS takes steps which include the institution of appropriate backup and recovery procedures; the conduct of appropriate performance testing and tuning in accordance with industry practice; and having certified personnel to manage the complex systems on a regular basis.

In addition, IBM believes that it will be essential for the GSIS to have appropriate support and maintenance arrangements to ensure availability of the Ilmaaams.

GSIS is now mulling its transfer to an Oracle operated database system.

"We will migrate to Oracle from IBM, and it will take us about four to five months for our operations to normalize," Polinar said.

Multi-million lawsuits have been filed by both camps against each other, which are now pending before the courts.


Published in the Sun.Star Davao newspaper on July 6, 2009.


Feedback: Your views and reactions

I am retired after spending

I am retired after spending my 35-year career in the Information Systems field here in the United States. I have been following this story since the beginning and been trying to find answers to a few questions which I deem very relevant to this issue. Maybe you might have access to the source to get the answers. Here are my questions.

1. I understand that this GSIS application was first installed in 2006 under IBM's OS/390 Operating System on the mainframe and DB2 as the database manager. After the first half of 2008, did GSIS not renew its license for OS/390 because it was migrating to an open system architecture, maybe Linux? If the answers to the above questions are yes, then the GSIS application must now be running with DB2 under Linux instead of OS/390.

2. Is Linux running on the same mainframe or on different servers?

3. What is the Authorized Program Analysis Report number (APAR) which came with the fix from IBM and did GSIS properly apply this fix? GSIS should be able to give the APAR number if they received one.

The reason I believe the answers to these questions are important is because by coincidence, GSIS reported that their performance problems started sometime in early 2008. It is very possible that a well-tuned DB2 application running on the mainframe could run like molasses as a result of the change in operating system/hardware if the necessary systems performance tuning was not done, or if the new hardware has not been sized adequately. If so, why focus all the blame on DB2?

Granted, there was a program error in DB2 failing when the size of the table space exceeded 2 TB. But this has been fixed if GSIS applied the fix which is documented in IBM's APAR LI73318. This is in the public domain of IBM and you can read it yourself if you Google APAR LI73318. It is possible that GSIS received a different APAR, the reason for my Question 3 above. If the performance of the system did not improve after the error in DB2 was fixed, then the performance problem could be due to other factors.

Truly yours,
Bert Peronilla, PhD Computer Science

PS: I installed the very first computer at UP in 1967, the IBM System/360 Model 40.