How To Set Up ODBC Connectivity To An AS/400Last reviewed: April 17, 1997Article ID: Q145943 |
The information in this article applies to:
SUMMARYMicrosoft SNA Server 2.11 includes the StarSQL ODBC/DRDA drivers for Windows 3.x and Windows NT client computers. The drivers allow applications that are designed to use the ODBC interface and SQL access to databases on IBM host computers and AS/400 without a host-based database gateway. NOTE: SNA Server 2.11 and SNA Server 2.11 Service Pack 1 include a single license of the StarSQL ODBC/DRDA driver. Therefore, the driver can only be used on a single client computer. If you want to install the driver on multiple client computers, make sure you have a valid SNA Server Client Access License (CAL). You can purchase additional licenses for the ODBC/DRDA driver from StarWare at (510) 704-2000. The SNA Server 2.11 includes the following informational ODBC files:
ADVOPTS.TXT APPLICS.TXT DBSMVS.TXT HINTS.TXT README.TXTSNA Server 2.11 Service Pack 1 includes the following ODBC files:
ADVOPTS.TXT APPLICS.TXT AS400.TXT CMNSRVR.TXT HINTS.TXT JAPANESE.TXT README.TXT MORE INFORMATIONThe configuration procedure of ODBC connection to an AS/400 varies. It depends on the StarSQL driver and OS/400 version on the AS/400. The following information is in AS400.TXT:
One Time Setup for StarSQL to AS/400The following instructions detail the latest setup procedure for StarSQL on an IBM AS/400. On v3r05 & earlier all steps must be carried out by a user with QSECOFR authority or the equivalent. Please read all instructions carefully and take special note of Isolation Level considerations and of differences between installation procedures for OS/400 v3r1 and OS/400 v3r05 & earlier. StarSQL v1.05 and later: Upon successful completion the user should be able to access all physical files (journaled and non-journaled) on an AS/400 running any version of OS/400. StarSQL pre-v1.05: Upon successful completion the user should be able to access all physical files (journaled and non-journaled) on an AS/400 running OS/400 v3r1. NOTE: For access to journaled physical files on OS/400 v3r05 and earlier, follow StarSQL instructions for creating a datasource which uses collections (see "CREATING COLLECTION ON THE AS/400" IN "HINTS.TXT"). Begin Installation:
To access non-journaled physical files on OS/400 v3r1, edit WINDOWS\ODBC.INI (16 bit) or NT Registry (32 bit). Add the following to the StarSQL data source description:
IsolationLevel=0Example: For WINDOWS or WFW (16bit): [STARSQL] Driver=C:\WINDOWS\SYSTEM\swodbc16.dll Description=example for v3r1 Server=RDBELLE CatQual=QSYS2 PkgColId=STARSQL Netlib=SWWAPPC.DLL ReadOnly=No LocalLU=SISYPHUS RemoteLU=ELLE ModeName=QPCSUPP AutoTypDefNam=QTDSQL400 AutoTypDefOvr=37,0,0 UID=PETER IsolationLevel=0 For Windows NT (32 bit): The NT registry is found in WINNT35\SYSTEM32\REGEDT32.EXE. To edit data sources go to HKEY_CURRENT_USER on Local Machine Go to SOFTWARE | ODBC | ODBC.INI | <data source name>. Highlight the appropriate StarSQL data source name. To add IsolationLevel: Go to EDIT | Add Value. Enter "IsolationLevel" with a Data Type of REG_SZ Select OK then enter and add the appropriate number (0) for the Value. The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
|
Additional query words: prodsna
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |