Starting clients and terminals

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

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.

An XTERM session stops working after the CICS Universal Client
is upgraded

The problem is caused because some files might have changed location between versions. The solution is to open a new XTERM window.