× 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: CA downloads
  • From: Gerald Magnuson <magnuson@xxxxxxx>
  • Date: Fri, 17 Oct 1997 08:42:48 -0500

Thomas Q. McCollem wrote:
<snip>
> When downloading, however, Client Access
> views this field as type "HEX", and brings down each byte in it's hex
> notation (i.e., "1" comes down as "F1"). NetSoft Elite/400 on the other
> hand views this field as the "CHAR" field that it is, downloading it
> properly. Has anyone come across this situation?  Is there a workaround or
> PTF available?
> 
Before you can download data from client access you need to build an
CBWTFR.INI
file.  the following came from the READMESP.TXT from the service pack.:


2.6.1  TRANSFERRING DATA WHEN THE FILE CCSID IS 65535
-----------------------------------------------------
   The Data Transfer function will not translate data between ASCII and
   EBCDIC, if the CCSID of the file on the AS/400 is 65535.  Uploads to
the
   AS/400 file will generate message "CWBTF0005 - Data in this field is
   incorrect or does not match PC data type."  Downloads to the PC will
   complete successfully, but the data will not be converted, appearing
as
   hexidecimal data instead of the correct character data.

   Data Transfer will now allow conversion from CCSID 65535 to the PC
CCSID
   on transfers to the PC.  The AS/400 job CCSID will be used for the
   conversion.  Data Transfer will also convert from the PC CCSID to the
   AS/400 job CCSID for transfers to the AS/400 when fields are tagged
with
   the 65535 CCSID.

   This conversion is controlled by creating an INI file named
CWBTFR.INI in
   your Windows install directory (which is usually C:\WINDOWS).  For
your
   convenience, we have shipped a sample CWBTFR.INI file in the Client
Access
   install directory (which by default is C:\Program Files\IBM\Client
Access).
   We also included a CWBTFR.TXT file, which explains the different
fields. To
   use CWBTFR.INI, copy it to your Windows install directory and change
it to
   reflect the options you wish to use.

   The CWBTFR.INI file must contain ONE of following lines:

   ForceTranslation=0;     for no translation of 65535 data
     OR
   ForceTranslation=1;     for translation of 65535 data

   If the CWBTFR.INI file is not found, or the correct section and value
   names are not present in the CWBTFR.INI file, Data Transfer will
default
   to not translate 65535 data.

   

-- 
Gerald Magnuson          Sr. Programmer Analyst
The Knapheide Manufacturing Company
Quincy,  Illinois  62301       (217) 222-7178 ext. 291
+---
| 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 MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.