|
Nice find, Steve. Here're a couple more: IBM's iSeries DB2 site at http://www.iseries.ibm.com/db2 An article from Summer of 1999 by Paul Conte in DB2 magazine http://www.db2mag.com/db_area/archives/1999/q2/99sp_conte.shtml HTH Vern -------------- Original message -------------- ---snip--- > > Dave - > > Definitions may differ, but _my_ definition of a "Flat" file is one that has > no external field definitions. A "Flat" file can be created easily by using > CRTPF with a record length specified instead of a DDS source member. > > In a given AS/400 - iSeries - i5 system, depending on the file structures > and their relationships, I would be more inclined to call a given DB2/400 > file a "non-relational" file rather than a "Flat" file... > > And, as others have mentioned, it is possible to build a non-relational > database in any SQL database... > > IMO, > A "Flat" file doesn't have external field definitions other than one large > field that contains all of the data. > > When using "Flat" files in programs, you generally use program-described > files with F & I specs in RPG or FD's in copy books for COBOL to describe > the fields in the file. > > As most of us know IBM midrangers know (or _should_ know), > the System/38 was born of what was originally known as the > "Future System" project within IBM's mainframe division. > > The "Future System" project began _before_ Dr. Codd first proposed > his relational database rules in 1970, and when Rochester got hold > of it the System/38 developers put more functionality (usability-wise) > into the "no-name" System/38 database than existed in any commercial > IBM mainframe database at the time (circa 1978). > > I'd like to see a one of the IBM database guys weigh in here to > address the 12 design points of Codd's model and how DB2/400 > measures up, particularly in light of this quote from an IBM DB2 > document. > > From > http://www-128.ibm.com/developerworks/db2/library/techarticle/0301jones/0301jone > > s.html > > > > A brief history of DB2 > > A series of research projects have been a steady source of technology for > the DB2 family since the beginning: > > The System R project resulted in the first IBM implementation of the > relational model. A project called ARIES delivered row-level locking > technology used throughout the database industry today. > > Cost-based query optimization has been an area of intense effort and > innovation ever since the System R days. The R Star project extended the > relational model to distributed system environments. > > The Starburst project focused on making the relational model extensible to > handle new forms of information and new kinds of optimization strategies. > > The Garlic project brought an emphasis on data federation, allowing data in > diverse systems, not just DB2 systems, to be managed together. > > Most recently, a technical preview based on DB2 has demonstrated the > integration of information from Web services and the use of XQuery as an > additional and powerful query language for managing XML content. > > The first implementation of relational technologies from the initial System > R project was the database integrated into the System/38 server in 1980. > > In 1982, the SQL/DSTM product was delivered on the mainframe operating > systems VM and VSE, also based on System R. > > DB2, formally called DATABASE 2, was born in 1983 on MVSTM. > > The database manager in OS/2® Extended Edition in 1987 was the first > relational database on distributed systems. > > SQL/400® for the new AS/400® server emerged in 1988. > > New DB2 editions were delivered on AIX® (1993), HP-UX and Solaris (1994), > Windows® (1995), and Linux (1999). > > > > In addition, read Wayne O. Evans account of the System/38 project here: > http://www.woevans.com/CPFDesign.pdf > > Regards, > Steve Landess > Austin, Texas > (512) 423-0935 > > ----- Original Message ----- > From: "Dave Odom" > To: > Sent: Monday, March 07, 2005 5:27 PM > Subject: Logical File or OPNQRYF or anyother way ? - Legacy iSeriesFlat > Files > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
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.