Talk:Count key data/Archive 2

Archive 1

Archive 2

Sections having nothing to do with CKD format

Some sections of the article deal with topics that seem unrelated to CKD format, such as Count key data § Dynamic paths, which discusses a feature that appears to discuss data paths; the feature sounds like one that could also be used with FBA. Others that might be unrelated to CKD include Count key data § Multiple Requesting and Count key data § Command Retry. Perhaps there should be a page, or a section of a page, discussing the architecture of IBM mainframe storage hardware and firmware, and perhaps the general notion of channel, control unit, and device. Guy Harris (talk) 06:28, 8 March 2024 (UTC)

The article lede does state the article also covers CKD channel commands but the sections cited above do seem to be inappropriate to this article. Problem is IBM channels are only briefly covered in the various IBM System articles, e.g. IBM System/360 Channels with the global article on Channel I/O being perhaps to generic for such material. Maybe these sections can be moved into the article on the IBM system in which such features were first announced. A bit of a research project, but maybe some of the editors will recall the announcement date and system. Tom94022 (talk) 19:22, 8 March 2024 (UTC)

Upon further study it seems to me most of what is in the block multiplexer channel enhancements section of this article should be moved to History of IBM CKD Controllers article. Tom94022 (talk) 21:40, 8 March 2024 (UTC)

History of IBM CKD Controllers looks as if it can serve as the page that "[discusses] the architecture of IBM mainframe storage hardware and firmware", at least for CKD drives. Guy Harris (talk) 21:55, 8 March 2024 (UTC)

The CCW opcodes controlling Dynamic paths are specific to ECKD controllers, and belong here until there is an ECKD article. I'm not aware of any FBA controller supporting them, I don't know enough about SCSI drives accessed over FCP to comment on them.

Some of the material belongs in IBM System/360#Input/Output. Some, however is specific to DASD, e.g., the Set Sector and Read Sector CCW opcodes.

There really ought to be architecture article fir S/360 through z/Architecture, as well as an ECKD article; much of what you mention would fit naturally there. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 15:25, 10 March 2024 (UTC)

"Architecture article", singular, or "architecture articles", plural? There's already IBM System/360 architecture, with IBM System/360 covering the family as a product line, and z/Architecture, with IBM Z covering the family as a product line, but the intermediate architectures don't have such a split.

(x86 has a single x86 page, which covers the product line of chips, and has some details common to 16-bit, 32-bit, and 64-bit architectures, and also IA-32 for the 32-bit version and x86-64 for the 64-bit version.) Guy Harris (talk) 23:17, 10 March 2024 (UTC)

The IBM System/360 architecture doesn't cover S/370. 370/XA, ESA/370, ESA/390 or z/Architecture, and is already at 86K; a single architecture article would be too big. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:27, 11 March 2024 (UTC)

Actually I think all architectures have homes either in articles or sections as follows S/370, 370/XA, ESA/370, ESA/390 or z/Architecture so all we have to do is find the right one to move the irrelevant material. Tom94022 (talk) 17:42, 11 March 2024 (UTC)