From: CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 24-JAN-1989 04:29 To: MRGATE::"ARISIA::EVERHART" Subj: RE: Async DECnet problems Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 23 JAN 89 11:54:43 PDT Received: from relay.ubc.ca by KL.SRI.COM with TCP; Mon, 23 Jan 89 11:39:22 PST Received: by relay.ubc.ca (5.59/1.14) id AA26795; Mon, 23 Jan 89 11:39:26 PST Date: 23 Jan 89 11:39 -0700 From: Ed Grochowski To: Message-Id: <182*pettvi@pet.med.ubc.ca> Subject: RE: Async DECnet problems >We have two MicroVAX computers which are connected by modem using >async DECnet. When either system reboots or crashes, the DECnet >connection between does not get re-established without some kind >of work-around solution. DECnet starts correctly, but NCP command >SHOW KNOWN CIRCUIT reveals that circuit TX-0-3 is "on -starting". >Now if I stop the network and then restart it, it finally works. >I did not have these problems when the computers were in the same >office and connected directly, they only started when we put modems >between the systems. They are UDS modems connected via our own >microwave comm system. >In the system startup procedures, I have set the terminal device >as DDCMP, etc... , and all of the DECnet parameters are in the >permanent database. Again, it worked when the two systems were >side by side, and now nothing. I had very similar problems with an asynchronous DECnet connection that ran over a leased phone line with data sets on each end. We performed the terminal set up as follows: SET TERM/PERM/PROT=DDCMP/EIGHT/NOLINE/NOTYPE/NOECHO "Term_port" The important qualifier is the NOTYPE (which is short for notypeahead). This sets the terminal ports up to ignore any unsolicited input (i.e. noise on the line, etc..). This seemed to do it for me. ------------------------------------------------------------------- Ed Grochowski UBC/TRIUMF Pet Program CDNnet: pettvi@pet.med.ubc.ca BITNET: edgro@triumfcl.bitnet -------------------------------------------------------------------