A question about Connect PE 5.0

Max Scarpa

A question about Connect PE 5.0
We have troubles with DB2 Connect Personal Edition 5.0.

On 30th Dec. all was ok, now 5th of January 2000 we can't connect to DB2 s/390
V5.

I think that DB2 Connect PE ODBC driver is not Y2K compatible and we obtain
the error:

parameter "119c" , value "", not supported.

I'm downloading Fixpack 6 & 12, but is it the right way to solve our problems ?

Any help will be appreciated

Thanks
Max Scarpa
System Admin



Peter Schwarcz (Bigpond)

Re: A question about Connect PE 5.0
(in response to Max Scarpa)
Massimo,

From my experience a 119c error is indicative of a codepage error.

You should check your DB2CODEPAGE on your PC and on OS/390.

You can check your NT settings from a DB2 command line prompt by typing
DB2SET, and review any values that you have set.

On OS/390 your codepage is set in the DSNHDECP member that is usually kept
in the same member as your DSNZPARM.

The problem could have been introduced over a restart of DB2 on OS/390 if
your DECP member was assembled some time before DB2 was restarted.



Regards,
Peter Schwarcz
PO Box 426,
Hawthorn Victoria
Australia 3122
[login to unmask email]


----- Original Message -----
From: Massimo Scarpa <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Wednesday, January 05, 2000 8:43 PM
Subject: A question about Connect PE 5.0


> We have troubles with DB2 Connect Personal Edition 5.0.
>
> On 30th Dec. all was ok, now 5th of January 2000 we can't connect to DB2
s/390
> V5.
>
> I think that DB2 Connect PE ODBC driver is not Y2K compatible and we
obtain
> the error:
>
> parameter "119c" , value "", not supported.
>
> I'm downloading Fixpack 6 & 12, but is it the right way to solve our
problems ?
>
> Any help will be appreciated
>
> Thanks
> Max Scarpa
> System Admin
>
>
>





Michale Yu

Re: A question about Connect PE 5.0
(in response to Peter Schwarcz (Bigpond))
Hello Massimo:

I have met the same problem when I connect to DB2 for OS/390 through DB2
CONNECT EE from NT several months ago. The reason is that either your code
page of DRDA AS or DRDA AR is not valide,I have solved this problem by
define correct CCSID for DRDA AS and DRDA AR both.You
could check information of CCSID in DB2 INSTALLATION and DB2 CONNECT EE
document.

Best regards.

from [login to unmask email]