Rex,
I cannot find Alan's quoted passage, but I think it is a stretch to say " With
the arrival of 2105s, the CU was inside the same cabinet as the drives and
Logical CUs (LCUs) were born."
I'm fairly certain that EMC, STK, and HDS delivering this well before IBM could
get the E10 and F20 out of the door.
I think it was more like last to market in IBM's case.
Ron
RON HAWKINS
Director, Ipsicsopt Pty Ltd (ACN: 627 705 971)
m+61 400029610| t: +1 4085625415 | f: +1 4087912585
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Pommier, Rex
Sent: Thursday, 16 May 2019 05:53
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] [External] Re: Ancient DASD connectivity
<quote from Alan below>
It was sheer size of the componentry that drove this design. I think the 3990
was the last stand-alone disk controller. With the arrival of 2105s, the CU
was inside the same cabinet as the drives and Logical CUs (LCUs) were born.
One big black box (literally). Adding additional cabinets no longer affected
the I/O configuration - just capacity.
</quote>
We don't hear much about them, but where did the 9340 subsystem fit in the
timeline between 3990 and 2105? or the RAMAC2? Both those devices had the
controller built in the same frame as the disk spindles. How about the RVA?
Rex
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Alan Altmark
Sent: Wednesday, May 15, 2019 1:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: Ancient DASD connectivity
On Wed, 15 May 2019 14:59:00 +0200, R.S. <r.skoru...@bremultibank.com.pl> wrote:
>In the old days there was a Storage Control Unit, i.e. 3830 and disk
>controller within disk cabinet, i.e. 3350-A2
>
>So, we have CPC-cable1-3830-cable2-3350A2controller-internal_cable3-disk.
>
>I'm trying to understand separation of duties between 3830 and 3350A2
>controller.
>What was defined as CU - it was 3830 or controller within 3350 cabinet?
>Which cable was a channel (Bus&Tag)? I guess it is "cable1" connecting
>CPC and 3830.
>
>Not to mention that some old reference manual's diagram shows yet
>another box between CPC and 3830 SCU.
Depending on the year, you might find (rusty memory):
host
- channel 0
- channel 1
- switch (2814/2914)
- channel 1
- Control unit 0 (bus & tag from channel/switch)
- device 0 ("string header") (A-Unit)
- device 1 (B unit)
- device 2 (B unit)
- device 3 (B unit)
- Control unit 1 (bus & tag) from CU 0
- repeat
- channel 2
- repeat
The A units handled the fan-out (signal and power) to dependent devices (B
units) in the string and had the logic to talk to the channel. The B units
were just dumb slaves to the A unit. The A units could only talk to B units
of the same type since all the power and signaling was custom. The interface
between the CU and the A unit was generally such that a CU could handle strings
of newer and older device types. The number of A units required, the number
of I/O devices included in an A unit, and the way B units were attached was
generally model specific, so you would see variations on the above. (Don't
confuse with more modern UNIT=3390B to indicate a PAV to MVS!)
It was sheer size of the componentry that drove this design. I think the 3990
was the last stand-alone disk controller. With the arrival of 2105s, the CU
was inside the same cabinet as the drives and Logical CUs (LCUs) were born.
One big black box (literally). Adding additional cabinets no longer affected
the I/O configuration - just capacity.
We still have switches, of course, but they're no longer pull-turn-push. :-)
Alan Altmark
IBM Systems Lab Services
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
The information contained in this message is confidential, protected from
disclosure and may be legally privileged. If the reader of this message is not
the intended recipient or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any disclosure,
distribution, copying, or any action taken or action omitted in reliance on it,
is strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
