T.R | Title | User | Personal Name | Date | Lines |
---|
419.1 | Try 800-DEC-GRIT for help | DPDMAI::DAVISGB | Gil Davis DTN 554-7245 | Fri Sep 01 1989 21:40 | 11 |
| After having read the paper I got from the competitive folks
(800-DEC-GRIT), I would hesitate to call what comes from IBM a
'database manager'. Call them and ask for the AS400 database review...
Seems that the dictionary is pretty primitive also...
It sounds like they are planning to fail. After all...if their
application is successful, then they HAVE to convert! Sounds
like....'What the heck doctor....do the filling now, and...while I'm in
the neighborhood...I'll just stop off next week for a root canal..!"
|
419.2 | | SNOC02::ANDERSONK | The Unbearable Lightness of Being | Mon Sep 04 1989 16:37 | 2 |
| Have you seen the rumours on failover/restart times for AS/400
databases?
|
419.3 | Partial Answer | KIKETT::NICHOLSON_PA | | Tue Sep 05 1989 21:02 | 31 |
| > < Note 419.2 by SNOC02::ANDERSONK "The Unbearable Lightness of Being" >
> Have you seen the rumours on failover/restart times for AS/400
> databases?
Yup.
This would be great fodder for most customers, but we're dealing
with a tough nut this time. A typical scenario: We suggested that
the AS/400's journalling was prohibitively expensive. At benchmark
time, IBM declined to turn on journalling. We *did* turn on
journalling in our benchmark; it didn't cost that much, and we thought
it made a strong statement about our solution. Eventually IBM
responded with a letter declaring that journalling on the AS/400
costs only a few percent in CPU utilization. The pro-IBM customer
accepted this as "proof", and as an indication that we were
IBM-bashing.
Bottom line: Any statements we make about IBM in front of this customer
need to be documented by "independent, authoritative" sources.
Probably not a bad idea for all customers, actually.
Back to the original question, which was "What is the compatibility
between AS/400 SQL and DB2 SQL? Can code written for one platform
easily move to the other?" The competitive hotline came through
with a note from the ibm_silverlake notesfile. Note 59.2 there
talks about SQL/400 and addresses the compatibility issue fairly
well. If anyone can add to that, I'll use their ammunition.
Paul
|
419.4 | MIS Week article may be useful | MERIDN::MATTHEWS | It's all Atanasoff's fault! | Fri Sep 08 1989 21:41 | 6 |
| Get ahold of someone who has back issues of MIS Week magazine -
one of the August issues had a wonderful (?) cover story about recovery
problems with AS/400s; some great interviews with end users who
have gotten burned...
Geo.
|
419.5 | Yet another pointer | SRFSUP::MCCARTHY | More fun than kissing a badger | Sun Sep 10 1989 02:31 | 11 |
|
Copies of the articles referred to in .-1 appear in the "Blue
Flashes" notes of the CISM::IBM_SILVERLAKE conference (KP7 to add it
to your notebook). They are also cross-posted in KACIE::IBM.
You will find some information about AS/400 and 370-class db
interoperability (of which there is not much; -ability, that is) in
the most recent "Blue Flash" note.
Regards,
Larry.
|
419.6 | If you wanted ammo to convert them to Rdb/VMS instead... | WIBBIN::NOYCE | Bill Noyce, FORTRAN/PARALLEL | Wed Sep 13 1989 22:13 | 6 |
| During development of VAX SQL, DB2 compatibility was the highest
goal. Now that the ANSI SQL standard is out, that is a higher
priority, but DB2 compatibility is still important.
Also, we have VIDA for DB2, which will allow programs on the VAX
to access DB2 databases as if they were using Rdb.
|