>Which makes "sense" if you think about what the "oedit" command actually
>does. Think of the OMVS command as doing a fork() to start a new UNIX
>process. Which is what it does.
Nope. OMVS (by default) starts the shell process as a local process (using
attach_exec, I believe), i.e. the
>>If you understand how UNIX works, this is quite sensible. See how the ISPF
>>interface to USS works.
>>
>Or fails to work. If under OMVS the user issues
>
>su other
>oedit file
>
>... the ISPF editor is invoked not under the other user ID, but under the ID
>that issued the OMVS command.
I
>>echo "id" > /tmp/sucommandfile
>>su < /tmp/sucommandfile
>>
>>This will show uid=0, because it is the sub shell (uid=0), which is reading
>>from /tmp/sucommandfile as if it >was stdin, and execute the commands found
>>therein.
>>
>Did this work for you on z/OS? Looking for alternatives on a
