MVS Jan 2005.p65 - CBT Tape
MVS Jan 2005.p65 - CBT Tape
MVS Jan 2005.p65 - CBT Tape
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
indicates whether the child process should run as a<br />
subtask within the parent process address space or<br />
whether the child process should run in its own address<br />
space. The following _BPX_SHAREAS options are<br />
supported:<br />
– NO – the child process is created in a separate<br />
address space. This is the default.<br />
– REUSE – the child process is created as a subtask in<br />
an existing task structure unless conditions exist that<br />
force the child process to initiate a new task structure.<br />
– MUST – the child process must run in the same<br />
address space as the parent or the spawn request will<br />
fail. Possible reasons for failure include:<br />
o if the set UID or set GID of the spawned program<br />
differs from the effective UID or the effective GID<br />
of the parent<br />
o the program to be run is APF authorized but the<br />
parent is not<br />
o the program to be run is unauthorized but the<br />
parent program is APF authorized<br />
o the parent process address space does not have<br />
sufficient resources.<br />
– YES – the child process will run as a subtask in the<br />
same address space as the parent unless conditions<br />
exist that force the creation of a child process address<br />
space.<br />
Spawn() initiates the requested program from its entry<br />
point address. In contrast, with fork() the child process<br />
program begins execution from the instruction following<br />
the fork() instruction (not the entry point of the program)<br />
and is always a copy of the parent process program.<br />
Spawn() can be used to execute a completely different<br />
program from that of the caller.<br />
© 2005. Reproduction prohibited. Please inform Xephon of any infringement.<br />
29