Don Baugh wrote: > Hey Steve, > > CLI applications must be stopped and restarted before changes to the > db2cli.ini take effect. Did you do this? > > You can also select the coordinator node of an application by setting the > environment variable DB2NODE to the node you wish. Check to see if this is > set in your environment. If it is, perhaps it takes precedence over the > db2cli.ini setting. > > Or you can have your CLI application do a putenv system call to set the > DB2NODE environment variable. >
I have had problems getting this to work in the db2cli.ini as well, but setting DB2NODE *always* works. One thing to remember: You need to connect to the physical server that has the partition you want. If you have 3 servers with 6 partitions, as in (db2nodes.cfg): 0 alpha 0 1 alpha 1 2 beta 0 3 beta 1 4 gamma 0 5 gamma 1 If you want to connect to partition 4 or 5, you need to catalog your TCPIP node to point to the machine 'gamma'. You can't use 'alpha' and request that you connect to partition 5 (if you do, you'll just default to the logical partition 0 on the machine you connected to). Good luck, - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
