Re: Attempting to use SQL HEX -- MIDRANGE-L

Subject: Re: Attempting to use SQL HEX
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Wed, 11 Jun 2014 14:39:14 -0400
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Jun 11, 2014 at 2:34 PM, Alan Shore <ashore@xxxxxxxx> wrote:

I also tried that - but when I send that value down in a web service,
the 40 translates to blank

Well, that's because it *IS* a blank (in typical EBCDIC encoding).
Bytes are bytes. What is it that you need? A 32-byte binary value,
or a 64-byte string whose value is the hexadecimal representation of a
32-byte binary value?

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Attempting to use SQL HEX , Alan Shore

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.