Re: Changing an existing PATH as seen in QSHELL

It is a release of an application that has no *set* time schedule. Sometimes it can be a few months (weeks if patching) and sometimes over a year. So I need to install the new code, change the path to include it and then do some testing. Being able to quickly change the path is the important part. So I think I have ended up with the best overall solution.

Thanks

Pete


Roger Harman wrote:

If you have a set algorithm for the changes, just script it in .profile.
Then, you don't have to search the archives.

I use AJS to remind people about scheduled changes and setups for new
fiscal years, etc.

Pete@xxxxxxxxxx 12/15/2009 5:03:10 PM >>>

I think Scott has the situation correct. The .profile being loaded last

was overwriting the changes I made to the environment variables. So I'll pulled the path from the .profile. This is the approach of least surprise for me. The environment variable is where I would normally
look.

However, knowing that the .profile is loaded last would allow me to play

with the PATH if I needed to. That or just changing the job environment

variable. In any case, I think I am clear on what is going on and hopefully will find this in the archives when I look to make the change again, a year or so from now :-)

Pete

Dennis Lovelady wrote:

The application I was use changes about every 6 months to a year so I
need to update the path so the newer executables can be found. If
there

is a better way to handle changes to path so that the executables can
be
found when run in QShell, let me know.

If you tell me (us) the old and new value of your variable, and your
schedule for the change, I'm confident I (we) can come up with a
once-and-for-all solution.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Life would be so much easier if we could just look at the source code.