|
Mark Lazarus wrote: > > As in SQL scripts? Sorry about the duplication, I was a day behind and > it kinda crossed in the mail. > Yes, can be stored and run from Ops Nav or AS/400 source files. > If it's completely global, then that's a large potential problem, since > software vendors couldn't really take advantage of it. Plus, from a > definition standpoint it doesn't really make much sense either. > LARGE_AMOUNT may mean one thing to one application and something totally > different to another. > True. But software vendors are already naming libraries that don't conflict. Remember also that the name is not limited to 10 characters. > BTW, is this in V4R4 only? How are the UDB features manipulated / viewed, > etc? Will there be a native implementation? Yes, V4R4 with the SF99104 group PTF, or the 'B' modification as some like to call it. It is not backward compatable, but then what is? Native? No. If you have been paying attention to what IBM says about the new features (column level security, etc.) in DB2 on the 400, then you know that they are not planning on enhancing DDS to support these functions. Commands may appear here and there, but DDS... no. Why build for a single environment? Java is not a single environment. DB2 CS and UDB were not for single environments. If the interface is defined and built as SQL statements, why add the expense on the 400 platform of trying to retrofit the features into DDS? Would you like to pay more or less for the Database? IBM has listened to people claiming that the 400 is just more expensive. More expensive DASD, more expensive operating system. Granted these are initial costs and not ongoing, but still more expensive to get into. The database is part of that cost. DDS is part of that cost. -- =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified AS/400 Professional System Administrator -- IBM Certified AS/400 Professional Network Administrator "The sum of all human knowledge is a fixed constant. It's the population that keeps growing!" +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.