>I just checked. AOPBATCH is on my z/OS 1.12 system in AOP.AAOPMOD1, which
is a "distribution" library. We don't license whatever the product is
either. So it is shipped. I didn't check to see if it would actually run.
z/OS is a package of elements and features. It used to be that features
>Doesn't exec(), like fork(), create a new execution environment, discarding
DDNAME allocations?
You're absolutely right. I didn't think of DDs, which is the whole purpose of
the local spawn in this context. Shame on me.
--
Peter Hunkeler
On Mon, Oct 16, 2017 at 12:27 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 16 Oct 2017 08:09:34 +0200, Peter Hunkeler wrote:
> >
> >My thoughts have been to first spawn() to a glue routine to get the local
> process and then to exec() to /bin/sh. Another
On Mon, 16 Oct 2017 08:09:34 +0200, Peter Hunkeler wrote:
>
>My thoughts have been to first spawn() to a glue routine to get the local
>process and then to exec() to /bin/sh. Another way be to invoke a shell script
>making sure _BPX_SPAWN_SCRIPT=YES is present.
>
Doesn't exec(), like fork(),
On 16/10/2017 2:09 PM, Peter Hunkeler wrote:
I guess COZBATCH has left out /bin/login, and exec()s to the shell to
avoid the above restrictions.
That's almost right, but COZBATCH uses spawn. By default it will run the
user's shell as a "login" shell. The tricky part is that /bin/sh has a
>>> I guess COZBATCH has left out /bin/login, and exec()s to the shell to
>>> avoid the above restrictions.
>>>
>>> That's almost right, but COZBATCH uses spawn. By default it will run the
>> user's shell as a "login" shell. The tricky part is that /bin/sh has a
>> sticky bit on, so to get a
>I have a question ...if a program is running in MVS as a STC...and wants to
>dub a UNIX process where do I find how this is explained and better yet an
>example so I can see it ?
Basically, you don't have to care. When a task (which is not yet dubbed) does
the first kernel call, i.e. it call
>The shell may be forking or doing something else.
It's not the shell alone. Primarily, it is BPXBATCH / BPXBATSL invoking
/bin/login to start the shell (when PARM='SH' is used). /bin/login is a
setuid program (target is uid=0) and z/OS UNIX does not allow locally spawned()
processes in
