> The first device to support "disconnect" was the 3330 No; the 3330 was a Johnny come lately. The first device such was the 2305 fixed head disk attached to the 2835 controller.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Wednesday, May 15, 2019 9:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Ancient DASD connectivity The first device to support "disconnect" was the 3330 which also connected to a 3830. Prior to that IO in both directions tied up the entire path from CPU to device and back for the duration (2314, 2311 dasd). The flow of a "typical" IO request: Channel passes commands to 3830 and disconnects. 3830 passes commands to "logic" boards in 3350A2 and disconnects "logic boards" issue commands to individual device (3350A2/B2) and disconnect. The following processing will then occur: Device handles requests and reconnects to logic boards. "logic boards" reconnect to 3830 3830 communicate to CPC Data transfer occurs. Note the entire path (device-logic boards-3830-channel) is "locked" for the duration of the data transfer. The paradigm has generally not changed since the "old days". The major differences between the "old days" and today: There is no longer a "separate" control unit e.g. 3830 This logic is now in the DASD device itself. The advent of cache controllers allows for the reconnection process to be performed "asynchronously". Again this is packaged in the device itself. Once the data has been passed from the device to the cache, the devices are free to handle other requests. This allows for greater DASD thruput. BTW, between the 3830/3350 and "modern DASD". There were stand-alone 3880/3380 and 3990/3390 "control units" with cache capability. The stand-alone logic represented by the 3830 , 3880 and 3990 control units have been absorbed into the device itself. Externally it is "CPU-->DASD box" Internally, all of the components of the "original paradigm" are still present with the detail obscured by the hardware. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of R.S. Sent: Wednesday, May 15, 2019 7:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Ancient DASD connectivity (this is mostly historical question) I'm trying to understand the role of old boxes in DASD connectivity. From IODF/HCD point of view we have CPC-channels-CU-some_cable-DEVice Nowadays in real world we have CPC-ficon-DASDbox and DASDbox is both CU+DEV (emulated). 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. -- 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,https://apc01.safelinks.protection.outlook.com/?url=www.mBank.pl&data=02%7C01%7Callan.staller%40HCL.COM%7C7e30a6a721eb4e26d65d08d6d935283d%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636935219702096401&sdata=256aP9a0gLzpePAowqaLDRZ0r1BmkBk1Z%2BqFd3Ju9EI%3D&reserved=0, 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,https://apc01.safelinks.protection.outlook.com/?url=www.mBank.pl&data=02%7C01%7Callan.staller%40HCL.COM%7C7e30a6a721eb4e26d65d08d6d935283d%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636935219702096401&sdata=256aP9a0gLzpePAowqaLDRZ0r1BmkBk1Z%2BqFd3Ju9EI%3D&reserved=0, 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 ::DISCLAIMER:: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- 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
