Yes, it uses getpwuid() to get your default shell.

But you can run any program with whatever options instead by using PARM=
see:  https://dovetail.com/docs/cozbatch/ref.html



Kirk Wolf
Dovetailed Technologies
http://dovetail.com

On Tue, Oct 17, 2017 at 10:32 PM, David Crayford <[email protected]>
wrote:

> On 18/10/2017 6:10 AM, Kirk Wolf wrote:
>
>> Yes, it works with bash, but the limitation with bash is that commands are
>> never local-spawned.   Therefore, you can't use DDs.
>>
>
> Yes, and that's an issue for me. I want to use bash in my shell but
> /bin/sh in COZBATCH so I can use DDnames. Are you getting the login shell
> using getpwuid()?
> Is there anyway to tell COZBATCH not to use the login shell? I can't see
> anything in the reference so I suspect not.
>
>
> Kirk Wolf
>> Dovetailed Technologies
>> http://dovetail.com
>>
>> On Tue, Oct 17, 2017 at 3:06 AM, David Crayford <[email protected]>
>> wrote:
>>
>> You probably already know this but COZBATCH works just fine with bash. I
>>> changed my default shell to bash and it works a treat.
>>>
>>> CoZBatch[N]: Copyright (C) 2005-2013 Dovetailed Technologies LLC. All
>>> rights reserved.
>>> CoZBatch[N]: version 3.1.0 2015-05-01
>>> CoZBatch[I]: executing progname=login-shell="-/usr/local/bin/bash"
>>>
>>>
>>> On 16/10/2017 10:46 PM, Kirk Wolf wrote:
>>>
>>> PS> CozBatch is 10 years old this year.   Its free to download and use
>>>> under our Community License.
>>>>
>>>> That's a good excuse for a party! :)
>>>
>>>
>>>
>>> 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
>>>>
>>>> ----------------------------------------------------------------------
>>> 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
>>
>
> ----------------------------------------------------------------------
> 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

Reply via email to