|
Dave, I think Joe's reply pertty much covers what you've said here: "But, alas, from the S/38 to now, the S/38 and its follow-ons are not truly relational and most of the files found thereon are generated as flat files although some are using what they have of a DB2-type engine. Oh, my, I have just committed blasphemy, at least per Rochester and those that follow their dogma. I know, I know, IBM Rochester has told you for decades the S/38, AS/400, iSeries, etc., is a relational database. I believed that as well back in 1984 after being indoctrinated by the S/38 folks in IBM classes. But sadly, it was and is not true." Let me add my observations: the problem isn't DB2 for iSeries, as DB2 for iSeries is as relational as any other RDBMS out there. The problem is most databases found in DB2 for iSeries aren't relational. For a relational DB to be managed by a relational DBMS, there have to be relationships between the data defined. All too often, DBs on the iSeries don't have primary and foreign keys defined. Charles Wilt iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.