cicsterm or cicsprnt fails to connect to the CICS server

The Client daemon can connect to the server, but cicsterm is unable to connect.

Symptom

The cicscli -s=servername command connects successfully, but cicsterm -s=servername or cicsprnt -s=servername command does not connect.

Probable cause

The CTIN transaction might not be defined or sign-on capable terminals are not supported by the CICS® server. Another possibility is that the CICS server does not have 3270 terminal support over TCP/IP.

Action

  1. Check that the CTIN transaction is defined on the server.
  2. Issue the cicsterm -s=servername -a or cicsprnt -s=servername -a command to install a terminal that is not sign-on capable. If this is successful, the server probably does not support sign-on capable terminals. cicsterm or cicsprnt attempts to install a sign-on capable terminal by default.
  3. Check that EPI is supported over the server connection being used.

For more information see cicsterm options and cicsprnt options.


Concept Concept

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/start_cicsterm2.html