Re: Character fields coming up as binary when viewed through SQL (JDBC)

Yes, that is the problem. There is a JDBC option to convert
untagged/binary/hex/for-bit-data character columns. If you specify that on
your connection JDBC URL you should get better results. Sorry, I don't have
JDBC URL syntax memorized; I'll leave that to you to look up. :)

On 7/11/07, James H. H. Lampert <jamesl@xxxxxxxxxxx> wrote:

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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.