RE: 7Zip Problem (from rpg400 list)

["Dennis Lovelady" <iseries@xxxxxxxxxxxx>]

> What you really want is /QOpenSys/usr/local pointing to /usr/local, or
> vice versa.  It really doesn't matter which way the link exists as long
> as one points to the other.  This allows PASE utilities to be used from
> qshell and vice versa.  PASE utilities are looking for something in
> /QOpenSys/usr/local, and qshell utilities are typically looking for
> something in /usr/local.

No, that is apparently what you want and maybe what Scott wants.  It's not
what I want and I'll argue that it's not what's best.  The reason it's not
what I want is that I don't want things in either environment that are not
valid.  For example, the zip (not 7-Zip) utility intended for AIX can be
installed in PASE but will not execute (last I tried) in QSH environment.
If I tie /usr/local together for the two environments, then in effect I have
a zip program in /usr/local/bin that won't run in my QSH environment.  If
later I decide to put in another ZIP executable just for QSH, then I don't
have a way to do it without messing up the PASE environment's zip.

In my PASE my PATH does not include /usr/local/bin; it includes
/QOpenSys/usr/local/bin instead, and the two are not linked.  I don't
install PASE stuff into /usr/local/anything; that stuff goes under the
/QOpenSys filesystem as IBM intended.  If there are scripts and so on that I
need to share between the environments, then I link at the file level, like
this:

    ln -fs /usr/local/bin/my-cool-script /QOpenSys/usr/local/bin

It just isn't that hard to do it right.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I don't want to achieve immortality through my work, I want to achieve it
through not dying."
        -- Woody Allen