Talk:Execute Channel Program
Appearance
![]() | Computing: Software Stub‑class | ||||||||||||
|
Duplicate info
I have been doing some work on this article and noticed that this article overlaps Channel I/O and, to some extent Count key data. The latter is strictly DASD, while it seems like the former should be less IBM-centric. On the other hand the topic of this article is the EXCP macro, and perhaps not the internals of CCWs. There seems to be no place where the CCW information fits well, but perhaps Channel I/O and Count key data have too much detail. I think we need another article to consolidate System/360 (and later) I/O processing and strip the excess out of these three articles. I don't know what such an article should be called. Peter Flass (talk) 16:18, 6 December 2019 (UTC)
- General information on S/360 channel command words should either be in a separate article or in in expanded section of Channel I/O. It's reasonable for that article to have a simple DASD channel program to illustrate the handling of Status Modifier, but any further examples of DASD channel programs should be in DASD-related articles. Likewise, information on the CAW, CCW and IDA list formats belongs in Channel I/O and IBM System/360 architecture, not in Execute Channel Program, Execute Channel Program in Real Storage or Start Input/Output. If anybody writes a S/370 architecture, S/390 architecture or IBM Z architecture article then that is where the new CCW and IDAL formats belong, possibly in addition to Channel I/O.
- The existing Channel I/O article is highly IBM Centric and doesn't even adequately cover older IBM systems. Perhaps it should be split into a generic article and an article specific to the S/360 family. I'd love to see someone add material on, e.g., CDC 1604, GE-600 series, UNIVAC 1107 Shmuel (Seymour J.) Metz Username:Chatul (talk) 19:33, 6 December 2019 (UTC)
- Agreed the Channel I/O article should be less IBM centric and would prefer expanding the article to add other "channels" to this article making the IBM Channel a specific instance. One problem might be finding an RS to combine the various "channels" in one article. A quick look at Patterson and Hennessy, "Computer Organization and Design' and Blaauw and Brooks, "Computer Architecture wasn't to helpful. Apparently today channel is a mainframe term and other than perhaps IBM it isn't much used these days.
- Shouldn't this talk be moved to the Channel I/O article and not here? Tom94022 (talk) 00:30, 9 December 2019 (UTC)