Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ucbvax!info-vax
From: VENARD@EDUCOM.BITNET
Newsgroups: mod.computers.vax
Subject: "Network partner exited" message
Message-ID: <8601030741.AA10116@ucbvax.berkeley.edu>
Date: Fri, 3-Jan-86 02:42:14 EST
Article-I.D.: ucbvax.8601030741.AA10116
Posted: Fri Jan  3 02:42:14 1986
Date-Received: Sat, 4-Jan-86 00:21:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: info-vax@sri-kl.arpa

We are a VAX site running version 4.1 of VMS.  We have jnet version 1.2
RSCS emulation software to enable our link to BITNET.  From time to time,
users sending network messages from within the VMS Mail Utility are confronted
with the following message:

        %MAIL-E-LOGLINK, error creating network link to node 0
        -System-F-Linkexit, network partner exited

After re-trying the same message 2 or 3 times the error goes away and the
message is successfully sent, but this is annoying.

The System Messages and Recovery Procedures Manual says this message means
the log file on the remote node was not open or was write locked.  Does this
make sense?  Does jnet really send a signal to the target node to check if
the "log file" is available, before it lets the user send a message to that
node?  Has anyone else seen this message?

Regards,

  Robert Venard