A/UX 2.0: 3270 Terminal Emulation

1) I am working on a Macintosh IIx with A/UX 2.0 and a Kinetics EtherPort II.
The company where I work has lots of Sun systems, DOS machines, and IBM
mainframes (even a few Crays). TCP/IP is the prevalent Comm protocol.

Using Telnet, we have no problem logging into IBM
mainframes running TCP/IP. A/UX does not seem to have a 3270 terminal
entry, so the 3270 screens don't appear as they should. Is there a 3270
type of term entry that will let the screens appear correctly under
CommandShell?

2) I tried to use Intercon's TCP Connect II. This package does provide 3270
terminal types via Telnet. Running from A/UX, the program lets you log
into a local Sun, but I can't seem to get across the router. The Intercon
tech support engineer didn't have an answer other than running under
Macintosh OS and setting the gateway address in the "Admin TCP" CDEV.
Looking at the "MacTCP" CDEV under A/UX, the gateway field is 0.0.0.0 even
though the route command has been run. Do you know why I can't get past
the router from TCP Connect while running under A/UX?


1) There is currently no 3270 termcap entry for a 3270 session in A/UX 2.0 /etc/termcap file.

However, there is a software package called tn3270, which, we believe, came with the 4.3BSD distribution.  It provides a solution for talking to IBM hosts running VM/CMS with the University of Wisconsin who developed TCP/IP codes. The tn3270 also includes a file called "map3270", which contains mapping between characters entered from the keyboard and 3270 keys used by the "tn3270" program doing 3270 emulation from UNIX.  Tn3270 requires the 4.3BSD curses to run.

Porting 4.3BSD tn3270 to A/UX or using the third-party tn3270 product would be the ideal solution.

"Admin TCP" is not needed by A/UX 2.0 MacTCP since TCP/IP is configured by A/UX "ifconfig" and other network services, like Domain nameserver and/or gateway. You only need "MacTCP" in the System Folder.

2) We have no experience with the TCP/Connect II software.  Is there any
control file provided by TCP/Connect II to specify the gateway and/or the domain name server to be used?  Like in NCSA Telnet 2.3, the "config.tel" file may contain information on gateways and name servers.  We have tested the NCSA Telnet 2.3 with MacTCP in A/UX 2.0 to a remote host via a gateway (router) without any problem.  The gateway information is generated by the A/UX "/usr/etc/route" or the /etc/in.routed" process as all information in
A/UX MacTCP is disabled and can't be changed.


Published Date: Feb 18, 2012