skip to main content
OpenEdge Data Management: DataServer for ODBC
Connecting the DataServer : Connecting a schema holder : Connecting a schema holder at startup : Using a remote DataServer configuration: examples
 
Using a remote DataServer configuration: examples
A remote connection differs from a local connection in that it requires the Host (-H) and Service (-S) parameters.
Use the following command syntax to start OpenEdge:
*In single-user mode
*In a remote-DataServer configuration
*With a local schema holder connected
*With an ODBC data source connected

Syntax on a Windows client:

prowin32 schema-holder-name -db datasrc-name -dt ODBC
-ld logical-datasrc-name -H hostname -S service-name
 -U userID -P password -Dsrv
qt_debug,EXTENDED,PRGRS_CONNECT,server=server-name

Syntax on a UNIX client:

pro schema-holder-name -db datasrc-name -dt ODBC
-ld logical-datasrc-name -H hostname -S service-name
 -U userID -P password -Dsrv
qt_debug,EXTENDED,PRGRS_CONNECT,server=datasrc-name
The following examples start OpenEdge in a remote DataServer configuration. In these examples:
*The schema holder's physical name is odbholder and it is read-only
*The data-source name is sports
*The data-source type is ODBC
*The logical data-source name is mydemo
*The host name is host1
*The service name is odbsrv
*The network type is TCP
*The user ID is bob
*The password is bobpass

On a Windows client:

prowin32 odbholder -RO -db sports -dt ODBC -ld mydemo -H host1
-S odbsrv -U bob -P bobpass
-Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=sqlserv1

On a UNIX client:

pro odbholder -RO -db sports -dt ODBC -ld mydemo -H host1
-S odbsrv -N TCP -U bob -P bobpass
-Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=sqlserv1
Note: This configuration assumes you started the remote DataServer broker using the command line interface. To connect to a DataServer broker started through Progress Explorer you must add the SVUB,1 setting to the -Dsrv parameter and add the -DataServicename parameter.