Re: Weird problems with Qp2RunPase

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hi Charles,

> Question: what about the environment variables? I assume that if I'm
> getting the PATH, I'm getting any other PASE environment variables
> that would be set if I had done a CALL QP2TERM to get the interactive
> shell.

Yes, you should be getting the environment variables.

> How about if I pass an extra, environ(1) =
> 'PASE_SYSCALL_NOSIGILL=plock=0' + x'00';
> In my call to the shell, I assume that will still exist when gpg gets
> called.

When QP2TERM starts up, it takes the normal ILE environment variables 
and copies them into the environment.  Then, it adds it's own 
environment variables to the environment, so that all of these variables 
are available to PASE programs/scripts. Then it starts a shell, which 
may add it's own, etc, etc.  The only time there should be a conflict is 
if two programs try to set the same variable for some reason.

With Qp2RunPase(), I believe that it uses the environ parameter instead 
of taking the ILE environment variables, but otherwise, it works the 
same way.

As a proof-of-concept, you might try something like this:

           parms(1) = '/QOpenSys/usr/bin/-sh' + x'00';
           parms(2) = '-c' + x'00';
           parms(3) = 'env' + x'00';

The "env" program will print out all of the environment variables to 
stdout.  Then you can see what they're set to....   This way, you can 
experiment with setting different variables, and see what you end up 
with in PASE.