Z/OS QMF & DB2 connect - unicode issues

Jaime Fernandez

Z/OS QMF & DB2 connect - unicode issues
Some time ago we implemented Conversion services an started testing with
tables in unicode. Recently founded that tables with graphic columns
produced errors when trying to be accessed from standard ebcdic (and
ascii, I guess) applications. I could find this note about:
http://www-1.ibm.com/support/docview.wss?uid=swg21206527

The note points to APAR PQ98170, wich fixes... some of the issues.
Applying this ptf we could work with those tables using spufi or dsntiaul,
but not QMF or DB2 Connect. The message we still get is:

"Your SQL statement referenced a character string with a coded character
set ID(CCSID) 01200 in a coded character set that differs from the
current one. To use this character string at the current server, this
character string must be translated from the source CCSID 01200 to the
target CCSID 65534"

I'm completely lost, because as long as I know 65534 is the default value
provided for non-unicode mixed and graphic ccsid's, and translation
from/to 65534 is not supported by Conversion services. So, how can I
force it? Should I change their values? Don't think so!! But I couldn´t
find any similar fix to QMF and DB2 Connect.

Anybody who has experienced this problems, or have some ideas...?

Thanks in advance

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Steve McAuliffe

Re: Z/OS QMF & DB2 connect - unicode issues
(in response to Jaime Fernandez)
Jamie,

May not be of use, but I had a similar error when testing the JDBC driver to the host, it seems that the full set of Java character sets wasn't installed on my machine.

I think it was this one..jre/lib/charsets.jar


Cheers,
Steve McAuliffe
Tel: (020) 8760 6988
Internal: x 66988

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf Of Jaime Fernandez
Sent: 28 June 2005 17:54
To: [login to unmask email]
Subject: [DB2-L] Z/OS QMF & DB2 connect - unicode issues

Some time ago we implemented Conversion services an started testing with tables in unicode. Recently founded that tables with graphic columns produced errors when trying to be accessed from standard ebcdic (and ascii, I guess) applications. I could find this note about:
http://www-1.ibm.com/support/docview.wss?uid=swg21206527

The note points to APAR PQ98170, wich fixes... some of the issues.
Applying this ptf we could work with those tables using spufi or dsntiaul, but not QMF or DB2 Connect. The message we still get is:

"Your SQL statement referenced a character string with a coded character set ID(CCSID) 01200 in a coded character set that differs from the current one. To use this character string at the current server, this character string must be translated from the source CCSID 01200 to the target CCSID 65534"

I'm completely lost, because as long as I know 65534 is the default value provided for non-unicode mixed and graphic ccsid's, and translation from/to 65534 is not supported by Conversion services. So, how can I force it? Should I change their values? Don't think so!! But I couldn´t find any similar fix to QMF and DB2 Connect.

Anybody who has experienced this problems, or have some ideas...?

Thanks in advance

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are authorised and regulated by the Financial Services Authority.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Roger Miller

Re: Z/OS QMF & DB2 connect - unicode issues
(in response to Steve McAuliffe)
65534 is the CCSID used for mixed and graphic on a subsystem where the
mixed attribute is turned off, in short an error. See the Installation
Guide Appendix for examples of CCSIDs. Here is a paste:

If you specify MIXED DATA=NO on installation panel DSNTIPF, specify an
SBCS CCSID from Table 122 in the EBCDIC CCSID field on DSNTIPF. You must
specify a SBCS CCSID from Table 123 on page 519 in the ASCII CCSID field
on DSNTIPF. Mixed character data and graphic data cannot be defined on a
system when you specify MIXED DATA=NO.

If you specify MIXED DATA=YES on installation panel DSNTIPF, specify a
mixed data CCSID from Table 122 in the EBCDIC CCSID field on DSNTIPF. You
must specify a mixed CCSID from Table 123 on page 519 in the ASCII CCSID
field. Table 122 and Table 123 on page 519 show the associated CCSIDs that
DB2 assigns for SBCS and DBCS data when you specify a specific MCCSID.

Roger Miller

On Tue, 28 Jun 2005 11:53:54 -0500, Jaime Fernandez <[login to unmask email]>
wrote:

>Some time ago we implemented Conversion services an started testing with
>tables in unicode. Recently founded that tables with graphic columns
>produced errors when trying to be accessed from standard ebcdic (and
>ascii, I guess) applications. I could find this note about:
>http://www-1.ibm.com/support/docview.wss?uid=swg21206527
>
>The note points to APAR PQ98170, wich fixes... some of the issues.
>Applying this ptf we could work with those tables using spufi or dsntiaul,
>but not QMF or DB2 Connect. The message we still get is:
>
>"Your SQL statement referenced a character string with a coded character
>set ID(CCSID) 01200 in a coded character set that differs from the
>current one. To use this character string at the current server, this
>character string must be translated from the source CCSID 01200 to the
>target CCSID 65534"
>
>I'm completely lost, because as long as I know 65534 is the default value
>provided for non-unicode mixed and graphic ccsid's, and translation
>from/to 65534 is not supported by Conversion services. So, how can I
>force it? Should I change their values? Don't think so!! But I couldn´t
>find any similar fix to QMF and DB2 Connect.
>
>Anybody who has experienced this problems, or have some ideas...?
>
>Thanks in advance
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm