Re: Where are the updates to Access Client Solutions forWindowsposted?

Paul,

So the confusion you have run into is common for WIndows people, myself included, because we are so used to an 'Installer' It sets up reasonably well suggested directory paths and off it goes. If you update it updates into the same path so we're good to go. Then along comes this much more Mac/Linux like thing that doesn't get installed so we end up using the long file name as the path such as "IBM_i_Access_Client_Solutions_LCD8_2010_05" as you suggested. That isn't really the intent though, it's suppose to be a 'delivery' folder.

Once we all get our hands around the fact that there is truly only one very important bit in there, acsbundle.jar and potentially the acslaunchxx.exe files we can plan a better implementation which I have now done. (I got it wrong the first time as you!) As a consultant I have many copies of this thing on my system. In a path ../iAccess I have a folder for @Frankeni one for @shell and then one for every customer I visit frequently. When I get updates to the product I simply copy the files mentioned above into the @Frankeni folder. Upgrade done! then I test to be sure it's OK for me. Then I copy it into @Shell and all the customer directories. Takes maybe 15 seconds to drag and drop. When I need to set up a new customer I make a copy of @Shell which has in it my keyboard layout and One system configured but my preferences for copy/past and to use tabs etc. Finally I add that customer's machine(s) to that new environment.

Because this thing isn't installed I can run multiple copies which is VERY cool and with tabs enable the sessions are grouped together that way.

So I think you are correct that perhaps what IBM needs are some scenarios for installation to help the windows folks 'get it'.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

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

Tim,

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)

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

Paul