In <-21782995201426460@unknownmsgid>, on 11/17/2012 at 10:30 AM, Quasar Chunawala <quasar.chunawa...@gmail.com> said:
>I hope this finds you in the pink of health. I am Quasar, and I hail >from Mumbai, India. I own a blog on the internet, parked at >http://www.mainframes360.com. I am an application developer by >profession. >I intend to write an article on TSO/E on my blog. You might try skimming "The ABC's of Systems Programming", paying particular attention to the Workload manager (WLM). However, be aware that a lot of things have changed over the decades. You might also scrounge around in bitsavers. >I would like you to throw some light on the technical underpinnings >of how TSO really accomplishes the feat of time-sharing. In current systems, there is no significant difference between a TSO session and a batch job; the same resource allocation methods apply to both. In the original TSO there were mechanisms that applied only to TSO sessions. >But, it occurs to me, why should a time-slot be given to a TSO >user, who hasn't pressed an AID key(like Enter)? That's not how time-slicing works. If a task is waiting for, e.g., an I/O operation then it doesn't get control of the CPU just because a time-slice interval has expired. The Dispatcher assigns a CPU to a ready unit of wok, not to one that is nondispatchable or in a wait state. BTW, the concept of AID applies to 3270 displays; while they are by far the most common today, they are not the only terminals that TSO supports. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2 <http://patriot.net/~shmuel> We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
