× 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: CCSID 65535 Translation in Client Access Transfer Requests
  • From: "john" <jbussert@xxxxxxxxxxx>
  • Date: Mon, 10 Jan 2000 15:18:52 -0600
  • Importance: Normal

Hey - now your published!

Let me know what the answer is.  I feel an article coming on...

jb

> -----Original Message-----
> From: mark.stepan@merrillcorp.com [mailto:mark.stepan@merrillcorp.com]
> Sent: Monday, January 10, 2000 2:36 PM
> To: midrange-l@midrange.com
> Subject: CCSID 65535 Translation in Client Access Transfer Requests
> 
> 
> 
> 
> Can someone out there please clarify this CCSID stuff for me? 
> Here's the
> situation:
> 
> We have a computer that sits in the background and does 
> nothing but file
> transfers between our Novell/NT servers and the 400's. We 
> starting moving away
> from the DOS version of Client Access in favor of the Windows 
> 9x/NT version. I
> came across a nuance that reared its head in the Windows 
> version where the file
> was all in HEX on the NT server pafter a download]. I tracked 
> it down to the
> CCSID translation parameter that appears to reside at the 
> ODBC configuration
> level of the PC as well as at the Transfer Request level. I 
> can't seem to make
> the setting "stick" such that I can put this matter to bed. The other
> alternative is to try and address the files that are created 
> on the 400's to
> make sure that they use CCSID 37 [as they will with a normal 
> DDS file].
> 
> I'm sure anyone that's dealt with this stuff knows what I'm 
> talking about and
> doesn't likely need any more explanation. Any ideas, 
> comments, or suggestions
> would be greatly appreciated.
> 
> Mark Stepan
> Technical Support Manager
> Merrill Corporation/St Cloud
> Mark.Stepan@MerrillCorp.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
> +---
> 
+---
| 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
+---

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.