Connecting to a Data Source Using a Connection String
If you want to use a connection string for connecting to a database, or if your application requires it, you must specify either a DSN (data source name), a File DSN, or a DSN-less connection in the string. The difference is whether you use the DSN=, FILEDSN=, or the DRIVER= keyword in the connection string, as described in the ODBC specification. A DSN or FILEDSN connection string tells the driver where to find the default connection information. Optionally, you may specify attribute=value pairs in the connection string to override the default values stored in the data source.
The DSN connection string has the form:
The FILEDSN connection string has the form:
The DSN-less connection string specifies a driver instead of a data source. All connection information must be entered in the connection string because there is no data source storing the information.
The DSN-less connection string has the form:
Table 4-1 gives the long and short names for each attribute, as well as a description. You can specify either long or short names in the connection string. Connection string attribute names are the same as the option names on the driver Setup dialog box tabs unless otherwise noted. The connection string attribute name does not have spaces between the words. For example, the connection string attribute name ApplicationUsingThreads is equivalent to the option name Application Using Threads.
The defaults listed in the table are initial defaults that apply when no value is specified in either the data source definition or in the connection string. If you specified a value for the attribute when configuring the data source, that value is the default. Note that if no default value is listed in the table for attributes that use a string value, an empty string is the default value.
An example of a DSN connection string with overriding attribute values for DB2 for Linux/UNIX/Windows is:
A FILEDSN connection string is similar except for the initial keyword:
A DSN-less connection string must provide all necessary connection information:
DRIVER=DataDirect DB2 Wire Protocol; IpAddress=123.456.78.90;PORT=5179;DB=DB2ACCT;UID=JOHN; PWD=XYZZY
CreateTable (ASCT)Invalid value for Alternate ID. DB2 permissions must be set to SYSADM. (This is not valid for DB2 UDB V5R1 for iSeries.)
Location=DB2DAT3)See "Configuring Connection Failover" for information about other connection options that you can set for this feature.
Threads (AUT)
Method (AM)SELECT * FROMSchema.TablenameCollection is also the current library. If the attempt to change the current schema fails, the connection fails and you receive the message,Invalid value for Alternate ID. DB2 permissions must be set to SYSADM. (This is not valid for DB2 V5R1 for iSeries.) Collection is overridden by Alternate ID on iSeries if a value is set for Alternate ID.
Method (EM)
DISPLAY DDFcommand.On DB2 for iSeries only, your system administrator can determine the name of your DB2 location using theWRKRDBDIREcommand. The name of the database that is listed as *LOCAL is the value you should use.The equivalent Setup dialog box option is Location Name.
ConversionErrors (RCCE)Code page conversion error encountered. In the case of parameter data conversion errors, the driver adds the following sentence:Error in parameterx, wherexis the parameter number. The standard rules for returning specific row and column errors for bulk operations still apply.When set to 1, if the driver encounters code page conversion errors, it returns an error instead of substituting 0x1A for unconverted characters.When set to 2, if the driver encounters code page conversion errors, it substitutes 0x1A for each character that cannot be converted and returns a warning.CHGDDMTCPA AUTOSTART(*YES) PWDRQD(*YES)starts the listener and ensures that it is active at IPL.