| Using DNS as the DECmcc namespace repostitory is usually convenient
for people running DECnet/OSI, since they usually are running DNS for
use with DECnet before they start with DECmcc. However, there is nothing
to prevent using a local file namespace in DECmcc while using DECnet/OSI.
Have you checked the NOTED::MCC-TOOLS conference for a procedure to
extract entities from the namespace? If you don't find anthing there,
contact Rob (TOOK::R_SPENCE) Spence.
-- Erik
|
| While using LOCAL_NS for MCC on an OSI node (using DNS) may not be a generic
problem I believe base note is looking for information about managing "other"
phase_v entities. I currently use a private_ns and have only bumped into one
'problem' managing phase_v entities of another NS....so far. Whether it's a
private NS or your proposed local NS the same theories apply. When using
phase_v event sinks the managed entity will send its fullname (from the other
NS) with the event. The map notification process can't deal with this and in
theory you can't get the event onto the map.
Theory doesn't always stop the persistent user though. I set up targetting
with wildcards and was able to get the event onto the map. The only problem is
that I can't 'see' the target info now when I do a DIRECTORY of TARGETs. This
appears to be a minor problem so the question goes to the engineers: Can we get
this fixed, although not originally supported??? Many, many, many, many users
will want to manage phase_v entities from either the MIR or a different NS,
this would be a big help for not restricting personal mngmt environments.
thanks,
brad...
|