Starts the interactive call level interface (CLI) environment for design and prototyping in CLI.
The db2cli command is located in the bin subdirectory of the directory where you installed IBM® data server product. On UNIX and Linux operating systems, the db2cli command is located in the home_dir/sqllib/bin directory, where home_dir is the home directory of the instance owner. On Windows operating systems, the command is located in the DB2PATH\bin directory, where DB2PATH is the installation location of the DB2® copy.
None
None
>>-db2cli--+------------------------------------------------+-->< +-validate--+----------------------+-------------+ | +-| Validate options |-+ | | '- -help---------------' | +-bind--+-filename--| Bind options |-+-----------+ | '- -help---------------------' | +-registerdsn--| Register DSN options |----------+ +-csc-- -info------------------------------------+ +-| Execsql options |----------------------------+ +-install--| Install options |-------------------+ +-writecfg--| Write configuration file options |-+ +-refreshldap--+----------+----------------------+ | '- -global-' | '- -help-----------------------------------------' Validate options |--+-+- -dsn--dsn_name------------------+--+------------------------------------+-+--> | '- -database--database:server:port-' '- -connect--+---------------------+-' | | '-| Connect options |-' | '- -all------------------------------------------------------------------------' >--+------------------+-----------------------------------------| '- -f--output_file-' Connect options |--+-------------------------+----------------------------------> +- -displaylic-- -odbcdsn-+ '- -useserverlic----------' >--+-+------------------------------------------+------------------------------------+--| | '- -user--username--+--------------------+-' | | '- -passwd--password-' | '-+------------------+-- --keystoredbpassword--keystoredbpasswd-- -user--username-' '- -user--username-' Bind options |--+- -dsn--dsn_name------------------+-------------------------> '- -database--database:server:port-' >--+------------------------------------------+-----------------> '- -user--username--+--------------------+-' '- -passwd--password-' >--+-----------------------------------+------------------------| '- -options--"various_bind_options"-' Register DSN options .- -user---. |--+-+- -add--+-+-------+--dsn_name---------+--------------------------+--+----------+-+--| | | | '- -dsn-' | | '- -system-' | | | '- -alldsn--+---------------+-' | | | | '- -includeldap-' | | | +- -remove--+--------------------------+--+-+-------+--dsn_name-+-+ | | | +- -copyname--copy_name----+ | '- -dsn-' | | | | | '- -allcopies--+---------+-' '- -alldsn------------' | | | | '- -force-' | | | '- -list--+-----------------------+-------------------------------' | | +- -copyname--copy_name-+ | | '- -allcopies-----------' | '- -help----------------------------------------------------------------------------' Execsql options .- -execute-----. |----execsql----+---------------+-------------------------------> '- -prepareonly-' >--+-| Server options |---+-- -inputsql--sqlfile----------------> '- -connstring--string-' >--+------------------------+-----------------------------------> '- -outfile--output_file-' >--+---------------------------------+--------------------------> '- -statementdelimiter--delimiter-' >--+-----------------------------------+--+--------+------------| '- -commentstart--comment_indicator-' '- -help-' Server options |-- -dsn--dsn_name--+----------------------------+--------------| '-| Authentication options |-' Authentication options |-- -user--username--+------------------+-----------------------| '- -passwd--passwd-' Install options (available only on Windows) |--+-+- -setup---------------------------------+-+--------------| | +- -cleanup--+--------------------------+-+ | | | '- -appdatapath--path_name-' | | | '- -cleanup--+---------+------------------' | | '- -force-' | '- -help--------------------------------------' Write configuration file options |--+-add--+-+- -dsn--dsn_name------------------------------------------+--+--------------------------------------------------------------------+-+-+--| | | '- -database--db_name-- -host--host_name-- -port--p_number-' | .-;----------------------------------. | | | | | | V | | | | | | +-+- -parameter--+--"----parameter_name--=--parameter_value-+--"-----+ | | | | | '- -parameters-' | | | | | | .-;------------------------------. | | | | | | V | | | | | | +- -sessionglobalvariables--"----globvar_name--=--globvar_value-+--"-+ | | | | | .-;--------------------------------. | | | | | | V | | | | | | '- -specialregisters--"----register_name--=--register_value-+--"-----' | | | | .-;----------------------------------. | | | | V | | | | +-+- -parameter--+--"----parameter_name--=--parameter_value-+--"-----------------------------------------------------------------------+ | | | '- -parameters-' | | | | .-;------------------------------. | | | | V | | | | +- -sessionglobalvariables--"----globvar_name--=--globvar_value-+--"-------------------------------------------------------------------+ | | | .-;--------------------------------. | | | | V | | | | '- -specialregisters--"----register_name--=--register_value-+--"-----------------------------------------------------------------------' | +-remove--+-+- -dsn--dsn_name------------------------------------------+--+------------------------------------------------------+-+------------+ | | '- -database--db_name-- -host--host_name-- -port--p_number-' | .-;--------------. | | | | | | V | | | | | | +-+- -parameter--+--"----parameter_name-+--"-----------+ | | | | | '- -parameters-' | | | | | | .-;------------. | | | | | | V | | | | | | +- -sessionglobalvariables--+-"----globvar_name-+--"-+-+ | | | | | '- -force----------------' | | | | | | .-;-------------. | | | | | | V | | | | | | '- -specialregisters--+-"----register_name-+--"-+------' | | | | '- -force-----------------' | | | | .-;--------------. | | | | V | | | | +-+- -parameter--+--"----parameter_name-+--"-----------------------------------------------------------------------------+ | | | '- -parameters-' | | | | .-;------------. | | | | V | | | | +- -sessionglobalvariables--+-"----globvar_name-+--"-+-------------------------------------------------------------------+ | | | '- -force----------------' | | | | .-;-------------. | | | | V | | | | '- -specialregisters--+-"----register_name-+--"-+------------------------------------------------------------------------' | | '- -force-----------------' | '- -help----------------------------------------------------------------------------------------------------------------------------------------'
Validates and tests the CLI environment configuration. This option shows a list of keywords that are found in the db2cli.ini and db2dsdriver.cfg files. If any keywords are invalid for the specified data source or database name, they are listed as UNKNOWN. IBM data server clients (the IBM Data Server Client or the IBM Data Server Runtime Client), the db2cli validate command lists the installed DB2 client packages on a Windows operating system. When you issue the db2cli validate command from the IBM data server clients, the list is limited to the IBM data server clients that are installed on the Windows operating system. To list IBM Data Server Driver for ODBC and CLI packages and the IBM data server client packages that are installed on a Windows operating system, you must issue the db2cli validate command from the IBM Data Server Driver for ODBC and CLI installation. The list indicates the current copy name as [C] and the default copy name as [D].
Binds the specified filename against the target database. The db2cli bind command first connects to the target database with the information provided in the db2cli bind command parameters then performs the bind action. Bind files have the extension .bnd.
Specifies the db2cli register DSN mode. Use this command parameter to register a DSN in the Windows operating system.
Executes or prepares the SQL statements specified in an input file. Can also save output to a file.
Only SQL statements and comments can be in the input SQL file. The file cannot contain CLI specific attributes or keywords. Batch SQL statements are not supported.
Registers or unregisters the IBM Data Server Driver for ODBC and CLI in the Windows registry.
If there is no existing <dsn> subsection with the dsn_nameas dsn alias in the configuration file, a new <dsn> subsection in the <dsncollection> section is added.
If there is a dsn subsection with the dsn_nameas dsn alias in the configuration file, new parameters or session global variables information provided is appended to the existing <dsn> subsection.
If you specify a new parameter element that is not found in the <dsn> subsection of the db2dsdriver.cfg configuration file, a new parameter element is added to the <dsn> subsection.
If the specified parameter element is already present in the configuration file, the existing parameter value in the <dsn> subsection is updated with the value that you specify with the -parameter[s] option.
Special characters, such as path separators in the value, must be preceded by the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified parameter.
If you specify a new session global variable parameter that is not found in the <dsn> subsection of the db2dsdriver.cfg configuration file, a new session global variable parameter element is added to the <dsn> subsection.
If the specified session global variable parameter element is already present in the configuration file, the session global variable value in the <dsn> subsection is updated with the value that you specify with the -sessionglobalvariables option.
Special characters, such as path separators in the value, must be preceded by the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified session global variable parameter.
If you specify a special register parameter that is not in the <dsn> subsection of the db2dsdriver.cfg configuration file, a new special register parameter element is added to that subsection. If the specified special register parameter element is already in the configuration file, the special register value in the <dsn> subsection is updated with the value that you specify for the -specialregisters parameter.
You must precede any special characters in the special register value (registerN_value) with the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified special register parameter.
If a <database> subsection with the same db_name information exists in the db2dsdriver.cfg configuration file, the specified parameter element is appended to the <database> subsection. Otherwise, the specified parameter elements or the session global variable parameter elements are added to a new <database> subsection.
If you specify a new parameter element that is not found in the <database> subsection of the db2dsdriver.cfg configuration file, a new parameter element is added to the <database> subsection.
If the specified parameter element is already present in the configuration file, the existing parameter value in the <database> subsection is updated with the value that you specify with the -parameter[s] option.
Special characters, such as path separators in the value, must be preceded by the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified parameter.
If you specify a new session global variable parameter that is not found in the <database> subsection of the db2dsdriver.cfg configuration file, a new session global variable parameter element is added to the <database> subsection.
If the specified session global variable parameter element is already present in the configuration file, the session global variable value in the <database> subsection is updated with the value that you specify with the -sessionglobalvariables option.
Special characters, such as path separators in the value, must be preceded by the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified session global variable parameter.
If you specify a special register parameter that is not in the <database> subsection of the db2dsdriver.cfg configuration file, a special register parameter element is added to that subsection. If the specified special register parameter element is already in the configuration file, the special register value in the <database> subsection is updated with the value that you specify for the -specialregisters parameter.
You must precede any special characters in the special register value (registerN_value) with the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified special register parameter.
To add a parameter to the global <parameters> section, specify the parameter information without indicating a database or a data source.
If you specify a new parameter element that is not found in the <parameters> subsection of the db2dsdriver.cfg configuration file, a new parameter element is added to the <parameters> subsection.
If the specified parameter element is already present in the configuration file, the existing parameter value in the <parameters> subsection is updated with the value that you specify with the -parameter[s] option.
Special characters, such as path separators in the value, must be preceded by the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified parameter.
If you specify a new session global variable parameter that is not found in the <parameters> subsection of the db2dsdriver.cfg configuration file, a new session global variable parameter element is added to the <parameters> subsection.
If the specified session global variable parameter element is already present in the configuration file, the session global variable value in the <parameters> subsection is updated with the value that you specify with the -sessionglobalvariables option.
Special characters, such as path separators in the value, must be preceded by the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified parameter.
If you specify a special register parameter that is not in the <parameters> subsection of the db2dsdriver.cfg configuration file, a special register parameter element is added to the <parameters> subsection. If the specified special register parameter element is already in the configuration file, the special register value in the <parameters> subsection is updated with the value that you specify for the -specialregisters parameter.
You must precede any special characters in the special register value (registerN_value) with the escape character "\".
The db2cli writecfg command does not verify the syntax or validate the value of the specified special register parameter.
To remove parameter elements or session global variable parameter elements information, specify the corresponding DSN and the parameter or session global variable information.
To remove the entire data source subsection, specify only the DSN without any parameters or session global variables information.
If the indicated parameter is not in the specified <dsn> subsection of the configuration file, no action is taken.
If the indicated session global variable is not in the specified <dsn> subsection of the configuration file, no action is taken.
To remove parameter elements or session global variable parameter elements information, specify the corresponding database name and the parameter or session global variable information.
To remove the entire database subsection, specify only the database name without any parameter or session global variable information.
If the indicated parameter is not in the <database> subsection of the configuration file, no action is taken.
If the indicated session global variable is not specified in the <database> subsection of the configuration file, no action is taken.
If the indicated parameter is not in the <parameters> section of the configuration file, no action is taken.
If the indicated session global variable is not in the <parameters> section of the configuration file, no action is taken.
The authentication type that is defined for a database in the LDAP server is appended or updated to the <dsn> section for that DSN alias in the IBM data server driver configuration file.
The Protocol parameter that is defined for a database in the LDAP server is appended or updated to the <dsn> section for that DSN alias only if the value is not TCPIP.
The following table lists the DCS parameters and equivalent keywords that are supported in the IBM data server driver configuration file. Only the listed DCS parameters can be appended or updated with the refreshldap option.DCS parameter | Equivalent keyword |
---|---|
map-file | SQLCODEMAP |
INTERRUPT_ENABLED | InterruptProcessingMode |
SYSPLEX | ConnectionLevelLoadBalancing |
BIDI | BiDiCCSID |
The db2cli refreshldap command creates the IBM data server driver configuration file if it is not present.
The db2cli refreshldap command updates the IBM data server driver configuration file with keywords that are equivalent to the CLI keywords, which are specified in the LDAP server. Any CLI keywords that are specified on the LDAP server that does not have equivalent IBM data server driver configuration keyword results in a warning message. Any gateway settings on the LDAP server, which are specified through GWNODE option are not appended or updated, and results in a warning message. The alternate server settings on the LDAP server are not appended or updated, and results in a warning message.If there is a DSN entry on the LDAP server that matches an existing DSN entry in the IBM data server driver configuration file that is not created from the LDAP server entry (without the LDAP=1 attribute), a warning is returned and the DSN entry is not updated.
If multiple DSN entries exist on the IBM data server driver configuration file for a same database but with different alias, only the DSN entries that were created from the LDAP server entry (with the LDAP=1 attribute) are removed when the DSN entry on the LDAP server is deleted.The db2cli refreshldap command can be issued only with the IBM Data Server Driver Package and IBM Data Server Driver for ODBC and CLI products.
The db2cli refreshldap command is similar to the REFRESH LDAP IMMEDIATE ALL command that can be issued from the IBM Data Server Client, IBM Data Server Runtime Client or IBM database server products.The interactive CLI interface consists of a set of commands that you can use to design, prototype, and test CLI function calls. It is a testing tool that is provided for the convenience of those programmers who want to use it, and IBM makes no guarantees about its performance. This interface is not intended for users, and so does not have extensive error-checking capabilities.
You can issue commands interactively or from within a file. Similarly, you can display the command output on the terminal or write it to a file. A useful feature of the IBM Data Server Driver for ODBC and CLI is the ability to capture all of the commands that are entered during a session, and to write them to a file, thus creating a command script that you can rerun at a later time.
For IBM Data Server client packages on Windows 64-bit operating systems, the 32-bit version of db2cli (db2cli32.exe) is supported in addition to the 64-bit version of the db2cli command.
SQL statements are executed by using the SQLExecDirect() function. When executing SQL statements, the db2cli execsql command uses the database settings specified in the db2cli.ini and db2dsdriver.cfg files.
Error messages returned by the db2cli command are formatted using the same format as the SQLGetDiagRec() function.
For 32-bit installations, the db2cli command by default registers only 32-bit DSN.
The DSN that you want to register must be in the db2cli.ini or the db2dsdriver.cfg file.
db2cli validate –dsn sample
db2cli validate -database dbname1:server1.net1.com:50001
db2cli validate -dsn "IBM - User Acceptance" -connect -user <userid> -passwd <password>
<configuration>
<dsncollection>
<dsn alias="alias1" name="name1" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="TRUE"/>
</dsn>
</dsncollection>
<databases>
<database name="name1" host="server1.net1.com" port="50001">
<parameter name="CurrentSchema" value="OWNER1"/>
</database>
</databases>
<parameters>
<parameter name="IsolationLevel" value="SQL_TXN_READ_COMMITTED"/>
</parameters>
</configuration>
db2cli writecfg add –dsn alias2 –database name2 -host server1.net1.com -port 50001
As
a result of this command, the dsncollection section
is modified as follows:<dsncollection>
<dsn alias="alias1" name="name1" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="TRUE"/>
</dsn>
<dsn alias="alias2" name="name2" host="server1.net1.com" port="50001"/>
</dsncollection>
db2cli writecfg add –dsn alias2 –parameters “DisableAutoCommit=FALSE;CurrentSchema=OWNER2;pureQueryXml=C:\\clico”
As
a result of this command, the dsncollection section
is modified as follows:<dsncollection>
<dsn alias="alias1" name="name1" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="TRUE"/>
</dsn>
<dsn alias="alias2" name="name2" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="FALSE"/>
<parameter name="CurrentSchema" value="OWNER2"/>
..<parameter name="pureQueryXml" value="C:\clico"/>
</dsn>
</dsncollection>
db2cli writecfg add –database name2 –host server1.net1.com -port 50001 -parameters “LockTimeout=20;KeepAliveTimeout=20000”
As
a result of this command, the databases section
is modified as follows:<databases>
<database name="name1" host="server1.net1.com" port="50001">
<parameter name="CurrentSchema" value="OWNER1"/>
</database>
<database name="name2" host="server1.net1.com" port="50001">
parameter name=" LockTimeout" value="20"/>
parameter name="KeepAliveTimeout" value="20000"/>
</database>
</databases>
db2cli writecfg add –dsn alias1 –parameter “DisableAutoCommit=FALSE”
As
a result of this command, the dsncollection section
is modified as follows:<dsncollection>
<dsn alias="alias1" name="name1" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="FALSE"/>
</dsn>
<dsn alias="alias2" name="name2" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="FALSE"/>
<parameter name="CurrentSchema" value="OWNER2"/>
..<parameter name="pureQueryXml" value="C:\clico"/>
</dsn>
</dsncollection>
db2cli writecfg add -parameter "ReceiveTimeout=20000"
As
a result of this command, the global section is modified as follows:<parameters>
<parameter name="IsolationLevel" value=" SQL_TXN_READ_COMMITTED"/>
<parameter name="ReceiveTimeout" value="20000"/>
</parameters>
db2cli writecfg remove –database name1 -host server1.net1.com -port 50001 –parameter “CurrentSchema”
As
a result of this command, the databases section
is modified as follows:<databases>
<database name="name1" host="server1.net1.com" port="50001">
</database>
<database name="name2" host="server1.net1.com" port="50001">
parameter name="LockTimeout" value="20"/>
parameter name="KeepAliveTimeout" value="20000"/>
</database>
</databases>
db2cli writecfg remove –dsn alias1
As
a result of this command, the dsncollection section
is modified as follows:<dsncollection>
<dsn alias="alias2" name="name2" host="server1.net1.com" port="50001">
<parameter name="DisableAutoCommit" value="FALSE"/>
<parameter name="CurrentSchema" value="OWNER2"/>
<parameter name="pureQueryXml" value="C:\clico"/>
</dsn>
</dsncollection>
create table employee(empid integer, empname varchar(100)
CREATE PROCEDURE proc1 ( )
DYNAMIC RESULT SETS 1 P1:
BEGIN
DECLARE cursor1 CURSOR WITH RETURN FOR SELECT * FROM fprem;
OPEN cursor1;
END P1
CREATE PROCEDURE PROC2(IN ID1 INTEGER,OUT NAME VARCHAR(20))
BEGIN
DECLARE CUR1 CURSOR WITH RETURN TO CALLER FOR SELECT * FROM EMPLOYEE1 WHERE ID=ID1;
OPEN CUR1;
END
This example also assumes the SQL file test.sql contains
the following text:--Populate table( employee )
insert into employee(empid, empname) values(1, 'Adam')
insert into employee(empid, empname) values(2, 'Atul')
select empid, empname from employee
--Execute the stored procedure
Call proc1( )
db2cli execsql –dsn sample –inputsql test.sql
IBM DATABASE 2 Interactive CLI Sample Program
(C) COPYRIGHT International Business Machines Corp. 1993,1996
All Rights Reserved
Licensed Materials - Property of IBM
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
insert into employee(empid, empname) values(1, 'Adam')
The SQL command completed successfully.
insert into employee(empid, empname) values(2, 'Atul')
The SQL command completed successfully.
select empid, empname from employee
EMPID EMPNAME
1, Adam
2, Atul
Call proc1()
EMPID EMPNAME
1, Adam
2, Atul
Run a CALL statement for a stored procedure that
has OUT arguments. The question mark (?) can be used as an OUT parameter. CALL PROC2( 1, ?)
Enter the
following db2cli command in a console window to
run the SQL statements in the file:db2cli execsql –dsn sample –inputsql test2.sql
The
following text is displayed in the console window:Value of output parameters
--------------------------
Parameter Name : NAME
Parameter Value : -
ID
-----------
1
Specify the -prepareonly option to prepare the SQL statements without running them. The DDL statements that are needed for the SQL statements must be run before you run the db2cli execsql command with the -prepareonly option.
--populate table( employee )
insert into employee(empid, empname) values(1, 'Adam');
insert into employee(empid, empname) values(2, 'Atul');
select empid, empname from employee;
Also, assume that
the table EMPLOYEE was created in the database. Enter the following db2cli command
in a console window to prepare the SQL statements in the file: db2cli execsql –prepareonly –dsn sample –inputsql test3.sql
The
following text is displayed in the console window:IBM DATABASE 2 Interactive CLI Sample Program
(C) COPYRIGHT International Business Machines Corp. 1993,1996
All Rights Reserved
Licensed Materials - Property of IBM
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
insert into employee(empid, empname) values(1, 'Adam')
The SQL command prepared successfully.
insert into employee(empid, empname) values(2, 'Atul')
The SQL command prepared successfully.
select empid, empname from employee
The SQL command prepared successfully.
If you place DDL statements that are required for DML statements in the same file,
the DML statements that require the DDL statements fail.
For example, assume that the following text is in the file test4.sql,
and assume that and the EMPLOYEE table has not been created in the database:
--create and populate table( employee )
create table employee(empid integer, empname varchar(100));
insert into employee(empid, empname) values(1, 'Adam');
insert into employee(empid, empname) values(2, 'Atul');
select empid, empname from employee;
-- try to create another table with the same name
create table employee(empid integer, empname varchar(100));
The
CREATE TABLE statement must be run before the INSERT and SELECT statements
can be run successfully.db2cli execsql –prepareonly –dsn sample –inputsql test4.sql
The
following text is displayed in the console window:IBM DATABASE 2 Interactive CLI Sample Program
(C) COPYRIGHT International Business Machines Corp. 1993,1996
All Rights Reserved
Licensed Materials - Property of IBM
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
create table employee(empid integer, empname varchar(100))
The SQL command prepared successfully.
insert into employee(empid, empname) values(1, 'Adam')
The SQL command failed. During SQL processing it returned:
[IBM][CLI Driver][DB2/6000] SQL0204N "EMPLOYEE" is an undefined name. SQLSTATE=42704
insert into employee(empid, empname) values(2, 'Atul')
The SQL command failed. During SQL processing it returned:
[IBM][CLI Driver][DB2/6000] SQL0204N "EMPLOYEE" is an undefined name. SQLSTATE=42704
select empid, empname from employee
The SQL command failed. During SQL processing it returned:
[IBM][CLI Driver][DB2/6000] SQL0204N "EMPLOYEE" is an undefined name. SQLSTATE=42704
create table employee(empid integer, empname varchar(100))
The SQL command prepared successfully.
In this example,
the two CREATE SQL statements prepared successfully, however the EMPLOYEE
table was not created in the database. The INSERT and SELECT statements
did not prepare successfully because the EMPLOYEE table was not in
the database.$ db2cli bind @db2cli.lst –database “mydb:test.torolab.ibm.com:446”
–options “BLOCKING unambig REOPT always ISOLATION RR”
LINE MESSAGES FOR db2cli.lst
------ --------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.
<configuration>
<dsncollection>
<dsn alias="sample" name="sample" host="hotel53.ibm.com" port="40576” ldap=1>
<parameter name="DisbaleAutoCommit" value="0"/>
<parameter name="AllowDeferredPrepare" value="1"/>
</dsn>
<dsn alias="EC205" name="STLEC1" host="INEC005.ibm.com" port="446" ldap=1>
<parameter name="InterruptProcessingMode" value="1"/>
</dsn>
<dsn alias="test1" name="test" host="xyz.ibm.com" port="446" ldap=1>
<parameter name="QueryTimeoutInterval" value="15"/>
<parameter name="Authentication" value="SERVER"/>
</dsn>
</dsncollection>
<databases>
<database name="sample" host="hotel53.ibm.com" port="40576"/>
<database name="STLEC1" host="INEC006.ibm.com" port="446">
<parameter name="ConnectionLevelLoadBalancing" value="1"/>
</database>
<database name="test" host="xyz.ibm.com" port="446"/>
</databases>
</configuration>