From: Scott Klement <opensource@xxxxxxxxxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Date: 02/27/2017 11:37 PM
Subject: Re: [IBMiOSS] /QOpenSys/QOpenSys?
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>
In my experience this comes up very often with 3rd party software that
has been compiled for AIX. The software has hard-coded paths of "/usr",
"/usr/lib", "/usr/bin" and the like -- and frequently its hard-coded
into the program.
The workaround, of course, is to use chroot. But now if you try to use
it in conjunction with software that expects /QOpenSys (such as a script
with a bang-path starting with /QOpenSys) the /QOpenSys causes it to
fail. Thus the symlink, which solves the problem.
In a perfect world, none of this stuff would be hard-coded... but
alas, the world is not perfect.
Since the symlink takes up almost no DASD, its worth having it there.