The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Amdahl UTS, AIX/370, AIX/ESA
Date: Tue, 5 Nov 2019 11:07:51 -0700	[thread overview]
Message-ID: <CAK7dMtAsBrLfuPOam0EfF3JyMqarnSrv-aHC8SwBRa=tpowzow@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PNgQFLxjx7eUK-Q7BVL-5xSyx2JUk46oTSV=wekAg1eg@mail.gmail.com>

Clem,

The AIX/386 stuff is readily available http://ps-2.kev009.com/aixps2/
and can run in virtualbox
https://astr0baby.wordpress.com/2018/09/14/running-aix-1-3-inside-virtual-box-5-2-16/

Regards,
Kevin

On Tue, Nov 5, 2019 at 10:30 AM Clem Cole <clemc@ccc.com> wrote:
>
>
>
> On Sun, Nov 3, 2019 at 10:40 PM Gregg Levine <gregg.drwho8@gmail.com> wrote:
>>
>> I've been trying to track down a copy of AIX/370 for
>> that emulator, especially since I do run VM/370 Release 6 on it. One
>> of the people in the community indicated that it was a product
>
>
> I can verify for a fact that Locus received bug reports from all over the world. There was a team in LA set up to handled them.  True, the customers were reported to be more academic than commercial, but there were commercial customers..  For instance, I was told that my current employer ran the simulation for then proposed/in-development 80386 on a 370-PS/2 cluster under iTCF  FWIW: I was under the impression they used TCF to migrate the very long running simulations from two different processors (I don't know that for sure, but I have been told that by two different people, so I'm comfortable repeating it).
>
> I was also told, for an IBM customer to try to get the product was quite difficult.  IBM sales basically tried really hard to not provide it and you had to know about it and know you to ask to get it.  Charlie may know more, but he was working on AIX/RS-6000 which as has been pointed out was a separate code base.
>
> As for finding an old copy of AIX/370 or AIX/386 (which are the same except for specific code that cared), I wish you good luck.  IBM kept the IP locked up.   We were firewalled at Locus and the code was only on a couple of very special systems and access was tightly controlled.   I was not on that team, so I never saw their raw IP ( so I would not be contaminated as I was one of the TNC architects).  But I was allowed to talk with Bruce and Greg who were the TCF architects.   We did all talk about common issues; but Greg and Bruce stayed out the TNC IP (until after the IBM contract ended) and myself and Roman stayed out of TCF.
>
>
> Clem
>
>

  reply	other threads:[~2019-11-05 18:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03 21:05 Kevin Bowling
2019-11-03 23:29 ` Dennis Boone
2019-11-04  0:06   ` Kevin Bowling
2019-11-04  1:29   ` Dennis Boone
2019-11-04  1:58     ` Kevin Bowling
2019-11-04  3:39 ` Gregg Levine
2019-11-04  4:49   ` Kevin Bowling
2019-11-04 15:32   ` Adam Thornton
2019-11-05 16:21   ` Ronald Natalie
2019-11-05 18:04     ` Kevin Bowling
2019-11-05 19:22       ` ron
2019-11-05 17:30   ` Clem Cole
2019-11-05 18:07     ` Kevin Bowling [this message]
2019-11-05 18:15       ` Clem Cole
2019-11-05 19:03       ` Christopher Browne
2019-11-05 19:12         ` Kevin Bowling
2019-11-05 19:26           ` SPC
2019-11-05 19:28             ` SPC
2019-11-05 20:26               ` Kevin Bowling
2019-11-05 20:10         ` Clem Cole
2019-11-05 20:42           ` Kevin Bowling
2019-11-05 21:11             ` Clem Cole
2019-11-05 22:11     ` [TUHS] one element of one of M factions of N companies [Re: " Charles H Sauer
2019-11-06  0:06       ` Theodore Y. Ts'o
2019-11-06  3:36         ` Charles H. Sauer
2019-11-06  7:59           ` [TUHS] AOS and IBM/RT " SPC
2019-11-06 15:51             ` Charles H Sauer
2019-11-07 22:40               ` Grant Taylor via TUHS
2019-11-08  4:39                 ` Jason Stevens
2019-11-21  6:26             ` Al Kossow
2019-11-21 11:58               ` Dan Cross
2019-11-21 13:07                 ` Brad Spencer
2019-11-21 14:19                   ` Dan Cross
2019-11-21 16:16                     ` Chet Ramey
2019-11-21 20:53                       ` Dan Cross
2019-11-21 16:43                     ` greg travis
2019-11-21 19:41                       ` arnold
2019-11-21 20:21                         ` Jon Steinhart
2019-11-21 17:33                   ` Charles H Sauer
2019-11-21 17:36                     ` Dan Cross
2019-11-21 18:11                     ` Brad Spencer
2019-11-21 17:29                 ` Charles H Sauer
2019-11-22 20:38                 ` Al Kossow

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='CAK7dMtAsBrLfuPOam0EfF3JyMqarnSrv-aHC8SwBRa=tpowzow@mail.gmail.com' \
    --to=kevin.bowling@kev009.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@tuhs.org \
    /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).