As I said, its documented in the Assembler Services guide. (under "Usage notes for spawn"). I'll admit that I was trying to let you have a nice "Ah Ha" moment yourselves when you see how IBM hid it. But I guess I'll ruin it for you :-)
- read carefully the notes regarding local spawning and "sticky bit" files. Hint: compare 9a) _BPX_SHAREAS=YES and 9b) _BPX_SHAREAS=MUST. - a new (better?) way is to use INHEMUSTBELOCAL Also: you can use the C library spawnp() or __spawnp2() to get at all of this. What you find using z/OS Unix is that the most complete documentation is in the Assembler Services guide. The C-library doc is spotty. Kirk Wolf Dovetailed Technologies http://dovetail.com PS> CozBatch is 10 years old this year. Its free to download and use under our Community License. On Mon, Oct 16, 2017 at 12:19 AM, David Crayford <[email protected]> wrote: > On 15/10/2017 10:57 PM, Kirk Wolf 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 >> sticky bit on, so to get a local spawn you have to use one of the >> workarounds documented in BPX1SPN >> > > What workaround? > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
