RE: Character fields coming up as binary when viewed through SQL (JDBC) -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

James,

Is the QZDASOINIT job showing any CPF5035 and/or CPF5029 diagnostic
errors?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H.
Lampert
Sent: Wednesday, July 11, 2007 10:50 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Character fields coming up as binary when viewed through SQL
(JDBC)

We've got a file that's giving us some grief.

If we view it from QuestView, everything is hunky-dory.
Likewise, if we view one of our QuestView demonstration
files from the SQuirreL SQL/JDBC client, everything still
works fine.

But if we access the problem file from SQuirreL, (or,
evidently, from anything else that uses JDBC) it thinks
the character fields are binary.

The one thing that jumps out at me, and suggests itself as
the cause of the problem, is that while a DSPFFD on a
QuestView demonstration file shows a CCSID of 37 for the
character fields, the problem file's character fields show
a CCSID of 65535 (isn't that the value for "unspecified"?)

Is this indeed the cause of the problem? Or is it
something else?

What can be done to fix, or at least mitigate, it?

--
JHHL

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.