ratilal@nrcnet0.nrc.ca (Ratilal Haria Rm 103 M60) (02/28/91)
Hello,
We need help and wonder if somebody has come across this before.
We are using Cisco version 8.1(14). When copying files across
2 DEC machines, the copy is not completed.
The two Ciscos are connected via a 56K serial line. The configuration
for DECNET is:
decnet cost 1
no decnet route-cache.
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
.
.
-RMS-F-WBE, error on write behind
Only 2048/2416 block were copied
Our VAX manager thinks the problem is with Cisco and yet we cannot
see what other options we can use.
ANY help/suggestions welcomed.
Thanks in advance ....
Ratilal Haria
--
*------------------------------------+------------------------*
|Ratilal Haria | Ratilal.Haria@NRC.CA |
|National Research Council of Canada | RRH@NRCVM01 |
|Networks Branch | ratilal@nrcnet0.nrc.ca |eden@fallout.uucp (Robert Eden) (03/04/91)
> 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 -------------------------------------------------------------------------