Jump to content

Talk:Fixed-block architecture

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by UnicornTapestry (talk | contribs) at 01:06, 7 January 2009 (CKD versus CHR/CTR: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing Stub‑class
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.
Note icon
This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the |auto= parameter.

CKD versus CHR/CTR

The article mistakes terminology:

IBM mainframe systems' disk layout had traditionally been count-key-data (CKD)…

In fact, the physical layout of the first FBA devices remained precisely the same; it was in the disc controllers that the differences occurred.

CKD had implications for the channel programmer, in that it was possible for a record to be located not solely by its location, but by a key. However, the actual architecture was CHR (cylinder-head-record), also called CTR (cyl-trk-rec). See DASD article.

--UnicornTapestry (talk) 01:06, 7 January 2009 (UTC)[reply]