Progress/400
Product Guide


Connection Parameters

Connection parameters control how Progress connects to a database. When using Progress to access a DB2/400 database, use the connection parameters shown in Table 4–1. Be sure to place the parameters that control the connection to a DB2/400 database after the database name in a connection statement.

The descriptions of these parameters are specific to connections between Progress clients and the Progress/400 DataServer and the network protocol that your configuration uses.

Table 4–1: Progress/400 Connection Parameters 
Parameter
Description
Used By
Protocol
-db
Physical Database Name (Dictionary Library)
All clients
TCP/IP and SNA
-Dsrv
DataServer
All clients
TCP/IP and SNA
-dt as400
Database Type
MS-Windows
UNIX
TCP/IP and SNA
-H
Host Name
MS-Windows
UNIX
TCP/IP and SNA
-is
Ignore Stamp
All clients
TCP/IP and SNA
-N
Network Type
MS-Windows
UNIX
TCP/IP and SNA
-P
Password
MS-Windows
UNIX
TCP/IP and SNA
-S
Service Name
MS-Windows
UNIX
TCP/IP
-Sn
Server Name
MS-Windows
UNIX
SNA
-U
Userid
MS-Windows
UNIX
TCP/IP and SNA

NOTE: The -ld parameter is not supported. To change the logical database name, see Remote Client DB2/400 Utilities."

This section and the "DATALIB Argument Usage Notes" section describe the parameters and their usage with the Progress/400 DataServer in detail.

Physical Database Name (-db)

The name of the database that you want to connect to. In the Progress/400 DataServer context, the physical database name is the name of the library that contains the server schema on the AS/400:

SYNTAX
-db physical-dbname 

DataServer (-Dsrv)

Use this parameter to pass connection information directly to the Progress/400 DataServer:

SYNTAX
-Dsrv keyword1, value1, keyword2, value2 

The syntax for specifying the arguments and their values has a second form:

SYNTAX
-Dsrv keyword1=value1, keyword2=value2 

Table 4–2 describes the arguments and values that the -Dsrv parameter accepts. The "DATALIB Argument Usage Notes" section provides some special usage notes on the DATALIB argument.

Table 4–2: DataServer (-Dsrv) Arguments
Keyword
Description
TRANSCTL
Specifies the kind of transaction control that DataServer applications use. There are four options:
COMMIT starts commitment control for all the DB2/400 database files associated with a server schema. A journal receiver must exist for each database file to enable transaction management. If you do not have journaling in effect for each DB2/400 file, the application returns an error.
LBI specifies that the client use a local before-image file to manage main transactions and nested subtransactions. See the "Transaction Control" section in "System Administration," for more information.
NONE specifies that there is no transaction control in effect.
OPTIONAL specifies that the DataServer use commitment control for all DB2/400 files for which there is an active journal. This allows the use of transaction management for some files and not for others. The DataServer opens files for which there is no active journal without commitment control. This is the default.
COMPRESS
Specifies that the client and the DataServer use compression when transferring database records back and forth. Compression also allows the DataServer to transfer more records to the client in each message when using pre-fetch. The allowed values are:
0 = off (the default)
1 = on
SBS
Specifies that the DataServer uses selection-by-server when appropriate. The allowed values are:
0 = off
1 = on (the default)
DATALIB
Specifies the library in which the DataServer opens DB2/400 files. If you specify a library name, you must enter it in capital letters. To open files using the DataServer’s library list, specify the value *LIBL instead of a library name. The default is to open files in the library whose name is stored in the P__FILE server schema file.
See the "DATALIB Argument Usage Notes" section for more information.
LFLVLCHK
Enables the CRC method of logical file level checking. In this method, the CRC is created from the file’s name, record format, key field names, types, and lengths to ensure that its CRC does not change if the file is moved or copied.
CRC = on.
The default is off.
CANCELQRY
For TCP/IP connections, allows the client to use CTRL-C (on UNIX machines) or CTRL-BREAK (on Windows machines) to cancel a query request. By default, control does not return to the client until the query completes. The allowed values are:
0 = off (the default)
1 = on
This argument is not available for SNA connections.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095