Starting clients and terminals

The following are solutions to problems that can occur when starting clients and terminals:

Users without administrator privileges cannot communicate with the Client daemon on Windows® 2000 Service pack 4

When users issue a cicscli command they receive error message CCL8024E. Service pack 4 introduced a new user right "Impersonate a client after authentication". To allow users to issue cicscli commands they must be granted this user right. To give users the right, do the following:
  1. Click Start -> Programs -> Administrative Tools -> Local Security Policy
  2. In the Local Security Policy tool, expand Local Policies and then select User Rights Assignment
  3. In the right pane, double click Impersonate a client after authentication
  4. Click Add, and then select the users who need to use the CICS® Universal Client
  5. Click OK twice to return to the main Local Security Policy window.
  6. Close the Local Security Policy application.

A cicsterm request has gone to the wrong server

If you do not specify the -s=servername option on the cicsterm command, the Client daemon sends a cicsterm request to either of: The servername should be as specified in the configuration file.

Problems loading protocol drivers

The message "Cannot load protocol driver" in the cicscli.log file means that you are trying to use a protocol driver that does not exist. Check your configuration file file to make sure that the driver name is correct, and is supported in this release.

The Client daemon can connect to the server, but cicsterm cannot

In other words, cicscli -s=servername connects successfully, but cicsterm -s=servername does not. Check the following:

CICS servers require APAR fixes to support terminal sign-on capability; see Supported software. Refer to the CICS Universal Client README file for the latest details and check the PTFs for the CICS servers.

See APARs and fixes for general information about APARs.