From: clemc@ccc.com (Clem cole)
Subject: [TUHS] UNIX on S/370
Date: Mon, 20 Nov 2017 23:34:11 -0500 [thread overview]
Message-ID: <374F4C47-30B2-4E3E-A493-62C259D25CF0@ccc.com> (raw)
In-Reply-To: <05ec01d3627a$6960cc80$3c226580$@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
Right. Generally you used the ps/2 as the terminals for AIX/370
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
> On Nov 20, 2017, at 10:40 PM, Ron Natalie <ron at ronnatalie.com> wrote:
>
> I'm pretty sure you could, but only on very rudimentary line mode stuff. Note that an IBM mainframe terminal doesn't really have the same paradigm as an ASCII terminal.
>
> You could go to a VM monitor and type IPL AIX and watch UNIX boot up.
>
>
> -----Original Message-----
> From: TUHS [mailto:tuhs-bounces at minnie.tuhs.org] On Behalf Of Grant Taylor via TUHS
> Sent: Monday, November 20, 2017 10:29 PM
> To: tuhs at minnie.tuhs.org
> Subject: Re: [TUHS] UNIX on S/370
>
>> On 11/20/2017 06:15 PM, Ron Natalie wrote:
>> AIX deflected all this by actually making the user facing stuff hang
>> off the i860/i386 nodes.
>
> Does that mean that you couldn't access AIX/370 from a traditional mainframe terminal?
>
> That seems bizarre to me. But it does sound like some other strange things I've heard come out of IBM before.
>
>> I remember talking extensively to Barry Appleman (VM’s TCP IP guY)
>> about writing an X3270 xterm variant.
>
> What would that have done? Are you meaning an app that would run on
> non-AIX/370 OSs that could then act similar to the i860/i386 client / node? (Was it trying to emulate a traditional serial dumb terminal?)
>
> #confused
>
>
>
> --
> Grant. . . .
> unix || die
>
next prev parent reply other threads:[~2017-11-21 4:34 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 0:57 Nemo
2017-11-20 1:01 ` Ronald Natalie
2017-11-20 1:06 ` Dave Horsfall
2017-11-20 3:50 ` arnold
2017-11-20 15:23 ` Clem Cole
2017-11-20 16:03 ` ron minnich
2017-11-20 16:31 ` Clem Cole
2017-11-20 19:44 ` Paul Winalski
2017-11-20 19:56 ` Larry McVoy
2017-11-20 23:43 ` Ron Natalie
2017-11-20 23:45 ` Larry McVoy
2017-11-20 23:49 ` Ron Natalie
[not found] ` <CAC20D2N=aBhdON1YqHH57ZG-TmC62yWGF4_=HK5Gp2XwdbHkyQ@mail.gmail.com>
2017-11-21 2:41 ` Larry McVoy
2017-11-29 22:42 ` Dave Horsfall
2017-11-29 22:55 ` ron minnich
2017-11-21 1:15 ` Ron Natalie
2017-11-21 3:29 ` Grant Taylor
2017-11-21 3:40 ` Ron Natalie
2017-11-21 3:46 ` Grant Taylor
2017-11-21 8:09 ` arnold
2017-11-21 16:49 ` Paul Winalski
2017-11-21 4:34 ` Clem cole [this message]
2017-11-21 5:42 ` Grant Taylor
2017-11-21 12:00 ` Ron Natalie
2017-11-21 13:51 ` Clem Cole
2017-11-21 14:59 ` Larry McVoy
2017-11-21 17:06 ` Clem Cole
2017-11-21 17:23 ` Clem Cole
2017-11-21 18:29 ` Larry McVoy
2017-11-21 19:10 ` Clem Cole
2017-11-21 15:40 ` Ron Natalie
2017-11-21 15:45 ` Larry McVoy
2017-11-21 13:24 ` Clem Cole
2017-11-22 1:33 ` Kevin Bowling
2017-11-22 6:35 ` Wesley Parish
2017-11-22 9:38 ` Kevin Bowling
2017-11-22 13:40 ` Clem Cole
2017-11-22 14:09 ` Ron Natalie
2017-11-22 13:51 ` Clem Cole
2017-11-22 14:04 ` Ron Natalie
2017-11-20 16:05 Noel Chiappa
2017-11-20 16:37 ` Clem Cole
2017-11-20 16:47 ` Charles H Sauer
2017-11-20 17:44 ` Toby Thain
2017-11-20 19:07 ` Paul Winalski
2017-11-20 19:10 ` Larry McVoy
2017-11-20 19:36 ` Warner Losh
2017-11-20 19:36 ` Larry McVoy
2017-11-20 19:39 ` Larry McVoy
2017-11-20 19:56 ` Arthur Krewat
2017-11-20 19:59 ` Larry McVoy
2017-11-20 19:27 ` arnold
2017-11-20 19:29 ` Larry McVoy
2017-11-20 22:56 ` Michael Parson
2017-11-20 23:23 ` Larry McVoy
2017-11-21 2:56 Noel Chiappa
2017-11-21 3:15 ` Ron Natalie
2017-11-21 3:51 ` Larry McVoy
2017-11-21 5:14 ` Warner Losh
2017-11-21 5:20 ` Larry McVoy
2017-11-22 15:38 Noel Chiappa
2017-11-28 0:13 ` Kevin Bowling
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=374F4C47-30B2-4E3E-A493-62C259D25CF0@ccc.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).