RE: getenv/putenv APIs

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Mike Cunningham
>
> Very cool!!! I guess the documentation I found is out of date. It had said
> that environment variables are not copied on a submitted job.
>
> From: Crispin
>
> Mike,
>
> I've been looking at this for exactly the same reason. On the SBMJOB
> command, have a look at the CPYENVVAR parameter. It will allow the
> variables to be copied.
>
> Crispin.

My only caveat on named properties vs. parameters is that you probably want
from the very beginning to have a good naming convention in place that
avoids collisions.  It's a real pain when you have two programs in your
stream that use the same property name but need different values in it.
Printed report options are typical; one report needs two copies, the other
needs one.  Both have a property "COPIES=".  How do you specify it?  Simple
prefixing is typically the way to get around this, even though it leads to
slightly more cumbersome property strings.

Joe