The DCAF network includes the workstations that have DCAF installed and the communications that link them.
The Example of a Distributed Console Access Facility Environment figure,
which follows, is one example of a basic DCAF environment.
The DCAF workstations communicate with the following communication protocols:
Controller A communicates directly with target E and with gateway B using switched asynchronous communication.
Controller A also communicates, via LU 6.2 over a Systems Network Architecture (SNA) network or backbone, through gateway B to the targets on the LAN. The SNA backbone represents the part of the network that connects (via switched lines, leased lines, or satellite communications) host computers, communication controllers, and other computer hardware. Any connections over an SNA backbone must go through a gateway.
Controller A communicates directly with target F via LU 6.2. For LU 6.2 communications, the physical unit type for the controller, target workstation, and DCAF gateway workstation must be configured as a type 2.1 (PU2.1).
Controller A communicates via TCP/IP through a router with LAN directory I and with target H.
Controller A communicates via IPX/SPX through a router with LAN directory K and with target J.
Controller A communicates via NetBIOS directly with LAN directory M and with targets L, N, and O on the LAN.
OS/2 target workstations on the LAN require that OS/2 Communications Manager, LAN Adapter and Protocol Support (LAPS) from NTS/2, or the LAN Server 2.0 be installed to provide the NetBIOS device drivers. In order to run DCAF with other applications that require NetBIOS services, you may need to increase the NetBIOS resources via the OS/2 Communications Manager or LAN Services.
DOS target workstations on the LAN require that a LAN support program be installed, such as the IBM LAN Support product. DCAF supports DOS target workstations on the LAN only.