I support an application where the primary key is a Date-Time Stamp.
When we converted from NEON to DB2 Connect, we were able to get the
update to work by setting the PATCH1 code to 131201 (combination of a
few others, but includes the Date Time stamp as CHAR26 patch).

I was doing some troubleshooting on another matter and came across
something peculiar. When running traces on my machine, the trace log
shows the PATCH1 is 384, not the 131201 set in the db2cli.ini file.
Consequently I cannot update ANYTHING. Some time ago I was doing some
testing of various PATCH1 combinations and this one one but had
removed it (or so I thought) some time ago.

My problem is:
I can't get my application to read the correct patch1 code and cannot
figure out where the PATCH1=384 is coming from. I have done the
following.
1. re-keyed the correct PATCH1 information into the db2cli.ini file.
2. added a couple lines at the end with ";" per a board suggestion.
3. created a new system ODBC connection.
4. Verified via the CCA that the correct patch1 info is there.
5. Re-booted after all changes.

>My db2cli.ini setting
[DB2A]
DESCRIPTION= Midwest Production
PATCH1=131201
DBALIAS=DB2A

>trace information echo
[ Process: 300, Thread: 276 ]
[ Date & Time: 11-03-2003 07:56:48.000011 ]
[ Product: QDB2/NT 7.1.0.65 ]
[ Level Identifier: 03060105 ]
[ CLI Driver Version: 07.02.0001 ]
[ Informational Tokens: "DB2 v7.1.0.65","nXXXXXX","XXXXXX" ]
........

( DSN="DB2A" )

( UID="XXXXXXX" )

( PWD="********" )

( DBALIAS="DB2A" )

( PATCH1="384" )<------------THIS IS WRONG AHH!

I really don't know where else to check. All other settings (ie.
setting the TraceFlush information I am able to edit via the
db2cli.ini file and have the changes take affect without a problem.)

Any suggestions would be most appreciated. Thank you.

You may have more than one db2cli.ini file.
Maybe you don't look at the right one?

http://publib.boulder.ibm.com/infoce...help/index.jsp
search for : db2cliinipath

Read this section
db2cli.ini Initialization File

The command
DB2 Get CLI cfg
can also show you the content of the db2cli.ini file. (no need to trace)

PM

"Liz Kegel" <elizabeth.kegel@us.fortis.com> a écrit dans le message de
news:f0624ade.0311030630.4fdc3bf0@posting.google.c om...
> I support an application where the primary key is a Date-Time Stamp.
> When we converted from NEON to DB2 Connect, we were able to get the
> update to work by setting the PATCH1 code to 131201 (combination of a
> few others, but includes the Date Time stamp as CHAR26 patch).
>
> I was doing some troubleshooting on another matter and came across
> something peculiar. When running traces on my machine, the trace log
> shows the PATCH1 is 384, not the 131201 set in the db2cli.ini file.
> Consequently I cannot update ANYTHING. Some time ago I was doing some
> testing of various PATCH1 combinations and this one one but had
> removed it (or so I thought) some time ago.
>
> My problem is:
> I can't get my application to read the correct patch1 code and cannot
> figure out where the PATCH1=384 is coming from. I have done the
> following.
> 1. re-keyed the correct PATCH1 information into the db2cli.ini file.
> 2. added a couple lines at the end with ";" per a board suggestion.
> 3. created a new system ODBC connection.
> 4. Verified via the CCA that the correct patch1 info is there.
> 5. Re-booted after all changes.
>
> >My db2cli.ini setting
> [DB2A]
> DESCRIPTION= Midwest Production
> PATCH1=131201
> DBALIAS=DB2A
>
> >trace information echo
> [ Process: 300, Thread: 276 ]
> [ Date & Time: 11-03-2003 07:56:48.000011 ]
> [ Product: QDB2/NT 7.1.0.65 ]
> [ Level Identifier: 03060105 ]
> [ CLI Driver Version: 07.02.0001 ]
> [ Informational Tokens: "DB2 v7.1.0.65","nXXXXXX","XXXXXX" ]
> .......
>
> ( DSN="DB2A" )
>
> ( UID="XXXXXXX" )
>
> ( PWD="********" )
>
> ( DBALIAS="DB2A" )
>
> ( PATCH1="384" )<------------THIS IS WRONG AHH!
>
> I really don't know where else to check. All other settings (ie.
> setting the TraceFlush information I am able to edit via the
> db2cli.ini file and have the changes take affect without a problem.)
>
> Any suggestions would be most appreciated. Thank you.