RE: Client Access Question

Read the  readmesp.txt  file included with CA/400 Win95/NT Service Packs.

Particularly this section (that has been in all the Service Packs for well over 
a year now):

3.0  DATA TRANSFER CONSIDERATIONS
---------------------------------
   The following sections describe additional support or known
   problems that you may notice while using the Data Transfer
   function.
 
3.1  TRANSFERRING DATA WHEN THE FILE OR DATA CCSID IS 65535
                            OR
WHY DOES MY DATA LOOK LIKE GARBAGE WHEN I PERFORMED A DOWNLOAD?
---------------------------------------------------------------
   By default, the Data Transfer function will not translate data between
   EBCDIC and ASCII if the data is tagged with a CCSID of 65535.  In
   previous versions of the Win 95/NT Client Access product, the 65535
   conversion was controlled by the CWBTFR.INI file.  This process
   has been changed, and the conversion is now controlled by the
   Data Transfer user interface.  Once the setting has been made in the
   user interface, it is then stored in the transfer request.  This is
   only true for .TTO and .TFR files.  .RTO and .DT files are still
   controlled by the CWBTFR.INI file.  The conversion setting for .RTO
   and .DT files can be modified in the Data Transfer user interface, but
   the setting will not be saved.
 
   The setting to control the conversion is found in the File, Properties
   information.
 
   WARNING:  This fix is designed as a workaround for people that can
             not change the CCSID of their files.  In order for this
             translation to work properly, you must be confident the
             data in the file matches the CCSID of your user profile.
             The design of the AS/400 is that data with a 65535 CCSID
             are not to be converted.  This fix will attempt to do a
             conversion of the data from the job CCSID to the PC CCSID.
             This conversion may not work if the data in the file does
             not match the user profile/job CCSID.
 
   The correct solution to this problem is to appropriately tag the data
   with the correct CCSID.  One way of doing this is by using CHGPF.
 
   For more information on the 65535 CCSID, see topic 2.2.3.2 in the
   AS/400 National Language Support book, SC41-1301-00.




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


-----Original Message-----
From:   Alex A Moore/EllisHosiery [SMTP:alexm@ellishosiery.com]
Sent:   Thursday, November 12, 1998 6:47 AM
To:     MIDRANGE-L@midrange.com
Subject:        Re: Client Access Question

Your data that appears as hex on the client (PC) side is probably defined 
as hex on the server (AS/400) side.  More often than not, this is the 
result of not externally defining the database file on the AS/400.  The 
file may have been created via CRTPF with no source or could have been an 
S/36 file.  The proper use of CCSID will also work, however some versions 
of client access / PTFs have some difficulty with this feature.




Wexler <ywexler@ibm.net> on 11/11/98 08:55:32 AM
Please respond to MIDRANGE-L@midrange.com
To:     MIDRANGE-L@midrange.com
cc: 
Subject:        Re: Client Access Question

Dana,
Check the CCSID on AS/400 side and at PC side.

KeatonDana@aol.com wrote:

> Hello all,
>
> I'm having trouble downloading a file from the 400.  I download it as 
ascii
> but it seems to keep the format of hex.  What gives?  I'm not sure how to
> proceed.  Any help will be appreciated.  Thanks.
>
> Dana Keaton
>
> Keatondana@aol.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---