Re: Getting hex data in Client Access file transfers -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Getting hex data in Client Access file transfers
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 14 Dec 2002 05:40:48 -0600
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Mark

This behavior is usually associated with the 66535 CCSID. Go to menu utem
File->Properties and look for the Conversions tab. There's a checkbox for
converting CCSID 66535.

HTH

Vern

At 09:15 PM 12/13/02 -0800, you wrote:

--
[ Picked text/plain from multipart/alternative ]

Does anyone know why signed numeric fields on the AS/400 are transfered as
hex when going to the PC?

I'm using Client Access Express for Windows95/98/NT. OS400 is V4R5 and
Windows is NT.

Thanks in advance,

Mark Taylor

As an Amazon Associate we earn from qualifying purchases.

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