>This is how z/OS emulates UNIX processes. >Some are invoked by fork() which leaves the 'parent' task running. >All invoked this way will terminate when the invoking task ends. >Others (like FTPD) are invoked by spawn() which leaves the process >running even when the 'parent' goes away. These are better managed >by modifying USS address spaces (OMVS) to terminate, or through the <shell.
Not quite. Some UNIX programs start a new child process and then terminate leaving the child active. Other UNIX programs start a new child and stay active waiting for the child to terminate. This depends on the implementation of the function the program has to fulfill. There are two ways to start a new process: fork() and spawn(). Whether the parent terminates before or after the child is not dependent on which of the above functions is being used. In MVS, everything needs a jobname, this is no different for z/OS UNIX processes. When a UNIX process starts a new child process, that child process inherits the jobname from its parent (except when a local process is started). If the original jobname is 7 or less characters, a single digit is appended. 1 for the first child, 2 for the second, ..., 1 again for the 10th child and so on. If the jobname is exactly 8 characters is left unchanged. In addition, there are ways to give a new child a specific jobname. Shell sessions have the userid as jobname and not inted's jobname. So, if you want syslogd to always show up with the same jobname, start it with an 8 character jobname. -- Peter Hunkeler Credit Suisse ---------------------------------------------------------------------- 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
