Progress
DataServer
for ODBC Guide
Connecting a Schema Holder at Startup
Progress supports connection parameters that you can use to connect both the Progress schema holder and an ODBC data source at startup. These parameters control how your system connects to a database. When the DataServer runs in a remote configuration, your startup command or parameter file must always include parameters that control networking options.
Table 4–1 describes the database connection parameters that you use when you connect to a schema holder and an ODBC data source through the DataServer.
Table 4–1: DataServer Connection Parameters Parameter Status Description Database Type ODBC(-dt ODBC) Optional Specifies that the type of the target data source is ODBC. Note that the data source must be a supported ODBC data source. Physical Database Name(-db) Required Indicates the name by which Progress recognizes the ODBC data source to which you want to connect. This name must match the name that you used when you registered the data source as an ODBC data source. Logical Database Name(-ld) Optional Specifies the logical name of the ODBC data source. This is the name that you use to refer to the data source in your applications. You must use this parameter only when the logical data-source name differs from its physical name. This name should match the logical database name that you defined in your schema holder.For example, your applications might refer to the Sybase demo database as mydemo. In this case, the physical name is demo, and the logical name is mydemo. Host Name(-H) Required for remote DataServer Indicates the name of the host machine in the network. Service Name(-S) Required for remote DataServer Indicates the name of the service that you are calling. If you use the NameServer with Progress Explorer, specify the service name or IP address of the host machine where the NameServer resides. If you are using probrkr, ProControl, or the Progress Explorer without a NameServer, specify the service name or IP address of the host machine where the broker resides. Network Type(-N ) Optional Indicates the network type. TCP is the only possible value. User ID(-U) Required if the ODBC data source requires it Supplies the login name that the DataServer uses to log into the ODBC data source. Password(-P) Required if the ODBC data source requires it Supplies the password that the DataServer uses to log into the ODBC data source. Different login name and password combinations allow for different levels of user privileges. Data Service(-DataService) Required for Progress Explorer connections Specifies the data service the NameServer uses. This must be used in conjuction with the -Dsrv option SVUB,1. For more information, see the "Starting and Stopping a Broker Process from the Progress Explorer and Connecting a Client" section. Single–User Mode(-1) Optional Specifies that a schema holder is used in single-user mode. Single–User Mode is the default unless a server is started for the schema holder. Read-Only(-RO) Optional Specifies that a schema holder is read-only. Connecting a schema holder as read-only increases processing speed at client startup time. It also allows multiple client processes on the same machine to access the schema holder without starting additional server processes. Local Cache(-cache) Optional Specifies that you are using a local cache file for the schema holder. Create the cache file with the SAVE CACHE COMPLETE statement. DataServer(-Dsrv) Optional Specifies options with which you control your ODBC Driver and DataServer environment. See the "Query Tuning with Connection and Startup Parameters" section in this chapter and the "ODBC Options" section in Chapter 6 for more information.NOTE: When you specify a list of -Dsrv parameters, be sure not to include any spaces anywhere in this list. Server Join(-nojoinbysqldb) Optional Specifies that the client evaluates and performs queries that have joins. This might slow performance, but it provides results that are consistent with Progress behavior.Use -nojoinbysqldb at startup time.
You can create a parameter file for each database:
- For a local DataServer, the parameter file must contain the -db parameter and can optionally contain the -Dsrv, -U, and -P connection parameters, depending on the requirements of the data service.
- For a remote DataServer, the same parameter conditions apply as for a local DataServer. In addition, a remote connection must contain the -H and -S connection parameters.
You can add more startup and connection parameters than the ones listed—these are the typical parameters. For a complete list of parameters and for information on how to create a parameter file, see the Progress Startup Command and Parameter Reference.
Using a Local DataServer Configuration: Examples
Use the following general command syntax to start Progress
:
You can type these commands on the command line of a program item property box.
The following examples start Progress in a local DataServer configuration. In these examples:
Using a Remote DataServer Configuration: Examples
This configuration is available only with the Enterprise DataServer for ODBC. A remote connection differs from a local connection in that it requires the Host (-H), Service (-S), and Network (-N) parameters.
Use the following command syntax to start Progress:
On a Windows Client:
On a UNIX Client:
The following examples start Progress in a remote DataServer configuration. In these examples:
On a Windows Client:
On a UNIX Client:
NOTE
This configuration assumes you started the remote DataSever broker using the command line interface or ProControl
To connect to a DataSever broker started through the Progress Explorer you must add the SVUB,1 setting to the -Dsrv parameter and add the -DataService name parameter.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |