In <[EMAIL PROTECTED]>, on 04/07/2006
at 10:38 AM, Michael Knigge <[EMAIL PROTECTED]> said:
>For example the call of "fork()" is somewhat strange.
Fork is a Unix service and doesn't obey the rules for non-Unix
services. You should have a bookshelf for z/OS Unix System Services,
and I believe that there are some redbooks as well.
>Now, I guess everything would become clearer if I would know exactly
>all the magic of address spaces, processes, thraeds, tasks, subtasks
>and so on.
Well, address spaces and tasks are described in the basic MVS
documentation, but for processes and threads you must consult the Unix
System Services manuals.
>Now.... is is task a process?
No. The closest Unix analog to a task is a thread.
>If I use subtasks - do I use multiple-process address spaces?
For a Unix application, it depends on how your system is configured.
For a non-Unix application, the question doesn't apply.
>What is the difference between a subtask and a thread?
A thread is a unit of work in a Unix context; a task is a unit of work
in an MVS context. A task belongs to a jobstep within an address space
and a thread belongs to a process.
>I've tried POP (Principles of Operation) but this wasn't the right
>one...
PoOps doesn't and shouldn't have information on the various operating
systems. Look at the Unix bookshelf and at the redbooks.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
