From: muta...@gmail.com   
      
   On Friday, June 18, 2021 at 5:50:19 AM UTC+10, anti...@math.uni.wroc.pl wrote:   
      
   > For some time my e-mail was on VM/CMS accessed via modem   
   > from a PC. Plain ATDT worked fine to establish connection.   
   > Terminal emulator (Kermit) knew that it was connected to   
   > EBCDIC system and did needed translation.   
   >   
   > Doing translation in modem actually would complicate   
   > terminal emulator.   
      
   Why? Kermit is already complicated by having the   
   burden of ASCII to EBCDIC translation, isn't it?   
      
   And you suddenly restrict yourself to terminal software   
   that has this complication.   
      
   > Namely, beside running terminal   
   > programs on mainframe terminal emulator also handled   
   > file transfers. Character translation inside modem   
   > would complicate file transfers, either terminal   
   > program would have to switch off character translation   
   > or somewhat compensate for it in file transfer protocol.   
      
   Yes, I agree that file transfers (instead of the terminal)   
   would need some complication added. Is this actually   
   a worse situation?   
      
   Regardless, solutions available are:   
      
   1. Use a file transfer protocol that sends binary data as   
   two hex characters for links that are considered to be   
   problematic. This will also bypass problems with other   
   characters like XON and Telnet.   
      
   2. Rely on the fixed 819/1047 translation being done and   
   compensate appropriately.   
      
   Note that I'm not trying to solve every problem in the   
   world simultaneously. I have a specific EBCDIC use-case   
   that I want to see work.   
      
   > So, you can do what you want, by why complicate things   
   > without need?   
      
   To take the burden off the vast bulk of the terminal   
   software. Terminal software already normally allows   
   you to set the modem dial string, e.g. ATDP or ATDT.   
   Why not ATDE?   
      
   > P.S. To folks who say that mainframe can not do ASYNC:   
   > this was done via a hardware hack on mainframe side.   
      
   Can you provide more details of this please?   
      
   Also, I assume that your VM/CMS software was still   
   operating on line mode, you couldn't run a character-based   
   application like micro-emacs?   
      
   Thanks. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)