From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] AIX/370 Questions
Date: Thu, 2 Mar 2017 03:32:10 -0600 [thread overview]
Message-ID: <2F012DBB-A685-47E6-9642-C1AA9F8A38B0@ronnatalie.com> (raw)
In-Reply-To: <c240a5dc-9228-4c60-8235-6b40b62d175b@HK2APC01FT052.eop-APC01.prod.protection.outlook.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
I’m not sure I’d characturize AIX as “just another system V”. TCF was pretty darned slick and it had most of the contemporary 4BSD features at the time. It really didn’t have 3270 or other traditional IBM support on the 370 side. That was the major reason for the TCF. The normal way you worked on the 370 side was to sit at a AIX PS/2 system and either go in on TCP/IP or X or just run the 370 programs on the PS/2 via TCF.
next prev parent reply other threads:[~2017-03-02 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 3:15 Clem Cole
2017-03-02 3:51 ` jsteve
2017-03-02 9:32 ` Ronald Natalie [this message]
2017-03-02 13:11 ` Clem Cole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2F012DBB-A685-47E6-9642-C1AA9F8A38B0@ronnatalie.com \
--to=ron@ronnatalie.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).