| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 170.1 | Try this... | TOOK::STRUTT | Colin Strutt | Fri Jul 06 1990 11:10 | 9 |
| Please humor me (or, if you're not American, humour me)
Please try
SHOW MCC 0 BRIDGE ALL ATTRIBUTES
It seems possible that the Bridge AM was not enrolled. (Or perhaps some
of the FMs were not enrolled properly).
Colin
|
| 170.2 | ID802_ERROR when Registering a bridge | BEAGLE::LORPHELIN | Chr Lorphelin TSCG/VBO | Fri Jul 06 1990 11:43 | 27 |
| Argh ...
It seems Bridge AM is enrolled :
$ mana/enterp
DECmcc (T1.0.1)
SHOW MCC 0 BRIDGE ALL ATTRIB
MCC 0 BRIDGE_AM
ALL ATTRIBUTES
AT 6-JUL-1990 16:36:50
Available Ports = { "XQA0:" }
Component Identification = "DECmcc Bridge AM"
Component Version = T1.0.1
REGISTER BRIDGE COMMS ADDRESS={08-00-2B-0B-66-1F}
%MCC-E-ID802_ERROR, Error in ID802 value
SHOW BRIDGE COMMS
Using default ALL IDENTIFIERS
BRIDGE NESEVO_NS:.COMMS
Identifiers
AT 6-JUL-1990 16:36:55
No such entity: BRIDGE NESEVO_NS:.COMMS
Unknown Entity = BRIDGE NESEVO_NS:.COMMS
|
| 170.3 | is Config enrolled? | TOOK::HAO | | Fri Jul 06 1990 12:49 | 14 |
| Note that Register commands goes to the Config FM. Could you check if
Config has been enrolled?
According to the error message you get when you try to enter the
address with surrounding curly braces, it looks as if the Address argument
is defined with a datatype of ID802, not a Set-of ID802. Therefore,
you don't need the braces.
Christine
|
| 170.4 | Enroll Config FM!? | CHRISB::BRIENEN | Chris Brienen - DECmcc (non-DECnet) AMs | Fri Jul 06 1990 12:54 | 18 |
|
The correct syntax for this command is:
REGISTER BRIDGE COMMS ADDRESS 08-00-2B-0B-66-1F
(equal sign is also allowed).
Several possible problems:
1. MCC-Bridge AM not enrolled (you've verified this)
2. Correct syntax (see above)
3. MCC-Config FM not enrolled <------- TRY THIS!
--------
My guess is that #3 is your problem (CALL_FUNCTION is failing and
never reacing CALL_ACCESS dispatch table).
|
| 170.5 | New <REGISTER BRIDGE> syntax ! | BEAGLE::LORPHELIN | Chr Lorphelin TSCG/VBO | Mon Jul 09 1990 10:24 | 8 |
|
Thanks a lot for your answers.
The syntax was the problem.
I was using T1.0.0 syntax !
{ CONFIG_FM was correctly enrolled.}
One question : Why should we REenroll CONFIG_FM , etc...
as MCC_STARTUP_DIR is doing it ?
|
| 170.6 | user vs. developer | GOSTE::CALLANDER | | Tue Jul 10 1990 14:16 | 11 |
|
One possible reason a user might have enrollment problems is when
they have made SYS$SPECIFIC copies of certain pieces of the kits;
like dispatch tables. A lot of our users are also developing AM's
and for this reason frequently have copies of certain MCC files
located in private directories with the MCC logicals redefined to
point to these locations. In these cases many times the installation
procedures will only affect the global (common) files and not the
private version.
|