RE: should have used an iseries/400

I see this one as bad project implementation, not necessarily the wrong
technology.  They didn't install or their VRU on time.  They had too many
cooks at the senior management level.  They brought in a consulting firm
that didn't have the requisite expertise.  They didn't perform volume
testing on the application server.  These are all mistakes you can make on
any platform.

I also think the article dumbs down the issues between DB2 and Oracle.
Quotes such as "trying to create places for data to fit that just aren't
there" and "The fields just didn't match up" suggest that the data model for
the new database didn't take into account the models for historical data in
the old databases.  This sounds more like database design problems and
failure to convert the old data completely or properly.  If you were
migrating PeopleSoft data from Oracle to JD Edwards on an iSeries you could
make the same mistakes, and it wouldn't be about be a technology
compatibility problem. 

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


-----Original Message-----
From: Jim Franz [mailto:franz400@triad.rr.com]
Sent: Wednesday, January 15, 2003 9:23 AM
To: Midrange Systems Technical Discussion
Subject: Re: should have used an iseries/400


>out of business...
The networks pulled the plug.
I think my original point got lost... They had problems integrating
2 diff databases and 2 diff hardware platforms.
While we could not host the Oracle8 (easily), the strength of
the iSeries in "integration" projects could have made it easier.
If you read the whole article, they also had a major project management
faulure. Even though VNS is dead, something has to replace it.
jim franz