Re: SQL weirdness: character fields look fine in STRSQL, but turn to hex in SQuirreL or in a BIRT report -- 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.

Subject: Re: SQL weirdness: character fields look fine in STRSQL, but turn to hex in SQuirreL or in a BIRT report
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 10 Apr 2018 14:38:42 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 4/10/18, 2:26 PM, Bryan Dietz wrote:

maybe the fields are in ccsid 65535.

Check to see if you have HEX translation on, in Squierrel it is and
option for JT400 driver properities

Hex translation was not enabled. I enabled it ("character"). No change. I disconnected and reconnected. Still no change. Tried "binary." Still no change.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.