Re: NT CA/400 transfer only HEX?

[Lo <raikovl1@xxxxxxxxxxxxxxxx>]

Christian Zander wrote:
> 
> Hello everybody,
> 
> maybe I missed something, but I have a problem with a filetransfer to PC
> and from PC with CA/400 for Win95/NT under NT 4.0 SP3.
> 
> I have an AS/400-file with one field. It is 128 Bytes long and does contain
> only "legal" characters (0-9, A-Z, -, +). Whenever I try to transfer it
> with rtopcb or interactive I get the field data in HEX. There seems to be
> no possibility to transfer it as normal CHAR.
> 
> With DOS CA/400 it works without problems. I have no difficulties under
> DOS. I need to transfer them correctly because I have some batch-files to
> transfer and process the files. I don't like to write a program which
> changes the HEX-notation back to normal ASCII.
> 
> Has anybody some ideas how and why this happens? Is there a possibility to
> use the DOS-transfer-programs like it is with the OS/2-CA/400 (you know,
> virtual DOS)?
> 
> Thanks in advance
> 
>  Chris
>  calling from Kassel, Germany

Look at your AS/400 CCSID parameter. I'd say you'll be on the safe side
only if you set it up to something meaningful (not default 65535) for
both the SYSVAL and your database (files).
Files are best recreated, because as far as I can remember, you can't
change CCSID of a logical - or maybe it was a problem only for the
previous releases.

Of course, there are PC-related workarounds, e.g. you can force CA/400
to translate 65535 data, but for that you'll need to fix every PC,
because the default is no translation.

One thing I can't understand is why IBM decided to convert 65535 data
to  character-hexadecimal representation in the first place. Who would
possibly need that?

Lo
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---