db2cli.ini question 
Author Message
 db2cli.ini question

Hello list,

I can't get DB2 to use my db2cli.ini changes when my client is AIX.
The client I'm attempting this from is DB2 EE v7 fixpack 2 on AIX.

For instance, I go into the db2cli.ini and add these lines to do a
trace:

[COMMON]
tracepathname=/db2temp
traceflush=1
trace=1

I get no output at all.  I've tried all the things they say in the
manuals.  I log off and make sure the application is restarted after I
make the change.  I set the permissions on this directory to 777, I've
tried tracefilename instead of tracepathname, I've tried it without
traceflush.  db2cli.ini is located in /home/db2inst1/sqllib/cfg and I
don't have DB2CLIINIPATH set to anything, although I've tried with it
set to /home/db2inst1/sqllib/cfg too.  Using application snapshots
I've verified that this instance is the client.

Another thing I've tried is setting the current sqlid like this (the
top one is for an OS/390 database, the bottom one is for an AIX
database:

[DB2DDEVL]            
CURRENTSQLID=SDEVLGRP

[fin80prd]            
CURRENTSCHEMA=sdevlgrp

These configurations don't get picked up at all.  Now if I try all of
this on my Win NT client, making the changes in the db2cli.ini on my
Win NT, it works just fine.

This is driving me nuts.  Is there something obvious I'm missing here?
 Anybody had similar experiences?

Thanks.
Steve Toeniskoetter



Sun, 16 May 2004 23:22:34 GMT
 db2cli.ini question

Quote:

> Hello list,

> I can't get DB2 to use my db2cli.ini changes when my client is AIX.
> The client I'm attempting this from is DB2 EE v7 fixpack 2 on AIX.

> For instance, I go into the db2cli.ini and add these lines to do a
> trace:

> [COMMON]
> tracepathname=/db2temp
> traceflush=1
> trace=1

> I get no output at all.  I've tried all the things they say in the
> manuals.  I log off and make sure the application is restarted after I
> make the change.  I set the permissions on this directory to 777, I've
> tried tracefilename instead of tracepathname, I've tried it without
> traceflush.  db2cli.ini is located in /home/db2inst1/sqllib/cfg and I
> don't have DB2CLIINIPATH set to anything, although I've tried with it
> set to /home/db2inst1/sqllib/cfg too.  Using application snapshots
> I've verified that this instance is the client.

> Another thing I've tried is setting the current sqlid like this (the
> top one is for an OS/390 database, the bottom one is for an AIX
> database:

> [DB2DDEVL]            
> CURRENTSQLID=SDEVLGRP

> [fin80prd]            
> CURRENTSCHEMA=sdevlgrp

> These configurations don't get picked up at all.  Now if I try all of
> this on my Win NT client, making the changes in the db2cli.ini on my
> Win NT, it works just fine.

> This is driving me nuts.  Is there something obvious I'm missing here?
>  Anybody had similar experiences?

> Thanks.
> Steve Toeniskoetter

Make sure that the person running the CLI program has permissions to
write to the log file. I'll bet that's your problem as your trying to
create a log file in / (root). Remember that the rootvg on RS/6000 is
setup very small by default and you could run out of filesystem space
quickly. If you really meant to put it into the directory include a
filename /db2temp/somefile.log. Also the program must be restarted. When
the program initializes it ENV handle is when this file is read.

- Bill Cunningham
Technial Lead
Bally {*filter*} and Systems



Mon, 17 May 2004 02:36:13 GMT
 db2cli.ini question

Quote:
> Hello list,

> I can't get DB2 to use my db2cli.ini changes when my client is AIX.
> The client I'm attempting this from is DB2 EE v7 fixpack 2 on AIX.

> For instance, I go into the db2cli.ini and add these lines to do a
> trace:

> [COMMON]
> tracepathname=/db2temp
> traceflush=1
> trace=1

> I get no output at all.  I've tried all the things they say in the
> manuals.  I log off and make sure the application is restarted after I
> make the change.  I set the permissions on this directory to 777,

Who is the owner of the directory?  Do you have the 't' flag set on it, i.e.
who will the files that are newly created belong to?

You should try to use the /tmp/ directory.  This has usually the proper
permissions.

--
Knut Stolze
DB2 Spatial Extender
IBM Silicon Valley Lab



Sat, 22 May 2004 12:43:47 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. question about plain text password in db2cli.ini

2. Default schema in db2cli.ini intermittantly ignored

3. Cannot set SCHEMA in db2cli.ini

4. Settings in DB2CLI.INI

5. schema.ini question

6. DB2CLI and SQL_QUERY_TIMEOUT

7. db2cli.lib for db2 Version 5.2

8. SQL Stored Procedures called through DB2CLI are not executed

9. Install ODBC for DB2 (db2cli.dll)

10. DB2CLI.dll

11. db2cli trace

12. Looking for db2cli.dll version 7.1.0.1 (07/28/2000)


 
Powered by phpBB® Forum Software