× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: File Attached cwbtfr.ini (fwd)
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Mon, 30 Mar 1998 17:30:57 -0600

Ah - but if you're files are created on the 400 with the correct CCSID
(for most of us in North America that would probably be 037), instead of
65535 (which means 'Do NOT translate') there would be no problem.

The new CA/400 file transfer that pays attention to these CCSID tags IS
actually a step forward as it's supposed to handle translation between
different character sets.

I believe the actual source of the problem goes gack to V3R1, or
sometime in V2 (I'm sure Al Barsa will recall  :-)   ) when the CCSID
tag was introduced, and the release update to that new release didn't go
through a correct conversion and retag your current files based on your
QCHRID or QLANGID.  Even today on V4 a lot of systems that started off
years ago and have been through multiple release conversions still have
QCCSID set to 65535.



Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: Don [SMTP:dr2@access.digex.net]
> Sent: Sunday, March 29, 1998 6:15 PM
> To:   midrange-l@midrange.com
> Subject:      File Attached cwbtfr.ini (fwd)
> 
> 
> To the folks that had problems with download translation, make sure
> this
> little file is in your c:\windows directory...  IT SHOULD HAVE BEEN
> ADDED
> on the load process, but some toad decided that we wouldn't need to
> make
> sure that we were running ebcdic on a 400 and ascii on a PC...they
> thought
> we would WANT TO DEFAULT to uploading files in ASCII format to the
> 400...
> 
> go figure...  This may be part of your problem...
> 
> (Tks to Mike Shaw!)
> 
> 
> It's needed for Client Access For Win 95 File Transfer.
> 
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.