The "acslaunch_win-32.exe" can authenticate the user for accessing the "greenscreen" and other components of the base Access Client Solutions install. However it can't authenticate users for ODBC connections. You do need to use the CWBLOGON for that. Review the post above by Michael Swenson, he provided a lot of key detail.
Original Message:
Sent: Wed November 01, 2023 03:11 AM
From: Roberto Colonnese
Subject: Automatic Logon
Hi, unfortunately I'm not a computer scientist, I do graphics, where I work I use As400 to extract food products to make advertising posters, the CWBLOGON no longer works, now I'm using another command
C:\Users\administrative4\IBM\ClientSolutions\Start_Programs\Windows_i386-32\acslaunch_win-32.exe /PLUGIN=logon /AUTH /SYSTEM=xxx.xxx.xxx.xxx /USERID=xxxxx /PASSWORD=xxxxx /GUI=2
for automatic access to Iseries without authenticating, but what I really can't automate are external programs like access or excel, I have to enter the password at least once, the user keeps it memorized.
I am attaching a screen of the information about the iseries that I use where there is also the java version.
Thank you.

------------------------------
Roberto Colonnese
Marketing
Colonialsud
Arzano
Original Message:
Sent: Wed November 01, 2023 01:56 AM
From: Satid Singkorapoom
Subject: Automatic Logon
Two more points: If you can still run CWBLOGON, it means you still have the old IBM i Access for Windows as well as IBM i ACS in your Windows PC and this may be the cause of the problem you are encountering. You should uninstall IBM i Access for Windows.
What JRE in Windows are you using? If it is not IBM Semeru 17 JRE for Windows, I suggest you switch to this JRE and try your .bat file again.
To install IBM Semeru 17 JRE for Windows, download its MSI file and run it for installation. Then you set Windows environment variable named JAVA_HOME to the installed folder path of Semeru JRE such as JAVA_HOME=C:\Program Files\Semeru\jre-17.0.8.101-openj9. After this, you should also make sure you see this Env Var from Windows SET command.
------------------------------
Chance favors only the prepared mind.
-- Louis Pasteur
------------------------------
Satid S.
Original Message:
Sent: Tue October 31, 2023 04:19 AM
From: Roberto Colonnese
Subject: Automatic Logon
------------------------------
Roberto Colonnese
Marketing
Colonialsud
Arzano
Original Message:
Sent: Tue October 31, 2023 04:18 AM
From: Roberto Colonnese
Subject: Automatic Logon
HI,
we certainly use odbc to interface the As400 with Access and Excel, this problem arose when I updated to the latest version, before I had Workstation 6.0 and I didn't have this problem, I ran a .bat when starting windows (which I attach) with this .bat managed to automatically insert the credentials and everything worked both on Iseries and on Access and Excel.
------------------------------
Roberto Colonnese
Marketing
Colonialsud
Arzano
Original Message:
Sent: Tue October 31, 2023 04:09 AM
From: Dominique Gayte
Subject: Automatic Logon
I Roberto,
Are you using an ODBC/OLE DB connection for Excel and Access? If this is the case, you should check if you have not forced the dialog box to be displayed in the configuration of ODBC Driver.
If you have a Active Directory, the most effective way is to set up an EIM-based SSO.
------------------------------
Dominique Gayte
Original Message:
Sent: Tue October 31, 2023 03:17 AM
From: Roberto Colonnese
Subject: Automatic Logon
Hello everyone,
I have an automatic logon problem, even though I think I have set the .bat file that I start to run automatically when I start a program you access or excel asks me to enter the password, can anyone help me understand where I'm wrong? I'll add some screenshots, thanks.
------------------------------
Roberto Colonnese
Marketing
Colonialsud
Arzano
Original Message:
Sent: Mon October 30, 2023 06:22 AM
From: Roberto Colonnese
Subject: Automatic Logon
------------------------------
Roberto Colonnese
------------------------------