Re: DDS Support (Re: NT web server access to AS400) -- MIDRANGE-L

Rob,

The main advantage to the customer is that IBM would be focusing all of
their resources on a single DDL instead of duplicating functionality across
both of them. I would hope that this would mean richer enhancements in a
more timely manner.

Now, you can argue that the sole DDL should be DDS. Personally, it doesn't
matter much to me whether it is DDS or SQL, because the actual time spent
working with the DDL is a tiny fraction of the overall development time on
most projects. Moreover, the syntax is so simple with both, that training a
new developer to use either is a non-issue.

Clearly, IBM feels that SQL is the way to go. Perhaps it is because they are
trying to standardize the DB feature set across all platforms. This (IMO) is
a good thing for us as developers. I'll grant you that if all you use is an
AS/400, and all you ever intend to use is an AS/400, then this DB
standardization offers no benefit for you. However, for those of us who
_have_ to write applications on multiple platforms (because an AS/400 is not
the best tool for every job), then what they are doing should simplify our
lives - and therefore it increases the likelyhood that we will deploy a
version of DB2 across all of our platforms.


Regards,

John Taylor
Canada

----- Original Message -----
From: "Rob Berendt" <rob@dekko.com>
To: <MIDRANGE-L@midrange.com>
Sent: Tuesday, June 27, 2000 17:07
Subject: Re: DDS Support (Re: NT web server access to AS400)


> What advantage would there be to the customer?
> SQL enhancements move at the speed of slugs.
> DDS comes up with ideas that the SQL should target itself
> to supporting.  Sort of like competition is good for the market.
> IBM lacks in supporting the new enhancements.  For example, you'd
> think that there is a good business function to use DECS to transfer
> BLOB information between Notes and DB2.
>
>
>
>
>
> john.taylor@telusplanet.net on 06/27/2000 05:51:47 PM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To: MIDRANGE-L@midrange.com@Internet
> cc:
> Fax to:
> Subject: Re: DDS Support (Re: NT web server access to AS400)
>
> Rob,
>
> Good point. Although that is not so much a deficiency of SQL, as it is a
> feature of DB2/400. What else can you think of?
>
> On another note, what harm would come of "stabilizing" DDS at this point,
> and focusing their (limited) resources on a single DDL? Presumably, IBM
> wouldn't even consider dropping support  for existing DDS features, so you
> wouldn't lose any existing functionality.
>
> Regards,
>
> John Taylor
> Canada
>
> ----- Original Message -----
> From: "Rob Berendt" <rob@dekko.com>
> To: <MIDRANGE-L@midrange.com>
> Sent: Tuesday, June 27, 2000 13:47
> Subject: Re: DDS Support (Re: NT web server access to AS400)
>
>
> > The combiniation of a View and an Index that a logical file with select
> and keys will give you.
> >
> >
> >
> >
> > john.taylor@telusplanet.net on 06/26/2000 05:57:55 PM
> > Please respond to MIDRANGE-L@midrange.com@Internet
> > To: MIDRANGE-L@midrange.com@Internet
> > cc:
> > Fax to:
> > Subject: Re: DDS Support (Re: NT web server access to AS400)
> >
> > Al,
> >
> > I always considered the various field/file reference abilities to be a
> > rather poor substitute for a decent data dictionary. Maintaining data
> > type/size consistency is probably one of the most basic functions in any
> > data dictionary tool. Another basic function of such a tool is the
> > generation of SQL statements for you.
> >
> > I assume that you already knew this, so you must have something else in
> > mind. Now I'm curious. Aside from multiple member support, what else do
we
> > get with DDS that can't be done with SQL and a dictionary?
> >
> > Regards,
> >
> > John Taylor
> > Canada
> >
> > ----- Original Message -----
> > From: "Al Barsa, Jr." <barsa2@ibm.net>
> > To: <MIDRANGE-L@midrange.com>
> > Sent: Monday, June 26, 2000 13:53
> > Subject: DDS Support (Re: NT web server access to AS400)
> >
> >
> > > At 02:15 PM 06/26/2000 -0500, you wrote:
> > > >Has anyone else heard that IBM is dropping (or maybe dropping support
> is
> > > >the wrong word) support for DDS. I heard this and found it shocking.
> > > >Just curious no flames please.
> > >
> > > Clearly DDS is no longer strategic to IBM.  They want everybody to go
> with
> > > SQL for file definition, which IMHO is brain dead.
> > >
> > > SQL does not support all of the features of DDS.  AS/400 databases
> contain
> > > many less database design errors than other databases, due to the
> > existence
> > > of the RLDREF keyword.
> > >
> > > IBM is of the opinion that they want to reduce everything to it's
lowest
> > > common denominator.  To force you to go to SQL, new database functions
> are
> > > only being added through SQL.  We are actively looking at extending
DDS
> > > through TAA Tool.  This is not a pre announcement, but something under
> > > investigation.
> > >
> > > Hey IBM, do it the AS/400 way, and you'll get a better product.
> > >
> > > Al
> > >
> > >
> > >
> > >
> > >
> > >
> > > +--------------------------------------------------+
> > > | Please do not send private mail to this address. |
> > > | Private mail should go to barsa@ibm.net.         |
> > > +--------------------------------------------------+
> > >
> > > Al Barsa, Jr. - Account for Midrange-L
> > > Barsa Consulting, LLC.
> > > 400 > 390
> > >
> > > Phone: 914-251-1234
> > > Fax: 914-251-9406
> > > http://www.barsaconsulting.com
> > > http://www.taatool.com
> > >
> > > +---
> > > | 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
> > > +---
> > >
> >
> > +---
> > | 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
> > +---
> >
> >
> > +---
> > | 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
> > +---
>
> +---
> | 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
> +---
>
>
> +---
> | 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
> +---

+---
| 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
+---