Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.folklore.computers > #210335 > unrolled thread
| Started by | robin.vowels@gmail.com |
|---|---|
| First post | 2020-03-08 16:07 -0700 |
| Last post | 2020-03-08 17:19 -0700 |
| Articles | 20 on this page of 590 — 35 participants |
Back to article view | Back to alt.folklore.computers
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: IBM system/360 ad robin.vowels@gmail.com - 2020-03-08 16:07 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-03-08 16:50 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-08 17:19 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-03-09 13:19 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-09 16:18 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-09 12:16 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-09 16:35 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-09 16:18 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-09 19:41 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-10 12:29 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-10 19:02 -0400
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-11 12:09 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-11 14:52 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-12 19:08 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-12 16:46 -0400
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-12 15:07 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-11 12:10 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-10 01:06 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-10 11:33 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-10 18:48 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-10 12:09 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-10 22:46 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-11 12:18 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-11 19:49 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-11 13:11 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-12 19:08 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-12 16:42 -0400
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-03-12 22:11 +0000
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-03-12 23:49 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-03-13 08:36 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-11 14:52 -0700
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-03-11 22:17 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-11 16:47 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-29 11:40 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 13:52 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 18:06 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-27 11:32 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-27 19:08 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-11 14:52 -0700
Re: IBM system/360 ad robin.vowels@gmail.com - 2020-03-11 18:17 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-12 15:03 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-03-12 15:29 -0700
Re: IBM system/360 ad robin.vowels@gmail.com - 2020-03-12 19:38 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-13 10:18 -0700
Re: IBM system/360 ad usenet@only.tnx (Questor) - 2020-03-13 18:07 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-13 11:43 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-27 11:31 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-27 19:08 +0000
Re: IBM system/360 ad antispam@math.uni.wroc.pl - 2020-06-12 01:34 +0000
Re: IBM system/360-30 John Levine <johnl@taugh.com> - 2020-06-13 00:19 +0000
Re: IBM system/360-30 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-06-13 00:26 +0000
Re: IBM system/360-30 Dan Espen <dan1espen@gmail.com> - 2020-06-12 20:38 -0400
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-03-09 21:38 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-10 12:11 -0400
Re: IBM system/360 ad antispam@math.uni.wroc.pl - 2020-06-12 02:11 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-06-12 10:13 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-06-12 07:54 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-06-12 12:04 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-06-12 10:31 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-22 11:11 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-06-12 07:49 -0700
Re: IBM 1130, system John Levine <johnl@taugh.com> - 2020-06-12 23:51 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-22 11:09 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-23 00:55 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-24 13:29 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-24 17:35 -0400
RPG was Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-24 23:03 +0000
Re: RPG was Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-25 01:19 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-24 18:37 -0700
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-25 07:26 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 07:12 -0400
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 11:29 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 07:51 -0400
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 14:34 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 11:01 -0400
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 15:15 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 11:39 -0400
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 12:15 -0400
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 15:24 -0400
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 16:50 -0400
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 15:34 -0400
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 16:53 -0400
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-25 23:14 +0000
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 17:28 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 11:13 -0700
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-26 07:01 +0000
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-26 11:31 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-26 10:11 -0700
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-26 13:26 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-26 11:28 -0700
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-26 20:23 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-26 14:35 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-26 12:08 -0700
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-26 15:13 -0400
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-26 14:28 -0700
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-26 22:33 +0100
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 15:47 -0400
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-26 11:10 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-26 08:15 -0400
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-26 14:51 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-26 16:20 +0100
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-26 12:24 -0400
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-26 16:46 +0000
Re: IBM system/360 ad Bob Eager <news0073@eager.cx> - 2020-08-26 19:52 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-26 17:00 -0400
Re: IBM system/360 ad Andreas Kohlbach <ank@spamfence.net> - 2020-08-27 14:11 -0400
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-26 20:21 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-26 22:38 +0100
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-27 06:32 +0000
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-27 11:39 +0000
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-27 13:38 +0000
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-27 12:03 +0000
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-26 20:11 +0000
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-26 21:17 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad drb@ihatespam.msu.edu (Dennis Boone) - 2020-08-26 12:13 -0500
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-26 11:27 -0700
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 17:21 +0100
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 17:37 +0000
Re: IBM system/360 ad Andy Leighton <andyl@azaal.plus.com> - 2020-08-26 04:07 -0500
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-25 12:02 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 08:29 -0400
Re: IBM system/360 ad Bob Eager <news0073@eager.cx> - 2020-08-25 12:35 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Bob Eager <news0073@eager.cx> - 2020-08-25 20:20 +0000
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-25 12:45 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 10:31 -0400
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-25 14:54 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 16:33 +0100
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 14:44 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 16:31 +0100
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 19:16 +0100
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 15:55 -0400
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-25 14:43 +0000
Re: IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-25 14:52 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 11:02 -0400
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 16:38 +0100
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 14:27 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-25 01:19 +0000
Re: IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-25 13:13 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 16:38 +0100
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-23 07:37 +0000
Re: IBM system/360 ad Gerard Schildberger <gerard46@rrt.net> - 2020-08-23 01:00 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-23 10:28 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-23 10:43 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-23 12:22 -0700
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-23 20:49 +0100
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-22 11:05 -0700
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-23 00:55 +0000
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-24 13:25 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-24 17:18 -0400
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-25 01:19 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-24 22:08 -0400
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-25 03:46 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 07:09 -0400
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-25 15:15 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 11:44 -0400
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 12:29 -0400
Re: IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-25 19:37 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 21:52 +0100
Re: IBM system/360 ad Johnatan Duck <pato@thunder.local> - 2020-08-26 07:44 +0000
Re: IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-26 12:21 +0000
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-26 15:15 +0100
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-26 17:42 -0700
Re: IBM system/360 ad Bob Eager <news0073@eager.cx> - 2020-08-27 09:43 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 16:43 -0400
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 22:27 +0100
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 14:38 -0700
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 18:09 -0400
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-26 00:12 +0000
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 20:35 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-24 18:37 -0700
Re: IBM system/360 ad Bob Eager <news0073@eager.cx> - 2020-08-25 11:18 +0000
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 07:40 -0400
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 08:26 -0400
Re: IBM system/360 ad Bob Eager <news0073@eager.cx> - 2020-08-25 12:35 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 10:26 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 16:44 -0400
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 07:56 -0400
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 09:41 -0400
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 10:43 -0400
Re: IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-25 16:28 +0100
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 11:52 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-25 15:16 +0000
Re: IBM system/360 ad "Kerr-Mudd,John" <notsaying@127.0.0.1> - 2020-08-25 12:56 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 10:40 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 10:59 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 15:58 -0400
Re: IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-25 19:57 +0000
Re: IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-25 16:48 -0400
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 14:26 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-25 19:07 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-23 06:55 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-23 10:23 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-23 14:33 -0400
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-23 23:28 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-24 13:39 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-24 18:37 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-24 22:13 -0400
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-24 20:09 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 14:11 -0700
Re: IBM system/360 Robin Vowels <robin.vowels@gmail.com> - 2020-08-25 23:18 -0700
Re: IBM system/360 hancock4@bbs.cpcn.com - 2020-08-26 14:34 -0700
Re: IBM system/360 Dan Espen <dan1espen@gmail.com> - 2020-08-26 17:49 -0400
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-26 22:28 +0000
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 06:49 -0700
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-27 17:27 +0000
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-08-27 11:49 -0700
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-27 19:39 +0000
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-08-28 12:42 -0700
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-28 20:21 +0000
Re: IBM system/360, whiz or dog? scott@slp53.sl.home (Scott Lurndal) - 2020-08-28 21:36 +0000
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-01 11:13 -0700
Re: IBM system/360, whiz or dog? Niklas Karlsson <anksil@yahoo.se> - 2020-09-01 19:17 +0000
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 18:22 -0700
Re: IBM system/360, whiz or dog? Niklas Karlsson <anksil@yahoo.se> - 2020-09-02 08:42 +0000
Re: IBM system/360, whiz or dog? Bob Martin <bob.martin@excite.com> - 2020-09-03 05:37 +0000
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-03 02:22 -0700
Re: IBM system/360, whiz or dog? Bob Eager <news0073@eager.cx> - 2020-09-03 09:48 +0000
Re: PL/something, IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-03 17:55 +0000
Re: PL/something, IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-03 19:31 +0100
Re: PL/something, IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-03 22:13 +0000
Re: PL/something, IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-03 19:24 -0700
Re: PL/something, IBM system/360, whiz or dog? Bob Martin <bob.martin@excite.com> - 2020-09-04 05:30 +0000
Re: PL/something, IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-04 16:08 -0700
Re: IBM system/360, whiz or dog? Bob Martin <bob.martin@excite.com> - 2020-09-04 05:21 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 10:00 -0400
Re: IBM system/360, whiz or dog? Bob Martin <bob.martin@excite.com> - 2020-09-05 05:51 +0000
Re: IBM system/360, whiz or dog? Bob Martin <bob.martin@excite.com> - 2020-09-05 06:34 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-05 10:08 -0400
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-08 19:13 -0700
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-08 12:16 -0700
Re: IBM system/360, whiz or dog? Dave Garland <dave.garland@wizinfo.com> - 2020-09-08 21:10 -0500
Re: IBM system/360, whiz or dog? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-09 05:07 +0000
Re: IBM system/360, whiz or dog? Bob Eager <news0073@eager.cx> - 2020-09-09 09:38 +0000
Re: IBM system/360, whiz or dog? gareth evans <headstone255@yahoo.com> - 2020-09-09 11:16 +0100
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-08 19:07 -0700
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-09-04 16:06 -0700
Re: IBM system/360, whiz or dog? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-09-02 12:18 -0600
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-01 19:20 +0000
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-01 16:06 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-01 19:12 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-02 11:59 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 09:11 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-02 14:05 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 12:18 -0400
Re: IBM system/360, whiz or dog? scott@slp53.sl.home (Scott Lurndal) - 2020-09-02 16:34 +0000
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-02 20:35 +0000
Re: IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-02 23:59 +0100
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-03 10:16 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 13:39 -0400
Re: IBM system/360, whiz or dog? lawrence <lawrenabae@abaluon.abaom> - 2020-09-03 18:31 -0500
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 19:45 -0400
Re: IBM system/360, whiz or dog? drb@ihatespam.msu.edu (Dennis Boone) - 2020-09-03 13:26 -0500
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 20:49 -0400
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-03 01:37 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 23:27 -0400
Re: IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-03 07:05 +0100
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-03 10:16 -0700
Re: IBM system/360, whiz or dog? antispam@math.uni.wroc.pl - 2020-09-03 12:29 +0000
Re: IBM system/360, whiz or dog? scott@slp53.sl.home (Scott Lurndal) - 2020-09-03 16:26 +0000
Re: IBM system/360, whiz or dog? drb@ihatespam.msu.edu (Dennis Boone) - 2020-09-03 13:11 -0500
Re: IBM system/360, whiz or dog? Richard Thiebaud <thiebauddick2@aol.com> - 2020-09-03 14:20 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-03 11:48 -0700
Re: IBM system/360, whiz or dog? Bob Eager <news0073@eager.cx> - 2020-09-03 19:57 +0000
Re: IBM system/360, whiz or dog? JimP <chucktheouch@gmail.com> - 2020-09-04 10:38 -0500
Re: IBM system/360, whiz or dog? scott@slp53.sl.home (Scott Lurndal) - 2020-09-03 19:04 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 18:00 -0400
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-03 10:55 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 14:02 -0400
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-03 22:45 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 19:11 -0400
Re: IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-02 17:45 +0100
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-02 10:10 -0400
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 12:22 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-02 09:53 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 15:19 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-02 20:52 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 21:04 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-03 07:19 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 09:15 -0400
Re: IBM system/360, whiz or dog? Quadibloc <jsavard@ecn.ab.ca> - 2020-09-03 13:28 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 18:04 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-04 05:48 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 10:07 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-04 14:56 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 11:07 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-04 19:49 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 16:12 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-04 20:34 +0000
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-04 16:53 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-04 21:23 +0000
Re: IBM system/360, whiz or dog? Niklas Karlsson <anksil@yahoo.se> - 2020-09-05 12:22 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 18:41 -0400
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-04 21:00 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-04 18:09 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 21:41 -0400
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-04 22:10 -0400
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-08 12:04 -0700
Re: IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-08 23:35 +0100
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-09 13:17 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 21:34 -0400
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-04 22:37 -0400
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 23:56 -0400
Re: fun with APL, was IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-05 19:02 +0000
Re: fun with APL, was IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-05 16:23 -0400
Re: fun with APL, was IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-05 16:37 -0400
Re: fun with APL, was IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-05 16:57 -0400
Re: fun with APL, was IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-05 17:09 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-05 17:38 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-05 22:05 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-06 06:30 -0700
Re: IBM system/360, whiz or dog? JimP <chucktheouch@gmail.com> - 2020-09-04 21:32 -0500
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-04 23:08 -0400
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-05 00:05 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-05 09:48 +0000
Re: IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-05 07:20 +0100
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-08 12:09 -0700
Re: IBM system/360, whiz or dog? gareth evans <headstone255@yahoo.com> - 2020-09-08 21:00 +0100
Re: IBM system/360, whiz or dog? JimP <chucktheouch@gmail.com> - 2020-09-09 14:45 -0500
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-08 11:53 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-08 18:37 -0400
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-09-08 11:59 -0700
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-08 15:22 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-04 16:02 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 19:43 -0400
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-04 18:13 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-05 09:47 +0000
Re: IBM system/360, whiz or dog? gareth evans <headstone255@yahoo.com> - 2020-09-05 12:21 +0100
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-03 21:45 +0000
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 19:01 -0400
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-02 13:16 -0400
Re: IBM system/360, whiz or dog? Stefan Möding <Sep2020.5.kill-9@spamgourmet.com> - 2020-09-02 16:14 +0200
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-02 07:20 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 12:36 -0400
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-09-02 13:19 -0400
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 15:25 -0400
Re: IBM system/360, whiz or dog? Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-02 14:43 +0100
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-09-02 06:35 -0700
Re: IBM system/360, whiz or dog? J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 12:40 -0400
Re: Fortran on IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-02 02:08 +0000
Re: Fortran on IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-02 06:12 +0000
Re: Fortran on IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-02 20:36 +0000
Re: Fortran on IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-02 20:54 +0000
Re: Fortran on IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-09-02 22:18 +0000
Re: Fortran on IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-09-03 06:27 +0000
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-27 16:48 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-08-27 16:40 -0700
Re: IBM system/360, whiz or dog? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-27 23:53 +0000
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-27 20:33 -0400
Re: IBM system/360, whiz or dog? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-28 02:46 +0000
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-27 23:08 -0400
Re: IBM system/360, whiz or dog? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-28 19:30 +0000
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-28 16:00 -0400
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-28 20:27 +0000
Re: IBM system/360, whiz or dog? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-28 21:01 +0000
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-08-28 15:15 -0700
Re: IBM system/360, whiz or dog? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-28 22:51 +0000
Re: IBM system/360/20, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-29 01:24 +0000
Re: IBM system/360, whiz or dog? Robin Vowels <robin.vowels@gmail.com> - 2020-08-28 20:28 -0700
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-29 18:19 +0000
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-08-29 19:52 -0700
Re: IBM system/360, model 20 PL/I John Levine <johnl@taugh.com> - 2020-08-30 17:47 +0000
Re: IBM system/360, model 20 PL/I Dan Espen <dan1espen@gmail.com> - 2020-08-30 14:16 -0400
Re: IBM system/360, model 20 PL/I Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-01 03:32 +0000
Re: IBM system/360, model 20 PL/I Quadibloc <jsavard@ecn.ab.ca> - 2020-08-30 15:11 -0700
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-08-30 19:41 -0700
Re: IBM system/360, model 20 PL/I Quadibloc <jsavard@ecn.ab.ca> - 2020-08-31 08:58 -0700
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-08-30 17:27 -0700
Re: IBM system/360, model 20 PL/I John Levine <johnl@taugh.com> - 2020-08-31 01:06 +0000
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-08-30 20:26 -0700
Re: IBM system/360, model 20 PL/I Peter Flass <peter_flass@yahoo.com> - 2020-08-30 20:34 -0700
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-08-31 21:21 -0700
Re: IBM system/360, model 20 PL/I John Levine <johnl@taugh.com> - 2020-08-31 16:34 +0000
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-08-31 22:13 -0700
Re: IBM system/360, model 20 PL/I Peter Flass <peter_flass@yahoo.com> - 2020-09-01 06:34 -0700
Re: IBM system/360, model 20 PL/I Quadibloc <jsavard@ecn.ab.ca> - 2020-09-01 16:52 -0700
Re: IBM system/360, model 20 PL/I hancock4@bbs.cpcn.com - 2020-09-01 11:07 -0700
Re: IBM system/360, model 20 PL/I Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-01 19:38 +0000
Re: IBM system/360, model 20 PL/I Dan Espen <dan1espen@gmail.com> - 2020-09-01 16:08 -0400
Re: IBM system/360, model 20 PL/I Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 18:41 -0700
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-08-29 11:22 -0700
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-08-28 12:49 -0700
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-28 16:23 -0400
Re: IBM system/360, whiz or dog? Thomas Koenig <tkoenig@netcologne.de> - 2020-08-29 12:21 +0000
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-29 09:41 -0400
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-08-29 11:24 -0700
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-29 15:07 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-08-29 17:52 -0700
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-29 22:21 -0400
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-08-28 07:20 -0700
Re: IBM system/360, whiz or dog? Peter Flass <peter_flass@yahoo.com> - 2020-08-27 16:40 -0700
Re: IBM system/360, whiz or dog? John Levine <johnl@taugh.com> - 2020-08-28 00:56 +0000
Re: IBM system/360, whiz or dog? hancock4@bbs.cpcn.com - 2020-08-28 12:46 -0700
Re: IBM system/360, whiz or dog? Dan Espen <dan1espen@gmail.com> - 2020-08-28 16:15 -0400
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-26 17:59 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-26 21:47 -0400
Re: KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-27 02:40 +0000
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-27 00:04 -0400
Re: KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 06:24 -0700
Re: KDF9, not IBM system/360 ad Bill Findlay <findlaybill@blueyonder.co.uk> - 2020-08-27 15:55 +0100
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-27 11:14 -0400
Re: KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-27 17:30 +0000
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-27 23:24 -0700
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-28 06:38 -0400
Re: KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-28 06:44 -0700
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-28 10:59 -0400
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 10:15 -0700
Re: KDF9 Robin Vowels <robin.vowels@gmail.com> - 2020-08-28 19:05 -0700
Re: KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-28 19:37 +0000
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-28 16:05 -0400
Re: stacks KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-28 20:30 +0000
Re: stacks KDF9, not IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-28 21:40 +0000
Re: stacks KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 15:15 -0700
Re: stacks KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 15:15 -0700
Re: stacks KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-28 20:03 -0400
Re: stacks KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 18:09 -0700
Re: KDF9, not IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-29 14:01 +0000
Re: Fortran, not KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-29 18:33 +0000
Re: Fortran, not KDF9, not IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-30 11:09 +0000
Re: Fortran, not KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-30 07:18 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-30 17:58 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-31 17:17 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-31 19:58 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-09-01 09:39 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 04:10 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-01 08:19 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-01 18:08 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-01 16:04 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 18:13 -0700
Re: block moves, 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-02 02:14 +0000
Re: block moves, 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 20:52 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-09-02 06:35 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 20:34 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-02 00:06 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 18:05 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-01 22:32 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-02 02:51 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-01 23:52 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-01 20:58 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-09-02 06:35 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-02 10:18 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-02 16:54 +0000
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-09-02 13:28 -0400
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-31 15:50 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-31 17:24 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-31 22:19 -0700
Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-31 22:23 -0700
Re: KDF9, not IBM system/360 ad Robert Marshall <spam@capuchin.co.uk> - 2020-08-28 18:58 +0100
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-28 15:23 -0700
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 18:09 -0700
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-29 11:21 -0700
Re: KDF9, not IBM system/360 ad usenet@only.tnx (Questor) - 2020-09-02 07:05 +0000
Re: KDF9 Robin Vowels <robin.vowels@gmail.com> - 2020-08-28 19:39 -0700
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-29 11:18 -0700
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-29 17:52 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-29 21:39 -0400
Re: KDF9, not IBM system/360 ad antispam@math.uni.wroc.pl - 2020-08-30 11:51 +0000
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-30 08:06 -0400
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-30 08:36 -0400
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-30 10:43 -0400
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-30 11:49 -0400
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-30 13:10 -0400
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-30 13:33 -0400
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-30 15:03 -0400
Re: KDF9, not IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-30 16:37 +0000
Re: Home made card reader Niklas Karlsson <anksil@yahoo.se> - 2020-08-30 16:55 +0000
Re: Home made card reader J. Clarke <jclarke.873638@gmail.com> - 2020-08-30 13:20 -0400
Re: Home made card reader Niklas Karlsson <anksil@yahoo.se> - 2020-08-30 17:23 +0000
Re: Home made card reader Robin Vowels <robin.vowels@gmail.com> - 2020-08-30 16:38 -0700
Re: Home made card reader John Levine <johnl@taugh.com> - 2020-08-31 00:27 +0000
Re: Home made card reader Niklas Karlsson <anksil@yahoo.se> - 2020-08-31 09:34 +0000
Re: Home made card reader usenet@only.tnx (Questor) - 2020-09-02 07:04 +0000
Re: Home made card reader Bob Eager <news0073@eager.cx> - 2020-09-02 08:27 +0000
Re: Home made card reader Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-02 16:54 +0000
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-30 15:04 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-30 18:19 -0400
Re: KDF9, not IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-31 07:23 +0100
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-29 20:34 -0700
Re: KDF9, not IBM system/360 ad gareth evans <headstone255@yahoo.com> - 2020-08-30 11:37 +0100
Re: KDF9, not IBM system/360 ad gareth evans <headstone255@yahoo.com> - 2020-08-30 11:40 +0100
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-30 07:31 -0700
Re: KDF9, not IBM system/360 ad usenet@only.tnx (Questor) - 2020-09-02 07:06 +0000
Re: KDF9, not IBM system/360 ad usenet@only.tnx (Questor) - 2020-09-02 07:03 +0000
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-09-02 06:35 -0700
Re: PDP-10, was KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-02 20:40 +0000
Re: PDP-10, was KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 21:06 -0400
Re: PDP-10, was KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-03 01:41 +0000
Re: PDP-10, was KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-09-02 23:28 -0400
Re: PDP-10, was KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-03 18:10 +0000
Re: PDP-10, was KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 17:25 -0400
Re: PDP-10, was KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-09-03 22:26 +0000
Re: PDP-10, was KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-09-03 19:03 -0400
Re: PDP-10, was KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-09-04 16:03 -0700
Re: PDP-10, was KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-09-04 23:34 -0700
Re: PDP-10, was KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-09-05 10:02 -0400
Re: PDP-10, was KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-09-05 17:38 -0700
Re: PDP-10, was KDF9, not IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-09-03 16:32 +0000
Re: PDP-10, was KDF9, not IBM system/360 ad usenet@only.tnx (Questor) - 2020-09-04 18:11 +0000
Re: KDF9, not IBM system/360 ad Bill Findlay <findlaybill@blueyonder.co.uk> - 2020-08-29 01:04 +0100
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-28 20:14 -0400
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-29 08:35 -0700
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-29 12:13 -0400
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-27 16:40 -0700
Re: KDF9, not IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-28 07:00 +0100
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-28 15:17 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-28 18:24 -0400
Re: KDF9, not IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-28 20:04 -0400
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 18:09 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-28 22:07 -0400
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-29 11:20 -0700
Re: KDF9, not IBM system/360 ad Thomas Koenig <tkoenig@netcologne.de> - 2020-08-29 12:28 +0000
Re: KDF9, not IBM system/360 ad Niklas Karlsson <anksil@yahoo.se> - 2020-08-29 12:31 +0000
Re: KDF9, not IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-29 23:58 +0000
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-09-01 11:10 -0700
Re: KDF9, not IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-09-02 05:21 +0100
Re: KDF9, not IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-09-02 16:54 +0000
Re: flaming, not at all KDF9, not IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-29 18:35 +0000
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-29 11:15 -0700
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-28 12:45 -0700
Re: KDF9, not IBM system/360 ad scott@slp53.sl.home (Scott Lurndal) - 2020-08-28 20:28 +0000
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-29 11:11 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-29 14:28 -0400
Re: KDF9, not IBM system/360 ad Ahem A Rivet's Shot <steveo@eircom.net> - 2020-08-29 19:39 +0100
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-28 16:59 -0400
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 15:15 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-28 18:25 -0400
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-28 18:09 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-28 22:28 -0400
Re: KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 10:28 -0700
Re: KDF9, not IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-08-29 08:40 -0700
Re: KDF9, not IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-27 06:32 +0000
Re: KDF9, not IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-27 07:50 -0700
Re: KDF9, not IBM system/360 ad J. Clarke <jclarke.873638@gmail.com> - 2020-08-27 18:56 -0400
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-27 11:39 -0700
Re: KDF9, not IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 06:34 -0700
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-27 11:44 -0700
Re: KDF9, not IBM system/360 ad Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2020-08-27 19:08 +0000
Re: KDF9, not IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-27 11:36 -0700
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 06:11 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-27 09:25 -0400
Re: IBM system/360 Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 10:32 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-27 07:50 -0700
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 10:36 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-27 16:40 -0700
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-28 05:10 -0700
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-27 06:20 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-08-27 09:31 -0400
Re: IBM system/360 ad John Levine <johnl@taugh.com> - 2020-08-27 17:42 +0000
Re: IBM system/360 ad Stoat <fake@fake.org> - 2020-08-28 15:49 +1200
Re: IBM system/360 ad gareth evans <headstone255@yahoo.com> - 2020-08-27 16:06 +0100
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 14:03 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-10 11:27 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-10 14:47 -0400
Re: IBM system/360 ad Rich Alderson <news@alderson.users.panix.com> - 2020-03-11 15:05 -0400
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-11 16:33 -0400
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-12 14:57 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-12 19:59 -0400
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-12 17:27 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-03-12 20:57 -0400
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-13 10:15 -0700
Re: IBM system/360 ad robin.vowels@gmail.com - 2020-03-10 18:06 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-03-11 12:32 -0700
Re: IBM system/360 ad antispam@math.uni.wroc.pl - 2020-06-12 02:52 +0000
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-06-12 10:27 -0400
Re: IBM system/360 ad antispam@math.uni.wroc.pl - 2020-06-14 13:40 +0000
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-06-14 09:01 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-06-14 12:36 -0400
Re: IBM system/360 ad antispam@math.uni.wroc.pl - 2020-06-15 21:58 +0000
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-06-12 07:49 -0700
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-06-12 12:57 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-06-12 17:39 -0400
Re: IBM system/360 ad Quadibloc <jsavard@ecn.ab.ca> - 2020-06-12 15:29 -0700
Re: IBM system/360 ad Dan Espen <dan1espen@gmail.com> - 2020-06-12 20:33 -0400
Re: IBM system/360 ad Jon Elson <elson@pico-systems.com> - 2020-03-11 21:23 -0500
Re: IBM system/360 ad robin.vowels@gmail.com - 2020-03-11 20:50 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-12 09:34 -0700
Re: IBM system/360 ad hancock4@bbs.cpcn.com - 2020-08-25 13:55 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-08-25 18:06 -0700
Re: IBM system/360 ad Robin Vowels <robin.vowels@gmail.com> - 2020-08-25 23:05 -0700
Re: IBM system/360 ad Peter Flass <peter_flass@yahoo.com> - 2020-03-08 17:19 -0700
Page 22 of 30 — ← Prev page 1 … 20 21 [22] 23 24 … 30 Next page →
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-08-28 20:30 +0000 |
| Subject | Re: stacks KDF9, not IBM system/360 ad |
| Message-ID | <ribphn$2t4b$4@gal.iecc.com> |
| In reply to | #213350 |
In article <ribo2h$bk2$3@dont-email.me>, Dan Espen <dan1espen@gmail.com> wrote: >> I'm surprised you never ran into stack machines. The Burroughs B5000 >> and its successors in the 1960s and 1970s used a stack as did the >> later HP3000. > >Doubtless some of the many UNIX systems I worked with were stack >oriented. ... I doubt it, the PDP-11 was a register machine as was every other machine ever saw Unix run on. Once they had enough transistors to put multiple registers in small machines, and we understood how to do compiler register allocation (the early Unix compilers used Sethi-Ullman numbering which wasn't very clever but was good enough), stacks lost their appeal. >Actually now I think about it, later z/os systems had a call stack >which I used a bit. That's not the same thing as being a stack machine. The call stack was all in memory and was a kludge to deal with the various addressing modes on the 370 and its successors. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2020-08-28 21:40 +0000 |
| Subject | Re: stacks KDF9, not IBM system/360 ad |
| Message-ID | <sRe2H.84411$lZ.50566@fx12.iad> |
| In reply to | #213356 |
John Levine <johnl@taugh.com> writes: >In article <ribo2h$bk2$3@dont-email.me>, >Dan Espen <dan1espen@gmail.com> wrote: >>> I'm surprised you never ran into stack machines. The Burroughs B5000 >>> and its successors in the 1960s and 1970s used a stack as did the >>> later HP3000. >> >>Doubtless some of the many UNIX systems I worked with were stack >>oriented. ... > >I doubt it, the PDP-11 was a register machine as was every other >machine ever saw Unix run on. Once they had enough transistors to put >multiple registers in small machines, and we understood how to do >compiler register allocation (the early Unix compilers used >Sethi-Ullman numbering which wasn't very clever but was good enough), >stacks lost their appeal. The B5500/B6500/etc (still alive as Unisys Clearpath, albeit emulated) and the HP-3000 are the two main stack architectures that I worked with. (The HP-3000 had a few ex-burroughs engineers on the design team as I understand it). Generally no programmer visible registers, all operations were memory to memory. So for an add, you'd push both operands on the stack first then issue the add instruction (which would replace the top two words with the result). Think RPN calculators.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-08-28 15:15 -0700 |
| Subject | Re: stacks KDF9, not IBM system/360 ad |
| Message-ID | <1551159091.620345632.764330.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #213362 |
Scott Lurndal <scott@slp53.sl.home> wrote: > John Levine <johnl@taugh.com> writes: >> In article <ribo2h$bk2$3@dont-email.me>, >> Dan Espen <dan1espen@gmail.com> wrote: >>>> I'm surprised you never ran into stack machines. The Burroughs B5000 >>>> and its successors in the 1960s and 1970s used a stack as did the >>>> later HP3000. >>> >>> Doubtless some of the many UNIX systems I worked with were stack >>> oriented. ... >> >> I doubt it, the PDP-11 was a register machine as was every other >> machine ever saw Unix run on. Once they had enough transistors to put >> multiple registers in small machines, and we understood how to do >> compiler register allocation (the early Unix compilers used >> Sethi-Ullman numbering which wasn't very clever but was good enough), >> stacks lost their appeal. > > The B5500/B6500/etc (still alive as Unisys Clearpath, albeit emulated) > and the HP-3000 are the two main stack architectures that I worked > with. > > (The HP-3000 had a few ex-burroughs engineers on the design team as > I understand it). > > Generally no programmer visible registers, all operations were memory > to memory. > > So for an add, you'd push both operands on the stack first then > issue the add instruction (which would replace the top two words > with the result). > > Think RPN calculators. > > Not really much different than loading the two values into registers and adding them, especially if the stack top was kept in registers. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-08-28 15:15 -0700 |
| Subject | Re: stacks KDF9, not IBM system/360 ad |
| Message-ID | <1188739418.620345381.729429.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #213356 |
John Levine <johnl@taugh.com> wrote: > In article <ribo2h$bk2$3@dont-email.me>, > Dan Espen <dan1espen@gmail.com> wrote: >>> I'm surprised you never ran into stack machines. The Burroughs B5000 >>> and its successors in the 1960s and 1970s used a stack as did the >>> later HP3000. >> >> Doubtless some of the many UNIX systems I worked with were stack >> oriented. ... > > I doubt it, the PDP-11 was a register machine as was every other > machine ever saw Unix run on. Once they had enough transistors to put > multiple registers in small machines, and we understood how to do > compiler register allocation (the early Unix compilers used > Sethi-Ullman numbering which wasn't very clever but was good enough), > stacks lost their appeal. > >> Actually now I think about it, later z/os systems had a call stack >> which I used a bit. > > That's not the same thing as being a stack machine. The call stack was > all in memory and was a kludge to deal with the various addressing > modes on the 370 and its successors. > I think the call stack was introduced to allow calls between address spaces. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-08-28 20:03 -0400 |
| Subject | Re: stacks KDF9, not IBM system/360 ad |
| Message-ID | <ric60h$9tu$1@dont-email.me> |
| In reply to | #213365 |
Peter Flass <peter_flass@yahoo.com> writes: > John Levine <johnl@taugh.com> wrote: >> In article <ribo2h$bk2$3@dont-email.me>, >> Dan Espen <dan1espen@gmail.com> wrote: >>>> I'm surprised you never ran into stack machines. The Burroughs B5000 >>>> and its successors in the 1960s and 1970s used a stack as did the >>>> later HP3000. >>> >>> Doubtless some of the many UNIX systems I worked with were stack >>> oriented. ... >> >> I doubt it, the PDP-11 was a register machine as was every other >> machine ever saw Unix run on. Once they had enough transistors to put >> multiple registers in small machines, and we understood how to do >> compiler register allocation (the early Unix compilers used >> Sethi-Ullman numbering which wasn't very clever but was good enough), >> stacks lost their appeal. >> >>> Actually now I think about it, later z/os systems had a call stack >>> which I used a bit. >> >> That's not the same thing as being a stack machine. The call stack was >> all in memory and was a kludge to deal with the various addressing >> modes on the 370 and its successors. >> > > I think the call stack was introduced to allow calls between address > spaces. Yes, as I remember it can do that too. But it works for things that don't cross address spaces. It's what's used for the LE option XPLINK. We looked at that option but never bit. But like I said, I was able to use it in HLASM pretty transparently. Okay, now I remember for a good story. We'd always had callable services for hex dumping storage areas and registers for tracing. The problem with all of them is that they required initialization (like an open0 and they would change at least some of the registers you might want to trace. I was trying to debug our debugger and I needed to be able to see everything that was going on including all the registers. I couldn't always find an easy place to insert the open either. So I wanted a macro I could just insert anywhere in an HLASM program that wouldn't disturb anything including linkage registers and the save areas. The stack feature got me part of the way there because it created a new save area that didn't hook up to anything else all on it's own. I needed a DCB to open, but you can search the DCB chain so that was easy. Before the thing would print it would just look at the allocation and allocate it if it wasn't already allocated. So, I was left with trying to pass args without messing with any registers. So, I looked around and one day I realized that the access registers were available and AR 0 was useless. You couldn't tell the hardware that you wanted to use AR 0 because zero was considered no access register. So I decided I could safely use AR 0 without anything messing with what was in there. So I ended up using AR 0 to preserve the one register I had to use without worrying that anything else would be using it. Eventually I was able to make the same routine callable from PL/I and C. Of course there I didn't need to worry about disturbing registers. So, I was already supporting a debugger but if I needed something that worked outside the debugger I had it. It proved quite useful. I could stick it anywhere including in IMS code. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2020-08-28 18:09 -0700 |
| Subject | Re: stacks KDF9, not IBM system/360 ad |
| Message-ID | <1252260051.620356069.325861.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #213377 |
Dan Espen <dan1espen@gmail.com> wrote: > Peter Flass <peter_flass@yahoo.com> writes: > >> John Levine <johnl@taugh.com> wrote: >>> In article <ribo2h$bk2$3@dont-email.me>, >>> Dan Espen <dan1espen@gmail.com> wrote: >>>>> I'm surprised you never ran into stack machines. The Burroughs B5000 >>>>> and its successors in the 1960s and 1970s used a stack as did the >>>>> later HP3000. >>>> >>>> Doubtless some of the many UNIX systems I worked with were stack >>>> oriented. ... >>> >>> I doubt it, the PDP-11 was a register machine as was every other >>> machine ever saw Unix run on. Once they had enough transistors to put >>> multiple registers in small machines, and we understood how to do >>> compiler register allocation (the early Unix compilers used >>> Sethi-Ullman numbering which wasn't very clever but was good enough), >>> stacks lost their appeal. >>> >>>> Actually now I think about it, later z/os systems had a call stack >>>> which I used a bit. >>> >>> That's not the same thing as being a stack machine. The call stack was >>> all in memory and was a kludge to deal with the various addressing >>> modes on the 370 and its successors. >>> >> >> I think the call stack was introduced to allow calls between address >> spaces. > > Yes, as I remember it can do that too. > But it works for things that don't cross address spaces. > It's what's used for the LE option XPLINK. > > We looked at that option but never bit. But like I said, I was > able to use it in HLASM pretty transparently. > > Okay, now I remember for a good story. > > We'd always had callable services for hex dumping storage areas and > registers for tracing. > The problem with all of them is that they required initialization (like > an open0 and they would change at least some of the registers you might want to > trace. > > I was trying to debug our debugger and I needed to be able to see > everything that was going on including all the registers. I couldn't > always find an easy place to insert the open either. So I wanted > a macro I could just insert anywhere in an HLASM program that wouldn't > disturb anything including linkage registers and the save areas. > > The stack feature got me part of the way there because it created a new > save area that didn't hook up to anything else all on it's own. > I needed a DCB to open, but you can search the DCB chain so that was > easy. Before the thing would print it would just look at the allocation > and allocate it if it wasn't already allocated. > So, I was left with trying to pass args without messing with any > registers. So, I looked around and one day I realized that the access > registers were available and AR 0 was useless. You couldn't tell the > hardware that you wanted to use AR 0 because zero was considered no > access register. So I decided I could safely use AR 0 without anything > messing with what was in there. > > So I ended up using AR 0 to preserve the one register I had to use > without worrying that anything else would be using it. > Eventually I was able to make the same routine callable from PL/I and C. > Of course there I didn't need to worry about disturbing registers. > > So, I was already supporting a debugger but if I needed something that > worked outside the debugger I had it. It proved quite useful. I could > stick it anywhere including in IMS code. > > SPIE and execute a halfword of zeroes. All your registers are saved for you. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | Thomas Koenig <tkoenig@netcologne.de> |
|---|---|
| Date | 2020-08-29 14:01 +0000 |
| Subject | Re: KDF9, not IBM system/360 ad |
| Message-ID | <ridn4n$fvc$1@newsreader4.netcologne.de> |
| In reply to | #213343 |
John Levine <johnl@taugh.com> schrieb: > (Register assignments by compilers wasn't well undestood until the > late 1970s.) Even so, the first-ever Fortran compiler did a very good job of it. Apparently, it took graph-coloring algorithms for register allocation to make it better (I presume that this is what you mean). What the first Fortran comiler did to parse algebraic formulas, however, was just weird. Recursive descent hadn't yet been invented yet, and it shows.
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-08-29 18:33 +0000 |
| Subject | Re: Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rie717$8uo$1@gal.iecc.com> |
| In reply to | #213408 |
In article <ridn4n$fvc$1@newsreader4.netcologne.de>, Thomas Koenig <tkoenig@netcologne.de> wrote: >John Levine <johnl@taugh.com> schrieb: > >> (Register assignments by compilers wasn't well undestood until the >> late 1970s.) > >Even so, the first-ever Fortran compiler did a very good job of it. >Apparently, it took graph-coloring algorithms for register >allocation to make it better (I presume that this is what you mean). Not really. The 704 had one accumulator and three half-length index registers so there wasn't a lot of register allocation to be done. Fortran H for S/360 generated excellent code for the 1960s but its register allocation was ad-hoc, trying to keep addresses and intermediate values in registers during a routine so they wouldn't have to be reloaded or recomputed. Graph coloring provided an overall framework to map values of any type into registers which was more powerful than the previous ad-hoc methods. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | Thomas Koenig <tkoenig@netcologne.de> |
|---|---|
| Date | 2020-08-30 11:09 +0000 |
| Subject | Re: Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rig1cu$7cm$1@newsreader4.netcologne.de> |
| In reply to | #213423 |
John Levine <johnl@taugh.com> schrieb: > In article <ridn4n$fvc$1@newsreader4.netcologne.de>, > Thomas Koenig <tkoenig@netcologne.de> wrote: >>John Levine <johnl@taugh.com> schrieb: >> >>> (Register assignments by compilers wasn't well undestood until the >>> late 1970s.) >> >>Even so, the first-ever Fortran compiler did a very good job of it. >>Apparently, it took graph-coloring algorithms for register >>allocation to make it better (I presume that this is what you mean). > > Not really. The 704 had one accumulator and three half-length index > registers so there wasn't a lot of register allocation to be done. Plus one quotient / remainder register. However, the register allocation for the index registers was key for the good performance of the compiler, especially with array accesses and DO loops, and this was why the generated code often matched hand-optimized assembly (or, as often as not, machine code). Spilling a register and loading it back takes time, that has not changed. Of course, once the 7094 arrived, they had more index registers to play with, because they removed that weird "or" mode. (Not sure if the compiler ever used that). > Fortran H for S/360 generated excellent code for the 1960s but its > register allocation was ad-hoc, trying to keep addresses and > intermediate values in registers during a routine so they wouldn't > have to be reloaded or recomputed. This is one thing where they probably fell back behind what was done for the Fortran I and II compilers. > Graph coloring provided an overall framework to map values of any type > into registers which was more powerful than the previous ad-hoc > methods. Sure.
[toc] | [prev] | [next] | [standalone]
| From | Quadibloc <jsavard@ecn.ab.ca> |
|---|---|
| Date | 2020-08-30 07:18 -0700 |
| Subject | Re: Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <36ca64c0-91b8-4120-9976-6bd580ce7d41o@googlegroups.com> |
| In reply to | #213447 |
On Sunday, August 30, 2020 at 5:09:19 AM UTC-6, Thomas Koenig wrote: > Of course, once the 7094 arrived, they had more index registers to play > with, because they removed that weird "or" mode. (Not sure if the > compiler ever used that). That's not _strictly_ accurate. The 7094 allowed the programmer to turn off that "weird OR mode", but it wasn't removed from the machine, which was perfectly capable of running in compatibility mode. John Savard
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-08-30 17:58 +0000 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rigpc6$gi7$2@gal.iecc.com> |
| In reply to | #213452 |
In article <36ca64c0-91b8-4120-9976-6bd580ce7d41o@googlegroups.com>, Quadibloc <jsavard@ecn.ab.ca> wrote: >On Sunday, August 30, 2020 at 5:09:19 AM UTC-6, Thomas Koenig wrote: > >> Of course, once the 7094 arrived, they had more index registers to play >> with, because they removed that weird "or" mode. (Not sure if the >> compiler ever used that). > >That's not _strictly_ accurate. The 7094 allowed the programmer to turn off that >"weird OR mode", but it wasn't removed from the machine, which was perfectly >capable of running in compatibility mode. I have asked a few times whether anyone actually used weird OR mode, or whether it was just an artifact of the wiring of the 704 that IBM, being IBM, documented just in case. Nobody ever said that they did. Given that the 704 was sign-magnitude but indexing did two's complement subtraction, it would have needed some seriously funky programming to do anything useful with it. I suppose someone must have sometime if it was worth keeping it as the default in the 7094. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | Thomas Koenig <tkoenig@netcologne.de> |
|---|---|
| Date | 2020-08-31 17:17 +0000 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rijbaq$nb6$1@newsreader4.netcologne.de> |
| In reply to | #213464 |
John Levine <johnl@taugh.com> schrieb:
> In article <36ca64c0-91b8-4120-9976-6bd580ce7d41o@googlegroups.com>,
> Quadibloc <jsavard@ecn.ab.ca> wrote:
>>On Sunday, August 30, 2020 at 5:09:19 AM UTC-6, Thomas Koenig wrote:
>>
>>> Of course, once the 7094 arrived, they had more index registers to play
>>> with, because they removed that weird "or" mode. (Not sure if the
>>> compiler ever used that).
>>
>>That's not _strictly_ accurate. The 7094 allowed the programmer to turn off that
>>"weird OR mode", but it wasn't removed from the machine, which was perfectly
>>capable of running in compatibility mode.
>
> I have asked a few times whether anyone actually used weird OR mode,
> or whether it was just an artifact of the wiring of the 704 that IBM,
> being IBM, documented just in case. Nobody ever said that they did.
I certainly didn't, the 704 is older than me :-)
There could be a use, though, but it would be narrow. Assuming you
had a Fortran program fragment like
DIMENSION A(4,11)
DO 10 J=1,9
DO 10 I=1,4
10 A(I,J) = 2.0
you could have one index register for I running from 0 to 3 and
another index register for J running from 0 to 32 in increments
of four, and then just or them together.
That sounds like something that a clever assembler (or machine
code) programmer would try, and probably spend hours debugging.
I have no clue if the Fortran compiler did anything like that.
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-08-31 19:58 +0000 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rijkp6$1roo$1@gal.iecc.com> |
| In reply to | #213493 |
In article <rijbaq$nb6$1@newsreader4.netcologne.de>, Thomas Koenig <tkoenig@netcologne.de> wrote: >There could be a use, though, but it would be narrow. Assuming you >had a Fortran program fragment like > > DIMENSION A(4,11) > DO 10 J=1,9 > DO 10 I=1,4 > 10 A(I,J) = 2.0 > >you could have one index register for I running from 0 to 3 and >another index register for J running from 0 to 32 in increments >of four, and then just or them together. That's the only thing I've been able to think of, and only in the special case that the first subscript is a power of two. Seems pretty obscure to be worth implementing in a compiler. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | Thomas Koenig <tkoenig@netcologne.de> |
|---|---|
| Date | 2020-09-01 09:39 +0000 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <ril4rl$k1$1@newsreader4.netcologne.de> |
| In reply to | #213497 |
John Levine <johnl@taugh.com> schrieb: > In article <rijbaq$nb6$1@newsreader4.netcologne.de>, > Thomas Koenig <tkoenig@netcologne.de> wrote: >>There could be a use, though, but it would be narrow. Assuming you >>had a Fortran program fragment like >> >> DIMENSION A(4,11) >> DO 10 J=1,9 >> DO 10 I=1,4 >> 10 A(I,J) = 2.0 >> >>you could have one index register for I running from 0 to 3 and >>another index register for J running from 0 to 32 in increments >>of four, and then just or them together. > > That's the only thing I've been able to think of, and only in the > special case that the first subscript is a power of two. Maybe this was something C.A.R. Hoare alluded to, in his "Hints on Programming Language Design": # In the early days of hardware design, some very ingenious but # arbitrary features turned up in order codes as a result of # orthogonal combinations of the function bits of an instruction, # on the grounds that some clever programmer would find a use for # them, -- and some clever programmer always did. Of course, he then goes on to write # Hardware designers have now learned more sense :-) > Seems pretty obscure to be worth implementing in a compiler. I don't think we will find out without somebody actually trying. Does anybody have an up-and-running IBM 704 emulator with the Fortran compiler and could compile a test program and examine the output? I don't, unfortunately.
[toc] | [prev] | [next] | [standalone]
| From | Robin Vowels <robin.vowels@gmail.com> |
|---|---|
| Date | 2020-09-01 04:10 -0700 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <48e694fc-d203-4f6f-a944-b40eaf76afbfn@googlegroups.com> |
| In reply to | #213493 |
On Tuesday, September 1, 2020 at 3:17:16 AM UTC+10, Thomas Koenig wrote: > There could be a use, though, but it would be narrow. Assuming you > had a Fortran program fragment like > > DIMENSION A(4,11) > DO 10 J=1,9 > DO 10 I=1,4 > 10 A(I,J) = 2.0 > > you could have one index register for I running from 0 to 3 and > another index register for J running from 0 to 32 in increments > of four, and then just or them together. That's an interesting optimisation. In PL/I, one might write A = 2.0; and that would be optimised to MVC A,B(4) MVC A+4,A(44*4-4) where B is the constant 2.0. > That sounds like something that a clever assembler (or machine > code) programmer would try, and probably spend hours debugging. > > I have no clue if the Fortran compiler did anything like that.
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-09-01 08:19 -0400 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rile83$dlm$1@dont-email.me> |
| In reply to | #213520 |
Robin Vowels <robin.vowels@gmail.com> writes: > On Tuesday, September 1, 2020 at 3:17:16 AM UTC+10, Thomas Koenig wrote: > >> There could be a use, though, but it would be narrow. Assuming you >> had a Fortran program fragment like >> >> DIMENSION A(4,11) >> DO 10 J=1,9 >> DO 10 I=1,4 >> 10 A(I,J) = 2.0 >> >> you could have one index register for I running from 0 to 3 and >> another index register for J running from 0 to 32 in increments >> of four, and then just or them together. > > That's an interesting optimisation. > > In PL/I, one might write > A = 2.0; > and that would be optimised to > MVC A,B(4) > MVC A+4,A(44*4-4) > > where B is the constant 2.0. Those length specifications belong on the first operand. Those move character instructions with data overlap are all specified by POP to be treated as if one byte at a time is being moved: For MOVE (MVC), each operand is processed left to right. When the operands overlap, the result is obtained as if the operands were processed one byte at a time and each result byte were stored immedi- ately after fetching the necessary operand byte. I don't know if the hardware has an optimization to recognize the overlap offset is 4 bytes and it can fetch/store 4 bytes at a time. The hardware would need another optimization to realize it can parallelize the whole operation and not wait to see what's in the next 4 bytes. Anyway, that's a common way to clear a print area, except it's done: MVI PRINT,X'40' MVC PRINT+1(131),PRINT I was always suspicious that this would cause a performance hit so I preferred to define an area of 132 spaces and move that to areas that needed clearing. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-09-01 18:08 +0000 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rim2n3$urv$1@gal.iecc.com> |
| In reply to | #213523 |
In article <rile83$dlm$1@dont-email.me>, Dan Espen <dan1espen@gmail.com> wrote: >Robin Vowels <robin.vowels@gmail.com> writes: > >> On Tuesday, September 1, 2020 at 3:17:16 AM UTC+10, Thomas Koenig wrote: >> >>> There could be a use, though, but it would be narrow. Assuming you >>> had a Fortran program fragment like >>> >>> DIMENSION A(4,11) >>> DO 10 J=1,9 >>> DO 10 I=1,4 >>> 10 A(I,J) = 2.0 >>> ... >> In PL/I, one might write >> A = 2.0; Sure, you can do that in modern Fortran, too. >Anyway, that's a common way to clear a print area, except it's done: > > MVI PRINT,X'40' > MVC PRINT+1(131),PRINT > >I was always suspicious that this would cause a performance hit >so I preferred to define an area of 132 spaces and move that to >areas that needed clearing. Since the 370 came along in the early 1970s you could write something like LA 2,PRINT target area LA 3,132 target length LA 5,x'40' SLL 5,24 padding byte in high byte, length zero MVCL 2,4 this is probably too clever for a 132 byte field but the POO says it's the fastest way to clear a block bigger than 256 bytes -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <dan1espen@gmail.com> |
|---|---|
| Date | 2020-09-01 16:04 -0400 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rim9fo$t5s$2@dont-email.me> |
| In reply to | #213532 |
John Levine <johnl@taugh.com> writes: > In article <rile83$dlm$1@dont-email.me>, > Dan Espen <dan1espen@gmail.com> wrote: >>Robin Vowels <robin.vowels@gmail.com> writes: >> >>> On Tuesday, September 1, 2020 at 3:17:16 AM UTC+10, Thomas Koenig wrote: >>> >>>> There could be a use, though, but it would be narrow. Assuming you >>>> had a Fortran program fragment like >>>> >>>> DIMENSION A(4,11) >>>> DO 10 J=1,9 >>>> DO 10 I=1,4 >>>> 10 A(I,J) = 2.0 >>>> ... >>> In PL/I, one might write >>> A = 2.0; > > Sure, you can do that in modern Fortran, too. > >>Anyway, that's a common way to clear a print area, except it's done: >> >> MVI PRINT,X'40' >> MVC PRINT+1(131),PRINT >> >>I was always suspicious that this would cause a performance hit >>so I preferred to define an area of 132 spaces and move that to >>areas that needed clearing. > > Since the 370 came along in the early 1970s you could write something like > > LA 2,PRINT target area > LA 3,132 target length > LA 5,x'40' > SLL 5,24 padding byte in high byte, length zero > MVCL 2,4 > > this is probably too clever for a 132 byte field but the POO says it's the fastest > way to clear a block bigger than 256 bytes Getting to the Z/Series you can get that blank in the high order of the low part of the 64 bit register with: IILF Rx,X'40000000' Insert Immediate Low Full -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Robin Vowels <robin.vowels@gmail.com> |
|---|---|
| Date | 2020-09-01 18:13 -0700 |
| Subject | Re: 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <742c4c80-bc40-492f-b648-6a72a0b64f73n@googlegroups.com> |
| In reply to | #213532 |
On Wednesday, September 2, 2020 at 4:08:37 AM UTC+10, John Levine wrote: > In article <r.......@dont-email.me>, > Dan Espen <d......@gmail.com> wrote: > >Robin Vowels <r........@gmail.com> writes: > > > >> On Tuesday, September 1, 2020 at 3:17:16 AM UTC+10, Thomas Koenig wrote: > >> > >>> There could be a use, though, but it would be narrow. Assuming you > >>> had a Fortran program fragment like > >>> > >>> DIMENSION A(4,11) > >>> DO 10 J=1,9 > >>> DO 10 I=1,4 > >>> 10 A(I,J) = 2.0 > >>> ... > >> In PL/I, one might write > >> A = 2.0; > Sure, you can do that in modern Fortran, too. . True, but the OP was referring to earlier verstions of FORTRAN up to FORTRAN 77. The difference is that in PL/I, its been possible to write that since 1966. . > >Anyway, that's a common way to clear a print area, except it's done: > > > > MVI PRINT,X'40' > > MVC PRINT+1(131),PRINT > > > >I was always suspicious that this would cause a performance hit > >so I preferred to define an area of 132 spaces and move that to > >areas that needed clearing. > > Since the 370 came along in the early 1970s you could write something like > > LA 2,PRINT target area > LA 3,132 target length > LA 5,x'40' > SLL 5,24 padding byte in high byte, length zero . I think that SR 5,5 and IC 5,=X'40' would be better than the previous two instructions, or even one straight L. . > MVCL 2,4 > > this is probably too clever for a 132 byte field but the POO says it's the fastest > way to clear a block bigger than 256 bytes.
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2020-09-02 02:14 +0000 |
| Subject | Re: block moves, 70X index OR mode, Fortran, not KDF9, not IBM system/360 ad |
| Message-ID | <rimv64$1l1e$2@gal.iecc.com> |
| In reply to | #213556 |
In article <742c4c80-bc40-492f-b648-6a72a0b64f73n@googlegroups.com>, Robin Vowels <robin.vowels@gmail.com> wrote: >> Since the 370 came along in the early 1970s you could write something like >> >> LA 2,PRINT target area >> LA 3,132 target length >> LA 5,X'40' >> SLL 5,24 padding byte in high byte, length zero >. >I think that SR 5,5 and IC 5,=X'40' would be better than the previous >two instructions, or even one straight L. The fill character has to be in the high byte of the register, not the low byte. I suppose you could do ICM 5,8,=X'40' but I don't see why that would be better than LA and SLL which don't have the extra memory reference. >> MVCL 2,4 >> >> this is probably too clever for a 132 byte field but the POO says it's the fastest >> way to clear a block bigger than 256 bytes. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
Page 22 of 30 — ← Prev page 1 … 20 21 [22] 23 24 … 30 Next page →
Back to top | Article view | alt.folklore.computers
csiph-web