| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4028.1 | Question is a bit sketchy... | TOOK::MINTZ | LKG2-2 near pole X3, cube 6072, dtn 226-5033 | Wed Nov 04 1992 13:35 | 6 |
| Perhaps if you give us the exact syntax that you are using for the show
command, and the error message, then we might be able to help.
While we're at it, which operating system are you using, and
what version of DECnet is installed?
|
| 4028.2 | | TOOK::GUERTIN | Don't waffle (unless you want to) | Wed Nov 04 1992 16:06 | 3 |
| And I assume you are using FCL?
-Matt.
|
| 4028.3 | | STKHLM::AMARTENSSON | | Mon Nov 09 1992 04:23 | 11 |
| Hi,
It is the same problem as in note 4019 and 3933.
The operating system version is VMS 5.5 and I use the iconic
map.
Error message is: "No corresponding entity instance exists".
I will provide a logfile if it helps.
Anna-Lena
|
| 4028.4 | MCC012_EXT - QAR 536 | TOOK::MINTZ | LKG2-2 near pole X3, cube 6072, dtn 226-5033 | Mon Nov 09 1992 09:05 | 3 |
| This note has been consolidated with other notes and entered
as QAR 536 in MCC012_EXT (see note 7).
|
| 4028.5 | | VERNA::V_GILBERT | | Tue Nov 10 1992 09:57 | 11 |
| For V1.3, the Iconic Map will continue decoding an examine directive even if
it has difficulty with any of the attributes. Instead of stopping decoding
with the first error status and displaying only the status, any attribute
which returns an error while being decoded will display -ERROR- in the text
widget associated with the attribute, and a popup message will display with
the following information:
Error decoding attribute <attribute name>
text of error message
Verna
|
| 4028.6 | -ERROR- is not enough for my customer | COPCLU::SORENC | S�ren H Christiansen - (7)857-2107 | Mon Dec 14 1992 08:43 | 23 |
| I have seen the same thing with a customer. The problem seems not to be
the decoding itself, but more the return value from DNA4_AM, when
access is specified. When you specify DEFAULT ACCESS for a node is
appears correctly (even the attribute name is right !), but when you in
addition specify ACCESS this appears as an error for this 'new'
attribute administrativeState, which does not make sence (?).
You can easily reproduce this by trying the following commands:
NCP: set node xxx access both
show node xxx char (to verify parameters)
MCC: show node4 xxx all char
<< here you get the error >>
NCP: clear node xxx access
MCC: show node4 xxx all char
<< no problem (the access field does not appear) >>
The QAR states that in V1.3 decoding will continue with -ERROR-, but I
rather have the attributes appear correctly (as can be seen with NCP).
Regards,
S�ren
|