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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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