Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-29 Thread Shmuel Metz (Seymour J.)
In 0871825165316453.wa.paulgboulderaim@listserv.ua.edu, on 12/22/2013 at 10:56 AM, Paul Gilmartin paulgboul...@aim.com said: ATTACH/DETACH appeared contemporaneously with TSO!? IBM Operating System/360 Concepts and Facilities, C28-6535-0, is ©1965 and mentions ATTACH. Even ATTACH for MFT

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-29 Thread Shmuel Metz (Seymour J.)
In 5000331903687025.wa.afg0510videotron...@listserv.ua.edu, on 12/22/2013 at 10:01 AM, Andreas F. Geissbuehler afg0...@videotron.ca said: In the early '70 IBM released a new and improved CRJE called TSO, CRJE was a new and improved CRBE, but TSO was something new. I believe it was part of

Re: Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-29 Thread Shmuel Metz (Seymour J.)
In 1689901514.1458087.1387743082672.javamail.r...@comcast.net, on 12/22/2013 at 08:11 PM, DASDBILL2 dasdbi...@comcast.net said: I seem to remember working with some S/360 Model 55 MPs at an FAA Air Route Traffic Control Center in 1978.  ITYM 9020, which used modified S/360 processors as

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-29 Thread Shmuel Metz (Seymour J.)
In 017401cefffc$510bc390$f3234ab0$@mcn.org, on 12/23/2013 at 11:30 AM, Charles Mills charl...@mcn.org said: http://bitsavers.trailing-edge.com/pdf/ibm/360/os/R19_Jun70/GC28-6628-5_System_Control_Blocks_Rel_19_Jun70.pdf gives the layout of the TCB and the field names all begin with TCB. Page

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-29 Thread Shmuel Metz (Seymour J.)
In 20131225020725.60c1924...@panix5.panix.com, on 12/24/2013 at 09:07 PM, Randy Hudson i...@panix.com said: No JES then; HASP might have been available, but it mostly worked by emulating devices and hooking into standard exits (IEFUJV, IEFUJI) to massage the JCL to point to its (pseudo-)

Re: Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-29 Thread Tony Harminc
On 22 December 2013 15:11, DASDBILL2 dasdbi...@comcast.net wrote: I seem to remember working with some S/360 Model 55 MPs at an FAA Air Route Traffic Control Center in 1978. They must have had smaller maximum real memories and run slower than model 65MPs, but had the same RPQ extra

Re: Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-29 Thread Anne Lynn Wheeler
used for BT channels, though with different pinouts, of course, is used for the Direct I/O feature. re: http://www.garlic.com/~lynn/2013o.html#56 Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?) 370 princ-of-ops, SIGP instruction for processor signaling

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-24 Thread Randy Hudson
In article 0871825165316453.wa.paulgboulderaim@listserv.ua.edu Gil wrote: ATTACH/DETACH appeared contemporaneously with TSO!? I'm astonished! I'd have guessed they were much older, perhaps even aboriginal OS/360. Was there no multiprocessing mechanism older than TSO? RYO, I suppose.

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-23 Thread Tom Marchant
On Sun, 22 Dec 2013 10:01:33 -0600, Andreas F. Geissbuehler wrote: TSO brought us Sub-Tasking and related macros ATTACH and DETACH No, it didn't. ATTACH and DETACH were both described in IBM Operating System/360 Concepts and Facilities, publication C28-6535-0, published in 1965.

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-23 Thread Charles Mills
@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Monday, December 23, 2013 9:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Curiosity: TCB mapping macro name - why IKJTCB? On Sun, 22 Dec 2013 10:01:33 -0600, Andreas F. Geissbuehler wrote: TSO brought us Sub-Tasking and related macros ATTACH

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-22 Thread Andreas F. Geissbuehler
Straight from a slowly fading memory... In the early '70 IBM released a new and improved CRJE called TSO, a TCAM application program. I believe it was part of IBM's worst-ever release, OS/MVT Release 19. TSO brought us Sub-Tasking and related macros ATTACH and DETACH using a newly expanded

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-22 Thread Paul Gilmartin
On Sun, 22 Dec 2013 10:01:33 -0600, Andreas F. Geissbuehler wrote: Straight from a slowly fading memory... In the early '70 IBM released a new and improved CRJE called TSO, a TCAM application program. I believe it was part of IBM's worst-ever release, OS/MVT Release 19. TSO brought us

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-22 Thread Steve Comstock
On 12/22/2013 9:56 AM, Paul Gilmartin wrote: On Sun, 22 Dec 2013 10:01:33 -0600, Andreas F. Geissbuehler wrote: Straight from a slowly fading memory... In the early '70 IBM released a new and improved CRJE called TSO, a TCAM application program. I believe it was part of IBM's worst-ever

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-22 Thread Anne Lynn Wheeler
paulgboul...@aim.com (Paul Gilmartin) writes: ATTACH/DETACH appeared contemporaneously with TSO!? I'm astonished! I'd have guessed they were much older, perhaps even aboriginal OS/360. Was there no multiprocessing mechanism older than TSO? RYO, I suppose. That's what I understand JES and

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-22 Thread Daniel Skwire
Multiprocessing support earlier than TSO? It was before my time, but I read and heard plenty about MVT/MP65, which predates TSO's rollout by a couple years, I think. MP65 had challenges: 'sympathy sickness where a CPU problem took down both CPUs in the complex, kinda sorta anti-redundancy, if

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-22 Thread Anne Lynn Wheeler
CPUs in the complex, kinda sorta anti-redundancy, if you will. Cured by MVS Alternate CPU recovery. Serialization? Not so good with TEST and SET, I think it was called. Much better with Compare and Swap, etc. re: http://www.garlic.com/~lynn/2013o.html#54 Curiosity: TCB mapping macro name - why

Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-22 Thread DASDBILL2
I seem to remember working with some S/360 Model 55 MPs at an FAA Air Route Traffic Control Center in 1978.  They must have had smaller maximum real memories and run slower than model 65MPs, but had the same RPQ extra instructions to enable multi-processing. Bill Fairchild - Original

Re: Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-22 Thread Daniel Skwire
I thought the FAA had special hybrid 6 computer systems, 3 x 2 way MPs? Interesting! Dan Sent from my iPad On Dec 22, 2013, at 3:11 PM, DASDBILL2 dasdbi...@comcast.net wrote: I seem to remember working with some S/360 Model 55 MPs at an FAA Air Route Traffic Control Center in 1978. They

Re: Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-22 Thread Ray Overby
userid - ssdrso Ray Overby Key Resources, Inc Ensuring System Integrity for z/Series (312) 574-0007 On 12/22/2013 4:56 PM, Daniel Skwire wrote: I thought the FAA had special hybrid 6 computer systems, 3 x 2 way MPs? Interesting! Dan Sent from my iPad On Dec 22, 2013, at 3:11 PM, DASDBILL2

Re: Early !BM multiprocessors (renamed from Curiosity: TCB mapping macro name - why IKJTCB?)

2013-12-22 Thread Anne Lynn Wheeler
dskw...@mindspring.com (Daniel Skwire) writes: I thought the FAA had special hybrid 6 computer systems, 3 x 2 way MPs? re: http://www.garlic.com/~lynn/2013o.html#54 Curiosity: TCB mapping macro name - why IKJTCB? http://www.garlic.com/~lynn/2013o.html#55 Curiosity: TCB mapping macro name - why

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-21 Thread Shmuel Metz (Seymour J.)
In 1891265032.6001250.1386631293335.javamail.r...@comcast.net, on 12/09/2013 at 11:21 PM, DASDBILL2 dasdbi...@comcast.net said: In general, hardware-oriented control blocks' mapping macros begin with IHA, That came later. IHA was originally Supervisor. I must assume its mapping DSECT macro

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-10 Thread Robert A. Rosenberg
At 16:37 -0500 on 12/10/2013, Peter Relson wrote about Re: Curiosity: TCB mapping macro name - why IKJTCB?: I don't really know, but someone (I can't remember who) mentioned to me something about this fairly recently. By the way, IHARB is mentioned. It's in maclib. But there's also IKJRB

Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread John McKown
Normally, I associate the prefix IKJ with TSO. Does anybody out there know why the TCB mapping macro is named IKJTCB instead of IHATCB. The PSA mapping macro is IHAPSA. The RB map name is IHARB. The ASCB map is IHASCB. Just curious. -- This is clearly another case of too many mad scientists,

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Micheal Butz
Maybe all the early mappings a had IKJ Sent from my iPhone On Dec 9, 2013, at 4:48 PM, John McKown john.archie.mck...@gmail.com wrote: Normally, I associate the prefix IKJ with TSO. Does anybody out there know why the TCB mapping macro is named IKJTCB instead of IHATCB. The PSA mapping

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Charles Mills
: Curiosity: TCB mapping macro name - why IKJTCB? Normally, I associate the prefix IKJ with TSO. Does anybody out there know why the TCB mapping macro is named IKJTCB instead of IHATCB. The PSA mapping macro is IHAPSA. The RB map name is IHARB. The ASCB map is IHASCB. Just curious. -- This is clearly

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread John Gilmore
TSO was not an original element of [any early flavor of] OS for the System/360. Its IKJ prefix came a lot later. TSO was initially a literal, dispensable option; it was not integrated into the operating system as it now is. John Gilmore, Ashland, MA 01721 - USA

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Charles Mills
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Gilmore Sent: Monday, December 09, 2013 2:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Curiosity: TCB mapping macro name - why IKJTCB? TSO was not an original element of [any early flavor of] OS for the System/360. Its IKJ prefix came a lot later

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread DASDBILL2
the S/360 was announced?  The mystery deepens. Bill Fairchild Franklin, TN - Original Message - From: John McKown john.archie.mck...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, December 9, 2013 3:48:03 PM Subject: Curiosity: TCB mapping macro name - why IKJTCB? Normally, I

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread J R
than named. . . Date: Mon, 9 Dec 2013 15:48:03 -0600 From: john.archie.mck...@gmail.com Subject: Curiosity: TCB mapping macro name - why IKJTCB? To: IBM-MAIN@LISTSERV.UA.EDU Normally, I associate the prefix IKJ with TSO. Does anybody out there know why the TCB mapping macro is named

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Gerhard Postpischil
On 12/9/2013 5:43 PM, Charles Mills wrote: I -- and John I am sure -- remember when it came along. A radical concept. A time sharing option for OS/360. Ooh. Not sure about this. And it gave new meaning to the word slow. I'm not so sure about the radical, as time-sharing was available earlier

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Tony Harminc
On 9 December 2013 19:14, J R jayare...@hotmail.com wrote: - The first word of the TCB proper, ie. +0 is TCBRBP, but this offset is fixed by architecture! I think a number of these comments on doubtful sounding fields came about only because of the microcoded assists that arrived in the days

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Jim Mulder
- The first word of the TCB proper, ie. +0 is TCBRBP, but this offset is fixed by architecture! Back in the early '70s, when I first noticed the IKJTCB macro, I speculated that TSO was the first component to macroize the DSECT, and hence gave it the IKJ prefix. I never found out the

Re: Curiosity: TCB mapping macro name - why IKJTCB?

2013-12-09 Thread Mike Schwab
http://www.cbttape.org/os360.htm Order the CD-ROM here. But I think it is the last version of OS/360. On Mon, Dec 9, 2013 at 7:50 PM, Tony Harminc t...@harminc.net wrote: deleted What we need is some source code from an OS/360 version before 20.x, which is when TSO became available. But of