From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] AIX/370 Questions
Date: Wed, 1 Mar 2017 22:15:54 -0500 [thread overview]
Message-ID: <CAC20D2NDooFTCBjVbvudmG7ia3YYkVs1_-2o466-ohni-1r+Rw@mail.gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On Wed, Mar 1, 2017 at 9:13 PM, Jason Stevens <
jsteve at superglobalmegacorp.com> wrote:
> Slightly off or on topic, but since you seem to know, and I've never seen
> aix 370 in the eild, did it require VM?
>
It could boot on raw HW.
> Did it take advantage of SNA, and allow front ends, along with SNA
> gateways and 3270's?
>
Not sure how to answer this. It was an IBM product and could be used
with a lot of other IBM's products. Generally speaking it was aimed at the
Educational market, although there were some commercial customers, for
instance Intel was reputed to do a lot of the 486 simulation on a TCF
cluster (I don't know that for sure, that was before I worked for Intel).
>
> Or was it more of a hosted TCP/IP accessable system?
>
Clearly, if you had a PS/2 in the cluster, that was your access point. I
think it was all mixed up in the politics of the day at IBM between
Enterprise, Workstations, and Entry systems. TCP/IP and Ethernets were not
something IBM wanted to use naturally. But the Educational market did
use it and certainly some folks at IBM saw the value.
UNIX was needed for the Education market as was TCP/IP so that going to be
the pointed head of the stick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170301/2cfe6145/attachment.html>
next reply other threads:[~2017-03-02 3:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 3:15 Clem Cole [this message]
2017-03-02 3:51 ` jsteve
2017-03-02 9:32 ` Ronald Natalie
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=CAC20D2NDooFTCBjVbvudmG7ia3YYkVs1_-2o466-ohni-1r+Rw@mail.gmail.com \
--to=clemc@ccc.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).