×
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.
So it sounds like you're suggesting I somehow change the declaration of the field in my files to BINARY. Can I do that in the DDS? Can I do it with some sort of a CHG or ALTER TABLE?
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, October 19, 2012 10:54 AM
To: java400-l@xxxxxxxxxxxx
Subject: Re: JT400 Record-level access problem
On 19 Oct 2012 10:46, CRPence wrote:
I suppose a likely problem origin is for use of CCSID 37 instead of
FOR BIT DATA; the collation [Sort Sequence] would be moot for the kind
of issue I am thinking of. <<SNIP>>
Actually the use of CHAR, even with FOR BIT DATA, would likely suffer the same type of problem I alluded. That is to suggest, even the declaration of CHAR FOR BIT DATA is still "character-string" data for which the blank-pad character changes between encoding choices ASCII vs EBCDIC. Thus I presume the data type to support 8-byte unsigned integer
*must* be BINARY... which I expect the database key processing *must*
*never* infer any pad-character to be used for comparisons.
--
Regards, Chuck
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/java400-l.
midrange.com
