Hi Paul

I understand not wanting, perhaps, to install over an existing installation - that, however, is what is recommended - the GettingStarted.html has the following in the section on updating an existing installation -

"To update your existing installation, follow the steps in section 5.0 Installation <file:///C:/Users/hambevm/Desktop/IBM%20ACS/IBMiAccess_v1r1/Documentation/GettingStarted_en.html#5.0> and overlay your existing installed files."

That is followed by this statement -

"Some administrators may choose to install the updated version in a new location. If you use this method, make sure you delete the old installation after you have verified the new installation."

So choosing the default location is, in fact, never the thing to do, seems to me. I think I never got the drift that you had put 1.1.4 in the default vs the "original" location - sorry about that.

So a strategy might be good to have, for verifying a new version - one person tests it in a different location - maybe in a network share scenario - then once satisfied, distribute to all, or have a network share everyone uses that gets the update after testing.

I guess for my own use I'm OK with overlaying things, as directed. If I need to go back, I always have the older ZIP file around.

The HOD file association matter is an interesting one - thanks for the resolution.


On 8/12/2015 10:17 AM, Steinmetz, Paul wrote:

First of all, thanks for all the ACS tips and updates.

A few ACS / ESS install / upgrade questions and issues.

1) The file/folder name is confusing/misleading.
Last year, August 2014, I downloaded and extracted my initial version of ACS from ESS.
Folder name was IBM_i_Access_Client_Solutions_LCD8_2010_05
This was Version 1.1.3 Build 4260 June 24, 2014

Last Friday, 8/7/2015, I downloaded and extracted the latest version of ACS from ESS.
Folder name was IBM_i_Access_Client_Solutions_LCD8_2010_09
This was Version 1.1.4 Build 5290 July 13, 2015.

The folder names are misleading.
Seeing 2010_05 and 2010_09 leads one to think this is an old version and not current.
Could the folder name be changed to coincide with the build date, 2015_07.

2) Because I extracted to the default folder, this resulted in two versions of ACS on my PC.
My HOD session desktop shortcut was still pointing to the old Version 1.1.3 Build 4260 June 24, 2014, not the new Version 1.1.4 Build 5290 July 13, 2015.
After days of frustration, not finding how to resolve this, I finally opened up a PMR.
IBM support did an IBM Assist on Site to better understand and see the issue.
It was determined that we had to re do the "File Associations".
I was not clear and how and where to accomplish this.
First, per IBM, we launched ACS from the acsbundle.jar file.
However, "File Associations" did not appear.
Closed ACS, relaunched from acslaunch_win-64.exe.
Tools tab, File Associations now appeared.
.hod was already selected, ok.
MSGGEN002 - The function completed successfully.
Retested the hod shortcut, but still launching the old version.

To resolve this issue.
Closed ACS, relaunched from acslaunch_win-64.exe.
Tools tab, File Associations.
Unchecked .hod, ok.
MSGGEN002 - The function completed successfully.
Tools tab, File Associations.
Rechecked .hod, ok.
MS GGEN002 - The function completed successfully.
Retested the hod shortcut, now launching the new, current version.

Reviewing and discussing the issue with support, had I not used the default folder name, and extracted to the same folder, could have avoided this.
However, I was not comfortable on extracting to the same folder, (what if something went wrong or new version was not working)

More detailed ACS upgrade instructions needed explaining:
1) Extraction default Folder issue
2) hod File Association issues and instructions.


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].