Talk:Task Control Block
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
History section
The entire history section has nothing to do with the subject of the article; it discusses the SRB, a newer and unrelated control block. This material belongs in MVS. --Shmuel (Seymour J.) Metz Username:Chatul (talk) 17:35, 20 January 2022 (UTC)
ECB
I was trying to find an article on ECB, Event Control Block, and found this. Is there any article related to ECB? Gah4 (talk) 23:10, 10 July 2023 (UTC)
- I'm not sure that separate articles are appropriate, but certainly the OS/360 and successors could usefully describe
- Event Control Block (ECB)
- WAIT and POST macros
- ENQ, DEQ and RESERVE macros
Similarly, the MVS article could usefully discuss
- Locks
- Service Request Block (SRB)
- Expand upon text currently in Task Control Block#History and then remove that section.
- SCHEDULE macro
Finally, UNIX System Services could usefully discuss latches. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 10:59, 11 July 2023 (UTC)
- I was wondering about more general than just IBM. (or OS/360 and successors.) Other OS must have the synchronization problem, too. Any OS that allows asynchronous I/O needs some method to synchronize things. Now, I suppose it could be OS internal, but could still be explained along with ECB. Well, OK, along with ECB there is WAIT and POST. Gah4 (talk) 03:46, 5 April 2025 (UTC)
Incorrect for from wikidata
@The Anome: Tasks in OS/360 and successors are roughly equivalent to threads in UNIX, not to processes. If it says otherwise in Wikidata, that should be fixed.
Prior to MVS, the ATTACH macro creates a subtask running in the same partition (PCP, MFT, OS/VS1) or region (MVT, SVS); in MVS, the ATTACH macro creates a subtask running in the same region and address space.
In UNIX System Services, starting with MVS/ESA OpenEdition, a new process normally runs in a separate address space, although there are provisions for sharing an address space. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:49, 4 April 2025 (UTC)
- Thank you! That's useful; I didn't know about the distinction. Do you want to fix things up to make the articles and Wikidata entries correct? — The Anome (talk) 18:13, 4 April 2025 (UTC)
- @Gah4 and The Anome:I've corrected it, and also added some information to OS/360 and successors. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 19:05, 4 April 2025 (UTC)
- Thank you! I learned something today. — The Anome (talk) 19:21, 4 April 2025 (UTC)
- @Gah4 and The Anome:I've corrected it, and also added some information to OS/360 and successors. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 19:05, 4 April 2025 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.