> >Hmmm. If a batch job spawns (not forks) a subprocess with _BPX_SHAREAS=YES wouldn't that subprocess run under the parent's JobID; no BPXAS, no STC?
Local child processes, started via local spawn(), or attach_exec(), or attach_execmvs(), are run in the same address space as the parent process. I.e. in the TSO, batch job initiator, APPC initiator or STC address space. (Don't know much about APPC programs, but I assume there is nothing prohibiting then to use UNIX services.) The same applies to the case when an non-UNIX program is being dubbed because it is using A UNIX service now, i.e. when it becomes a UNIX process. Jobname and jobid are address space level attributes, not task or process level. Non-local child processes, started via fork(), or non-local spawn(), *always* run in UNIX initiator address space, aka BPXAS. BPXAS was introduced with OS/390 V1.3 (I seem to remember). Before that, APPC initiators were used to provide a home for non-local child processes. -- Peter Hunkeler -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
