| Well, first off, 3.0 is no longer suppported.
Second, the error message is bizarre - dcp usually SENDs
control messages, it doesn't RECEIVE them.
Because I'm curious, if you get a trace (use the -d switch
to dcp), I'll take a look. But even if its a problem on
the UNIX side, we're not going to do a 3.0 fix.
Vince
|
|
Vince,
here the trace:
dcp -d p/300,54/PRIV::IMBBA6.CMD /usr/var/tmp/imbba6.cmd 2>&1 > TRACE
-> DAP - transmitted configuration message (unblocked), length = 17
00 20 12 0d 07 00 00 01 00 a2 c0 d1 f1 8e a8 a0 04
<- DAP - received configuration message (unblocked), length = 17
26 04 04 01 07 00 00 02 00 f7 fb d9 fe ae bc a6 0c
-> DAP - transmitted attributes message (blocked), length = 4
0d 01 02 02
-> DAP - transmitted access message (unblocked), length = 17
01 00 0a 49 4d 42 42 41 36 2e 43 4d 44 02 00 91 06
...IMBBA6.CMD....
<- DAP - received name message (blocked), length = 6
08 04 44 55 30 3a
..DU0:
<- DAP - received name message (blocked), length = 7
04 05 5b 31 2c 31 5d
..[1,1]
<- DAP - received name message (blocked), length = 14
02 0c 49 4d 42 42 41 36 2e 43 4d 44 3b 31
..IMBBA6.CMD;1
<- DAP - received attributes message (blocked), length = 23
cd 80 7d 01 02 02 02 02 00 88 cb 45 41 00 02 02 00 02 02 00
46 01 00
<- DAP - received date and time message (blocked), length = 39
0b 31 37 2d 46 45 42 2d 39 35 20 31 33 3a 33 38 3a 35 31 30
32 2d 4f 43 54 2d 39 35 20 30 30 3a 35 38 3a 31 33 03 00
.17-FEB-95 13:38:510
2-OCT-95 00:58:13..
<- DAP - received name message (blocked), length = 23
01 15 44 55 30 3a 5b 31 2c 31 5d 49 4d 42 42 41 36 2e 43 4d
44 3b 31
..DU0:[1,1]IMBBA6.CM
D;1
<- DAP - received acknowledge message (unblocked), length = 0
-> DAP - transmitted control message (unblocked), length = 3
02 08 00
<- DAP - received acknowledge message (unblocked), length = 0
-> DAP - transmitted control message (unblocked), length = 5
01 49 03 00 02
<- DAP - received status message (unblocked), length = 2
Invalid Message, CONTROL message error, Block count field (BLKCNT).
18 91
dcp: error reading "DU0:[1,1]IMBBA6.CMD;1", Bad format DAP message received
Invalid Message, CONTROL message error, Block count field (BLKCNT).
-> DAP - transmitted access complete message (unblocked), length = 1
01
<- DAP - received access complete message (unblocked), length = 1
02
Bye.
Paolo
|
| Things become a bit clearer. The RSX system doesn't like
the block count field OSF sends in its control message.
We send a value of 2, which is quite normal, and should fit
in the negotiated buffer size (2*512 + few-bytes-overhead) <
1062 (the buffer size RSX gave us).
Has anything changed on the RSX system? What happens if you
try image mode (dcp -i) ?
Vince
|
|
Vince,
with a dcp -i the problem is the same, apparently nothing is changed
on RSX11 system, it is an old installation
In his lan he has a VAX with OpenVms 5.5-2 and DECnet phase iv
the copy works fine from PDP to VAX and UNIX to VAX and vice-versa.
Now the customer is investigating on RSX11 and testing from an Alpha
with 3.2c.
I'll post here the news.
Bye.
Paolo
|