Yes.

A script submits a job to a batch queue:
qprt -P$myqueue -C -T "$PROGID" qbatchexec

The script that submits the above job determines the
queue name (in $myqueue variable) that the job will run under, export all
variables
needed by qbatchexec (another script), including LIBPATH.

When qbatchexec is under the control of the batch queue, I echo $LIBPATH
at the beginning of the script. AND LIBPATH is empty!

This is the scenario.

Thanks for any input on this.
"Laurenz Albe" <invite@spam.to.invalid> wrote in message
news:1129533644.553808@proxy.dienste.wien.at...
> SBC Global News <someone@microsoft.com> wrote:
>> We are currently testing out 5.3L.
>>
>> I am finding a few differences from 4.3+.
>>
>> One is LIBPATH is not passed on to the
>> job when submitting it in the batch queue.
>>
>> How do I disable this behavior? Or shall
>> I say how can I pass on to the child process
>> the LIBPATH variable?
>
> Sorry to give such a trivial answer, but your description seems to
> suggest that you didn't export the environment variable.
>
> Does the problem go away if you type
> export LIBPATH
> before invoking the batch job?
>
> Yours,
> Laurenz Albe