Consultor Eletrônico

Intersolv 16 ODBC 2.5 REQUIRES PRGS 8.1B Client/Networking

As of 6/16/97 both Local and Remote Brokers are supported using 8.1b
client
etworking and Intersolv's 2.5 16bit ODBC driver for Progress.

8.1b (or higher) Client/Networking are the only supported versions of
Progress to use with Intersolv's 16bit ODBC driver. Clients must be
Win3.1 or Windows 95

THE FOLLOWING PLATFORMS / ENVIRONMENTS ARE CURRENTLY SUPPORTED

Remote OID-Remote DB in Self Service NT and UNIX
Remote OID-Remote DB in Client Server UNIX
Local OID-Local DB Single User LOCAL
Local OID-Local DB Multi User LOCAL
Local OID-Remote DB Multi User NT and UNIX


Installation / Configuration Procedures

1. Install a Progress Client that has v8.1b+ Client Networking
capability (ProVision, 4GL Dev Sys, Client Networking, or Person
Database) on the client (non NT Windows).

2. Install the INTERSOLV 16bit ODBC 2.5 driver for PROGRESS.

3. Configure the Intersolv Driver to Connect to a Progress Database.
From your client click on Control Panel, then double click on ODBC.
Select 'Add', select 'INTERSOLV 2.50 Progress', then 'OK'.
'Datasource Name' and 'Description' can be whatever you want.
Enter the physical database name for the 'Database Name'.

OID/OIB Connection Options.

If using a Remote OIB/OID change 'OID/OIB Location' to Remote.
The only 'Protocol' supported is TCP. Enter a valid service name
for 'Service Name'. Enter the host name where the Database is
started under 'Host Name'.
If using a Local Broker change 'OID/OIB Location' to Local.
The only 'Protocol' supported is WIPC. Enter a non valid Service
Name under 'Service Name'. I usually call it something like
JUNK. The Local Broker gets spawned automatically, so there is
no Broker to start manually.

Database Connection options

If the Progress Database is running on the NT platform and the
'OID/OIB Location' is set to Remote. the
'Database Access Mode' must be set do Direct. The 'Database
Path' must be the location of the Database i.e. \DATA\.
'Database Operating System' must be set to the correct Operating
System. If the 'OID/OIB Location' is set to Local then the
'Database Access Mode' must be via Server. The 'Protocol' can b
be a valid protocol; NETBIOS, SPX, TCP. The 'Service Name' and
'Host Name' must be valid names.

If the Progress Database is running on a UNIX platform the
'Database Access Mode' can be Direct or via Server.
For Direct connection follow the instructions listed above. For
via Server conection you will need to specify the 'Protocol';
TCP is the only tested protocol under UNIX. The 'Service Name'
and 'Host Name' must be valid names.

5. Rename \WINDOWS\SYSTEM\PROESQL.DLL PROESQL.OLD and
copy ESQL01.DLL from %DLC%\BIN to WINDOWS\SYSTEM\ as PROESQL.DLL.
i.e. COPY C:\DLC\BIN\ESQL01.DLL C:\WINDOWS\SYSTEM\PROESQL.DLL

6. Verify %DLC%\BIN is included in the system path.

7. You will need to set the environment Variable DLC to the %DLC%
directory. i.e. add the statement SET DLC=C:\DLC to the
AUTOEXEC.BAT file.


NOTE
THE FOLLOWING DATABASE VERSIONS HAVE BEEN TESTED IN THE PREVIOUSLY
DESCRIBED ENVIRONMENTS.

NT UNIX VMS
8.1A 8.1A 8.1A
8.0B 8.0B
7.3B 7.3D
7.3C

When using a Remote OIB/OID on both NT and UNIX you need to set the
following environment variables on the system where the OIB/OID is
located:

NT
prooidrv=c:\dlc\bin\oibrkr32.exe
prooibrk=c:\dlc\bin\oidrvr32.exe

UNIX
prooidrv=$DLC/bin/_prooidv
prooibrk=$DLC/bin/_prooibk


Other related kbase's...

15151 Remote NT broker configuration
16723 Remote UNIX broker configuration
16431 INTERSOLV Driver Specifications
16663 4389 errors with Intersolv's ODBC
16488 HITCHHIKERS GUIDE to Intersolv's ODBC 2.5
16717 Local OID-Local DB Single User
16718 Local OID-Local DB Multi User
16719 Local OID-Remote DB Multi User
16721 Remote OID-Remote DB in Self Service
16722 Remote OID-Remote DB in Client Server
16725 Intersolv's ODBC- Required Client Environment Variables

Progress Software Technical Support Note # 16751