OpenEdge Data Management: DataServer for Microsoft SQL Server

Connecting the DataServer
6–4
For diagnostic purposes only, it is acceptable to bypass the NameServer connection and
connect directly to the broker instance. To do this, specify the reserved DataService name
none or add the -DirectConnect parameter as follows:
Or
-DataService none
-DirectConnect
• Set the -S parameter to one of the following:
– The port number assigned to the controlling NameServer (when the -DataService
value is not none) or the port number of the broker instance that you started in the
Explorer (when the -DataService value is none)
– The service name in your services file whose associated port matches the port of
the controlling NameServer (when the -DataService value is not none) or the
broker instance that you started in the Explorer (when the -DataService value is
none)
• Set the -H parameter to the name of the machine where the NameServer and/or broker
instance are running.
If you do not set the required -Dsrv SVUB,1 and optional -DataService data–service
connection parameters as described in this section, the client is assumed to be configured for a
standard OpenEdge broker and the -H and -S parameters are used to locate a ProBroker
executable on the appropriate host machine. By setting the SVUB parameter on, you redirect the
-H and -S parameters to locate the appropriate NameServer and/or broker on the host machine.
The following example illustrates how to use these connection parameters for a client that
connects to a NameServer:
CONNECT mssholder -db mssdemo -dt MSS -U bob -P bobpass -H host1
-S mssport -DataService mssbroker1 -Dsrv SVUB,1.