Re: Modernization and multi-member files

Joe,

Gee, in this case, I'm not arguing IBM vs. the rest or the RDBMS nor am I arguing IBM is not the most ANSI compatible. I'm speaking mainly of the difference in two things that make DB2/400 very different than the rest of its "brothers" in IBM. One, and we've been down this road before, Rochester's implementation of its DB2 vs the rest of IBM. Rochester found a way to make a DB2 on the i5 that would have somewhat of a look and feel of a DB2, so they could claim they are in the "family" but it is not, nor does it operate the same; and I'm not talking the single level store stuff nor the ANSI SQL capability.

Second, the WAY the implementation is used by a lot of the i world; not anything like the rest of IBM's DB2 shops. That's why the rest of the IBM DB2 community tilts their head like the RCA dog when i5 folks talk of their OS having a DB2. I know because I've brought it up at DB2 User Group meetings, banging the IBM i drum. While they are polite, they consider all the rest of the DB2s, VM, VSE, MVS, AIX and Windoz, even old DB2/2, as being a DB2 but not the i5. My "bullet points" above are some reasons why.

I'm sure many here are saying... OK, so what. The answers are contained in some of my previous missives on this subject. But, the most compelling is... to make the i5 able to compete in the market place after the current batch of old architecture folks are gone. But, perhaps I'd better stop tilting at this windmill as it's clear I"m goring someone's ox, committing blasphemy and folks don't want to hear non-dogma views of their system's future.

Dave