History of IBM CKD Controllers
Beginning with its 1964 System/360 announcement, IBM's mainframes initially accessed CKD (Count key data) subsystems via a channel connected to separate Storage Control Units (SCUs) with attached Direct Access Storage Devices (DASD), typically a hard disk drive. This practice continued in IBM's larger mainframes thru System/370; however low end systems generally used lower cost integrated attachments where the function of the SCU was combined with that of the channel, typically called an Integrated File Adapter.
Wikipage redirect
Link from a Wikipage to another Wikipage
seeAlso
primaryTopic
History of IBM CKD Controllers
Beginning with its 1964 System/360 announcement, IBM's mainframes initially accessed CKD (Count key data) subsystems via a channel connected to separate Storage Control Units (SCUs) with attached Direct Access Storage Devices (DASD), typically a hard disk drive. This practice continued in IBM's larger mainframes thru System/370; however low end systems generally used lower cost integrated attachments where the function of the SCU was combined with that of the channel, typically called an Integrated File Adapter.
has abstract
Beginning with its 1964 System ...... controls attaching an A-unit.
@en
Link from a Wikipage to an external page
Wikipage page ID
48,481,944
page length (characters) of wiki page
Wikipage revision ID
961,285,694
Link from a Wikipage to another Wikipage
wikiPageUsesTemplate
comment
Beginning with its 1964 System ...... ed an Integrated File Adapter.
@en
label
History of IBM CKD Controllers
@en