SYSGFH@ALBNYVM1.BITNET (Grant Harders) (02/07/90)
I recently saw, on this list, mention of a problem when running MVS client Telnet from terminals attached to SNA control units. I have a similar problem, only with VM client Telnet. Here is what happens: - I Telnet to remote VM node "X", using a 3278-2 terminal (logmode=D4A32782) attached to a 3174-01L (SNA) control unit (no problem). (VM -> TCPIP(Telnet) -> K200 -> Ethernet -> Proteon box -> NYSERnet....) - Now at Node "X": - I "Dial VTAM" and receive the VTAM Logon screen (again no problem). - I type in a valid VTAM application name, press enter and am immediately disconnected. - I log back on (reconnect), type in "BEGIN" and find myself in the selected Node "X" VTAM application. I now continue my session with no further problems. This does not happen when: - I Telnet to a VM node using a terminal attached to a Non-SNA control unit or - gain access to the remote VM node through PVM (SNA and Non-SNA terminals are OK) or - do not "Dial VTAM", but use a VM based application (e.g. ISAAC). This only happens when: - I Telnet to a VM node using a terminal attached to a SNA control unit and - "Dial VTAM" and select a VTAM application. TCP/IP, 5798-FAL 1.2.1 with MX record support, is running on a VM/HPO 5 (516+) system with the Spartacus K-200 box and the Lippke 2.15 driver. Any suggestions would be appreciated. I am quite new to the TCP/IP game and expect that I may have missed something simple (I hope). Thanks. - Grant