LOTUS CONNECTORS
/QIBM/UserData/LOTUS/DOMINOXXX
For example, the odbc.ini for an LEI server running Domino 8x is located at the following address:
/QIBM/UserData/LOTUS/DOMINO8x/EITODBC/odbc.ini
Editing the odbc.ini file for i5/OS Users
To edit the odbc.ini file, use the EDTF command specifying the path to the odbc.ini file. For example, to edit the odbc.ini file of an LEI server running Domino 8x enter the following command at the command line:
EDTF '/QIBM/UserData/LOTUS/DOMINO8x/EITODBC/odbc.ini'
Note Do not use a Windows-based text editor to edit the odbc.ini file. Lines in the odbc.ini file must end with a line feed (LF) character. Many text editors often end lines with a carriage return and line feed (CRLF), which will yield errors when attempting to use the odbc.ini file. If an editor that ends lines with CRLF has already been used, you can remove the CR characters from the odbc.ini using the instructions in the section entitled "Removing CR in the odbc.ini File" below.
Note All /QIBM/ProdData/LOTUS/DOMINOXXX/... paths in the odbc.ini are relative to the version of Domino that the server is running. These paths change dependent on the version of Domino the Domino server is running. For example, for a Domino server running Domino 8, these paths would appear as shown below:
/QIBM/ProdData/LOTUS/DOMINO8x/...
A sample odbc.ini file that would be used on a Domino 8x server is shown below for use when connecting to either the Sybase Wire Protocol or Oracle Wire Protocol using an i5/OS system. Instances of the term "Data Direct" are replaced with the term "IBM Lotus OEM" in the .ini file.
[ODBC Data Sources]
DB2 Wire Protocol= 5.2 DB2 Wire Protocol Driver
dBase=IBM Lotus OEM 5.2 dBaseFile(*.dbf)
FoxPro3=IBM Lotus OEM 5.2 dBaseFile(*.dbf)
Informix=IBM Lotus OEM 5.2 Informix
Informix Wire Protocol=IBM Lotus OEM 5.2 Informix Wire Protocol
Oracle=IBM Lotus OEM 5.2 Oracle
Oracle Wire Protocol=IBM Lotus OEM 5.2 Oracle Wire Protocol
Progress9=IBM Lotus OEM 5.2 Progress9
Progress10=IBM Lotus OEM 5.2 Progress10
SQLServer Wire Protocol=IBM Lotus OEM 5.2 SQL Server Wire Protocol
Sybase Wire Protocol=DataDirect 5.2 Sybase Wire Protocol
Text=DataDirect 5.2 TextFile(*.*)
[DB2 Wire Protocol]
Driver=/opt/odbc/lib/LOdb220.so
Description=DataDirect 5.2 DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Collection=OS/390 and AS/400 (leave blank for DB2 UDB)
Database=DB2 UDB (leave blank for OS/390 and AS/400)
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=DB2 server host
IsolationLevel=CURSOR_STABILITY
Location=OS/390 and AS/400 (leave blank for DB2 UDB)
LogonID=UID
password=PWD
Package=DB2 package name
PackageOwner=
TcpPort=DB2 server port
WithHold=1
[DB2V71]
Database=DB2V71
IpAddress=rage
Package=DDODBC
TcpPort=50000
[Informix Wire Protocol]
Driver=/opt/odbc/lib/LOifcl20.so
Description=DataDirect 5.2 Informix Wire Protocol
ApplicationUsingThreads=1
CancelDetectInterval=0
Database=db
HostName=Informix host
PortNumber=Informix server port
ServerName=Informix server
TrimBlankFromIndexName=1
[InformixDSN]
Database=qetest
HostName=flood
PortNumber=1526
ServerName=informix_940
[Oracle Wire Protocol]
Driver=/opt/odbc/lib/LOora20.so
Description=DataDirect 5.2 Oracle Wire Protocol
ArraySize=60000
CachedCursorLimit=32
CachedDescLimit=0
CatalogIncludesSynonyms=1
CatalogOptions=0
DefaultLongDataBuffLen=1024
DescribeAtPrepare=0
EnableDescribeParam=0
EnableNcharSupport=0
EnableScrollableCursors=1
EnableStaticCursorsForLongData=0
EnableTimestampWithTimeZone=0
HostName=Oracle server
LocalTimeZoneOffset=
LockTimeOut=-1
PortNumber=1521
ProcedureRetResults=0
SID=Oracle SID
UseCurrentSchema=1
[ODBCToOracle10]
SID=flood
[SQLServer Wire Protocol]
Driver=/opt/odbc/lib/LOmsss20.so
Description=DataDirect 5.2 SQL Server Wire Protocol
Address=SQLServer host,SQLServer server port
AnsiNPW=Yes
QuotedId=No
[ODBCToSQLServer7]
Address=frost,1433
Database=Tracey
[Sybase Wire Protocol]
Driver=/opt/odbc/lib/LOase20.so
Description=DataDirect 5.2 Sybase Wire Protocol
ApplicationName=
ArraySize=50
Charset=
CursorCacheSize=1
EnableQuotedIdentifiers=0
InitializationString=
Language=
NetworkAddress=Sybase host,Sybase server port
OptimizePrepare=1
PacketSize=0
RaiseErrorPositionBehavior=0
SelectMethod=0
WorkStationID=
[ODBCTOSybase12]
Database=SILK_DATA
NetworkAddress=frost,5000
[ODBC]
IANAAppCodePage=4
InstallDir=/opt/odbc
Trace=0
TraceDll=/opt/odbc/lib/odbctrac.so
TraceFile=odbctrace.out
UseCursorLib=0
The odbc.ini file is supplied with example connections for various data sources. To create a new data source name (DSN), copy one of the existing examples and change the required entries to match those of the data source. In the example above, the section starting with "[ODBCtoOracle9]" is the configuration information for the data source named ODBCtoOracle9. It uses the Oracle Wire Protocol driver (specified by the "Driver="line) to connect to a system named tsunami (specified by the "HostName=" line) on port 1521 (specified by the "PortNumber='" line) with SID tsunami (specified by the "SID=" line). You may need to specify the fully-qualified host name for the "HostName=" entry. The required options vary for each type of data source. For details on configuration options see the following user documentation:
/QIBM/ProdData/LOTUS/..../EITODBC/books/odbc/books.pdf
Note When using an Oracle Wire Protocol ODBC data source, ProcedureRetResults=1 must be set in the Data Source configuration in order to get result sets from stored procedures.
Note All /QIBM/ProdData/LOTUS/... paths in the odbc.ini depend on which Domino version the server is running, as described above.
Removing CR in the odbc.ini File
If the odbc.ini file was edited using the CRLF line terminator instead of the LF line terminator, you can remove the CR character using the following procedure:
1. From the command line type "CALL QP2TERM" (no quotes) to start a PASE terminal session
2. Change to the directory where the odbc.ini file is located. An example is shown below: