>But, there was/is a case with ESA 5.2, where there is only >the forked/spawned/whatever USS piece is the only part left, >and the originating/calling address space is no longer with >us. It's a USS process, with no apparent parrent, and caused >us grief when we were trying to 'get it right' with our WLM >policy. >If it's 'fixed', all the better.
In the beginnings there was only fork(), spawn() came later. Parents never disappeared if not programmed to act so. But you might have had problems with the jobnames of new (non-local) processes. Since you're referring to problems with the WLM policy, I guess you had some classification rule catching the initial job but found that the child is not caught by this rule. The FTP daemon comes to mind: It forks once or twice at startup and the parent(s) terminate there after leaving only the final child in place. But note that the ftpd code itself let's the parents terminate. -- 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
