From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  6-DEC-1989 14:16
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Transmit timer

Message-Id:  <8912061903.AA29930@crdgw1.ge.com>
Received: From ICDC.LLNL.GOV by CRVAX.SRI.COM with TCP; Wed,  6 DEC 89 09:46:19 PDT
Date: Wed, 6 Dec 89 09:44 PST
From: "Kevin Oberman, LLNL, (415)422-6955" <OBERMAN@icdc.llnl.gov>
Subject: Transmit timer
To: INFO-VAX@SRI.COM
X-Vms-To: IN::SRI.COM::INFO-VAX

>    In Bill Hancock's column in the October 30 issue of "Digital Review", 
>he discusses altering the time interval between two successive Ethernet 
>packets transmitted by the same DECnet node.  This is of great interest
>since apparently a fast machine can overrun a slower machine by 
>transmitting packets without a break and making it necessary to retransmit 
>packets.
>
>    He says "A DECnet session was used for this, and the gap was adjusted
>with the Circuit parameter Transmit Timer, which is one-sixteenth of a
>second value." (page 39, last column) 
>
>    Now the DECnet VAX documentation mentions a "transmit timer" but only 
>in connection with DDCMP ciruits.  NCP SHOW CHARACTERISTICS CIRCUIT BNT-0
>does not show any transmit timer.

What! Bill Hancock be wrong! NEVER!

In fact, the transmit timer is valid for Ethernet devices as well as DDCMP.
Just NCP SET CIRC xxx-0 TRANSMIT 1 and you will get the effect.

Since the granularity of the transmit timer is so course, I doubt that you will
want to go larger than 1, but since it may be changed without shutting down the
net, you can play with it easily. This is VERY significant on systems using
DEBNA and critical on systems using the new DEBNI.

					R. Kevin Oberman
					Lawrence Livermore National Laboratory
					Internet: oberman@icdc.llnl.gov
   					(415) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.