Kbase 16979: Actuate DEVWB to VMS - How to connect
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/06/1998 |
|
Actuate DEVWB to VMS - How to connect
How to connect Actuate DEVWB to a Progress db on VMS :
To connect Actuate to a db on VMS you need to use the ESQL32.DLL on
the PC side as to connect to any other db on any platform. On the
server side you need to use OIB local to the VMS machine (the
configuration is similar than other platforms), to start the OIB use:
$ progress/oib=start/host=<host>/service=<service>
etwork=tcp
Be sure to have defined the logical names PROOIBRK and PROOIDRV (e.g):
$ define/system prooibrk bin:_prooibk.exe
$ define/system prooidrv bin:_prooidv.exe
Define specific services (assuming TCP) in sys$system:services.dat
(unix style) as
oibsv 3000/tcp
oibsv1 3010/tcp
oibsv2 ...
oibsv3 ...
Define the same services on the PC side as well.
Is suggested to connect to the Progress db broker using shared memory,
so in the Actuate connection parameters type -db dbname as the 1st
parameter (Db connection list). In this way the performance is
better:
1) The OIB is local on VMS
2) The connection to the Progress db is Shared memory instead of
using networking.
VERY IMPORTANT. The customer should have the patch version 7.3c13 as
minimum on the VMS machine. Or 8.1a + 8.1a01 (the patch a01 is
required because there was a bug on the OIB for 8.1a when using 32 bit
drivers on the PC).
svi
Jun-24, 97
Progress Software Technical Support Note # 16979