To whom this may concern
Current releases of DB2 Express-C apparently no longer create and support the db2cli.ini file. What is one supposed to do if an application relies on the existence of this file? Any ideas on how to read the variables (I use Microsoft Access VBA most of the time), previously available by reading the contents of the db2cli.ini file, if this file doesn't exist?
Business data processing specialist
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2012-07-13T15:07:30Z by Leo_52
Pinned topic db2cli.ini file
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-07-13T15:07:30Z at 2012-07-13T15:07:30Z by Leo_52
SystemAdmin 110000D4XK5837 PostsACCEPTED ANSWER
Re: db2cli.ini file2012-07-08T14:59:06Z in response to Leo_52Hello Leo,
The sample db2cli.ini file is no longer provided, but it can be recreated with the UPDATE CLI CFG command. For example,
db2 "update cli cfg for section SAMPLE using DBAlias MySampleDatabase"
creates a db2cli.ini file containing :
For a reference of all CLI configuration keywords, have à look at :
Hope this helps.
Leo_52 060000XSAJ69 PostsACCEPTED ANSWER
Re: db2cli.ini file2012-07-13T15:07:30Z in response to SystemAdminHello Yves-Antoine
Sorry, my question wasn't quite to the point! Using Windows Vista/7, the db2cli.ini file is created in the C:\Users\Username\Documents directory by default. This will of course lead to problems if another machine or network user is trying to access data stored in this path. Adding the DB2 registry database variable DB2CLIINIPATH and setting it to point to a directory which other users can access across the network solves this problem.
I apologize, should my posting have led to confusion, but I am currently recovering from a cerebral apoplexy.