RE: SQL SERVER/ISERIES INTEGRATION -- MIDRANGE-L

Yes, you are exactly correct. It is managed by the Open Group. It was
originally supposed to rival the MS ODBC standard, but neither were accepted
as standards across SQL server databases, mainly because MS and Oracle
refused to play and IBM didn't think that selling "connections and seat
licenses" to connect to a database would fly. So much for IBM's visionaries
of that day.

Yes, you need Oracle Code on your AS/400 or iSeries system. Last I heard, it
was VERY VERY expensive and did have CLI support to go both ways. It was
also chargeable for each connection FROM the iSeries to the Oracle database.
>From what I remember (and it's been about 6-7 years), it was extremely
large, slow and didn't work very well. Of course, I can't say much since
almost everything Oracle does is pretty much that way.

The only reason I'm even up on this is because our package is actually an
ODBC manager as well as an ODBC driver to connect to ODBC compliant servers
without any software on the remote server. We are still working on the
Oracle connections and should have it completed before the lawyers finish up
with all of the nasty letters we get from Oracle. We are in general release
with the MSSQL driver and have the testing completed for Sybase and MySql,
but have only had demand for MSSQL.

John Brandt 
iStudio400.com 
(903) 523-0708 
Home of iS/ODBC - MSSQL access from iSeries and RPG. 




-----Original Message-----
From: CWilt@xxxxxxxxxxxx [mailto:CWilt@xxxxxxxxxxxx]
Sent: Tuesday, November 09, 2004 3:57 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: SQL SERVER/ISERIES INTEGRATION


John

Sorry, I was mixing up DRDA and CLI.

But DRDA is not just an IBM standard.  While IBM created DRDA, it is now
managed by the Open Group.  

Is Oracle really DRDA compliant? Seems they have a "Transparent Gateway"
option, but it only allows Oracle to access DB2 not the other way around.

Interesting, I found this quote:
KEY FEATURES
Ease of Implementation
# Takes advantage of the native DRDA capabilities of DRDA servers
# Requires no Oracle code on your DRDA server system 

Yet the manual specifically says:
1.8.1 Gateway Changes to Your AS/400 System

Installing the gateway on your AS/400 system produces the following changes
to the system:

   1. A library is created, with the instance name as given in the first
installation panel. (For an example, refer to Example 4-1, "Install Oracle
Transparent Gateway Panel"). Almost all of the gateway will be found in this
library, with the exception of some objects dealing with service programs
and the items mentioned in parts 3 and 4 of this list.
The gateway can also be installed into a previously-created DB2/400 SQL
COLLECTION that contains nothing but objects of type *FILE (physical and
logical files), a journal of type *JRN, a journal receiver of type *JRNRCV,
and a data dictionary object of type *DTADCT. The collection name will be
the name of the library in which these objects are created by DB2/400.
   2. A user profile is created. The user profile has the same name as the
library that is created when you install the gateway.
   3. A subdirectory entry is created in the /home directory in the
Integrated File System. The subdirectory entry name will be the same as the
instance name. Thus, if ORACLE is the instance name, then a subdirectory
node will be created at /home/ORACLE. Further nodes will be created below
this node. Agent trace files will appear (if requested) in a subdirectory of
the created node. An initialization file will also appear in a subdirectory
of this node.
   4. A library named ORASRVLIB is created. If the installation software
finds that it must install the service programs that are found on the
installation medium, then a library with a name such as ORASRVnnnn (where
nnnn is a number) will be created. The relevant service programs and a file
that is used for NLS transactions will be placed in that library. Additional
files or members within files may be added to the ORASRVLIB library.
   5. A message queue with the name of the installation library is created
in the QUSRSYS library. This is as a result of using the CRTUSRPRF command
to create the user profile that corresponds to the installation library.

Wouldn't that be considered "Oracle code on your DRDA server system"???

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: John Brandt Sr. [mailto:pgmr@xxxxxxxxxxxxxxx]
> Sent: Tuesday, November 09, 2004 1:34 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: SQL SERVER/ISERIES INTEGRATION
> 
> 
> ODBC is the Microsoft connectivity standard and has nothing 
> to do with DRDA.
> DRDA is the IBM connectivity standard.
> The only "DRDA" compliant databases I am aware of are DB2 (PC, Server,
> Linux, Unix, iSeries and Mainframe) and Informix. Oracle and 
> Sybase both
> have DRDA connectors as options. DB2 is ODBC compliant as a 
> server, not as a
> client.
> Microsoft does not have a DRDA connector, but you can use 
> ODBC or JDBC to
> connect "FROM" a MSSQL server to a DRDA database.
> 
> John Brandt 
> iStudio400.com 
> (903) 523-0708 
> Home of iS/ODBC - MSSQL access from iSeries and RPG. 
> 
> 
> 
> 
--
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.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.789 / Virus Database: 534 - Release Date: 11/7/04
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.789 / Virus Database: 534 - Release Date: 11/7/04