[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
215.0. "WITH and attributes data type + UNDEFINE error." by HERON::MORALES (DEC:.VBO.EIS.Telecom.DTN828-5383) Mon Jul 30 1990 11:16
I have installed ETFT update 1.0 and ift 1.1, I have encountered the
following errors:
1-
***************************************************************************
SYSTEM-MINKA>manage/enter
DECmcc (T1.0.1)
MCC> define mynode node4 minka
MCC> sho mynode
Using default ALL IDENTIFIERS
Node4 51.1022
Identifiers
AT 30-JUL-1990 15:47:14
Examination of Attributes shows:
Address = 51.1022
Name = MINKA
MCC> undefine
%SNO-F-NOMSG, Message number 001F507C
%MCC-F-TRM_FAILURE, PM unable to continue
SYSTEM-MINKA>
***********************************************************************
You have the same results without defining anything just typing
MCC> undefine
This worked ok with MCC T1.0.0
2-In the EFTupdate release notes it is said that WITH qualifier doesn't
support constructor data type.How can I know an attribute's data type ??
Is this the reason why I have the following error:DECmcc (T1.0.1)
MCC> sho bridge *, with (hardware type = DEBET LAN bridge 200)
Using default ALL IDENTIFIERS
%MCC-E-UNBAL_OPENCLOSE, Open and close delimiters are not balanced
This works with other attributes.
Best regards,
Manuel.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 215.1 | hardware types supported | GOSTE::CALLANDER | | Mon Jul 30 1990 19:34 | 22 |
|
the undefine error is part of qar #1090 in the mcc_dev data base.
Thank you for noticing it. It is a case of a return status not being
reset to return the error. Undefine needs to be followed by the
symbol to undefine. (Nice to at least know people are using the
features of the FCL).
Okay the other WITH problem is due to the fact that the hardware
type you entered is incorrect. I will have to look into why you
got such a horrendous message; my guess is that since the type was
wrong it couldn't figure out what to do with the 200) at the end.
the correct hardware types are:
"DEBET LAN Bridge 100"
"DEBET LAN Bridge 150"
"DEBAM LAN Bridge 200"
"Vitalink Translan III"
"Vitalink Translan 350"
"Unsupported Bridge"
|