>>> 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 local spawn you have to use one of the
>> workarounds documented in BPX1SPN
 >
>What workaround?


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.


--
Peter Hunkeler



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to