Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!hao!ames!necntc!jeff
From: jeff@necntc.UUCP
Newsgroups: comp.os.vms,comp.sys.dec,comp.dcom.lans
Subject: DECNET across x.25
Message-ID: <4081@necntc.NEC.COM>
Date: Thu, 7-May-87 16:11:23 EDT
Article-I.D.: necntc.4081
Posted: Thu May  7 16:11:23 1987
Date-Received: Sat, 9-May-87 05:17:35 EDT
Organization: NEC Electronics Inc.  Natick, MA 01760
Lines: 35
Keywords: DML DECnet x.25
Xref: utgpu comp.os.vms:439 comp.sys.dec:157 comp.dcom.lans:406
Summary: how to determine the cost of an X.25 DLM DECnet circuit

As the summary states, we are in need of finding out how much
overhead there is in maintaining a DLM circuit across X.25.

The current situation is this:

In the USA, there is one system (VMS) hooked up to TYMNET via
a 9.6kbps HDLC line and the VAX PSI software.  We run on an
8300 using the DMB32 for our psi sync port.  All this works nice.

There are many other systems within the USA but only the one node
with the X.25 connection.  We have setup PSI ACCESS for the other 
nodes in the USA to utilize the X.25.  Now the problem.

We have sites in Europe that we must connect to for transfer of
data.  I have succeeded in established an X.25 DLM circuit to
one machine in Germany on Datex-p.  I have found that during
the day (0700-2000 EST), throughput is horrible and the link
is extremely prone to faults (circuit fault type messages from decnet).

I have a couple of questions/queries given this backgroud:

1)  What parameters may be tweeked to help maintain this circuit?

2)  How may the actual cost of maintaining this circuit be determined?

If you have any experience with X.25 DLM circuits, I sure would like
to chat with you for a little bit...  

Please respond via email.

Regards,

-- 
Jeff Janock - NEC Electronics +1 617 655 8833 jeff@necntc.NEC.COM
{ames, decvax, harvard, linus, mit-eddie}!necntc!jeff