| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 459.1 | Housecleaning/moving | RMULAC.DVO.DEC.COM::S_WATTUM | | Tue Nov 12 1996 08:17 | 9 |
| 459.2 | where do I find info on #290 | KERNEL::TALBOT | Trevor Talbot | Fri May 23 1997 12:14 | 6 |
| Please can you point to me to info on #290,
I have a problem that maybe the same...but need your details on this case to be
sure.
-Trev
|
| 459.3 | | RMULAC::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Fri May 23 1997 12:30 | 14 |
| #290 refers to a problem with the following symptoms:
NCL> show node <remote_node> osak protocol versions
or
NCL> show node <remote_node> osak all
NCL returns the following error messages:-
command failed due to:
return data corrupt or incorrectly encoded on remote system
|
| 459.4 | | KERNEL::TALBOT | Trevor Talbot | Fri May 23 1997 12:40 | 14 |
| Hi,
Thanks for the reply,
This may not be the same...but,
ncl> show mts ....
gives unavailable resource and in a an output file we get osak_s_invaei with a
status:256
any ideas if the latest eco for osak fixes this....
-Trev
|
| 459.5 | | RMULAC::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Fri May 23 1997 13:42 | 7 |
| This is not the same problem, and you should take this problem up with X.400
engineering
.
It sounds like you are issueing a command which is causing the MTS network
management agent to "wave 4 in the air" and that's the reason for the "process
error" - it is unlikely that the OSAK ECO would have any impact on this, though
it probably would not hurt to go ahead and apply it.
|