Problem solve Get help with specific problems with your technologies, process and projects.

Client Access Express password cache

Stop that darn pop-up window from appearing when you're trying to connect to Client Access.

You Can View User Feedback To This Tip

Don't you hate having the connection window pop up every day when you connect to the Client Access screen, and then have to log in to the display?

IBM has provided the ability for Windows NT/2000/XP computers to do what was available for Windows 98 -- the ability to remember the connection password. You can put this into a batch file in the startup, but I prefer to put it into a registry entry, so it will run prior to any startup group program (in case you have your display session in your startup). The best thing to do is to create a generic ID on the AS400/iSeries/i5, and use that password only for connections. I've enclosed the registry entry that I've used as an example here:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRun] "Client Access PW Cache"=""C:Program FilesIBMClient AccessCWBLOGON.EXE" iseries /u userid /p password"

The easiest way to implement this:

On a PC, create a text key using REGEDIT named "Client Access PW Cache."

Double Click on the key to enter the value (including the quote marks.)

"C:Program FilesIBMClient
AccessCWBLOGON.EXE" iseries /u userid /p password

Where iSeries is the name (or IP address of the iSeries), you want to connect to the user ID that is a generic user ID and password.

Export the HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRun

Edit the .REG file created and remove the entries other than the "Client Access PW Cache" information.

On all machines that you want to include this onto, you can double-click the .REG file created here and allow it to update the registry.

I got pointed to this information from IBM support. For more information in Client Access, click on the help, and search for CWBLOGON.


  • This is not a well-recommended method of connecting users to an iSeries. The problem with this is that all other functions and programs that access the iSeries do so with the authorities of the single user profile. This can bypass all object authority settings, and it frustrates auditing because everything happens under a single user ID.

    A better method is to use the "Sign-on information" on the Connections tab of the system's Properties window from iSeries Navigator. You can set it to "Use the Windows user ID" or Kerberos to avoid multiple sign-on windows, and these options protect the integrity of the iSeries' authority structure. IBM only discusses this method for use on a server that needs to perform unattended operations (in which case the machine should be in a secure server room, not available for general user logon.) The "Common user ID" myth stems from the installation manual for Client Access in 1995 where the term "common user ID" referred to a user ID used by a person among multiple machines, not for a single user ID used by multiple people.— Jeffrey Gardner

    More on this topic

    The Best Web Links: Tips, tutorials and more.

    Visit the ITKnowledge Exchange and get answers to your systems management questions fast.

    Read this Featured Topic: Take control of your iSeries. 

    Ask the Experts yourself: Our systems management gurus are waiting to answer your technical questions.


Dig Deeper on Performance