🚀 go-pugleaf

In article <TADGUY.89Oct25132145@offa.cs.odu.edu> tadguy@cs.odu.edu (Tad Guy) writes:
>In article <8259@cbmvax.UUCP> valentin@cbmvax.UUCP (Valentin Pepelea) writes:
>   In article <89294.123406GIAMPAL@AUVM.BITNET> GIAMPAL@AUVM.BITNET writes:
>   >While on the subject of X, Y, and Z modem protocols, has any one
>   >ever seen/used any of these under CMS on an IBM mainframe?  Kermit
>   >is terribly frustrating and something like this would be helpful
>   >to many I'm sure.

>   The problem with transfering files to and from IBM mainframes is
>   that characters on the IBM side are not stored in ASCII format but
>   trather in EBCDIC (pronounced "epsodic") format.

>This happens only if you request character set translation to occur.

>Since some protocol converters can become ``transparent'' (as if done
>with CMS Kermit), it seems reasonable that someone could write a
>zyx-modem program for CMS...
>
>	...tad

When this problem was explained to me, we were using an IBM 7171 protocol
converter. When it was in transparent mode it would pass characters
transparently but still required an end-of-line character; this makes sense
to me because IBM mainframes talk in half-duplex and need some indication of
when to turn the line around.  Kermit uses an end of line indicator; I know
xmodem doesn't, am fairly sure that ymodem doesn't either, and I would bet
a very small sum of change that zmodem doesn't since it seems to have
descended from the others.  I think this all means that you can't use
[xyz]modem with IBM mainframes without a new form of protocol converter
or actually re-programming the current protocol converters.  Maybe someone
who knows more about this than I can explain better...

--> steve

-- 
Steve Wahl
Northern Telecom, Inc.       (612) 932-8079
S-100, 9701 Data Park        steve@ntmtka.mn.org
Minnetonka, MN 55343         {rosevax,bungia}!ntmtka!steve