TN3270

The TN3270 communication point connects to a remote TN3270 server listening for connections on the port specified in the Remote Host and Remote Point configuration properties. The optional properties Local Address and Local Port can be used to force the communication point to connect using a specific interface and local TCP/IP port number.

Generally the TN3270 server is a Microsoft® SNA server or IBM communications server. The Remote Port for these systems is generally 23. The TN3270 communication point also needs to know which Logical Unit (LU), also known as the terminal ID, to connect to, and the CICS logon string.

The LU is an 8 character terminal ID for the interface. The CICS logon string determines whether the connection is to the Test or Production system. This string can simply be the CICS region to connect to or be of the form:

LOGON APPLID=CICS????

Supported Operational Modes: All.

Configuration Properties

Property	Description
Remote Host	The hostname/IP address of the TN3270 server to which you want to connect.
Remote Port	The port number on remote host to connect to. This should generally be set to `23`.
Local Address	The hostname/IP address of the local interface to bind the socket connection to (all interfaces if empty).
Local Port	The port number to bind the local socket to.
Use SSL	Options: `True`, `False`. Default: `False` If this property is set to `True`, secure socket layer is be used for this connection and all messages will be encrypted. It is recommended that SSL be enabled for TN3270 communication points whenever it is supported by the remote server. Refer to TLS/SSL Support in Rhapsody for details.
SSL Protocol Mode	Refer to SSL Protocol Versions for details.
SSL Cipher Suites	Refer to SSL Cipher Suites for details.
Use SSL Client Mode	Options: `True`, `False`. Default: `True` If this property is set to `True`, SSL client mode will be enabled. Note that this is NOT the same as TLS client authentication. TLS client authentication is supported by configuring one or more private keys in the Secure Keys configuration property.
Secure Keys	Identifies the private keys used for authenticating Rhapsody's end of the SSL connection. When configured with a private key, the SSL client supports SSL client authentication if requested by the SSL server. Refer to Client Authentication for details.
Trusted Certificates	Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is not configured with the SSL server's certificate, then this SSL client operates in anonymous server authentication mode. It is highly recommended that the server's certificate always be provided here to allow server authentication to be performed. Refer to Server Authentication for details.
CICS Logon String	The string to send to the mainframe once connected to the LU.
LU Name	The name of the 'Logical Unit' to connect to. If you do not enter the LU Name, the Tn3270 server automatically chooses one for you.
Log Connections	Options: `True`, `False`. Default: `False` If `True`, establishing and dropping of all connections to the communication point are logged to the log file specified in the Connection Log File property. Use of this logging facility will slow the communication point down considerably. It is intended for debugging purposes and should not generally be used.
Log Data	Options: `True`, `False`. Default: `False` If `True`, all data passed over the connections of the communication point is logged to the log file. This is potentially a lot of data.
Log Data As Hex	Options: `True`, `False`. Default: `False`. If `True`, the hexadecimal representation of the data is logged to the log file. If `False`, the data is logged exactly as it is as it passes over the communication point connection.
Connection Log File	The full file name (path and file name) of the file on the server to which you want to log the information.
Extra Information	Options: `None`, `Log Time`. Default: `Log Time` Indicates if timestamps should be written to the log with each event. If set to `Log Time`, the timestamps are logged with each event.

Refer to Out->In and In->Out Properties for general details on a communication point's Bidirectional, In->Out and Out->In modes.