Re: upgrade SC1 - OpenSSH

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hi Chris,

Yeah, I saw your message stating that it's not in the GO LICPGM, option 
10...  it arrived in my Inbox about 30 seconds after I clicked "send" :-)

Anyway:

1) The symlink will only work if the Alliance product does not use any 
new features that were added in 3.8.1p1. So you might be able to get by 
in a pinch (which sounds like what you're doing), but this isn't a great 
solution.

2) I wonder why Alliance is hard-coding the directory name to begin 
with?  Seems like a poor design choice.  Why not use the one IBM 
intended people to use (the link in /QopenSys/usr/bin) so that when 
OpenSSH is upgraded, you automatically get the current installed 
version?   Or, better yet, use PATH -- that's what it's for.

But, #2 is, of course, probably not something you can control...

-SK



On 11/29/2012 11:59 AM, Chris Bipes wrote:
> Not installed at all.  A carry over from an upgrade.  New hardware with the OS loaded, then restored the old system in a move from a 520 to a 720.  How I missed this piece I do not know.  I upgraded the 520 to 6.1 prior to the hardware upgrade.  Anyhow I created a symbolic link and all is working.  (Ok that's cheating.)
>
> I have been in contact with Alliance tech support and they wanted me to upgrade their software from 5.2 to 5.3.  Now I get to do their upgrade, Install the SC1 and patch it all up but with the deadline being next Wednesday, the symbolic link has the application working today.