When Access Client Solutions (ACS) is discussed, most people think of the Java client installed on their workstation, but what some may not know is that ACS is also installed on the IBM i system. This is what the “Inner ACS” in the title refers to - an “internal” ACS on the IBM i server. And like IBM i and other software installed on the system, it is important to keep this software component updated.
In this post I will describe why ACS is on the server and will show tips for how to keep it updated on IBM i. Since ACS has just been updated to version 1.1.9.8 (as mentioned in my previous post IBM i 7.6 has been announced), this is a good time to discuss this subject.
Why is ACS on the server? #
You may wonder why ACS is installed on the server, when it’s a client and used on your workstation. Well, ACS is a Java program and Java runs on all platforms, including IBM i, so IBM used this to install a copy of ACS in IBM i and have it run on the server. ACS is installed in this path: /QIBM/proddata/Access/ACS/Base/acsbundle.jar.
Having ACS on IBM i allows
- IBM i Services to generate Excel files from SQL data
- the IBM i server to act as a software repository for updating ACS on the workstations
ACS is used by SQL #
Yes, ACS on IBM i is the foundation for the SYSTOOLS.GENERATE_SPREADSHEET SQL scalar function. The SQL function uses the cldownload function of ACS to convert the output from the query to a spreadsheet file in IFS. This is more advanced than the CL commands CPYTOIMPF and CPYTOSTMF, since it can generate different kinds of file types, comma-separated values (csv), OpenDocument spreadsheet (ods), text (txt), the popular pre-2007 Excel spreadsheet (xls) and the even more popular current Excel spreadsheet (xlsx). So it is ACS that allows IBM i to generate spreadsheet files (which can then be distributed, e.g. by email or file transfer), and without ACS no spreadsheets.
IBM i as a software repository for ACS #
There are many ways to upgrade ACS on a workstation, and one is to use the Check for new version function in the Help menu in the ACS main control panel:
This will make ACS check for a new version on the specified location, as defined in the Edit > Preferences:
You can select your IBM i server here, and ACS will use this server when checking for new ACS versions. If no system is selected, ACS will use the IBM repository on the internet. If a new version of ACS is found, ACS will offer to download and install the new version to the local workstation. By using your IBM i as an ACS update source, you control when a new version will be offered to your users. Only when the ACS in IBM i is updated, will the users be offered this new version.
How do I update ACS on IBM i? #
ACS is updated using the normal PTF framework. When ACS is available in a new version, IBM will generate a PTF for that version for each supported IBM i version. You can find the latest PTF identifiers in this link on IBM Support. Don’t be confused of the program number 5733XJ1 on the page - the PTF will be for IBM i, i.e. 5770SS1.
This is the PTF identifiers for ACS 1.1.9.8, at the time of this writing:
Base package PTFs last updated April 2025 version 1.1.9.8
5770SS1 V7R3M0 SJ04931
5770SS1 V7R4M0 SJ04932
5770SS1 V7R5M0 SJ04933
5770SS1 V7R6M0 SJ04934
The next available update is planned for August 2025
You simply order, download and install the PTF for your version of IBM i - and ACS on the server will have been updated. Very easy and simple, only one PTF.
Also included in Db2 PTF group #
If you’re lazy, as most of us are, you can wait for IBM to update the Db2 for IBM i PTF group and install this collection of PTFs. This PTF group is vital to IBM i and include ACS updates and RPG updates on top of the Db2 and SQL updates you would normally expect from the name of the PTF group. Having the ACS PTF in the Db2 for IBM i PTF group is a logical consequence of the fact that the SYSTOOLS.GENERATE_SPREADSHEET SQL scalar function relies on ACS, so ACS must be updated when SQL is updated.
But it’s your choice, when you want to have ACS on IBM i updated. You either do it yourself or let IBM do it for you. Both options are fine, but I personally prefer to do it myself, since I can then control the user experience and timing. My policy is to install and test any new ACS version on my own workstation and verify there are no issues with it (which I haven’t found so far, ACS is a rock-solid product), and after some time and smoketests I get the PTF and install it on the IBM i partition used for the user updates. This way I control when the users will have the new ACS version offered as an update.
I hope you now have a full understanding of why ACS is on the IBM i server and how you can update it yourself. Feel free to reach out to me, if you have any questions.
Reply by Email