|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Actually the 400 started out as the Least Common Denominator of the S/38 and the S/36. There were a lot of features in the S/36 that were sorely missed, (at least until DDS was dumped for SQL). For example, you could define a file in IDDU and restrict the values for certain fields. Then if you ran the S/36 equivalent of UPDDTA it would prevent you from doing so. When we migrated that to the AS/400 that was dropped. The DDS keywords that were supposed to do the same thing were only there to make SDA try to adopt some of these for screens. They were ignored by UPDDTA. Now SQL with constraints seems to have plugged that glaring hole. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Chuck Lewis" <clewis@iquest.net> Sent by: midrange-l-admin@midrange.com 12/18/2002 10:50 AM Please respond to midrange-l To: <midrange-l@midrange.com> cc: Fax to: Subject: RE: Thats all folks! James wrote: <By the way, doesn't that paragraph make people happy to see how much good work was done by IBM way back in 1991? The 36 was a pain but the underlying architecture was good.> Actually the core of OS/400 at the time was from the S/38... goes back even FURTHER :-) Chuck _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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-2024 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.