IETF Logo Mail Archive

ASCII tn3270 datastream

Tom Schlender <TWS1@rsvl.unisys.com> Thu, 14 October 1993 19:18 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11165; 14 Oct 93 15:18 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11161; 14 Oct 93 15:18 EDT
Received: from list.nih.gov by CNRI.Reston.VA.US id aa26125; 14 Oct 93 15:18 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (IBM VM SMTP V2R2) with BSMTP id 8445; Thu, 14 Oct 93 15:16:47 EDT
Received: from LIST.NIH.GOV by LIST.NIH.GOV (Mailer R2.10 ptf000) with BSMTP id 8443; Thu, 14 Oct 93 15:16:39 EDT
Date: Thu, 14 Oct 1993 13:44:04 -0600
Reply-To: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
X-Orig-Sender: IETF TN3270E Working Group List <TN3270E@list.nih.gov>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tom Schlender <TWS1@rsvl.unisys.com>
Organization: Unisys Corp., Roseville, MN
Subject: ASCII tn3270 datastream
X-To: tn3270e@list.nih.gov
To: Multiple recipients of list TN3270E <TN3270E@list.nih.gov>
Message-ID: <9310141518.aa26125@CNRI.Reston.VA.US>

We provide a Telnet server on our mainframe that provides TN3270
support.  We have an unusual situation in that our 3270 application
programs on the mainframe expect the data to be in ASCII rather than
EBCDIC.  Therefore, our communications program is converting the
ASCII data to EBCDIC on output, and from EBCDIC to ASCII on input.
Of course, the client on the PC is also doing ASCII/EBCDIC
conversions.  For performance reasons, we would like to avoid the
ASCII/EBCDIC conversions at both ends; that is, send ASCII rather
than EBCDIC when in tn3270 mode.

Is there a method using current 3270 capabilities for both parties to
agree to send ASCII rather than EBCDIC while in tn3270 mode?  If not,
is there some way to incorporate this into the TN3270 Enhancements
draft RFC?

Thank you.
Tom Schlender                    tws1@rsvl.unisys.com
Unisys Corporation               Phone: (612) 635-5621
Roseville, MN

v2.23.0 | Report a Bug | By Email