Google
 

Trailing-Edge - PDP-10 Archives - BB-R598A-RM_1983 - swskit-v3/nvt/virtual-terminal.mem
There is 1 other file named virtual-terminal.mem in the archive. Click here to see a list.
     This document describes the virtual terminal hacks available from
HOSS. There are  some basic ground  rules for the  use of these hacks. 
1) All virtual terminal support programs which are not mentioned in an
SPR are unsupported. 2) All unsupported software is to be presented to
customers as unsupported  software. i.e. sell PL90 with it or describe
its unsupported nature in writing. NEVER describe unsupported software
as a part of a DECnet product.

     Virtual terminal support software can be listed a number of ways:

	1) Supported or unsupported
	2) Protocols it supports
	3) Provides pseudo routing in phase II networks or not
		(poor man's routing)

     Many virtual terminal programs can be written by making different
choices from  the above list.  Following are  the programs provided on 
this tape.  Remember  that a virtual  terminal facility requires  both
active and  passive programs, and that  the protocol used  must be the
same for both programs.

1) TOPS20 ---> TOPS20.    This is  supported for DECnet-20  V2.1.  The
active task  is SETHOST.EXE, the  passive task is MCBNRT.  Both are on
the DECnet-20 V2.1 Distribution tape.

2) TOPS20 ---> VAX, RSTS, IAS, RSX11M, RT.  The active task on the -20
is HOST.EXE.  It is  provided on both  the TOPS-20 Tools  tape and the
DECnet-20 V2.1 SWSKIT.  It supports poor man's routing.

3) RSTS/IAS ---> TOPS20.  The  RSTS program  NET20.BAS, provides  both 
the active  and passive  tasks for  virtual terminal support. It  also
does poor man's routing.  To install it, get it with  the OLD command,
then merge the RSTS DECnet routines.  This is unsupported  code, based
on the supported NCT utility. It uses NRT20 protocol  and communicates
with  HOST.EXE on the -20.  The passive task on the -20 is NRTSRV.

4) RSX11M ---> TOPS20.  The RSX11M  Macro program 11HOST.MAC, provides
the active task  to communicate to the -20.  This is  unsupported code
which uses the NRT20 protocol. It should work on both Phase II and III
11M systems.

5) VMS ---> TOPS20.  The  VMS command SET HOST nodename allows  you to 
communicate to the -20.  The -20 program NRTSRV (or MCBNRT for Rel 5.0
KL model B sites) provides the passive task.

6) TOPS10 <---> TOPS20.  Active and  passive tasks  are  available  to
communicate over the TOPS-10 DECnet Compatible Port (DCP) with the -20.  
They are available on the DCP tape available through Software Services.