6.9.3 CTCT (Channel-to-Channel emulation via TCP Connection)

6.9.3.1 Function

This is an emulated Channel-to-Channel adapter to another Hercules system. CTCT only supports IP
traffic and cannot be used to transport NJE, SNA, PVM, etc. type payloads. This may change in the
future.

6.9.3.2 Syntax

Descriptive

CTCT lport rhost rport bufsize

Diagram

Êʬ¬¬ ¬¬¬ CTCT ¬¬¬ lport ¬¬¬ rhost ¬¬¬ rport ¬¬¬ bufsize ¬¬¬¬¬¬¬¬¬¬¬ÊÍ

6.9.3.3 Parameter

devaddr

This is the device address.

CTCT

This specifies the CTCT device/protocol type.

lport

Specifies the local TCP port. This is the TCP port that Hercules will listen on for this
CTC adapter.

rhost

Specifies the remote host. This is the name or IP address of the remote host sys-
tem that Hercules is running on, not the name or IP address of the OS running
under this instance of Hercules.

rport

Specifies the remote TCP port. The rport parameter on this system must match the
lport parameter on the remote system and vice versa.

bufsize

Specifies the buffer size for the link. If this link is used for IP traffic this parameter
should be more than the MTU of the interface definition in the OS TCPIP stack.

6.9.4 Examples

Example 1:

Define 3088 CTC adapters on device addresses 0400 and 0401. The device/protocol type is CTCT
(Channel-to-Channel emulation via TCP connection). The local TCP ports on which Hercules will listen
are 30880 and 30881. The IP address of the remote host is 192.168.100.2, the remote ports are also
30880 and 30881. The buffer size for the link is 2048 KB.

0400.2 3088 CTCT 30880 192.168.100.2 30880 2048

or

0400 3088 CTCT 30880 192.168.100.2 30880 2048
0401 3088 CTCT 30881 192.168.100.2 30881 2048

6.9.5 CTCE (Enhanced Channel-to-Channel emulation via TCP
Connection)

6.9.5.1 Function

The CTCE device type will emulate a real 3088 Channel-to-Channel Adapter also for non-IP traffic, en-
hancing the CTCT capabilities. CTCE connections are also based on TCP/IP between two (or more)
Hercules instances, and requires an even-odd pair of port numbers per device side.

Only the even port numbers are to be configured; the odd numbers are just derived by adding 1 to the
configured even port numbers. The socket connection pairs cross-connect, the arrows are showing the
the send -> receive direction:

InstanceA-lport-even -> InstanceB-rport-odd
InstanceB-lport-odd <- InstanceA-rport-even

CTCE connected Hercules instances can be hosted on either Unix or Windows platforms, both sides do
not need to be the same.

6.9.5.2 Syntax

Descriptive

CTC lport raddress rport [mtu [sml]]

Diagram

Êʬ¬¬ ¬¬¬ CTC ¬¬¬ lport ¬¬¬ raddress ¬¬¬ rport ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬Ê

ʬ¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬§¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ÊÍ

mtu ¬¬¬§¬¬¬¬¬¬¬¬¬¬¬«

sml