|
Hi Kyle, One further point about DSPF -- use F15 to see the CCSID of the file and change it if necessary. Peter Dow Dow Software Services, Inc. www.dowsoftware.com 909 793-9050 voice 909 793-4480 fax > -----Original Message----- > From: rpg400-l-bounces@xxxxxxxxxxxx > [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Simon Coulter > Sent: Saturday, January 21, 2006 1:39 PM > To: RPG programming on the AS400 / iSeries > Subject: Re: Reading IFS bin file into an RPG variable > > > > On 22/01/2006, at 3:16 AM, Kyle Collie wrote: > > > If I do a wrklnk on an IFS file, I see this: > > > > GIF89a ÷ ÿÿÿðíîGFG... > > > > But in debug, my temp variable contains this: > > > > åñã / 7 0ÒÓåãå x¿ÝzÞ^xÐÞ ~xzwÝ(r) (í ... > > > > Not nearly the same. > > > > What am I missing? If is a codepage issue? > > When viewing data in binary you can only rely on the hexadecimal code > points of each character. From the above 3 points you can see that the > data in debug is the correct output. The data in DSPF has, probably, > been converted from ASCII to EBCDIC. > > Using the F10=Display Hex option in DSPF will show you the hex data. > This should match the hex output in debug. > > NOTE:- On 530 DSPF shows the real Hex data from the file content. On > some earlier releases DSPF would show the Hex values of the converted > output which is not much use at all. > > NOTE:- On some early releases DSPF only shows Hex output when using a > 24*80 display device. It will not show hex output in wide-screen > (27*132) mode--also less than helpful. I see this "oversight" has been > corrected in 530. I don't know in exactly what release they fixed this. > > Regards, > Simon Coulter. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.14.21/236 - Release Date: 1/20/2006
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.