Radoslaw,

And who manufactured and shipped the RVA before it was called an RVA? 

I was working with an ICEBERG before IBM and STK had even thought about inking 
a deal. Iceberg 1994. RVA 1996.

I'm pretty sure the EMC Symmetrix 5500 supported LCU before the RVA rebadging 
happened. I'm not sure about the EMC 4800.

I'm not strong on IOCP and such like, but wasn't it the LCU support for the 
3880 that allowed the RAID vendors to provide LCU that looked like more than 
one box? Something tells me that this was why you could cross-connect halves of 
a 3880 controller to different strings.

Prepared to be corrected.


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 R.S.
Sent: Monday, 20 May 2019 05:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] [External] Re: Ancient DASD connectivity

W dniu 2019-05-17 o 14:47, Ron Hawkins pisze:
> 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.

Yes, you are right, with one exception: also IBM delivered LCUs before 2105.
Example: RVA (the larger one) had up to 1024 devices. Yes, RVA was STK under 
the cover, but delivered by IBM.
Of course 3990 CU definition allow LCUs.
However 2105 (Shark) was first disk system supporting PAVs.

BTW: I liked HDS 7700C/E aka Comparex Tetragon 2000/2100 boxes. With one
drwaback: number of logical paths. The number was small, 16 per channel. 
So, 4 CUs and 5 LPARs and you have interesting problems with not clue form the 
system. I spent 2 days trying to IPL system from fifth LPAR...

Regards
--
Radoslaw Skorupka
Lodz, Poland




======================================================================

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) 
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać 
karze.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. 
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, 
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 
01.01.2018 r. wynosi 169.248.488 złotych.

If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169,248,488 as at 1 January 2018.

----------------------------------------------------------------------
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

Reply via email to