| Ian,
All this says is that in the MS, the variant information for routing counters
is not quite correct. An attribute with code 43 is being returned in outp but
the form generated by looking at the DEPENDS ON info does not have that
attribute.
I know that the phase 5 team has a few such problems like this to clean up
after FT release. Perhaps they might comment further.
Verna
|
| I suspect that in this case the attribute is missing from the MSL. The
Routing MSL on DSSR doesn't use the DEPENDS ON clause (although I only
checked the NCL form -- someone could have added it to the MCC form). The
attribute is Manual Addresses Dropped from Area. I don't know why it is
missing from the MSL included with that kit -- it is present in the current
MSLs and I don't remember it being a recent addition.
By the way, why on earth would MCC pay any attention to DEPENDS ON
information for *response* parameters (attribute values, response arguments,
etc.)? MCC has the absolute, definitive statement of whether an attribute is
going to be in the response or not by looking to see if it actually *is* in
the response! The DEPENDS ON information cannot add anything at that time.
The DEPENDS ON info is useful for telling people what you expect to see
returned and, for example, for supplying a menu of attributes to allow the
user to pick some. However, if the user has asked for ALL COUNTERS and gets
some which shouldn't be there according to the DEPENDS ON clause then MCC
shouldn't bat an eyelid. It is like the DEFAULT= clause: it is there for
information only and to help with some UI styles. You should assume it is
always wrong (it usually is!).
Graham
|