HP 3000 Manuals HP 3000 Manuals
Installing and Configuring the ODBC Interface
Now that the files are on the PC, you can install PC API. The ODBC
interface uses 500 KBytes of disk storage. To install the ODBC
interface, do the following:
* From your PC, type the following to extract the ODBC files from
the self-extracting file:
C:\PCAPI> mkdir ODBC
C:\PCAPI> cd ODBC
C:\PCAPI\ODBC> ..\hpodbc
* Run Microsoft Windows.
* Ensure that all applications other than Program Manager are
closed.
* From the File menu, click on Run.
* Execute setup to install the PC API files. Use the path where
your PC API files are located. For example:
c:\pcapi\odbc\setup
* Press Continue to get to the Install Drivers dialog box.
* From the Install Drivers dialog box, select the HP ALLBASE/SQL
driver by clicking on it and then click on OK to install the
files. All files will be copied to \WINDOWS\SYSTEM directory and
the ODBC Administrator will be installed in the Control Panel with
the icon name of ODBC. The ODBC Administrator is used to add,
modify, or delete Data Source Names (DSN).
* From the Data Sources dialog box you can configure Data Source
Names. Click on Setup.
* From the HP ALLBASE/SQL ODBC Setup dialog box, type in the
required data. Then click on OK.
* From the Data Sources dialog box, click on Close.
You can add, modify, or delete Data Source Names at any time by
using the ODBC Administrator. To use the ODBC Administrator, open
the Control Panel and click on the ODBC icon.
* Copy the ODBCVIEW.HP file from your PC client to the server. For
example:
C:\> cd windows\system
C:\WINDOWS\SYSTEM> DSCOPY odbcview.hp
Host#UserName/Passwd.SomeAccount/Password#odbcview
* Execute the odbcview command file on the server for each
DBEnvironment. For example:
isql=> CONNECT TO 'DBEName';
isql=> START odbcview;
isql=> exit;
Note: ODBCVIEW requires DBA authority.
The ODBCINST.INI file is created when you install the ODBC interface.
The ODBC.INI file is created and maintained by the ODBC Administrator.
Both of these files exist in your \WINDOWS directory. Here is an example
of what they look like.
ODBCINST.INI
------------
[ODBC Drivers]
HP ALLBASE/SQL=Installed
[HP ALLBASE/SQL]
Driver=C:\WINDOWS\SYSTEM\allbase.dll
Setup=C:\WINDOWS\SYSTEM\allbassp.dll
ODBC.INI
--------
[ODBC Data Sources]
Parts=HP ALLBASE/SQL
[PARTS]
Driver=C:\WINDOWS\SYSTEM\allbase.dll
Description=Parts Database
LastUser=#mpeix/HP3000:PartsDBE.SomeGrp.SomeAcct#Session1,SomeUser.SomeAccount
DefaultIsolation=
The complete syntax for the LastUser= line is:
#mpeix/Host:DBEName[,[NetType][,ConFlag]]#UserName
mpeix is the keyword that indicates that this is an
MPE/iX connection string.
Host is the host name of the database server. This is a
character string containing up to 8 characters.
DBEName is the name of the DBEnvironment containing one or
more databases.
The syntax for the fully qualified DBEName is:
DBEName[.Group[.Account]]
NetType specifies the networking software residing on the
PC that is to be used to communicate with the
server. Typically, you specify NetType only when
you have more than one type of supported data
communications software loaded on the client.
NetType has the following optional values:
lw directs PC API to use Novell LAN WorkPlace
provided by Novell.
nw directs PC API to use NetWare. If you
specify nw, NetWare/iX must be running on the
database server. The server node number and
net number need to be specified:
nw [ServerNodeNumber][NetNumber]
ws directs PC API to use the "Windows Sockets"
interface. This interface is for network
programming under Microsoft Windows.
sk directs PC API to use HP Sockets.
ip directs PC API to use NetIPC (HP Network
Services). Enter the NetType in lower case.
The default order that PC API uses to search
for data communications software is shown in
the above list.
For example, suppose you have both NetWare
and NetIPC loaded on your PC client. Using
the default search order, PC API always
attempts to use NetWare to communicate with
the database server. In order to direct PC
API to use NetIPC rather than NetWare, you
need to override this default by specifying a
NetType of ip.
ConFlag turns conversion on.
an converts the ROMAN8 character set to the ANSI
character set on the PC client and then
converts the data to ROMAN8 when returned to
the database server.
r8 is the default. There is no conversion.
UserName is the MPE/iX logon. The syntax for LogonString
is:
[SessionId],User[/UserPass].Account[/AcctPass][,Group[/GrpPass]]
The DefaultIsolation= line allows you to optionally specify one of the
four ALLBASE/SQL isolation levels:
* Repeatable Read (RR)
* Cursor Stability (CS)
* Read Committed (RC)
* Read Uncommitted (RU)
For more information, refer to the "Isolation Levels" section later in
this chapter.