Browse Prior Art Database

Remote Channel To Channel Protocol

IP.com Disclosure Number: IPCOM000122486D
Original Publication Date: 1991-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 3 page(s) / 75K

Publishing Venue

IBM

Related People

Kawashima, K: AUTHOR

Abstract

Described herein is a remote channel to channel protocol which provides an unlimited connection capability for ACF-VTAM multiple channel to channel sessions through a high speed (greater than 6 megabits per second) communication line.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 56% of the total text.

Remote Channel To Channel Protocol

      Described herein is a remote channel to channel protocol
which provides an unlimited connection capability for ACF-VTAM
multiple channel to channel sessions through a high speed (greater
than 6 megabits per second) communication line.

      ACF-VTAM provides multiple channel-to-channel session connect
function between two host processors using channel to channel
equipment, but the distance between these two host processors can not
be unlimited for the following reason.
-Channel interface has the limitation of cable length between the
host processor and the attached control unit (CTC equipment in this
case), that is, 400 feet.  Therefore, the maximum distance between
two host processors using CTC is 800 feet.

      In order to solve the problem described above, RCTC (Remote
Channel-to-Channel) protocol has the following function.
-The RCTC control unit is attached to each host processor, and two
RCTC control units are connected through high speed lines to each
other.  The configuration sample is shown in Figure 1.
-RCTC control unit provides multiple sessions between two host pro
cessors.  That is, ACF-VTAM can establish more than one CTC session
between two host processors by using one pair of RCTC control units.
Each CTC session is assigned an independent subchannel address.

      RCTC receives data from host processors and responds with
accept status, then sends it to remote-side RCTC. Remote-side RCTC
receive...