Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!evax!utacfd!letni!mic!montagar!fallout!eden
From: eden@fallout.uucp (Robert Eden)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Problem while Copying Files
Message-ID: <3051@fallout.uucp>
Date: 4 Mar 91 12:51:41 GMT
References: <1991Feb27.180011.9530@nrcnet0.nrc.ca>
Organization: DECUS DFWLug BBS - Dallas, TX
Lines: 49

>      For the copy command and its following errors are as follows:
> 
>          $COPY FOX"GUEST PWD"::M60.DAT M60.DAT
>     
>          %COPY-E-READERR, error reading FOX"GUEST PWD"::DISK$FOX:[GUEST]M60.DAT
>          -RMS-F-SYS, QIO system service request failed
>          -SYSTEM-F-LINKEXIT, network partner exited

"network partner exited" is one of the most poorly described errors you
can get on VMS (I consider it right up there with exceeded quota).
Here's what happens when you start a decnet link..

                         Sender     Receiver
		Connect Request  |  Connect Acknowledge
                                 |  Connect Confirm 
                          ----- data -----

When DECNET receives a connect request it creates a process in the
requested context. Once the process has been sucessfully started, the
CONNECT ACKNOWLEDGE is sent to the originator.  The created process then
executes the system's SYS$SYLOGIN and users's LOGIN.COM file just like any
other process.  Once this is done, this process then runs the appropriate
application program (FAL in this case).  This program must open a channel
back to the original user (SYS$NET) causing the CONNECT CONFIRM to be sent.

If the SYS$NET file is not opened within the originator's DECNET OUTGOING TIMER
characteristic, the NETWORK PARTER EXITED error is returned to the originator.

Unless the destination system is very slow, the problem is most likely with
the users's LOGIN.COM file.  If you do something that causes the process
to terminate you will get that message (SET TERM/INQ used to do that, 
but it only returns a warning now.)  I suggest you add the following
line to the top of this users's LOGIN.COM.

 		$ if f$mode().eqs."NETWORK" then exit

This will skip the entire LOGIN.COM file.  You can also check the user's
NETSERVER.LOG file for any errors.  (it is SYS$OUTPUT for that receiver
process)  I don't think the router is causing you problems.


p.s. - I don't have my DECNET internal's manual handy so I can't be sure
       of the specific names of parameters and such, but idea is correct.
-- 
-------------------------------------------------------------------------
Robert Eden    817-897-0491                             EDEN@fallout.uucp
Commanche Peak Steam Electic Station                    Glen Rose, TX
               ^^^^^^^^^^^^^^^^^^^^^ politicese for a nuke plant
-------------------------------------------------------------------------