| 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 |
I had the MCCELM010 FT kit installed sometime ago and recently updated to
the V1.0 version. This version was the one for those who had the FT
installed earlier.
It was a full installation with dictionary and parse table built.
The FDDI STATE and OPTICAL BYPASS STATE for LINE, shows up as unknown
attributes.
The log file is below:
$MCC
DECmcc (V1.1.0)
SHOW MCC 0 CONC_AM ALL CHAR
MCC 0 CONC_AM
AT 29-AUG-1991 10:57:40 Characteristics
Examination of attributes shows:
Component Identification = "DECmcc Concentrator AM"
Component Version = V1.0.0
SHOW CONC DC500A LINE 1 ALL FDDI STATE
%MCC-W-ATTRUNKNOWN, unknown attribute FDDI
SHOW CONC DC500A LINE 1 ALL OPTICAL BYPASS STATE
%MCC-W-ATTRUNKNOWN, unknown attribute OPTICAL
SHOW MCC 0 BRIDGE_AM ALL CHAR
MCC 0 BRIDGE_AM
AT 29-AUG-1991 10:57:41 Characteristics
Examination of attributes shows:
Component Identification = "DECmcc Bridge AM"
Component Version = V1.2.0
SHOW BRIDGE DB500A LINE 1 ALL FDDI STATE
%MCC-W-ATTRUNKNOWN, unknown attribute FDDI
SHOW BRIDGE DB500A LINE 1 ALL OPTICAL BYPASS STATE
%MCC-W-ATTRUNKNOWN, unknown attribute OPTICAL
EXIT
What could be causing this problem?
Raj
ACT Singapore
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1417.1 | Remove the word 'ALL' | WLYWLD::SZABIET | Tue Sep 03 1991 17:04 | 14 | |
Raj,
Try entering your FDDI STATE and OPTICAL BYPASS STATE commands
without using the word 'ALL'. Use 'ALL' when you wish to see
all attributes that belong to a partition.
MCC> SHOW CONC DC500A LINE 1 FDDI STATE
MCC> SHOW CONC DC500A LINE 1 OPTICAL BYPASS STATE
MCC> SHOW CONC DC500A LINE 1 ALL CHAR
^^^
Hope this helps,
Linda
| |||||
| 1417.2 | use of all | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Wed Sep 04 1991 11:29 | 6 |
Linda is right on target. To check out the acceptable attribute names they should be in the on-line help (if they have one). You can also use the PF@ context sensitive help from the fcl forms mode to find out what valida partitions are supported for this entity class. | |||||
| 1417.3 | Still the same | ZPOVC::RAMARAJ | Wed Sep 04 1991 13:01 | 10 | |
Linda,
Even without the ALL, its the same error, unknown attribute FDDI or
OPTICAL BYPASS.
Jill,
In forms the valid partitions does not show FDDI or OPTICAL BYPASS.
Raj
| |||||
| 1417.4 | how to look up the right parseable name | GOSTE::CALLANDER | Sat Sep 07 1991 10:47 | 33 | |
Raj,
It really looks like you are entering the syntax wrong for the command.
At this point the only easy way to find out what the real names
for the attributes are, are to go to the source.
When you rebuilt the parse tables at installation time, did you
happen to keep around the MCC_PTB_PARSER.DAT file? this file contains
a listing of all valid directive/entity combinations including the
attribute names. Check that file for the list of valid attribute
combinations. By the fact that the PF2 key gave you the context
sensitive help and not an error, you must have correctly completed
the installation.
If you do not have the .DAT around and do not want to create a new
one, then you will have to check it in DAP.
$manage/tool/dict (requires prives to access the dictionary files)
DAP> SHOW CLASS CONCENTRATOR SUBCLASS LINE
(mind you, you must enter the class names exactly as registered,
see on-line help v:show e:PF2 to see the registered names)
This will list all commands and attributes supported for the entity
class. When you see on that interests you:
DAP> SHOW ATTRIBUTE name_of_interest DEFINITION PRESENTATION_NAME
to see what string the parser expects. Checking the .DAT is definitely
a fast way if you have it around.
jill
| |||||