On 16-Jun-2015 12:19 -0600, James H. H. Lampert wrote:
It sounds oxymoronic.
What exactly is a "Binary Character" field?
"5" instead of "A" in the DDS;
AFaIK: In DDS specification, I believe that would be: "H" instead of
"A". Probably also the same effect [a Binary Character field] is seen
for a field defined with the [resolved] field-level keyword of CCSID and
the specification of 65535 [or possibly the special-value *HEX, if
supported].
"5" instead of "A" returned by QUSLFLD, but what . . . is . . . it?
Both the DDS data type H or SQL CHAR FOR BIT DATA are implemented as
a /shift/ data type whereby an effective [but non-existent\imaginary]
keyboard shift denotes data-type restrictions\characteristics; the term
is borrowed from other /shifts/ such as forced-upper from CapsLock and
the Double-Byte mode shift. The /hexadecimal/ shifted type suggests
that any character data that is entered into the field must not get
translated according to the character encoding or code page associated
with the Record Format [that instead may come\resolve from the value for
the File].
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.
midrange.com
